Each log file is tagged with the timestamp of the operation. Log files are named as opatch_<date mm-dd-yyyy>_<time hh-mm-ss>.log.
A new log file is created each time OPatch is executed.
For example, if a log file is created on May 17th, 2013 at 11.55 PM, it will be named as follows:
You can set OPatch to debug mode by setting the environment variable OPATCH_DEBUG to TRUE.
OPatch also maintains an index of the commands executed with OPatch and the log files associated with it in the
opatch_history.txt file located in the <ORACLE_HOME>/cfgtoollogs/opatch directory. A sample of the
history.txt file is as follows:
Date & Time : Tue Apr 26 23:00:55 PDT 2013 Oracle Home : /private/oracle/product/11.2.0/db_1/ OPatch Ver. : 188.8.131.52.2 Current Dir : /scratch/oui/OPatch Command : lsinventory Log File : /private/oracle/product/11.2.0/db_1/cfgtoollogs/opatch/opatch-2013_Apr_26_23-00-55-PDT_Tue.log
This section to contain a list of other documentation that may provide support. The main link will point to the "Master Note for OPatch" (Doc ID 293369.1) in MOS.
Patch Set FAQ: See Patchset FAQ (Doc ID 552777.1) for a complete summary of patchset FAQs. This document is available in My Oracle Support.
Information Center: Patching and Maintaining Oracle Database Server/Client Installations (Doc ID 1351428.1 )
Oracle now offers a wide range of products, including hardware and operating systems. However, patches required by some products are not currently supported by OPatch.
If the Oracle product you install (such as Oracle Database or Fusion Middleware) creates an Oracle home directory, then OPatch is provided as part of that installation.
Typically, the types of Oracle products not supported by OPatch include:
Hardware (for example, firmware updates for Sun servers).
Operating system (for example, kernel patch updates for Oracle Linux or Oracle Solaris.)
Java (for example, patch updates for JRE, JDK)
Software products that do not create an Oracle home directory (for example, Oracle OpenOffice)