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 : 24-05-2017
ORA-24352

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

  • ora-28363 : buffer provided not large enough for output
  • ora-39025 : jobs of type string are not restartable
  • ora-06549 : PL/SQL: failed to dynamically open shared object (DLL): string
  • ora-13517 : Baseline (id = string) does not exist
  • ora-22978 : only simple attribute name is allowed in the WITH OBJECT OID clause
  • ora-36646 : (XSDUNION08) Only concat dimensions can be redefined as UNIQUE. workspace object is not a concat dimension.
  • ora-10668 : Inject Evil Identifiers
  • ora-02728 : osnfop: access error on oracle executable
  • ora-37150 : line string, column string, string
  • ora-36612 : (XSLMS01) invalid OLAP message number: value
  • ora-16211 : unsupported record found in the archived redo log
  • ora-25239 : message ID not supplied when dequeuing from exception queue string.string
  • ora-36393 : (XSMXCLEA03) When using the AGGREGATES, CHANGES or CACHE options, you must specify the ALL keyword.
  • ora-24912 : Listener thread failed. string
  • ora-19503 : cannot obtain information on device, name="string", type="string", parms="string"
  • ora-22608 : cannot add an attribute to the already generated image handle
  • ora-13771 : cannot obtain exclusive lock string on "SQL Tuning Set" "string" owned by user "string"
  • ora-02455 : The number of cluster key column must be 1
  • ora-01935 : missing user or role name
  • ora-12519 : TNS:no appropriate service handler found
  • ora-06309 : IPA: No message queue available
  • ora-27071 : unable to seek to desired position in file
  • ora-13467 : unsupported GeoRaster metadata specification: string
  • ora-30574 : Cannot create rollback segment in tablespace with AUTO segment space management
  • ora-31111 : table string cannot be hierarchically enabled
  • ora-14163 : subpartition number string: INITRANS value must be less than MAXTRANS value
  • ora-06539 : target of OPEN must be a query
  • ora-15003 : diskgroup "string" already mounted in another lock name space
  • ora-29317 : datafile string does not exist
  • ora-14050 : invalid ALTER INDEX MODIFY PARTITION option
  • 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.