My Oracle Support Banner

ORA-00600: [kfrValAcd30] :: While mounting ASM diskgroup after wrong OS patch applied (Doc ID 2122324.1)

Last updated on AUGUST 29, 2022

Applies to:

Oracle Database - Standard Edition - Version and later
Oracle Database - Enterprise Edition - Version to [Release 12.1]
Information in this document applies to any platform.


Unable to mount the ASM diskgroup on node 2 after OS level bad patch applied.
That resulted OS level disk to become read-only.

And later while mounting same diskgroup on node 2,ASM level it was failing with below,


Mon Mar 21 18:31:11 2016

* allocate domain 1, invalid = TRUE
kjbdomatt send to inst 1
Mon Mar 21 18:31:11 2016
NOTE: attached to recovery domain 1
Mon Mar 21 18:31:11 2016
NOTE: starting crash recovery of group 1 (FLOCALP_DATA) thread=1 ckpt=39.7270 domain=1 inc#=2 instnum=1
NOTE: starting crash recovery of group 1 (FLOCALP_DATA) thread=2 ckpt=59.8582 domain=1 inc#=8 instnum=2 <<-----------
Errors in file /u01/app/grid/diag/asm/+asm/+ASM2/trace/+ASM2_ora_59169.trc (incident=328267):
ORA-00600: internal error code, arguments: [kfrValAcd30], [FLOCALP_DATA], [1], [39], [7270], [40], [7312], [], [], [], [], []
Incident details in: /u01/app/grid/diag/asm/+asm/+ASM2/incident/incdir_328267/+ASM2_ora_59169_i328267.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.

File_name :: alert_+ASM2.log



Other node ,it was working fine and mounting of same diskgroup taking place without any issue .


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.