This chapter provides guidelines to help you troubleshoot problems with Oracle Communications Offline Mediation Controller.
When any problems occur, it is best to do some troubleshooting before you contact Oracle Global Support:
You know your installation better than Oracle Global 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 Global 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 Global Support will ask them of you:
What exactly is the problem? Can you isolate it?
Oracle Global 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 Global 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?
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.
If you cannot resolve the Offline Mediation Controller problem, contact Oracle Global Support.
Before you contact Oracle Global 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 Global Support.
This section describes common problems found when running Offline Mediation Controller and their solutions.
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.
After installing only Administration Server, when you run the createAdminSvrCert script to create 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 does not exist.
Solution
You must manually import Administration Server's public certificate into Administration Client's truststore.
To manually import Administration Server's public certificate into Administration Client's truststore:
Log on to the system on which the Offline Mediation Controller is installed.
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.
Enter Administration Client's truststore password.
The Trust this certificate prompt appears.
Enter y, which trusts the certificate.
Administration Server's public certificate is imported to Administration Server's truststore.
After installing only Node Manager, when you run the createNodeMgrCert script to create Node Manager certificate, you receive the "keytool error: java.io.FileNotFoundException: OMC_home/config/adminserver/adminServerTuststore.jks (No such file or directory) " error.
Possible Cause
The OMC_home/config/adminserver/adminServerTuststore.jks does not exist.
Solution
You must manually import Node Manager's public certificate into Administration Server's truststore.
To manually import Node Manager's public certificate into Administration Server's truststore:
Log on to the system on which the Offline Mediation Controller is installed.
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.
Enter Administration Server's keystore (truststore) password.
The Trust this certificate prompt appears.
Enter y, which trusts the certificate.
Node Manager's public certificate is imported to Administration Server's truststore.