ORA-38730: Invalid SCN/TIMESTAMP expression.

Cause : The expression supplied in a FLASHBACK DATABASE command was invalid.

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

Retry the command using a valid number or time stamp expression.

update : 22-08-2017
ORA-38730

ORA-38730 - Invalid SCN/TIMESTAMP expression.
ORA-38730 - Invalid SCN/TIMESTAMP expression.

  • ora-12596 : TNS:internal inconsistency
  • ora-23615 : Block number string does not exist for script string
  • ora-32344 : cannot create a secondary materialized view with synonym as base table
  • ora-13918 : Updating system alert with reason_id string failed; previous alert not found
  • ora-16026 : parameter string contains an invalid attribute value
  • ora-31082 : invalid attribute "string" specified in declaration of "string"
  • ora-02020 : too many database links in use
  • ora-02313 : object type contains non-queryable type string attribute
  • ora-39012 : Client detached before the job started.
  • ora-39168 : Object path string was not found.
  • ora-24369 : required callbacks not registered for one or more bind handles
  • ora-02309 : atomic NULL violation
  • ora-13826 : empty SQL profile not allowed for create or update SQL profile
  • ora-15171 : invalid syntax in the alias path after 'string'
  • ora-07630 : smpdal: $DELTVA failure
  • ora-07510 : scgbrm: $getlki unexpected return on lockid string
  • ora-33010 : (XSAGDNGL04) Relation workspace object is duplicated in the AGGMAP workspace object.
  • ora-01674 : data file string is an old incarnation rather than current file
  • ora-33098 : (APABBR01) A value of 'string' is not valid for the workspace object option.
  • ora-26576 : cannot acquire SR enqueue
  • ora-16502 : the Data Guard broker operation succeeded with warnings
  • ora-00151 : invalid transaction ID
  • ora-00350 : log string of instance string (thread string) needs to be archived
  • ora-01341 : LogMiner out-of-memory
  • ora-24271 : translation type must be either T, S or M
  • ora-25136 : this cluster can contain only one table
  • ora-32406 : cannot alter partitioning for existing materialized view log
  • ora-22631 : attribute [string] is is not well-formed or does not match the type
  • ora-24236 : source text is empty
  • ora-31422 : owner schema string does not exist
  • 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.