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 : 25-04-2017
ORA-24357

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

  • ora-13797 : invalid SQL Id specified, string
  • ora-14137 : Table in partially dropped state, submit DROP TABLE PURGE
  • ora-30006 : resource busy; acquire with WAIT timeout expired
  • ora-01904 : DATAFILE keyword expected
  • ora-33336 : (DSSEXIST04A) Analytic workspace string is not attached.
  • ora-01907 : TABLESPACE keyword expected
  • ora-19400 : System type conflict with object SYS.string
  • ora-24900 : invalid or unsupported mode paramater passed in call
  • ora-14309 : Total count of list values exceeds maximum allowed
  • ora-06504 : PL/SQL: Return types of Result Set variables or query do not match
  • ora-01967 : invalid option for CREATE CONTROLFILE
  • ora-28261 : CURRENT_USER can not be used in PLSQL Definer's Right procedure.
  • ora-36885 : (XSSRF04) Error rewriting OLAP DML expression. Column name too big
  • ora-06959 : Buffer I/O quota is too small
  • ora-08102 : index key not found, obj# string, file string, block string (string)
  • ora-29664 : Unable to generate the helper class for the defined type
  • ora-01338 : Other process is attached to LogMiner session
  • ora-19322 : An error occurred while reading from host (string): port (string)
  • ora-31640 : unable to open dump file "string" for read
  • ora-28526 : invalid describe information returned to Heterogeneous Services
  • ora-14189 : this physical attribute may not be specified for an index subpartition
  • ora-07758 : slemcw: invalid handle
  • ora-27010 : skgfwrt: write to file failed
  • ora-16640 : CRS warns that multiple instances may still be running
  • ora-16564 : lookup failed, syntax error at string
  • ora-22953 : Cardinality of the input to powermultiset exceeds maximum allowed
  • ora-06905 : CMX: connect error
  • ora-16704 : cannot modify a read-only property
  • ora-07442 : function address must be in the range string to string
  • ora-29259 : end-of-input reached
  • 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.