ORA-24356: internal error while converting from to COBOL display type.

Cause : nAi tnrean lreor raw sneocnueter dudirgnc noevsroi notC BOLOd silpyat py.e

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

oCtnca tuctsmores puoptr.

update : 26-09-2017

ORA-24356 - internal error while converting from to COBOL display type.
ORA-24356 - internal error while converting from to COBOL display type.

  • ora-13791 : cannot resume a tuning task created to tune a single statement
  • ora-13779 : invalid load option
  • ora-04015 : ascending sequences that CYCLE must specify MAXVALUE
  • ora-12027 : duplicate filter column
  • ora-36951 : (XSFCAST28) The ALLOCLAST parameter cannot be set to YES unless PERIODICITY specifies more than one cycle.
  • ora-37038 : (XSMLTDCL04) You cannot change definitions of objects in analytic workspace string because it is attached in MULTI mode.
  • ora-19122 : unsupported XQuery declaration
  • ora-01105 : mount is incompatible with mounts by other instances
  • ora-13420 : the SRID of the geometry parameter was not null
  • ora-24121 : both cascade and a block range passed to DBMS_REPAIR.CHECK_OBJECT procedure
  • ora-24906 : invalid recepient attribute passed into OCI call
  • ora-28232 : invalid input length for obfuscation toolkit
  • ora-02736 : osnfpm: illegal default shared memory address
  • ora-19256 : XQ0036 - missing type definitions in imported module
  • ora-02333 : cannot create constraints on attributes of this column
  • ora-28363 : buffer provided not large enough for output
  • ora-12216 : TNS:poorly formed PREFERRED_CMANAGERS addresses in TNSNAV.ORA
  • ora-30647 : error retrieving access parameters for external table string.string
  • ora-01969 : You must specify RESETLOGS or NORESETLOGS
  • ora-00081 : address range [string, string) is not readable
  • ora-32006 : %s initialization parameter has been deprecated
  • ora-36956 : (XSFCAST25) There are only number PERIODICITY values. You cannot specify more OFFSET values.
  • ora-16800 : redo transport service for a standby database incorrectly set to ALTERNATE
  • ora-24380 : invalid mode specification
  • ora-26501 : RepAPI operation failure
  • ora-15107 : missing or invalid ASM disk name
  • ora-27049 : unable to seek to and read the last block
  • ora-24158 : invalid table alias
  • ora-28107 : policy was disabled
  • ora-16563 : unable to add value, syntax error at "string"
  • 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.