My Oracle Support Banner

ASM Crash by GMON Due to ORA-600 [KFDPHBEAT_REAPIO:02] (Doc ID 2106160.1)

Last updated on JANUARY 24, 2020

Applies to:

Oracle Database - Enterprise Edition - Version and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.


One of our ASM instances crashed causing database instances to restart on 1 node.

The 'alert+ASM1.log' file shows that diskgroup REDO was mounted when
'gmon' reported an ORA-600 error in the I/O function [kfdpHbeat_reapIO:02] on REDO.

In companion with the internal error (ORA-600) we see a corruption in the asm block header reported (ORA-15196).
After asm instance rebounce, no disks are available for REDO. The diskgroup cannot be mounted anymore.

Sat May 30 23:25:43 2015
SUCCESS: diskgroup REDO was mounted

Fri Jun 05 11:11:40 2015
Errors in file <ASM trace directory>/+ASM1_gmon_8723.trc (incident=221838):
ORA-00600: internal error code, arguments: [kfdpHbeat_reapIO:02], [3], [31],[], [], [], [], [], [], [], [], []
ORA-15196: invalid ASM block header [kfdp.c:14537] [endian_kfbh] [0] [0] [0 != 1]

Fri Jun 05 11:12:20 2015
ORA-15017: diskgroup "REDO" cannot be mounted
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "REDO"
Fri Jun 05 11:12:20 2015
ERROR: no read quorum in group: required 2, found 0 disks





To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.