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;

Similar Messages

Error while creating asm disk group:::urgent

i am getting this error though i have given total path in DISK parameter.
SQL> CREATE DISKGROUP dgroup1
2 NORMAL REDUNDANCY
3 FAILGROUP ctlr1
4 DISK 'disk1'
5 FAILGROUP ctlr2
6 DISK 'disk2';
CREATE DISKGROUP dgroup1
ERROR at line 1:
ORA-15018: diskgroup cannot be created
ORA-15031: disk specification 'disk2' matches no disks
ORA-15031: disk specification 'disk1' matches no disks

hi all,
thnx for ur attention i am able to solve the issue by doing the following steps...
[oracle@sierra200 product]$ su - root
Password:
[root@sierra200 root]# losetup /dev/loop1 /u04/app/oracle/product/asmdisks/disk1
[root@sierra200 root]# losetup /dev/loop1 /u04/app/oracle/product/asmdisks/disk2
ioctl: LOOP_SET_FD: Device or resource busy
[root@sierra200 root]# losetup /dev/loop1 /u04/app/oracle/product/asmdisks/disk1
ioctl: LOOP_SET_FD: Device or resource busy
[root@sierra200 root]# losetup /dev/loop2 /u04/app/oracle/product/asmdisks/disk2
[root@sierra200 root]# vi /etc/sysconfig/rawdevices
# raw device bindings
# format: <rawdev> <major> <minor>
# <rawdev> <blockdev>
# example: /dev/raw/raw1 /dev/sda1
# /dev/raw/raw2 8 5
/dev/raw/raw1 /dev/loop1
/dev/raw/raw2 /dev/loop2
[root@sierra200 root]# /etc/init.d/rawdevices start
Assigning devices:
/dev/raw/raw1 --> /dev/loop1
/dev/raw/raw1: bound to major 7, minor 1
/dev/raw/raw2 --> /dev/loop2
/dev/raw/raw2: bound to major 7, minor 2
done
[root@sierra200 root]# chown oracle:dba /dev/raw/raw1
[root@sierra200 root]# chown oracle:dba /dev/raw/raw2
[root@sierra200 root]# chmod 660 /dev/raw/raw1
[root@sierra200 root]# chmod 660 /dev/raw/raw2
[root@sierra200 root]# exit
logout
shut the instance and make the disk string as '/dev/raw/raw*'
and then create spfile from pfile. and then nomount the instance.
SQL> CREATE DISKGROUP dgroup1
2 NORMAL REDUNDANCY
3 FAILGROUP ctlr1
4 DISK '/dev/raw/raw1'
5 FAILGROUP ctlr2
6 DISK '/dev/raw/raw2';
Diskgroup created.
SQL> select name, state,total_mb,free_mb,path from v$ASM_DISK;
NAME STATE TOTAL_MB FREE_MB
PATH
DGROUP1_0001 NORMAL 100 50
/dev/raw/raw2
DGROUP1_0000 NORMAL 100 50
/dev/raw/raw1
Regards,
Sravan

Adding disk to existing disk group in ASM on the windows 2003 server.

Guys,
Can someone please share some opinions of adding an extra disk to an existing disk group ( DG_FRA ) in ASM on a windows 2003 server ( like any issues when bringing db backup ). This is a production database and I want to be careful , so that I don't have any issues with the database. Existing DG_FRA is 550GB ( size of the image copy is 325GB ),recently we have been running heavy loads and this is filling up the archive logs and forcing us to take incremental backups couple of times before deleting the archive logs. As a result of this we decided to add an extra 200GB so that we don't have to do this backups frequently during the day. Storage is on EMC SAN and the database is in 11G.
Thanks for all your help.

There will not be any issues..
stamp the disk and then add the disk.
You can also follow this approach -
stamp the disk.
create a new group and then add a datafile in this new group for the existing tablespace.

Re-installation with existing product code/disk but no disk drive.

I have a new laptop and need to re-register my Photoshop C6 student and teachers edition, can I do this with my existing product code?
Also if it is possible, how do I then re-install Photoshop with no disk drive? (I originally just popped the disk in and entered my product code.)
(Additional information: Both my laptop and Photoshop are for Windows.)

Hello,
if you are able to do that, you should deactivate (Help -> Deactivate) the Adobe software before you lose the machine to it being reset. You will still use the same serial number to activate the soiftware when you get the application(s) reinstalled.
If you need any help with activation you can contact Adobe Support directly by chat or phone.
Here is a link to a page with options to help make contact: (Contact Support – Download and Installation)
http://www.adobe.com/support/download-install/supportinfo/
Hans-Günter

Adding quorum disk causing wasted space?

Hi,
Any idea whether this is a bug or an expected behavior?
Seeing this with ASM 11.2.0.4 and 12.1.0.4
Have a Normal redundancy disk group (FLASHDG22G below) with two disks of equal size. With no data on the disk group the Usable_file_MB is equal to the size of one disk, as expected.
But if I add a small quorum disk to the disk group, the Usable_file_MB decreases to 1/2 of the disk size. So, half of the capacity is lost.
Thoughts?
[grid@symcrac3 ~]$ asmcmd lsdsk -k
Total_MB Free_MB OS_MB Name        Failgroup Failgroup_Type Library Label UDID Product Redund   Path
   20980    20878 20980 SYMCRAC3_A FG1        REGULAR         System                         UNKNOWN /dev/symcrac3-a-22G
     953      951    953 QUORUMDISK FGQ        QUORUM          System                         UNKNOWN /dev/symcrac3-a-quorum
   20980    20878 20980 SYMCRAC4_A FG2        REGULAR         System                         UNKNOWN /dev/symcrac4-a-22G
[grid@symcrac3 ~]$ asmcmd lsdg
State    Type    Rebal Sector Block       AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files Name
MOUNTED NORMAL N         512   4096 1048576     42913    42707            20980           10388              0             N FLASHDG22G/

There are two separate issues:
1) ASMCMD silently fails to add quorum failure groups. Adds them, but as regular failure groups.
2) Even if a quorum failure group is added with SQLPlus, the space is still lost – I have just confirmed it. And it doesn’t matter whether I add a quorum disk to an existing group or create a new group with a quorum disk.
For #2 here is the likely source of the problem. Usable_File_MB = (FREE_MB – REQUIRED_MIRROR_FREE_MB ) / 2.
REQUIRED_MIRROR_FREE_MB is computed as follows (per ASM 12.1 user guide):
–Normal redundancy disk group with more than two failure groups
   The value is the total raw space for all of the disks in the largest failure group. The largest failure group is the one with the largest total raw capacity. For example, if each disk is in its own failure group, then the value would be the size of the largest capacity disk.
Instead, it should be "with more than two regular failure groups".
With just two failure groups it is not possible to restore full redundancy after one of them fails. So, REQUIRED_MIRROR_FREE_MB = 0 in this case.
Also REQUIRED_MIRROR_FREE_MB should remain 0 even when there are three failure groups if one of them is a quorum failure group. But the logic seems to be broken here.

How to add ASM Disk to Disk Group that is shown as MEMBER?

HI,
We have a Production Oracle RAC on HP-UX. We have Two Disk Groups one for Arcive (ARC_DISK) and other for Database(DATA_DISK).
Today I wanted to add another 200 GB of Disk Space to the DATA_DISK Group.
I opened DBCA and could not find the new disk in the 'Show Candidates' option. But after the Unix admin changed the ownership and permission of the Disk, it was shown in 'Show Candidates' option. I selected this Disk and continued but got an error later as we didnt change the ownership and permission from the 2nd Unix server. After doing this, , when I open DBCA to add disk, nothing is shown in 'Show Candidates' option but when we click on 'Show All', the new disk is listed as MEMBER (header status) but not allocated to any Disk Group.
I would like to know how to allocate this Disk (which is already shown as MEMBER) to the DATA_DISK - ASM diskgroup. This is a production database system.
Rgds,
Thiru

user1983888 wrote:
Hi,
Due to huge difference in Disk Size which I am trying to add to the existing Disk Group which has 1024 GB of Disk, would it be a better idea to create a new Disk Group with 200g GB Disk? Will this command work as the header_status is already MEMBER?
SQL>CREATE DISKGROUP DATA_DISK1
EXTERNAL REDUNDANCY
DISK 'disk path';
Thanks.Yes, you can create new diskgroup (DATA_DISK1). Just make sure all datafile in DATA_DISK autoextend off, then create all your new datafile to the new diskgroup DATA_DISK1. The command will not work as the header_status is MEMBER. You'll receive ORA-15018 & ORA-15033 error. As I mentioned before, you need to use FORCE option or format the disk using dd* command before perform above command.
1st Option : (Format the raw disk using dd command creating new diskgroup. Header_status MEMBER -> CANDIDATE). E.g.
1. dd if=/dev/zero of=/dev/rdsk/c2t1d0 bs=8192 count=1000 //any rac nodes
2. # chown oracle:oinstall /dev/rdsk/c2t1d0 //perform on both node. This apply if using LVM or direct access to raw
3. SQL> create diskgroup data_disk1 external redundancy disk '/dev/rdsk/c2t1d0'; //any RAC node in ASM instance
4. SQL> alter diskgroup data_disk1 mount; //try to mount on the other node
2nd Option : (Using FORCE option when creating the new diskgroup. Header_Status = MEMBER)
1. # chown oracle:oinstall /dev/rdsk/c2t1d0 //perform on both node. This apply if using LVM or direct access to raw
2. SQL> create diskgroup data_disk1 external redundancy disk '/dev/rdsk/c2t1d0' force; //any RAC node in ASM instance
3. SQL> alter diskgroup data_disk1 mount; //try to mount on the other node
Just be careful when using FORCE option or DD command. If you perform this operation on existing ASM disk groups disk, it may destroy existing disk groups.

Cleaning up ASM disk group after failed rman duplicate session?

I am using rman duplicate to create a clone of a production database. The rman duplicate failed in phase 1 (retoration of datafiles) and my datafile are being restored to an ASM diskgroup.
I read in the metalink note Manual Completion of a Failed RMAN Duplicate [ID 360962.1] the following...
Note : From 10g onwards, if duplicate failed during step 1, which is the restore of datafiles, it is probably best to restart the duplicate process. Any files that have already been restored will be skipped and the duplicate process can continue without manual intervention
So I followed the advice in the note and started the rman duplcate script over again from the beggining. I am hoping it will have the intelligence to skip any files that have already been restored but if it is not since this is 10.1.0.3 and I cannot use the asmcmd command to connect to the ASM instance to delete any files that have been created then how can I delete and of the files since the database instance never got created correctly and cannot open?
Any thought on how I can now cleanup the files in the ASM disk group? Also, has anyone started an rman duplicate again after it has previously failed and did it actually skip the files that are already there as stated in the metalink note?
Thanks.

Unfortunately the v$asm_file does not have the entire file name or path it just gives you the follwing...
SQL> desc v$asm_file
Name Null? Type
GROUP_NUMBER NUMBER
FILE_NUMBER NUMBER
COMPOUND_INDEX NUMBER
INCARNATION NUMBER
BLOCK_SIZE NUMBER
BLOCKS NUMBER
BYTES NUMBER
SPACE NUMBER
TYPE VARCHAR2(64)
REDUNDANCY VARCHAR2(6)
STRIPED VARCHAR2(6)
CREATION_DATE DATE
MODIFICATION_DATE
This really stinks I wish I didn't have to work with 10gr1 at all but the database I am trying to move to a ew server and new storage is running this version and we did not want to upgrade the existing database first before attempting the migration because it is reliant upon tape backups which I do not have alot of confidence in...

Error while creating asm disk group

i am trying to convert my database SRAVAN as an ASM instance.
so do i need to set ORACLE_SID=+ASM???? r else it wil be SRAVAN??
I WAS ENDED UP WITH FOLLOWING ERRORS WHILE CREATING DISK GROUP.
guyz please do help me
SQL> CREATE DISKGROUP dgroup1
2 NORMAL REDUNDANCY
3 FAILGROUP ctlr1
4 DISK '/u04/app/oracle/product/asmdisks/disk1'
5 FAILGROUP ctlr2
6 DISK '/u04/app/oracle/product/asmdisks/disk2';
CREATE DISKGROUP dgroup1
ERROR at line 1:
ORA-15018: diskgroup cannot be created
ORA-15031: disk specification '/u04/app/oracle/product/asmdisks/disk2' matches
no disks
ORA-15025: could not open disk '/u04/app/oracle/product/asmdisks/disk2'
ORA-15059: invalid device type for ASM disk
Linux Error: 32768: Unknown system error
Additional information: 42
Additional information: -1073785968
ORA-15031: disk specification '/u04/app/oracle/product/asmdisks/disk1' matches
no disks
ORA-15025: could not open disk '/u04/app/oracle/product/asmdisks/disk1'
ORA-15059: invalid device type for ASM disk
Linux Error: 32768: Unknown system error
Additional information: 42
Additional information: -1073785968
[oracle@sierra200 dbs]$ cd /u04/app/oracle/product/asmdisks
[oracle@sierra200 asmdisks]$ ls -ltr
total 205008
-rwxrwxrwx 1 oracle oinstall 104857600 Jul 27 11:42 disk1
-rwxrwxrwx 1 oracle oinstall 104857600 Jul 27 11:47 disk2
Thanks & Regards
Sravan Dalavai

Looks like you are asking ASM to use plain files. Have you used the Device Loopback (losetup) a d made the emulate raw devices?
http://www.idevelopment.info/data/Oracle/DBA_tips/Automatic_Storage_Management/ASM_20.shtml

ASM Disk Sizes in a Disk Group

I have a Diskgroup that contains one ASMDisk that is 500gb. It needs to grow and my question is - Does the next disk added to the group need to be of the same size?
For example -
ASM_Disk1 = 500gb and is in ASM_Diskgrp1
ASM_Disk2 - 250gb >> can it be added to ASM_Diskgrp1
There is concern about balancing, etc. done by ASM
Wondering what experiences anyone has had with this?
Thanks!

Hi,
It's not mandatory, You can use disks with diferent sizes, but is extremally recomended that You put disks with the same size in a disk group.
you'd better use disks with the same storage capacity and performance.
The main reason is that ASM balances the I/O from all disks in a disk group due to this, put disks with the same same storage capacity and performance helps to improve the I/O and storage efficiently within the ASM disk group.
Regards,
Cerreia

Can The ASM Disk Header and Disk Group Be Renamed?

I have a requirement to mount multiple SAN clones (EMC Symclone) of a production ASM instance on the same development server. RMAN is too slow to be an option, unless I find a white paper explaining any way to make RMAN perform a clone faster than the SAN.
The default response is normally, "Do your clone to dedicated hardware." However, that answer is not an option for obvious financial reasons, especially since I am working with a RAC environment with ~10 development and test environments.
The only way to do this (that I can think of) is to rename the disk header and probably the disk group prior to making it available to the ASM instance.
I have heard that Oracle has come up with an undocumented solution for one or more businesses. I believe it has something to do with the kfed library located in $ORACLE_HOME/rdbms/lib.
Has anyone out there managed to do this? If so, can you share your solution or point me in the right direction?
I know I am not the only one out there looking for a solution to this issue...
Thanks in advance.

This is absolutely possible. Can be done via kfed. I never found the answer searching the net and had to figure it out. Here it is in hopes that it helps someone else. DISCLAIMER.... If you screw up your disks don't blame me. If you have any questions about this you can email me: [email protected]
The procedure is basically this:
- compile kfed
- dump the disk header with kfed
- Modify the dump file
- write the dump back to the disk header.
** Changing ANYTHING other than the diskgroup name will render your disks useless.
Here is a script to do the work for you:
for file in `ls /dev/vx/rdsk/as1_pccdw/asmdata*`
do
echo "Processing DATA disk $file ..."
search=ASCDW_DATA
replace=AS1CDW_DATA
newlength=`echo $replace | wc -m`
let newlength=$newlength-1
shortname=`echo $file | cut -f 6 -d /`
kfed op=read dev=$file | sed -e '24,24s/ '$search' / '$replace' /' -e '24,24s/length=.*/length='$newlength'/' > /tmp/$shortname.kfed
kfed op=write dev=$file text=/tmp/$shortname.kfed CHKSUM=YES
done
for file in `ls /dev/vx/rdsk/as1_pccdw/asmredo*`
do
echo "Processing REDO disk $file ..."
search=ASCDW_REDO
replace=AS1CDW_REDO
newlength=`echo $replace | wc -m`
let newlength=$newlength-1
shortname=`echo $file | cut -f 6 -d /`
kfed op=read dev=$file | sed -e '24,24s/ '$search' / '$replace' /' -e '24,24s/length=.*/length='$newlength'/' > /tmp/$shortname.kfed
kfed op=write dev=$file text=/tmp/$shortname.kfed CHKSUM=YES
done
Edited by: user4630111 on Nov 10, 2008 6:03 PM

EM Alert: Warning:+ASM Disk Group requires rebalance

Environment:
O.S Version : HP-UX B.11.31 U ia64
Oracle DB Version : 11.2.0.3.0 , Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
Database files are on : ASM Disk Group
It is about the ASM Diskgroup low disk space alert by Oracle Enterprise Manager.
Message=Disk Group DG_FLASH_01 requires rebalance because at least one disk is low on space.
Metric=Disk Minimum Free (%) without Rebalance
Metric value=18.961548
Disk Group Name=DG_FLASH_01
Severity=Warning
Target Name=+ASM_dbsrver.siva.com
Target type=Automatic Storage Management
There is only 1 LUN assigned to this diskgroup +DG_FLASH_01_.
We have a Oracle Enterprise Manager Grid Control Job MN_DBSRVR_DEL_ARCHIVELOGS runs every 12 hours by 1 AM and again at 1PM daily. It cleans-up the archivelogs older than 3 days old. The FLASH diskgroup is continuously being written with new files for both archivelogs and flashback logs.
If there was multiple disks and a vast difference between the files on the different LUNs then a rebalance would be good to run.
How to address such recurring alert of " *Disk Group DG_FLASH_01 requires rebalance because at least one disk is low on space*. " with _only one LUN on the +ASM Diskgroup_?

As I stated earlier there is only one disk on this diskgroup
DISK_NUMBER      OS_MB   TOTAL_MB    FREE_MB NAME                           PATH
          0      65536      65536      12995 DG_FLASH_01_0000        /devasm/gc/ora_asm_gc_b03_a14_d10_08_36
          0      65536      65536      43064 DG_DATA_01_0000         /devasm/gc/ora_asm_gc_b03_a13_d12_08_35So disk REBALANCE not required
Edited by: Sivaprasad S on Feb 14, 2013 11:46 PM

Pros/Cons for a Seperate ASM Archivelog Disk Group

We have a non-ASM best practice of having our archivelogs on their own filesystem. When there is a major problem that fills up this space the datafiles (separate filesystem) themselves are not affected and the backup area used by RMAN (separate filesystem) is fully functional to perform archivelog sweeps.
My DBA team and I have the same concern about having the archivelogs in the FRA along with backups, etc., in the ASM. We are proposing a third disk group just for archivelogs. Also a best practice of always having at least 1 spare disk available that can be added to a disk group in an emergency.
Is there a reason why this is not a good idea or unnecessary? My team is new to ASM and I don't pretend to understand all the real world intracies of Oracle managing the FRA space/archivelogs/rman backups/etc.Thanks for any insight you can offer.

I have read and am quite aware of Oracle's recommendations and have been an Oracle DBA since the venerable 7.0.16 release. In fact I have read through some 20 or so related Oracle white papers concerning ASM. However, in the 24 years I have been working with databases I am also well aware things don't always go as planned. You will fill up a disk group eventually whether that is from unexpectedly high data activity, human error, monitoring being down or any number of possibilities.
So if we make the assumption that the FRA disk group will be out of space due to excessive numbers of archivelogs and/or RMAN retention widow and backup growth problems how do we quickly solve the issue while my prod DB is unavailable? Ah the real world ... If archivelogs and backups are in the FRA I really only have three choices, 1. add a disk to the disk group if I have one, or 2. manually delete files thus potentially impacting recoverability or 3. possibly temporarily reducing my RMAN recovery window to allow RMAN to clean out "old" backup sets (thus impacting my SLA recovery window. Yes there are probably other variations on these also.
Therefore, we are proposing having a best practice of a spare disk available and a seperate disk group for archivelogs so we have two potential methods to recover from this scenario. Now back to the original question, is there a reason why a seperate disk group for archivelogs is not a good idea or unnecessary?
Thanks

Question about using mixed size disk groups with ASM

I support a 10g RAC cluster running 10.2.0.3 and using ASM. We currently have a data disk group that is 600 Gb in size, made up of 3 individual 200 Gb raw disk devices. The RAC cluster is running on an IBM pSeries server using AIX 5.3
I need to add more space, but the system adminstrator can only give me 100 Gb in the new raw device. What will be the impact, if any, of adding this smaller raw disk device into the same ASM data disk group? I understand that ASM tries to "balance" the overall usage of each raw device. Will ASM still work okay, or will it be constantly trying to rebalance the disk group because the one raw device is only half the size of the other three? Any help and advice given will be greatly appreciated. Thank you!

I need to add more space, but the system adminstrator can only give me 100 Gb in the new raw device. What will be the impact, if any, of adding this smaller raw disk device into the same ASM data disk group? I understand that ASM tries to "balance" the overall usage of each raw device. Will ASM still work okay, or will it be constantly trying to rebalance the disk group because the one raw device is only half the size of the other three? Any help and advice given will be greatly appreciated. Thank you!Hi ,
There will be no impact and ASM will automatically balance the things.
Also check :
ASM Technical Best Practices [ID 265633.1]
Regards
Rajesh

How reInstall Gride Infrastructure and Use old ASM disk groups

<pre>Hello to all
I installed Grig Infrastructure 11gR2 on a standalone server (OS is Linux)
and I configured ASM and my database created on ASM
Conceive that my OS disk corrupted and OS doesn't start and the Gride Home is on that disk,
and I have to install OS again
My ASM disks are safe , Now how can I install Grig Infrastructure again somehow that it can use previous ASM disks
and disk groups and I don't oblige to create my database again ?
In the step 2 of installing Gride Infrastructure it has four options
<pre>
1.Install and configure Oracle Grid Infrastructure for a Cluster
2.Configure Oracle Grid Infrastructure for a Standalone Server
3.Upgrade Oracle Gride Infrastructure or Oracle Automatice Storage Management
4.Install Oracle Gride Infrastructure Software Only
</pre>
If I select the option 2 it wants to create a disk group again
I guess that I need to select option 4 and then do some configuration but I don't know what I must configure
Do you know answer of my question , if yes please explain it's stages
Thank you so much
</pre>

Hi,
no you are not obliged to recreate your database again. However there is a small flaw in the installation procedure, which does not make it 100% easy...
When you installed the Oracle Restart (Standalone GI), your ASM diskgroup will contain the SPFILE of the ASM instance. And this is exactly the small flaw you will be encountering. So you have 2 options for "recovery":
1.) Do a software only install (4), and run roothas.pl. This however will not create any ASM entries. You would have to add it manually (using srvctl) and you can specify the ASM Spfile with the srvctl command. Problem here is however to have to know where your ASM spfile has been. If you have a backup of your OLR and a backup of the GPNP profile, this might be easier to find out.
2.) Do a new installation (2) and configure a new diskgroup (with a "spare" disk or small lun and a new name), that Oracle restart creates ASM instance and the new ASMSpfile for you.
Then you can simply mount the diskgroup containing your database additionally. You then shoudl however move your new ASMSpfile to the new diskgroup (or simply exchange it with the existing one). In this case it is easier to find out where it was - however you will need a spare (though small) LUN for the new spfile (temporarily, until you exchange it).
In either case after you have your ASM instance back (and access to your old diskgroup), you have to reregister your database and services - if you do not have an OLR backup.
Again => It is doable and you can simply mount the ASM diskgroup containing your database. However I suggest you try this one time to know what really needs to be done in this case.
Regards
Sebastian

Standby Database ASM Disk Groups

Hi Guys
I wonder if anyone can tell me - does a standby database have to have an identical configuration for its ASM Disk Groups?
My production database has two disk groups, one for data and the other for temp. Can I get away with a single diskgroup in my standby database or would I need two of the same name as the production database?
Cheers
Simon

Hi Saml
I have been busy googling at the same time as discussing this and it would appear that it will use the db_file_name_convert:
http://asanga-pradeep.blogspot.com.au/2012/07/11gr2-standalone-data-guard-with-asm.html
The link above shows the output of someones RMAN session where the OMF names are changed automatically. Problem is that some people are recommending that the parameter not be used, so now I am really confused!
I think I will try the parameter, if it doesnt work or the duplicate fails I will drop the temp table space in production and then do the duplicate, then recreate the temp tablespace. I can do that because there will be no one on the system on Sunday when I do it.
Thanks again for your help - I will let you know how it goes.
Ragards
Simon

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

Similar Messages

Maybe you are looking for