Interested to Buy Any Domain ? << Click Here >> for more details...
RMAN-05004: target database log mode is NOARCHIVELOG
- 1 Answers
- 4041 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: An attempt was made to apply TSPITR to a database
that is in NOARCHIVELOG mode.
Action: If all required archive log files are available to
TSPITR, alter the target database log mode to ARCHIVELOG and
retry the TSPITR operation. Otherwise, TSPITR cannot be
applied to this database.
Please add more information about this Error
| Is This Answer Correct ? | 1 Yes | 0 No |
ORA-30182: invalid precision specifier
ORA-13600: error encountered in Advisor string
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
ORA-03290: Invalid truncate command - missing CLUSTER or TABLE keyword
NID-00128: Cannot revert change of database, change not in progress
ORA-01162: block size string in file header does not match configured block sizes
NNO-00268: warning: configuration database is not used, using checkpoint data instead
DRG-12232: invalid attribute tag format
ORA-29323: ALTER DATABASE SET COMPATIBILITY command not supported by string
ORA-25240: message ID and dequeue condition/correlation ID specified in dequeue options
ORA-31012: Given XPATH expression not supported
RMAN-06183: datafile or datafilecopy larger than MAXSETSIZE: file# string string
Oracle Errors 
