1. Installation Guide
  2. Troubleshooting the Unified Inventory Management Installation

8 Troubleshooting the Unified Inventory Management Installation

This chapter describes how to troubleshoot the Oracle Communications Unified Inventory Management (UIM) installation.

Reporting Problems

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.

Problem: RCU Creation Fails Due to Invalid Common User or Role Name

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.

Solution

When using the RCU installer (see "Creating the Database (MetaData) Schema for UIM"), you need to provide the Oracle 19c pluggable database (pdb) details.

To create a valid user name:

  1. Ensure that the pdb is up.

  2. Open a command prompt and log in to SQL*Plus.

  3. Run the following command to change the open mode of the PDB SID from mounted to opened:

    alter pluggable database $PDB_SID open;

  4. Run 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, 19c Release 3 (19.3).

Problem: Database Server and Application Server Have Different Dates

If the DB server and the Application server have different dates, then the two servers will not be able to communicate with each other.

Solution

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.

Problem: Unable to Create the UIM Administrator User Except During Installation

If the UIM Administrator user is not created during installation, then the user will not be able to log in to the UIM user interface or the UIM Web services.

Solution

To create the UIM Administrator user, after the UIM installation has been completed, perform the following:

  1. Log in to the WebLogic Administration Server Console.

  2. In the left section, under Change Center, click Lock & Edit.

  3. In the left section, under Domain Structure, click SecurityRealms.

    The Summary of Security Realms page appears.

  4. Click myrealm.

    The Settings for myrealm page appears.

  5. Click the Users and Groups tab.

  6. Click the Groups tab, click New and enter the following group properties:

    • Group name

    • Group description

    • Provider (select from the list)

  7. Create the new group, click OK.

  8. Click the Users tab, click New and enter the following user properties:

    • User name

    • User description

    • Provider (select from the dropdown list)

    • User password

  9. Create the new user, click OK.

  10. Click Release Configuration.

  11. Log in to the Enterprise Manager console.

  12. In the left section, expand WebLogic Domain and select the domain name.

  13. Right-click the domain name, select Security, and then select Application Roles.

    The Application Roles page appears.

  14. 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.

  15. Select the uimuser role and click Edit.

    The Edit Application Role: uimuser page appears.

  16. In the Members section, click Add.

    The Add Principal dialog box appears.

  17. In the Type field, select Group from the dropdown list and then click the search icon.

  18. Select the group created in steps 6 and 7, then click OK.

  19. Click OK to save and close the Edit Application Role: uimuser page.

Problem: Unable to Run SQL Script

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.

Solution

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:

  1. Open a command prompt and log in to SQL*Plus.

  2. Run 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

  3. Run the following command to change the number of processes:

    alter system set processes=2000 scope=spfile;

  4. Run 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

Problem: Timers are Not Started

If the timers are not started for any reason, you need to manually restart them.

Solution

To restart the timers:

  1. Log in to the WebLogic Server Administration Console.

  2. On the Home page, under Domain Structure, click the Deployments link.

    The Summary of Deployments page appears.

  3. Expand oracle.communications.inventory.

  4. Expand EJBs.

  5. Click the TimerBean link.

    The Settings for TimerBean page appears.

  6. Click the Control tab.

  7. Select a timer and click Activate Timers.

    This restarts the selected timer.

Problem: Deploying Enterprise Manager Error on Managed Servers

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)

Solution

Do not deploy Enterprise Manager to the managed servers in a WebLogic domain. Only deploy Enterprise Manager on the Admin Server.

Problem: Errors Observed in Managed Server Logs When Redeploying Cartridges During UIM Upgrade

When redeploying cartridges during UIM upgrade, you observe the following errors in the managed server logs:

[EL Severe]: ejb: 2017-10-20 14:00:54.023--ServerSession(810796743)--Exception [EclipseLink-22106] (Eclipse Persistence Services - 2.6.5.v20170607-b3d05bd):
org.eclipse.persistence.exceptions.RemoteCommandManagerException
Exception Description: Could not create external JMS connection with Topic UIMCacheTopic and Topic Factory UIMPomsTopicConnectionFactory. Also, check your context properties are set correctly.
Internal Exception: Exception [EclipseLink-22101] (Eclipse Persistence Services - 2.6.5.v20170607-b3d05bd): org.eclipse.persistence.exceptions.RemoteCommandManagerException
Exception Description: Could not obtain JNDI context, check your properties are set correctly.
Internal Exception: javax.naming.AuthenticationException: [Security:090938]Authentication failure: The specified user failed to log in. javax.security.auth.login.FailedLoginException: [Security:090302]Authentication 
Failed: User specified user denied [Root exception is javax.security.auth.login.FailedLoginException: [Security:090938]Authentication failure: The specified user failed to log in. 
javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User specified user denied]

Solution

Do the following:

  1. Delete the stage, tmp, and cache directories from the following location:

    Domain_Home/servers/ManagedServers

  2. Redeploy the cartridges.

Problem: Errors Observed After Domain Upgrade

After upgrading the domain, you observe the following errors:

weblogic.application.library.LibraryDeploymentException: [J2EE:160145]Failed
to deploy library Extension-Name: jax-rs, Specification-Version: 2,
Implementation-Version: 2.22.4.0, because of conflicting library Manifest
values, and library information registered with the server:
[Implementation-Version: 2.22.4.0 vs. 2.22.1.0]. Check the library
MANIFEST.MF file and correct version information there to match server
settings, or undeploy the misconfigured library.
     at
weblogic.application.internal.library.LibraryDeploymentFactory.getLibData(Libr
aryDeploymentFactory.java:129)
     at
weblogic.application.internal.library.LibraryDeploymentFactory.createDeploymen
t(LibraryDeploymentFactory.java:50)
     at
weblogic.application.internal.DeploymentManagerImpl.createDeployment(Deploymen
tManagerImpl.java:195)
     at
weblogic.application.internal.DeploymentManagerImpl.access$800(DeploymentManag
erImpl.java:61)
     at
weblogic.application.internal.DeploymentManagerImpl$DeploymentCreatorImpl.crea
teDeployment(DeploymentManagerImpl.java:628)
     Truncated. see log file for complete stacktrace

Solution

Do the following:

  1. Log in to the WebLogic Administration Server Console.

  2. In the left section, under Domain Structure, click Deployments.

    The Summary of Deployments page appears.

  3. Select the check box beside the jax-rs-2.0.war library and click Delete.

  4. Reinstall the jax-rs-2.0.war library from the following location:

    MW_Home/wlserver/common/deployable-libraries/jax-rs-2.0.war

Problem: Errors Observed During UIM Installation

When installing UIM, you observe the following errors:

Error: Unable to execute command. DB Tool utility execution failed. Internal error occured. Please check installer log files for more details.
SEVERE: Error: Unable to check user privilege in Oracle database. Privilege check failed : The DB user does not have required privileges. 
Please check whether the user has the following privileges ''CREATE USER','CREATE SESSION','GRANT ANY PRIVILEGE','GRANT ANY ROLE','SELECT ANY TABLE','SELECT ANY DICTIONARY''.
Exception signaled in a SQL operation. Please checkinstaller log files for more details.
Exception in thread "main" java.sql.SQLException: ORA-28040: No matching authentication protocol
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:388)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:381)

Solution

Do the following:

  1. Add the following properties in the ORACLE_HOME/network/admin/sqlnet.ora file: 

    SQLNET.ALLOWED_LOGON_VERSION_SERVER=8
SQLNET.ALLOWED_LOGON_VERSION_CLIENT=8

  2. Restart the database.

Problem: Error Occurred While Expanding oracle.communications.inventory in the Console

While expanding the oracle.communications.inventory deployment from a WebLogic console, you observe the IesRunTasksRemote exception.

Solution

Deploy the uim_core_lib.ear and set the Targets to both Administration and the Cluster servers.