|
SQL> drop diskgroup data;
drop diskgroup data
*
ERROR at line 1:
ORA-15039: diskgroup not dropped
ORA-15073: diskgroup DATA is mounted by another ASM
instance
|
If you are not able to drop a diskgroup, and ORA-15039 is returned along
with ORA-15039: diskgroup not dropped,
it means the diskgroup needs to be dismounted on all instances except current
instance where you are issuing DROP DISKGROUP command.Following command shows
that diskgroup DATA that we want to drop is mounted by all instances.
|
$crsctl stat res -t
…
…
…
ora.DATA.dg
ONLINE ONLINE myhostdb1
ONLINE ONLINE myhostdb2
ONLINE ONLINE myhostdb3
…
…
…
SQL> select name,state, inst_id from gv$asm_diskgroup where name='DATA';
NAME STATE INST_ID
------------------------------ ----------- ----------
DATA MOUNTED 1
DATA MOUNTED 2
DATA MOUNTED 3
|
Now you have to ways to dismount a diskgroup. Either log into all other instances one my one and dismount the diskgroup as follows.
|
SQL> alter diskgroup DATA dismount;
|
Or use crsctl from one node to dismount/stop the diskgroup (services) from all other instances.
|
$ crsctl stop resource ora.DATA.dg -n myhostdb2
CRS-2673: Attempting to stop 'ora.DATA.dg' on
'myhostdb2'
CRS-2677: Stop of 'ora.DATA.dg' on 'myhostdb2'
succeeded
$ crsctl stop resource ora.DATA.dg -n myhostdb3
CRS-2673: Attempting to stop 'ora.DATA.dg' on
'myhostdb3'
CRS-2677: Stop of 'ora.DATA.dg' on 'myhostdb2'
succeeded
SQL>select name,state, inst_id from
gv$asm_diskgroup where name='DATA';
NAME STATE INST_ID
------------------------------ ----------- -----------------------
DATA MOUNTED 1
DATA
DISMOUNTED 2
DATA
DISMOUNTED 3
|
Now diskgroup should drop
without any error.
|
SQL> drop diskgroup data;
|
No comments:
Post a Comment