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-08111: a partitioned index may not be coalesced as a whole
NNL-00577: list_domains: list authoritative domains in the region or subtree
O2F-00323: Internal error in OTT facility O2F
ORA-19705: tag value exceeds maximum length of string characters
ORA-16101: a valid start SCN could not be found
ORA-09270: szalloc: error allocating memory for security
LSX-00119: value is not valid restriction of parent's minLength
ORA-32033: unsupported column aliasing
NPL-00301: maximum ASN.1 element nesting depth string exceeded on write
ORA-16626: failed to enable specified object
PLS-01467: The value list of the IN predicate, if not a subquery, must contain only value_specifications
ORA-04940: unsupported optimization of Oracle binary, check alert log for more info