ORA-7445 [Kfcldumple] in ASM alert log and DIAG trace file
(Doc ID 1084000.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Server - Enterprise Edition - Version 184.108.40.206 to 220.127.116.11 [Release 11.1]
Information in this document applies to any platform.
The error is seen in cluster installations with ASM version 18.104.22.168
Many ORA-7445 [kfclDumpLe] errors get reported in ASM alert log, usually on one node only, and the errors are logged in ASM DIAG trace file. Incidents are also generated with DIAG incident trace files.
No ASM instances crash and no database instances crash.
ASM alert log would typically have the error reported as follows (multiple times):
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0xE000000A8] [PC:0x1053E755C, kfclDumpLe()+02fc]
Errors in file <diag dest>/asm/+asm/+ASMN/trace/+ASMN_diag_nnnnnn.trc (incident=iiiiii):
ORA-07445: exception encountered: core dump [kfclDumpLe()+02fc] [SIGSEGV] [ADDR:0xE000000A8] [PC:0x1053E755C] [Address not map
ped to object] 
Incident details in: <diag dest>/asm/+asm/+ASMN/incident/incdir_iiiiii/+ASMN_diag_nnnnnn_iiiiiii.trc
ASM DIAG trace/incident file would typically have the following:
Dump continued from file: <diag dest>/asm/+asm/+ASMN/trace/+ASMN_diag_nnnnnn.trc
ORA-07445: exception encountered: core dump [kfclDumpLe()+02fc] [SIGSEGV] [ADDR:0xE000000A8] [PC:0x1053E755C] [Address not mapped to object] 
----- Call Stack Trace -----
kfclDumpLe ... kjzddss kjzdreqhdl kjzddl kjzgpoll kjzdm_rac kjzdm kstdm ksbrdp opirip opidrv sou2o opimai_real main
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