Interested to Buy Any Domain ? << Click Here >> for more details...
ORA-39150: bad flashback time
- 1 Answers
- 6441 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: A flashback time was specified for the Data Pump job
which either could not be parsed or else could not be
translated into a system change number (SCN). This typically
occurs when
Action: Specify an explicit SCN for the desired flashback
rather than a time.
Please add more information about this Error
| Is This Answer Correct ? | 2 Yes | 1 No |
NID-00441: All previous backups and archived redo logs for this database are unusable.
ORA-12522: TNS:listener could not find available instance with given INSTANCE_ROLE
CLSR-01004: Failed to mount database
NNL-00022: error changing trace level from string to string, level change ignored
PCC-00020: Unable to obtain define variables at line number in file string
KUP-02006: script line too long
ORA-19801: initialization parameter DB_RECOVERY_FILE_DEST is not set
ORA-13763: illegal ranking attribute "string"
ORA-06110: NETTCP: message send failure
ORA-32337: cannot alter materialized view with pending changes refresh on commit
ORA-26705: cannot downgrade capture process after Streams data dictionary has been upgraded
ORA-39051: parameter string specified multiple times
Oracle Errors 
