I face with that error on R12.1.3 E-Business Suite version with  11.2.0.1 two node RAC database on AIX system with ASM.  Our first instance has Global Enqueue Services Deadlock detected errors in alert.log with ORA-00600: internal error code, arguments: [kjbmprlst:shadow], [], [], [], [], [], [], [], [], [], [], [] error message.

One of the Concorrent manager hang. While we are checking issue We notice that upper error message mention in alert.log file.Whit this error Our prod process has been stop.We restart job from beginning.

For our issue We have been worked together with Oracle Support. Mainly this issue will be fixed  in 12.1.

Here is the solution Suggestion with some useful metalink notes:

Symptoms:
+++++++++
RAC instance crashes with ORA-600 [kjbmprlst:shadow] or ORA-600[kjbrref:pkey], or ORA-600[kjbmocvt:rid],[kjbclose_remaster:!drm], ORA-600 [kjbrasr:pkey]

Possible Causes:
++++++++++++++
This group of ORA-600 are related with DRM (dynamic resource remastering) messaging or read mostly locking. Quite few bugs involved:
Document 9458781.8 Missing close message to master leaves closed lock dangling crashing the instance with assorted Internal error
Document 9835264.8 ORA-600 [kjbrasr:pkey] / ORA-600 [kjbmocvt:rid] in RAC with dynamic remastering
Document 10200390.8 ORA-600[kjbclose_remaster:!drm] in RAC with fix for 9979039
Document 10121589.8 ORA-600 [kjbmprlst:shadow] can occur in RAC
Document 11785390.8 Stack corruption / incorrect behaviour possible in RAC
Document 12408350.8 ORA-600 [kjbrasr:pkey] in RAC with read mostly locking
Document 12834027.8 ORA-600 [kjbmprlst:shadow] / ORA-600 [kjbrasr:pkey] with RAC read mostly locking

Solutions:
++++++++++
Most of above bugs are fixed in 11.2.0.3, apply 11.2.0.3 patchset should avoid the bugs with the exception of Bug 12834027 [http://bug.oraclecorp.com/pls/bug/webbug_edit.edit_info_top?rptno=12834027] , this bug will be fixed in 12.1. Workaround for the bug is:

Disable DRM
or
Disable read-mostly object locking
eg: Run with “_gc_read_mostly_locking”=FALSE

Please refer to above Document number for each bug explanation and solution.

Advertisements