My Oracle Support Banner

ASM failed to start and throws error in ASM Alert log with "ORA-00600: internal error code, arguments: [kfcema40]" (Doc ID 2112692.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Database - Enterprise Edition - Version and later
Information in this document applies to any platform.


The ASM was not starting up but the HAS and CSS were up and running, in the ASM alert log you can see the following errors:

ERROR: diskgroup LOG_A was not mounted
ORA-00600: internal error code, arguments: [kfcema40], [2], [1], [22], [5365], [], [], [], [], [], [], []

Errors in file /u01/app/grid/diag/asm/+asm/+ASM2/trace/+ASM2_ora_32677.trc (incident=92670):
ORA-00600: internal error code, arguments: [kfcema40], [2], [1], [22], [5365], [], [], [], [], [], [], []
Incident details in: /u01/app/grid/diag/asm/+asm/+ASM2/incident/incdir_92670/+ASM2_ora_32677_i92670.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
NOTE: recovery (pass 2) of diskgroup 5 (LOG_A) caught error ORA-600
Errors in file /u01/app/grid/diag/asm/+asm/+ASM2/trace/+ASM2_ora_32677.trc:
ORA-00600: internal error code, arguments: [kfcema40], [2], [1], [22], [5365], [], [], [], [], [], [], []

Abort recovery for domain 5
NOTE: crash recovery signalled OER-600
ERROR: ORA-600 signalled during mount of diskgroup LOG_A
NOTE: cache dismounting (clean) group 5/0x19486FFA (LOG_A)


 There were recent issues with the disks which were fixed which caused un expected DB aborts, or server reboots, and kill daemon processes (ocssd, crsd, lgwr, sysmond, ohasd).


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.