This chapter describes how to troubleshoot the Oracle Communications Network Integrity installation. For more information on troubleshooting Network Integrity, see Network Integrity System Administrator's Guide. To verify that the installation was successful, see "Verifying the Network Integrity Installation".
This section describes the following installation problems, and how to resolve them:
Problem: Installer Fails to Update Application KEYSTORE Table
Problem: Installer Fails to Update Application INFORMATION Table
Problem: Inability To Run Scans or Resolve Discrepancies After Upgrading
If the installer fails to update the application KEYSTORE table, the installer is interrupted and the following error message appears:
Unable to update application key store 'AppKeyStore', please check log files for more details. Refer to Network Integrity documentation for executing this step manually.
Click the Continue button to complete the installation. Manually update the application KEYSTORE table when the installation is complete.
To manually update the application KEYSTORE table:
Navigate to NI_Home/POMSClient.
Execute the following command:
jre_Path/bin/java -javaagent:lib/eclipselink.jar -cp POMSClient.jar oui.j2ee.poms.client.UpdateAppKeyStore DB_HostName DB_Port DB_ServiceName NI_Schema_UserName NI_Schema_Password default aes 128
where:
jre_Path contains the jre folder inside the Java Development Kit (JDK) installation directory
DB_HostName is the database host name
DB_Port is the database port number
DB_ServiceName is the database service name or system ID
NI_Schema_UserName is a valid Network Integrity database user name for the schema
NI_Schema_Password is the password for the Network Integrity schema user name
Connect to the application KEYSTORE table and verify the following:
That the COMPONENT column has a value of default.
That the ENCRYPTALGORITHM column has a value of aes.
That the KEYLENGTH column has a value of 128.
Restart Network Integrity for the changes to take effect, as explained in Network Integrity System Administrator's Guide.
If the installer fails to update the application INFORMATION table, the installer is interrupted and the following error message appears:
Unable to update application details 'ApplicationInfo', please check log files for more details. Refer to Network Integrity documentation for executing this step manually.
Click the Continue button to complete the installation. Manually update the application INFORMATION table when the installation is complete.
To manually update the application INFORMATION table:
Navigate to NI_Home/POMSClient.
Execute the following command:
jre_Path/bin/java -javaagent:lib/eclipselink.jar -cp POMSClient.jar oui.j2ee.poms.client.UpdateAppInfoTable DB_HostName DB_Port DB_ServiceName NI_Schema_UserName NI_Schema_Password "Network Integrity" NI_Version SUCCESS
where:
jre_Path contains the jre folder inside the JDK installation directory
DB_HostName is the database host name
DB_Port is the database port number
DB_ServiceName is the database service name or system ID
NI_Schema_UserName is a valid Network Integrity database user name for the schema
NI_Schema_Password is the password for the Network Integrity schema user name
NI_Version is the version of Network Integrity being installed
Connect to the application INFORMATION table and verify the following:
That the NAME column has a value of Network Integrity.
That the VERSION column has the correct version of Network Integrity.
That the STATUS column has a value of SUCCESS.
After upgrading Network Integrity, you may be unable to run scans or resolve discrepancies using cartridges if you have unmigrated cartridges still deployed to your system.
To confirm that you are experiencing this issue, verify the following:
Network Integrity displays the following error messages when you try to run a scan:
Unable to start scan, as cartridge is in the process of getting deployed or undeployed.
Network Integrity displays the following error messages when you try to resolve discrepancies:
All Plugins are not ready. Cartridge deploy or undeploy is in progress.
The DisPlugin database table has the value 0 set for the pluginready attribute for some cartridges.
Resolve this issue by doing the following:
Migrate all deployed, unmigrated cartridges that you are licensed and permitted to migrate.
Run the Troubleshoot_delete_unused_plugins_post_upgrade.sql script to delete the remaining unmigrated cartridges from your system:
In Network Integrity, delete all scan configurations related to unmigrated cartridges.
From the command prompt, go to the NI_Home/integrity/upgrade/migration directory.
Enter the following command, to execute the script as the Network Integrity MDS DB schema user, using sqlplus:
Troubleshoot_delete_unused_plugins_post_upgrade.sql
Follow the command-line prompts.
The script deletes all cartridges from the system that have a pluginready value of 0 in the DisPlugin database table.
Restart Network Integrity.
Run a test scan to confirm that the issue is resolved.
This procedure is only applicable if you are running WebLogic Server 10.3.6 on a Solaris platform with a 64-bit JVM.
There is a known issue that is encountered when starting the WebLogic server. Specifically, the 64-bit native libraries are not loaded correctly. To confirm that you have this issue, search the standard output log for the following error:
Unable to load performance pack
If the Network Integrity environment has McAfee AntiVirus software installed, the Application server takes a long time to start.
Add the NI_Home, MW_Home, and WL_Home/server/lib/Java_Home directories to the McAfee exclusion list so that these directories are excluded from being scanned.
where:
NI_Home is the directory in which the Network Integrity software is installed.
MW_Home is the directory in which the Oracle Fusion Middleware products, files, and folders are installed.
WL_Home is the directory in which WebLogic Server is installed. WL_Home is located in MW_Home.
Java_Home is the JDK installation directory.