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-13198: Spatial error: string
TNS-04008: %-25s | string
ORA-22290: operation would exceed the maximum number of opened files or LOBs
ORA-27076: unable to set limit for open files
ORA-38765: Flashed back database cannot be opened read-only.
ORA-01876: year must be at least -4713
ORA-07595: sppid: $GETJPIW failure
ORA-30658: attempt was made to create a temporary table with EXTERNAL organization
ORA-19802: cannot use DB_RECOVERY_FILE_DEST without DB_RECOVERY_FILE_DEST_SIZE
ORA-16749: Resource guard encountered errors in switchover to logical primary
ORA-01112: media recovery not started
ORA-02093: TRANSACTIONS_PER_ROLLBACK_SEGMENT(string) more than maximum possible(string)