This chapter describes issues associated with Oracle Fusion Middleware administration. It includes the following topics:
This section describes configuration issues and their workarounds. It includes the following topics:
Section 3.1.1, "Problems Using Oracle Database 12.2 with This Release"
Section 3.1.2, "Limitations in Moving from Test to Production"
Section 3.1.3, "MDS purgeMetadata Command Can Take a Long Time"
Section 3.1.4, "SSL Certificate Chain Required on Certain Browsers"
When you use Oracle Database 12.2. or higher, you may run into the following issues:
When you create a Metadata Services (MDS) database schema using Repository Creation Utility (RCU) or upgrade the MDS database schema using Upgrade 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. The security fix 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 policies are enforced for INSERT statements, which is not the case.
To work around this error, 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 Upgrade Assistant to create or upgrade the MDS database schema.
When you use Oracle Fusion Middleware with Oracle Database 12.2 or higher, 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 may be 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 work around 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 12.1.3, select Release 12.1.0.2.0.
Note the following limitations in moving from test to production:
On Windows, with Oracle Data Integrator in your source environment, before you run the pasteConfig script, you must set HOSTNAME as a system variable
If you are using Oracle Data Integrator on Windows, after you run the pasteConfig script, update the config.properties file with the following:
odi.shared.config.dir.path=%DOMAIN_HOME%/config/oracledi
When you are moving Oracle Platform Security Services and the data is moving from LDAP to LDAP, the source and target LDAP domain component hierarchy must be same. If it is not, the Oracle Platform Security Services data movement will fail. For example, if the source is hierarchy is configured as dc=us,dc=com, the target LDAP must have the same domain component hierarchy.
On Windows, Node Manager and any configured system components must be shut down before you run the copyConfig script.
The movement scripts do not support environments where multitenancy is enabled.
On Windows, the pasteConfig operation fails if the SSL-only mode is enabled in configurations that include both WebCenter Content and Capture. This is not an issue on Linux.
To work around this issue, before executing the movement scripts, enable non-SSL ports in addition to SSL ports. Then, run the copyBinary, paste Binary, copyConfig and pasteConfig scripts. After the scripts complete successfully, disable non-SSL ports on the target environment so that you have an SSL-only environment.
When you execute pasteConfig and the archive contains Oracle Platform Security Services, the script may return the following errors:
oracle.security.audit.util.StrictValidationEventHandler handleEvent
WARNING: Failed to validate the xml content. Reason: cvc-complex-type.2.4.b:
The content of element '' is not complete. One of
'{"http://xmlns.oracle.com/ias/audit/audit-2.0.xsd":source}' is expected..
Apr 24, 2013 6:28:29 AM
oracle.security.audit.util.StrictValidationEventHandler handleEvent
WARNING: Failed to validate the xml content. Reason: cvc-complex-type.2.4.b:
The content of element '' is not complete. One of
'{"http://xmlns.oracle.com/ias/audit/audit-2.0.xsd":source}' is expected..
You can ignore these errors.
When your environment includes Oracle Business Activity Monitoring, the bamcommand.log.0 log file may contain the following benign error message after you execute the pasteConfig script:
oracle.beam.impexp.commandline.util.ImportExportClient.main: Exception occurred in method Import/Export(-dbusername,DEFAULT,-dburl,DEFAULT,-dbdriver,DEFAULT,-cmd,import, -file,/scratch/aime/t2pprodsoa/soa/bam/bin/BAMT2PEMSArtifacts.zip,-mode,append) Exception: java.io.FileNotFoundException: /scratch/oracle/t2pprodsoa/soa/bam/bin/BAMT2PEMSArtifacts.zip (No such file or directory)
You can ignore this message.
When your environment includes Oracle Business Activity Monitoring, the log file may contain the following benign error message after you execute the copyConfig or pasteConfig scripts:
<Apr 29, 2014 1:04:39 AM MDT> <Warning> <JNDI> <BEA-050001> <WLContext.close() was called in a different thread than the one in which it was created.>
You can ignore this message.
When you move any environment which contains a Web Tier component, such as Oracle HTTP Server, the copyBinary script may return the following message:
Warning Message :1 Nov 20, 2014 10:47:57 - WARNING - CLONE-20266 Unable to archive a file. Nov 20, 2014 10:47:57 - CAUSE - CLONE-20266 The file "/scratch/oracle/webtier6400/network/log/cgisock.9465" did not have sufficient permission to access. Nov 20, 2014 10:47:57 - ACTION - CLONE-20266 Correct the permission of above file and run copyBinary again.
You can safely ignore this message.
When autopurge is not enabled or manual purge is not frequently executed, the MDS database repository could have a lot of older (non-tip) versions accumulated. This can result in the next purge operation to take a very long time (possibly hours). In such a case, the purge operation may need to be terminated to avoid affecting the system performance. Currently, it is not possible to terminate the purge operation using Oracle Fusion Middleware tools. Instead, you need to do this at the database level.
To terminate the purge operation, contact the DBA. The DBA can identify the database session where the purgeMetadata operation is executing and kill the session to stop the purge. Note that MDS purges 300 documents in each iteration, commits the change, and repeats until all purgeable documents are processed. As a result, killing the database session will not affect already committed purge iterations.
When you configure SSL for Oracle HTTP Server, you may need to import the entire certificate chain (rootCA, Intermediate CAs and so on).
Certain browsers, for example Internet Explorer, require that the entire certificate chain be imported to the browsers for SSL handshake to work. If your certificate was issued by an intermediate CA, you will need to ensure that the complete chain of certificates is available on the browser or the handshake will fail. If an intermediate certificate in the chain expires, it must be renewed along with all the certificates (such as OHS server) in the chain.
This section describes configuration issues and workarounds. It includes the following topic:
The Service table page of Fusion Middleware Control contains a mention of shared service tables. Shared service tables are not supported.
There are no documentation errata at this time.