|
?
SPU
?
?
- SPU contains only the CPU program security fixes
- PSU contains the CPU program security fixes and additional high-impact/low-risk critical bug fixes
- BP includes all PSU fixes along with additional high value fixes
An installation can only use?one?of the SPU,PSU or BP patching methods.
All methods allow “interim patches” to be installed,but the version of an interim patch required may vary depending on the patching method.?
Windows platforms are special in that they do not support normal “interim patches”.
See "More Information on Proactive Database Patches" near the end of this document for details of current and historic proactive patches.
Version Numbers
The various patching methods have different ways to indicate the version as detailed in the following table:
|
Term
Version Number
Example
Major Release
Designated by the first 2 fields of the version (fields are separated by decimal points)
11.2
Base Release
First 4 fields are the version of a Major Release
11.2.0.1
Patch Set Release (PSR)
Designated by the 4th field of the version
11.2.0.4
Patch Set Update (PSU)
Designated by 5th?field of a version.
11.2.0.4.160419
Bundle Patch (BP)
Also designated by 5th?field of a version but with text to indicate which series of bundle
Exadata Database Bundle Patch 11.2.0.4.160419
Security Patch Update (SPU)
Designated by a month/year
11.2.0.4 Jan 2015 SPU
As of November 2015,the version numbering for new Bundle Patches,Patch Set Updates,and Security Patch Updates for Oracle Database have a new format. This new format replaces the numeric 5th field of the bundle version with a release date in the form YYMMDD:
YY is the last 2 digits of the year
MM is the numeric month (2 digits)
DD is the numeric day of the month (2 digits)
Note that the release date is the release date of the main BP,PSU,or SPU.
This new version format makes it easier to see which bundle patches are from which time frame,and in particular,which patches are from the same Critical Patch Update release. For examples and more information,see My Oracle Support?Note 2061926.1,Oracle Database,Enterprise Manager and Middleware - Change to Patch Numbering from Nov 2015 onwards.
Note:
Only the first 4 fields of a version are shown in Database views / trace banners etc..? The 5th field and patching method can be verified by checking the inventory of an installation.?
eg: "opatch lsinventory" will show the Patch Set (or Base Release) level along with a list of patches installed. The patch listing usually shows a descriptive line/s for SPU/PSU/BP patches indicating what patch method and version is in use.
In earlier RDBMS Product versions (such as Oracle 8 and Oracle 9),this same version numbering system was referred to as "digits",as in "the version number 9.2.0.4 shows the Major Release is the first two digits of 9.2". Therefore,you may still find some legacy Oracle sources that refer to a version number such as 12.1.0.2,as "showing the Major Release is the first two digits of 12.1". Since "12.1" is technically 3 digits and *not* 2 digits,the term "field" used in the table above is preferred over the legacy term "digit".
Testing Overview
（编辑：济南站长网）
【声明】本站内容均来自网络，其相关言论仅代表作者个人观点，不代表本站立场。若无意侵犯到您的权利，请及时与联系站长删除相关内容!
