Database Reference
In-Depth Information
In this case, it is recommended to perform a full offline backup of the entire in-
frastructure, which includes:
•
Oracle system files
•
JDK
•
Middleware Home
•
JMS file stores
•
Transaction logs
•
SOA domain
•
Database (using a tool such as RMAN)
Before applying patches
The overwhelming majority of Oracle patches are downloaded from Oracle Sup-
port and come in the form of an OPatch. Many, but not all of these patches
provide some form of rollback mechanism. If the patch application is unsuccess-
ful, it will not be installed. If the patch application is successful, but does not re-
solve your particular problem, it can be rolled back (in other words, uninstalled).
These patches can be OPSS patches, JDK patches, OWSM patches, Oracle
WebLogic Server patches, Oracle SOA Suite patches, Oracle BPM patches,
BAM patches, or any type of patch related to one of the many underlying sub-
components. Even though most (but not all) patches can be rolled back, there
are rare cases where patches can corrupt or produce undesirable results in your
system. It is both our and Oracle's recommendation to backup your environment
prior to applying a patch. However, with a little bit of understanding of the patch,
it may not be necessary to perform a full backup, and only a partial backup may
be needed.
If the patch is a JDK patch, simply perform an offline backup of JDK (this being
the common JDK directory or the one specific to your installation).
If the patch is an Oracle SOA Suite
11g
patch, simply perform an offline backup
of the following:
