If you login to metalink and use the ora-600 lookup tool you get the following output for argument 12235
This article discusses the internal error "ORA-600 ", what
it means and possible actions. The information here is only applicable
to the versions listed and is provided only for guidance.
ORA-600  [a] [b] [c] [d] [e]
versions 7.0 to 9.2
This error shows up when Oracle detects an Oracle defunct process.
When an Oracle process starts up, it reads data from the SGA that defines
what type of process it should become.
If the process does not locate any valid customization data, it reports
ORA-600  and exits.
On a heavily loaded system, ORA-600  may be a symptom that the server
process was too slow in starting. That is, the process that initiated the
new server may timeout waiting for the new process to start and abandon the
new server request. In the new server process it is possible that the new
server reaches the code to customize its operation before the os request to
kill the process is actioned. The messages "ksbsrv: No startup
acknowledgement from forked process ..." and "Timed out trying to start
shared server ..." may be reported to trace and alert files.
USER/ORACLE INTERFACE LAYER
Ignore the error.
One of the most common reasons for this error to be reported is that
someone typed 'oracle' manually at the OS prompt.
If this error is reported regularly and appears not to be explained
by comments made in this note, contact Oracle Support Services.
Bug# 3616023 P See Note 3616023.8
Tru64: "skgpspawn failed:category = 27143" during process / instance startup
Bug# 405159 See Note 405159.8
OERI:12235 possible starting any slave process