数据库报oracle error：OAR-00600[12235],[],[],[],[],[],[]

OAR-00600[12235],[],[],[],[],[],[]

跟踪文件-Call Stack Trace

calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
ksedmp+0148 bl ksedst 10288D11C ?
ksfdmp+0018 bl 01FD4778
kgeriv+0118 bl _ptrgl
kgesiv+0080 bl kgeriv FFFFFFFFFFFF5E8 ? 000000000 ?
FFFFFFFFFFFFED0 ?
9FFFFFFF0007CF8 ?
BADC0FFEE0DDF00D ?
ksesic0+005c bl kgesiv 000000000 ? 000000800 ?
BADC0FFEE0DDF00D ?
BADC0FFEE0DDF00D ?
FFFFFFFFFFFE4A0 ?
opirip+0488 bl 01FD466C
opidrv+0300 bl opirip 110266FF0 ? 000000000 ?
000000000 ?
sou2o+0028 bl opidrv 32FFFFF470 ? 0A004F570 ?
000000000 ?
main+01a4 bl 01FD40E8
__start+0090 bl main 000000000 ? 000000000 ?

--------------------- Binary Stack Dump ---------------------

[@more@]

oracle support 的解决方案：

两篇文档：ID 403519.1、ID 456154.1

内容如下：

一.

In this DocumentSymptoms
Cause
Solution
References

---

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

Applies to:

Oracle Server - Enterprise Edition - Version: 9.2.0.6 and later [Release: 9.2 and later ]
Information in this document applies to any platform.
***Checked for relevance on 09-APR-2012***

Symptoms

Alert Log encounter the error below:

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

Cause

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.

Suspected BUG 4408380 9.2.0.6 RDBMS 9.2.0.6 DICTIONARY PRODID-5 PORTID-59 ORA-600 3949307 Abstract: INSTANCE HUNG - ORA-600 [12235].


- alert log and trace file show the error ORA-600 [12235] .

----- Call Stack Trace -----

ksedmp ksfdmp kgeriv kgesiv ksesic0 opirip opidrv sou2o main start

The error cannot be simply ignored. The side effects as per bugs descriptions are:
- instance hanging
- processes cannot startup

Solution

The solution is to apply the patch or upgrade to a version where the fix is included.

Apply the 9.2.0.6.0 one-off Patch 3949307

To download the patch ,please login to Metalink and select following:
Patches
Simple Search
Search By Patch Number(s) ->3949307
Platform or Language -> AIX 5L Based System (64-bit)

二.

In this Document

Purpose

Troubleshooting Steps

References

Applies to:

Oracle Server - Enterprise Edition - Version 8.1.7.0 to 11.2.0.3 [Release 8.1.7 to 11.2]
Oracle Server - Standard Edition - Version 7.0.16.0 to 11.2.0.3 [Release 7.0 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 20-Jan-2012***
This document refers to database/RDBMS versions 7.0 to 10.2.0.5. Much of this will also be relevant to future releasesPurpose

The purpose of this guide is to explain the meaning of the ORA-600 [12235] error and some of the possible causes. It is intended as a starting point in the troubleshooting process. It does not contain in depth step by step instructions for each eventuality, but there is enough information to allow you to determine whether or not this is a serious issue, and if so, what the possible cause might be. There are links provided to allow you to find additional information as required.

Troubleshooting Steps

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]

DESCRIPTION:

This error shows up when a background process is not properly started.

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. The messages "ksbsrv: No startup acknowledgment 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

1.

There is no DB corruption involved here. This is not generally serious unless the SGA is corrupt and the error keeps occurring.

2.

This can be caused in some releases by just typing 'oracle' at the command line. To eliminate this you can add a dummy 'oracle' shell script in a bin directory in the users PATH before the $ORACLE_HOME/bin
directory.

You can create the script as follows:

cd $ORACLE_HOME
mkdir dummy
cd dummy
touch $ORACLE_HOME/dummy/oracle
chmod a+x $ORACLE_HOME/dummy/oracle
Then modify PATH to have $ORACLE_HOME/dummy/oracle before $ORACLE_HOME/bin

3.

You should look for any other errors close to this one.
For example, this has been seen alongside ORA-03113. You should investigate accompanying errors and contact Oracle Support if you are in need of assistance.

4.

Is LOG_ARCHIVE_START=TRUE but your database is in NOARCHIVELOG mode ?
If so, you may be able to eliminate the problem by setting:
LOG_ARCHIVE_START = FALSE and restarting the database

5.

If you see this error:
"skgpspawn failed:category = 27143, depinfo = 13, op = open, loc = skgpstime2"
or, if your operating system is HP TRU64 you may be encountering Bug 3616023
Please see Note 281338.1.

6.

If this error occurs with unpublished error ORA-10388 during a parallel query interrupt you may be hitting Bug 4711175 which is fixed in releases 10.1.0.6 and 10.2.0.1

7.

If you are running Oracle 8.0 or below and using PQO, MTS, Prespawned Servers etc..apply the latest 8.0.6 patch set or upgrade to a supported version of the database to protect against unpublished bug 405159.

8.

If you are running Grid Control and the ORA-600 [12235] is accompanied by connection failure errors in the emagent.trc the server definitions may not be set up correctly in /etc/hosts and /etc/netsvc.con. Refer to Note 1389794.1.

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/28227905/viewspace-1060230/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/28227905/viewspace-1060230/