Last updated on July 28th, 2019 at 08:42 am
include both the security fixes and priority fixes. The key with PSUs is they
are minor version upgrades (e.g., 188.8.131.52.1 to 184.108.40.206.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 220.127.116.11.0/18.104.22.168.0 respectively does not change the database version . That means PSU 10.2.0.4.x /10.2.0.5.x, 22.214.171.124.x, 126.96.36.199.x /188.8.131.52.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, 184.108.40.206 for Oracle 11g R1 and 220.127.116.11 /18.104.22.168 for Oracle 11g R2
PSU’s also will not change the version of oracle binaries (like sqlplus, exp/imp etc.)
How to Verify if PSU is installed in the ORACLE_HOME
$ 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)
Verify the PSU Post Install steps were run in the DB
select substr(action_time,1,30) action_time,