CA RiskMinder Windows Installation Guide › Troubleshooting RiskMinder Errors › Database-Related Errors

Database-Related Errors

Problem:

I ran the RiskMinder database scripts and I did not see any errors. However when i try to access a RiskMinder table, I see an error message stating that the table does not exist.

or

I am using Oracle database and I see the following error when I try to access a table:

ERROR : common.database.DBFOManagerImpl(65) : Failed to retrieve Database error codes for Datasource[1]. Error: ORA-00942: table or view does not exist.

Cause:

• The database user that you used to run the scripts did not have the required file permissions.
• You did not run the database scripts in the specified order.

Solution:

Do the following:

1. Ensure that the user has the right file permissions.
2. Clean up the database.

   See section, "Dropping RiskMinder Schema" for detailed instructions.

3. Run the database scripts again in the right order.

   See section, "Running Database Scripts" for more information in case of single-system installation.

   See section, "Running Database Scripts" for more information in case of distributed-system installation.

4. Run the following query to verify if the database was seeded correctly:

   SELECT SERVERNAME, VERSION FROM ARRFSERVERS;
   

Problem:

The connection to my Oracle database fails with the following entry in the RiskMinder Server log file:

ReportError: SQL Error State:08001, Native Error Code: 30FD, ODBC Error: [DataDirect][ODBC Oracle driver][Oracle]ORA-12541: TNS:no listener

Solution:

Check the following:

• Listener service on your database server.
• The TNSnames.ora file settings on the system where RiskMinder Server is installed.

Problem:

Connection to the Oracle database fails with the following entry in the RiskMinder Server log file:

TNS:listener could not resolve SERVICE_NAME given in connect descriptor

Solution:

Check for the following:

• Database is started. If it is not, you will see the above message.
• If the database is running, probably the database has not registered yet with the listener. This occurs when the database or listener just starts up. Typically, this problem should be solved by waiting a minute or so.
• If you are using static registration, make sure the SERVICE_NAME entry used in the connection string (TNSNAMES.ORA, NAMES, OID, ...) matches a valid service know by the listener.
• You can use C:>tnsping SERVICE_NAME - to check the status or C:>lsnrctl services - to verify all the services known to listener.

Problem:

Connection to the Oracle database fails with the following entry in the RiskMinder Server log file:

ORA-03113: end-of-file on communication channel

Cause:

This is a generic error that indicates that the connection has been lost. This can be caused by many reasons such as:

• Network issues or problems
• Forceful disconnection of a Server session
• Oracle Database crash
• Database Server crash
• Oracle internal errors, such as ORA-00600 or ORA-07445, causing aborts
• Oracle Client or TNS layer inability to handle the connections

Solution:

Check for the possible causes mentioned in the preceding list.

Problem:

Connection to the database fails with the following entry in the RiskMinder Server log file:

Database password could not be obtained from securestore.enc

Cause:

The database details might not be available in securestore.enc file.

Solution:

Use the DBUtil tool to update the securestore.enc file with the database details.

Book: Refer to CA RiskMinder Administration Guide for more information on how to use DButil.

Problem:

Connection to the MSSQL database fails with the following error:

java.sql.SQLException: No Datasource is set.

Cause:

The possible reason for this problem might be that the required JDBC JAR file might not be copied or might not be copied to the correct location on the application server you are using.

This is because the Administration Console, User Data Service (UDS), and Sample Application, which are Java-dependent components of RiskMinder need Java Database Connectivity (JDBC) Java ARchive (JAR) files to connect to the database.

Solution:

Do the following:

1. If required, download the JDBC JAR file for the database you are using:
   • For Oracle Databases: ojdbc14.jar (version 10.2.0.1.0)
   • For Microsoft SQL Server Databases: sqljdbc.jar (version 1.2.2828)
   • For MySQL: mysql-connector-java-5.1.22-bin.jar (version 5.1.22)
2. Copy or deploy the JDBC JAR:
   • If you are using Apache Tomcat, then refer to the "Apache Tomcat" subsection of the "Step 3: Copying JDBC JAR Files to Your Application Server".
   • If you are using IBM WebSphere, then refer to the "IBM WebSphere" subsection of the "Step 3: Copying JDBC JAR Files to Your Application Server".
   • If you are using Oracle WebLogic, then refer to the "Oracle WebLogic" subsection of the "Step 3: Copying JDBC JAR Files to Your Application Server".
   • If you are using JBoss Application Server, then refer to "JBoss Application Server" subsection of the "Step 3: Copying JDBC JAR Files to Your Application Server".