Summary of Bugs containing ORA-00600[12333] Error [ID 428629.1]

Summary of Bugs containing ORA-00600[12333] Error [ID 428629.1]
   Modified 09-MAY-2007     Type REFERENCE     Status PUBLISHED  

In this Document
  Purpose
  Scope
  Summary of Bugs containing ORA-00600[12333] Error

Applies to:
Oracle Server - Enterprise Edition - Version: 8.1.7.4 to 10.2.0.3
Information in this document applies to any platform.
Purpose
The purpose of this Note is to explain bugs filed for ORA-00600 [12333] error against specific Oracle database versions, and explain the symptoms of each bug, workarounds if any and references the patch available at the time this article was written.

Scope

This article is a consolidated effort to summarize the top bugs reported ORA-00600 [12333] which have been fixed. It is directed towards Oracle Support Analysts and Oracle Customers to have an overview of various bugs logged for the same error.

Error Description:

This is a communication mismatch between the Oracle executable and the client program
The error may have a number of different root causes. For example, a network error may have caused bad data to be received, or the client application may have sent wrong data, or the data in the network buffer may have been overwritten.
Summary of Bugs containing ORA-00600[12333] Error
Bug 5578649 (Unpublished)
Abstract: ORA-600 [12333] WHEN 10.2.0.2 PATCH4 IS APPLIED

Version affected: 10.2.0.2 with Patch 4

Fixed in version: 10.2.0.2 with Patch 5

Backportable: No

Symptoms:

This bug is specific to Window platform.
ORA-00600 [12333] can occur while running on 10.2.0.2 with Patch 4

Details:

The problem is most likely due to bad JDBC module in Patch4 and fixed in Patch5

Workaround:

None

Patch details:

Applying patch 5 or later can fix this issue

Bug 4018783

Abstract: OERI [12333] on import of table with a LONG column

Versions affected: 9.2.0.6

Fixed in version : 9.2.0.7

Backportable: Yes

Symptoms:

To be seeing this bug the following must be true:
1. Import raises an Ora-600 [12333]
2. The failure occurs on a table with a LONG datatype
3. The table has a tab$.flags entry that does not have bit 0x1 set

Details:

Import may fail with ORA-600 [12333] for tables that have been
backed up and have LONG columns.(The tab$.flags entry for the table does not have bit 0x1 set)
This flag can have been cleared by an incremental backup, or an ALTER TABLE ... BACKUP command.

Workaround:

Perform. some "dummy" DML on the table to get the 0x1 tab$.flags bit set.

Patch details:

Currently there is no one-off patch available for any platform. and version

Bug 2855665

Abstract: ORA-600[12333] in PRO/OCI clients sharing statement handles

Version affected: 8.1.7.4

Fixed in version: 8.1.7.5 & 9.2.0.5

Backportable: 8.1.7

Symptoms:

ORA-00600 [12333] when sharing stmt handles with sql raising client side error

Details:

ORA-600 [12333] when sharing statement handles if the SQL
raises a client side error.

Workaround:

None

Patch details:

One-off patch available for few platforms on top of 8.1.7.4
Check the Metalink for Merge Patch availability.

Bug 3668164 (Unpublished)
Abstract: OERI[12333] / ORA-1461 when reloading cursor with long datatype bind.

Version affected: 10.1.0.3 & 10.1.0.4

Fixed in version: 10.1.0.5 & 10.2.0.1

Backportable: yes

Symptoms:

To be seeing this bug the following should be true:
1. Ora-600 [12333] or Ora-1461 is raised
2. The problem cursor has a LONG datatype bind (eg LONG RAW, CLOB etc)
3. The database version is 10g
4. There is evidence of cursors being reloaded due to shared pool pressure

Details:

Cursors operating on LONG datatype binds may raise an ORA-600 [12333]
should they be reloaded into the shared pool.

Workaround:

dbms_shared_pool.keep() may be used to ensure that the cursor never gets
reloaded. Also, increasing the shared pool size may help avoid the problem.

Patch details:

One-off patch available for few platforms on top of 10.1.0.3 & 10.1.0.4
Check the Metalink for Patch 3668164 availability.

Bug 4216266 

Abstract: OERI[12333] from INSERT .. RETURNING from 8.0 client

Version affected: 9.2.0.5, 9.2.0.6 & 10.1.0.4

Fixed in version: 10.1.0.5 & 10.2.0.1

Backportable: yes

Symptoms:

If you re-executing insert with returning clause with out binds from 8.0.6
client to 8i and above server and if you hit ORA-3106/ORA-600[12333] then
you might be hitting this bug

Details:

ORA-600[12333] can occur when re-executing an insert with a returning
clause with out binds from an 8.0 client to 8i (or higher) server.
Note: This fix introduces the problem described in bug 4459410.

Workaround:

None

Patch details:

One-off patch available for few platforms on top of 9.2.0.5
Check the Metalink for Patch 4216266 availability.

<>

Abstract: OCILobWrite with OCI_LAST_PIECE can cause OERI:12333 on next DB access

Version affected: 9.2.0.6

Fixed in version: 11.0

Backportable: Yes

Symptoms:

When OCI application invokes OCILobWrite with OCI_LAST_PIECE (incorrect usage, should have been OCI_FIRST_PIECE or OCI_ONE_PIECE)and a ORA-600 [12333] is received from server it is this bug.

Details:

If an OCI application invokes OCILobWrite with OCI_LAST_PIECE (incorrect usage) then an ORA-600 [12333] occurs on the next database access.

Workaround:

Correct the application application.
(ie: it should use OCI_FIRST_PIECE or OCI_ONE_PIECE before trying to use OCI_LAST_PIECE)

Patch details:

Currently there is no one-off patch available for any platform. and version

<>

Abstract: JDBC clients can get OERI[12333] on cancel from second thread

Version affected: 9.2.0.7 10.1.0.5 & 10.2.0.2

Fixed in version: 9.2.0.8, 10.1.0.6 & 10.2.0.3

Backportable: Yes

Symptoms:

-

Details:

Multithreaded JDBC clients which cancel operations on the server executing
from another thread can fail with ORA-600 [12333] as writes to the NET
connection may not be syncronized.

Workaround:

None

Patch details:

Merge patches available for few platforms on top of 10.1.0.3 & 10.2.0.2
Check the Metalink for Merge Patch availability.

<>

Abstract: OERI:12333 binding a NULL as FIXED_CHAR from JDBC

Version affected: 10.1.0.4 & 10.2.0.1

Fixed in version: 10.1.0.5, 10.2.0.2 & 11.0

Backportable: Yes

Symptoms:

Bind a null with type as FIXED_CHAR if you get an exception you might have hit this bug.

Details:

ORA-600 [12333] can occur binding a NULL with type FIXED_CHAR in JDBC.

Workaround:

Have more than one bind.
eg: if you have a query as,
"SELECT c1 FROM T1 WHERE c2 = :1"
binding as setNull (1, FIXED_CHAR)
instead do,
"SELECT c1 FROM T1 WHERE 1 = :1 AND c2 = :2"
setInt (1, 1)
setNull (2, FIXED_CHAR)

Patch details:

Currently there is no one-off patch available for any platform. and version

<>

Abstract: OERI:12333 from JDBC MERGE SQL with a batch size > 1

Version affected: 10.1.0.3 & 10.1.0.4

Fixed in version: 10.1.0.5 & 10.2

Backportable: Yes to 10.1.0.x

Symptoms:

1. Execute a batch with sql string starting with MERGE keyword.
2. If you see ORA-600 when the batch size is > 1 then you might have hit this bug.

Details:

An ORA-600 [12333] can occur for a MERGE SQL operation issued
from a JDBC client with a batch size > 1.

Workaround:

Do not use JDBC batching

Patch details:

Currently there is no one-off patch available for any platform. and version

<>

Abstract: OERI:12333 possible over DB link with LONG type

Version affected: 9.2.0.3 & 9.2.0.4

Fixed in version: 9.2.0.5 & 10.1

Backportable: yes

Symptoms:

When you have a table with long column bound with SQLT_AFC type and insert it
using a dblink, then you get 12333, this is the bug you are hitting.

Details:

A query which has a table accessed over a database link
with a long column bound with an SQLT_AFC type (instead
of a long type) can result in ORA-600 [12333]

Workaround:

Use SQLT_LNG for the bind instead of SQLT_AFC .

Patch details:

One-off patch available for few platforms on top of 9.2.0.4
Check the Metalink for Patch 3124179 availability.

<>

Abstract: OERI:12333 from OCI_DESCRIBE_ONLY of SQL with a BIND over HS

Version affected:  9.2.0.3

Fixed in version: 9.2.0.5 & 10.1

Backportable: yes

Symptoms:

If you lose connection to Oracle (ORA-3113) and see an ORA-600 in the
Oracle trace file internal error code, argument: [12333] ... and a
stack like: ksedmp(), kgeriv(), kgesiv(), ksesic3(), opitsk(), then
you are seeing this bug

Details:

The Heterogenious Services (HS) module does not properly handle
OCIStmtExecute( OCI_DESCRIBE_ONLY ) followed with a regular
OCIStmtExecute. This resulted in an ORA-600 [12333]

eg:
Assume "SELECT DNAME FROM WHERE DNAME = :B0000"
is used in an OCI program that does the following:
OCIStmtPrepare
OCIStmtExecute - OCI_DESCRIBE_ONLY
OCIBindByName
OCIDefineByPos
OCIStmtExecute - OCI_DEFAULT
This may fail with ORA-600 [12333]

Workaround:

Do not use OCIStmtExecute( OCI_DESCRIBE_ONLY ) for statements including binds which use an HS service.

Patch details:

One-off patch available for few platforms on top of 9.2.0.3
Check the Metalink for Patch 3058769 availability.

Bug 3057986 (Unpublished)
Abstract: OERI [12333] possible if a client shares a statement handle between SQL / PLSQL

Version affected: 8.1.7.4 & 9.2.0.4

Fixed in version: 9.2.0.5 & 10.1

Backportable: yes

Symptoms:

ORA-00600[12333] when sharing stmt handles with sql/plsql raising client side error

Details:

ORA-600 [12333] can occur if a client shares a statement handle
between SQL and PLSQL calls.

Workaround:

None

Patch details:

One-off patch & merge patches available for few platforms on top of 8.1.7.4 & 9.2.0.4
Check the Metalink for Patch availability.

Disclaimer:

This note contains most frequently hit bugs that can throw the error ORA-00600 [12333]. However the above mentioned are not the complete list of bugs that can generate this error.

Show Related Information Related
Products

    * Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Enterprise Edition

Errors
ORA-12333; ORA-1461; ORA-3106; ORA-3113; ORA-600[12333]