In this Document
Applies to:
Oracle Database - Enterprise Edition - Version 9.2.0.8 to 12.1.0.2 [Release 9.2 to 12.1]
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Purpose
Frequently Asked Questions for Oracle Database Server Patching.
Questions and Answers
1) What is a patch?
A patch is a piece of code/software designed to fix problems with the
existing code/software. This includes fixing security vulnerabilities
and other bugs, and improving the usability or performance.
2) Why are patches needed?
Patches are needed to fix problems with program code that is not working as expected.
3) What is an Interim patch?
Interim patches, also known as "one-off" patches, are created to
provide a specific fix between the release of patch sets. They require
a particular base release or patch set to be installed before they can
be applied. They generally address specific bugs for a particular
customer, and generally should not be applied unless instructed by
Oracle to do so.
4) What is a patch conflict?
If a patch makes different changes to the same section of code
that another patch modifies, then these two patches conflict, and only
one of them can be installed (unless a merge or overlay patch is
available).
Example:
- Patch A, which is already installed in the Oracle home, updates aaa.o, bbb.o and ccc.o in libserver10.a
- Patch B, which is to be installed, updates aaa.o and ddd.o in libserver10.a
- Patch B is in conflict with Patch A because they both update object aaa.o in libserver10.a
Result: OPatch reports Patch B is in conflict with Patch A and
recommends an SR be filed requesting a merge of Patch A and Patch B
created. If the option to continue the installation is selected, Patch A
will be rolled back and Patch B will be installed. The bugs fixed in
Patch A will no longer be fixed.
5) What is a Superset patch?
If a particular patch to be applied contains all of the fixes
included in an already installed patch, plus additional fixes, then the
patch with more fixes is a superset patch, and there is no conflict.
Example:
- Patch C and D, which is already installed in the Oracle home, fixed bugs 5, 6,7 and 8
- Patch E,which is to be installed, fixes bugs 5,6,7,8,9, and10.
- Patch E is considered a superset of Patch C and D .
Result: it is not considered as an error situation. OPatch removes
the subset patches from the Oracle Home and applies the new patch.
6) What is a Combination conflict?
If a patch to be installed conflicts with more than one already
installed patch, this is considered a combination conflict. In this
case, OPatch will remove all conflicting patches then apply only the new
patch.
7) What is a subset conflict?
If all the bugs fixed by the patch being installed are fixed in a
patch already installed in the Oracle Home, the patch being installed
is a subset.
Example:
- Patch A, which is already installed in the Oracle home, fixed bugs 1, 2 and 3
- Patch B, which is to be installed, fixes bugs 1 and 2.
- Patch B is a subset of Patch A
Result: it is not considered as an error situation. Patch B will not be installed and reported as a subset to Patch A
8) What is a Duplicate conflict?
If a patch is installed and it is reinstalled, it is considered a duplicate
Example:
- Patch A, which is already installed in the Oracle home, fixed bugs 1, 2 and 3
- Patch A is reinstalled
Results: If -skip_duplicate is included in the apply command, OPatch
will skip the duplicate. If not set, OPatch will rollback Patch A and
reapply it
9) What is a Security Patch Update (SPU)?
Critical Patch Updates are the primary means of releasing
security fixes for Oracle products. CPUs are cumulative with respect to
prior CPUs and generally contain only security fixes.
10) What is a Merge patch?
A merge patch is one where multiple conflicting patches are combined into one integrated patch.
11) What is a Bundle patch?
A collection of different patches packaged together as one unit
that is issued between patch sets. A patch bundle is usually cumulative.
Windows bug fixes for the Database are generally issued as a patch
bundle.
12) What are Patch Set Updates (PSU)?
A collection of proactive, stabilizing cumulative patches for a
particular product version (base release or patch set). PSUs are
cumulative and include all of the security fixes from CPU patches, plus
additional fixes.
13) What is an Overlay patch?
When an interim patch conflicts with a PSU, patch conflict resolution
is achieved by providing a new patch that coexists with (and requires)
the PSU patch. The new patch overlays the PSU, and the PSU is a
pre-requisite for the overlay patch.
14) What is a Patch Set?
The main way in which Oracle provides bug fixes in between
releases. Oracle bundles a number of fixes, test them thoroughly
together, and package them together for easy download and installation.
They generally do not include new functionality and do not require a
new certification. All of the fixes in the patch set have been tested
and are certified to work with each other.
Please refer to the following article for more detailed patch set information.
Note 552777.1 Patchset FAQ
15) What is a Terminal patch set?
The last patch set planned to be released on a particular platform
for a given Oracle Database release is called a Terminal patch set.
16) What is a Terminal or Final patch ?
In general the terminology of Terminal and Final patch is often
referred for SPU and PSU. It is nothing but the last patch planned to be
released on a particular platform for a given Oracle release. However
this is applicable only for the customers who are in Premier Support.
Sometimes
it can happen that based on development's discretion Oracle may still
continue to release the patches even after the Terminal or Final patch
is announced but only for those who have purchased Extended Support
License from Oracle.
17) What is the Error Correction Policy for Oracle Database Server?
Please refer the following article for detailed information about the error correction policy for Oracle Database Server:
Note 209768.1 Database, FMW, EM Grid Control, and OCS Software Error Correction Support Policy
18) What is the Oracle lifetime support policies?
Please refer the following article for detailed information about the Oracle lifetime support policy :
Note 971415.1 Oracle Lifetime Support policies
Below notes are redirected to this note:
Different types of Patch Conflicts - Superset/Subset/Duplicate/Bug/File (Doc ID 563656.1)
How To Determine Patch Is Superset/Subset Patch ? (Doc ID 307706.1)
References
NOTE:971415.1 - Oracle Lifetime Support Policies
NOTE:1430923.1 - Patch Nomenclature for Oracle Products
NOTE:209768.1 - Database, FMW, Enterprise Manager, TimesTen In-Memory Database, and OCS Software Error Correction Support Policy
NOTE:552777.1 - Patchset FAQ
To Bottom