My Oracle Support Banner

ORA-00600 [kjbrpickcur:!cur] AND Instance Termination Due to Error 484 (Doc ID 2462825.1)

Last updated on FEBRUARY 19, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 to 18.3.0.0.0 [Release 12.1 to 18]
Information in this document applies to any platform.

Symptoms

In a 12.1.0.2 Real Application Cluster environment, one of the database Instance terminate after below ORA-00600 error

alert_orcl1.log (from <oracle base>/diag/rdbms/orcl/orcl1/trace location):
Fri Mar 23 03:32:12 2018
Errors in file $TRACE/<instancename1>_lms1_170124.trc(incident=168157):
ORA-00600: internal error code, arguments: [kjbrpickcur:!cur], [0], [0],[], [], [], [], [], [], [], [], []
Incident details in: $INCIDENT/<instancename1>_lms1_170124_i168157.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Fri Mar 23 03:32:13 2018
Errors in file $TRACE/<instancename1>_lms1_170124.trc:
ORA-00600: internal error code, arguments: [kjbrpickcur:!cur], [0], [0],[], [], [], [], [], [], [], [], []
Fri Mar 23 03:32:13 2018
Dumping diagnostic data in directory=[cdmp_20180323033213], requested by (instance=1, osid=170124 (LMS1)), summary=[incident=168157].
Fri Mar 23 03:32:13 2018
Sweep [inc][168157]: completed
Sweep [inc2][168157]: completed
Fri Mar 23 03:32:19 2018
Errors in file $TRACE/<instancename1>_lms1_170124.trc:
ORA-00600: internal error code, arguments: [kjbrpickcur:!cur], [0], [0], [], [], [], [], [], [], [], [], []
Fri Mar 23 03:32:19 2018
USER (ospid: 170124): terminating the instance due to error 484
Fri Mar 23 03:32:19 2018
System state dump requested by (instance=1, osid=170124 (LMS1)), summary=[abnormal instance termination].
System State dumped to trace file $TRACE/<instancename1>_diag_170096_20180323033219.trc
 
Corresponding incident trace have following messages:

$INCIDENT/incdir_168157/<instancename1>_lms1_170124_i168157.trc:

*** ACTION NAME:() 2018-03-23 03:32:12.566

[TOC00000]
Jump to table of contents
Dump continued from file:$TRACE/<instancename1>_lms1_170124.trc
[TOC00001]
ORA-00600: internal error code, arguments: [kjbrpickcur:!cur], [0], [0],[], [], [], [], [], [], [], [], []

[TOC00001-END]
[TOC00002]
========= Dump for incident 168157 (ORA 600 [kjbrpickcur:!cur]) ========
[TOC00003]
----- Beginning of Customized Incident Dump(s) -----
[TOC00004]
GCS RESOURCE 0x2c76030b0 hashq [0x2cfe164a0,0x2ca75ec30] name[0x44592e.a] pkey 0.10.15675499 domid 0
grant (nil) cvt (nil) send (nil)@1,0 write 0x2cd266b48,0@2
flag 0x200000 mdrole 0x10 mode 0 scan 0.0 role GLOBAL
disk: 0x0209.19e89542 write: 0x0209.19e9783b lwbscn: 0x0000.00000000 cnt 0x0 hist 0xe7
xid 0x0000.000.00000000 sid 1 pkwait 0s rmacks 0
refpcnt 0 weak: 0x0000.00000000 inrcv 0
pkey 0.10.15675499 undo 0 stat 5 masters[32768, 1->32768] reminc 4
RM# 16135 flg x46 type x0 afftime xa0769488, acquire time 5665095
#replays: 0:0 1:0
benefit 0, total 0, remote 0, remote cost 0
cr benefit 0, cr total 0, cr remote 0, cr remote cost 0
hv 60 [stat 0x0, 1->1, wm 32768, RMno 0, reminc 4, dom 0]
kjga st 0x4, step 0.0.0, cinc 4, rmno 16135, flags 0x6020
lb 0, hb 131071, myb 68389, drmb 68389, apifrz 0
GCS RESOURCE END
[TOC00004-END]
2018-03-23 02:32:12.566797 : kjbmbassert [0x44592e.a]
2018-03-23 02:32:12.566821 : kjbmsassert(0x44592e.a)(to 2)(lvl 4)
----- End of Customized Incident Dump(s) -----

Call stack Trace: kjbmpocr => kjbrgdbaping => kjbrpickcur.

$TRACE/<instancename1>_lms1_170124.trc: 

Incident 168157 created, dump file: $INCIDENT/incdir_168157/<instancename1>_lms1_170124_i168157.trc
ORA-00600: internal error code, arguments: [kjbrpickcur:!cur], [0], [0],[], [], [], [], [], [], [], [], []

kjmpbmsg: caught non-fatal error 600
kjmpbmsg fatal error on 32
MSG [32:KJX_B_OCR] [0x44592e.a] inc=4 len=352 sender=(2,2) seq=322235431
fg=iqb stat=KJUSERSTAT_DONE spnum=17 flg=x0
flow ctrl: ver=1 flag=109 len=352 tkts=0 seq=322235431 wrp=0
sndr=2 dest=1 rcvr=2
FUSION MSG 0x7f1c0cddad58,32 from 2 spnum 17 ver[4,16135] ln 352 sq[2,8] flg x0
OCR [0x44592e.a, 15675512.10] lockp[0x239f693e8,3721] shadow[0x2cd266b48,25046]
reqid xf4a seq 0x1 fl 0x49.0 md x2 infosz 152 opt 0x0
seq 0x1 change-scn scn: 0x0000.19e40000 xid 0x0000.000.00000000
grant 1 convert 0 role x3
pi [0x209.0x19e9677d] flags 0x0 state 0x100
disk scn 0x209.19543d9f writereq scn 0x0.0 rreqid x9c4
msgRM# 16135 bkt# 68389 drmbkt# 68389
pkey 0.10.15675512
hv 60 [stat 0x0, 1->1, wm 32768, RMno 0, reminc 4, dom 0]
kjga st 0x4, step 0.31.0, cinc 4, rmno 16135, flags 0x6020
lb 0, hb 131071, myb 68389, drmb 68389, apifrz 0
FUSION MSG DUMP END

 $TRACE/<instancename1>_lmon_170110.trc:

*** 2018-03-23 03:31:55.233

* DRM RCFG called (swin 0)
CGS recovery timeout = 145 sec
Begin DRM(16135) (swin 0)
AFFINITY pdb 0 tsn 10 object id 15675499, mysize 8642, maxsize 8723, objscan 1.1, create affinity to instance 1
AFFINITY pdb 0 tsn 10 object id 15675501, mysize 7386, maxsize 7386, objscan 1.1, create affinity to instance 1
AFFINITY pdb 0 tsn 10 object id 15675502, mysize 8601, maxsize 8696, objscan 1.1, create affinity to instance 2
Total pkey count in this drm 3, my cumulative object size 24629, cache size 443292
.

.
End DRM(16135) (total time 0.5 secs)

 

Changes

 No changes in the environment.

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
Symptoms
Changes
Cause
Solution
 Community Discussions
References


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