Grid version: 11.2.0.4
OS : OEL 6.4
I know that gurus here are not fond of ASMLib. But it is something I have to live with.
I need to reuse the oracleasm Disks I have dropped from Diskgroup X so that I can add these disks to Diskgroup Y.
-- Dropping disks RECO_D7 and RECO_D8
SQL> ALTER DISKGROUP RECO_DG drop disk RECO_D7 ;
Diskgroup altered.
SQL> ALTER DISKGROUP RECO_DG drop disk RECO_D8 ;
Diskgroup altered.
After the above DROP command , v$asm_disk.HEADER_STATUS for the above disks became 'FORMER'
SQL> select name, path, state, mount_status, header_status, total_mb,free_mb from v$asm_disk where HEADER_STATUS != 'MEMBER';
NAME PATH STATE MOUNT_STATUS HEADER_STATUS TOTAL_MB FREE_MB
-------------------- -------------------------- -------- -------------------- -------------------- ---------- ----------
ORCL:RECO_D7 NORMAL CLOSED FORMER 0 0
ORCL:RECO_D8 NORMAL CLOSED FORMER 0 0
To 'clean up' oracleasm disks , this is what I understand from googling.
Step1. # dd if=/dev/zero of=/dev/sdmna1 bs=1024 count=100
Step2. # /etc/init.d/oracleasm deletedisk RECO_D7
-- Now I hope I should be able use the disk partition to create a new oracleasm Disk
Step3. # /etc/init.d/oracleasm createdisk DATA78 /dev/sdmna1
Are my above steps in the correct order ? Or, Should step2 be executed before step1 ? I am a bit confused on why zero padding (dd command) is done before the oracleasm deletedisk command is executed ?