Database Instance Crash with ORA-600 [kclbla_2] (Doc ID 1355547.1)

Last updated on MARCH 11, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.2 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 Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

1. Database instance crash with ORA-600 [kclbla_2] in LMS process.

2. Database instance alert log shows the following:

[date and time]
Errors in file <diagnostic_dest>/diag/rdbms/<dbname>/<instname>/trace/<instname>_lms[n]_[LMS_PID].trc (incident=[INC_NUMBER]):
ORA-00600: internal error code, arguments: [kclbla_2], [N1], [N2], [N3], [N4], []
Incident details in: /u01/app/oracle/diag/rdbms/<dbname>/<instname>/incident/incdir_[INC_NUMBER]/<instname>_lms[n]_[LMS_PID]_i[INC_NUMBER].trc
...
Errors in file <diagnostic_dest>/diag/rdbms/<dbname>/<instname>/trace/<instname>_lms[n]_[LMS_PID].trc:
ORA-00600: internal error code, arguments: [kclbla_2], [N1], [N2], [N3], [N4], []
LMS[n] (ospid: LMS_PID): terminating the instance due to error 484
System state dump requested by (instance=[n], osid=LMS_PID (LMS[n])), summary=[abnormal instance termination].
System State dumped to trace file <diagnostic_dest>/diag/rdbms/<dbname>/<instname>/trace/<instname>_diag_[DIAG_PID].trc
[date and time]
ORA-1092 : opitsk aborting process
[date and time]
Instance terminated by LMS[n], pid = [LMS_PID]
...

3. The resulting LMS incident trace file [instance_name]_lms[n]_[LMS_PID]_i[INC_NUMBER].trc has the contents similar to this:

Dump continued from file: <diagnostic_dest>/diag/rdbms/<dbname>/<instname>/trace/<instname>_lms[n]_[LMS_PID].trc
ORA-00600: internal error code, arguments: [kclbla_2], [N1], [N2], [N3], [N4], []

========= Dump for incident [INC_NUMBER] (ORA 600 [kclbla_2]) ========
----- Beginning of Customized Incident Dump(s) -----
GLOBAL CACHE ELEMENT DUMP
...
LIST OF BUFFERS LINKED TO THIS GLOBAL CACHE ELEMENT:
flg: 0x0a680000 state: SCURRENT tsn: [N2]
...

[Block dumps...]

----- End of Customized Incident Dump(s) -----

*** [date and time]
dbkedDefDump(): Starting incident default dumps (flags=0x2, level=3, mask=0x0)

----- SQL Statement (None) -----
Current SQL information unavailable - no cursor.

----- Call Stack Trace -----
skdstdst()
ksedst1()
ksedst()
dbkedDefDump()
ksedmp()
ksfdmp()
dbgexPhaseII()
dbgexExplicitEndInc()
dbgeEndDDEInvocationImpl()
dbgeEndDDEInvocation()
kclbla()
kjblpbast()
kjbmpbast()
kjmxmpm()
kjmpbmsg()
kjmsm()
ksbrdp()
opirip()
opidrv()
sou2o()
opimai_real()
ssthrdmain()
main()

NOTE: The call stack trace has been edited for clarity.

Changes

Cause

	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.

Database Instance Crash with ORA-600 [kclbla_2] (Doc ID 1355547.1)

Applies to:

Symptoms

Changes

Cause

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

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