ORA-00600  ON JAVA CLASS RECOMPILATION
Last updated on NOVEMBER 28, 2016
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 11.1 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 19-04-2013***
After applying the July2009 CPU all Java Classes fail on recompiling with:
ORA-00600: internal error code, arguments: , , 
When using Oracle Database Server 11.1.0.x
AND attempting to compile all Java Classes via a custom script created like:
'alter java class "' || k.owner || '"."' || k.object_name || '" compile;' cmd
from dba_objects k
-- k.owner = '<owner_name>'
and k.object_type = 'JAVA CLASS'
and k.owner not in ( 'SYS' )
order by k.owner, k.object_name
the following error occurs:
ORA-00600: internal error code, arguments: , , , , , , , , , , , 
The SQL Statement in the trace file contains a statement similar to:
ALTER JAVA CLASS "<Owner_name>"."<Java_Class>" compile
A Call Stack similar to:
ksedst1 ksedst dbkedDefDump dbgexPhaseII dbgexProcessError
The trace may also contain an ORA-29953
You also observe that once this happens it takes a long time to close the SQLPlus session
and that the PGA may grow abnormally. You may notice various memory errors occur when doing numerous java class resolutions in the same session. (unpublished Bug 8871468)
Other observations include:
When resolving a valid class which has inner classes an ORA-29553 occurs. (unpublished Bug 8871412)
Resolve numerous classes in the same session until out of memory starts occurring. If SEGVs in jol_build_method_table or jol_setup_invoker_arrays also occur. (unpublished Bug 8909146)
A SEGV in jol_setup_invokers_array after an error in class resolution is an indication. (unpublished Bug 8889889)
A patch or upgrade has taken place in the database server.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms