20000-20999 |
RMAN-20000 |
abnormal termination of job step
Cause: A job step encountered an error and could not recover.
This error should be followed by other errors indicating the cause of the
problem.
Action:
Check the accompanying error. |
RMAN-20001
|
target database not found in recovery catalog
Cause: target database is not found in the recovery catalog
Action:
make sure that the target database is registered in the recovery recovery
catalog. |
RMAN-20002
|
target database already registered in recovery catalog
Cause: target database is already registered in the recovery
catalog
Action:
if the target database is really registered, there is no need to register it
again. Note that the recovery catalog enforces that all databases have a unique
DBID. If the new database was created by copying files from an existing
database, it will have the same DBID as the original database and cannot be
registered in the same recovery catalog. |
RMAN-20003
|
target database incarnation not found in recovery catalog
Cause: resetlogs change# and/or time of the target database
doesn't match any database incarnation in the recovery catalog.
Action:
if target database was opened with resetlogs option then use 'reset database'
to register the new incarnation. |
RMAN-20004
|
target database name does not match name in recovery catalog
Cause: name of the target database doesn't match the one stored
in the recovery catalog
Action:
This is an internal error, call support. |
RMAN-20005
|
target database name is ambiguous
Cause: two or more databases in the recovery catalog match this
name
Action:
none. |
RMAN-20006
|
target database name is missing
Cause: target database instance is not started or db_name
initialization parameter is not set
Action:
startup the instance and make sure that db_name parameter is set. |
RMAN-20009
|
database incarnation already registered
Cause: this incarnation is already registered in the recovery
catalog
Action:
No action is required. |
RMAN-20010
|
database incarnation not found
Cause: database incarnation does not match any database
incarnation in the recovery catalog
Action:
specify a valid database incarnation key. |
RMAN-20011
|
target database incarnation is not current in recovery catalog
Cause: the database incarnation that matches the resetlogs
change# and time of the mounted target database control file is not the current
incarnation of the database
Action: If 'reset database to incarnation
' was used to make an old incarnation current then restore the target database from a backup that matches the incarnation and mount it. You will need to do 'startup nomount' before you can restore the control file using RMAN. Otherwise use 'reset database to incarnation
' make the intended incarnation current in the recovery catalog. |
RMAN-20029
|
cannot make a snapshot control file
Cause: another operation that needs the snapshot control file is
in progress
Action:
try again later if necessary. |
RMAN-20030
|
resync in progress
Cause: this procedure can not be called while a resync is in
progress
Action:
This is an internal error. |
RMAN-20031
|
resync not started
Cause: this procedure can only be called in a resync
Action:
This is an internal error. |
RMAN-20032
|
checkpoint change# too low
Cause: the checkpoint change# is less than the one of the
previous resync or the checkpoint change# is null
Action:
make sure that the right control file is used. |
RMAN-20033
|
control file sequence# too low
Cause: the control file sequence is less than the one of the
previous resync
Action:
make sure that the right control file is used. |
RMAN-20034
|
resync not needed
Cause: the control file has not changed since the previous resync
Action:
nothing since the recovery catalog is in sync. |
RMAN-20039
|
format requires character when duplexing
Cause: SET_DUPLEX=ON was specified, but %c was not part of the
format.
Action:
Include %c in format, or use %U. |
RMAN-20201
|
datafile not found in the recovery catalog
Cause: The specified datafile is not found in the recovery
catalog
Action:
make sure that the datafile name is correct and that the recovery catalog is
up-to-date. |
RMAN-20202
|
tablespace not found in the recovery catalog
Cause: the specified tablespace is not found in the recovery
catalog
Action:
make sure that the tablespace name is correct and that the recovery catalog is
up-to-date. |
RMAN-20203
|
translation in progress
Cause: this procedure can not be called when name translation is
in progress
Action:
this is an internal error. |
RMAN-20204
|
translation not started
Cause: getDatafile procedure was called before
translateTablespace
Action:
this is an internal error. |
RMAN-20205
|
incomplete UNTIL clause
Cause: The sequence# was NULL
Action:
this is an internal error. |
RMAN-20206
|
log sequence not found in the repository
Cause: The specified log sequence does not exists in log history
of the current database incarnation
Action:
check the thread# and sequence#. |
RMAN-20207
|
UNTIL TIME or RECOVERY WINDOW is before RESETLOGS time
Cause: UNTIL TIME and RECOVERY WINDOW cannot be less than the
database creation time or RESETLOGS time.
Action:
Check the UNTIL TIME or RECOVERY WINDOW. If the database needs to be restored
to an old incarnation, use the RESET DATABASE TO INCARNATION command. |
RMAN-20208
|
UNTIL CHANGE is before RESETLOGS change
Cause: UNTIL CHANGE cannot be less than the database RESETLOGS
change.
Action:
Check the UNTIL CHANGE. If the database needs to be restored to an old
incarnation, use the RESET DATABASE TO INCARNATION command. |
RMAN-20209
|
duplicate datafile name
Cause: Two datafiles have the same name
Action:
this is an internal error. |
RMAN-20211
|
FROM TIME is before RESETLOGS time
Cause: FROM TIME cannot be less than the database creation time
or RESETLOGS time.
Action:
Check the FROM TIME. If the database needs to be restored to an old
incarnation, use the RESET DATABASE TO INCARNATION command. |
RMAN-20212
|
UNTIL CHANGE is an orphan incarnation
Cause: Specified UNTIL CHANGE was an orphan incarnation.
Action:
Check the UNTIL CHANGE or UNTIL RESTORE POINT. If the database needs to be
restored or flashed back to an orphan incarnation, use the RESET DATABASE TO
INCARNATION command. |
RMAN-20215
|
backup set not found
Cause: The specified backup set key was not found in the recovery
catalog
Action:
Specify a different backup set key. |
RMAN-20217
|
datafile not part of the database
Cause: the datafile does not exists or did not exist at until
time/scn
Action:
check the datafile name or number. This is an internal error for restore
database or tablespace. |
RMAN-20218
|
datafile not found in recovery catalog
Cause: This is an internal error
Action:
Contact Oracle Customer Support. |
RMAN-20220
|
control file copy not found in the recovery catalog
Cause: the specified control file is not in the recovery catalog
or it has been marked deleted
Action:
check the filename. |
RMAN-20221
|
ambiguous control file copy name
Cause: more than one control file copy in the recovery catalog
match the specified name.
Action:
none. |
RMAN-20222
|
datafilename not found in recovery catalog or is ambiguous
Cause: The specified datafilename is not the name of a datafile
that is currently part of the target database, or an UNTIL clause has been
specified and the filename was for a different datafile at the time specified
by the UNTIL clause than it is now.
Action:
Use a datafile number to specify the datafile you want to RESTORE or RECOVER. |
RMAN-20230
|
datafile copy not found in the recovery catalog
Cause: the specified datafile is not in the recovery catalog or
it has been marked deleted
Action:
check the datafile copy name or key. |
RMAN-20231
|
ambiguous datafile copy name
Cause: more than one control file copy in the recovery catalog
match the specified name.
Action:
use the datafile copy key to uniquely specify the datafile copy. |
RMAN-20240
|
archived log not found in the recovery catalog
Cause: the specified archived log was not found in the recovery
catalog or it has been marked deleted
Action:
check the archived log name or key. |
RMAN-20241
|
ambiguous archived log name
Cause: more than one archived log in the recovery catalog match
the specified name
Action:
use the archived log key to uniquely specify the archived log. |
RMAN-20250
|
offline range not found in the recovery catalog
Cause: the specified offline was not found in the recovery
catalog
Action:
check that recovery catalog is current. |
RMAN-20260
|
backup piece not found in the recovery catalog
Cause: the specified backup piece is not in the recovery catalog
or it has been marked deleted
Action:
check the backup piece handle or key. |
RMAN-20261
|
ambiguous backup piece handle
Cause: more than one backup piece in the recovery catalog match
the specified handle
Action:
use the backup piece key to uniquely specify the backup piece. |
RMAN-20272
|
no parent backup found for the incremental backup
Cause: no available backup or copy that could be used as the
parent of the incremental backup was found in the recovery catalog.
Action:
take a level 0 backup or copy of the datafile first. |
RMAN-20280
|
too many device types
Cause: more than 8 device types were allocated
Action:
make sure that the job allocates at most 8 different device types. |
RMAN-20298
|
DBMS_RCVCAT package not compatible with the recovery catalog
Cause: The version of the recovery catalog tables does not work
with this version of the DBMS_RCVCAT package.
Action:
Check that the recovery catalog packages and schema are installed correctly.
The UPGRADE CATALOG command can be used to upgrade the recovery catalog tables
and packages to the most current version. |
RMAN-20299
|
DBMS_RCVMAN package not compatible with the recovery catalog
Cause: The version of the recovery catalog tables does not work
with this version of the DBMS_RCVMAN package.
Action:
Check that the recovery catalog packages and schema are installed correctly.
The UPGRADE CATALOG command can be used to upgrade the recovery catalog tables
and packages to the most current version. |
RMAN-20310
|
proxy copy not found in the recovery catalog
Cause: the specified proxy copy is not in the recovery catalog or
it has been marked deleted
Action:
check the proxy copy handle or key. |
RMAN-20311
|
ambiguous proxy copy handle
Cause: more than one proxy copy in the recovery catalog matches
the specified handle
Action:
use the proxy copy key to uniquely specify the proxy copy. |
RMAN-20401
|
script already exists
Cause: a CREATE SCRIPT was issued, but a script with the
specified name already exists.
Action:
use a different name or use REPLACE SCRIPT. |
RMAN-20501
|
redo logs from parent database incarnation cannot be applied
Cause: A RESTORE or RECOVER of a datafile was requested, but
recovery of the datafile would require applying redo logs that were generated
before the most recent OPEN RESETLOGS.
Action:
If a full backup or datafile copy from the current database incarnation exists,
ensure that it is marked AVAILABLE, and that a channel of the correct device
type is allocated. It may also be necessary to remove the FROM BACKUPSET or
FROM DATAFILECOPY or FROM TAG operands if these have been specified. |
RMAN-20502
|
DELETE EXPIRED cannot delete objects that exist - run
CROSSCHECK
Cause: A DELETE EXPIRED command was run, but the object was
actually found to exist. This means the recovery catalog or control file is out
of sync with reality.
Action:
Run CROSSCHECK. |
RMAN-20503
|
DELETE cannot delete expired objects - run CROSSCHECK or DELETE
EXPIRED
Cause: A DELETE command was run without EXPIRED option, but the
object doesn't exist. This means the recovery catalog or control file is out of
sync with reality.
Action:
Run CROSSCHECK. |
RMAN-20504
|
corruption list not found in recovery catalog
Cause: corruption list is empty
Action:
make sure that one or more blocks are marked corrupted in v$copy_corruption and
v$backup_corruption and recovery catalog is up-to-date. |
RMAN-20505
|
create datafile during recovery
Cause: applying of archived log caused a create datafile
redo-entry to to terminate recovery.
Action:
none. This message is never displayed. RMAN automatically detects this case and
creates the datafile. |
RMAN-20506
|
no backup of archivelog found
Cause: during the recover process, no backup was found from which
the archivelogs could be restored.
Action:
this message should be followed by a list of missing archivelogs. Please make
the necessary archivelog backups available and try again. |
RMAN-20507
|
some targets are remote - aborting restore
Cause: during the restore process, one or more backup files were
unavailable locally for the restore operation.
Action:
This message should be accompanied with the list of remote backup files. Recall
these backups from remote location and retry the RESTORE command. |
