ASM Rebalance Power

Hi, there,
This is probably a stupid question. I think most of mine are...!
For ASM rebalancing, if we don't specify a POWER value in our ALTER DISKGROUP data REBALANCE statement, it defaults to whatever the value of asm_power_limit is. On our system, this is 4
However, whenever we had to drop a disk from our Exadata machine, we specified the REBALANCE POWER of 11 for the DATA diskgroup to speed things up (we had to…). We left the other two diskgroups at 4 because they were hardly used at the time.
Whenever we replaced the disk in the array, the storage cell picked it up and performed a rebalance. Again, the DATA diskgroup ran at a rebalance power of 11 and the other ran at 4 (the default).
Is there a setting somewhere which overrides the ASM instance’s default (asm_power_limit) for individual diskgroups. I’m worried now that all ASM rebalance operations on that diskgroup will be running at power 11 and causing performance hits to my system…
I’ve tried reading the fine manuals and it seems like the only option is to perform the rebalance itself:
ALTER DISKGROUP data REBALANCE POWER 4;
Not great as I don’t want to kick off a rebalance if I can help it…
Mark

Apparently, the REBALANCE POWER for a diskgroup is the last POWER granted by either a 'ALTER DISKGROUP ... REBALANCE POWER x' statement or by a reading of the spfile. In our case, the REBALANCE POWER for the diskgroup is 11.
In order to reduce this down to the default REBALANCE POWER (asm_power_limit), we have to either make ASM read the SPFILE (either dismount/mount the diskgroup or restart ASM) or we have to issue a new statement. This statement will perform a REBALANCE:
ALTER DISKGROUP data REBALANCE POWER 4;
Hope this helps someone out in the future!

Similar Messages

Difference between rebalance power 0 and rebalance power 6 in asm

Hi ,
What is the difference between the below statements and the impact on the database?
alter diskgroup name1add disk '/dev/ora_asm_disk87' rebalance power 0;
alter diskgroup name2 add disk '/dev/ora_asm_disk88' rebalance power 6;
DB version:11.2.0.2
OS:AIX

user13364377 wrote:
Hi ,
What is the difference between the below statements and the impact on the database?
alter diskgroup name1add disk '/dev/ora_asm_disk87' rebalance power 0;
alter diskgroup name2 add disk '/dev/ora_asm_disk88' rebalance power 6;
DB version:11.2.0.2
OS:AIXpower 0 = DO NOTHING.
power 6 = do stuff
power 11 = do stuff faster than power 6 (consume more I/O and CPU)
In the above example, it will actually rebalance both disk87 and disk88 at the same time.
In this example the rebalance of 88 would wait until disk87 rebalance completes.
alter diskgroup name1add disk '/dev/ora_asm_disk87' rebalance power 6;
alter diskgroup name2 add disk '/dev/ora_asm_disk88' rebalance power 6;

Want to move datafiles, controlfiles, redolog on new ASM Disks (11gR2 RAC)

Hi Guys,
Setup: Two Node 11gR2 (11.2.0.1) RAC on RHEL 5.4
Existing disks are from Old SAN & New Disks are from New SAN.
Can I move all datafiles (+DATA), controlfiles (+CTRL), redolog (+REDO) on new ASM Disks by adding disks in is same Diskgroup & dropping older disks from existing Diskgroup taking advantage of ASM Re-balancing Feature.
1) add required disks in the DATA Diskgroups,
ALTER DISKGROUP DATA ADD DISK
'/dev/oracleasm/disks/NEWDATA3' NAME NEWDATA_0003,
'/dev/oracleasm/disks/NEWDATA4' NAME NEWDATA_0004,
'/dev/oracleasm/disks/NEWDATA5' NAME NEWDATA_0005
REBALANCE POWER 11;
Check rebalance status from v$ASM_OPERATION.
2) When rebalance completes, drop the old disks.
ALTER DISKGROUP DATA DROP DISK
NEWDATA_0000,
NEWDATA_0001
REBALANCE POWER 11;
Check rebalance status from v$ASM_OPERATION.
3) Do it same for Redo log groups & Controlfile Diskgroups.
I hope, I could do this Activity, even if database is Up. is there possibility of Database block Corruption ??? (or is it necessary to perform above steps when database is down)
Would be appreciated, your quick responses on the same.
It's an urgent requirement. Thanks.
Regards,
Manish

Manish Nashikkar wrote:
Hi Guys,
Setup: Two Node 11gR2 (11.2.0.1) RAC on RHEL 5.4
Existing disks are from Old SAN & New Disks are from New SAN.
Can I move all datafiles (+DATA), controlfiles (+CTRL), redolog (+REDO) on new ASM Disks by adding disks in is same Diskgroup & dropping older disks from existing Diskgroup taking advantage of ASM Re-balancing Feature.
1) add required disks in the DATA Diskgroups,
ALTER DISKGROUP DATA ADD DISK
'/dev/oracleasm/disks/NEWDATA3' NAME NEWDATA_0003,
'/dev/oracleasm/disks/NEWDATA4' NAME NEWDATA_0004,
'/dev/oracleasm/disks/NEWDATA5' NAME NEWDATA_0005
REBALANCE POWER 11;
Check rebalance status from v$ASM_OPERATION.
2) When rebalance completes, drop the old disks.
ALTER DISKGROUP DATA DROP DISK
NEWDATA_0000,
NEWDATA_0001
REBALANCE POWER 11;
Check rebalance status from v$ASM_OPERATION.
3) Do it same for Redo log groups & Controlfile Diskgroups.
I hope, I could do this Activity, even if database is Up. is there possibility of Database block Corruption ??? (or is it necessary to perform above steps when database is down)
Would be appreciated, your quick responses on the same.
It's an urgent requirement. Thanks.
Regards,
Manish
Hi Manish,
Yes you can do that by adding new disk to existing diskgroup and delete old diskgroup. The good thing is this can be done online however you need to make sure the rebalance power is meet your business time, higher rebalance power is faster to rebalance to complete however it also will consume more resources
Cheers

How to add and remove storage from ASM at the same time?

Scenario:
I want to drop some disks from asm
1- Add disk to asm -----> rebalance
2- drop disk from asm ----> rebalance
Is there anyway to make this process faster instead of going to rebalancing twice?

I think you could try something like this.....
Add with a power limit of zero and then drop the disks with a powerlimit of 11.
alter system set ASM_POWER_LIMIT=0;
select * from v$asm_operation;
alter diskgroup DBFILE01_GRP
add disk 'ORCL:DB0009', 'ORCL:DB0010', 'ORCL:DB0011', 'ORCL:DB0012';
alter diskgroup DBFILE01_GRP drop disk DB0001, DB0002, DB0003, DB0004;
alter diskgroup DBFILE01_GRP rebalance power 11;
select * from v$asm_operation;

How to increase space in ASM disk groups?

Hi All,
I am a newbie DBA in my team and today morning got a OEM alert that:
Target name=+ASM_ZEUS.techiebros.com
Message=Disk Group DATA requires rebalance because at least one disk is low on space.
Any solution?

To solve it you can run this command: Alter diskgroup ASMDB Add Disk 'here the way of the new disk' Rebalance power 4 WAIT;
After that, you can see through the v$asm_operation;
Read : <http://jarneil.wordpress.com/2008/10/27/asm-rebalance-io-saturation/> or < http://docs.oracle.com/cd/B19306_01/server.102/b14200/statements_1006.htm>

ASM 11.1.0.7.0 and RDBMS client with version (10.2.0.4)

Hi all,
we are trying to expand the space in our ASM. Using a RAC system with two instances.
- ASM Version is 11.1.0.7.0
- RDBMS client with version (10.2.0.4)
Ad the time the ASM is rebalancing the database instances are going down.
- The alert logs from ASM
SQL> ALTER DISKGROUP ORADATA ADD DISK '/dev/mapper/1HITACHI_D60062610068-part1' SIZE 51199 M REBALANCE POWER 2
WARNING: Deprecated privilege SYSDBA for command 'ALTER DISKGROUP ADD/DROP/REBALANCE'
NOTE: Assigning number (2,2) to disk (/dev/mapper/1HITACHI_D60062610068-part1)
NOTE: requesting all-instance membership refresh for group=2
NOTE: initializing header on grp 2 disk ORADATA_0002
NOTE: cache opening disk 2 of grp 2: ORADATA_0002 path:/dev/mapper/1HITACHI_D60062610068-part1
NOTE: requesting all-instance disk validation for group=2
Tue Oct 13 15:12:42 2009
NOTE: disk validation pending for group 2/0x44480376 (ORADATA)
Tue Oct 13 15:12:45 2009
Tue Oct 13 15:12:45 2009
WARNING: RDBMS client (SID1:SID,ÿ) with version (10.2.0.4.0) is not compatible with a pending operation
NOTE: ASM client SID1:SID died unexpectedly.
Alert Logs from DB Instance
ORA-15064: error in comunication with ASM-Instance..
Shutting down instance
My question: Does anyone know if we face a bug ore some configuration issues ?
THX ! Woo

Hy Moo,
My question: Does anyone know if we face a bug ore some configuration issues ?It seems to be some kind of problem in the disk group configuration. You can verify it querying compatibility and database_compatibility fields from v$asm_diskgroup view.
As You should know, there are ASM new features that requires COMPATIBLE.ASM and COMPATIBLE.RDBMS attributes of the ASM diskgroup be set to at least Oracle 11.1. ( Fast Disk Resync is one example of it), maybe You are facing a configuration issue, not hitting a bug.
Hope it helps,
Cerreia

Resize ASM Diskgroup

Hi All,
My exadata quarter rack machine has two asm diskgroups, DATA1 with 5TB and RECO with 3TB.
I'd like to resize RECO to 1TB and DATA1 to 7TB.
I know ALTER DISKGROUP RESIZE command, but my question is about resize RECO volume from 3 to 1 TB: is it supported by Oracle?? Let me know risks /issues with this resize?
Regards.
Giovanni

Ok, thanks.
My idea was:
step 1> resize from ASM by ALTER DISKGROUP RECO RESIZE ALL SIZE xxG REBALANCE POWER 11;
step 2> resize GRIDDISKs of RECO* on each cell for each griddisk by CellCLI> ALTER GRIDDISK griddisk_name size=xxG;
step 3> check griddisk detail for RECO
step 4> check size of a DATA griddisk
step 5> check free space on CELLDISKs
step 6> resize GRIDDISKs of DATA* on each cell for each griddisk by CellCLI> ALTER GRIDDISK griddisk_name size=new_sizeG;
step 7> resize from ASM by ALTER DISKGROUP DATA RESIZE ALL REBALANCE POWER 11;
step 8> check status of all asmdisks using "v$asm_disk"
step 9> check DB alert logs
step 10> check cell alert history on each cell
Now, I'm reading your suggested note #1245494, thanks very much

DB Shutdown While dropping/adding ASM disks

Hi all,
I am using oracle database 10gR2 (10.2.0.3) on AIX 5.3.
I have dropped two large disks from my diskgroup and at the same time i added some small disks to the same diskgroup. Now rebalancing and dropping disks process in in progress and EM is showing that it will take more than 10 hours to comple. Although I have set the rebalance power to 11.
MY question is if I shutdown my database at this point then will it effect my database or on next startup ASM will resume the process??.
For safe side I have executed following query:
ALTER DISKGROUP oradata UNDROP DISKS;
So will there be any impact on database if we reboot our database at this stage??
Any idea???

I have taken the risk and have restarted my database and nothing went wrong. My database is up and rebalancing process has restarted.

Adding 2 disks to existing production ASM disk group - (urgent)

Environment: AIX
ORACLE: 10.2.0.4 RAC ( 2 node)
We want to add 2 disks(/dev/asm_disk65 & /dev/asm_disk66) to existing production ASM diskgroup (DATA_GRP01).
SQL> /
DISK_GROUP_NAME DISK_FILE_PATH DISK_FILE_NAME DISK_FILE_FAIL_GROUP
DATA_GRP01 /dev/asm_disk14 DATA_GRP01_0006 DATA_GRP01_0006
DATA_GRP01 /dev/asm_disk15 DATA_GRP01_0007 DATA_GRP01_0007
DATA_GRP01 /dev/asm_disk13 DATA_GRP01_0005 DATA_GRP01_0005
DATA_GRP01 /dev/asm_disk3 DATA_GRP01_0010 DATA_GRP01_0010
DATA_GRP01 /dev/asm_disk12 DATA_GRP01_0004 DATA_GRP01_0004
DATA_GRP01 /dev/asm_disk11 DATA_GRP01_0003 DATA_GRP01_0003
DATA_GRP01 /dev/asm_disk10 DATA_GRP01_0002 DATA_GRP01_0002
DATA_GRP01 /dev/asm_disk4 DATA_GRP01_0011 DATA_GRP01_0011
DATA_GRP01 /dev/asm_disk1 DATA_GRP01_0001 DATA_GRP01_0001
DATA_GRP01 /dev/asm_disk9 DATA_GRP01_0016 DATA_GRP01_0016
DATA_GRP01 /dev/asm_disk0 DATA_GRP01_0000 DATA_GRP01_0000
DATA_GRP01 /dev/asm_disk7 DATA_GRP01_0014 DATA_GRP01_0014
DATA_GRP01 /dev/asm_disk5 DATA_GRP01_0012 DATA_GRP01_0012
DATA_GRP01 /dev/asm_disk8 DATA_GRP01_0015 DATA_GRP01_0015
DATA_GRP01 /dev/asm_disk2 DATA_GRP01_0009 DATA_GRP01_0009
DATA_GRP01 /dev/asm_disk16 DATA_GRP01_0008 DATA_GRP01_0008
DATA_GRP01 /dev/asm_disk6 DATA_GRP01_0013 DATA_GRP01_0013
[CANDIDATE] /dev/asm_disk65
[CANDIDATE] /dev/asm_disk66
We issue,
ALTER DISKGROUP DATA_GRP01 ADD DISK '/dev/asm_disk65'; name DATA_GRP01_0017 REBALANCE POWER 5;
ALTER DISKGROUP DATA_GRP01 ADD DISK '/dev/asm_disk66'; name DATA_GRP01_0018 REBALANCE POWER 5;
SQL> ALTER DISKGROUP DATA_GRP01 ADD DISK '/dev/asm_disk65' name DATA_GRP01_0017 REBALANCE POWER 5;
ALTER DISKGROUP DATA_GRP01 ADD DISK '/dev/asm_disk65' name DATA_GRP01_0017 REBALANCE POWER 5
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15075: disk(s) are not visible cluster-wide
Node1:
crw-rw---- 1 oracle dba 38, 68 Nov 18 02:33 /dev/asm_disk65
crw-rw---- 1 oracle dba 38, 13 Nov 18 02:53 /dev/asm_disk13
crw-rw---- 1 oracle dba 38, 10 Nov 18 03:00 /dev/asm_disk10
crw-rw---- 1 oracle dba 38, 3 Nov 18 03:00 /dev/asm_disk3
crw-rw---- 1 oracle dba 38, 7 Nov 18 03:00 /dev/asm_disk7
crw-rw---- 1 oracle dba 38, 2 Nov 18 03:00 /dev/asm_disk2
crw-rw---- 1 oracle dba 38, 8 Nov 18 03:00 /dev/asm_disk8
crw-rw---- 1 oracle dba 38, 15 Nov 18 03:00 /dev/asm_disk15
crw-rw---- 1 oracle dba 38, 14 Nov 18 03:00 /dev/asm_disk14
crw-rw---- 1 oracle dba 38, 12 Nov 18 03:00 /dev/asm_disk12
crw-rw---- 1 oracle dba 38, 11 Nov 18 03:00 /dev/asm_disk11
crw-rw---- 1 oracle dba 38, 5 Nov 18 03:00 /dev/asm_disk5
crw-rw---- 1 oracle dba 38, 4 Nov 18 03:00 /dev/asm_disk4
crw-rw---- 1 oracle dba 38, 69 Nov 18 03:39 /dev/asm_disk66
crw-rw---- 1 oracle dba 38, 9 Nov 18 04:39 /dev/asm_disk9
crw-rw---- 1 oracle dba 38, 6 Nov 18 06:36 /dev/asm_disk6
crw-rw---- 1 oracle dba 38, 16 Nov 18 06:36 /dev/asm_disk16
Node 2 :
crw-rw---- 1 oracle dba 38, 68 Nov 15 17:59 /dev/asm_disk65
crw-rw---- 1 oracle dba 38, 69 Nov 15 17:59 /dev/asm_disk66
crw-rw---- 1 oracle dba 38, 8 Nov 17 19:55 /dev/asm_disk8
crw-rw---- 1 oracle dba 38, 7 Nov 17 19:55 /dev/asm_disk7
crw-rw---- 1 oracle dba 38, 5 Nov 17 19:55 /dev/asm_disk5
crw-rw---- 1 oracle dba 38, 3 Nov 17 19:55 /dev/asm_disk3
crw-rw---- 1 oracle dba 38, 2 Nov 17 19:55 /dev/asm_disk2
crw-rw---- 1 oracle dba 38, 10 Nov 17 19:55 /dev/asm_disk10
crw-rw---- 1 oracle dba 38, 4 Nov 17 21:04 /dev/asm_disk4
crw-rw---- 1 oracle dba 38, 12 Nov 17 21:45 /dev/asm_disk12
crw-rw---- 1 oracle dba 38, 14 Nov 17 22:21 /dev/asm_disk14
crw-rw---- 1 oracle dba 38, 15 Nov 17 23:06 /dev/asm_disk15
crw-rw---- 1 oracle dba 38, 11 Nov 17 23:18 /dev/asm_disk11
crw-rw---- 1 oracle dba 38, 9 Nov 18 04:39 /dev/asm_disk9
crw-rw---- 1 oracle dba 38, 6 Nov 18 04:41 /dev/asm_disk6
crw-rw---- 1 oracle dba 38, 16 Nov 18 06:20 /dev/asm_disk16
crw-rw---- 1 oracle dba 38, 13 Nov 18 06:20 /dev/asm_disk13
node1 SQL> select GROUP_NUMBER,NAME,STATE from v$asm_diskgroup;
GROUP_NUMBER NAME STATE
1 DATA_GRP01 MOUNTED
2 FB_GRP01 MOUNTED
SQL> select GROUP_NUMBER,NAME,PATH,HEADER_STATUS,MOUNT_STATUS from v$asm_disk order by name;
GROUP_NUMBER NAME PATH HEADER_STATUS MOUNT_STATUS
1 DATA_GRP01_0000 /dev/asm_disk0 MEMBER CACHED
1 DATA_GRP01_0001 /dev/asm_disk1 MEMBER CACHED
1 DATA_GRP01_0002 /dev/asm_disk10 MEMBER CACHED
1 DATA_GRP01_0003 /dev/asm_disk11 MEMBER CACHED
1 DATA_GRP01_0004 /dev/asm_disk12 MEMBER CACHED
1 DATA_GRP01_0005 /dev/asm_disk13 MEMBER CACHED
1 DATA_GRP01_0006 /dev/asm_disk14 MEMBER CACHED
1 DATA_GRP01_0007 /dev/asm_disk15 MEMBER CACHED
1 DATA_GRP01_0008 /dev/asm_disk16 MEMBER CACHED
1 DATA_GRP01_0009 /dev/asm_disk2 MEMBER CACHED
1 DATA_GRP01_0010 /dev/asm_disk3 MEMBER CACHED
1 DATA_GRP01_0011 /dev/asm_disk4 MEMBER CACHED
1 DATA_GRP01_0012 /dev/asm_disk5 MEMBER CACHED
1 DATA_GRP01_0013 /dev/asm_disk6 MEMBER CACHED
1 DATA_GRP01_0014 /dev/asm_disk7 MEMBER CACHED
1 DATA_GRP01_0015 /dev/asm_disk8 MEMBER CACHED
1 DATA_GRP01_0016 /dev/asm_disk9 MEMBER CACHED
0 /dev/asm_disk65 MEMBER IGNORED
0 /dev/asm_disk66 MEMBER CLOSED
Please guide us with next step, we are running out of space. The disks are added to non-existing group name (group number zero in above query).How to drop the disks and add it again.
Is there query to drop disk with pathname like alter diskgroup <disk group name> drop disk '<path of the disk?'; -> is it right???
Thanks in advance.
Sakthi
Edited by: SAKTHIVEL on Nov 18, 2010 10:08 PM

1. just use one alter diskgroup command, rebalance would be executed just one time
2. on node 2, do you see the disks as on node 1?
select GROUP_NUMBER,NAME,PATH,HEADER_STATUS,MOUNT_STATUS from v$asm_disk order by name;3. try this:
ALTER DISKGROUP DATA_GRP01
ADD DISK '/dev/asm_disk65' name DATA_GRP01_0017,
'/dev/asm_disk66' name DATA_GRP01_0018
REBALANCE POWER 5;

Increasing Size of ASM.....

Expanding the Lun was quite easy. I happen to increase /dev/sdb from 200G to 250G
I then started the ASM instance and issued following command.
alter diskgroup TTGS_GROUP1 resize all size 50000M;
This is so it did not understand the same disk name '/dev/sdb' . it use to say /dev/sdb not in TTG_GROUP1.
I am unable to locate the new space. What could be the reason.
Thanks
Shiva

Hi
Here are the few commands that you can try, I had used these on a Windows box:
C:\Documents and Settings\gurpartap>sqlplus / as sysdba
SQL*Plus: Release 10.1.0.2.0 - Production on Fri May 11 19:57:11 2007
Copyright (c) 1982, 2004, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
Enter value for usr: sys
Enter value for db: +ASM
sys@+ASM>select * from v$instance;
INSTANCE_NUMBER INSTANCE_NAME
HOST_NAME
VERSION STARTUP_T STATUS PAR THREAD# ARCHIVE
LOG_SWITCH_
LOGINS SHU DATABASE_STATUS INSTANCE_ROLE ACTIVE_ST
1 +asm
GURPARTA-MLCJZI
10.1.0.2.0 10-MAY-07 STARTED 0 STOPPED
ALLOWED NO ACTIVE UNKNOWN NORMAL
sys@+ASM>alter diskgroup DGROUP add disk 'c:\asmfiles\disk2';
Diskgroup altered.
sys@+ASM>alter diskgroup DGROUP rebalance power 5;
Diskgroup altered.
sys@+ASM>
ALTER DISKGROUP asm1dg2 RESIZE ALL SIZE 32M;
Can you see the increaased space from Unix in the RAW devices.
Hope this Heps
Regards

How to migrate RAC/ASM 10g to a new SAN on Unix

Hi everybody,
I have an Oracle RAC 10g using ASM on Solaris Sparc 10.
And I need to change my SAN storage for a better.
Somebody can tell me the steps to follow or a Metalink note?
Thanks & regards...

Hi
With ASM your life is simple.. Just add the new disks from new storage to ASM and drop old disks and throttle the reblance operations..
ALTER DISKGROUP <DG> Add disk <from new storage>
ALTER DISKGROUP <DG) drop disk <old disks>
ALTER DISKGROUP <DG> REBALANCE POWER 11;
You can query the V$ASM_OPERATIONS to monitor the rebalance progress. Once all the disks are dropped, you can unplug the old storage from the system.
Similarly, you can use ocrconfig -replace ocr/ocrmirror to migrate the OCR (Online)
Votedisks, you need to bring the cluster down (due to a bug in 10g, online if you are 11)..
# crsctl query css votedisk
# crsctl add css votedisk <new vote disk> /crsctl delete css votedisk <old vote disk>

ASM Disk Migration

HI There,
Im working on an 11.2.0.3 GI and RDBMS running on AIX 7.1
I have a situation where one of the one of the ASM disk groups on a particular cluster consists of 20 disks, 10 of which need to be swapped out for 10 new disks.
As far as I am aware (correct me if im wrong) the following procedure should work, can be done online and should have no impact to any databases using the diskgroup (apart from the asm rebalance):
-Start with 20 disks (lets call them 'disk1 to disk20' allocated to diskgroup '+DISKGROUP_A'
- I have ten new disks (lets call them disk21 - disk30'
- I want to swap out 'disk11 to 'disk20' for new disks 'disk21 to disk30'
- First Add disks 'disk21 to disk30' to ASM diskgroup '+DISKGROUP_A'
- Allow rebalance to finish
- Once rebalance finished drop 'disk11 to disk20' from '+DISKGROUP_A'
- Allow rebalance to finish again
- Confirm that disks 'disk11 to disk20' are now shown as 'FORMER'
- Disks can then physically be removed.
My Question, is there a better way of doing what I am trying to achieve here, the above process worries me a little, simply because Im putting my self totally in the hands of oracle, crossing my fingers and hoping it works.
- Any better suggestions?
- Any suggestions around safeguarding the above approach?
Any opinions would be appreciated
Thanks

Hi
The best way is to allow the ASM to do the migration:
Create the new ASM disks
Add those disks to your ASM diskgroup
Wait to the re balance processes finish
Remove old disks from your diskgroup
Wait to the re balance processes finish
Drop the old ASM disks
Disconnect physical disks
I migrate all the storage (old SAN to new SAN ) for one RAC including OCR_Voting with zero down time, without problems.
This is the post:
OCR_Voting Disk Migration
Regards

Stop running asm rebalancing proecss

Hi,
I'm working on an Oracle Database 11g Release 11.1.0.6.0 - 64bit Production With the Real Application Clusters option.
I added a new disk to a diskgroup, and the rebalacing process started.
Is it possible to stop it, and re-run later manually?
If it's possible, there are some bad side effects of this operation?
Thanks in advance,
Samuel

No this is not possible.
You should have waited adding the disk until it was more convenient, or manually set the rebalance power to e.g. a value of 1 ( one ), so it is not very resource consuming
HTH
FJFranken

Migration of Storage

Hi Gurus,
We are running application on Oracle 10g RAC with ASM storage (NETAPPS) on IBM machine with Windows 2003 64-bit OS. Planning to upgrade the storage, note that the new storage is EMC.
Please kindly help me with moving the database from one storage to other storage.
As per my knowledge below are steps to perform while moving the data files, please clarify or help me accordingly if the steps are not correct.
1) Create DISK Group with NEW Storage ( Can we have different storage for DISK GROUPS???)
2) Mount the Database
3) COPY the DATAFILES using RMAN COPY command to new DISK Group.
4) Switch Datafile to COPY
5) RECOVER Database
6) DELETE old Datafile copy.
7) Open the database.
Are the above steps are correct for migrating data files???????
Also, please guide me to migrate OCR and Voting Disks to the new storage??????

875394 wrote:
Hi Gurus,
We are running application on Oracle 10g RAC with ASM storage (NETAPPS) on IBM machine with Windows 2003 64-bit OS. Planning to upgrade the storage, note that the new storage is EMC.
Please kindly help me with moving the database from one storage to other storage.
As per my knowledge below are steps to perform while moving the data files, please clarify or help me accordingly if the steps are not correct.
1) Create DISK Group with NEW Storage ( Can we have different storage for DISK GROUPS???)
2) Mount the Database
3) COPY the DATAFILES using RMAN COPY command to new DISK Group.
4) Switch Datafile to COPY
5) RECOVER Database
6) DELETE old Datafile copy.
7) Open the database.
Are the above steps are correct for migrating data files???????
Also, please guide me to migrate OCR and Voting Disks to the new storage??????
Though your steps are possible but I would do another method if you want to keep the current diskgroup
1. prepare disks on new storage with same size with current storage disks
2. add new disks from new storage to existing diskgroup
SQL >alter diskgroup <diskgroup name> add disk
‘<new disk on new storage>’ rebalance power 10;
3. wait until the rebalance operation completes, check from v$asm_operation
4. delete old disks from old storage
SQL > alter diskgroup <diskgroup name> drop disk
<old disk> rebalance power 10;
5. see step 3
6. now move the ocr
# > ocrconfig -replace ocr <new disk>
# > ocrconfig -replace ocrmirror <new disk>
7. now move votingdisks
# > crsctl delete css votedisk <OLD_DISK> –force
# > crsctl add css votedisk <NEW_DISK> –force
Hope this helps
Cheers

Question on adding LUNs to disk group

GI version :11.2.0.3.0
Platform : OEL
I need to add 2TB to the following disk group. Each LUN is 100gb in size.
100gb x 20 = 2 Tera Byte. Which means I have to run 20 commands like below
SQL> ALTER DISKGROUP DATA_DG1 ADD DISK '/dev/sdc1' rebalance power 4;Each ALTER DISKGROUP...ADD DISK command's rebalance takes around 30 minutes to complete.
So, this operation will take 10 hours to complete.
ie. 20 x 30 = 600 minutes = 10 hours !!!I have a 3-node RAC. Can I run ALTER DISKGROUP...ADD DISK commands in parallel from each node ? Will ASM instance allow
multiple rebalance operations in a single Disk group ?

http://docs.oracle.com/cd/E11882_01/server.112/e18951/asmdiskgrps.htm
Oracle ASM can perform one disk group rebalance at a time on a given instance. If you have initiated multiple rebalances on different disk groups on a single node, then Oracle processes these operations in parallel on additional nodes if available; otherwise the rebalances are performed serially on the single node. You can explicitly initiate rebalances on different disk groups on different nodes in parallel.
Why do you need to run 20 of these commands??
Can you not just add 20 of the disks in one go:
ALTER DISKGROUP DATADG ADD DISK
'/devices/diska5' NAME disk1,
'/devices/diska6' NAME disk2,
'/devices/diska7' NAME disk3,
...etc
You shouldn't need to manually rebalance as Oracle will automatically do the rebalancing when the configuration changes unless you want to use a non-default value of power as defined by the ASM_POWER_LIMIT parameter. You can run the above command with a rebalance option as well if you you need to do so.

ASM Rebalance Power

Similar Messages

Maybe you are looking for