Cause: The BLOCKRECOVER command was
specified.Action: Remove the BLOCKRECOVER
command.
Relared Errors: A>RMAN-05010:
target database must be opened in READ WRITE mode for TSPITRA>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 [...]
Cause: SET NEWNAME … TO NEW is not
allowed with TSPITR.Action: Set the new name to a specific
file name and retry.
Relared Errors: A>RMAN-05009:
Block Media Recovery requires Enterprise EditionA>RMAN-05010:
target database must be opened in READ WRITE mode for TSPITRA>RMAN-05011:
auxiliary instance must be in nomount state for TSPITRA>RMAN-05012:
[...]
Cause: A command was entered that
requires a channel, and no channel is allocated.Action: Use ALLOCATE CHANNEL before
using the command
Relared Errors: A>RMAN-05008:
SET NEWNAME TO NEW not allowed (datafile string)A>RMAN-05009:
Block Media Recovery requires Enterprise EditionA>RMAN-05010:
target database must be opened in READ WRITE mode for TSPITRA>RMAN-05011:
auxiliary [...]
Cause: Standby recover can only be
performed for the whole database.Action: Change the tablespace list to a
database specification.
Relared Errors: A>RMAN-05007:
no channel allocatedA>RMAN-05008:
SET NEWNAME TO NEW not allowed (datafile string)A>RMAN-05009:
Block Media Recovery requires Enterprise EditionA>RMAN-05010:
target database must be opened in READ WRITE mode for TSPITRA>RMAN-05011:
[...]
Cause: The requested tablespace has been
re-created and is not allowed in point-in-time recovery.Action: Remove the indicated tablespace
from the recovery set and retry the operation.
Relared Errors: A>RMAN-05006:
cannot recover clone standby single tablespacesA>RMAN-05007:
no channel allocatedA>RMAN-05008:
SET NEWNAME TO NEW not allowed (datafile string)A>RMAN-05009:
Block Media Recovery requires [...]
Cause: An attempt was made to apply
TSPITR to a database that is in NOARCHIVELOG mode.Action: If all required archive log
files are available to TSPITR, alter the target database log mode to
ARCHIVELOG and retry the TSPITR operation. Otherwise, TSPITR cannot be applied
to this database.
Relared Errors: A>RMAN-05005:
point-in-time [...]
Cause: The SYSTEM tablespace or a
tablespace containing rollback segments is not allowed in point-in-time
recovery.Action: Remove the indicated tablespace
from the recovery set and retry the operation.
Relared Errors: A>RMAN-05004:
target database log mode is NOARCHIVELOGA>RMAN-05005:
point-in-time recovery is not allowed for re-created tablespace
stringA>RMAN-05006:
cannot recover clone [...]
Cause: Previously encountered error(s)
were issued which require corrective action.Action: Resolve the error conditions,
and then re-issue the RECOVER command.
Relared Errors: A>RMAN-05003:
point-in-time recovery is not allowed for tablespace
stringA>RMAN-05004:
target database log mode is NOARCHIVELOGA>RMAN-05005:
point-in-time recovery is not allowed for re-created tablespace
stringA>RMAN-05006:
cannot recover [...]
Cause: RMAN is attempting to use the
specified filename as a restore destination in the auxiliary database, but
this name is already in use by the target database.Action: Use the CONFIGURE AUXNAME
command to specify a name for the datafile that does not conflict with a
filename in use by the [...]
Cause: Either: -) The controlfile
mounted by the auxiliary database does not have an entry for this datafile,
therefore filename conversion is not possible. -) A COPY DATAFILE TO AUXNAME
command was issued, but no auxname was set for this datafile.Action: Use the CONFIGURE AUXNAME
command to specify a filename that [...]
 |  |  |  |  |
| By N2H | ||||
