Upgrade Errors

CA RiskMinder Windows Installation Guide › Troubleshooting RiskMinder Errors › Upgrade Errors

Upgrade Errors

This section describes the troubleshooting steps, which will help you resolve the errors that you might face while upgrading RiskMinder.

Problem:

The upgrade tool fails with the following error:

Error Occured: IO exception while parsing, %ARCOT_HOME%\tools\common\upgrade\xml\arcot-<product-name>-upgrade-meta-data.xml

Cause:

The upgrade tool could not find the arcot-<product-name>-upgrade-meta-data.xml file. Here, product-name can be either common or riskfort.

Solution:

Check if the arcot-<product-name>-upgrade-meta-data.xml file exists in %ARCOT_HOME%\tools\common\upgrade\xml\.This error can commonly occur when the arcot-common-db-upgrade.zip file is not extracted using the Extract To Here option.

Problem:

The upgrade tool fails with the following error:

Internal Error: Could not initialize upgrade tool. Error:: Cannot load JDBC driver class 'oracle.jdbc.driver.OracleDriver' Error Occured: Upgrade Initialization Error:oracle.jdbc.driver.OracleDriver

Cause:

The upgrade tool could not find the JDBC library to connect to the database.

Solution:

Check whether the JDBC library is copied to the %ARCOT_HOME%\tools\common\upgrade\lib directory.

If the JDBC library is already copied, then check whether the name of the JDBC JAR file is correctly specified, as described in Step 6 in "Step 2: Migrating the Database for Common Components for RiskMinder 2.x or 3.0" ("Upgrading RiskMinder"). Also, check if the JDBC JAR file corresponds to the database configured in the arcotcommon.ini file against the DbType parameter.

Problem:

The upgrade tool fails with the following error:

FATAL: ARCOT_HOME Environment Variable Not Set

Cause:

ARCOT_HOME is not set.

Solution:

Set the ARCOT_HOME environment variable and run the upgrade tool.

Problem:

The upgrade tool fails with the following error:

Error Occured: Upgrade Initialization Error:Could not create DBService instance"

Solution:

Check if the user name and password are configured correctly in the arcotcommon.ini and securestore.enc files, respectively.

Problem:

The upgrade tool fails with the following error:

Error Occured: Upgrade Initialization Error:Io exception: The Network Adapter could not establish the connection"

Solution:

Check if the JDBC URL is correct and points to the correct database. Ensure that the database is up and running.

Problem:

The upgrade tool fails with the following error:

javax.crypto.BadPaddingException: Given final block not properly padded

Cause:

The key label used to encrypt the data is not the same as the key used for decryption.

Solution:

Ensure that the master key label used to encrypt data in the database is the same as the key label used by the upgrade tool to decrypt data. The master key label is stored in the securestore.enc file in the %ARCOT_HOME%\conf directory.

Problem:

The upgrade tool fails with the following or similar error:

"java.sql.SQLException: ORA-20010: -1031-ORA-01031: insufficient privileges"

Cause:

The database user configured in the arcotcommon.ini file does not have sufficient database privileges to carry out the database upgrade.

Solution:

Ensure that the administrator performing the upgrade has the required database privileges. Installation time privileges are applicable to upgrade also.

Problem:

The upgrade tool fails with the following or similar error:

"ORA-01536: space quota exceeded for tablespace"

Cause:

The database user configured in the arcotcommon.ini file has exhausted the space quota in the tablespace.

Solution:

The DBA must increase the quota for the user. You must restart the upgrade tool after you re-import the pre-upgrade data.

Problem:

After the upgrade process, the Administration Console fails to start and returns the following error:

ERROR : taglib.tiles.InsertTag : ServletException in '/WEB-INF/jsp/dynamic/navbar_GA.jsp': File &quot;/WEB-INF/jsp/dynamic/navbar_GA.jsp&quot;

Cause:

The Work folder of the application server where Administration Console is deployed still contains the cache of the earlier Administration Console version.

Solution:

Clear the Work folder of the application server where Administration Console is deployed and restart the application server.

Problem:

After the upgrade process, an administrator belonging to the LDAP repository can no longer log in to Administration Console.

Cause:

The administrator might be disabled in LDAP.

Solution:

Ensure that the administrator is not disabled in LDAP. Disabled administrators are not allowed to log in to Administration Console.

Problem:

After the upgrade process, RiskMinder Server or Case Management Server do not start and the following lines appear in the log file:

ArDBM::Executing Query[ArRFProtocolRegistryQuery_InsertProtocolDetailsForInstance]
ArDBConnection::GetDBDiagnosis: SQL State:23000, Native Code: 1, ODBC code: [Arcot Systems][ODBC Oracle Wire Protocol driver][Oracle]ORA-00001: unique constraint (XXXXXXX.UN_ARPROTOCOLREGISTRY) violated
Dbm::SQL State:23000, Native Code: 1, ODBC code: [Arcot Systems][ODBC Oracle Wire Protocol driver][Oracle]ORA-00001: unique constraint (XXXXXXX.UN_ARPROTOCOLREGISTRY) violated

Cause:

The auto-generated indexes for the corresponding unique key in Oracle 11g database are not dropped. Even after you run the drop constraint on the unique key, the corresponding index is not dropped.

Solution:

To resolve this issue, do the following:

Run the following SQL commands:

DELETE FROM ARRFINSTANCES;
DELETE FROM ARRFPROTOCOLREGISTRY WHERE INSTANCEID <> 'DEFAULTID';
ALTER TABLE ARRFPROTOCOLREGISTRY DROP CONSTRAINT UN_ARPROTOCOLREGISTRY CASCADE;
COMMIT;

Verify whether the index has been dropped by running the following command:
```
Select * from user_indexes where index_name='UN_ARPROTOCOLREGISTRY';
```
You should not see any rows returned for the preceding query.
Start RiskMinder Server and Case Management Server.