_VERSION:12.1.0.1.1
_ERROR_CODE:16
_ERROR_MSG:The Oracle Home may be locked by other OPatch/OUI processes. Maybe
you are installing some Oracle products or you are using OPatch to patch some
Oracle products on this machine.
_ACTION: You can check whether there is OPatch or OUI process running by
running $ORACLE_HOME/oui/bin/runInstaller. If this command fails, that means
there is other OPatch or OUI process running. Please kill those processes,
remove the file $ORACLE_HOME/.patch_storage/patch_locked and then retry. 
_ERROR_CODE:17
_ERROR_MSG:Private option '-supplied_nodes' is not provided in apply/napply
session. This error should not happen on FMW12 environment.
_ACTION:Please make sure the private option '-supplied_nodes' is used in
apply/napply session. FMW12 user should not use '-supplied_nodes' option on
FMW12 environment.
_ERROR_CODE:20
_ERROR_MSG:The Oracle Home may be locked by other OPatch/OUI processes. Maybe
you are installing some Oracle products or you are using OPatch to patch some
Oracle products on this machine.
_ACTION: You can check whether there is OPatch or OUI process running by
running $ORACLE_HOME/oui/bin/runInstaller. If this command fails, that means
there is other OPatch or OUI process running. Please kill those processes,
remove the file $ORACLE_HOME/.patch_storage/patch_locked and then retry. 
_ERROR_CODE:21
_ERROR_MSG:OPatch is not able to set up online patch properties file.
_ACTION:Please contact Oracle Support.
_ERROR_CODE:22
_ERROR_MSG:The Oracle Home may be locked by other OPatch/OUI processes. Maybe
you are installing some Oracle products or you are using OPatch to patch some
Oracle products on this machine.
_ACTION: You can check whether there is OPatch or OUI process running by
running $ORACLE_HOME/oui/bin/runInstaller. If this command fails, that means
there is other OPatch or OUI process running. Please kill those processes,
remove the file $ORACLE_HOME/.patch_storage/patch_locked and then retry. 
_ERROR_CODE:24
_ERROR_MSG:OPatch cannot write the lock file. Possible causes are:
      No read or write permission to ORACLE_HOME lock file.
      The ORACLE_HOME lock file is corrupted.
_ACTION:Please try to delete $ORACLE_HOME/.patch_storage/patch_locked, if you
are able to delete the file, please run OPatch again. If you cannot delete
this file, you might don?t have write permission to the Oracle Home. You have
to be the owner of the Oracle Home with write permission to run OPatch.
_ERROR_CODE:25
_ERROR_MSG:When you run OPatch in silent mode, you need to provide an Oracle
Configuration Manager (OCM) response file.
_ACTION:Please use "emocmrsp" or "emocmrsp.bat" to create a response file.
Then run OPatch with ?ocmrf option pointing to the response file created. 
_ERROR_CODE:26
_ERROR_MSG:The patch is already installed in the Oracle Home. This error
should not happen on FMW12 environment.
_ACTION:If you are patching Oracle databases, please use 'opatch util
applySql' for sql related patches or 'opatch util enableOnlinePatch' for
online patches to add sids to already installed patch(es).
_ERROR_CODE:27
_ERROR_MSG:OPatch is not able to get the patch rollback area.
_ACTION:Please invoke 'opatch lsinventory' to see if the patch to be rolled
back was already installed in the Oracle Home. If the patch that you want to
rollback is in the Oracle Home, either the patch storage is deleted by
mistake, or the patch inventory got corrupted. Please contact Oracle Support.
_ERROR_CODE:28
_ERROR_MSG:FMW12 uses one-off patching model. This error should not happen on
FMW12 environment.
_ACTION:If you see this error message, please contact Oracle Support.  
_ERROR_CODE:29
_ERROR_MSG:You want to roll back a patch, but OPatch thinks that you have not
applied that patch because it is not in the Oracle Home inventory. It is
possible that you specify a wrong patch ID.
_ACTION:If you are using the wrong patch ID, please use the correct one and
try again. If you think that you are using the correct one, please run 'opatch
lsinventory' command to check whether the patch ID exists in the inventory. If
the patch exists and you cannot rollback, please contact Oracle Support.
_ERROR_CODE:30
_ERROR_MSG:Some of the prerequisite checks failed.
_ACTION:Please look at log file to locate the prerequisite that failed. You
can invoke 'opatch apply -report' or 'opatch rollback -report' to run all
prerequisite checks again.,
_ERROR_CODE:31
_ERROR_MSG:The patch(es) require a higher version of OPatch than the version
you have in the Oracle Home.
_ACTION:Please download latest OPatch from My Oracle Support. If this is FMW12
or later, use Patch 16733520. If it is DB12.1 or later, use Patch 16733530. If
it is none of the above, use Patch 6880880.
_ERROR_CODE:32
_ERROR_MSG:The patchs patching model is not suitable for the Oracle Home.
_ACTION:This patch is not suitable for this Oracle Home. Please make sure you
have downloaded the right patch.
_ERROR_CODE:33
_ERROR_MSG:Given Oracle Home are not compatible with the Patch Set Update(s)
given. You should not run into this issue on FMW12 or DB12.1.
_ACTION:This version of OPatch/OUI doesn't support Patch Set Update. Please
contact Support.
_ERROR_CODE:34
_ERROR_MSG:The OUI does not support 'Fusion Apps' patching.
_ACTION:You need a higher version of the current OUI version in the Oracle
Home to install this patch.
_ERROR_CODE:35
_ERROR_MSG:Some required command line input values are not given.
_ACTION:Please check if you have typed in the correct command line options.
_ERROR_CODE:36
_ERROR_MSG:DB Instance given is not up or is invalid.
_ACTION:OPatch requires DB instances to be up and running for online patching.
Please make sure that the specified DB instances are up.
_ERROR_CODE:37
_ERROR_MSG:Some required system command(s) are missing.
_ACTION:There are missing system commands that OPatch needs to proceed
patching. Make sure they are in your PATH.
_ERROR_CODE:38
_ERROR_MSG:Some of the patches given is not applicable on current platform.
_ACTION:This patch is not suitable for this platform. Please make sure you
have selected the right platform.
_ERROR_CODE:39
_ERROR_MSG:Some components required by the given patch(es) are missing from
the Oracle Home.
_ACTION:This patch requires some components to be installed in the home.
Either the Oracle Home doesn't have the components or this patch is not
suitable for this Oracle Home. 
_ERROR_CODE:40
_ERROR_MSG:OPatch cannot auto roll back the conflicting Patch Set Update.
_ACTION:There is a patch conflict with a Patch Set Update. Please contact
Oracle Support.
_ERROR_CODE:41
_ERROR_MSG:The patch(es) modify files that are being used.
_ACTION:OPatch needs to modify files which are being used by some processes.
Therefore it cannot proceed. Please bring down all related processes and try
again.
_ERROR_CODE:42
_ERROR_MSG:Some patch(es) required by the patch(es) to be installed are not
installed in the Oracle Home.
_ACTION:This patch requires some other patches to be installed in the Oracle
Home. OPatch cannot find those required patches in the Oracle Home. Therefore
it cannot proceed. Please make sure you install those patches first and try
again.
_ERROR_CODE:43
_ERROR_MSG:The patch(es) cannot be rolled back.
_ACTION:OPatch won't be able to roll back the given patch. A common reason is
there are other patches that depend on this patch. You need to roll back those
dependent patches before you can roll back this patch.
_ERROR_CODE:44
_ERROR_MSG:OPatch cannot proceed patch(es) given with multiple language
translation molecules in a session.
_ACTION:Please make sure that there is only one translation-language molecule
given to OPatch for the specified patch(es) in a session.
_ERROR_CODE:45
_ERROR_MSG:OPatch failed to backup the Oracle Home for restore.
_ACTION:OPatch failed to back up the Oracle Home for restore in case things go
wrong during patch installation. Please check if you have the privilege to
access and modify the Oracle Home.
_ERROR_CODE:46
_ERROR_MSG:OPatch is not able to back up $OH/inventory/oneoffs.
_ACTION:OPatch failed to back up the Oracle Home inventory for restore in case
things go wrong during patch installation. Please check if you have the
privilege to access and modify $ORACLE_HOME/.patch_storage/backup/oneoffs
directory.
_ERROR_CODE:47
_ERROR_MSG:OPatch is not able to backup $OH/inventory/ContentsXML.
_ACTION:OPatch failed to back up the Oracle Home inventory for restore in case
things go wrong during patch installation. Please check if you have the
privilege to access and modify $ORACLE_HOME/.patch_storage/backup/ContentsXML
directory.
_ERROR_CODE:48
_ERROR_MSG:OPatch is not able to backup $OH/product.xml
_ACTION:OPatch failed to back up the patch inventory (product.xml). Please
check if the file exists in $ORACLE_HOME.
_ERROR_CODE:49
_ERROR_MSG:OPatch is not able to backup patch(es) for restore.
_ACTION:OPatch failed to back up existing patches in the Oracle Home inventory
-- patches that are impacted by new patch installation. Please check if you
have privilege to access and modify those files.
_ERROR_CODE:50
_ERROR_MSG:Some of the patch(es) to be installed have no unique patch id or
the unique patch id defined is incorrect.
_ACTION:The patch has missing or incorrect "unique patch id" metadata. Do not
install it.
_ERROR_CODE:55
_ERROR_MSG:There are conflicts between the patch to be installed and the
patches already installed in the Oracle Home.
_ACTION:There are conflicts between the incoming patch and the patches already
installed in the Oracle Home. Please see the log file for details.
_ERROR_CODE:56
_ERROR_MSG:You are installing a patch but the Oracle Home already has another
patch or the same patch installed that fixes the same set of bugs.
_ACTION:The fixes by this patch are currently in the Oracle Home. There is no
need to apply this patch.
_ERROR_CODE:57
_ERROR_MSG:You are installing a patch and the Oracle Home has another patch
that fixes less bugs.
_ACTION:The incoming patch is a superset of some patches installed in the
Oracle Home.
_ERROR_CODE:58
_ERROR_MSG:Some of the online patch(es) have conflict.
_ACTION:There are conflicts with online patch. Please contact Oracle Support.
_ERROR_CODE:59
_ERROR_MSG:Patch conflicts found. If you install this patch, you may lose
important bug fixes.
_ACTION:Please contact Oracle Support to resolve the conflicts.
_ERROR_CODE:60
_ERROR_MSG: Patch conflicts found. If you install this patch, you may lose
important bug fixes.
_ACTION:Please contact Oracle Support to resolve the conflicts.
_ERROR_CODE:61
_ERROR_MSG: Patch conflicts found. If you install this patch, you may lose
important bug fixes.
_ACTION:Please contact Oracle Support to resolve the conflicts.
_ERROR_CODE:62
_ERROR_MSG: Patch conflicts found. If you install this patch, you may lose
important bug fixes.
_ACTION:Please contact Oracle Support services to solve the conflicts.
_ERROR_CODE:63
_ERROR_MSG: Patch conflicts found. If you install this patch, you may lose
important bug fixes.
_ACTION:Please contact Oracle Support services to solve the conflicts.
_ERROR_CODE:64
_ERROR_MSG:Online patch to be installed has conflict with a regular patch.
_ACTION:You need to roll back the conflicting patches before applying the
online patch.
_ERROR_CODE:65
_ERROR_MSG:The non-online patch to be installed has conflict with an online
patch.
_ACTION:You need to roll back the conflicting online patches before applying
the new patch.
_ERROR_CODE:66
_ERROR_MSG:Patches to be installed have conflict among themselves.
_ACTION:You need to remove the conflicting patches in the list and try again.
_ERROR_CODE:67
_ERROR_MSG:Patch to be installed has conflict with part of a composite patch
installed in Oralce Home.
_ACTION:No patches can be applied right now. Please refer to My Oracle Support
Note 1299688.1 for instructions on resolving patch conflicts.
_ERROR_CODE:70
_ERROR_MSG:Patch to be installed has conflict with patches installed in Oracle
Home which cannot be auto-rolled back.
_ACTION:Please roll back the conflict patches using 'opatch rollback' command.
_ERROR_CODE:71
_ERROR_MSG:OPatch failed to bac kup patch files that are to be rolled back for
restore.
_ACTION:OPatch failed to backup existing patches in the Oracle Home inventory
-- patches that are impacted by patch roll back. Please check if you have
priviledge to access and modify those files.
_ERROR_CODE:72
_ERROR_MSG:OPach failed to create FP file. You should not run into this error
on FMW12 or DB12.1.
_ACTION:OPatch failed to prepare files for remote command execution. Please
check if you have the privilege to create files under
$ORACLE_HOME/.patch_storage.
_ERROR_CODE:75
_ERROR_MSG:OPatch failed to create DP file. You should not run into this error
on FMW12 or DB12.1.
_ACTION:OPatch failed to prepare directories for remote command execution.
Please check if you have the privilege to create files under
$ORACLE_HOME/.patch_storage. You should not run into this error on FMW12 or
DB12.1.
_ERROR_CODE:76
_ERROR_MSG:OPatch failed to create autoFp/autoFr/autoDr/autoRc files. You
should not run into this error on FMW12 or DB12.1.
_ACTION:OPatch failed to prepare files for remote command execution. Please
check if you have the privilege to create files under
$ORACLE_HOME/.patch_storage.
_ERROR_CODE:100
_ERROR_MSG: The patch has a pre-script that exits with non-zero exit code when
called by OPatch.
_ACTION: Check the patch README and/or Support to see if you need to run the
pre-script again.
_ERROR_CODE:101
_ERROR_MSG: The patch has a pre-script that exits with non-zero exit code when
called by OPatch.
_ACTION: Check the patch README and/or Support to see if you need to run the
pre-script again.
_ERROR_CODE:102
_ERROR_MSG:The Oracle Home is not ready to be patched. Please check log files
for more detail.
_ACTION:Please make sure the specified Oracle Home you want to apply the patch
to is ready to be patched.
_ERROR_CODE:103
_ERROR_MSG:OPatch failed to register the patch to Oracle Home inventory.
_ACTION:OPatch failed to record this patch in the inventory. Please contact
Oracle Support.
_ERROR_CODE:104
_ERROR_MSG:OPatch failed to register the patch into stand alone Oracle Home
inventory. You should not see this error on FMW12 and DB12.1.
_ACTION:Please check if you have the privilege to create StandAlone inventory
fort this $ORACLE_HOME or if your Oracle Home has OUI installed.
_ERROR_CODE:105
_ERROR_MSG:OPatch failed to copy some of the files.
_ACTION:Please check if you can copy files to this $ORACLE_HOME.
_ERROR_CODE:106
_ERROR_MSG:OPatch failed to update some of the jar files.
_ACTION:Please check if you have the privilege to update the file.
_ERROR_CODE:107
_ERROR_MSG:OPatch failed to update some of the archive files.
_ACTION:Please check if you have the privilege to update the file. Some
products such as DB12 GI Oracle Home locks the files, so you must bring down
instances and unlock the home before patching. Please look at the patch README
for instructions.
_ERROR_CODE:108
_ERROR_MSG:OPatch failed to replace some of the files with the original files.
_ACTION:Please check if you have the privilege to update the file. Some
products such as DB12 GI Oracle Home locks the files, so you must bring down
instances and unlock the home before patching. Please look at the patch README
for instructions.
_ERROR_CODE:109
_ERROR_MSG:OPatch failed to update some of the archives.
_ACTION:Please check if you have the privilege to update the file. Some
products such as DB12 GI Oracle Home locks the files, so you must bring down
instances and unlock the home before patching. Please look at the patch README
for instructions.
_ERROR_CODE:110
_ERROR_MSG:OPatch failed to update some of the jar files. Some products such
as DB12 GI Oracle Home locks the files, so you must bring down instances and
unlock the home before patching. Please look at the patch README for
instructions.
_ACTION:Please check if you have the privilege to update the file.
_ERROR_CODE:111
_ERROR_MSG:OPatch failed to create a Makefile for manual restore.
_ACTION:Please check if you have the privilege to create files under directory
$ORACLE_HOME/.patch_storage.
_ERROR_CODE:112
_ERROR_MSG:OPatch failed to write to Makefile for manual restore.
_ACTION:Please check if you have the privilege to create files under directory
$ORACLE_HOME/.patch_storage. Some products such as DB12 GI Oracle Home locks
the files, so you must bring down instances and unlock the home before
patching. Please look at the patch README for instructions.
_ERROR_CODE:113
_ERROR_MSG:Some of the make commands have failed.
_ACTION:Please refer to the log file and contact Oracle Support.
_ERROR_CODE:115
_ERROR_MSG:OPatch failed to regenerate library.
_ACTION:Please contact Oracle Support.
_ERROR_CODE:116
_ERROR_MSG:OPatch failed to save the patch into inventory.
_ACTION:Please check if you have the privilege to modify the Oracle Home's
inventory ($ORACLE_HOME/inventory/oneoffs).
_ERROR_CODE:117
_ERROR_MSG:OPatch failed to save the patch files into inventory/oneoffs.
_ACTION:Please check if you have the privilege to create sub-directory under
$ORACLE_HOME/inventory/oneoffs.
_ERROR_CODE:118
_ERROR_MSG:OPatch failed to register the patch into stand alone Oracle Home
inventory.
_ACTION:Please check if you have the privilege to modify the Stand-Alone
Oracle Home inventory.
_ERROR_CODE:119
_ERROR_MSG:OPatch failed to register the patch into stand alone Oracle Home
inventory.
_ACTION:Please check if you have the privilege to save a patch to the
Stand-Alone Oracle Home inventory.
_ERROR_CODE:120
_ERROR_MSG:OPatch failed to remove patch entry from inventory.
_ACTION:Please check if you have read/write access to the Oracle Home's
inventory.
_ERROR_CODE:122
_ERROR_MSG:Please bind the FA config instance object to the artifact using
bindToClone() API.
_ACTION:Please bind the FA config instance object to the artifact using
bindToClone() API.
_ERROR_CODE:123
_ERROR_MSG:OPatch was not able to map this artifact to an Oracle Home.
_ACTION:Please map Oracle Home for the artifacts.
_ERROR_CODE:124
_ERROR_MSG:OPatch was not able to find out the patch to which this artifact is
mapped.
_ACTION:Please map patch for the artifacts.
_ERROR_CODE:125
_ERROR_MSG:OPatch requires that Patch be installed in Oracle Home for the FA
operation.
_ACTION:Please firstly install the patch which contains the artifacts you want
to deploy.
_ERROR_CODE:126
_ERROR_MSG:The artifact file is not copied. Possible causes are:
     	OPatch was not able to verify if the artifact was copied during the
installation of the patch.            
	OPatch will not able to deploy this artifact as the corresponding file
was not copied during installation of the patch.
	OPatch will not able to deploy this artifact as there are no valid
patch actions to be applied for the Oracle Home.
	OPatch will not able to deploy this artifact as there is no equivalent
copy action in the patch.
	OPatch will not able to deploy this artifact as the equivalent copy
action has version less than or equal to the ones installed in Oracle Home.
_ACTION:Please install the patch that contains the artifacts's corresponding
file and make sure the files are copied to the Oracle Home correctly.
_ERROR_CODE:127
_ERROR_MSG:OPatch failed to get the FMW client for artifact execution
(Internal OPatch issue)
_ACTION:Please contact Oracle Support services to correct this problem.
_ERROR_CODE:128
_ERROR_MSG:OPatch does not support the operation for this artifact.
_ACTION:Please make sure the operation is supported by OPatch or you can do it
manually.
_ERROR_CODE:129
_ERROR_MSG:OPatch failed to lock the Oracle Home.
_ACTION:Please check if there are any other process using the Oracle Home.
_ERROR_CODE:130
_ERROR_MSG:OPatch failed to unlock the Oracle Home.
_ACTION:Please contact Oracle Support services to solve this problem.
_ERROR_CODE:131
_ERROR_MSG:OPatch failed to create the log file.
_ACTION:Please make sure you have the right privilege to create file under log
location.
_ERROR_CODE:132
_ERROR_MSG:Error connecting to Admin Server. 
_ACTION:Please start AdminServer and give correct credential.
_ERROR_CODE:133
_ERROR_MSG:Failed to check the state of the Admin Server. Possible causes are:
	Not able to get the state of Admin Server.
	The desired state Admin Server should be 'RUNNING'.
_ACTION:Please make sure the AdminServer is in the right status.
_ERROR_CODE:134
_ERROR_MSG:OPatch failed to find the SOA Server. Please check if the SOA
Server is present and and is in RUNNING state.
_ACTION:Please start SOA server and give correct credential.
_ERROR_CODE:135
_ERROR_MSG:SOA Server/soa-infra is not ready to accept requests.
_ACTION:Please make sure the SOA server is in the right status.
_ERROR_CODE:136
_ERROR_MSG:Invalid Path for SOA Composite. Composite will not be redeployed
during deployment operation.
_ACTION:Please make sure the composite exists.
_ERROR_CODE:137
_ERROR_MSG:The composite with input revision is not deployed. Current
Operation cannot be performed.
_ACTION:Please run the command again or you can deploy the composite manually.
_ERROR_CODE:138
_ERROR_MSG:Timeout occurred when deploying SOA composite. No SOA artifact
recovery will be initiated.
_ACTION:Please make sure the SOA server is ready to receive requests and
response.
_ERROR_CODE:139
_ERROR_MSG:OPatch was not able to get the list of deployed SOA Composites.
_ACTION:Please try corresponding WLST command listDeployedComposite and make
sure it can get the list of deployed composites.
_ERROR_CODE:140
_ERROR_MSG:Error in setting up JMX Connectivity. 
_ACTION:Please make sure the AdminServer and SOA server is in the right
status.
_ERROR_CODE:141
_ERROR_MSG:SOA Composite can't get started or is already started.
_ACTION:Please try corresponding WLST command startComposite and make sure the
composite can get started.
_ERROR_CODE:142
_ERROR_MSG:SOA Composite can't get stopped or is already stopped.
_ACTION:Please try corresponding WLST command stopComposite and make sure the
composite can get stopped.
_ERROR_CODE:143
_ERROR_MSG:Error in export composite in SOA Deploy.
_ACTION:Please try corresponding WLST command exportComposite and make sure
you can get the exported composite.
_ERROR_CODE:144
_ERROR_MSG:Error in extract plan.
_ACTION:Please try corresponding WLST command extractPlan and make sure you
can get the extracted plan.
_ERROR_CODE:145
_ERROR_MSG:Error in executing export all Updates.
_ACTION:Please try corresponding WLST command exportUpdates and make sure you
can get the exported updates. 
_ERROR_CODE:146
_ERROR_MSG:JDev Customizations were performed on the current active revision.
Hence, it cannot be imported by OPatch.
_ACTION:Please manually import JDev customizations from the current revision
into the new revision of the composite.
_ERROR_CODE:147
_ERROR_MSG:Error in executing attach plan.
_ACTION:Please try corresponding WLST command attachPlan and make sure you can
attach plan to the incoming composite.
_ERROR_CODE:148
_ERROR_MSG:OPatch was not able to merge updates using SOA's merge tool.
_ACTION:Please try corresponding WLST command mergeUpdates and make sure you
can merge updates to the incoming composite.
_ERROR_CODE:149
_ERROR_MSG:Error in activating previously deployed SOA Composite.
_ACTION:Please try corresponding WLST command activateComposite and make sure
you can make the status of the previous composite into active.
_ERROR_CODE:150
_ERROR_MSG:Error in assigning 'default' to the SOA Composite.
_ACTION:Please try corresponding WLST command assignDefault and make sure you
can make the composite as default.
_ERROR_CODE:151
_ERROR_MSG:OPatch was not able to find a previous revision ID to fall back and
activate if the composite is to be un-deployed.
_ACTION:Please make sure a same composite with different revision has already
been deployed to the server.
_ERROR_CODE:152
_ERROR_MSG:Error in retiring previous revision of the composite.
_ACTION:Please try corresponding WLST command retireComposite and make sure
you can retire the default composite.
_ERROR_CODE:153
_ERROR_MSG:Error in deploying SOA composite.
_ACTION:Please try corresponding WLST command deployComposite and make sure
you can deploy the composite manually.
_ERROR_CODE:154
_ERROR_MSG:Error in Disable EDN Events Delivery.
_ACTION:Please try corresponding WLST command disableEventsDelivery and make
sure you can disable EDN events.
_ERROR_CODE:155
_ERROR_MSG:Error in Enable EDN Events Delivery API.
_ACTION:Please try corresponding WLST command enableEventsDelivery and make
sure you can enable EDN events.
_ERROR_CODE:156
_ERROR_MSG:Error in import updates to the SOA composite.
_ACTION:Please try corresponding WLST command importUpdates and make sure you
can import updates to the incoming composite. 
_ERROR_CODE:157
_ERROR_MSG:Error in getting default Revision of the composite.
_ACTION:Please check if runtime classpaths are properly set.
_ERROR_CODE:158
_ERROR_MSG:Error in undeploying Composite.
_ACTION:Please try corresponding WLST command undeployComposite and make sure
you can undeploy the composite manually.
_ERROR_CODE:161
_ERROR_MSG:No Base composite is deployed for the composite.
_ACTION:Please deploy the base composite.
_ERROR_CODE:162
_ERROR_MSG:Could not find SOA Composite jar.
_ACTION:Please make sure the composite exists.
_ERROR_CODE:163
_ERROR_MSG:Temp location is not specified or OPatch doesn't have read/write
permissions to the Temp location.
_ACTION:Please check if the temporary location
%ORACLE_HOME%/.patch_storage/%cookedpatchid% is accessible.
_ERROR_CODE:164
_ERROR_MSG:OPatch was not able to copy composite jar to the temporary
location.
_ACTION:Please make sure you can create object under temporary location.
_ERROR_CODE:165
_ERROR_MSG:Error in getting default Revision of the composite.
_ACTION:Please try corresponding WLST command listDeployedComposites and make
sure you can get the default revision of the composite.
_ERROR_CODE:166
_ERROR_MSG:The composite is not in active state. Current Operation cannot be
performed.
_ACTION:Please try corresponding WLST command activateComposite and make sure
you can change the status of the composite to active.
_ERROR_CODE:167
_ERROR_MSG:Error in deploying SOA Resource Bundle.
_ACTION:Please try corresponding WLST command and make sure you can deploy SOA
ResourceBundle artifacts manually.
_ERROR_CODE:168
_ERROR_MSG:Please set the correct patch location for the BIP artifact using
setOriginalPatchLocation() API.
_ACTION:Please set the correct patch location for the BIP artifact using
setOriginalPatchLocation() API.
_ERROR_CODE:169
_ERROR_MSG:The mandatory keys in the interview are not filled for this
artifact.
_ACTION:Please give all the mandatory interview values required for deploying
BI artifacts.
_ERROR_CODE:170
_ERROR_MSG:The original patch location set for BIP artifact does not exist
(or) is not a directory.
_ACTION:Please check the original patch location set for BIP artifact.
_ERROR_CODE:171
_ERROR_MSG:Please set the correct BI home for the BIP artifact using
setBIHome() API.
_ACTION:Please set the correct BI home for the BIP artifact using setBIHome()
API.
_ERROR_CODE:173
_ERROR_MSG:Error in deploying BIP.
_ACTION:Please try corresponding WLST command and make sure you can deploy BIP
artifacts manually.
_ERROR_CODE:174
_ERROR_MSG:Invalid credentials of the Node manager.
_ACTION:Please give the correct credential for Node Manager.
_ERROR_CODE:175
_ERROR_MSG:Check Server Life Cycle failed for some servers.
_ACTION:Please make sure Node Manager is correctly configured and started.
_ERROR_CODE:176
_ERROR_MSG:Some targets are not configured.
_ACTION:Please configure the targets correctly and run the command again.
_ERROR_CODE:177
_ERROR_MSG:Error in getting JMX connection after Admin Server restart.
_ACTION:Please make sure you can start AdminServer via Node Manager.
_ERROR_CODE:178
_ERROR_MSG:The server is in not-desired state .
_ACTION:Please check if you can control servers to be in the right status via
Node Manager.
_ERROR_CODE:179
_ERROR_MSG:The server is already up & running.
_ACTION:Please make sure you can stop servers via Node Manager.
_ERROR_CODE:180
_ERROR_MSG:Not connected to Admin Server. Start Admin Server first.
_ACTION:Please make sure you can start servers via Node Manager.
_ERROR_CODE:181
_ERROR_MSG:Error in stopping Manager Server through Node Manager.
_ACTION:Please configure Node Manager correctly and make sure you can stop
Manager Server via Node Manager.
_ERROR_CODE:182
_ERROR_MSG:Error in starting Manager Server through Node Manager.
_ACTION:Please configure Node Manager correctly and make sure you can start
Manager Server via Node Manager.
_ERROR_CODE:183
_ERROR_MSG:Error in stopping AdminServer through Node Manager.
_ACTION:Please configure Node Manager correctly and make sure you can stop
AdminServer via Node Manager.
_ERROR_CODE:184
_ERROR_MSG:Error in starting Admin Server through Node Manager.
_ACTION:Please configure Node Manager correctly and make sure you can start
AdminServer via Node Manager.
_ERROR_CODE:185
_ERROR_MSG:Node Manager not set for the Admin Server.
_ACTION:Please connect AdminServer to the Node Manager.
_ERROR_CODE:186
_ERROR_MSG:Unable to List the deployed composites.
_ACTION:Please try corresponding WLST command listDeployedComposites to see if
you can get all the deployed composites. 
_ERROR_CODE:201
_ERROR_MSG:Execution of post script failed.
_ACTION:Please contact Oracle Support services to fix the post script.
_ERROR_CODE:203
_ERROR_MSG:The directory does not exsit.
_ACTION:Please check whether you have the read privilege to the
%ORACLE_HOME%/.patch_storage/COOKED_PATCH_ID/rac directory.
_ERROR_CODE:204
_ERROR_MSG:OPatch exits on request.
_ACTION:Please apply the patch to the remote nodes manually.
_ERROR_CODE:205
_ERROR_MSG:OPatch exits on request. The patch has not been remotely copied to
the remote nodes.
_ACTION:Please run OPatch on the remote nodes to install the patch.
_ERROR_CODE:206
_ERROR_MSG:Null list of nodes. OPatch was not able to remotely copy the patch
to the remote nodes.
_ACTION:Please check the configuration of your RAC system to see why OPatch
cannot get the node list.
_ERROR_CODE:207
_ERROR_MSG:Command-line option error while attempting to patch remote nodes:
both apply and rollback flags are set.
_ACTION:Please try 'opatch -help' command to correct the command you used.
_ERROR_CODE:208
_ERROR_MSG:Command-line option error while attempting to patch remote nodes:
none of apply and rollback flags is set.
_ACTION:Please try 'opatch -help' command to correct the command you used.
_ERROR_CODE:209
_ERROR_MSG:Removing files on remote nodes failed. 
_ACTION:Please apply the patch to the remote nodes manually.
_ERROR_CODE:210
_ERROR_MSG:Removing directory on remote nodes failed.
_ACTION:Please apply the patch to the remote nodes manually.
_ERROR_CODE:211
_ERROR_MSG:Propagating files to remote nodes failed.
_ACTION:Please apply the patch to the remote nodes manually.
_ERROR_CODE:212
_ERROR_MSG:Propagating directory to remote nodes failed.
_ACTION:Please apply the patch to the remote nodes manually.
_ERROR_CODE:213
_ERROR_MSG:OPatch failed to re-link on remote node.
_ACTION:Please apply the patch to the remote nodes manually.
_ERROR_CODE:214
_ERROR_MSG:OPatch failed to run command on remote node.
_ACTION:Please apply the patch to the remote nodes manually.
_ERROR_CODE:215
_ERROR_MSG:Error getting the patches to apply.
_ACTION:Error getting the patches to apply. Please make sure you have
specified a proper directory with valid patches.
_ERROR_CODE:216
_ERROR_MSG:NApply was not able to get the list of patches to apply.
_ACTION:No patches could be identified to apply. Please make sure you have
specified a proper directory with valid patches.
_ERROR_CODE:218
_ERROR_MSG:There are no patches that can be applied now.
_ACTION:No patches can be applied right now. Please refer to My Oracle Support
Note 1299688.1 for instructions on resolving patch conflicts.
_ERROR_CODE:219
_ERROR_MSG:Patch requires component(s) that are not installed in OracleHome.
_ACTION:Your Oracle Home does not have a required component to install a
patch. Please check to make sure this patch is needed for your Oracle Home.
_ERROR_CODE:220
_ERROR_MSG:Given patches are invalid online patch or the format not matched
with opatch version.
_ACTION:Please check the patch structure.
