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-13458: GeoRaster metadata SRS error
RMAN-08009: channel string: starting archive log backupset
ORA-00104: deadlock detected; all public servers blocked waiting for resources
ORA-27464: invalid schedule type string
QSM-02080: mv log must have primary key
RMAN-03019: asynchronous RPCs are NOT working
ORA-02335: invalid datatype for cluster column
PCC-02129: CMD-LINE: Client supplied static options table is invalid
ORA-01117: adding file 'string' with illegal block size: string; limit is string
PLS-00439: A LIMIT clause must be used within a BULK FETCH
DRG-50301: server error reading request queue
PCC-02445: USING clause valid only on a PREPAREd dynamic statement