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 : 24-05-2017
ORA-13009

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

  • ora-31196 : XML nodes over string in size cannot be printed
  • ora-34286 : (MXDCL53) workspace object cannot be used in this context because it is a string.
  • ora-01932 : ADMIN option not granted for role 'string'
  • ora-01346 : LogMiner processed redo beyond specified reset log scn
  • ora-08465 : input mask contains more than 32 characters
  • ora-13375 : the layer is of type [string] while geometry inserted has type [string]
  • ora-22296 : invalid ALTER TABLE option for conversion of LONG datatype to LOB
  • ora-01597 : cannot alter system rollback segment online or offline
  • ora-13628 : Insufficient privileges to access the task belonging to the specified user
  • ora-30452 : cannot compute AVG(X), VARIANCE(X) or STDDEV(X), without COUNT(X) or SUM(X)
  • ora-10914 : invalid TABLESPACE GROUP clause
  • ora-27480 : window "string" is currently open
  • ora-07713 : sksamtd: could not mount archival device (SYS$MOUNT failure)
  • ora-38707 : Media recovery is not enabled.
  • ora-25533 : FAST_START_IO_TARGET or LOG_CHECKPOINT_INTERVAL is specified
  • ora-39115 : %s is not supported over a network link
  • ora-12015 : cannot create a fast refresh materialized view from a complex query
  • ora-13043 : failed to read metadata from the _SDOLAYER table
  • ora-36913 : (XSAGDNGL49) In AGGMAP workspace object, LOAD_STATUS object workspace object must be an undimensioned VALUESET over the relation dimension.
  • ora-38495 : data type for the stored attribute string is inconsistent.
  • ora-06916 : CMX: error in data read (t_datain)
  • ora-32058 : operation restricted to SYSDBA users
  • ora-00221 : error on write to control file
  • ora-19770 : invalid change tracking file name
  • ora-15010 : name is already used by an existing ASM disk
  • ora-06529 : Version mismatch - PL/SQL profiler
  • ora-38781 : cannot disable media recovery - have guaranteed restore points
  • ora-32839 : property string is reserved, names with MGWPROP$_ prefix are not valid
  • ora-31115 : XDB configuration error: string
  • ora-19253 : XQ0033 - too many declarations for namespace prefix string
  • 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.