This section describes configuration issues and their workarounds. It includes the following topics:
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 got SYS.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:
For Oracle BI Enterprise Edition, you must use ODBC DataDirect drivers to establish connections to ODBC data sources.
ODBC DataDirect drivers are also used by the Oracle Platform Security Services (OPSS) security store implementation to access credentials.
In Oracle BI Enterprise Edition, DataDirect ODBC framework version 8.0.2 and Oracle Wire Protocol version 7.1.6 are configured for data source name (DSN) and DNS-less connectivity without additional configuration.
The certified Oracle Database versions include:
12.2.1.2 or higher
11.2.0.4 or higher
To support Oracle BI Enterprise Edition 12.2.1.2.0, you must configure the 12.2.0.1 version of Oracle Database to allow older client versions to connect. Set the minimum authentication protocol allowed when connecting to Oracle Database instances to version 11 by adding the following setting to your Oracle Database server sqlnet.ora file:
SQLNET.ALLOWED_LOGON_VERSION_SERVER=11
You can find additional information about the DataDirect drivers in the Progress DataDirect documentation located in the following Oracle BI Enterprise Edition 12c installation directories:
oracle_home\bi\common\ODBC\Merant\7.1.6\help
oracle_home\bi\common\ODBC\Merant\8.0.2\help
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.
In an environment with Oracle SOA Suite, Oracle B2B, or Oracle Business Process Management, you may receive the one of the following sets of errors when the Oracle WebLogic Server Administration port is enabled:
SEVERE : [PLUGIN][SOA] - ERROR - Apr 19, 2016 2:03:24 AM - CLONE-53003 Error in examining B2B. SEVERE : [PLUGIN][SOA] - CAUSE - Apr 19, 2016 2:03:24 AM - CLONE-53003 B2B examination failed. SEVERE : [PLUGIN][SOA] - ACTION - Apr 19, 2016 2:03:24 AM - CLONE-53003 Make sure that all the specified values are correct and domain configuration isvalid. Check managed server logs and clone logs for more details. oracle.as.t2p.sdk.model.exception.FMWT2PCopyConfigException: Apr 19, 2016 2:03:24 AM - CLONE-53003 Error in examining B2B.User 'principals=[weblogic, Administrators]' has administration role. All tasks by administrators must go through an Administration Port.
SEVERE : [PLUGIN][SOA] - ERROR - Apr 25, 2016 4:38:13 AM - CLONE-53004 Error in examining Human WorkFlow. SEVERE : [PLUGIN][SOA] - CAUSE - Apr 25, 2016 4:38:13 AM - CLONE-53004 Human WorkFlow examination failed. SEVERE : [PLUGIN][SOA] - ACTION - Apr 25, 2016 4:38:13 AM - CLONE-53004 Make sure that all the specified values are correct and domain configuration is valid. Check managed server logs and clone logs for more details. oracle.as.t2p.sdk.model.exception.FMWT2PCopyConfigException: Apr 25, 2016 4:38:13 AM - CLONE-53004 Error in examining Human WorkFlow. Apr 25, 2016 4:38:13 AM - CLONE-53004 Error in examining Human WorkFlow.oracle.bpel.services.workflow.client.WorkflowServiceClientException: javax.naming.AuthenticationException: User 'principals=[weblogic, Administrators]' has administration role. All tasks by administrators must go through an Administration Port. [Root exception is java.lang.SecurityException: User 'principals=[weblogic, Administrators]' has administration role. All tasks by administrators must go through an Administration Port.]
To workaround this issue, disable the Oracle WebLogic Server Administration port using the Administration Console.
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 may have a lot of older (non-tip) versions accumulated. In this situation, the next purge operation may take a very long time (possibly hours). You may need to terminate the purge operation to avoid affecting the system performance. Currently, it is not possible to terminate the purge operation using Oracle Fusion Middleware tools. Instead, you must terminate the operation 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 does not affect already committed purge iterations.
In some circumstances, when you start a Managed Server from the Administration Console, an error similar to the following is logged on the Node Manager console. It indicates an issue while initializing Automatic Diagnostic Repository (ADR).
SEVERE: failure initializing ADR oracle.dfw.common.DiagnosticsException: failure loading adrci binary from the system path: null Cause: DFW-40112: There was an error executing adrci commands; the following errors have been found "null"
You can ignore this error because Node Manager does not use ADR.
When you configure SSL for Oracle HTTP Server, you may need to import the entire certificate chain (rootCA, Intermediate CA’s and so on).
Certain browsers, for example Internet Explorer, require that the entire certificate chain be imported to the browsers for the 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: