2 Installation Issues

2.1.1 Port Conflict When Oracle WebCenter Framework and Oracle Content DB are Installed on the Same Machine

If Oracle WebCenter Framework and Oracle Content DB are installed on the same machine, you may see a message in opmn.log that is similar to the following:

06/06/07 06:22:52 [ons-connect] Passive connection 127.0.0.1,6100 missing connect

To check whether these links exist:

ls -l /usr/bin/gcc /usr/bin/cc

Check if the gcc and cc commands are symbolic links, for example:

gcc -> /opt/gcc295/bin/gcc
cc -> /opt/gcc295/bin/gcc

This is due to a port conflict. To correct this problem, perform the following steps:

1. Open the DB_ORACLE_HOME/opmn/conf/ons.config file for editing.

2. Set the localport to a port other than 6100. For example:

   localport=7100
   
   

3. Restart the database listener:

   DB_ORACLE_HOME/bin/lsnrctl stop
   DB_ORACLE_HOME/bin/lsnrctl start
   
   

4. Restart the Oracle WebCenter Framework instance:

   opmnctl stopall
   opmnctl startall
   
   

2.1.2 Installation Failure for Turkish Locale

The following installation types will fail with the Turkish locale:

• Basic Installation

• Advanced Installation: Oracle WebCenter Framework with Oracle HTTP Server

• Advanced Installation: Oracle WebCenter Framework

This is because Oracle WebCenter Framework Configuration Assistant fails with the following errors:

ERROR:  'Instruction unknown: load?nstruction'
FATAL ERROR:  'Could not compile stylesheet

For all installation types, the component toolbox on the Configuration Assistants page of Oracle Universal Installer is not displayed properly for the Turkish locale.

Oracle recommends that you avoid running the Oracle Universal Installer to install Oracle Application Server using the Turkish locale.

2.1.3 Exception After Installing Oracle HTTP Server

After perfoming Oracle HTTP Server installation, the following exception is displayed in the oraInstallyyyy-mm-dd_hh-mm-ssAM/PM.err file:

java.io.FileNotFoundException: 
/home/10132/ccd/RC2B/wsJP2/jre/1.4.2/javaws/cacerts (no such file or 
directory) 
at java.io.FileOutputStream.open(Native Method) 
at java.io.FileOutputStream.<init>(FileOutputStream.java:179) 
at java.io.FileOutputStream.<init>(FileOutputStream.java:70) 
at 
oracle.sysman.oii.oiij.OiijFastJarExtracter.copyFileFromJar(OiijFastJarExtract 
er.java:215) 
at 
oracle.sysman.oii.oiij.OiijFastJarExtracter.copyJarContents(OiijFastJarExtract 
er.java:170) 
at 
oracle.sysman.oii.oiij.OiijFastJarExtracter.extract(OiijFastJarExtracter.java: 
123) 
at 
oracle.sysman.oii.oiij.OiijJarExtractQueue$OiijJarExtractWorker.run(OiijJarExt 
ractQueue.java:338)

However, this exception message is benign and can be safely ignored.

2.1.4 Java Virtual Machine Parameters for Installation

After installing Oracle Application Server, and then, Oracle Communication and Mobility Server, you must perform the following tasks:

• Upgrade Java Development Kit (JDK) to version 1.5.0_05. For more information on upgrading JDK, refer to 396096.1 note available on OracleMetaLink at:

  https://metalink.oracle.com

• Edit the following Java Virtual Machine (JVM) parameters in the $ORACLE_HOME/opmn/conf/opmn.xml file:

  -Xss128k -Xms1280m -Xmx1280m -Xmn16m
  -XX:SurvivorRatio=16 -XX:CICompilerCount=1 -Xoptgc -XX:+ForceMmapReserved
  -XX:-UseHighResolutionTimer -XX:SchedulerPriorityRange=SCHED_NOAGE
  -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.DevPollSelectorProvider
  -XX:-ExtraPollBeforeRead
  -XX:+UseTLAB -XX:TLABSize=32k -XX:-UseFastAccessorMethods
  -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=80
  -XX:+UseParNewGC -XX:PermSize=128m -XX:MaxPermSize=128m
  
  

  The JVM parameters are used to activate the Oracle Communication and Mobility Server instance.

  Note:

  To perform standalone installation of Oracle Communication and Mobility Server, you need to run these parameters in the command-line interface along with the startup command.

2.2.1 Length Restrictions on Content Database Schema Password is Incorrect in the Oracle Universal Installer Online Help

The following topic in the Application Server Control online help incorrectly states the valid length of the Content Database schema password when installing Oracle Application Server 10g Release 3 (10.1.3.2):

• "Specify Content Database Schema Password"

The length of the Content Database schema password must be between 5 and 30 characters long.