Skip to Main Content

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

ASM Failgroup understanding problem / diskgroup forced dismount

MarcelDBAJun 24 2019 — edited Jul 25 2019

Hello @all,

Oracle Version 12.2.0.1

one question to asm failgroups.

I build a dg with normal redundancy.

First with only one disk in every failgroup. When  one of the disks is missing /failing , all runs fine. DG ist still mountet.

So now i have build a dg with two failgroups, each with two disks.

Now i force a failing disk in one of the failgroups. As i read about failgroups, the failure of one failgroup is accepted.

But in my case asm dismount the dg:

SQL> select name, GROUP_NUMBER,TYPE, state from v$asm_diskgroup;

NAME                           GROUP_NUMBER TYPE   STATE

------------------------------ ------------ ------ -----------

DATA                                      1 NORMAL MOUNTED

OCR                                       3 NORMAL MOUNTED

LOG                                       2 NORMAL MOUNTED

SQL> select DISK_NUMBER,NAME,MOUNT_STATUS,HEADER_STATUS,OS_MB,TOTAL_MB,FAILGROUP,PATH from v$asm_disk where group_number = 2;

DISK_NUMBER NAME                           MOUNT_S HEADER_STATU      OS_MB   TOTAL_MB FAILGROUP                      PATH

----------- ------------------------------ ------- ------------ ---------- ---------- ------------------------------ ------------------------------

          4 LOGB1                          CACHED  MEMBER            12288      12288 DATASTO2                       /dev/ASM-LOGB1

          3 LOGA2                          CACHED  MEMBER            12288      12288 DATASTO1                       /dev/ASM-LOGA2

          0 LOG_0000                       CACHED  MEMBER            12288      12288 DATASTO2                       /dev/ASM-LOGA1

          1 LOG_0001                       CACHED  MEMBER            12288      12288 DATASTO1                       /dev/ASM-LOGB2

SQL> select DISK_NUMBER,NAME,MOUNT_STATUS,HEADER_STATUS,OS_MB,TOTAL_MB,FAILGROUP,PATH from v$asm_disk where group_number = 2;

no rows selected

SQL> select name, GROUP_NUMBER,TYPE, state from v$asm_diskgroup;

NAME                           GROUP_NUMBER TYPE   STATE

------------------------------ ------------ ------ -----------

LOG                                       0        DISMOUNTED

DATA                                      1 NORMAL MOUNTED

OCR                                       3 NORMAL MOUNTED

Here the alert log from asm:

2019-06-24T22:08:49.746346+02:00

WARNING: Write Failed. group:2 disk:3 AU:1 offset:4190208 size:4096

path:/dev/ASM-LOGA2

         incarnation:0xf0f0e962 asynchronous result:'I/O error'

         subsys:System krq:0x7f1b4df37060 bufp:0x7f1b4de28000 osderr1:0x69b5 osderr2:0x0

         IO elapsed time: 0 usec Time waited on I/O: 0 usec

WARNING: Hbeat write to PST disk 3.4042320226 in group 2 failed. [2]

2019-06-24T22:08:49.782417+02:00

NOTE: checking PST: grp = 2

2019-06-24T22:08:49.782906+02:00

GMON checking disk modes for group 2 at 36 for pid 36, osid 15027

2019-06-24T22:08:49.785091+02:00

ERROR: no read quorum in group: required 1984286416, found 1 disks

2019-06-24T22:08:49.785648+02:00

NOTE: checking PST for grp 2 done.

NOTE: initiating PST update: grp 2 (LOG), dsk = 3/0xf0f0e962, mask = 0x6a, op = clear mandatory

2019-06-24T22:08:49.786222+02:00

GMON updating disk modes for group 2 at 37 for pid 36, osid 15027

2019-06-24T22:08:49.788467+02:00

ERROR: no read quorum in group: required 1984286416, found 1 disks

2019-06-24T22:08:49.816649+02:00

NOTE: cache dismounting (not clean) group 2/0xC25019A7 (LOG)

2019-06-24T22:08:49.818646+02:00

ERROR: no read quorum in group: required 1984286416, found 1 disks

2019-06-24T22:08:49.818802+02:00

ERROR: Could not read PST for grp 2. Force dismounting the disk group.

2019-06-24T22:08:49.819627+02:00

NOTE: messaging CKPT to quiesce pins Unix process pid: 15029, image: oracle@oras1 (B001)

2019-06-24T22:08:49.820126+02:00

NOTE: halting all I/Os to diskgroup 2 (LOG)

2019-06-24T22:08:49.821407+02:00

NOTE: LGWR doing non-clean dismount of group 2 (LOG) thread 1

NOTE: LGWR sync ABA=19.149 last written ABA 19.149

2019-06-24T22:08:49.822311+02:00

NOTE: initiating dirty detach from lock domain 2

2019-06-24T22:08:49.861760+02:00

WARNING: Offline of disk 3 (LOGA2) in group 2 and mode 0x7f failed on ASM inst 1

2019-06-24T22:08:49.863582+02:00

ERROR: ORA-15130 in COD recovery for diskgroup 2/0xc25019a7 (LOG)

ERROR: ORA-15130 thrown in RBAL for group number 2

2019-06-24T22:08:49.864508+02:00

Errors in file /u01/app/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_rbal_5503.trc:

ORA-15130: diskgroup "LOG" is being dismounted

2019-06-24T22:08:50.049521+02:00

ASM Health Checker found 1 new failures

2019-06-24T22:08:50.143149+02:00

List of instances (total 1) :

1

My inst 1

2019-06-24T22:08:50.144482+02:00

Dirty detach reconfiguration started (new ddet inc 1, cluster inc 2)

Global Resource Directory partially frozen for dirty detach

dirty detach - domain 2 invalid = TRUE

0 GCS resources traversed, 0 cancelled

2019-06-24T22:08:50.174914+02:00

Dirty Detach Reconfiguration complete (total time 0.0 secs)

2019-06-24T22:08:50.217855+02:00

freeing rdom 2

2019-06-24T22:08:50.238249+02:00

WARNING: dirty detached from lock domain 2

NOTE: CKPT released recovery enqueue for thread 1 group 2 (LOG)

2019-06-24T22:08:50.245286+02:00

NOTE: cache dismounted group 2/0xC25019A7 (LOG)

NOTE: cache deleting context for group LOG 2/0xc25019a7

2019-06-24T22:08:50.247775+02:00

SQL> alter diskgroup LOG dismount force /* ASM SERVER:3260029351 */

2019-06-24T22:08:52.808395+02:00

WARNING: Read Failed. group:2 disk:3 AU:1 offset:0 size:4096

path:/dev/ASM-LOGA2

         incarnation:0xf0f0e962 synchronous result:'I/O error'

         subsys:System krq:0x7f1b4df79770 bufp:0x7f1b4df39000 osderr1:0x69b5 osderr2:0x0

         IO elapsed time: 0 usec Time waited on I/O: 0 usec

WARNING: Read Failed. group:2 disk:3 AU:1 offset:4096 size:4096

path:/dev/ASM-LOGA2

         incarnation:0xf0f0e962 synchronous result:'I/O error'

         subsys:System krq:0x7f1b4df79b88 bufp:0x7f1b4df5d000 osderr1:0x69b5 osderr2:0x0

         IO elapsed time: 0 usec Time waited on I/O: 0 usec

2019-06-24T22:08:52.810240+02:00

ERROR: no read quorum in group: required 1984286416, found 1 disks

ERROR: Could not read PST for grp 2. Force dismounting the disk group.

WARNING: Read Failed. group:2 disk:3 AU:1 offset:0 size:4096

path:/dev/ASM-LOGA2

         incarnation:0xf0f0e962 synchronous result:'I/O error'

         subsys:System krq:0x7f1b4df79770 bufp:0x7f1b4df39000 osderr1:0x69b5 osderr2:0x0

         IO elapsed time: 0 usec Time waited on I/O: 0 usec

WARNING: Read Failed. group:2 disk:3 AU:1 offset:4096 size:4096

path:/dev/ASM-LOGA2

         incarnation:0xf0f0e962 synchronous result:'I/O error'

         subsys:System krq:0x7f1b4df79b88 bufp:0x7f1b4df5d000 osderr1:0x69b5 osderr2:0x0

         IO elapsed time: 0 usec Time waited on I/O: 0 usec

2019-06-24T22:08:52.828871+02:00

ERROR: no read quorum in group: required 1984286416, found 1 disks

2019-06-24T22:08:52.829352+02:00

ERROR: Could not heartbeat PST for grp 2. Force dismounting the disk group.

WARNING: Read Failed. group:2 disk:3 AU:1 offset:0 size:4096

path:/dev/ASM-LOGA2

         incarnation:0xf0f0e962 synchronous result:'I/O error'

         subsys:System krq:0x7f1b4df79770 bufp:0x7f1b4df39000 osderr1:0x69b5 osderr2:0x0

         IO elapsed time: 0 usec Time waited on I/O: 0 usec

WARNING: Read Failed. group:2 disk:3 AU:1 offset:4096 size:4096

path:/dev/ASM-LOGA2

         incarnation:0xf0f0e962 synchronous result:'I/O error'

         subsys:System krq:0x7f1b4df79b88 bufp:0x7f1b4df5d000 osderr1:0x69b5 osderr2:0x0

         IO elapsed time: 0 usec Time waited on I/O: 0 usec

2019-06-24T22:08:52.838713+02:00

ERROR: no read quorum in group: required 1984286416, found 1 disks

ERROR: Could not read PST for grp 2. Force dismounting the disk group.

WARNING: Read Failed. group:2 disk:3 AU:1 offset:0 size:4096

path:/dev/ASM-LOGA2

         incarnation:0xf0f0e962 synchronous result:'I/O error'

         subsys:System krq:0x7f1b4df79770 bufp:0x7f1b4df39000 osderr1:0x69b5 osderr2:0x0

         IO elapsed time: 0 usec Time waited on I/O: 0 usec

WARNING: Read Failed. group:2 disk:3 AU:1 offset:4096 size:4096

path:/dev/ASM-LOGA2

         incarnation:0xf0f0e962 synchronous result:'I/O error'

         subsys:System krq:0x7f1b4df79b88 bufp:0x7f1b4df5d000 osderr1:0x69b5 osderr2:0x0

         IO elapsed time: 0 usec Time waited on I/O: 0 usec

2019-06-24T22:08:52.844711+02:00

ERROR: no read quorum in group: required 1984286416, found 1 disks

ERROR: Could not read PST for grp 2. Force dismounting the disk group.

2019-06-24T22:08:52.870818+02:00

ERROR: ORA-15130 in COD recovery for diskgroup 2/0xc25019a7 (LOG)

ERROR: ORA-15130 thrown in RBAL for group number 2

2019-06-24T22:08:52.871477+02:00

Errors in file /u01/app/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_rbal_5503.trc:

ORA-15130: diskgroup "" is being dismounted

2019-06-24T22:08:53.256278+02:00

Errors in file /u01/app/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_rbal_5503.trc:

ORA-15130: diskgroup "" is being dismounted

2019-06-24T22:08:53.356798+02:00

GMON dismounting group 2 at 38 for pid 43, osid 15029

2019-06-24T22:08:53.361175+02:00

NOTE: Disk LOG_0000 in mode 0x7f marked for de-assignment

NOTE: Disk LOG_0001 in mode 0x7f marked for de-assignment

NOTE: Disk LOGA2 in mode 0x7f marked for de-assignment

NOTE: Disk LOGB1 in mode 0x7f marked for de-assignment

2019-06-24T22:08:53.366130+02:00

SUCCESS: diskgroup LOG was dismounted

2019-06-24T22:08:53.367747+02:00

SUCCESS: alter diskgroup LOG dismount force /* ASM SERVER:3260029351 */

SUCCESS: ASM-initiated MANDATORY DISMOUNT of group LOG

2019-06-24T22:08:53.422301+02:00

NOTE: diskgroup resource ora.LOG.dg is offline

So why asm dismount the dg? Is my understanding incorrect about the failgroups?

Thanks for your advices.

Marcel

Comments
Post Details
Added on Jun 24 2019
13 comments
5,667 views