4 Troubleshooting

This chapter describes typical installation and configuration problems and their solution. It contains the following sections:

• "Port Conflicts"

• "Loss of Network Connection During Installation"

• "Garbage Collection Performance Issues"

• "Cleanly Uninstalling OCMS and Correcting Problems from Manually Uninstalling OCMS"

Port Conflicts

As described in "Port Requirements" in the Product and Installation Overview chapter of this guide, OCMS requires the use of specific ports for SIP, Presence, and Edge Proxy communications.

The InstallShield for OCMS performs a check of the SIP port during installation to make sure it is not being used by another application.

If any other ports required for OCMS are already being used by another application, the OCMS installation fails, and the port conflicts are logged in the ocmsinstall.log file as "Address in Use." Examine the ocmsinstall.log file to determine the port conflicts. Reconfigure the ports used by your existing applications.

Loss of Network Connection During Installation

During the OCMS installation, an active network connection is required.

In the uncommon event that a network connection is lost during installation, the installation can fail. Examine the ocmsinstall.log file to see a log of this event.

Garbage Collection Performance Issues

Using the default Java Virtual Machine (JVM) settings provided in the OCMS installation can create garbage collection performance issues for some large installations. If you experience these issues, evaluate and configure the following parameters:

• Set the PermSize of the Oracle TimesTen database according to how many users you want to support. 720,000 users require about 768MB of PermSize. OCMS is installed with a default value of 256 MB.

• Set the heap size and other parameters accordingly. With an Oracle TimesTen PermSize setting of 768 MB, change the JVM startup parameters in $ORACLE_HOME/opmn/conf/opmn.xml to include the following:

  -XX:PermSize=128m -XX:MaxPermSize=128m -Xss128k -Xmx1280M -Xms1280M

• To run the OCMS SIP Servlet Container without Oracle TimesTen In-Memory Database, set the JVM startup parameters in $ORACLE_HOME/opmn/conf/opmn.xml to include the following:

  -XX:PermSize=128m -XX:MaxPermSize=128m -Xss128k -Xmx1536M -Xms1536M

Cleanly Uninstalling OCMS and Correcting Problems from Manually Uninstalling OCMS

You should always use the uninstaller to cleanly uninstall an OCMS installation since manually deleting OCMS can result in problems if OCMS is to be installed again.

Cleaning Uninstalling OCMS

In Windows XP you can uninstall OCMS by running uninstaller.exe located in the \_uninst folder in the OCMS installation directory. In Linux you can uninstall OCMS by running uninstaller.bin located in the \_uninst folder in the OCMS installation directory.

In standalone developer mode, complete the uninstallation by deleting the entire installation home directory, if it exists. For an Oracle Application Server installation, also delete the ocms and sdp directories from the installation home directory.

When uninstalling OCMS, the ocmsinstall.log file records error messages when applications are removed (whether they are installed or not). For example:

############ UNDEPLOY - AGGREGATIONPROXY ############C:\as10132_ocms\jdk\bin\java -jar (!ERROR unexpected EOF!) Undeploy error: Undeploy failed: Unable to undeploy: Application aggregationproxyear does not exist!

Correcting Problems from Manually Uninstalling OCMS

If you have manually deleted folders or files and receive an error message indicating that OCMS cannot be installed because it is already installed, perform the following procedure to clean the machine:

1. Locate the following directory:

   • For Windows XP operating systems, navigate to the <COMMONFILES>\InstallShield\Universal\common\Gen1\_vpddb directory. Typically <COMMONFILES> is located at C:\Program Files\Common Files.

     For Linux operating systems, navigate to the <USERHOME>/Installshield/Universal/common/Gen1/_vpddb directory. Typically the <USERHOME> location is located at /home/<username>.

2. Open the vpd.script file and search for "SIP Container."

3. Delete all "INSERT INTO INSTALL_SOFTWARE_OBJECT" lines related to your previous installation of OCMS from the vpd.script file.

4. Delete all persisted variables from the vpd.script file. Search for "INSERT INTO PERSISTED_VARIABLES_TABLE" and "LOCAL_PERSISTED_VARIABLES".