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-13201: invalid parameters supplied in CREATE INDEX statement
PLS-00509: Implementation Restriction : Pass a returned record to a temporary identifier before selecting a field
ORA-25130: cannot modify primary key - primary key not defined for table
ORA-08431: raw data missing zero as defined in picture
DRG-52104: the Oracle Text environment could not initialize
ORA-27034: maximum length of ORACLE_SID exceeded
ORA-32836: database user string must be granted role string
ORA-14107: partition specification is required for a partitioned object
RMAN-06741: database name is "string" and DBID is string
ORA-12706: this CREATE DATABASE character set is not allowed
ORA-01088: cannot shut down ORACLE while active processes exist
TNS-00262: %20sstringnumber