oracle 10g rac +asm 进行加物理磁盘与减物理磁盘的测试

对asm进行加磁盘与减磁盘的测试

加了9个200G的磁盘与减少9个200G的磁盘，asm分布 I/O的时间花了大概两个
小时左右，主要看v$asm_operation视图

EST_WORK是要移动的单元的总数，SOFAR是重新平衡操作中到目前为止已移动的单元的数量。
EST_RATE是重新平衡操作每分钟移动的单元的当前数量，EST_MINUTES给出剩余时间的估计值（以分钟计）。

然后state状态有以下几钟
State of the operation:
WAIT – No operations running for the group
RUN – Operation running for the group
REAP – Operation is being run down
HALT – Operation halted by admin
ERRS – Operation halted by errors

具体过程参考metalink 837308.1

主题: Exact Steps To Migrate ASM Diskgroups To Another SAN Without Downtime.
文档 ID: 837308.1 类型: HOWTO
上次修订日期: 15-JUN-2009 状态: PUBLISHED

In this Document
Goal
Solution

——————————————————————————–

Applies to:
Oracle Server – Enterprise Edition – Version: 10.1.0.2 to 11.1.0.7
Information in this document applies to any platform.

Goal
The present document explains in detail the exact steps to migrate ASM diskgroups from one SAN to another SAN without a downtime.

Solution
If your plans are replacing the current disks associated to your diskgroups with a new storage, this operation can be accomplished without any downtime, so you can follow the next steps
1) Backup all your databases and valid the backup (always required to protect your data).

2) Add the new path (new disks from the new storage) to your asm_disktring to be recognized by ASM:
Example:
SQL> alter system set asm_disktring = ‘/dev/emcpowerc*’ , ‘/dev/emcpowerh*’;
Where: ‘/dev/emcpowerc*’ are the current disks.
Where: ‘/dev/emcpowerh*’ are the new disks.

3) Confirm that the new disks are being detected by ASM:
SQL> select path from v$asm_disk;

4) Add the new disks to your desired diskgroup:
SQL> alter diskgroup add disk
‘’,
‘’,
‘’,
‘’,
.
.
.
‘’;

5) Then wait until the rebalance operation completes:
SQL> select * from v$asm_operation;
SQL> select * from gv$asm_operation;

6) Finally, remove the old disks:
SQL> alter diskgroup drop disk
,
,
,
,
.

;

7) Then wait until the rebalance operation completes:
SQL> select * from v$asm_operation;
SQL> select * from gv$asm_operation;

8) Done, your ASM diskgroups and database have been migrated to the new storage.
Note: Alternatively, we can execute add disk & drop disk statements in one operation,
in that way only one rebalance operation will be started as follow:
SQL> alter diskgroup
add disk ‘‘, .., ‘‘
drop disk , , .., rebalance <#>;
This is more efficient than separated commands (add disk & drop disk statements).