Interested to Buy Any Domain ? << Click Here >> for more details...
RMAN-06533: KEEP ... NOLOGS option is not supported when
database is open
- 2 Answers
- 11235 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-39082: Object type string created with compilation warnings
ORA-15006: template "string" does not exist
TNS-02405: GMS call failed, check GMS logs.
ORA-01122: database file string failed verification check
ORA-39107: Master process string violated startup protocol. Master error:
DRG-13007: cannot define an alternate value for the DEFAULT sub lexer
PLS-00541: size or length specified is too large.
ORA-12629: TNS:no event test
ORA-38755: Flashback is already turned on for this tablespace.
DRG-11113: value of string must be one of string
DRG-50934: parser hash create failure
PLS-00231: function 'string' may not be used in SQL
Oracle Errors 
