Troubleshooting OSM Installation Problems

9 Troubleshooting OSM Installation Problems

This chapter describes some of the issues you may encounter during the Oracle Communications Order and Service Management (OSM) installation process, and their solutions.

Coherence Configuration Error: ORA-00001: unique constraint

The following error can occur in the OSM WebLogic server console when creating an order:

com.mslv.oms.handler.InternalErrorException: ORA-00001: unique constraint ORDERMGMT4701.XPKOM_ORDER_FLOW_COORDINATOR) violated

This error occurs because incorrect or missing Coherence settings cause the nodes in the cluster to be unaware of each other. The servers are unaware that they must generate order IDs that take the other servers into consideration. This problem does not occur if the same server gets all of the createOrder requests. The problem occurs when any other server gets a request and uses the wrong formula to generate the order ID.

For more information about Coherence, see "Configuring Oracle Coherence for an OSM Cluster."

Error About T3 After Initial OSM Startup

The first time you start the OSM server after installation, you may see an exception indicating T3 file attachment not found.

If this occurs, restart the server.

Node Manager Does Not Create IP Address for Whole Server Migration

When you start up a managed server that is configured for whole server migration, the managed server fails to start because node manager does not create the floating IP address for the managed server.

If this occurs, ensure that you have selected Automatic Server Migration Enabled when you configured the managed server. Node manager does not allocate IP addresses to managed server unless this value is selected. See "Configure Managed Servers for Whole Server Migration" for information about setting this value.

Database Connection Problems During Installation

If you receive database connection errors when clicking Connect on the Database Server Connection Information dialog box, click Retry. This sometimes fixes the problem.

This issue is related to latency in the database connection. Acceptable network latency should be between 0.2 and 0.4 msec. Anything higher than 1 msec can substantially reduce OSM performance.

To verify network latency, do the following:

Log in to the machine running the OSM server.
Run the following command:
```
#ping -s osm_database
```
where osm_database is the host name or IP address of the machine running the OSM database server.

The system responds with lines similar to the following:
```
PING osm_database: 56 data bytes
64 bytes from osm_database: icmp_seq=0. time=0.389 ms
64 bytes from osm_database: icmp_seq=1. time=0.357 ms
```
A value for time of less than 0.4 indicates acceptable network latency. A value greater than 1.0 indicates excessive network latency.

Note:

Solaris uses the -s option. Linux and AIX do not require this option.

JMS Server Connection Problems

After installation, when you restart the server, you may receive an error message from the JMS server connecting to the database. Many retries of the operation occur.

First, check the database connectivity as the database listener or database instance might be down. As a last resort, you may have to re-create the JMS server resource (not recommended) or re-run the OSM installation.

JDBC Errors When First Order Submitted

If you receive JDBC errors when the first order is submitted to OSM, you may need to turn on JDBC logging. Refer to the Oracle WebLogic Server documentation.

No Users or Groups Are Displayed

After OSM installation, you do not see any users or groups on the Users and Groups tab in the WebLogic Server Administration Console. This is because non-dynamic changes have been made, and the WebLogic administration server (and managed server, if applicable) requires a restart.

To resolve this issue:

Restart the administration/managed server to clear the condition.

If the condition does not clear, proceed with the steps below.
Log in to the WebLogic Server Administration Console and select Domain.
Select the Security tab.
Select Advanced. If necessary, scroll down the page to find Advanced.
Select the Allow Security Management Operations if Non-dynamic Changes have been Made check box.
Click Save.
Navigate to the Users and Groups tab.

Your users and groups are displayed.

OSM and RCU Installers Are Slow to Run Database Tablespace Query

It can take an unusually long time for the OSM Installer and RCU Installer to run a database tablespace query. Purging the Oracle Database recycle bin ensures that the installers can run the database tablespace query more quickly.

To purge the Oracle Database recycle bin system wide:

Log in to SQL*Plus as a user with sysdba privileges.
Enter the following command:
```
purge dba_recyclebin;
```
The recycle bin is purged system wide.

To purge the Oracle Database recycle bin for a single user:

Log in to SQL*Plus as the OSM installer database user.
Enter the following command:
```
purge recyclebin;
```
The recycle bin for the database user is purged.

OSM Installer Issues for UNIX or Linux

If you are re-using the installation directory or the operating system temporary directory, you might have a problem running the installer on a UNIX or Linux system. To resolve this, you must start two sessions: a session for WebLogic Server, and separate a session for running OSM Installer.

To start a UNIX or Linux session for WebLogic Server:

Ensure the OSM WebLogic Server has the following Java Virtual Machine (JVM) setting:

-Djava.io.tmpdir=./tmp

Note:

If OSM WebLogic Server is installed in a cluster environment, create a tmp_servername directory in the WebLogic Server domain directory, and use the following setting for each server in the cluster:

-Djava.io.tmpdir=./tmp_servername

where servername is the name of each server in the cluster. For example, to install OSM on oms_cluster, which consists of oms_server1 and oms_server2, start oms_server1 by using -Djava.io.tmpdir=./tmp_oms_server1, and start oms_server2 by using -Djava.io.tmpdir=./tmp_oms_server2.

To start a UNIX or Linux session for running OSM Installer:

Create a new directory, and then create a temporary directory within that new directory. For example:

/home/osm_user/new_osm_install

/home/osm_user/new_osm_install/tmp
Download the OSM software media pack for your operating system from the Oracle software delivery website, located at:

https://edelivery.oracle.com/

and save it to the directory that you created. For example, /home/osm_user/new_osm_install.
Ensure that the Oracle Database and Oracle WebLogic Server instances that you intend to use for OSM are running.
Follow step 7 of the procedure to install OSM, located in the "Installing OSM" topic.
In the temporary directory that contains the installation executable file, for example, /home/osm_user/new_osm_install, run the OSM Installer by doing one of the following:
- On Oracle Linux and Red Hat Enterprise Linux, run the following command:
```
InstallLinux.bin -is:tempdir ./tmp
```
- On Oracle Solaris, run the following command:
```
InstallSparc.bin -is:tempdir ./tmp
```
- On IBM AIX, run the following command:
```
InstallAix.bin -is:tempdir ./tmp
```
- On Windows, navigate to the directory containing the installation executable files and double-click Install.exe.
Continue with step 10 of the procedure to install OSM, located in the "Installing OSM" topic.

Command for unpack.jar Fails with a Write Error

If you run the unpack.jar command and you receive a write error, you must provide a target application tag (-app_dir) while running the command.

For example:

./unpack.sh -template=/scratch/oracle/Middleware/user_projects/domains/osmprak_72251to730_upgddomain_final8may.jar -domain=/scratch/oracle/Middleware/user_projects/domains/osmprak_72251to730_upgddomain -app_dir=/scratch/oracle/Middleware/user_projects/applications/osmprak_72251to730_upgddomain

Managed Servers are Unable to form Coherence Cluster

After restarting the managed servers upon successful installation of OSM, you may see the following warning in the managed server log file:

<Warning> <com.oracle.coherence> <BEA-000000> <2021-03-22 04:28:03.513/133.795 Oracle Coherence GE 192.0.2.1 
<Warning> (thread=Cluster, member=n/a): Delaying formation of a new cluster; 
TcpRing failed to connect to senior Member(Id=1, Timestamp=2021-03-22 04:24:17.89, Address=192.0.2.1:7777, MachineId=43781, 
Location=site:location.compute.example.com,machine:192.0.2.1,process:9670,member:M1, Role=c1); 
if this persists, it is likely the result of a local or remote firewall rule blocking connections to TCP-ring port 7777>

This issue occurs because the required ports are not enabled in the firewall. As a result, OSM managed servers cannot form a Coherence cluster and the load distribution may not happen properly.

Note:

This issue occurs mostly in private cloud environments.

To resolve the issue, enable the following ports in the firewall:

7
17991, 17992, and 17993
In the setDomainEnv.sh file, enable these ports in JAVA_OPTIONS for all the machines as shown below:
```
export JAVA_OPTIONS="${JAVA_OPTIONS} -Dcoherence.localport=17991 -Dcoherence.localport.adjust=17993
```

Coherence uses these ports for forming the cluster.

For more details, see the "What Are All The Ports Needed To Be Opened For Coherence?" knowledge article (Doc ID: 1472388.1) on My Oracle Support.