Interested to Buy Any Domain ? << Click Here >> for more details...
RMAN-06533: KEEP ... NOLOGS option is not supported when
database is open
- 2 Answers
- 11449 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / ulhas
the database must be mounted and not open so that this
command runs. Also the backupset can be compressed during
such a backup
RMAN> backup as compressed backupset database keep until
time "to_date('30-AUG-2009','dd-mon-yyyy')" nologs;
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / guest
Cause: The KEEP ... NOLOGS option was specified for a backup
or copy of on open database. This kind of backup requires
archive logs for recovery, so archive logs must be kept.
Action: Remove the KEEP ... NOLOGS option and resubmit the
command.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 1 No |
ORA-26724: only SYS is allowed to set the Capture or Apply user to SYS.
TNS-12618: TNS:versions are incompatible
ORA-29660: Unable to find the class defined in the EXTERNAL NAME clause
ORA-09798: Label comparison failed.
PCB-00231: Host and indicator variables may not have the same name.
PCC-00002: Invalid syntax at column number in line number of file string
ORA-27005: cannot open file for async I/O on device not supporting async
ORA-36820: (XSLMINFO00) The LIMITMAPINFO function encountered an error while parsing the LIMITMAP.
NNO-00622: warning: too many auto-refresh failures for name "string", query expired
EXP-00037: Export views not compatible with database version
QSM-01032: materialized view, string, not found
ORA-29339: tablespace block size string does not match configured block sizes
Oracle Errors 
