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-12448: policy string not applied to schema string
ORA-09815: File name buffer overflow
NNL-00931: Requests refused, no cached meta-data: number
ORA-07700: sksarch: interrupt received
ORA-09960: Unable to establish signal handler for termination signal
EXP-00041: INCTYPE parameter is obsolete
ORA-02333: cannot create constraints on attributes of this column
IMG-00901: VIR signature version mismatch
ORA-31619: invalid dump file "string"
ORA-36954: (XSFCAST24) The cycle number must be between 1 and number. You specified number.
KUP-04049: record number discarded from file string
ORA-07484: snlkput: cannot convert(put) lock.