ORA-00600 [12333]【每日一译】--2012-10-17

Applies to:
Oracle Server - Enterprise Edition - Version: 8.1.7.4 to 11.2.0.3 - Release: 8.1.7 to 11.2

Information in this document applies to any platform.

应用于：

ORACLE服务企业版本8.1.7.4-11.2.0.3-发行号8.1.7-11.2

在此篇文章的信息应用于任何平台。

Purpose

This article will discuss the common causes and troubleshooting tips for ORA-00600 [12333]/ORA-3137 error. ORA-3137[12333] in 11g is the same as ORA-600 [12333] and the same diagnostic steps apply.

目标

此篇文章将讨论常见的原因和排除故障提示信息对于ORA-00600 [12333]/ORA-3137 error. ORA-3137[12333]在11G的报错相同于ORA-600 [12333]并且可以使用同样的诊断

步骤。

ORA-00600 [12333] can occur with three additional numeric values when a request is being received from a network packet and the request code in the packet is not recognized.

ORA-00600 [12333]发生于3个额外的数值不能在包中被识别，这些值通过网络包的请求接收。

Last Review Date --最后概述日期
November 03, 2006 -2006.11.3
Instructions for the Reader --读者的指示
A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.

Troubleshooting Details

一个排除故障向导是指供协助解决一个指定的问题。如果可以，诊断工具包含在文档里协助于排除故障。

For any ONE-TIME occurrence we can safely ignore the error. This error does not relate to any potential data corruption or any data loss. Check Note 35928.1 for known issues and two basic usages of OERI(12333):

    Usage with 3 additional numeric values
    Usage with 4 additional values ... new since 8.0.X

对于之前的发生，我们可以安全的忽略这个错误，这个错误没有涉及任何隐藏数据灾难和任何的数据丢失。核对记录35928.1提供了公开的问题和2个基本的OERI(12333)的使用。

#关于3个额外数值的用法

#关于4个额外数值的用法。。。从8.0.X

 In case the errors are seen consistently and no known issues matches to your issue then do the following

在这种情况下错误是一致性被发现并且未知的问题未符合你的情况请做如下

Common Causes & Solutions:
常见原因&解决：
1.  Check the client software version. An incompatible client software can cause such internal error. The following note explains the supported combinations of clients for a particular RDBMS Server release.
Note 207303.1 Client / Server / Interoperability Support Between Different Oracle Versions

 1.核对客户端软件版本。一个不兼容客户端软件可能导致内部错误。以下笔记展示了对于客户端和数据库服务端版本的组合支持。

2. An incompatible NLS Client setting can also trigger such internal errors. Check the NLS settings as explained in the following note.
Note 77442.1 ORA_NLS (ORA_NLS32, ORA_NLS33, ORA_NLS10) Environment Variables explained

 2.一个不兼容的NLS客户端设置也可能会触发这些内部错误。核对NLS设置在以下的笔记中展示。

Note 77442.1 ORA_NLS (ORA_NLS32, ORA_NLS33, ORA_NLS10)环境变量展示。

3. Try to reproduce the issue from a different client machine, preferably from server. This will rule out the possibility of bad network. If the execution fails from a particular client then it could be due to the bad network from that client to server. The error ORA-600[12333] could occur when a request is being received from a network packet and the request code in the packet is not recognized.

 3.试图去重现问题从不同的客户端机器，最好是从服务端。这将排除糟糕网络的可能性。如果从一个特殊客户端执行失败那么它可能的原因是从客户端到服务端的糟糕网络

。错误代码ORA-600[12333]可能发生当一个请求从网络包中接收并且那个在包中的请求代码是不能识别的。

4. If error still continues , then do the following to understand from where the error is generated.

4.如果错误仍然继续，请按如下理解错误是在哪里发生的；

     We need to understand which session/program/application that triggers this issue. This shall be found from the trace files under the session state object '(session)'. Sometimes the ORA-00600 [12333] trace files will not capture the session information.  In such cases we can check with the end users about any issues around the time-frame of this internal error.

我们需要理解哪些会话/应用/程序/触发这个错误。它将在用户状态对象下面TRACE文件里被发现。有时候ORA-00600[12333]TRACE文件将不会捕捉会话信息。如果是这种情况我们可以核对最终用户在这个发生内部错误的任何问题。

    There is a HIGH chance for application run-time exception to lead to this ORA-00600 [12333]. Due to the unhandled exceptions there is a chance for incomplete information passed to the server hence the internal errors are raised. In such cases, handling those exceptions (or) addressing those errors on the application code will resolve the issue.

对于应用的运行期间存在一个高的机率导致这个ORA-00600[12333]错误。由于未处理的异常，会有一个未完成的信息传递给服务器所以内部错误会显示。处理这些异常或者解决这些错误，通过应用代码将可解决问题。

     In few cases, the problem application will work for a while before it terminates with the error. This could be due to the TIMEOUT settings at the Application Server (or) Forms Server.,etc. To resolve this either tune the failing application to complete within the TIMEOUT value (or) reset the TIMEOUT to an optimal value.

在少数情况下，问题是应用在被这错误中断时会工作一段时间。这可能由于是超时设置在应用服务器上或者是窗体服务器上。比如。为了解决调试失败应用在超时范围值内完成或者是重设超时值到一个最佳值。

    There could be more possibilities here; in simple words the approach should be from application side, which would help us to understand the other issues that triggered this network interruption (ORA-00600 [12333]).

 这存在更多的可能；简而言之处理方法在应用那边，它将帮助我们去理解其它触发这些网络中断的问题（ORA-00600[12333]).

5. If you notice JDBC Client as the failing program under Session state object, please check the following

如果你记得JDBC客户端当失败应用在用户状态对象下，请核对以下：

    That you use latest compatible version of JDBC Drivers in your application side.

    Note 430839.1 to verify the version of JDBC Drivers and for Installation steps.

那个你使用最新兼容版的JDBC驱动在应用端。

NOTE 430839.1验证了JDBC驱动和安装的步骤。

     Monitor and try to handle correctly the timeouts from the application
    Check that idle or died programs/processes are not just killed at the client side but using a good cleaning procedure.

    Increase queue sizes / buffers and similar from the jdbc side.

监视和尝试正确处理应用方面的超时，核对空闲或者死亡的程序/进程并不仅在客户端中KILL而要使用一个好的清理进程。

增加队列大小/缓存并且和JDBC端相同。

Further diagnostics regarding JDBC Application driver can be found:
Note 1361107.1 Suggestions For Troubleshooting ORA-3137 [12333] Errors Encountered When Using Oracle JDBC Driver

进一步的诊断关于JDBC应用驱动可以被发现：

NOTE 1361107.1建议对于故障排除ORA-3137[12333]错误遭遇当使用ORACLE的JDBC驱动.

6. In-case if all the above suggestions does not help to identify the cause, and the ORA-00600 [12333] persists we may need to enable the networking tracings from the problem client and need to review the network traces to understand where the problem occurs. See Note 219968.1 Title: SQL*Net, Net8, Oracle Net Services - Tracing and Logging at a Glance. Check the network logs for errors and fix them with the network administrator.

假设以上所有的建议都不能帮你去检测原因。并且ORA--00600[12333]仍持续我们可能需要开启网络的跟踪从问题的客户端和需要重新查看网络的跟踪和理解问题发生的位置。可以参阅219968.1标题 SQL*Net, Net8, Oracle Net Services-跟踪并马上登录。核对网络日志错误并且和网络管理员修复。

6.

E.g.:

ifconfig -a
=======
eth0 Link encap:Ethernet HWaddr ...
...

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7855996 errors:288 dropped:291 overruns:0 frame:0
TX packets:9874201 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1325085201 (1263.6 Mb) TX bytes:1313633137 (1252.7 Mb)
Interrupt:9 Base address:0x1080

In this case the network administrator should investigate the RX packets errors listed above (RX packets:7855996 errors:288 dropped:291).

 

References
NOTE:207303.1 - Client / Server / Interoperability Support Between Different Oracle Versions
NOTE:219968.1 - SQL*Net & Oracle Net Services - Tracing and Logging at a Glance
NOTE:35928.1 - ORA-600 [12333] "Fatal Two-Task Protocol Violation"
NOTE:430839.1 - Providing a JDBC Testcase to Oracle Support
NOTE:77442.1 - ORA_NLS (ORA_NLS32, ORA_NLS33, ORA_NLS10) Environment Variables explained.
NOTE:752297.1 - ORA-03137: TTC Protocol Internal Error : [12333] Using JDBC Driver