ORA-600 [KFDAUDEALLOC2] AND INSTANCE CRASH EVEN WITH THE FIX OF BUG 14467061 (Doc ID 1903273.1)

Last updated on JULY 05, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.3 to 12.1.0.1 [Release 11.2 to 12.1]
Information in this document applies to any platform.

Symptoms

 

Customer got ORA-600 [kfdAuDealloc2] and instance crashed even with the fix of bug 14467061.

 

Mon Jun 02 09:39:25 2014
Errors in file /odb1/asm/diag/asm/+asm/+ASM3/trace/+ASM3_ora_2283.trc (incident=561):
ORA-00600: internal error code, arguments: [kfdAuDealloc2], [187], [603], [28], [], [], [], [], [], [], [], []
Incident details in: /odb1/asm/diag/asm/+asm/+ASM3/incident/incdir_561/+ASM3_ora_2283_i561.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
ERROR: An unrecoverable error has been identified in ASM metadata. The instance will be taken down.
Mon Jun 02 09:39:41 2014
NOTE: AMDU dump of disk group DG2SVC created at /odb1/asm/diag/asm/+asm/+ASM3/incident/incdir_561
NOTE: starting check of diskgroup DG2SVC
ERROR: file +dg2svc.603.849027701: F603 PX3 => D0 A1896 => F3 PX126: fnum mismatch
ERROR: file +dg2svc.603.849027701: F603 PX4 => D0 A1983 => F3 PX127: fnum mismatch
ERROR: file +dg2svc.603.849027701: F603 PX5 => D0 A2214 => F1861 PX221: fnum mismatch
ERROR: file +dg2svc.603.849027701: F603 PX6 => D0 A2228 => F1861 PX222: fnum mismatch
....
ERROR: disk DG2SVC_DISK1, AT 4: D0 A2214 => F1861 X221: extent not mapped
ERROR: disk DG2SVC_DISK1, AT 4: D0 A2216 => F1861 X232: extent not mapped
ERROR: disk DG2SVC_DISK1, AT 4: D0 A2228 => F1861 X222: extent not mapped
ERROR: disk DG2SVC_DISK1, asz 0, AT 14: AT full, FS avail
NOTE: disk DG2SVC_DISK1, used AU total mismatch: DD={52750, 0} AT={53279, 0}
ERROR: check of diskgroup DG2SVC found 51 total errors
ORA-15049: diskgroup "DG2SVC" contains 51 error(s)
Mon Jun 02 09:39:44 2014
Dumping diagnostic data in directory=[cdmp_20140602093944], requested by (instance=3, osid=2283), summary=[incident=561].
Errors in file /odb1/asm/diag/asm/+asm/+ASM3/trace/+ASM3_ora_2283.trc (incident=562):
ORA-00600: internal error code, arguments: [17090], [], [], [], [], [], [], [], [], [], [], []
Incident details in:
/odb1/asm/diag/asm/+asm/+ASM3/incident/incdir_562/+ASM3_ora_2283_i562.trc
Dumping diagnostic data in directory=[cdmp_20140602093945], requested by (instance=3, osid=2283), summary=[incident=562].
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file /odb1/asm/diag/asm/+asm/+ASM3/trace/+ASM3_ora_2283.trc (incident=563):
ORA-00600: internal error code, arguments: [kfdAuDealloc2], [187], [603], [28], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [17090], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /odb1/asm/diag/asm/+asm/+ASM3/incident/incdir_563/+ASM3_ora_2283_i563.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
ERROR: An unrecoverable error has been identified in ASM metadata. The instance will be taken down.
....

 

This fatal assert brought down ASM instances on all nodes. After ASM instances restarted, the problem diskgroup got auto-mounted. Then RBAL process detected the corruptions again during COD recovery rollback, which triggered the fatal assert and crashed ASM instances again. This cycle repeated many times on all nodes until the problem diskgroup was manually dropped by the customer. 

 

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms