6 Troubleshooting Offline Mediation Controller

Learn how to troubleshoot problems in Oracle Communications Offline Mediation Controller.

Topics in this document:

Troubleshooting Checklist

When any problems occur, it is best to do some troubleshooting before you contact Oracle Support:

  • You know your installation better than Oracle Support does. You know if anything in the system has been changed, so you are more likely to know where to look first.

  • Troubleshooting skills are important. Relying on Oracle Support to research and solve all of your problems prevents you from being in full control of your system.

If you have a problem with your Offline Mediation Controller system, ask yourself these questions first, because Oracle Support will ask them of you:

  • What exactly is the problem? Can you isolate it?

    Oracle Support needs a clear and concise description of the problem, including when it began to occur.

  • What do the log files say?

    This is the first thing that Oracle Support asks for. Check the error log for the Offline Mediation Controller component you are having problems with.

  • Has anything changed in the system? Did you install any new hardware or new software? Did the network change in any way? Does the problem resemble another one you had previously? Has your system usage recently jumped significantly?

  • Is the system otherwise operating normally? Has response time or the level of system resources changed? Are users complaining about additional or different problems?

Using Error Logs to Troubleshoot Offline Mediation Controller

Offline Mediation Controller error log files provide detailed information about system problems. If you are having a problem with Offline Mediation Controller, look in the log files.

Offline Mediation Controller logs specific details about actions performed in the Offline Mediation Controller GUI in Administration Server log files.

Getting Help for Offline Mediation Controller Problems

If you cannot resolve the Offline Mediation Controller problem, contact Oracle Support.

Before you contact Oracle Support, try to resolve the problem with the information logged in the log files. If this does not help to resolve the problem, note the following 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 after which the problem occurred, even if you do not think they are relevant.

  • List of all Offline Mediation Controller components and patches installed on your system.

When you are ready, report the problem to Oracle Support.

Common Problems and Their Solutions

Although Offline Mediation Controller is designed to be trouble free, you might encounter a problem. You can view descriptions of some common problems along with their solutions:

Problem: ps: illegal option

When you start Node Manager or the Administrative Server, you receive a "ps: illegal option" error message.

Possible Cause

The ps script from the ucb package is used. You must use the ps script in the /usr/bin or /bin directory.

Solution

In the PATH environment variable, make sure that /usr/bin and /bin appear before /usr/ucb.

Problem: keytool error: java.io.FileNotFoundException While Creating Administration Server Certificate

After installing only Administration Server, when you run the createAdminSvrCert script to create the Administration Server certificate, you receive the "keytool error: java.io.FileNotFoundException: OMC_home/config/GUI/adminClientTruststore.jks (No such file or directory)" error message, where OMC_home is the directory in which Offline Mediation Controller is installed.

Possible Cause

The OMC_home/config/GUI/adminClientTruststore.jks file does not exist.

Solution

You must manually import the Administration Server's public certificate into the Administration Client's TrustStore.

To manually import the Administration Server's public certificate into the Administration Client's TrustStore:

  1. Log on to the system on which Offline Mediation Controller is installed.

  2. Run the following command:

    OMC_home/jre/bin/keytool -import -v -trustcacerts -alias adminServer -file OMC_home/config/adminserver/adminServer.cer -keystore OMC_home/config/GUI/adminClientTruststore.jks

    The Enter keystore password prompt appears.

  3. Enter the Administration Client's TrustStore password.

    The Trust this certificate prompt appears.

  4. Enter y, which trusts the certificate.

    The Administration Server's public certificate is imported into the Administration Server's TrustStore.

Problem: keytool error: java.io.FileNotFoundException While Creating Node Manager Certificate

After installing only Node Manager, when you run the createNodeMgrCert script to create the Node Manager certificate, you receive the "keytool error: java.io.FileNotFoundException: OMC_home/config/adminserver/adminServerTuststore.jks (No such file or directory)" error message.

Possible Cause

The OMC_home/config/adminserver/adminServerTuststore.jks file does not exist.

Solution

You must manually import the Node Manager's public certificate into the Administration Server's TrustStore.

To manually import the Node Manager's public certificate into the Administration Server's TrustStore:

  1. Log on to the system on which Offline Mediation Controller is installed.

  2. Run the following command:

    OMC_home/jre/bin/keytool -import -v -trustcacerts -alias nodeManager -file OMC_home/config/nodemgr/nodeManager.cer -keystore OMC_home/config/adminserver/adminServerTuststore.jks

    The Enter KeyStore password prompt appears.

  3. Enter the Administration Server's KeyStore (TrustStore) password.

    The Trust this certificate prompt appears.

  4. Enter y, which trusts the certificate.

    The Node Manager's public certificate is imported into the Administration Server's TrustStore.

Problem: com.maverick.ssh.SshException When FTP is Used in Collection or Distribution Cartridge Pack

When File Transfer Protocol (FTP) is used in the Collection or Distribution cartridge pack, you receive the "com.maverick.ssh.SshException" error.

Possible Cause

All of the required security providers are not included in the Java security files.

Solution

Manually copy the following JAR files into the Java_home/jre/lib/ext directory (where Java_home is the directory in which the supported version of Java is installed) and then restart the system:

  • bcprov-ext-jdk15on-158.jar

  • bcprov-jdk15on-158.jar

To restart the system, see "Starting and Stopping Offline Mediation Controller".

Problem: Error While Starting Node Manager with SSL Enabled

When you start Node Manager with Secure Sockets Layer (SSL) enabled, you receive the following error:

Cannot support TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 with currently installed providers

Possible Cause

All of the required security providers are not included in the Java security files.

Solution

Manually copy the JARs from the jce_policy-8.zip file into the Java_home/jre/lib directory and then restart the system. You can download this file from Oracle Technology Network:

https://www.oracle.com/java/technologies/javase-jce8-downloads.html

To restart the system, see "Starting and Stopping Offline Mediation Controller".

Problem: CDRs Going to Delayed or No-Response Directories in ECE DC Node While Processing Large Number of Records

When processing a large volume of call detail records (CDRs) in Offline Mediation Controller, many CDRs are routed to the delayed response and no response directories in the ECE DC node after aggregation.

Possible Cause

Excessive I/O operations from debug logging, insufficient JVM memory for high-volume processing, and a too-short response timeout in the ECE DC node, which together can combine to delayed or non-responsive CDR handling.

Solution