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, "Problems Using Oracle Database 12.2 with This Release"
Section 2.2, "Secure Access Control Configuration Requires Short Hostname"
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, "High Availability Documentation for Oracle Forms and Reports 11g Release 2 (11.1.2.2)"
When you use Oracle Database 12.2.*, you may run into the following issues:
When you create an MDS database schema using RCU or upgrade the MDS database schema using Patch Set Assistant against Oracle Database 12.2, the operation may fail.
You may receive the error ORA-28104: input value for statement_types is not valid. This is because, as part of a security fix beginning with Oracle Database 12.2, for the DBMS_RLS.ADD_POLICY procedure, statement types of INSERT and UPDATE_CHECK with a value of FALSE (the default value) are no longer allowed. It results in an ORA-28104 error while registering Virtual Private Database policies.
This error is returned to avoid giving the impression that Virtual Private Database policy are enforced for INSERT statements, which is not the case.
To workaround this, configure the system with "_allow_inserts_with_UPDATE_CHECK" set to True, by executing the following SQL command:
ALTER SYSTEM SET "_allow_insert_with_update_check"=TRUE scope=spfile
Then, restart the database and re-run RCU or the Patch Set Assistant to create or upgrade the MDS database schema.
When you use Oracle Fusion Middleware with Oracle Database 12.2.*, you may encounter the following error:
ORA-00932: inconsistent datatypes: expected SYS.AQ$_JMS_MESSAGE gotSYS.AQ$_JMS_MESSAGE
The error occurs because during enqueue and dequeue of AQ$_JMS_MESSAGE type, the version number sent to the database server maybe inconsistent. This happens when TOID (the type's unique identifier) for AQ$_JMS_MESSAGE type in type$ is a user-defined TOID and not a fixed SYSTEM defined TOID.
To workaround this error, install the following patch, which replaces the ojdbc6.jar file used by Oracle Fusion Middleware:
https://updates.oracle.com/download/21663638.html
For Oracle Fusion Middleware 11g, select Release 11.1.1.7 .0.
When you install Oracle Fusion Middleware Release 11gR1 or Release 11gR2 products with Oracle Database 12.2.0.1, you may run into following error:
ORA-28040: No matching authentication protocol
This occurs because there is no 11g verifier for the proxy user.
Use the following workaround to create the 11g Verifier and allow the connection to the 12.2.0.1 Oracle Database from the Oracle Fusion Middleware installation to proceed:
Set ORACLE_HOME to the Oracle Database 12.2.0.1 Oracle home.
Add the following line to the sqlnet.ora file (in ORACLE_HOME/network/admin):
SQLNET.ALLOWED_LOGON_VERSION=11
Connect to the database as sys as sysdba user and execute the following SQL commands:
ALTER SYSTEM set sec_case_sensitive_logon=FALSE scope=spfile; shutdown immediate; startup; alter user sys identified by sys_password; alter user system identified by sys_password;
If you want to use latest DB security features, you should not set SQLNET.ALLOWED_LOGON_VERSION=11. To workaround this, patch RCU with the DBCPUjul2015 patch:
Download the patch from the following location. It is in the form of a zip file. Unzip it.
Because the patch is based on Oracle Database 11.1.0.7 release, apply it on a 11.1.0.7.0 Oracle Database. In the directory in which you unzipped the patch, enter the following commands:
setenv ORACLE_HOME oracle home of 11.1.0.7.0 db
setenv PATH $ORACLE_HOME/OPatch:$PATH
setenv PATH /usr/ccs/bin:$PATH
Execute following command to apply the patch from the patch unzipped directory:
opatch napply -skip_subset -skip_duplicate
After the patch is applied, copy the following files to the RCU_Home to the specified directories:
| File to Copy from Patched Database | Copy to This Location |
|---|---|
| ORACLE_HOME/jdbc/lib/ojdbc*.jar | RCU_HOME/jdbc/lib/ojdbc*.jar |
| ORACLE_HOME/lib/libclntsh.so.11.1 | Copy to this location, renaming the file:
RCU_HOME/lib/libclntsh.so.11.1 RCU_HOME/lib/libclntsh.so.10.1 RCU_HOME/lib/libclntsh.so |
| ORACLE_HOME/sqlplus/lib/* | Replace RCU_HOME/sqlplus/lib/* |
Now RCU is patched with the security patch and can be used to install Oracle Fusion Middleware schemas.
During Forms and Reports configuration, if you choose to configure Access Control in secure mode by selecting Configure the OAM in secure mode on the Access Control screen, you must specify the short hostname (no domain information) in the "Hostname" field.
For example, myexamplehost would be acceptable, but myexamplehost.exampledomain.com would result in an error message.
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 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
OUI-67200:Make failed to invoke "/usr/bin/make -f ins_rdbms.mk iextproc ORACLE_HOME=/home/Oracle/mwARU/Oracle_FRHome1"....'gcc: /home/Oracle/mwARU/Oracle_FRHome1/rdbms/lib/hormc.o: No such file or directory make: *** [/home/Oracle/mwARU/Oracle_FRHome1/rdbms/lib/extproc Error 1
OUI-67124
OUI-67124:Re-link fails on target "iextproc".
This is due to a failure in the Install log. You may safely ignore this warning as it does not impair any functionality.
In a Release 2, 11.1.2 Oracle Fusion Middleware environment, refer to the Oracle Fusion Middleware High Availability Guide, 11g Release 1 (11.1.1) for high availability information on Oracle Forms and Reports.
See the following topics:
"Transforming Oracle Portal, Forms, Reports, and Discoverer"
"Configuring High Availability for Oracle Portal, Forms, Reports, and Discoverer"
"Oracle Portal, Forms, Reports, and Discoverer Workbook"
See the following topics in "Considerations for High Availability Oracle Database Access":
"Oracle Forms"
"Oracle Reports and Oracle Discoverer"
In Oracle Forms and Reports 11.1.2.2, the JDK located in Oracle Home can be updated to Java 7. The default installation includes Java 6. To update to JDK 7 or an updated Java 6, perform the following tasks:
Stop all processes associated with the installation.
Back up your existing JDK. The default location is ORACLE_HOME\jdk).
Install the new JDK in the same location as your existing JDK.
Restart all processes.
For more information, see Note 1492980.1 on My Oracle Support.