ORA-600 [12333] "Fatal Two-Task Protocol Violation" [ID 35928.1]
   Modified 16-DEC-2010     Type REFERENCE     Status PUBLISHED  

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:             
  ORA-600 [12333] [a] [b] [c] [d]

VERSIONS:          
  Versions 6.0 to 10.2
 
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 onwards

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

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

  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
  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.