What is a PSU patch for Oracle Home?
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., 22.214.171.124.1 to 126.96.36.199.2). Once a PSU is applied, only PSUs can be applied in future quarters until the database is upgraded to a new base version.
More details about PSU
- The PSU released for Oracle Database Server version 10.2.0.4.0/10.2.0.5.x , 11.1..0.7.0 and 188.8.131.52.0/184.108.40.206.0 respectively does not change the database version . That means PSU 10.2.0.4.x /10.2.0.5.x, 220.127.116.11.x, 18.104.22.168.x /22.214.171.124.x ( where x is the fifth digit ) does NOT change the 5th digit of the Oracle Database Server version.
- opatch lsinventory” still shows the version as 10.2.0.4.0/10.2.0.5.0 for Oracle 10g R2, 126.96.36.199 for Oracle 11g R1 and 188.8.131.52 /184.108.40.206 for Oracle 11g R2
- PSU’s also will not change the version of oracle binaries (like sqlplus, exp/imp etc.)
- PSU patches are available till 12cR1 only. Oracle has moved to release update and revision with 12cR2 and above. we can use the same below queries to obtain information about Release Update and revision also
how to check PSU patch version in oracle/ Release Update/Release Update revision
$ opatch lsinv -bugs_fixed | grep PSU 85733156 88334280 Tue Feb 09 16:54:18 MST 2012 DATABASE PSU 10.2.0.4.3 (INCLUDES CPUJAPR2011) 8833280 883280 Tue Feb 09 16:54:18 MST 2011 DATABASE PSU 10.2.0.4.4 (INCLUDES CPUOCT2010)
The below command can be used to get the information about PSU/Release update/Release update revision
$ORACLE_HOME/OPatch/opatch lsinventory|grep "Patch description" $ORACLE_HOME/OPatch/opatch lsinventory -details $ORACLE_HOME/OPatch/opatch lspatches
Verify the PSU Post Install steps were run in the DB
select substr(action_time,1,30) action_time, substr(id,1,10) id, substr(action,1,10) action, substr(version,1,8) version, substr(BUNDLE_SERIES,1,6) bundle, substr(comments,1,20) comments from registry$history;
With 12cR1 and above
set line 1000 col action form a12 col version form a40 col description form a85 col action_date form a20 select description, action, to_char(action_time,'DD/MM/RR HH24:MI:SS') action_date, from dba_registry_sqlpatch;
xml-20108: (fatal error) start of root element expected : Check out this page for the solution on the error org.xml.sax.SAXParseException: : XML-20108 we get while applying the opatch
How to run Opatch in non interactive form : Check how to apply opatch in silent mode
rollback the Oracle patch: check out this on how to rollback the oracle patch like database patch, application patch, Application server patch with detailed steps
opatch failed with error code 73: Find out the cause and resolution for the topmost common issues in Window while applying patches using opatch
download Patch from Oracle using Wget : Downloading oracle patches from the Oracle website is time-consuming. We download Patch from Oracle using Wget directly to the server to save time and energy
check patches applied in WebLogic : This page contains details on how to check patches applied in WebLogic in version 10.3.6,12.1.1,12.1.1 above with commands