RE: Slightly Urgent ASM Question - Cancel Rebalance operation

From: <Christopher.Taylor2_at_parallon.net>
Date: Wed, 24 Apr 2013 14:28:43 -0500
Message-ID: <F05D8DF1FB25F44085DB74CB916678E8879D9D952C_at_NADCWPMSGCMS10.hca.corpad.net>



Specified as an ADD and DROP in one statement.
GROUP_NUMBER DISK_NUMBER NAME                           PATH                           MOUNT_S HEADER_STATU MODE_ST STATE
------------ ----------- ------------------------------ ------------------------------ ------- ------------ ------- --------
           1           8 DG_CCMNASP1_ARCHIVE_01_0001    /dev/raw/raw112                CACHED  MEMBER       ONLINE  NORMAL
           1           9 DG_CCMNASP1_ARCHIVE_01_0002    /dev/raw/raw113                CACHED  MEMBER       ONLINE  NORMAL
           1          10 DG_CCMNASP1_ARCHIVE_01_0003    /dev/raw/raw114                CACHED  MEMBER       ONLINE  NORMAL
           1          11 DG_CCMNASP1_ARCHIVE_01_0004    /dev/raw/raw115                CACHED  MEMBER       ONLINE  NORMAL
           1          12 DG_CCMNASP1_ARCHIVE_01_0005    /dev/raw/raw116                CACHED  MEMBER       ONLINE  NORMAL
           1          13 DG_CCMNASP1_ARCHIVE_01_0006    /dev/raw/raw117                CACHED  MEMBER       ONLINE  NORMAL
           1           0 DG_CCMNASP1_ARCHIVE_01_0050    /dev/raw/raw70                 CACHED  MEMBER       ONLINE  DROPPING
           1           1 DG_CCMNASP1_ARCHIVE_01_0051    /dev/raw/raw71                 CACHED  MEMBER       ONLINE  DROPPING
           1           2 DG_CCMNASP1_ARCHIVE_01_0052    /dev/raw/raw72                 CACHED  MEMBER       ONLINE  DROPPING
           1           3 DG_CCMNASP1_ARCHIVE_01_0053    /dev/raw/raw73                 CACHED  MEMBER       ONLINE  DROPPING
           1           4 DG_CCMNASP1_ARCHIVE_01_0054    /dev/raw/raw79                 CACHED  MEMBER       ONLINE  DROPPING
           1           5 DG_CCMNASP1_ARCHIVE_01_0055    /dev/raw/raw83                 CACHED  MEMBER       ONLINE  DROPPING
           1           6 DG_CCMNASP1_ARCHIVE_01_0056    /dev/raw/raw84                 CACHED  MEMBER       ONLINE  DROPPING
           1           7 DG_CCMNASP1_ARCHIVE_01_0057    /dev/raw/raw97                 CACHED  MEMBER       ONLINE  DROPPING

Regarding your PS, I know [unfortunately]. It was a stopgap measure and temporary and this storage migration will resolve that.

I talked to the storage folks and was acknowledged that they inadvertently shorted me disks.

Another question, can I run an ADD DISK to add additional DISKS while this operation is in this state?

Any other thoughts are much appreciated!

Chris

From: Bobak, Mark [mailto:Mark.Bobak_at_proquest.com] Sent: Wednesday, April 24, 2013 2:22 PM
To: Taylor Christopher - Nashville; oracle-l_at_freelists.org; Dave.Herring_at_acxiom.com Subject: RE: Slightly Urgent ASM Question - Cancel Rebalance operation

Hi Chris,

Did you just add the new disks, or did you issue a single alter diskgroup command that specified an add and a drop?

What state are the disks in?
select group_number,disk_number,name,path,mount_status,header_status,mode_status,state from v$asm_disk;

If all you did was add new disks, then you should be able to just as easily drop them again, with no harm.

-Mark

PS Not directly related to your question, but all the disks in a given diskgroup should be the same size, or you can run into weird space allocation errors, where there's free space in a DG, but it can't be used, and you'll get out of space errors with free space available.

From: Christopher.Taylor2_at_parallon.net<mailto:Christopher.Taylor2_at_parallon.net> [mailto:Christopher.Taylor2_at_parallon.net] Sent: Wednesday, April 24, 2013 3:15 PM
To: oracle-l_at_freelists.org<mailto:oracle-l_at_freelists.org>; Bobak, Mark; Dave.Herring_at_acxiom.com<mailto:Dave.Herring_at_acxiom.com> Subject: Slightly Urgent ASM Question - Cancel Rebalance operation

We're in the process of migrating existing ASM Disk Groups to a new storage configuration (new disks (metavolumes), same array).

We've done this in DEV/QA and everything went fine.

Now, in Prod, I started the ARCHIVELOG diskgroup migration and discovered that the disks I was given aren't enough for the space I'm currently using.

So, the first thing I did was set the REBALANCE POWER for the operation to 0.

Now v$asm_operation shows no rows.

My Diskgroup in question now shows the below - what I need to know is: Can I now REMOVE the disks I started to add which are RAW112 through RAW117 until I get the right number of disks from storage, or am I in a weird/bad situation?

Thanks!!

DG_DATABASE_NAME_ARCHIVE_01

 /dev/raw/raw112    DG_DATABASE_NAME_ARCHIVE_01_0001            69,044          2,326      3.37

/dev/raw/raw113 DG_DATABASE_NAME_ARCHIVE_01_0002 69,044 2,324 3.37
/dev/raw/raw114 DG_DATABASE_NAME_ARCHIVE_01_0003 69,044 2,326 3.37
/dev/raw/raw115 DG_DATABASE_NAME_ARCHIVE_01_0004 69,044 2,325 3.37
/dev/raw/raw116 DG_DATABASE_NAME_ARCHIVE_01_0005 69,044 2,326 3.37
/dev/raw/raw117 DG_DATABASE_NAME_ARCHIVE_01_0006 69,044 2,327 3.37
/dev/raw/raw70 DG_DATABASE_NAME_ARCHIVE_01_0050 138,097 71,422 51.72
/dev/raw/raw71 DG_DATABASE_NAME_ARCHIVE_01_0051 138,097 71,422 51.72
/dev/raw/raw72 DG_DATABASE_NAME_ARCHIVE_01_0052 138,097 71,412 51.71
/dev/raw/raw73 DG_DATABASE_NAME_ARCHIVE_01_0053 138,097 71,412 51.71
/dev/raw/raw79 DG_DATABASE_NAME_ARCHIVE_01_0054 138,097 71,832 52.02
/dev/raw/raw83 DG_DATABASE_NAME_ARCHIVE_01_0055 69,044 35,717 51.73
/dev/raw/raw84 DG_DATABASE_NAME_ARCHIVE_01_0056 69,044 35,733 51.75
/dev/raw/raw97 DG_DATABASE_NAME_ARCHIVE_01_0057 69,044 35,734 51.76

Chris Taylor
Oracle DBA
Parallon IT&S

--
http://www.freelists.org/webpage/oracle-l
Received on Wed Apr 24 2013 - 21:28:43 CEST

Original text of this message