Release 8.0.4
A58312-01
Library |
Product |
Contents |
Index |
| Oracle8
Error Messages
Release 8.0.4 A58312-01 |
|
Cause: Either:
Action: Use the SET CLONENAME command to specify
a filename that the clone database can use as a restore destination.
Cause: The controlfile mounted by the clone database
does not have an entry for this datafile, therefore filename conversion
is not possible.
Action: Use the SET CLONENAME command to specify
a filename that the clone database can use as a restore destination.
Cause: RMAN is attempting to use the specified filename
as a restore destination in the clone database, but this name is already
in use by the target database.
Action: Use the SET CLONENAME command to specify
a name for the datafile that does not conflict with a filename in use by
the target db.
Cause: Previously encountered error(s) were issued
which require corrective action.
Action: Resolve the error conditions, and then re-issue
the RECOVER command.
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.
06000-06999: KRMK Errors
Cause: The RECOVER.BSQ file could not be opened.
Action: Check that the file was installed correctly
and that the user running RMAN has authority to read the file.
Cause: A syntax error was encountered while parsing
RECOVER.BSQ.
Action: Ensure that the correct version of the file
is installed and that it has not been modified in any way.
Cause: A command that is allowed only when a recovery
catalog connect string was supplied was attempted.
Action: Avoid using the command, or restart RMAN
and supply a recovery catalog connect string via the RCVCAT parameter.
Cause: This message should be accompanied by other
error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
Cause: This message should be accompanied by other
error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
Cause: The target database has not mounted the controlfile,
and its INIT.ORA file does not specify the DB_NAME parameter.
Action: MOUNT the target database, or add the DB_NAME
parameter to its INIT.ORA and restart the instance.
Cause: An error occurred while looking up the specified
datafile in the recovery catalog or target database controlfile.
Action: This error is accompanied by other errors
describing the reason for the failure. Ensure that the filename is entered
correctly. If the datafile was added recently, then a RESYNC CATALOG must
be done to update the recovery catalog.
Cause: An invalid incremental backup level was specified.
Action: Incremental backup level must be between
0 and 8.
Cause: A RELEASE or SETLIMIT command was found for
a channel identifier that was not yet allocated.
Action: Correct the channel identifier, or add an
ALLOCATE CHANNEL command.
Cause: A channel identifier was reused without first
releasing the channel.
Action: Add a RELEASE CHANNEL command.
Cause: Not all commands are implemented for the beta
release.
Action: Avoid using the command.
Cause: An error occurred while looking up the specified
datafilecopy name in the recovery catalog or target database controlfile.
Action: This error is accompanied by other errors
describing the reason for the failure. Ensure that the filename is entered
correctly. If the datafile copy was created when the recovery catalog was
not available, then a RESYNC CATALOG must be done to update the recovery
catalog.
Cause: The specified operand appears more than once
in the same backup specifier or backup command.
Action: Delete the duplicate operand.
Cause: The parser package initialization routine
returned an error.
Action: This message should be accompanied by other
error message(s) indicating the cause of the error.
Cause: A backup spec operand appears more than once
in a backup specification.
Action: Delete the duplicate operand.
Cause: An error occurred while looking up the specified
tablespace name in the recovery catalog or target database controlfile.
Action: This error is accompanied by other errors
describing the reason for the failure. Ensure that the tablespace is entered
correctly. If the tablespace was added recently, then a RESYNC CATALOG
must be done to update the recovery catalog.
Cause: This is an informational message.
Cause: The FROM DATAFILECCOPY/BACKUPSET option applies
only to datafile and controlfile restores.
Action: Use this option only for datafile and controlfile
restores.
Cause: The FROM TAG option applies only to datafile
and controlfile restores.
Action: Use this option only for datafile and controlfile
restores.
Cause: A datafile, tablespace, or database restore
could not proceed because no backup or copy of the indicated file was found.
It may be the case that a backup or copy of this file exists but does not
satisfy the criteria specified in the user's restore operands.
Action: None - this is an informational message.
See message RMAN-06026 for further details.
Cause: A controlfile restore could not proceed because
no backup or copy of the controlfile was found. It may be the case that
a backup or copy of this file exists but does not satisfy the criteria
specified in the user's restore operands.
Action: None - this is an informational message.
See message RMAN-06026 for further details.
Cause: An archivelog restore could not proceed because
no backup of the indicated archived log was found. It may be the case that
a backup of this file exists but does not satisfy the criteria specified
in the user's restore operands.
Action: None - this is an informational message.
See message RMAN-06026 for further details.
Cause: Some of the files specified for restore could
not be found. Message RMAN-06023, RMAN-06024, or RMAN-06025 is also issued
to indicate which files could not be found. Some common reasons why a file
can not be restored are that there is no backup or copy of the file that
is known to recovery manager, or there are no backups or copies that fall
within the criteria specified on the RESTORE command, or some datafile
copies have been made but not cataloged.
Action: The Recovery Manager LIST command can be
used to display the backups and copies that Recovery Manager knows about.
Select the files to be restored from that list.
Cause: An archivelog record specifier did not match
any archivelogs in the recovery catalog.
Action: Resubmit the command with a different archivelog
record specifier. The Recovery Manager LIST command can be used to display
all archivelogs that Recovery Manager knows about.
Cause: The CHANNEL, TAG, FROM, VALIDATE, or PARMS
option was specified more than once in the restore command or in one of
the restore specifications.
Action: Correct and resubmit the command.
Cause: The INCLUDE CURRENT CONTROLFILE option was
specified for an archivelog backup set.
Action: Use this option only for datafile backup
sets.
Cause: The DELETE INPUT option was specified for
a backup that contains the current controlfile or datafiles.
Action: Remove the option and resubmit the command.
Cause: An error was received when calling DBMS_RCVMAN.
Action: This message should be accompanied by other
error message(s) indicating the cause of the error.
Cause: No channel of TYPE DISK was allocated.
Action: Allocate a channel of TYPE DISK and re-issue
the command.
Cause: A COPY, BACKUP, or RESTORE command requests
a specific channel, but the requested channel has not been allocated.
Action: ALLOCATE the channel, or correct the channel
identifier.
Cause: No channels are allocated.
Cause: The RECOVER.BSQ file is incompatible with
the RMAN executable.
Action: Install the correct version of RECOVER.BSQ.
Cause: A SET NEWNAME command was issued to restore
a datafile to a location other than the original datafile, and Recovery
Manager determined that the best candidate for restoring the file is the
datafile copy with the same name, therefore the file is already restored
and no action need be taken.
Action: None - this is an informational message.
Cause: An incremental backup of a datafile copy was
requested.
Action: Change the incremental level to 0, or request
a full backup.
Cause: A call to DBMS_RCVMAN returned an error.
Action: This message should be accompanied by other
error message(s) indicating the cause of the error.
Cause: A SWITCH command was specified for a datafile,
but no destination was specified and no SET NEWNAME command has been previously
issued for that file. An explicit file to switch to must be specified if
no SET NEWNAME command has been issued.
Action: Correct and resubmit the SWITCH command.
Cause: The best candidate controlfile for restoration
is the one that is named in the RESTORE (controlfile) command, hence no
action need be taken.
Action: None - this is an informational message.
Cause: An attempt was made to switch a datafile to
a copy of a different datafile.
Action: Correct and resubmit the SWITCH command.
Cause: The tag option was supplied but does not apply
to this type of backup.
Action: Remove the TAG operand and re-enter the command.
Cause: The TAG option was supplied but does not apply
to this type of copy.
Action: Remove the TAG operand and re-enter the command.
Cause: The specified operand appears more than once
in the same copy specification.
Action: Remove the redundant operand.
Cause: The LEVEL option was supplied but does not
apply to this type of copy.
Action: Remove the LEVEL operand and re-enter the
command.
Cause: An error occurred while translating an archivelog
name to its recovery catalog recid/timestamp. This message should be accompanied
by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
Cause: The indicated datafile was specified more
than once in the same restore command.
Action: Correct and resubmit the RESTORE command.
Cause: The controlfile was specified more than once
in the same RESTORE command.
Action: Correct and resubmit the RESTORE command.
Cause: A backup of a backup set was requested.
Action: Feature not implemented yet, so do not use
it.
Cause: An archivelog which was requested to be restored
(either explicitly or using a range specification) does not need to be
restored because it already exists on disk.
Action: None - this is an informational message.
Cause: This option was specified in a backup specification.
Action: Remove the DELETE INPUT option.
Cause: An incremental backup at level 1 or higher
could not find any parent backup or copy of the indicated datafile. A level
0 backup of the datafile will be taken automatically.
Action: This is an informational message only.
Cause: This message is accompanied with another message
identifying the missing log. The log would be needed to perform the media
recovery, but the log is not on disk and no backup set containing the log
is available.
Action: Determine if a backup set containing the
log can be made available. If so, then use the CHANGE command to make the
backup set available and retry the command. If not, then a point in time
recovery up to the missing log is the only alternative.
Cause: Media recovery is requesting a log whose existence
is not recorded in the recovery catalog or controlfile.
Action: If a copy of the log is available, then add
it to the recovery catalog and/or controlfile via a CATALOG command and
then retry the RECOVER command. If not, then a point in time recovery up
to the missing log is the only alternative.
Cause: A log which was on disk at the start of media
recovery or which should have been restored from a backup set could not
be found.
Action: Check the Recovery Manager message log to
see if the log was restored by a previous job step. If so, then check the
V$ARCHIVED_LOG view to see if the log is listed in the controlfile. If
so, then validate that the log exists on disk and is readable. If the log
was not restored, or was restored but no record of the log exists in V$ARCHIVED_LOG,
then contact Oracle support.
Cause: A backup could not proceed because the datafile
header could not be read or the header was not valid.
Action: Make the datafile accessible or skip it.
Cause: A RECOVER command was issued, but the target
database controlfile is not mounted.
Action: Mount the target database controlfile by
issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager.
Cause: The controlfile has been restored from a backup
or was created via ALTER DATABASE CREATE CONTROLFILE.
Action: Use the RECOVER DATABASE command to perform
the recovery.
Cause: This error should be accompanied by one or
more instances of message RMAN-06094.: Refer to message RMAN-06094.: RMAN-06069:
controlfile is missing the filename for datafile name
Cause: Media recovery of a backup controlfile added
this datafile to the controlfile, but it does not set the filename because
that is unsafe.
Action: If the datafile is on disk, then issue ALTER
DATABASE RENAME to correct the controlfile. Otherwise, RESTORE the datafile,
and then use SWITCH to make it known to the controlfile. If the tablespace
containing this datafile will be dropped, then reissue the RECOVER command
with a SKIP clause to skip recovery of this tablespace.
Cause: An error was encountered when trying to open
the specified datafile.
Action: Ensure that the datafile exists and is accessible.
Action: RESTORE the datafile to a new location, then
do a SWITCH, and then retry the RECOVER command.
Cause: ORACLE detected a corruption in the file header.
A media failure has probably occurred.
Action: RESTORE the datafile to a new location, then
do a SWITCH, and then retry the RECOVER command.
Cause: The file header indicates that this file is
not a datafile. The file may have been overlaid or corrupted.
Action: RESTORE the datafile to a new location, then
do a SWITCH, and then retry the RECOVER command.
Cause: The file header indicates that this file belongs
to some other ORACLE database.
Action: RESTORE the datafile to a new location, then
do a SWITCH, and then retry the RECOVER command.
Cause: The datafile header indicates the file contains
a different datafile number.
Action: RESTORE the datafile, and then retry the
RECOVER command.
Cause: The controlfile entry for this datafile specifies
a different version of this datafile. Different versions of a datafile
can exist when a tablespace is dropped, and a new tablespace is created
which reuses the same datafile numbers.
Action: If the datafile is correct, the fix the controlfile
by using the SWITCH command. Otherwise, RESTORE the correct version of
this datafile and retry the RECOVER command.
Cause: The controlfile appears to be older than the
specified datafile, but it is not marked as a backup controlfile. This
indicates that the controlfile has been replaced with an older version.
This error does not occur when a backup controlfile which was created via
Recovery Manager or the ALTER DATABASE BACKUP CONTROLFILE command is restored
because such controlfiles are marked as backups.
Action: RESTORE a controlfile and perform RECOVER
DATABASE.
Cause: A RECOVER command was issued, but the target
database is not mounted.
Action: Issue ALTER DATABASE MOUNT.
Cause: X$KCVFH returned the specified code in the
HXERR column when it was queried for the specified datafile.
Action: Ensure the datafile exists and is readable.
Using a more recent release of Recovery Manager may return a more meaningful
error message. If you do not have a more recent version of Recovery Manager,
contact Oracle support.
Cause: The specified tag refers to multiple datafile
copies belonging to different datafiles.
Action: Specify the datafilecopy by filename rather
than by tag.
Cause: The recovery catalog database returned an
error. This error explains the cause of the problem.
Action: Correct the problem and retry.
Cause: A REPLICATE command was issued, but the target
database is already mounted.
Action: Dismount the target database controlfile
by issuing ALTER DATABASE CLOSE and ALTER DATABASE DISMOUNT via Enterprise
Manager or Server Manager.
Cause: A RESTORE command for the specified datafile
could not find a destination name for the specified datafile.
Action: Add a SET NEWNAME command prior to the RESTORE
command to specify the restore destination for this file.
Cause: The SKIP OFFLINE option was specified for
an archivelog backup set.
Action: Use this option only for datafile backup
sets.
Cause: The SKIP READONLY option was specified for
an archivelog backup set.
Action: Use this option only for datafile backup
sets.
Cause: The indicated file is not found, or is found
but is not the same file that the recovery catalog thinks it is. It is
likely that some operation outside of Recovery Manager has altered the
file, or that Recovery Manager has not resynced with the target database.
Action: Re-catalog the file and retry the operation.
Cause: The indicated file is not found, or is found
but is not the same file that the recovery catalog thinks it is. It is
likely that some operation outside of Recovery Manager has altered the
file, or that Recovery Manager has not resynced with the target database.
Action: Re-catalog the file and retry the operation.
Cause: An error occurred while looking up the specified
controlfile copy in the recovery catalog or target database controlfile.
Action: This error is accompanied by other errors
describing the reason for the failure. Ensure that the filename is entered
correctly. If the controlfile copy was created when the recovery catalog
was not available, then a RESYNC CATALOG must be done to update the recovery
catalog.
Cause: No channel was allocated before executing
the CHANGE BACKUPPIECE DELETE command.
Action: Use ALLOCATE CHANNEL FOR DELETE before deleting
backup pieces.
Cause: An error occurred while looking up the specified
backup piece in the recovery catalog or target database controlfile.
Action: This error is accompanied by other errors
describing the reason for the failure. Ensure that the name or key is entered
correctly. If the backup piece was created when the recovery catalog was
not available, then a RESYNC CATALOG must be done to update the recovery
catalog.
Cause: The specified datafile number was dropped
and then reused. The controlfile mounted by the target database contains
the newer version of the datafile, but the recovery catalog contains information
about only the older version.
Action: Issue a RESYNC command to update the recovery
catalog, then reissue the failing command. If the error persists, contact
Oracle support.
Cause: A RECOVER command was issued, and the recovery
catalog indicates the specified datafile should be part of the recovery,
but this datafile is not listed in the controlfile, and cannot be found
on disk.
Action: Issue a RESTORE command for this datafile,
using the same UNTIL clause specified to the RECOVER command (if any),
then reissue the RECOVER.
Cause: The controlfile currently mounted by the target
database contains a newer incarnation of a datafile number than the recovery
catalog indicates is appropriate for the point-in-time being recovered
to.
Action: Restore the controlfile, using the same UNTIL
clause specified on the failing RECOVER command, then reissue the command.
If no controlfile can be restored, then you should issue a CREATE CONTROLFILE
command.
Cause: A SET NEWNAME was issued for this datafile,
but no SWITCH command was issued before the RECOVER command.
Action: Issue a SWITCH command to make the NEWNAME
take effect before doing RECOVER.
Cause: This is an informational message to accompany
message RMAN-06003 or RMAN-06004.: No action required.
Cause: A BACKUP command was issued, but the target
database controlfile is not mounted.
Action: Mount the target database controlfile by
issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager.
Cause: A datafile, tablespace, or database restore
could not proceed because the backup of the indicated file exists on a
device type that was not allocated for restore.
Action: None - this is an informational message.
See message RMAN-06026 for further details.: RMAN-06101: no channel to
restore a backup or copy of the controlfile
Cause: A controlfile restore could not proceed because
the backup of the indicated file exists on a device type that was not allocated
for restore.
Action: None - this is an informational message.
See message RMAN-06026 for further details.: RMAN-06102: no channel to
restore a backup or copy of log thread name seq num scn num
Cause: An archivelog restore could not proceed because
the backup of the indicated file exists on a device type that was not allocated
for restore.
Action: None - this is an informational message.
See message RMAN-06026 for further details.: RMAN-06103: duplicate qualifier
found in REPORT command: name
Cause: The indicated qualifier appears more than
once in a REPORT qualifier list.
Action: Delete the duplicate qualifier and retry
the operation.
Cause: Only one name specifier (like or all) may
be specified in the LIST command qualifier list.
Action: Correct and resubmit the command.
Cause: The indicated qualifier appears more than
once in a LIST qualifier list.
Action: Delete the duplicate qualifier and retry
the operation.
Cause: A command was issued that requires the target
database to be mounted, but the target database is not mounted.
Action: Mount the target database controlfile by
issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager.
Cause: The REPORT NEED BACKUP DAYS command may report
some files as requiring backups when they really do not, because the most
current online status of the file is not known unless a current controlfile
is mounted.
Action: No action required, however, a current controlfile
should be mounted, if possible, to get the most accurate REPORT output.
Cause: An error occurred while looking up the specified
datafilecopy key in the recovery catalog.
Action: This error is accompanied by other errors
describing the reason for the failure.
Cause: An error occurred while looking up the specified
archivelog key in the recovery catalog.
Action: This error is accompanied by other errors
describing the reason for the failure.
Cause: The indicated file will not be included in
the backup set because it is offline and the SKIP OFFLINE option was specified.
Action: No action required. This is an informational
message only.
Cause: The indicated file will not be included in
the backup set because it is read only and the SKIP READONLY option was
specified.
Action: No action required. This is an informational
message only.
Cause: The indicated file will not be included in
the backup set because it could not be read, and the SKIP INACCESSIBLE
option was specified.
Action: No action required. This is an informational
message only.
Cause: The specified channel id is invalid. DELETE
and DEFAULT are reserved channel names and may not be specified by users.
Action: Specify a different channel ID.
Cause: The snapshot controlfile name was not set,
so RMAN set it to the default value.
Action: No action required. This is an informational
message only.
Cause: The SKIP OFFLINE and SKIP READONLY options
are only permitted when the target database controlfile is current. When
the target controlfile is not current, it is not possible to obtain a datafile's
offline/readonly status.
Action: Remove the skip option or mount a current
controlfile on the target database.
Cause: A backup command was issued that includes
the specified datafile, but the datafile is not listed in the controlfile.
The controlfile is not current (it is a backup or a created controlfile).
Action: Recover the controlfile to make it current,
then retry the backup command.
Cause: A RESTORE UNTIL was issued, and the recovery
catalog choose an older incarnation of the datafile than is listed in the
controlfile.
Action: If the recovery catalog has correct data
for the datafile, then restore a backup controlfile using the same UNTIL
clause, then retry the datafile restore. Otherwise, restore a backup of
the incarnation of the datafile listed in the controlfile.
Cause: An operating system command has completed.
Action: None - this is an informational message.
Cause: A host command returned a non-zero return
code.
Action: Correct the offending command.
Cause: This message should be accompanied by other
error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
Cause: A 'REPORT SCHEMA at_clause' command was issued,
but there is no recovery catalog database.
Action: If you are not using a recovery catalog,
then you may only issue the 'REPORT SCHEMA' command with no at_clause.
Cause: A 'REPORT SCHEMA' with no at_clause was issued,
and there is no recovery catalog, and there is also no controlfile mounted
at the target database, so there is no place to get the information about
the current list of files comprising the database.
Action: Use a recovery catalog or mount a controlfile
at the target database.
Cause: A 'REPORT SCHEMA' with no at_clause was issued,
and there is no recovery catalog, and the controlfile mounted by the target
instance is not current, so the information about the current list of datafiles
may not be current.
Action: Use a recovery catalog or mount a current
controlfile.
Cause: The TAG option was specified with LIST INCARNATION.
This is not permitted because there is no TAG associated with a database
incarnation.
Action: Remove the TAG option and re-run the LIST
command.
Cause: The TAG option was specified with an ARCHIVELOG
list. This is not permitted because there is no TAG associated with archivelog
copies or backup sets.
Action: Remove the TAG option and re-run the LIST
command.
Cause: The DEVICE TYPE option was specified with
a list COPY or INCARNATION command. This is not permitted because only
backup sets may reside on different types of devices.
Action: Remove the DEVICE TYPE option and re-run
the LIST command.
Cause: The ALL or LIKE option was specified with
a list BACKUPSET or INCARNATION command. This is not permitted because
only copies of datafiles or archivelogs have filenames that may be tested
with a LIKE operand.
Action: Remove the LIKE or ALL option and re-run
the LIST command.
Cause: The FROM or UNTIL option was specified with
LIST INCARNATION. This is not permitted because there is no time associated
with a database incarnation.
Action: Remove the FROM or UNTIL option and re-run
the LIST command.
Cause: A CHANGE or REPORT command needs to compute
the list of backups that are redundant and may be deleted. If the mounted
controlfile is not current, it may not be possible to determine if a satisfactory
backup exists for files which have been offline since the last OPEN RESETLOGS.
Action: No action need be taken - this is an informational
message only. To ensure a complete report of obsolete backups, mount a
current controlfile.
Cause: A CHANGE or REPORT command needs to compute
the list of backups that are redundant and may be deleted. A backup was
found for a file which is shown as offline in the target database controlfile,
but the backup contains changes beyond the SCN when the file went offline.
This is most likely because the target database controlfile is not really
current, but is a restored copy of an older controlfile.
Action: Mount a current controlfile or a backup controlfile.
Cause: A CHANGE or REPORT command could find no files
that meet the specified criteria for obsoleteness.
Action: None - this is an informational message.
Cause: The REDUNDANCY operand specified for a CHANGE
or REPORT OBSOLETE command was zero.
Action: Specify a REDUNDANCY operand of 1 or greater.
Cause: A 'SET CLONENAME' command was issued, but
there is no recovery catalog database.
Action: If a recovery catalog exists, then specify
the RCVCAT option when starting Recovery Manager, otherwise the 'SET CLONENAME'
command may not be used.
Cause: This message is issued in response to a SET
CLONENAME command.
Action: None - this is an informational message.
Cause: This is an informational message. It should
be accompanied by other messages.
Cause: The CHANGE VALIDATE command may not be performed
on a backup piece.
Action: The CHANGE VALIDATE command may only be performed
on datafile copies and archived logs. To verify the contents of a backup
set, use the VALIDATE BACKUPSET command, which must be use inside of an
RMAN RUN command.
Cause: The CHANGE DATAFILE COPY VALIDATE command
found that the datafile copy could not be found or no longer contains the
same data, so its record was deleted from the recovery catalog.
Action: None - this is an informational message.
Cause: The CHANGE DATAFILE COPY VALIDATE command
found that the datafile copy still matches its data in the recovery catalog.
Action: None - this is an informational message.
Cause: The CHANGE CONTROLFILECOPY VALIDATE command
found that the controlfile copy could not be found or no longer contains
the same data, so its record was deleted from the recovery catalog.
Action: None - this is an informational message.
Cause: The CHANGE CONTROLFILECOPY VALIDATE command
found that the controlfile copy still matches its data in the recovery
catalog.
Action: None - this is an informational message.
Cause: The CHANGE ARCHIVELOG VALIDATE command found
that the archived log could not be found or no longer contains the same
data, so its record was deleted from the recovery catalog.
Action: None - this is an informational message.
Cause: The CHANGE ARCHIVED LOG VALIDATE command found
that the archived log still matches its data in the recovery catalog.
Action: None - this is an informational message.
Cause: An error occurred while looking up the specified
backup set in the recovery catalog or target database controlfile.
Action: This error is accompanied by other errors
describing the reason for the failure. Ensure that the key is entered correctly.
If the backup set was created when the recovery catalog was not available,
then a RESYNC CATALOG must be done to update the recovery catalog.
Cause: No backup pieces for the requested backup
set were found in the recovery catalog, or the target database controlfile.
Action: Specify an existing backup set.
Cause: This error is accompanied by other errors
explaining the cause.
Action: Correct the clonename if it is wrong via
the SET CLONENAME command.
Cause: This is the SQL statement about to be executed
for a SQL command.
Action: None, informational message only.
Cause: This message should be followed by one or
more RMAN-06162 or RMAN-06164 messages.: Use the additional messages to
pinpoint the error.
Cause: A RECOVER command could not proceed because
incremental backup sets or archive log 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.
Cause: Clone type was specified for the controlfile,
but no SET NEWNAME command has been previously issued for a datafile.
Action: Issue SET NEWNAME command for every datafile
in the recovery set.
Cause: A clone command was issued but no connection
to the clone database has been established.
Action: Issue a CONNECT CLONE command to connect
to the clone database.
Cause: A DELETE SCRIPT command was executed.
Cause: The initialization failed.
Action: This message should be accompanied by other
error message(s) indicating the cause of the error.
Cause: An ALLOCATE CHANNEL command could not be processed.
Action: This message should be accompanied by other
error message(s) indicating the cause of the error.
Cause: An error occurred during command execution.
Action: This message should be accompanied by other
error message(s) indicating the cause of the error.
Cause: An error occurred while releasing resources
associated with the specified channel.
Action: This message should be accompanied by other
error message(s) indicating the cause of the error.
Cause: An exception handling error occurred on the
specified channel.
Action: This message should be accompanied by other
error message(s) indicating the cause of the error.
Cause: The maximum number of RMAN channels has been
exceeded. Note that one channel is reserved for RMAN.
Action: Allocate fewer channels. Contact Oracle if
you have a need for more channels in a single job.
Cause: A datafile copy operation completed successfully.
Action: No action required. This is an informational
message only.
Cause: All of the backup pieces have been successfully
applied, but X$DBMS_BACKUP_RESTORE indicates that the restore conversation
is not complete. This usually means that the backup set contained corrupt
data.
Action: Restore the files from a different backup
set, if possible. The Recovery Manager CHANGE BACKUPPIECE UNAVAILABLE can
be used to prevent Recovery Manager from attempting to restore from the
corrupt backup piece(s).
Cause: The record that identifies the source file
for a copy or backup database does not contain the same data as is stored
in the recovery catalog.
Action: Perform a full resync and retry the operation.
If the problem persists, then contact Oracle.
Cause: The record identifying the named file was
no longer present in the target database controlfile, and repeated attempts
to inspect the file were unsuccessful in creating the record. This could
be because the circular-reuse section of the controlfile which holds information
about the specified type of file is too small and there is other database
activity which is causing the record to be overwritten before it can be
used.
Action: Try increasing either the size of the controlfile
circular-reuse section for this file type (datafile copy or archived log,
as indicated in the error message, or the CONTROL_FILE_RECORD_KEEP_TIME
initialization parameter. If neither of those remedies works then contact
Oracle.
Cause: This is an internal error that should never
be issued.
Action: Contact Oracle Worldwide Support.
Cause: The specified datafile has not had its checkpoint
advanced since the previous backup, therefore it does not need a new incremental
backup.
Action: No action required. This is an informational
message only.
Cause: All datafiles for this incremental backup
set were skipped, therefore no backup set is created.
Action: No action required. This is an informational
message only.
Cause: An invalid target connect string was supplied.
Action: Specify a valid connect string and re-run
the job.
Cause: An invalid recovery catalog connect string
was supplied.
Action: Specify a valid connect string and re-run
the job.
Cause: The specified Oracle error was received.
Action: This message should be accompanied by other
error message(s) indicating the cause of the error. Check the accompanying
errors.
Cause: Recovery manager was unable to connect to
the target database.
Action: This message should be accompanied by other
error message(s) indicating the cause of the error. Ensure that the target
database is started, and that the connect string is valid.
Cause: Recovery manager was unable to connect to
the recovery catalog.
Action: Ensure that the recovery catalog is started,
and that the connect string is valid. This message should be accompanied
by other error message(s) indicating the cause of the error.
Cause: An error was received while trying to open
a cursor. This message should be accompanied by other error message(s)
indicating the cause of the error.
Action: If the associated Oracle error message indicates
a condition that can be corrected, do so, otherwise contact Oracle Worldwide
Support.
Cause: An error message was received while running
the SQL statement shown.
Action: If the associated Oracle error message indicates
a condition that can be corrected, do so, otherwise contact Oracle.
Cause: An error was received while trying to close
a cursor. This message should be accompanied by other error message(s)
indicating the cause of the error.
Action: If the associated Oracle error message indicates
a condition that can be corrected, do so, otherwise contact Oracle.
Cause: An error was received while trying create
a channel context. This message should be accompanied by other error message(s)
indicating the cause of the error.
Action: If the associated Oracle error message indicates
a condition that can be corrected, do so, otherwise contact Oracle.
Cause: An error was received while disconnecting
from Oracle. This message should be accompanied by other error message(s)
indicating the cause of the error.
Action: No action required. This message is informational
only.
Cause: Recovery Manager's channel context had an
error while checking to see if a remote procedure call had completed. This
message should be accompanied by other error message(s) indicating the
cause of the error.
Action: If other error messages indicate a condition
that can be corrected, do so, otherwise contact Oracle.
Cause: Recovery Manager could not synchronize properly
with a remote procedure call.
Action: This is an internal error that should not
be issued. Contact Oracle Worldwide Support.
Cause: An error occurred while initializing the KGU
subsystem.
Action: This is an internal error that should not
be issued. Contact Oracle Worldwide Support.
Cause: An error occurred while initializing the PL/SQL
subsystem.
Action: This is an internal error that should not
be issued. Contact Oracle Worldwide Support.
Cause: This is a PL/SQL error.
Action: The text of this message will be issued by
the PL/SQL subsystem. See the PL/SQL error message manual.
Cause: An error occurred while compiling a PL/SQL
program.
Action: This is an internal error that should not
be issued. Contact Oracle Worldwide Support.
Cause: An error occurred while creating a PL/SQL
runtime context.
Action: This is an internal error that should not
be issued. Contact Oracle Worldwide Support.
Cause: An error was received while trying initialize
a channel context. This message should be accompanied by other error message(s)
indicating the cause of the error.
Action: If other error messages indicate a condition
that can be corrected, do so, otherwise contact Oracle Worldwide Support.
Cause: An error was received during inter-step cleanup
of a channel context.
Action: This is an internal error that should not
be issued. Contact Oracle Worldwide Support.
Cause: An error was received while initializing the
Recovery Manager execution layer in preparation for running a job. This
message should be accompanied by other error message(s) indicating the
cause of the error.
Action: If other error messages indicate a condition
that can be corrected, do so, otherwise contact Oracle Worldwide Support.
Cause: An error was received while waiting for a
remote RPC to complete. The error occurred in the system-dependent sleep
routine.
Action: This is an internal error that should not
be issued. Contact Oracle Worldwide Support.
Cause: The Recovery Manager internal RPC router received
a package name that it could not understand.
Action: This is an internal error that should not
be issued. Contact Oracle Worldwide Support.
Cause: The Recovery Manager could not create the
RPC polling context which is required to test for RPC completion. This
message should be accompanied by other error message(s) indicating the
cause of the error.
Action: If other error messages indicate a condition
that can be corrected, do so, otherwise Contact Oracle Worldwide Support.
Cause: The Recovery Manager could not enable the
target database connection to test for RPC completion.
Action: This is an internal error that should not
be issued. Contact Oracle Worldwide Support.
Cause: An network error occurred while attempting
to register the target database connection to test for RPC completion.
Action: This is an internal error that should not
be issued. The message numbers are issued by the Net8 layer. Contact Oracle
Worldwide Support.
Cause: Recovery Manager could not locate a necessary
context area while attempting to register the target database connection
to test for RPC completion.
Action: This is an internal error that should not
be issued. Contact Oracle Worldwide Support.
Cause: An network error occurred while waiting for
a remote RPC to complete.
Action: This is an internal error that should not
be issued. The message numbers are issued by the Net8 layer. Contact Oracle
Worldwide Support.
Cause: PL/SQL returned an unexpected return code
while executing one channel program.
Action: This is an internal error that should not
be issued. Contact Oracle Worldwide Support.
Cause: An RPC to a target database instance was issued,
but was not observed to start within 5 timeouts.
Action: This error is probably accompanied by other
error messages giving the precise cause of the failure.
Cause: An RPC to the target database or recovery
catalog database encountered an error.
Action: This error is accompanied with the error
message from the server where the error occurred.
Cause: An unhandled PL/SQL exception occurred during
a job step.
Action: This error is accompanied by the error messages
describing the exception.
Cause: PL/SQL detected a problem during the compilation
of a job step.
Action: This error message is accompanied by the
error messages describing the exception.
Cause: PL/SQL detected an unhandled exception during
execution of a job step, but no further information is available.
Action: Contact Oracle Worldwide Support.
Cause: A call to a remote package resulted in an
exception.
Action: The exception should indicate what went wrong.
Cause: This is just an informational message. It
should be preceded by message RMAN-10030.: No action required.
Cause: This is an debugging message and can be ignored.
Cause: The database connection for the specified
channel no longer exists. Either the session was terminated by some external
means or the channel terminated because of an internal error.
Action: Check for an Oracle trace file for detailed
information on why the session terminated.
Cause: This error should be accompanied by other
errors giving the cause of the polling error.
Cause: Recovery manager message file is out of date.
Action: Make sure that the recovery manager error
message file is current and installed in the correct location.
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: This error should be followed by other errors
indicating the cause of the problem.
Cause: The target database is not found in the recovery
catalog.
Action: Make sure that the target database is registered
in the recovery catalog.
Cause: The 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.
Cause: Resetlogs change number and/or time of the
target database does not match any database version in the recovery catalog.
Action: If the target database was opened with the
resetlogs option, then use RESET DATABASE to register the new version.
Cause: Name of the target database does not match
the one stored in the recovery catalog.
Action: This is an internal error, call Oracle Worldwide
Support.
Cause: Two or more databases in the recovery catalog
match the DB_NAME initialization parameter of the instance and the target
database is not mounted, so RMAN cannot get its DBID.
Action: Mount the target database then retry the
operation.
Cause: Target database instance is not started or
the DB_NAME initialization parameter is not set.
Action: Start the instance and make sure that the
DB_NAME parameter is set.
Cause: The database incarnation key was not specified.
Action: Specify a valid database incarnation key.
Cause: This incarnation of the database is already
registered in the recovery catalog.
Action: Informational only. No action required.
Cause: Database incarnation does not match any database
incarnation in the recovery catalog.
Action: Specify a valid database incarnation key.
Cause: The database incarnation that matches the
RESETLOGS CHANGE number and the time of the mounted target database controlfile
does not correspond to the current incarnation of the database.
Action: If RESET DATABASE TO INCARNATION key
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 controlfile using RMAN.
Otherwise use RESET DATABASE TO INCARNATION key make the intended
incarnation current in the recovery catalog.
Cause: Another operation that needs the snapshot
controlfile is in progress.
Action: Wait until the other operation completes.
Then retry the operation.
Cause: The recovery catalog has already been resynced
from a controlfile that has a higher checkpoint change number. If this
is RESYNC CATALOG command then the mounted controlfile has been restored
from an old backup. If this RESYNC CATALOG FROM CONTROLFILECOPY command
the specified controlfile copy is too old.
Action: If the right controlfile was mounted or specified
then RESYNC is not needed. Otherwise mount or specify the correct controlfile
and try again.
Cause: The recovery catalog has already been resynced
from a controlfile that has a higher checkpoint sequence#. If this is RESYNC
CATALOG command then the mounted controlfile has been restored from an
old backup. If this RESYNC CATALOG FROM CONTROLFILECOPY command the specified
controlfile copy is too old.
Action: If the right controlfile was mounted or specified
then RESYNC is not needed. Otherwise mount or specify the correct controlfile
and try again.
Cause: The control file has not changed since the
previous resync.
Action: Informational only. No action is needed because
the recovery catalog is in sync.
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.
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.
Cause: The specified log sequence does not exists
in log history of the current database incarnation.
Action: Check the THREAD and LOGSEQ. If the database
needs to be recovered to a log sequence number before the current database
incarnation, use RESET DATABASE TO INCARNATION command first.
Cause: UNTIL TIME can not be less than the database
creation time or resetlogs time.
Action: Check the UNTIL TIME. If the database needs
to be restored to an old incarnation, use RESET DATABASE TO INCARNATION
command.
Cause: UNTIL change can not be earlier 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.
Cause: Two datafiles have the same name. This is
an internal error.
Action: Contact Oracle Worldwide Support.
Cause: This is an internal error.
Action: Contact Oracle Worldwide Support. This is
an internal error
Cause: This is an internal error.
Action: Contact Oracle Worldwide Support. This is
an internal error
Cause: This is an internal error.
Action: Contact Oracle Worldwide Support. this is
an internal error
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.
Cause: This is an internal error.
Action: Contact Oracle Worldwide Support.
Cause: The specified controlfile is not in the recovery
catalog or it has been marked deleted.
Action: Check that the filename is correct and retry
the operation.
Cause: More than one controlfile copy in the recovery
catalog matches the specified name.
Action: Use the controlfile copy key to uniquely
specify the controlfile copy (not implemented in Beta2).
Cause: Either:
the specified datafile name is not the name that currently exists in
the target database an UNTIL clause was specified and the filename does
not correspond to the datafile
Action: Use a datafile number to specify the datafile
you want to RESTORE or RECOVER.
Cause: The specified datafile is not in the recovery
catalog or it has been marked deleted.
Action: Check the datafile copy name or key.
Cause: More than one controlfile copy in the recovery
catalog matches the specified name.
Action: Use the datafile copy key to uniquely specify
the datafile copy.
Cause: The specified TAG does not match any datafile
copy 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.
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.
Cause: No archivelogs in the specified archivelog
range could be found.
Action: Check the archive log specifier.
Cause: The specified offline was not found in the
recovery catalog.
Action: Check that the recovery catalog is current.
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.
Cause: More than one backup piece in the recovery
catalog matches the specified handle.
Action: Use the backup piece key to uniquely specify
the backup piece.
Cause: An illegal incremental backup level was requested.
Action: Valid incremental backup levels are 1 through
4. Specify a valid level.
Cause: An internal error occurred.
Action: Contact Oracle Worldwide Support.
Cause: No available backup or copy that could be
used as the parent of the incremental backup was found in the recovery
catalog.
Action: Perform a level 0 incremental backup or copy
of the datafile first.
Cause: More than 8 device types were allocated.
Action: Make sure that the job allocates at most
8 different device types.
Cause: The installed versions of the recovery catalog
and the DBMS_RCVCAT package are incompatible.
Action: Check that the recovery catalog packages
and schema are installed correctly. It may be necessary to run an upgrade
script to upgrade the recovery catalog schema.
Cause: The installed versions of the recovery catalog
and the DBMS_RCVMAN package are incompatible.
Action: Check that the recovery catalog packages
and schema are installed correctly. It may be necessary to run an upgrade
script to upgrade the recovery catalog schema.
Cause: An operation that requires a recovery catalog
was requested, but no recovery catalog is in use.
Action: If a recovery catalog is available, restart
RMAN and specify the a connect string for the recovery catalog database
via the RCVCAT parameter.
Cause: A CREATE SCRIPT or DELETE SCRIPT specified
a script name that could not be found.
Action: Check the script name.
Cause: A CREATE SCRIPT was issued, but a script with
the specified name already exists.
Action: Use a different name for the script or use
REPLACE SCRIPT.
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 datafilecopy 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.
