Cause: The user attempted to modify the
configuration which cannot be changed for a BACKUP or STANDBY control file
while the mounted control file was either BACKUP or STANDBY. The following
configurations can be changed only when connected to primary database instance
that has CURRENT/CREATED control file type mounted: CONFIGURE RETENTION [...]
Cause: The AUXILIARY DESTIONATION option
was specified for a normal recovery. It is only allowed for tablespace point
in time recovery.Action: Remove the AUXILIARY
DESTIONATION option and re-run the RECOVER command.
Relared Errors: A>RMAN-05021:
this configuration cannot be changed for a BACKUP or STANDBY control
fileA>RMAN-05500:
the auxiliary database must [...]
Cause: A RECOVER COPY command could not
proceed because incremental backup sets exist on a device type that has not
been allocated.Action: Use the LIST command to
determine which device type is needed, then allocate a channel of that
type.
Relared Errors: A>RMAN-05020:
cannot specify AUXILIARY DESTIONATION option for normal
[...]
Cause: This error message can follow one
or more RMAN-5017 or RMAN-5019 error messages.Action: See RMAN-5017 or RMAN-5019 error
messages documentation for more information.
Relared Errors: A>RMAN-05019:
WARNING: no channel of required type allocated to recover copy of datafile
nA>RMAN-05020:
cannot specify AUXILIARY DESTIONATION option for normal
recoveryA>RMAN-05021:
this [...]
Cause: A RECOVER COPY command was not
able to proceed because no copy of indicated file was found to recover.
Possible causes include the following:
1. no copy of indicated file exists on disk that satisfy the criteria
specified in the user`s recover operands.
2. copy of indicated datafile exists [...]
Cause: This is an informational message
to indicate the RMAN could not successfully restore the files using the
specified backups. An attempt was made to restore the datafiles/archivelogs/
controlfile/SPFILE using a previous existing backup.Action: See accompnaying additional
error messages indicating the cause of the failover.
Relared Errors: A>RMAN-05017:
no copy of [...]
Cause: RMAN is attempting to use the
specified control filename for TSPITR as a restore destination in the
auxiliary database, but this name is already in use by the target
database.Action: Set control_files parameter in
the auxiliary instance to a name that does not conflict with a filename in use
[...]
Cause: The instance could not be started
because no default parameter file (either PFILE or SPFILE) could be found. The
instance will be started in restricted mode with default parameters.Action: None - this is an informational
message.
Relared Errors: A>RMAN-05013:
auxiliary control filename string conflicts with a file used by the
[...]
Cause: The Auxiliary instance was not in
nomount state.Action: Open the auxiliary instance in
nomount state.
Relared Errors: A>RMAN-05012:
trying to start the Oracle instance without parameter files
…A>RMAN-05013:
auxiliary control filename string conflicts with a file used by the
tarA>RMAN-05016:
failover to previous backupA>RMAN-05017:
no copy of [...]
Cause: The target database was not
opened in read write mode.Action: Open the database in read write
mode.
Relared Errors: A>RMAN-05011:
auxiliary instance must be in nomount state for TSPITRA>RMAN-05012:
trying to start the Oracle instance without parameter files
…A>RMAN-05013:
auxiliary control filename string conflicts with a file used by [...]
 |  |  |  |  |
| By N2H | ||||
