Do Patchset Updates (PSU's) Change the Oracle Release Version/Fifth Digit? [ID 861152.1] |
||
|
||
|
Modified 08-SEP-2011 Type HOWTO Status PUBLISHED |
|
In this Document
Goal
Solution
References
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.
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.
Do Patchset Updates (PSU's) Change the Oracle ReleaseVersion/Fifth 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 fifth 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
$ 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.28.02.856762 AM 4 APPLY 10.2.0.4 PSU PSU 10.2.0.4.3
23-AUG-10 07.31.48.001892 AM 1 APPLY 10.2.0.4 PSU PSU 10.2.0.4.4
Note: The registry$history will not contain 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
-------------------------------------------------------------------------------------------------------
Blog: http://blog.csdn.net/tianlesoftware
Weibo: http://weibo.com/tianlesoftware
Email: [email protected]
DBA1 群:62697716(满); DBA2 群:62697977(满) DBA3 群:62697850(满)
DBA 超级群:63306533(满); DBA4 群:83829929(满) DBA5群: 142216823(满)
DBA6 群:158654907(满) DBA7 群:69087192(满) DBA8 群:172855474
DBA 超级群2:151508914 DBA9群:102954821 聊天 群:40132017(满)
--加群需要在备注说明Oracle表空间和数据文件的关系,否则拒绝申请