How to check the PSU & CPU patch applied status???
[ora@sujeet ~]$ cd $ORACLE_HOME/OPatch
[ora@sujeet ~]$ opatch lsinv -bugs_fixed | grep PSU
[ora@sujeet ~]$ opatch lsinv -bugs_fixed | grep CPU
Opatch status check:
[ora@sujeet ~]$ opatch lsinventory|grep <patch no>
Security Patch status:-
SQL> select * from sys.registry$history;
-----------------------------------------
SET linesize 200 pagesize 200
col action_time FOR a28
col version FOR a10
col comments FOR a35
col action FOR a25
col namespace FOR a12
SELECT * FROM registry$history;
---------------------------------------------
NOTE:
1.Critical Patch Update (CPU)
2.Patch Set Update (PSU)
Critical Patch Update (CPU) now refers to the overall release of security fixes each quarter rather than the cumulative database security patch for the quarter. Think of the CPU as the overarching quarterly release and not as a single patch.
Patch Set Updates (PSU) are the same cumulative patches that include both the security fixes and priority fixes. The key with PSUs is they are minor version upgrades (e.g., 11.2.0.1.1 to 11.2.0.1.2). Once a PSU is applied, only PSUs can be applied in future quarters until the database is upgraded to a new base version.
Security Patch Update (SPU) terminology is introduced in the October 2012 Critical Patch Update as the term for the quarterly security patch. SPU patches are the same as previous CPU patches, just a new name. For the database, SPUs can not be applied once PSUs have been applied until the database is upgraded to a new base version.
Bundle Patches are the quarterly patches for Windows and Exadata which include both the quarterly security patches as well as recommended fixes.
Keeping your Oracle database software up to date is a critical and time-consuming task for DBAs. For many years now, Oracle has been releasing Critical Patch Updates on a quarterly basis. These patches, as the name implies, contain critical updates to the software, often released in response to a newly found security vulnerability. More recently, Oracle has also been releasing Patch Set Updates on a quarterly basis. These also contain important fixes to the Oracle software. However, there is confusion about the difference between the two and more importantly, confusion about which one needs to be applied. So whats the difference and which one should you apply?
According to Oracle Support article ID 1446582.1: Frequently Asked Questions (FAQ) Patching Oracle Database Server:
“A PSU is 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. 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.”
So, there you have it. CPUs are smaller and more focused than PSU and mostly deal with security issues. PSUs contain bug fixes AND they contain the security fixes from the CPU. When you download a PSU, it will tell you which CPU it contains. PSUs are on the same quarterly schedule as the Critical Patch Updates (CPU), specifically the Tuesday closest to the 17th of January, April, July, and October. One thing to keep in mind, however, is that once a PSU has been installed, the recommended way to get future security content is to apply subsequent PSUs. Reverting from PSU back to CPU, while possible, would require significant effort and so is not advised. So with this in mind, why would someone choose to apply a CPU rather than a PSU? I suppose for folks who are concerned only with security fixes and not functionality fixes, a CPU-only approach may be best. It does seem to be the more conservative approach as a CPU is (in theory) less like to cause trouble than a PSU, simply because it has less code changes in it.
No comments:
Post a Comment