ORACLEAUTOMATICSTORAGEMANAGEMENT-Chapter 2 ASMInstance (3)

ASM supports rolling upgrade. You can use the rolling upgrade method to create a patchsets for ASM or migrate to a new version to provide higher-level and lower-level high availability. Note: To use the ASM rolling migration feature, the ASM software version must be at least 11.1. In addition, the latest version of ORACLE clusterware is required for Rolling upgrade. Figure (Omitted) before starting the rolling migration, you must use the command TO set the ASM instance in the cluster TO the rolling migration mode, for example (execute version upgrade): alter system start rolling migration TO 11.2.0.2;
Remember that the preceding rolling upgrade command does not actually execute the upgrade and migration. It is only a preparation for upgrading and migration of the cluster ASM instance. In addition, rolling migration is not retained if all ASM instances fail in rolling migration mode. Figure (Omitted) shows 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 that 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 in the migration-ready status. Once the rolling upgrade is enabled, each ASM instance can be shutdown so that the software upgrade can be started. After a specific instance is upgraded, the ASM instance can restart and mount the disk group. At this time, the upgraded ASM instance is added to the cluster in a later version. This configuration can only be used in rolling upgrade mode.
The following steps summarize the migration process:

1. confirm that all nodes have installed the new software version. 2. Confirm that oracle clusterware runs in the maximum version. 3. Make sure all ASM instances are of the same version. 4. Ensure that the rebanlance operation is not in progress. If the rebanlance operation is running, wait until the operation is complete. Then start migration. 5. Use the following command to set the ASM cluster to the migration Mode: Alter system start rolling migration to 11.2.0.2; 6. Stop the ASM instance in the old version. 7. Start the ASM instance from the new version ORACLE_HOME. 8. Execute the task again ~ Step 5 until all ASM instances in the cluster are upgraded. 9. After all the ASM instance software is upgraded, use the following command to disable the rolling migration Mode: Alter system stop rolling migration; The following operations are restricted in rolling migration Mode: Disk mount and dismount operations on all database files, such as file open, close, read, write, resize, deleteASM, and shutdown of RDBMS instances, startup and recovery 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 disabled, all functions of ASM can be used.