CA RiskMinder UNIX Installation Guide › Upgrading RiskMinder › Upgrading to Release 3.1 › Migrating the Database to Release 2.2.7 for RiskMinder
Migrating the Database to Release 2.2.7 for RiskMinder
Important! Perform this procedure in this section only if you are upgrading from release 1.x. If you are upgrading from release 2.x or 3.0.x, you can ignore this procedure.
After you migrate the database for Arcot common components, migrate the database to the release 2.2.7 state for RiskMinder components.
Follow these steps:
- Copy the arcot-riskfort-upgrade-1.x-2.2.7.zip file to the ARCOT_HOME directory.
- Extract the contents of the arcot-riskfort-upgrade-1.x-2.2.7.zip file in this directory.
- Navigate to the following directory:
$ARCOT_HOME/dbscripts/<db_type>/upgrade-scripts
Here, db_type can be mssql or oracle.
- Run the SQL script corresponding to your current release of RiskMinder, as listed in the following table.
Current RiskFort Release
|
SQL Script to Run
|
1.5.1 or 1.5.1.x
|
arcot-riskfort-upgrade-1.5.1.8-2.2.7.sql
|
1.6 or 1.6.0.x
|
arcot-riskfort-upgrade-1.6.0.3-2.2.7.sql
|
1.7 or 1.7.0.x
|
arcot-riskfort-upgrade-1.7.0.3-2.2.7.sql
|
- Navigate to the following directory:
$ARCOT_HOME/dbscripts/<db_type>/upgrade-scripts/
Here, db_type can be mssql or oracle.
- Run the arcot-post-upgrade-for-common-1.0.sql script.
This script results in the following changes:
- The user ID for Master Administrator is changed from MASTER_ADMIN to MASTERADMIN.
- The password for the MASTERADMIN account is master1234!
- The organization that MASTERADMIN belongs to is MASTERADMIN. This configuration is useful when you filter reports.
- The Administrators group is configured with WebFort User/Password authentication. Administrators belonging to this group must continue to use the same user name and password.
- Group2 is the initial Default Organization.
Copyright © 2013 CA.
All rights reserved.
|
|