ORA-13642: The specified string string provided for string cannot be converted to a date. The acceptable date format is string.

Cause : The uesr suplpied ad ate vlaue ina n incrorect ofrmat.

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

Retryb y suplpying avlid vlaue.

update : 30-04-2017
ORA-13642

ORA-13642 - The specified string string provided for string cannot be converted to a date. The acceptable date format is string.
ORA-13642 - The specified string string provided for string cannot be converted to a date. The acceptable date format is string.

  • ora-00065 : initialization of FIXED_DATE failed
  • ora-12487 : clearance labels not between DBHIGH and DBLOW
  • ora-02260 : table can have only one primary key
  • ora-32506 : expecting one of string, string, or string but found string
  • ora-01982 : invalid auditing option for tables
  • ora-35066 : (QFGET03) Extension number number is missing for EIF file string.
  • ora-30682 : improper value for argument OPTION_FLAGS
  • ora-30037 : Cannot perform parallel DML after a prior DML on the object
  • ora-24056 : internal inconsistency for QUEUE string and destination string
  • ora-23363 : mismatch of mview base table "string" at master and mview site
  • ora-29349 : tablespace 'string' already exists
  • ora-23450 : flavor already contains object "string"."string"
  • ora-34183 : (MXCHGDCL22) Partition number already exists.
  • ora-13422 : invalid model coordinate parameter
  • ora-23417 : unknown materialized view type: string
  • ora-22902 : CURSOR expression not allowed
  • ora-07716 : sksachk: invalid device specification for ARCHIVE
  • ora-00053 : maximum number of enqueues exceeded
  • ora-28611 : bitmap index is corrupted - see trace file for diagnostics
  • ora-04021 : timeout occurred while waiting to lock object stringstringstringstringstring
  • ora-03239 : maxextents (string) reached in LOB segment string.string subpartition string
  • ora-37074 : (XSMCSESS02) Variable workspace object has no default aggmap.
  • ora-06603 : LU6.2 Driver: Error allocating memory
  • ora-06809 : TLI Driver: could not clear the IPX ethernet SAP at init
  • ora-31428 : no publication contains all the specified columns
  • ora-29389 : too many errors during validation
  • ora-06780 : TLI Driver: recv error code failed
  • ora-31014 : Attempted to delete the root container
  • ora-07633 : smsdbp: illegal protection value
  • ora-14257 : cannot move partition other than a Range or Hash partition
  • 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.