ORACLE AUTOMATIC STORAGE Management Translator-Chapter II ASM Instance (3)

ASMSupportRolling Upgrades, forASMhit Patchsets or migrate to a new version you can use the rolling upgrade method to provide a higher levelthe lower level of high availability. Note that in order to use ASM's rolling migration special, the ASM software version is at least 11.1. In addition, rolling upgrades requireORACLE Clusterware is the latest version. figure (slightly)before starting a rolling migration, you must use the command to set the ASM instance in the cluster to rolling migration mode, such as (perform version upgrade):ALTER SYSTEM START rolling migration to 11.2.0.2;
remember that the previous rolling upgrade command does not actually perform an upgrade migration, it is only a preparatory work for the cluster ASM instance upgrade migration. in addition,Scrolling migration does not hold state if all ASM instances fail in rolling migration mode.figure (slightly)to view the current cluster status, you can use the following query:

sql> SELECT sys_context (' sys_cluster_properties ', ' cluster_state ') from DUAL; Sys_context (' sys_cluster_properties ', ' cluster_state ') ----------------------------------------------------- Normal The output above shows the cluster is in a NORMAL (non-migration) state. sql> SELECT sys_context (' sys_cluster_properties ', ' cluster_state ') from DUAL; Sys_context (' sys_cluster_properties ', ' cluster_state ') ----------------------------------------------------- Rolling migration

The output shows that the cluster is a migration-ready state. Once the rolling upgrade is enabled, each ASM instance can be shutdown so that the software upgrade can be started. ASM instances can restart and Mount disk groups after a specific instance upgrade is complete. At this point, the upgraded ASM instance is re-joined to the cluster with a high version. This configuration is only allowed in rolling upgrade mode.
The following steps summarize the migration process:

1. Confirm that all nodes have a new version of the software installed 2. Confirm that Oracle Clusterware is running at the highest version 3. Verify that all ASM instance versions are the same 4. Ensure that the rebanlance operation is not in progress, if the rebanlance operation is running, etc. after the operation is completed Start migration again. 5. Set ASM Cluster to migration mode using the following command: ALTER SYSTEM START rolling migration to 11.2.0.2; 6. Stop running the ASM instance under the old version. 7. Start the ASM instance from the new version oracle_home. 8. Repeat the steps until all ASM instances in the cluster have been upgraded. 9. When all ASM instance software has been upgraded, disable the rolling migration mode using the following command: ALTER SYSTEM STOP rolling migration; The following operations are restricted in rolling migration mode: Disk group mount and dismount Operations for all database files, such as file open,close,read,write,resize and delete Shutdown,startup and recovery for ASM and RDBMS instances Access to the v$ view is restricted The following operations are not allowed in rolling migration mode: Rebalance Adding and dropping disks, online and offline disks After the migration mode is off, all ASM functions are available.