2 Installation, Configuration, and Upgrade

This chapter describes known issues and workarounds when installing or upgrading Oracle Forms and Reports 11g Release 2 (11.1.2).

This chapter contains the following sections:

• Section 2.1, "Oracle HTTP Server Returns 503 Apache Bridge Failure Error While Toggling Between Forms and Reports"

• Section 2.2, "Domain Configuration Fails on SUSE11 Operating Systems"

• Section 2.3, "Oracle Access Manager (OAM) Requires Fully Qualified Domain Name"

• Section 2.4, "Oracle HTTP Server Port Conflicts After Upgrade from Oracle Fusion Middleware 11g Release 1 (11.1.1)"

2.1 Oracle HTTP Server Returns 503 Apache Bridge Failure Error While Toggling Between Forms and Reports

While toggling between Oracle Forms and Oracle Reports applications through Oracle HTTP Server, you may see the "503 Apache Bridge failure" error. This is due to the wrong patch 12632886 being shipped with the Oracle Forms and Reports installer.

To work around this problem:

1. Download the new OPatch 12632886 (OHS-WLS COMMUNICATION NOT WORKING ON IPV6 ENABLED SOLARIS M/C [Patch ID 14069292]) for your Windows Platform from My Oracle Support:

   https://support.oracle.com/ 
   

2. Shut down all servers running from your Oracle home:

   opmnctl stopall
   

3. Go to the directory where patch 12632886 is located:

   cd path_to_patch\12632886
   

4. Run OPatch to deinstall the improper patch:

   opatch rollback -id 12632886 
   

5. Re-apply patch 12632886:

   opatch apply
   

2.2 Domain Configuration Fails on SUSE11 Operating Systems

On 32-Bit and 64-Bit SUSE11 operating systems, domain creation may fail at:

opmnctl startproc ias-component=RptSvr_nsh2110213_asinst_1

with the following error:

ORACLE_HOME/bin/rwserver: error while loading shared libraries: libXm.so.3:
cannot open shared object file: No such file or directory.

To work around this issue:

1. Obtain and install openmotif22-libs-2.2.4-189.1.i586.rpm.

2. Create the following soft links in the /usr/lib64 directory:

   • libXm.so -> libXm.so.4.0.3

   • libXm.so.3 -> libXm.so.4.0.3

   • libXm.so.4 -> libXm.so.4.0.3

2.3 Oracle Access Manager (OAM) Requires Fully Qualified Domain Name

Depending on your system configuration, your Oracle Forms and Reports configuration may fail at the OAM Registration step. The following error can be see in the installAction.out file:

INFO: URL is invalid : http://examplehost:8888
Sep 20, 2011 1:06:29 PM oracle.security.am.engines.rreg.client.RegClient main
SEVERE: Exception encountered: RemoteAgentRegistrationException. Specific exception:agentBaseURL is
invalid.oracle.security.am.engines.rreg.common.RemoteAgentRegistrationException: agentBaseURL is invalid.
agentBaseURL is invalid : http://examplehost:8888
The remote registration process did not succeed! Please find the specific error message below.
agentBaseURL is invalid.
Exit Status: 1
OAM Registration failed.

To work around this issue:

1. Exit the configuration tool or Oracle Forms and Reports Installer.

2. Edit the hosts file on your system and modify it to include the fully qualified host name and IP address of your system.

3. Restart the Oracle Forms and Reports configuration tool.

2.4 Oracle HTTP Server Port Conflicts After Upgrade from Oracle Fusion Middleware 11g Release 1 (11.1.1)

When you upgrade from Oracle Fusion Middleware 11g Release 1 (11.1.1), you can choose to modify your new 11g Release 2 (11.1.2) installation to use the same ports as your 11g Release 1 (11.1.1) installation.

Alternatively, you can continue use the ports defined during the 11g Release 2 (11.1.2) installation.

In the latter case, you can run both the 11g Release 1 (11.1.1) environment and the newly upgraded 11g Release 2 (11.1.2) instance at the same time with no port conflicts.

However, in some cases, after upgrading to Oracle Forms and Reports 11g Release 2 (11.1.2), you might experience port conflicts when attempting to start the Oracle HTTP Server in both the 11g Release 1 (11.1.1) and 11g Release 2 (11.1.2) instances. This is because not all the paths in the Oracle HTTP Server configuration files were upgraded successfully.

This issue occurs if the paths to the admin.conf and ssl.conf files in the httpd.conf file are hard-coded, rather than defined using system variables. As a result, they continue to reference the configuration files in the 11g Release 1 (11.1.1) source Oracle instance, rather than the files in the 11g Release 2 (11.1.2) destination Oracle instance.

To work around this issue, perform the following task in the destination Oracle instance:

1. Locate the httpd.conf file for the destination Oracle HTTP Server.

   The file is located in the following location in the destination Oracle instance:

   (UNIX) DEST_ORACLE_INSTANCE/config/OHS/ohs1/httpd.conf
   (WINDOWS> DEST_ORACLE_INSTANCE\config\OHS\ohs1\httpd.conf
   

2. Edit the httpd.conf file with a text editor and locate the include directives for the admin.conf and ssl.conf files.

   For example:

   (Windows) C:\Oracle\Middleware\mw_home\asinst_1/config/OHS/ohs1/admin.conf
   (UNIX) /disku01/Oracle/Middleware/mh_home/config/OHS/ohs1/admin.conf
   

3. Modify the directives so they reference the admin.conf and ssl.conf files in the destination Oracle instance, rather than the source Oracle instance.

4. Save and close the httpd.conf file.

5. Restart the Oracle HTTP Server instance.