ORA-24351: invalid date passed into OCI call

Cause : A bad date was passed into one of the OCI calls.

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

Check your date bind values and correct them.

update : 26-05-2017
ORA-24351

ORA-24351 - invalid date passed into OCI call
ORA-24351 - invalid date passed into OCI call

  • ora-08003 : sequence string.NEXTVAL exceeds internal limits
  • ora-06011 : NETASY: dialogue too long
  • ora-29827 : keyword USING is missing
  • ora-36708 : (XSMXALLOC00) Variable workspace object must be dimensioned to be used by the ALLOCATE command.
  • ora-26761 : Standby Redo Logs not available for real time mining
  • ora-23404 : refresh group "string"."string" does not exist
  • ora-01225 : thread number string is greater than MAXINSTANCES string
  • ora-19036 : Invalid query result set in newContextFromHierarchy()
  • ora-19806 : cannot make duplex backups in recovery area
  • ora-19282 : XQ0068 - It is a static error if a Prolog contains more than one xmlspace declaration
  • ora-19163 : XP0004 - XQuery type mismatch: argument type mismatch: expected - 'string' got - 'string' for function 'string'
  • ora-25316 : Late in the current transaction to begin an Enqueue/Dequeue operation
  • ora-12027 : duplicate filter column
  • ora-29346 : invalid tablespace list
  • ora-07469 : sppst: mclear error, unable to clear semaphore.
  • ora-23607 : invalid column "string"
  • ora-09791 : slembdf: translation error, unable to translate error file name.
  • ora-28175 : incorrect certificate type
  • ora-14259 : table is not partitioned by Hash method
  • ora-12072 : updatable materialized view log data for "string"."string" cannot be created
  • ora-13417 : null or invalid layerNumber parameter
  • ora-22901 : cannot compare nested table or VARRAY or LOB attributes of an object type
  • ora-27432 : step string does not exist for chain string.string
  • ora-32841 : invalid value for property string
  • ora-27507 : IPC error disconnecting from a port
  • ora-36157 : (XSMXAGGRCOMMIT) To use the AUTOCOMMIT keyword, you must also specify the AUTOUPDATE keyword.
  • ora-32129 : cannot get information about this column
  • ora-30658 : attempt was made to create a temporary table with EXTERNAL organization
  • ora-07281 : slsget: times error, unable to get cpu time.
  • ora-16547 : cannot disable the primary database
  • 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.