ORA-24352: invalid COBOL display type passed into OCI call

Cause : A bad COBOL display type was passed into one of the OCI calls.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Check your COBOL display type bind values and correct them.

update : 20-08-2017

ORA-24352 - invalid COBOL display type passed into OCI call
ORA-24352 - invalid COBOL display type passed into OCI call

  • ora-28543 : Error initializing apply connection to non-Oracle system
  • ora-01519 : error while processing file 'string' near line string
  • ora-40282 : invalid cost matrix
  • ora-06030 : NETDNT: connect failed, unrecognized node name
  • ora-19903 : test recovery not allowed when recovering to new incarnation
  • ora-33082 : (XSAGDNGL41) In AGGMAP workspace object, the non-dimensioned valueset workspace object must have a parent QDR in its VALUESET statement over the VALUESET's base dimension.
  • ora-14640 : add/coalesce index partition operation is valid only for hash partitioned global indexes
  • ora-35074 : (QFHEAD02) EIF file string cannot be read by this version of string.
  • ora-27078 : unable to determine limit for open files
  • ora-08000 : maximum number of session sequence lists exceeded
  • ora-15101 : no action specified
  • ora-14401 : inserted partition key is outside specified partition
  • ora-25303 : Buffered operation allowed only on the owner instance
  • ora-02329 : column of datatype string cannot be unique or a primary key
  • ora-14012 : resulting partition name conflicts with that of an existing partition
  • ora-19233 : XQ0013 - invalid pragma
  • ora-06777 : TLI Driver: error reading parms
  • ora-29521 : referenced name string could not be found
  • ora-13184 : failed to initialize tessellation package
  • ora-30459 : 'string.string' cannot be refreshed because the refresh method is NONE
  • ora-10863 : Control behavior of buffered background operations
  • ora-30117 : syntax error at 'string' at the start of input
  • ora-01030 : SELECT ... INTO variable does not exist
  • ora-15106 : missing or invalid operating system disk locator string
  • ora-33263 : Could not create analytic workspace string
  • ora-40205 : invalid setting name string
  • ora-24366 : migratable user handle is set in service handle
  • ora-23480 : Column string is not a top-level column of "string"."string".
  • ora-31645 : unable to read from dump file "string"
  • ora-29706 : incorrect value string for parameter ACTIVE_INSTANCE_COUNT
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.