16:The Oracle home may be locked by other OPatch/OUI processes. Please kill those processes, remove the file $ORACLE_HOME/.patch_storage/patch_locked and then retry.
17:Please make sure the private option '-supplied_nodes' is used in apply/napply session.
20:Please make sure no other OPatch or OUI processes is running. Try to run $ORACLE_HOME/oui/bin/runInstaller.
21:Please contact Oracle Support.
22:Please make sure no other OPatch or OUI processes is running. Try running $ORACLE_HOME/oui/bin/runInstaller.
24:Please run OPatch again. If problem exists, please contact Oracle Support.
25:Please use "emocmrsp" or "emocmrsp.bat" to create a response file
26:Please use 'opatch util applySql' for sql related patches or 'opatch util enableOnlinePatch' for online patches to add sids to already installed patch(es).
27:Please invoke 'opatch lsinventory' to see if the patch to be rolled back was already installed in the Oracle Home.
28:This Oracle Home uses snowball patching model in which patches must be rolled back as last-in-first-out. The patch you tried to roll back was not last-in, hence can't be rolled back until other patches had been rolled back first.
29:Please check the patch ID because OPatch was not able to find it to roll it back.
30:Please look at log file to locate the prerequisite that failed. Invoke 'opatch apply  -report' or 'opatch rollback  -report'.
31:Please download latest OPatch from My Oracle Support by Patch 6880880, release version (as appropriate) and appropriate platform.
32:This patch is not suitable for this Oracle Home. Please make sure you have downloaded the right patch.
33:This version of OPatch/OUI doesn't support Patchset Update.
34:You need a higher version of the current OUI version which is put the current OUI number here.
35:Please check if you have typed in the correct command line.
36:OPatch requires DB instances to be up and running for online patching. Please make sure that the specified DB instances are up.
37:There are missing system commands that OPatch needs to proceed patching.
38:This patch is not suitable for this platform. Please make sure you have selected the right platform.
39: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.
40:There is a patch conflict with a Patchset Update. Please contact Oracle Support.
41:OPatch needs to modify files which are being used by some processes.
42:This patch requires some other patches to be installed in the Oracle Home. OPatch cannot find those required patches in the Oracle Home.
43: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.
44:Please make sure that there is only one translation-language molecule given to OPatch for the specified patch(es) in a session.
45:OPatch failed to back up the Oracle Home for restore in case things go wrong during patch installation. Please check if you has the privilege to access and modify the Oracle Home.
46:OPatch failed to back up the Oracle Home inventory for restore in case things go wrong during patch installation. Please check if you has the privilege to access and modify $ORACLE_HOME/.patch_storage/backup/oneoffs directory.
47:OPatch failed to back up the Oracle Home inventory for restore in case things go wrong during patch installation. Please check if you has the privilege to access and modify $ORACLE_HOME/.patch_storage/backup/ContentsXML directory.
48:OPatch failed to back up the patch inventory (product.xml). Please check if the file exists in $ORACLE_HOME.
49: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 priviledge to access and modify those files.
50:The patch(es) has missing or incorrect "unique patch id" metadata. Do not install patch(es).
55:There are conflicts between the incoming patch and the already-installed patched. Please see the log file for details.
56:The fixes by this patch are currently in the Oracle Home. There is no need to apply this patch.
57:The incoming patch is a superset of some patches installed in the Oracle Home.
58:There are conflicts with online patch. Please contact Oracle Support.
59:Please contact Oracle Support services to solve the conflicts.
60:Please contact Oracle Support services to solve the conflicts.
61:Please contact Oracle Support services to solve the conflicts.
62:Please contact Oracle Support services to solve the conflicts.
63:Please contact Oracle Support services to solve the conflicts.
64:You need to roll back the conflicting patches before applying the online patch.
65:You need to roll back the conflicting online patches before applying the new patch.
66:You need to roll back the conflicting patches before applying the patch.
67:No patches can be applied right now. Please refer to My Oracle Support Note 1299688.1 for instructions on resolving patch conflicts.
70:Please roll back the conflict patches using 'opatch rollback' command.
71: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.
72:OPatch failed to prepare files for remote command execution. Please check if you have the privilege to create files under $ORACLE_HOME/.patch_storage.
75:OPatch failed to prepare directories for remote command execution. Please check if you have the privilege to create files under $ORACLE_HOME/.patch_storage.
76:OPatch failed to prepare files for remote command execution. Please check if you have the privilege to create files under $ORACLE_HOME/.patch_storage.
77:OPatch failed to generate temporary files for remote command execution. Please check if you have the privilege to create files under $ORACLE_HOME/.patch_storage.
100:The patch has a pre-script and OPatch failed to invoke it.
101:The patch has a pre-script which returns error.
102:Please make sure the specified Oracle Home you want to apply the patch to is ready to be patched.
103:OPatch failed to record this patch in the inventory. Please contact Oracle Support.
104:Please check if you have the privilege to create StandAlone inventory fort this $ORACLE_HOME.
105:Please check if you can copy files to this $ORACLE_HOME.
106:Please check if you have the privilege to update the file.
107:Please check if you have the privilege to update the file.
108:Please check if you have the privilege to overwrite the file.
109:Please check if you have the privilege to update the file.
110:Please check if you have the privilege to update the file.
111:Please check if you have the privilege to create files under directory $ORACLE_HOME/.patch_storage.
112:Please check if you have the privilege to create files under directory $ORACLE_HOME/.patch_storage.
113:Please refer to the log file and contact Oracle Support.
115:Please check if you have the privilege to modify the Oracle Home's inventory.
116:Please check if you have the privilege to modify the Oracle Home's inventory ($ORACLE_HOME/inventory/oneoffs).
117:Please check if you have the privilege to create sub-directory under $ORACLE_HOME/inventory/oneoffs.
118:Please check if you have the privilege to modify the Stand-Alone Oracle Home inventory.
119:Please check if you have the privilege to save a patch to the Stand-Alone Oracle Home inventory.
120:Please check if you have read/write access to the Oracle Home's inventory.
121:Some deployments failed. Please contact Oracle Support.
122:Please bind the FA config instance object to the artifact using bindToClone() API.
123:Please map Oracle Home for the artifacts.
124:Please map patch for the artifacts.
125:Please firstly install the patch which contains the artifacts you want to deploy.
126:Please install the patch that contains the artifacts's corresponding file and make sure the files are copied to the Oracle Home correctly.
127:Please contact Oracle Support services to correct this problem.
128:Please make sure the operation is supported by OPatch or you can do it manually.
129:Please check if there is any other process that is using the Oracle Home.
130:Please contact Oracle Support services to solve this problem.
131:Please make sure you have the right privilege to create file under log location.
132:Please start AdminServer and give correct credential.
133:Please make sure the AdminServer is in the right status.
134:Please start SOA server and give correct credential.
135:Please make sure the SOA server is in the right status.
136:Please make sure the composite exists.
137:Please run the command again or you can deploy the composite manually.
138:Please make sure the SOA server is ready to receive requests and response.
139:Please try corresponding WLST command listDeployedComposite and make sure it can get the list of deployed composites.
140:Please make sure the AdminServer and SOA server is in the right status.
141:Please try corresponding WLST command startComposite and make sure the composite can get started.
142:Please try corresponding WLST command stopComposite and make sure the composite can get stopped.
143:Please try corresponding WLST command exportComposite and make sure you can get the exported composite.
144:Please try corresponding WLST command extractPlan and make sure you can get the extracted plan.
145:Please try corresponding WLST command exportUpdates and make sure you can get the exported updates. 
146:Please manually import JDev customizations from the current revision into the new revision of the composite.
147:Please try corresponding WLST command attachPlan and make sure you can attach plan to the incoming composite.
148:Please try corresponding WLST command mergeUpdates and make sure you can merge updates to the incoming composite.
149:Please try corresponding WLST command activateComposite and make sure you can make the status of the previous composite into active.
150:Please try corresponding WLST command assignDefault and make sure you can make the composite as default.
151:Please make sure a same composite with different revision has already been deployed to the server.
152:Please try corresponding WLST command retireComposite and make sure you can retire the default composite.
153:Please try corresponding WLST command deployComposite and make sure you can deploy the composite manually.
154:Please try corresponding WLST command disableEventsDelivery and make sure you can disable EDN events.
155:Please try corresponding WLST command enableEventsDelivery and make sure you can enable EDN events.
156:Please try corresponding WLST command importUpdates and make sure you can import updates to the incoming composite. 
157:Please check if runtime classpaths are properly set.
158:Please try corresponding WLST command undeployComposite and make sure you can undeploy the composite manually.
160:Please undeploy the same composite or skip deploy the composite as the same composite has been deployed.
161:Please deploy the base composite.
162:Please make sure the composite exists.
163:Please check if the temporary location %ORACLE_HOME%/.patch_storage/%cookedpatchid% is accessible.
164:Please make sure you can create object under temporary location.
165:Please try corresponding WLST command listDeployedComposites and make sure you can get the default revision of the composite.
166:Please try corresponding WLST command activateComposite and make sure you can change the status of the composite to active.
167:Please try corresponding WLST command and make sure you can deploy SOA ResourceBundle artifacts manually.
168:Please set the correct patch location for the BIP artifact using setOriginalPatchLocation() API.
169:Please give all the mandatory interview values required for deploying BI artifacts.
170:Please check the original patch location set for BIP artifact.
171:Please set the correct BI home for the BIP artifact using setBIHome() API.
172:Please check if runtime classpaths are properly set.
173:Please try corresponding WLST command and make sure you can deploy BIP artifacts manually.
174:Please give the correct credential for Node Manager.
175:Please make sure Node Manager is correctly configured and started.
176:Please configure the targets correctly and run the command again.
177:Please make sure you can start AdminServer via Node Manager.
178:Please check if you can control servers to be in the right status via Node Manager.
179:Please make sure you can stop servers via Node Manager.
180:Please make sure you can start servers via Node Manager.
181:Please configure Node Manager correctly and make sure you can stop Manager Server via Node Manager.
182:Please configure Node Manager correctly and make sure you can start Manager Server via Node Manager.
183:Please configure Node Manager correctly and make sure you can stop AdminServer via Node Manager.
184:Please configure Node Manager correctly and make sure you can start AdminServer via Node Manager.
185:Please connect AdminServer to the Node Manager.
186:Please try corresponding WLST command listDeployedComposites to see if you can get all the deployed composites. 
200:Please contact Oracle Support services to fix the post script.
201:Please contact Oracle Support services to fix the post script.
202:Please apply the patch to the remote nodes manually.
203:Please check whether you have the read privilege to the %ORACLE_HOME%/.patch_storage/COOKED_PATCH_ID/rac directory.
204:Please apply the patch to the remote nodes manually.
205:Please apply the patch to the remote nodes manually.
206:Please check the configuration of your RAC system.
207:Please try 'opatch -help' command to correct the command you used.
208:Please try 'opatch -help' command to correct the command you used.
209:Please apply the patch to the remote nodes manually.
210:Please apply the patch to the remote nodes manually.
211:Please apply the patch to the remote nodes manually.
212:Please apply the patch to the remote nodes manually.
213:Please apply the patch to the remote nodes manually.
214:Please apply the patch to the remote nodes manually.
215:Error getting the patches to apply. Please make sure you have specified a proper directory with valid patches.
216:No patches could be identified to apply. Please make sure you have specified a proper directory with valid patches.
217:A combination of composite and singleton patches are being put up for apply. Please use 'opatch apply' for composite patches and 'opatch napply' to apply many singleton patches in one shot.
218:No patches can be applied right now. Please refer to My Oracle Support Note 1299688.1 for instructions on resolving patch conflicts.
219: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.
220:Unsupported cmd-line option, composite patches do not support '-phBaseDir' or '-phBaseFile'. Please use '-ph' on each composite patch instead.
221:Composite patches are not supported for this method.
