Do you want to change the database version number after the PSU update?

After installing the PSU patch, the login database found that the Sqlplus, the database version number has not changed. View MOS official gives the following explanations. At the same time do a test, will hit the PSU patch after the database cold backup to the patch before the database can still

Start the database without any errors.

Applies To:

Oracle database-enterprise edition-version 10.2.0.4 to 12.1.0.1 [Release 10.2 to 12.1]
Information in this document applies to any platform.

GOAL

This article helps to find whether PSUs released for Oracle Database Server 10gr2 (10.2.0.x) and 11gR1 (11.1.0.x), 11g R2 (11.2.0.x) and 12c R1 (12.1.0.1) Change the database version.

Solution

Do patchset Updates (PSUs ' s) change the Oracle Release version/fifth Digit?

Answer:no.

The psu  i.e 10.2.0.4.x or higher, 11.1.0.7.x  and 11.2.0.1.x or higher and 12.10.1 Relea Sed for Oracle Database Server version 10.2.0.4.x or higher , 11.1..0.7.0, 11.2.0.1 or higher and 12.1.0.1   RE Spectively does not change the database version  that means 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/11.2.0.3.x/11.2.0.4.x and 12.1.0.1. x  (where x is the fifth digit) does not change the 5th digit of the Oracle Database Server version.

After applying the PSU "Opatch lsinventory"  still shows the version as 10.2.0.4.0/10.2.0.5.0 for Oracle 10g R 2, 11.1.0.7 for Oracle 11g R1, 11.2.0.1/11.2.0.2/11.2.0.3/11.2.0.4 for Oracle 11g R2 and 12.1.0.1 for Oracle 12c R1&NBSP ;

PSU ' S also will not change the version of Oracle binaries (like Sqlplus, Exp/imp etc.)

Note:it is also applicable for the Oracle Enterprise Manager Grid Control and EM Agent

Although Patch Set Updates is referenced by their 5-place version number, with the 10.2, 11.1 and 11.2 PSUs the product Banners and Oracle Universal Installer (OUI) information is not updated with the new version number. For the 10.2, 11.1, 11.2 and 12.1 PSUs, use the Opatch inventory information to determine the PSU version currently instal Led.

Example

> Opatch lsinventory

and compare it to the version table listed in

Note 854428.1 Patch Set Updates for Oracle products

Section 7, "Determining the Patch Set Update Version"

Or

1. Make sure your Opatch version was 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.2 Oracle_homes

$ opatch Version
Invoking Opatch 10.2.0.4.8

Opatch version:10.2.0.4.8

2. Verify if PSU is installed in the Oracle_home

$ Opatch lsinventory-bugs_fixed | Egrep ' psu| PATCH SET UPDATE '

...
12827740 13343461 Wed, 07:11:36 GMT, PSU 11.1.0.7.9 (includes CPUOCT2011)
13343461 13343461 Wed Feb 07:11:36 GMT DATABASE PATCH SET UPDATE 11.1.0.7.10 (includes

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

For Windows : Get the output as mentioned below

Example output:

Action_time ID ACTION VERSION BUNDLE COMMENTS
----------------------------   -- ------ -------- ------ --------------

30-jul-12 10.28.44.656000 PM APPLY 11.2.0.2 Winbun Patch 20

Note:the Registry$history would not contain the row showing the PSU Post Install step were executed unless Catbundle.sql is  Executed. This means if the Post Install steps were skipped because the DB is upgraded or created after installing the PSU, this RO W would not exist

Note: MoS view the registry$history view to see if the DB is updating the PSU and can also be viewed through the dba_registry_history view.

This article is from "Technical achievement dream!" "Blog, be sure to keep this provenance http://dreamsanqin.blog.51cto.com/845412/1535784