How to perform rolling upgrade-downgrade in 11g ASM

 

The purpose of this document is to provide information about the ASM rolling upgrade feature and step by step to install a patchset or patch in ASM home without downtime.

Solution

The following conditions shoshould be met for to perform ASM rolling upgrade

(*) An ASM rolling upgrade applies only to clustered ASM instances.

(*) Separate ASM home. (ASM and DB home shocould not be same)

(*) You can perform rolling upgrades only in environments with 11g Release 1 (11.1) and later release

Ie the following combination is possible

11g CRS, 11g ASM with 11g Database
Or
11g crs.11g ASM with 10g Database

(*) ASM Sid format shocould be + ASM [1-9]

/Etc/oratab
+ ASM1:/Oracle/ASM/product/11.1.0/asm_1: N
Db11g:/Oracle/ASM/product/11.1.0/db_1: N
 

ASM rolling upgrade (step by step)

1) to perform a rolling upgrade, you shoshould have separate ASM home

To enable the ASM instance for Rolling migration mode, you can use this command to start the rolling migration to <database version>.

Alter system start rolling migration to '11. 1.0.7.0 ';

You can run this command from any one of the ASM instance in the cluster. this command does not actually perform the rolling migration but communicates with all the ASM instances in the cluster. this command informs the other ASM instances of RAC that it is preparing to perform an upgrade. once the rolling migration is enabled, You can query each ASM instance to view current state of the ASM;

SQL> select sys_context ('sys _ cluster_properties ', 'Cluster _ state') from dual;

Sys_context ('sys _ cluster_properties ', 'Cluster _ state ')
--------------------------------------------------------------------------------
In rolling upgrade

The above output shows ASM instance in rolling upgrade status. Once you confirm the state of the ASM instance in rolling upgrade, you can now safely perform the below steps to upgrade ASM home in rolling method.

2) shutdown the DB instance, ASM instance and listener

Srvctl stop instance-D <dB Name>-I <Instance name>

Srvctl stop ASM-n <node name>

Srvctl stop listener-n <node name>-L <listener Name>

3) apply the software upgrade to the ASM home.

Select the current node from the node selection page ("specify hardware cluster installation mode ")

Node selection page does not allow to deselect the remote node (s) for the following reason

ASM and database homes are same

ASM Sid is not in the format of + ASM [1-9]

4) apply the patch 7436280 locally (* this step is required only to upgrade from 11.1.0.6 to 11.1.0.7 patchset *)

CD 1, 7436280
Opatch apply-Local

5) Startup the ASM instance, DB instance, listener

Srvctl start ASM-n <node name>

Srvctl start instance-D <dB Name>-I <Instance name>

Srvctl start listener-n <node name>-L <listener Name>

6) Repeat steps 2 to 5 on remaining ASM instances in the cluster.

7) after successful upgrade of ASM on all node, need to end the ASM rolling migration operation and to signal the ASM instance new version state.

Alter system stop rolling migration;

* Validates that all of the members of the cluster are at the same software version. if there are one or more ASM instances that have different versions, then oracle displays an error and the cluster continues to be in rolling upgrade mode.
* Rebalance operations that were pending are restarted if the setting for the asm_power_limit parameter enables this.
* The ASM instances begin supporting the full clustered ASM functionality.

 

ASM rolling downgrade

You need to have an ASM Home software and central inventory backup (before apply the patchset) to downgrade.

Perform the following steps for removing the 11.1.0.7 Patch Set

1) to enable the ASM instance for Rolling downgrade mode, you can use this command to start the rolling mirgration to <database version>.

Alter system start rolling migration to '11. 1.0.7.0'

This command does not actually perform the rolling downgrade but communicates with all the ASM instances in the cluster. this command informs the other ASM instances of RAC that it is preparing to perform an downgrade. once the rolling downgrade is enabled, You can query each ASM instance to view current state of the ASM;

SQL> select sys_context ('sys _ cluster_properties ', 'Cluster _ state') from dual;

Sys_context ('sys _ cluster_properties ', 'Cluster _ state ')
--------------------------------------------------------------------------------
In rolling downgrade

The above output shows ASM instance in rolling downgrade status. Once you confirm the state of the ASM instance in rolling downgrade, you can now safely perform the below steps to downgrade ASM home in rolling method.

2) shutdown the instance, ASM instance and listener.

Srvctl stop instance-D <dB Name>-I <Instance name>

Srvctl stop ASM-n <node name>

Srvctl stop listener-n <node name>-L <listener Name>

3) restore the Oracle 11g installation and central inventory that you backed up before applying the patch set. (See/etc/orainst. Loc .)

4) Startup the ASM instance and check v $ version information shows previous version IE 11.1.0.6

Srvctl start ASM-n <node name>

Srvctl start instance-D <dB Name>-I <Instance name>

Srvctl start listener-n <node name>-L <listener Name>

5) Repeat steps 2 to 4 on remaining ASM instances in the cluster.

6) after successful downgrade of ASM on all node, need to end the ASM rolling downgrade operation and to signal the ASM instance new version state.

Alter system stop rolling migration;

During the ASM upgrade/downgrade mode, only the following operations are permitted.

* Mount diskgroup
* Unmount diskgroup
* Database file open, close, resize, and delete
* Limited access to fixed views and Fixed Packages ie only local views are available; all global views are not allowed during rolling upgrade/downgrade Mode

Not allowed operations

* Rebalance
* Add/drop/online/offline Disk

Please check the known issues with ASM rolling upgrade.

Note.742647.1 ASM rolling upgrade fails with SIGSEGV in ksxpcini ()
Note.746816.1 Ora-15160: Rolling migration internal fatal error during upgrade of ASM to 11.1.0.7.0
Bug 7673203 cannot perform ASM rolling upgrade if Sid not in format + ASM [1-9]

 

 

 

 

 

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.