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
Please add more information about this Error
|Is This Answer Correct ?||0 Yes||1 No|
QSM-00752: the parameter string contains an invalid combination of options string
ORA-22313: cannot use two versions of the same type "string"
ORA-33006: (XSAGDNGL02) The relation workspace object is not related to itself.
NNL-00525: Shows or sets the server's default-forwarding status
NZE-28865: SSL connection closed
ORA-35917: (XSHIDE05) You cannot HIDE model workspace object because the analytic workspace in which it is defined has not been upgraded to version string.
NZE-29241: a buffer block needs to more space but its length is fixed
LSX-00003: invalid attribute "~1S" for element "~2S"
SQL*Loader-00103: Invalid log file name on command line
ORA-25960: join index cannot be based on a temporary table
ORA-26077: direct path column array is not initialized
ORA-01754: a table may contain only one column of type LONG