General Issues and Workarounds
This section describes configuration issues and their workarounds. It includes the following topics:
MDS purgeMetadata Command Can Take a Long Time
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.
Node Manager May Return An Error About ADR
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.
Configuration Issues and Workarounds
This section describes configuration issues and workarounds. It includes the following topic:
Deprecated and Desupported Features
The following administrative feature is desupported beginning in 12c (220.127.116.11):
Moving from test to production.
The scripts and procedures used to move your environment from a test to a production environment is no longer supported. However, if you want to change the network configuration, such as host name, network domain name, or IP address, you can use the chghost utitlity, as described in About Changing the Network Configuration in Administering Oracle Fusion Middleware.
Documentation Errata for Administering Oracle Fusion Middleware
The following lists the documentation errata for administration issues:
Using WLST with the Lifecycle Managment Tools
In an SSL-only domain, to connect to a server using WLST, you must set some properties for the start, stop, and discovery actions to succeed.
[ -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.TrustKeyStore=DemoTrust ] [ -Dweblogic.security.JavaStandardTrustKeyStorePassPhrase=password] [ -Dweblogic.security.CustomTrustKeyStoreFileName=filename -Dweblogic.security.TrustKeystoreType=jks [ -Dweblogic.security.CustomTrustKeyStorePassPhrase=password]] [ -Dweblogic.security.SSL.hostnameVerifier=classname]
For more information about setting the properties, see Using the WebLogic Scripting Tool in Understanding the WebLogic Scripting Tool.
For more information about the start, stop, and discovery actions, see Additional Information About Standard Actions in Configuring Oracle Fusion Middleware Using Lifecycle Management Tools.