22/08/13 Document 35928.1

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=1000552890682412&id=35928.1&_afrWindowMode=0&_adf.ctrl-state=csbhabf62_564 1/3

PowerView is Off (0)Consultor IT Contact Us Help

Note: For additional ORA-600 related information please read Note:146580.1

PURPOSE: This article discusses the internal error "ORA-600 [12333]", what it means and possible actions. The information here is only applicable to the versions listed and is provided only for guidance.

ERROR:

Format: ORA-600 [12333] [a] [b] [c] [d]

VERSIONS: Versions 6.0 and above DESCRIPTION:

There are three forms of the OERI(12333) error:

i. Usage with 4 additional values: ORA-600 [PTI] [b] [c] [d] Reported by Oracle release 8.0 and above

ii. Usage with 4 additional values: ORA-600 [a] [b] [c] [d] Reported by Oracle release 8.0 and above

iii. Usage with 3 additional values: ORA-600 [a] [b] [c] Reported by Oracle release 7 and above

The first form of the error is "ORA-600 [12333] [PTI] [b] [c] [d]"

This may be reported when parsing storage options on alter/create of various database objects. The [b], [c], [d] arguments identify a specific statement type being parsed.

This form of the error indicates a problem in the sql parser. As common functions are used to parse the storage options of different database objects, this error code is used as a semantic check that the parser has not passed options that are invalid for the statement being parsed.

The second form of the error is "ORA-600 [12333] [a] [b] [c] [d]"

This represents a Two Task Protocol violation and is reported because an OCI call has been sent in the wrong order.

The third form of the error is "ORA-600 [12333] [a] [b] [c]"

The ORA-600 [12333] is reported 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. The three additional values report the invalid request values received.

The error may have a number of different root causes. For example, a multi-threaded Client-side application sent an OCI call out of order, or the data in the network buffer may have been overwritten.

Since there are many potential causes of this error, it is essential to have a reproducible testcase to correctly diagnose the underlying cause.

ARGUMENTS:

Form i. Arg [a] PTI Arg [b] Parse process Options Arg [c] Statement type Arg [d] Check identification, e.g., INDEX

Form ii. Arg [a] TTI message Arg [b] OPI function code

ORA-600 [12333] "Fatal Two-Task Protocol Violation" (Doc ID 35928.1) To Bottom

Modified: 28-Jun-2013 Type: REFERENCE Status: PUBLISHED Priority: 2 Comments (0)

Dashboard Service Requests Patches & UpdatesKnowledge Search Knowledge Base Advanced

Dashboard >

22/08/13 Document 35928.1

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=1000552890682412&id=35928.1&_afrWindowMode=0&_adf.ctrl-state=csbhabf62_564 2/3

Arg [b] OPI function code Arg [c] Sequence number Arg [d] typically 0

Form iii. Arg [a] TTI Layer Function code received Arg [b] Function code Arg [c] Sequence FUNCTIONALITY: USER/ORACLE INTERFACE LAYER IMPACT: PROCESS FAILURE NO DATA CORRUPTION SUGGESTIONS:

Update to the latest Client or Database patch set.

Check the Known Issues section below for your version.

Check networking connections and NLS settings: Note:77442.1.

Please ensure that the issue is reproducible before pursuing with Oracle Support Services. Known Issues:

Known Bugs

You can restrict the list below to issues likely to affect one of the following versions by clicking the relevant button:

9.2.0.8 10.1.0.5 10.2.0.2 10.2.0.3 10.2.0.4 10.2.0.5 11.1.0.6 11.1.0.7 11.2.0.1 11.2.0.2 Show all Bugs

NB Bug Fixed Description

937337011.2.0.2.8, 11.2.0.2.BP18,11.2.0.3, 12.1.0.1

The wrong cursor may be executed by JDBC thin following a query timeout / ORA-3137 [12333]

9243912 11.2.0.2, 12.1.0.1 Additional diagnostics for ORA-3137 [12333] / OERI:12333

8643311 11.2.0.2, 12.1.0.1 ORA-3137 / ORA-600 [12333] from INSERT .. RETURNING / Procedure with OUT parameter

8625762 11.1.0.7.3, 11.2.0.1 ORA-3137 [12333] due to bind data not read from wire

6737706 10.2.0.5, 11.2.0.1 OERI [12333] / ORA-3137 possible from multi table insert SQL with long binds

6667800 10.2.0.5, 11.1.0.7 OERI:12333 / client hang using OCILob() in multithreaded OCI client

5926074 10.2.0.4, 11.1.0.6 OERI [12333] on update of more than one CLOB column

4669305 9.2.0.8, 10.2.0.3, 11.1.0.6 Enhancement: Add diagnostics for OERI[12333]

4551798 9.2.0.8, 10.2.0.3, 11.1.0.6 JDBC clients can get OERI[12333] on cancel from second thread

4448950 10.1.0.5, 10.2.0.2, 11.1.0.6 OERI:12333 binding a NULL as FIXED_CHAR from JDBC

4366667 10.2.0.2, 11.1.0.6 OCILobWrite with OCI_LAST_PIECE can cause OERI:12333 on next DB access.

4271217 10.2.0.3, 11.1.0.6 OERI:kpolcsc1 / OERI:12333 from JDBC setCharacterStream() for CLOB data

4252999 10.1.0.5, 10.2.0.1 OERI:12333 from JDBC MERGE SQL with a batch size > 1

4216266 10.1.0.5, 10.2.0.1 OERI[12333] from INSERT .. RETURNING from 8.0 client

3668164 10.1.0.5, 10.2.0.1 OERI[12333] / ORA-1461 when reloading cursor with long datatype bind

3124179 9.2.0.5, 10.1.0.2 OERI:12333 possible over DB link with LONG type

3058769 9.2.0.5, 10.1.0.2 OERI:12333 from OCI_DESCRIBE_ONLY of SQL with a BIND over HS

3057986 9.2.0.5, 10.1.0.2 OERI [12333] possible if a client shares a statement handle between SQL / PLSQL

2855665 9.2.0.5, 10.1.0.2 ORA-600[12333] in PRO/OCI clients sharing statement handles

2207382 9.0.1.4, 9.2.0.2, 10.1.0.2 OERI:12333 fetching from Oracle/DB2 in XA

4018783 9.2.0.7 OERI [12333] on import of table with a LONG column

5955927 OERI[12333] from INSERT with OUT bind

2172327 8.1.7.4, 9.0.1.0 XA application using SELECT FOR UPDATE NOWAIT may get OEI:12333 instead of ORA-54

1273347 8.1.6.2, 8.1.7.0 OERI:12333 can occur

953506 8.0.6.2, 8.1.6.0Clients expecting ORA-1405/1406 may get ORA-3106 or OERI:12333 if a function returns NULL and isrepeatedly executed without rebinding

709582 8.1.5.1, 8.1.6.0 RMAN: OERI:12333 possible on SHUTDOWN IMMEDIATE using BACKUP_TAPE_IO_SLAVES

755887 8.0.5.2, 8.0.6.0 PLSQL Update of REMOTE LONG may error ORA-2055

'*' indicates that an alert exists for that issue.'+' indicates a particularly notable issue / bug.

22/08/13 Document 35928.1

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=1000552890682412&id=35928.1&_afrWindowMode=0&_adf.ctrl-state=csbhabf62_564 3/3

'+' indicates a particularly notable issue / bug.'I' indicates an install issue / bug included for completeness.'P' indicates a port specific bug."OERI:xxxx" may be used as shorthand for ORA-600 [xxxx].

REFERENCES:

Note:77442.1 ORA_NLS (ORA_NLS32, ORA_NLS33, ORA_NLS10) Environment Variables explained.Note:389713.1 Understanding and Diagnosing ORA-00600 [12333] / ORA-3137 [12333] Errors

REFERENCES

NOTE:77442.1 - ORA_NLS (ORA_NLS32, ORA_NLS33, ORA_NLS10) Environment Variables explained.NOTE:389713.1 - Understanding and Diagnosing ORA-00600 [12333] / ORA-3137 [12333] ErrorsNOTE:218073.1 - Oracle7 Client Connection to Oracle9i Server Fails With ORA-00600 [12333]

Related

Products

Oracle Database Products > Oracle Database > Oracle Database > Oracle Database - Enterprise Edition > Internals Errors (ORA-600 & ORA-7445)Oracle Database Products > Oracle Database > Oracle Database > Oracle Database - Personal Edition > Internals Errors (ORA-600 & ORA-7445)Oracle Database Products > Oracle Database > Oracle Database > Oracle Database - Standard Edition > Internals Errors (ORA-600 & ORA-7445)

Keywords

BUGTAG_ADDBUGS; DDRCONFIRMED; DYNAMIC ADV USE; INTTEAMREVIEWED

Errors

ORA-600[12333]

Back to Top

Copyright (c) 2013, Oracle. All rights reserved.

Legal Notices and Terms of Use

Privacy Statement