昨天巡检一个客户的数据库时发现有ora-00600 12235错误,并且出现频率不高
客户数据库版本9.2.0.7 操作系统AIX 5.3
Mon Dec 22 12:01:15 2008
Errors in file /software/oracle/admin/sjqddb/bdump/sjqddb_ora_5644398.trc:
ORA-00600: internal error code, arguments: [12235], [], [], [], [], [], [], []
解决该问题的方法:
以下metalink解释
Note: For additional ORA-600 related information please read Note 146580.1
PURPOSE:
This article discusses the internal error "ORA-600 [12235]", what
it means and possible actions. The information here is only applicable
to the versions listed and is provided only for guidance.
ERROR:
ORA-600 [12235] [a] [b] [c] [d] [e]
VERSIONS:
versions 7.0 to 9.2
DESCRIPTION:
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 [12235] and exits.
On a heavily loaded system, ORA-600 [12235] 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.
FUNCTIONALITY:
USER/ORACLE INTERFACE LAYER
IMPACT:
NO IMPACT
SUGGESTIONS:
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.
Known Issues:
Bug# 3616023 P See Note 3616023.8
Tru64: "skgpspawn failed:category = 27143" during process / instance startup
Fixed: 10.2.0.1
Bug# 405159 See Note 405159.8
OERI:12235 possible starting any slave process
Fixed: 8.0.6.0
通看metalink解释说是人为的运行了oracle命令也有可能造成该bug出现,
对生产系统没什么影响,可以忽略。