ORA-600 [17090] Seen Frequently in Alert Log File (Doc ID 1076838.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 11.1.0.7 to 11.2.0.1.0 [Release 11.1 to 11.2]
Information in this document applies to any platform.

Symptoms

The following symptoms have been attributed to this issue :-

a) The following errors are seen in the alert log :-

ORA-00600: internal error code, arguments: [17090]], [], []

It should noted that this error is very generic and can be seen in many bugs so the following
symptoms also need to be encountered.

b) After adding _kse_snap_ring_size=30 [please ensure caution with this parameter,
there is nothing to suggest that it should impact performance but since this is a hidden
parameter only set in a TEST environment or attempt to use a lower value and
if set in PROD do so when the system is not under load] parameter and restarting the instance
we see in the new 600 traces information similar to :-

SNAP #24:
BEFORE kgedec TOPERR 2
CALLSTACK <-ksedsts()+0254<-ksf_short_stack()+0054<-kge_snap_callstack()+0038
<-kge_errorstack_snap_before()+0058<-kgedec()+0170<-psdextp()+0570<-pefccal()+03cc
<-pefcal()+01ec<-pevm_FCAL()+00dc<-pfrinstr_FCAL()+0074<-pfrrun_no_tool()+005c
<-pfrrun()+1128<-pen_xcal_interpreted()+01b4<-pen_XCAL_i()+00e4<-700000530029d14
<-pevm_NCAL()+0054<-pfrinstr_XCAL_SCAL()+017c<-pfrinstr_XCAL()+0010
<-pfrrun_no_tool()+005c<-pfrrun()+1128<-plsql_run()+0720<-peicnt()+0238
<-kkxexe()+027c<-opiexe()+3218<-kpoal8()+106c<-opiodr()+0b98
<-ttcpip()+115c<-opitsk()+1700<-opiino()+09f0<-opiodr()+0b98
<-opidrv()+0440<-sou2o()+0090<-opimai_real()+01b0<-main()+0090<-__start()+0098

ERRORSTACK ORA-25228: timeout or end-of-fetch during message dequeue from .
ORA-25228: timeout or end-of-fetch during message dequeue from APPLSYS.WF_DEFERRED

If ORA-25228 is seen in addition to the 600[17090] this article is a strong candidate, the patch
if available can be applied and if still unresolved can be removed via OPatch

c) A mix of PLSQL native and interpreted compilation could result in this error

The output of the following query showed that some packages were compiled as NATIVE

SELECT name, type, plsql_code_type
FROM dba_plsql_object_settings
WHERE name in ('WF_EVENT_QH', 'WF_EVENT', 'DBMS_AQ');

NAME TYPE PLSQL_CODE_TYPE
------------------------------ ------------ ---------------
DBMS_AQ PACKAGE INTERPRETED
DBMS_AQ PACKAGE BODY INTERPRETED
WF_EVENT PACKAGE INTERPRETED
WF_EVENT PACKAGE BODY NATIVE
WF_EVENT_QH PACKAGE INTERPRETED
WF_EVENT_QH PACKAGE BODY INTERPRETED

A mix of PLSQL native and interpreted compilation could result in this error

It is not always simple to identify if a mix is present, the error/bug has been seen in a number
of APPS environments but the BUG is not APPS specific. 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms