Do patchset updates (PSU's) change the Oracle release version/fifth th digit? [ID 861152.1]

 

Do patchset updates (PSU's) change the Oracle release version/fifth th digit? [ID 861152.1]
	Modified08-sep-2011TypeHowtoStatusPublished

In this document
Goal
Solution
References

Applies:

Oracleserver-Enterprise Edition-version: 10.2.0.4 to 11.2.0.2-release: 10.2 to11.2
Information in this document applies to anyplatform.

Goal

Thisarticle helps to find whether PSU released for Oracle Database server10gr2 (10.2.0.x) and 11gr1 (11.1.0.x) and 11g R2 (11.2.0.x) change the database version.

Solution

Do patchset updates (PSU's) change the Oracle releaseversion/Reset th digit?

Answer: No.

The psu I. E 10.2.0.4.x/10.2.0.5.x, 11.1.0.7.x and11.2.0.1.x/11.2.0.2.x released for Oracle Database Server version10.2.0.4.0/10.2.0.5.x, 11. 1 .. 0.7.0 and 11.2.0.1.0/11.2.0.2.0 respectively does not change the database version. thatmeans PSU 10.2.0.4.x/10.2.0.5.x, 11.1.0.7.x, 11.2.0.1.x/11.2.0.2.x (where X is the same th digit) does not change the 5th digit of the oracledatabase server version.

After applying the PSU 10.2.0.4.x/10.2.0.5.x, 11.1.0.7.x, 11.2.0.1.x/11.2.0.2.x "opatch lsinventory" still shows theversion as 10.2.0.4.0/10.2.0.5.0 for Oracle 10g R2, 11.1.0.7 for Oracle 11gr1 and 11.2.0.1/11.2.0.2 for Oracle 11g r2

PSU's also will not change the version of Oracle binaries (likesqlplus, exp/IMP etc .)

Note: It is also applicable for the Oracle Enterprise managergrid control and EM agent

Although patch set updates are referenced by their 5-place version number, withthe 10.2, 11.1 and 11.2 PSUs the product banners and Oracle universalinstaller (Oui) information are not updated with the new version number. forthe 10.2, 11.1 and 11.2 PSUs, use the opatch inventory information to determinethe PSU version currently installed.

Example:

> Opatch lsinventory

And compare it to the version table listed in

Note 854428.1 patch set updates fororacle Products

Section 7, "determining the Patch Set Update version"

Or

1. Make sure your opatch version is at or above

• 10.2.0.4.5 for Version 10.2 oracle_homes
• 11.1.0.6.5 for version 11.1 oracle_homes
• 11.2.0.1.0 for version 11.1 oracle_homes

$ opatch version 
InvokingOPatch 10.2.0.4.8 

OPatchVersion: 10.2.0.4.8

2. Verify if PSU is installed in the ORACLE_HOME

$ opatch lsinv -bugs_fixed | grep PSU 

85761568833280 Tue Feb 09 16:54:18 MST 2010 DATABASE PSU 10.2.0.4.3 (INCLUDESCPUJUL2009) 
88332808833280 Tue Feb 09 16:54:18 MST 2010 DATABASE PSU 10.2.0.4.4 (INCLUDESCPUOCT2009)

3. 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;

Action_time ID action version bundle comments
----------------------------------------------------------------
23-aug-10 07.282132.856762 am 4 apply 10.2.0.4 PSU 10.2.0.4.3
23-aug-10 07.31.48.001892 am 1 apply 10.2.0.4 PSU 10.2.0.4.4

 

Note: The registry $ history will not contain in the row showingthe PSU post install step was executed unless catbundle. SQL is executed. this means if the post install steps were skipped because the DB was upgradedor created after installing the PSU, this row will not exist

 

 

 

 

 

Bytes -------------------------------------------------------------------------------------------------------

Blog: http://blog.csdn.net/tianlesoftware

WEAVER: http://weibo.com/tianlesoftware

Email: dvd.dba@gmail.com

Dba1 group: 62697716 (full); dba2 group: 62697977 (full) dba3 group: 62697850 (full)

Super DBA group: 63306533 (full); dba4 group: 83829929 (full) dba5 group: 142216823 (full)

Dba6 group: 158654907 (full) dba7 group: 69087192 (full) dba8 group: 172855474

DBA super group 2: 151508914 dba9 group: 102954821 chat group: 40132017 (full)

-- Add the group to describe the relationship between Oracle tablespace and data files in the remarks section. Otherwise, the application is rejected.