Pre-requsite for 11.2.0.1 to 11.2.0.2 ASM rolling upgrade

 

 

This note is to clarify the patch requirement when doing 11.2.0.1 to 11.2.0.2 rolling upgrade.

 

Pre-requsite for 11.2.0.1 to 11.2.0.2 ASM rolling upgrade

There has been some confusion as what patches need to be applied for 11.2.0.1 ASM rolling upgrade to 11.2.0.2 to be successful. documentation regarding this is not very clear (at the time of writing) and a documentation bug has been filed and documentation will be updated in the future.

There are two bugs related to 11.2.0.1 ASM rolling upgrade to 11.2.0.2:

(1) Unpublished bug 9413827: 11201 to 11202 ASM rolling upgrade-old CRS stack fails to stop
(2) Unpublished bug 9706490: LNX64-11202-UD 11201-> 11202, DG offline after restart CRS stack during upgrade

Some of the symptoms include error message when running rootupgrade. sh:
ORA-15154: Cluster rolling upgrade incomplete (from bug: 9413827)
Or
Diskgroup status is shown offline after the upgrade, crsd. log may have:

2010-05-12 03:45:49. 029: [agfw] [1506556224] agfw proxy server sending
Last reply to PE for message: resource_start [ora. mydg1.dg rwsdcvm44 1] ID 4098: 1526
Textmessage [CRS-2674: Start of 'ora. mydg1.dg 'on 'rwsdcvm44' failed]
Textmessage [ora. mydg1.dg rwsdcvm44 1]
Ora. mydg1.dg rwsdcvm44 1:

The following are some scenario and corresponding action that may be taken:

1). If $ gi_home is on version 11.2.0.1.2 (I. e gi psu2 is applied ):

Action: You can apply patch: 9706490 for version 11.2.0.1.2.

Unpublished bug 9413827 is fixed in 11.2.0.1.2 GI psu2. patch: 9706490 for version 11.2.0.1.2 is built on top of 11.2.0.1.2 GI psu2 (I. e. when des the 11.2.0.1.2 GI psu2, hence already des the fix for 9413827 ). applying Patch: 9706490 between des both fixes. opatch will recognize 9706490 is superset of 11.2.0.1.2 GI psu2 (patch: 9655006) and rollback patch 9655006 before applying patch: 9706490 ).

2). If $ gi_home is on version 11.2.0.1.0 (I. e. No GI PSU applied ).

Action: You can apply patch: 9706490 for version 11.2.0.1.2. This wocould Make sure you have applied 11.2.0.1.2 GI psu2 plus both 9706490 and 9413827 (which is already ded In Gi psu2 ).

3). If $ gi_home is on version 11.2.0.1.1 (GI psu1) (this is rare since GI psu1 was only released for Linux platforms and was quite old ).

Action: You can rollback GI psu1 then apply patch: 9706490 on version 11.2.0.1.2.

So for all cases, it is recommended to apply patch: 9706490 for version 11.2.0.1.2.

Regardless which situation, opatch may show conflicts with other CRS patch installed in the gi home. you need to check if those CRS fixes are already encoded in 11.2.0.2 or not. most likely you can rollback those fixes because they are already fixed in 11.2.0.2.

 

 

 

 

From Oracle

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

Blog: http://blog.csdn.net/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 dba5 group: 142216823

Chat group: 40132017 chat 2 group: 69087192

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