ORA-13009: the specified date string is invalid

Cause : The specified date string has a bad component or does not match the specified format string.

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

Make sure that the components of the date string are valid and that the date and format strings match.

update : 27-06-2017
ORA-13009

ORA-13009 - the specified date string is invalid
ORA-13009 - the specified date string is invalid

  • ora-04051 : user string cannot use database link string.string
  • ora-21780 : Maximum number of object durations exceeded.
  • ora-25326 : Array string operation failed for message at index string
  • ora-12640 : Authentication adapter initialization failed
  • ora-06815 : TLI Driver: could not link SPX and IPX streams
  • ora-02144 : no option specified for ALTER CLUSTER
  • ora-40208 : duplicate or multiple algorithm settings for function string
  • ora-01676 : standby file name convert of 'string' exceeds maximum length of string
  • ora-02240 : invalid value for OBJNO or TABNO
  • ora-31446 : this session does not own the lock handle for string
  • ora-26008 : Invalid syntax or bind variable in SQL string for column string. string
  • ora-25130 : cannot modify primary key - primary key not defined for table
  • ora-28339 : missing or invalid encryption algorithm
  • ora-00201 : control file version string incompatible with ORACLE version string
  • ora-01137 : data file string is still in the middle of going offline
  • ora-14280 : all rows in table do not qualify for specified subpartition
  • ora-12216 : TNS:poorly formed PREFERRED_CMANAGERS addresses in TNSNAV.ORA
  • ora-07402 : sprst: cannot restore user signal handler.
  • ora-02021 : DDL operations are not allowed on a remote database
  • ora-24361 : basic bind call not invoked before invoking advanced bind call
  • ora-07564 : sldext: wildcard in filename or extension
  • ora-06031 : NETDNT: connect failed, unrecognized object name
  • ora-19926 : Database cannot be converted at this time
  • ora-01541 : system tablespace cannot be brought offline; shut down if necessary
  • ora-38407 : The ADT associated with the attribute set already exists.
  • ora-19585 : premature end of volume on piece string
  • ora-19863 : device block size string is larger than max allowed: string
  • ora-19767 : missing TRACKING keyword
  • ora-26678 : Streams capture process must be created first
  • ora-15076 : Emulating I/O errors on the OSM disk
  • 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.