Interested to Buy Any Domain ? << Click Here >> for more details...
RMAN-06533: KEEP ... NOLOGS option is not supported when
database is open
- 2 Answers
- 11303 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-12831: Must COMMIT or ROLLBACK after executing INSERT with APPEND hint
ORA-36680: (XSDPART18) workspace object is not a dimension of the PARTITION TEMPLATE.
ORA-27194: skgfdvcmd: sbtcommand returned error
PLS-00500: invalid operator binding
RMAN-20501: redo logs from parent database incarnation cannot be applied
LPX-00274: can't import node type
NNL-00417: Distinguished Name: string
NNL-00807: Queries received, type SOA: number
ORA-37027: (XSMLTRESYNC02) Object workspace object cannot be resynced without modified object workspace object because they share a modified composite dimension.
TNS-00503: Illegal ADDRESS parameters
ORA-07449: sc: usnewlock failed.
ORA-16586: Could not edit database property through instance.
Oracle Errors 
