ASMDG on a particular does not go offline if its instances is being used by other database instances (3856450)

Last published : Sep 23, 2026
If you initiate an offline of the ASMDG group on a node which has its ASMInstance being used by one of more DB z resources from the cluster, then the offline would fail and a fault would get reported on both the ASM and DB level.
Workaround: Run the following SQL command to check the ASM DG running on the node:
SQL> select INST_ID,GROUP_NUMBER, INSTANCE_NAME,
DB_NAME, INSTANCE_NAME||':'||DB_NAME client_id from gv$asm_client;
lang=txt lang=txt lang=txt lang=txt lang=txt
INST_ID GROUP_NUMBER INSTANCE_NAME DB_NAME CLIENT_ID
lang=txt lang=txt lang=txt lang=txt lang=txt
3 2 oradb2 oradb oradb2:oradb
lang=txt lang=txt lang=txt lang=txt lang=txt
3 2 oradb3 oradb oradb3:oradb
lang=txt lang=txt lang=txt lang=txt lang=txt
3 2 +ASM3 +ASM +ASM3:+ASM
lang=txt lang=txt lang=txt lang=txt lang=txt
3 1 +ASM3 +ASM +ASM3:+ASM
lang=txt lang=txt lang=txt lang=txt lang=txt
1 2 oradb1 oradb oradb1:oradb
lang=txt lang=txt lang=txt lang=txt lang=txt
1 1 -MGMTDB _mgmtdb -MGMTDB:_mgmtdb
lang=txt lang=txt lang=txt lang=txt lang=txt
1 1 +ASM1 +ASM +ASM1:+ASM
lang=txt lang=txt lang=txt lang=txt lang=txt
4 2 oradb4 oradb oradb4:oradb
8 rows selected.
In the above table:
  • oradb1 is using the ASMInstance 1
  • oradb2 and oradb3 are using ASMInstance 3
  • oradb4 is using ASMInstance 4
Use the following SQL to relocate the ASMpool to another node:
SQL> alter system relocate client 'oradb4:oradb';
System altered.
If the command does not work, please refer Oracle documentation for further information on relocating the client.