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 : 24-06-2017

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

  • ora-28011 : the account will expire soon; change your password now
  • ora-12982 : cannot drop column from a nested table
  • ora-38904 : DML error logging is not supported for LOB column "string"
  • ora-31435 : an error occurred during the purge operation
  • ora-19380 : invalid plan filter
  • ora-02300 : invalid value for OIDGENERATORS
  • ora-01140 : cannot end online backup - all files are offline or readonly
  • ora-02153 : invalid VALUES password string
  • ora-07615 : $CHANGE_CLASS failed in retrieving the specified file label
  • ora-16051 : parameter string contains an invalid delay time
  • ora-00130 : invalid listener address 'string'
  • ora-08191 : Flashback Table operation is not supported on remote tables
  • ora-31214 : DBMS_LDAP: PL/SQL - Invalid LDAP mod type.
  • ora-09804 : Class conversion from binary to ORACLE failed.
  • ora-26741 : cannot assemble lobs
  • ora-19560 : %s is not a valid device limit
  • ora-22620 : buffer size too small to hold the value
  • ora-16563 : unable to add value, syntax error at "string"
  • ora-09350 : Windows 32-bit Two-Task driver unable to allocate context area
  • ora-16083 : LogMiner session has not been created
  • ora-30550 : index depends on a package/function spec/body which is not valid
  • ora-23375 : feature is incompatible with database version at string
  • ora-30061 : Internal Event for Savepoint Tracing
  • ora-28164 : REVOKE already specified
  • ora-24313 : user already authenticated
  • ora-16567 : Data Guard broker internal parser error at "string"
  • ora-16544 : modifying DG_BROKER_START requires SID='*' qualifier
  • ora-26714 : User error encountered while applying
  • ora-29833 : indextype does not exist
  • ora-37178 : column string has no values
  • 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.