Interested to Buy Any Domain ? << Click Here >> for more details...
RMAN-06533: KEEP ... NOLOGS option is not supported when
database is open
- 2 Answers
- 11356 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-13157: Oracle error ORAstring encountered while string
ORA-16771: Converting physical standby to primary failed in the failover operation.
NNL-00218: Ignoring spurious trailing text "string"
DRG-12409: syntax error for label in string
NNF-01004: DCE returned unspecified error string
ORA-12014: table 'string' does not contain a primary key constraint
ORA-06954: Illegal file name
ORA-28270: Malformed user nickname for password authenticated global user.
ORA-31114: XDB configuration has been deleted or is corrupted
AMD-00156: formula "string" to modify does not exist in Workspace "string"
ORA-13609: The specified task string must be executing to be cancelled or interrupted.
ORA-01937: missing or invalid role name
Oracle Errors 
