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-06-2017

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

  • ora-24192 : the property name cannot be null
  • ora-10579 : Can not modify control file during test recovery
  • ora-10926 : trace name context forever
  • ora-02490 : missing required file size in RESIZE clause
  • ora-14630 : subpartition resides in offlined tablespace
  • ora-28054 : the password has expired. string Grace logins are left
  • ora-01137 : data file string is still in the middle of going offline
  • ora-00027 : cannot kill current session
  • ora-01742 : comment not terminated properly
  • ora-23535 : instantiating templates from multiple back ends is not allowed.
  • ora-19264 : XQ0044 - invalid namespace in attribute constructors
  • ora-16721 : unable to set LOG_ARCHIVE_DEST_n initialization parameters
  • ora-07484 : snlkput: cannot convert(put) lock.
  • ora-25228 : timeout or end-of-fetch during message dequeue from string.string
  • ora-19232 : XQ0012 - imported schemas violate validity rules
  • ora-29760 : instance_number parameter not specified
  • ora-30941 : Cannot specify empty URI for non-default namespace 'string'
  • ora-00351 : recover-to time invalid
  • ora-16814 : incorrect redo transport setting for AlternateLocation for standby database
  • ora-36648 : (XSDUNION09) Concat dimension workspace object is already defined as UNIQUE.
  • ora-13284 : failure to copy geometry object for conversion in place
  • ora-02473 : Error while evaluating the cluster's hash expression.
  • ora-19903 : test recovery not allowed when recovering to new incarnation
  • ora-31508 : invalid parameter value for synchronous change set
  • ora-31198 : Mismatch in number of bytes transferred due to non-binary mode
  • ora-24434 : OCIStmtRelease called before OCIStmtPrepare2.
  • ora-09979 : skxfqhsnd: Error Sending a message to another endpoint
  • ora-06923 : CMX: illegal break condition
  • ora-29869 : cannot issue ALTER without REBUILD on a domain index marked FAILED
  • ora-02158 : invalid CREATE INDEX 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.