5000-5999 |
RMAN-05000
|
CONFIGURE AUXNAME required for datafile string
Cause:Either: -) The control file 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 the auxiliary
database can use as a restore destination. |
RMAN-05001
|
auxiliary filename string conflicts with a file used by the
target database
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 target db. |
RMAN-05002
|
aborting point-in-time tablespace recovery
Cause:Previously encountered error(s) were issued which require
corrective action.
Action:
Resolve the error conditions, and then re-issue the RECOVER command. |
RMAN-05003
|
point-in-time recovery is not allowed for tablespace string
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. |
RMAN-05004
|
target database log mode is NOARCHIVELOG
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. |
RMAN-05005
|
point-in-time recovery is not allowed for re-created tablespace
string
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. |
RMAN-05006
|
cannot recover clone standby single tablespaces
Cause:Standby recover can only be performed for the whole
database.
Action:
Change the tablespace list to a database specification. |
RMAN-05007
|
no channel allocated
Cause:A command was entered that requires a channel, and no
channel is allocated.
Action:
Use ALLOCATE CHANNEL before using the command |
RMAN-05008
|
SET NEWNAME TO NEW not allowed (datafile string)
Cause:SET NEWNAME ... TO NEW is not allowed with TSPITR.
Action:
Set the new name to a specific file name and retry. |
RMAN-05009
|
Block Media Recovery requires Enterprise Edition
Cause:The BLOCKRECOVER command was specified.
Action:
Remove the BLOCKRECOVER command. |
RMAN-05010
|
target database must be opened in READ WRITE mode for TSPITR
Cause:The target database was not opened in read write mode.
Action:
Open the database in read write mode. |
RMAN-05011
|
auxiliary instance must be in nomount state for TSPITR
Cause:The Auxiliary instance was not in nomount state.
Action:
Open the auxiliary instance in nomount state. |
RMAN-05012
|
trying to start the Oracle instance without parameter files ...
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. |
RMAN-05013
|
auxiliary control filename string conflicts with a file used by
the target database
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 by the target database. |
RMAN-05014
|
tablespaces with undo segments were not found in recovery
catalog
Cause:The recovery catalog did not have information about
tablespaces with undo segments.
Action:
Manually specify the tablespaces with undo segments in the optional UNDO
TABLESPACES clause of the RECOVER command. |
RMAN-05015
|
WARNING: not enough information in recovery catalog for
specified point in time recovery
Cause:The recovery catalog did not have information about the
tablespaces with undo segements at the specified point-in-time. This happened
because the current recovery catatog was not in use at the specified
point-in-time. A list of tablespaces with undo segments was supplied.
Action:
RMAN assumes that the current set of tablespaces with undo segments is the same
set that was in use at the specified point-in-time. If the set of tablespaces
with undo segments changes, the recovery fails. If recovery fails, use the
optional UNDO TABLESPACES clause of the RECOVER command to specify the correct
set of tablespaces. |
RMAN-05016
|
failover to previous backup
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/ control file/SPFILE using a previous
existing backup.
Action:
See accompanying additional error messages indicating the cause of the
failover. |
RMAN-05017
|
no copy of datafile number found to recover
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 on disk but no incremental backup was
found to apply to the datafile copy.
Action:One of the following: 1. Use or correct TAG specification
to recover a different datafile copy.
2. Use BACKUP FOR RECOVER OF COPY command to create necessary incremental
backup or copy. |
RMAN-05018
|
some datafile copies cannot be recovered, aborting the RECOVER
command
Cause:This error message can follow one or more RMAN-5017 or
RMAN-5019 error messages.
Action:
See RMAN-5017 or RMAN-5019 error message documentation for more information. |
RMAN-05019
|
WARNING: no channel of required type allocated to recover copy
of datafile number
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. |
RMAN-05020
|
cannot specify AUXILIARY DESTINATION option for normal recovery
Cause:The AUXILIARY DESTINATION option was specified for a normal
recovery. It is only allowed for tablespace point in time recovery.
Action:
Remove the AUXILIARY DESTINATION option and re-run the RECOVER command. |
RMAN-05021
|
this configuration cannot be changed for a BACKUP or STANDBY
control file
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 POLICY CONFIGURE EXCLUDE CONFIGURE
ARCHIVELOG DELETION POLICY
Action:
Connect to primary database instance and execute the command. |
RMAN-05022
|
TRANSPORT TABLESPACE may not be used with user-managed
auxiliary instance
Cause:A user-managed auxiliary instance was specified.
Action:
Retry the operation with an RMAN-managed auxiliary instance. |
RMAN-05023
|
TABLESPACE DESTINATION required
Cause:A required TABLESPACE DESTINATION was not specified.
Action:
Specify a TABLESPACE DESTINATION and retry the operation. |
RMAN-05024
|
List of tablespaces presumed to have UNDO segments
Cause:Accompanying message to 5015.
Action:
See action of message 5015. |
RMAN-05025
|
tablespace string
Cause:Accompanying message to 5015.
Action:
See action of message 5015. |
RMAN-05026
|
WARNING: presuming following set of tablespaces applies to
specified point in time
Cause:RMAN assumes that the current set of tablespaces with undo
segments is the same set that was in use at the specified point-in-time. If the
set of tablespaces with undo segments changes, the recovery fails. If recovery
fails, use the optional UNDO TABLESPACES clause of the RECOVER command to
specify the correct set of tablespaces.
Action:
RMAN assumes that the current set of tablespaces with undo segments is the same
set that was in use at the specified point-in-time. If the set of tablespaces
with undo segments changes, the recovery fails. If recovery fails, use the
optional UNDO TABLESPACES clause of the RECOVER command to specify the correct
set of tablespaces. |
RMAN-05027
|
List of tablespaces expected to have UNDO segments
Cause:Accompanying message to 5026.
Action:
See action of message 5026. |
RMAN-05028
|
tablespace string
Cause:Accompanying message to 5026.
Action:
See action of message 5026. |
RMAN-05029
|
UNDO TABLESPACE clause is only valid for Tablespace
Point-in-Time Recovery
Cause:The UNDO TABLESPACE clause was specified for non-Tablespace
Point-in-Time Recovery (TSPITR).
Action:
Remove the UNDO TABLESPACE clause. |
RMAN-05030
|
CLONE clause cannot be used with Tablespace Point-in-Time
Recovery
Cause:The CLONE clause was specified for a Tablespace
Point-in-Time Recovery (TSPITR).
Action:
Remove the CLONE clause. |
RMAN-05031
|
cannot specify UNDO TABLESPACES clause for normal recovery
Cause:The UNDO TABLESPACES clause was specified for a normal
recovery. It is only allowed for tablespace point in time recovery.
Action:
Remove the UNDO TABLESPACES clause and re-run the RECOVER command. |
RMAN-05032
|
data file string will be created automatically during restore
operation
Cause:The specified data file did not have an available backup.
Action:
None. This is an informational message displayed for VALIDATE or PREVIEW option
of the RESTORE command. |
RMAN-05033
|
Media recovery start SCN is string
Cause:The above SCN would be starting media recovery SCN, if the
specified files are restored.
Action:
None. This is an informational message displayed for PREVIEW option of the
RESTORE command. |
RMAN-05034
|
Recovery must be done beyond SCN string to clear data files
fuzziness
Cause:The above SCN identifies the minimum SCN beyond which the
media recovery must be performed on the specific data files to clear the media
recovery fuzziness for all data files.
Action:
None. This is an informational message displayed for PREVIEW option of the
RESTORE command. |
RMAN-05035
|
archive logs generated after SCN string not found in repository
Cause:The repository did not have a record of archived logs
containing the redo generated after the specified SCN.
Action:
None. To avoid this message, perform a log switch if the database is in open
mode. |
RMAN-05040
|
List of tablespaces that have been dropped from the target
database:
Cause:One or more tablespaces in the recovery set were not found
in the controlfile of the target database.
Action:
None. Informational message. |
RMAN-05041
|
Error during export of metadata
Cause:Export of metadata received an error from datapump.
Action:
This message is accompanied by other error message(s) indicating the cause of
the error. |
RMAN-05042
|
Error during import of metadata
Cause:Import of metadata received an error from datapump.
Action:
This message is accompanied by other error message(s) indicating the cause of
the error. |
RMAN-05043
|
tablespace string
Cause:Accompanying message to 5040.
Action:
See Action of message 5040. |
RMAN-05044
|
Performing export of metadata...
Cause:This is an informational message only.
Action:
No action is required. |
RMAN-05045
|
Performing import of metadata...
Cause:This is an informational message only.
Action:
No action is required. |
RMAN-05046
|
Export completed
Cause:This is an informational message only.
Action:
No action is required. |
RMAN-05047
|
Import completed
Cause:This is an informational message only.
Action:
No action is required. |
RMAN-05048
|
specified filename string conflicts with a file used by the
target database
Cause:The specified filename was already in use by another
datafile in the database.
Action:
Use SET NEWNAME command to specify a different name for the datafile that does
not conflict with a filename in use by the target database. |
RMAN-05049
|
datafile string is an Oracle Managed File, DB_CREATE_FILE_DEST
not set at target
Cause:A tablespace point-in-time recovery (tspitr) was attempted
but the datafile is an Oracle Managed File and DB_FILE_CREATE_DEST is not
currently set for the target database.
Action:
Specify DB_FILE_CREATE_DEST for the target database or provide a NEWNAME for
the specified datafile. |
RMAN-05500
|
the auxiliary database must be not mounted when issuing a
DUPLICATE command
Cause:A DUPLICATE command was issued, but the auxiliary database
is mounted.
Action:
Dismount the auxiliary database. |
RMAN-05501
|
aborting duplication of target database
Cause:Previously encountered errors require corrective action.
Action:
Resolve the error conditions, and reissue the DUPLICATE TARGET DATABASE
command. |
RMAN-05502
|
the target database must be mounted when issuing a DUPLICATE
command
Cause:A DUPLICATE command was issued, but the target database
control file is not mounted.
Action:
Mount the target database control file by issuing ALTER DATABASE MOUNT via
Enterprise Manager or Server Manager. |
RMAN-05503
|
at least one auxiliary channel must be allocated to execute
this command
Cause:No auxiliary channels were allocated.
Action:
Allocate an auxiliary channel. |
RMAN-05504
|
at least two redo log files or groups must be specified for
this command
Cause:Only one redo log file or group was specified
Action:
Specify at least one more redo log file or group |
RMAN-05505
|
auxiliary filename conversion of 'string' exceeds maximum
length of string
Cause:When the given filename is converted to the name used for
the auxiliary database, the converted name is larger than the maximum allowed
filename.
Action:
Change initialization parameter DB_FILE_NAME_CONVERT to convert to a valid
filename. |
RMAN-05506
|
error during recursive execution
Cause:This message should be accompanied by other error
message(s) indicating the cause of the error.
Action:
Check the accompanying errors. |
RMAN-05507
|
standby control file checkpoint (string) is more recent than
duplication point in time (string)
Cause:A DUPLICATE FOR STANDBY command was issued, but the
checkpoint of the control file is more recent than the last archivelog or the
specified point in time.
Action:
If an explicit point in time was specified, change it to be at least the
control file checkpoint; otherwise archive (and backup/copy) the current log. |
RMAN-05510
|
Duplicate finished
Cause:This is an informational message only.
Action:
No action is required. |
RMAN-05511
|
Datafile string skipped by request
Cause:This is an informational message only.
Action:
No action is required. |
RMAN-05512
|
tablespace string cannot be skipped from duplication
Cause:The SYSTEM and SYSAUX tablespaces were not included in the
duplicate database. They must be present.
Action:
Remove the SYSTEM and/or SYSAUX tablespace from the SKIP list and retry the
operation. |
RMAN-05513
|
cannot duplicate, control file is not current or backup
Cause:DUPLICATE requires that the target database has a current
control file.
Action:
Open the target database and retry operation. |
RMAN-05514
|
tablespace string has undo information, cannnot skip
Cause:All tablespaces that have undo information must be included
in the duplication.
Action:
Remove the specified tablespace from the SKIP list and retry the operation. |
RMAN-05515
|
Duplicate for standby does not allow the use of SET UNTIL
Cause:A SET UNTIL clause was specified for the command.
Action:
Remove the SET UNTIL clause and try again. |
RMAN-05516
|
duplicate operand specified: string
Cause:The specified operand appears more than once in the same
duplicate option list
Action:
Delete the duplicated operand. |
RMAN-05517
|
temporary file string conflicts with file used by target
database
Cause:RMAN attempted to use the specified temporary file as a
restore destination in the auxiliary database, but this name was already in use
by the target database.
Action:
Use the SET NEWNAME FOR TEMPFILE command to specify a name for the indicated
temporary file, making sure that the new name does not conflict with a filename
in use by target database. Alternatively, use DB_FILE_NAME_CONVERT and retry
the command. |
RMAN-05520
|
database name mismatch, auxiliary instance has string, command
specified string
Cause:The database name specified in the initialization parameter
was not the same as the database name provided in the DUPLICATE command.
Action:
Correct the database name in the command or adjust the database name of the
auxiliary instance. |
