3 Installation Issues

3.1.1 Response Files Created through the Record Mode Are Not Supported

If you want to run the installer with a response file (to perform a silent or non-interactive installation), you cannot use response files created through the -record command-line option in the installer, as described in the "Creating Response Files by Using the Record Mode in the Installer" section in the Oracle Application Server Installation Guide. Instead, you must use response files that were created from the provided response file templates; you replace the placeholder values in the template files with your own values.

3.1.2 IPv6 Not Supported

This release of Oracle Application Server is not certified to run on machines that are configured with IPv6. You have to install and run this release of Oracle Application Server on machines that are configured with IPv4.

3.1.3 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:

If your host contains an Oracle Application Server 10g (9.0.4) installation, you may have installed gcc-2.95 or gcc-2.96 on your system, as outlined in Oracle Application Server Quick Installation and Upgrade Guide 10g (9.0.4) for Linux x86. The procedure involved creating symbolic links for /usr/bin/gcc and /usr/bin/cc to the appropriate version of the executables.

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
   

3.1.4 Installation Failure for Turkish Locale

All installation types fail with the Turkish locale:

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.

3.1.5 Set db_create_file_dest Before Installing Against a File System Database

If you are installing against a file system-based database, you must set the db_create_file_dest parameter to the location of the DB data files before starting the installation. For example:

SQL> ALTER SYSTEM SET db_create_file_dest='C:\oradata' SCOPE=BOTH

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

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

If you are installing against a raw database, this parameter must be null.

Note that the cdb_alter_system.sql script does not set this parameter. You must set it manually.

3.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.