ORA-24357: internal error while converting from to OCIDate.

Cause : An internal error was encountered during conversion to OCIDate type.

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

Contact customer support.

update : 22-07-2017
ORA-24357

ORA-24357 - internal error while converting from to OCIDate.
ORA-24357 - internal error while converting from to OCIDate.

  • ora-13261 : geometry table string does not exist
  • ora-26026 : unique index string.string initially in unusable state
  • ora-02814 : Unable to get shared memory
  • ora-21300 : objects option not installed
  • ora-00711 : new tablespace name is invalid
  • ora-34346 : (MXDSS04) The string analytic workspace cannot be detached.
  • ora-30374 : materialized view is already fresh
  • ora-31517 : CDC change table string.string already exists
  • ora-31104 : Cannot find lock with token "string" on "string" for unlock
  • ora-19589 : %s is not a snapshot or backup control file
  • ora-29345 : cannot plug a tablespace into a database using an incompatible character set
  • ora-04020 : deadlock detected while trying to lock object stringstringstringstringstring
  • ora-34286 : (MXDCL53) workspace object cannot be used in this context because it is a string.
  • ora-30934 : 'string' (string node) cannot be inserted in parent 'string' (string node)
  • ora-00451 : foreground process died unexpectedly
  • ora-00062 : DML full-table lock cannot be acquired; DML_LOCKS is 0
  • ora-00302 : limit of string logs exceeded
  • ora-10854 : Sets poll count used for AQ listen code under RAC
  • ora-32643 : invalid use of window function in MODEL rule
  • ora-10651 : incorrect file number block number specified
  • ora-36923 : (XSVPMVTOPART04) workspace object is not a LIST or RANGE PARTITION TEMPLATE.
  • ora-12225 : TNS:destination host unreachable
  • ora-24778 : cannot open connections
  • ora-03002 : operator not implemented
  • ora-19577 : file string is MISSING
  • ora-16204 : DDL successfully applied
  • ora-02230 : invalid ALTER CLUSTER option
  • ora-12524 : TNS:listener could not resolve HANDLER_NAME given in connect descriptor
  • ora-02703 : osnpopipe: pipe creation failed
  • ora-00230 : operation disallowed: snapshot control file enqueue unavailable
  • 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.