This chapter describes how to troubleshoot the Oracle Communications Unified Inventory Management (UIM) installation.
Before calling Oracle Support, perform the following:
Problems can often be fixed by shutting down UIM and restarting the computer that it runs on. See UIM System Administrator's Guide for more information.
If that does not solve the problem, the first troubleshooting step is to look at the error log for the application or process that reported the problem.
Prepare and gather the following pertinent information:
A clear and concise description of the problem, including when it began to occur.
Relevant portions of the relevant log files.
Relevant configuration files.
Recent changes in your system, even if you do not think they are relevant.
List of all UIM components and patches installed on your system.
When you are ready, report the problem to Oracle Support.
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 UIM 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 Oracle_Home/POMSClient.
Execute the following command:
Java_Home/bin/java -javaagent:lib/eclipselink.jar -cp POMSClient.jar oui.j2ee.poms.client.UpdateAppKeyStore DB_HostName DB_Port DB_ServiceName UIM_Schema_UserName UIM_Schema_Password default aes 128
where:
DB_HostName is the database host name
DB_Port is the database port number
DB_ServiceName is the database service name or system ID
UIM_Schema_UserName is a valid UIM database user name for the schema
UIM_Schema_Password is the password for the UIM 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.
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 UIM 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 Oracle_Home/POMSClient.
Execute the following command:
Java_Home/bin/java -javaagent:lib/eclipselink.jar -cp POMSClient.jar oui.j2ee.poms.client.UpdateAppInfoTable DB_HostName DB_Port DB_ServiceName UIM_Schema_UserName UIM_Schema_Password "UIM" UIM_Version SUCCESS
where:
DB_HostName is the database host name
DB_Port is the database port number
DB_ServiceName is the database service name or system ID
UIM_Schema_UserName is a valid UIM database user name for the schema
UIM_Schema_Password is the password for the UIM schema user name
UIM_Version is the version of UIM being installed
Connect to the application INFORMATION table and verify the following:
That the NAME column has a value of UIM.
That the VERSION column has the correct version of UIM.
That the STATUS column has a value of SUCCESS.
If MDS schema creation through RCU fails and the following error message appears:
ORA-65096: invalid common user or role name.
The error is due to the use of a database name that is not valid for common users or roles. In addition to the usual rules for user and role names, common user and role names must start with C## or c## and consist only of ASCII characters.
When using the RCU installer (see "Creating the Database (MetaData) Schema for UIM"), you need to provide the Oracle 12c pluggable database (pdb) details.
To create a valid user name:
Ensure that the pdb is up.
Open a command prompt and login to SQL*Plus.
Execute the following command to change the open mode of the PDB SID from mounted to opened:
alter pluggable database $PDB_SID open;
Execute the following command to switch to the PDB SID:
alter session set container=$PDB_SID
For more information about how to configure the pdb, see Oracle Database Administrator's Guide, 12c Release 1 (12.1).
If the DB server and the Application server have different dates, then the two servers will not be able to communicate with each other.
Ensure that the Database server and Application server dates are set close to each other. They can have different dates due to time zone differences, but they should not be in different weeks.
See Oracle Database Globalization Support Guide for information and instructions on setting the date.
If the UIM Administrator user is not created during installation, then the user will not be able to login to the UIM user interface or the UIM Web services.
To create the UIM Administrator user, after the UIM installation has been completed, perform the following:
Log in to the WebLogic Administration Server Console.
In the left section, under Change Center, click Lock & Edit.
In the left section, under Domain Structure, click SecurityRealms.
The Summary of Security Realms page appears.
Click myrealm.
The Settings for myrealm page appears.
Click the Users and Groups tab.
Click the Groups tab, click New and enter the following group properties:
Group name
Group description
Provider (select from the list)
Create the new group, click OK.
Click the Users tab, click New and enter the following user properties:
User name
User description
Provider (select from the dropdown list)
User password
Create the new user, click OK.
Click Release Configuration.
Log in to the Enterprise Manager console.
In the left section, expand WebLogic Domain and select the domain name.
Right-click the domain name, select Security, and then select Application Roles.
The Application Roles page appears.
In the Application Stripe field, select oracle.communications.inventory from the dropdown list, and then click the search icon.
A list of role names will appear.
Select the uimuser role and click Edit.
The Edit Application Role: uimuser page appears.
In the Members section, click Add.
The Add Principal dialog box appears.
In the Type field, select Group from the dropdown list and then click the search icon.
Click OK to save and close the Edit Application Role: uimuser page.
If the number of processes is not set high enough to accommodate your installation, the installer is interrupted and the following error message appears:
Unable to run SQL Script.
If you click Retry, the same error message appears.
If you click Continue, errors regarding JMS connections and JDBC connections not being found are encountered.
After the installation completes, you may notice that several database resources in the WebLogic domain were not created. In this situation, the UIM installer log reflects the following:
Exception Name: oui.j2ee.core.exception.JOUIUnabletoConnectException Exception String: Error: Unable to run SQL Script. SQL Exception: Error Code = 17002, SQL State = null, Oracle DB Message = Io exception: Connection refused (DESCRIPTION=(TMP=)(VSNNUM=186647296)(ERR=12516)(ERROR_STACK= (ERROR=(CODE=12516)(EMFI=4)))). Exception signaled in a connect operation. Please check installer log files for more details. Exception Severity: 1
And the UIM installer error log reflects the following:
INFO: Creating SQL script execution log file at [ /scratch/share/domains/clusterUim723b240/UIM/scripts/llr_log.txt] Sep 4, 2016 2:29:12 PM oui.j2ee.core.common.JDBCComponent getEncryptedConnectionImpl SEVERE: SQL Exception: Error Code = 17002, SQL State = null, Oracle DB Message = Io exception: Connection refused(DESCRIPTION=(TMP=)(VSNNUM=186647296)(ERR=12516)(ERROR_STACK= (ERROR=(CODE=12516)(EMFI=4)))) Sep 4, 2016 2:29:12 PM oui.j2ee.actions.database.AI_RunSQLScriptSP installAction SEVERE: Error: Unable to run SQL Script. SQL Exception: Error Code = 17002, SQL State = null , Oracle DB Message = Io exception: Connection refused(DESCRIPTION=(TMP=)(VSNNUM=186647296)(ERR=12516)(ERROR_STACK=(ERROR=(CODE=12516)(EMFI=4)))). Exception signaled in a connect operation. Please check installer log files for more details.
This problem is encountered when your total number of processes exceeds the specified number of processes. The problem can occur when running multiple managed servers, which multiplies the number of database connections used. For example, if you have 3 persistent stores per managed server, and you have 20 managed servers, 60 processes are consumed just for the persistent stores.
Change the number of processes to a higher number. The default number of processes is 150 and Oracle recommends that this value be set to 2000 when installing the database, as described in "Tuning the Database".
To change the number of processes:
Open a command prompt and login to SQL*Plus.
Execute the following command to determine the current number of processes:
show parameter process;
The output shows the following:
NAME TYPE VALUE
---------------------------- ---------- ----------
aq_tm_processes integer 1
cell_offload_processing boolean true
db_writer_processes integer 1
gcs_server_processes integer 0
global_txn_processes integer 1
job_queue_processes integer 1000
log_archive_max_processes integer 4
processes integer 150
processor_group_name string
Execute the following command to change the number of processes:
alter system set processes=2000 scope=spfile;
Execute the following command to validate the current number of processes:
show parameter process;
The output should show the following:
NAME TYPE VALUE
---------------------------- ---------- ----------
aq_tm_processes integer 1
cell_offload_processing boolean true
db_writer_processes integer 1
gcs_server_processes integer 0
global_txn_processes integer 1
job_queue_processes integer 1000
log_archive_max_processes integer 4
processes integer 2000
processor_group_name string
If the timers are not started for any reason, you need to manually restart them.
To restart the timers:
Log in to the WebLogic Server Administration Console.
On the Home page, under Domain Structure, click the Deployments link.
The Summary of Deployments page appears.
Expand oracle.communications.inventory.
Expand EJBs.
Click the TimerBean link.
The Settings for TimerBean page appears.
Click the Control tab.
Select a timer and click Activate Timers.
This restarts the selected timer.
This problem occurs if you create a WebLogic domain for a server cluster installation and deploy the Enterprise Manager to the managed servers. In this scenario the following NullPointerException error can occur:
<ManagedServer01> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <9ce3222e-dd29-4da5-b4a8-73602be2e080-00000003> <1482848744159> <BEA-101165> <Could not load user defined filter in web.xml: oracle.sysman.eml.app.EMTargetAuthFilter. java.lang.NullPointerException at oracle.sysman.eml.app.EMTargetAuthFilter.init(EMTargetAuthFilter.java:119) at weblogic.servlet.internal.FilterManager$FilterInitAction.run (FilterManager.java:374)
Do not deploy Enterprise Manager to the managed servers in a WebLogic domain. Only deploy Enterprise Manager on the Admin Server.