RMAN-06533: KEEP ... NOLOGS option is not supported when
database is open
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-24022: the specified parameters has no effect on the queue
ORA-22620: buffer size too small to hold the value
PLS-00438: value in LIMIT clause: 'string' use is invalid
ORA-16191: Primary log shipping client not logged on standby
ORA-16115: loading Log Miner dictionary data
ORA-01286: start interval required
ORA-30076: invalid extract field for extract source
QSM-02066: Oracle error: see RELATED_NUM and RELATED_TEXT for details
TNS-00061: INTCTL: Bad command or syntax error: You must specify a trace level
PLS-00238: external parameter name string not found in formal parameter list
ORA-16103: Logical Standby apply must be stopped to allow this operation
NNL-00566: set|show log_file_name [<filename>] [<server_list>] : set|show the log file name on one or more servers