Important! If you have installed CA RiskMinder with AuthMinder and you have completed the RiskMinder upgrade, then do not migrate the database for Arcot common components because this step has already been performed during the RiskMinder upgrade.
Migrate the database for the Arcot common components that are used in release 7.1.01.
Follow these steps:
This folder contains the following zip files that are applicable for this migration path:
%ARCOT_HOME%
Note: For Oracle Database and IBM DB2 UDB, use the JDBC JAR version that is applicable to your database. For Microsoft SQL Server, use sqljdbc4.0 (Microsoft JDBC Driver 4.0 for SQL Server).
%ARCOT_HOME%\tools\common\upgrade\
java [JVM_Options] -jar arcot-common-upgrade-framework.jar [--log-file <log-file-name>] [--log-level <log-level>][--commit-batch-size <batch_size>] [--product-name common][--prompt][--mst]
The following table describes the options that are supported by this JAR:
Option |
Description |
---|---|
JVM-Options |
The following JVM options are required only if LDAP organizations are configured:
|
log-file |
Specifies the path to the log file:
|
-log-level |
Specifies the log level. If you do not provide any value, the upgrade log level is set to INFO. |
commit-batch-size |
Specifies the number of transactions to be issued to the database before a COMMIT statement is issued. |
product-name |
Specifies the name of the product that has to be migrated. The default value is common. |
prompt |
Prompts whether to proceed further after each phase is completed successfully. You can choose to run the tool later to continue from where it stopped. If this option is not specified, the upgrade tool runs without any prompting until the upgrade process is completed. |
mst |
Refers to the Monitoring Sleep Time. If you specify this option, the upgrade tool prints diagnostic messages describing the progress made during upgrade after sleeping for the specified duration (in minutes.) The default value is two minutes. |
The upgrade tool also prints verification information.
Important! While migrating the database, if you encounter errors due to a step that you have performed incorrectly, restore the database backup that you created earlier. After you verify that the database is correctly restored, retry the database migration procedure.
Copyright © 2013 CA Technologies.
All rights reserved.
|
|