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, "Domain Configuration Fails on SUSE11 Operating Systems"
Section 2.3, "Error Message About a Failed Copy in the Upgrade Log File Can Be Ignored"
Section 2.4, "OPATCH Failure Warning in the Install Log Can be Ignored"
Section 2.5, "Backing Up Your Database and Database Schemas"
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:
Obtain and install openmotif22-libs-2.2.4-189.1.i586.rpm.
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
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:
Locate the httpd.conf file for the destination Oracle HTTP Server.
The file is located in the following location in the destination Oracle instance:
(WINDOWS> DEST_ORACLE_INSTANCE\config\OHS\ohs1\httpd.conf
Edit the httpd.conf file with a text editor and replace all source paths with destination paths for all the directives in httpd.conf file.
For example, replace the following path:
"ServerRoot "<Source Oracle Instance>/config/OHS/ohs1"
with
"ServerRoot "<Destination Oracle Instance>/config/OHS/ohs1"
Save and close the httpd.conf file.
Edit the ssl.conf file located at <Destination Oracle Instance>/config/OHS/ohs1/ssl.conf by replacing the forward slash with the backward slash as shown in the following example:
Before workaround:
</Directory> BrowserMatch ".*MSIE.*" / nokeepalive ssl-unclean-shutdown / downgrade-1.0 force-response-1.0 </IfModule>
After workaround:
</Directory> BrowserMatch ".*MSIE.*" \ nokeepalive ssl-unclean-shutdown \ downgrade-1.0 force-response-1.0 </IfModule> </VirtualHost>
Save and close the ssl.conf file.
Restart the Oracle HTTP Server instance.
When you upgrade to Oracle Forms and Reports 11g Release 2 (11.1.2), the Upgrade Assistant generates a log file of the upgrade process. For more information, see "Locating the 11g Release 1 (11.1.1) to 11g Release 2 (11.1.2) Upgrade Log Files" in the Oracle Fusion Middleware Upgrade Guide for Forms and Reports.
In the log file, you might find an error message such as the following:
[copy] Failed to copy ... EmbeddedLDAP.lok due to The process cannot access the file because another process has locked a portion of the file
You can safely ignore this error.
On 32-Bit Linux operating systems, you might find the following types of OPATCH failure warnings in the Install log during OPATCH execution:
OUI-67200:Make failed to invoke "/usr/bin/make -f ins_rdbms.mk iextproc ORACLE_HOME=/scratch/aime1/Oracle/mwARU/Oracle_FRHome1"....'gcc: /scratch/aime1/Oracle/mwARU/Oracle_FRHome1/rdbms/lib/hormc.o: No such file or directory
make: *** [/scratch/aime1/Oracle/mwARU/Oracle_FRHome1/rdbms/lib/extproc
Error 1
OUI-67124:Re-link fails on target "iextproc".
OUI-67200:Make failed to invoke "/usr/bin/make -f ins_rdbms.mk iextproc ORACLE_HOME=/scratch/aime1/Oracle/mwARU/Oracle_FRHome1"....'gcc: /scratch/aime1/Oracle/mwARU/Oracle_FRHome1/rdbms/lib/hormc.o: No such file or directory
make: *** [/scratch/aime1/Oracle/mwARU/Oracle_FRHome1/rdbms/lib/extproc
Error 1
This is due to a failure in the Install log. You may safely ignore this warning as it does not impair any functionality.
Section 3.2.4 "Backing Up Your Database and Database Schemas" of the Oracle Fusion Middleware Patching Guide for Oracle Forms and Reports guide mentions the incorrect schema version registry table name. The correct schema version registry table name is SYSTEM.SCHEMA_VERSION_REGISTRY$.
Section 3.6 "Verifying Your Patch Set Installation" of the Oracle Fusion Middleware Patching Guide for Oracle Forms and Reports guide must include an additional (optional) verification step in order to access the Enterprise Manager Agent at the following URL:
http://host:port/emd/main