This content has been marked as final. Show 3 replies
I assume you were using raw devvice for ASM, you can not re-size the raw device.
Since you are using same HDD, not much performance change.
First take Backup of the database. You can do the resize of existing diskgroup provided if you have additional space in Storage. The Steps are
1. resize existing LUN from storage (If you have additional LUNs or Space)
2. Allocate new size from OS
3. In rolling fashion, shutdown ASM instances.
4. Only when all ASM have been recycled, you should resize the disk
Command is below :
1. SQL> select * from v$asm_operation;
2. SQL> alter diskgroup DG1 resize disk <diskgroup> size <value>m;
3. SQL> select * from v$asm_operation;
4. SQL> select group_number G#, disk_number D#, state, redundancy, name, path, total_mb, free_mb, (total_mb - free_mb) used_mb from v$asm_disk order by name;
Then you can check from 'asmcmd' also
You can do that if you use disk partition (eg: On Linux + ASMLIB), then you can create the ASM Disks for your diskgroups.
/dev/sda1 = Partition 1 with ASM HEADER
/dev/sda2 = Partition 2 without ASM (you can add this later)
I would not recommend that, after all the disk is the same so, why not use it full for ASM?