This chapter contains the following sections:
This chapter lists solutions for common (and uncommon) system problems.
To verify that Oracle Identity Analytics started properly, do one of the following:
Check the log file.
A successful launch of Oracle Identity Analytics is recorded in the application log file, which is named rbacx.log. The entry listed in the log file includes the Oracle Identity Analytics version number and a time stamp that records when the application started.
An example log entry is listed here:
"17:27:11,218 INFO [ContextLifecycleListener] Oracle Identity Analytics (build: 4.1.0.20080903_406_3061) Started"
Open the application in a browser.
You can verify that Oracle Identity Analytics started correctly by typing http://localhost:9080/rbacx in a browser on the local application server machine.
The localhost portion of the URL assumes that you are checking the application from the local application server (that is, you are not checking from a remote machine). The URL also assumes that Oracle Identity Analytics is deployed on TCP port 9080.
If you are opening the URL from a remote machine, format the URL as follows:
http://<application server hostname>:<port>/rbacx
Start and stop Oracle Identity Analytics using the Application Control Panel of your application server. For example, if you are using the Glassfish™ application server, use the Administrative Console to start and stop Oracle Identity Analytics.
This section describes solutions to errors that are commonly encountered when working with Oracle Identity Analytics.
This error occurs when Oracle Identity Analytics is unable to connect to the database. The error is logged in the rbacx.log file.
Failed to obtain DB connection from data source 'springNonTxDataSource.QuartzScheduler': java.sql.SQLException: Connections could not be acquired from the underlying database! [ See nested exception: java.sql.SQLException: Connections could not be acquired from the underlying database! ]
Check the jdbc.properties configuration file in the $RBACX_HOME/conf folder.
Check the conf-context.xml file in the /WEB-INF/ folder.
Ensure that JDBC drivers corresponding to the database type are present in /WEB-INF/lib.
Verify that database server connectivity can be established from the application server.
The following error occurs when the workflows.xml file is not configured properly in the /WEB-INF/classes folder.
Error loading workflow Role Membership Workflow com.opensymphony.workflow.FactoryException: Error in workflow descriptor: [file:/] <WORKFLOWS_FILE_PATH>role-user-membership-workflow.xml: root cause: <$RBACX_HOME>\conf\workflows\role-user-membership-workflow.xml (The device is not ready)
The following error is generated when Oracle Identity Analytics reports cannot be rendered by the system:
20:44:43,498 ERROR [JasperPrintRenderer] Error rendering report: java.io.FileNotFoundException:<$FILE_PATH>\<$FILE_NAME>.jasper
Any inaccuracies in the Oracle Identity Analytics configuration would generate errors and cause Oracle Identity Analytics not to launch. Two common files where configuration errors can cause failure are conf-context.xml and reporting-context.xml.
Some of the common errors are listed here:
java.io.FileNotFoundException: C:\Vaau\rbacx-4.1\conf\jdbc.properties (The system cannot find the path specified) java.io.FileNotFoundException: C:\Vaau\rbacx-4.1\conf\mail.properties (The system cannot find the path specified) java.io.FileNotFoundException: C:\Vaau\rbacx-4.1\conf\ldap.properties (The system cannot find the path specified) java.io.FileNotFoundException: C:\Vaau\rbacx-4.1\conf\iam.properties (The system cannot find the path specified)
The java.lang.OutOfMemoryError exception in the log is caused by Java heap fragmentation. This fragmentation occurs when no contiguous chunk of free Java heap space is available from which to allocate Java objects.
Importing RACF accounts from a file fails when running OIA on WebLogic. The following error is logged:
Error reading object from byte stream
Go to the following location and open iam.properties in a text editor:
$RBACX_HOME/conf/iam.properties
Locate the following line in iam.properties and change the value from 5 to 0:
Old value for WebLogic:
com.vaau.rbacx.iam.file.import.sharedAttributesCompressionLevel=5
New value for WebLogic:
com.vaau.rbacx.iam.file.import.sharedAttributesCompressionLevel=0
Restart the server and try the account import again.