Release 8.0.4
A58312-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 Error Messages Release 8.0.4 A58312-01 |
|
Cause: The device block size returned by sequential I/O OSD is invalid.
Action: Correct the block size and retry the operation.
Cause: A read error was detected on the input file.
Action: Check that the file is not corrupt and retry the operation.
Cause: A write error was detected on the output file.
Action: Check that the file is not corrupt and retry the operation.
Cause: A call to get device information returned an error. Most likely one or more of the following was entered incorrectly: device name, type, parameters.
Action: Check that the device name, type, and parameters are correct and retry the operation.
Cause: A call to create file returned an error.
Action: Check additional messages and access permissions, make the necessary corrections, then retry the operation.
Cause: A call to identify the file returned an error. Most likely the filename was entered incorrectly or the file does not exist.
Action: One or more other messages should be displayed to help pinpoint the cause of the error. Check if the file exists, then retry the operation.
Cause: A call to create the sequential file returned an error. Most likely the access permissions were set incorrectly.
Action: One or more other messages should be displayed to help pinpoint the cause of the error. Check access permissions and correct if necessary. Then retry the operation.
Cause: A call to retrieve the sequential file returned an error. Most likely the filename was entered incorrectly or the file does not exist.
Action: One or more other messages should be displayed to help pinpoint the cause of the error. Check if the filename was entered correctly and that the file exists. Then retry the operation.
Cause: A call to delete the file returned an error. Most likely the filename was entered incorrectly or the file does not exist.
Action: One or more other messages should be displayed to help pinpoint the cause of the error.
Cause: A call to delete the sequential file returned an error.
Action: One or more other messages should be displayed to help pinpoint the cause of the error.
Cause: A call to resize the file returned an error.
Action: One or more other messages should be displayed to help pinpoint the cause of the error.
Cause: Attempted to use BACKUP/RESTORE functions while connected to the dispatcher in a multi-threaded server. This is not allowed because the device that is used for backup and restore must remain allocated to a single process.
Action: Connect directly to the instance then re-execute the BACKUP or RESTORE function.
Cause: The indicated device could not be allocated because it is allocated to another session, or no device was named, or all devices of the requested type are busy.
Action: Either attempt to allocate another device or wait until the required device is no longer busy.
Cause: The device type indicated is invalid.
Action: Supply a correct device type and retry the allocation.
Cause: The device name indicated is invalid.
Action: Supply a correct device name and retry the allocation.
Cause: The specified device could not be allocated.
Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.
Cause: The initialization parameter LOG_ARCHIVE_MIN_SUCCEED_DEST is not within the valid range.
Action: Specify a correct value. If the database is in ARCHIVELOG mode with automatic archiving enabled, LOG_ARCHIVE_MIN_SUCCEED_DEST should be either 1 or 2.
Cause: LOG_ARCHIVE_DUPLEX_DEST has been disabled possibly due to failure to archive to that destination.
Action: Either
Cause: An error occurred in the platform-specific device code.
Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.
Cause: The specified device could not be de-allocated.
Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.
Cause: An error occurred while sending the indicated command to the session device.
Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.
Cause: An invalid type of device limit was specified in a call to X$DBMS_BACKUP_RESTORE.SETLIMIT.
Action: Use one of the documented limits: KBYTES, READRATE, or PARALLEL.
Cause: The attempted datafile, archivelog, or controlfile copy requires that a null device be allocated to the session, but a non-null device was found.
Action: Deallocate the current device and allocate a null device to the session, then retry the copy.
Cause: The indicated file, which is an archivelog, controlfile, or datafile was found to be empty during a copy, scan, or backup operation.
Action: Ensure that the correct files are being specified for the copy or backup operation.
Cause: When opening the file to be placed in a copy or backup set, or to be inspected, the header was not recognized as a valid file header for a file of the indicated type (datafile, archivelog, or controlfile), belonging to the current database, or perhaps the file does belong to the current database but has been changed since it was specified for inclusion in the backup set.
Action: Ensure that the correct files are being specified for the copy or backup operation.
Cause: An error occurred while writing to a file.
Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error if possible, then retry the copy, backup, or restore operation.
Cause: The user-specified limit of allowable corrupt blocks was exceeded while reading the specified datafile for a datafile copy or backup.
Action: None. The copy or backup operation fails. The session trace file contains detailed information about which blocks were corrupt.
Cause: An ALTER statement attempted to reduce the size of the indicated file while the same file is being backed up or copied.
Action: Retry the resize after the backup or copy is complete.
Cause: An attempt was made to allocate a device to a session while another device is already allocated.
Action: Deallocate the current device and retry the operation.
Cause: An operation was attempted which requires a device to be allocated to the current session, and there is no device allocated.
Action: Allocate a device then retry the operation.
Cause: A file number used in a COPY, BACKUP, or RESTORE operation is not valid for the current database.
Action: Specify a valid file number and retry the operation.
Cause: The input file specified for a COPY or BACKUP operation could not be opened because the record describing the file is not found in the controlfile.
Action: Specify a correct recid/stamp and retry the copy or backup.
Cause: The input file specified for a COPY or BACKUP operation could not be opened because the file is being resized.
Action: Wait for the resize to complete then retry the copy or backup.
Cause: The file access enqueue could not be obtained for a file specified in a COPY or BACKUP operation. If the enqueue type shown is "shared", then the file is the input file for a backup or copy. If the type is "exclusive", then the file is the output file for a datafile copy or restore which is attempting to overwrite the currently active version of that file. In this case, the file must be offline or the database must be closed.
Action: Wait until the conflicting operation is complete, then retry the COPY or BACKUP.
Cause: This type of COPY or RESTORE requires an output file name.
Action: Specify an output filename and retry the operation.
Cause: During a BACKUP, RESTORE, COPY or SCAN operation, the indicated file did not contain as many blocks as were indicated in the file header.
Action: The input copy or backup piece is probably corrupt. If another backup or copy of the file that is being restored exists, then the corrupt file can be deleted from the recovery catalog and the operation can be restarted.
Cause: The specified file number was not found in the control file.
Action: Specify a correct file number and retry the operation.
Cause: A copyDataFileCopy or restoreDataFileTo function specified a file number but no output file name, indicating that the output filename should be taken from the controlfile. However, the controlfile entry for this file indicates that it was created for a file that was present in the data dictionary but not named during the last CREATE CONTROLFILE statement, so the name in the controlfile cannot be used for restoration.
Action: Either specify an output filename or issue a SQL RENAME command to enter a valid name for this file in the controlfile.
Cause: A BACKUP or RESTORE operation was attempted before a conversation was started.
Action: Start a conversation then retry the operation.
Cause: An attempt was made to proceed from the file naming phase to the piece processing phase of a BACKUP or RESTORE conversation before any files have been specified for BACKUP or RESTORE.
Action: Specify some files then retry the operation.
Cause: An error occurred which forced the termination of the current BACKUP or RESTORE conversation.
Action: There should be other error messages to help identify the cause of the problem. Correct the error and begin another conversation.
Cause: The indicated file, which was specified as the target for a COPY or RESTORE operation is already in use by the database.
Action: Specify a different name and retry the COPY or RESTORE operation.
Cause: While creating the indicated backup piece, an end-of-volume condition was encountered before all of the backup set control data was written to the backup piece. This is most likely a media error, because the amount of backup set control data is very small in relation to the total amount of data in a backup set.
Action: Retry the piece with a larger piece of output media.
Cause: The user-specified limit of k-bytes per backup piece is not enough to hold the backup set control data.
Action: Use the SETLIMIT procedure to increase the k-byte limit and retry the operation.
Cause: An error occurred while reading from a file.
Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error then retry the COPY, BACKUP, or RESTORE operation.
Cause: The indicated record has been marked as deleted. This indicates that the corresponding file has either been overwritten by another copy or restore, or that the copy was "consumed" by a switchToCopy operation.
Action: If you know the name of the file you want to copy, then inspect it and then retry the copy specifying the new recid.
Cause: The controlfile that is the source for a backup or copy operation is not a SNAPSHOT or BACKUP controlfile.
Action: Specify the name of a SNAPSHOT or BACKUP controlfile.
Cause: You tried to begin a BACKUP or RESTORE conversation, but another conversation is already active in this session.
Action: Either continue the current conversation, or call backupCancel or restoreCancel to end the current conversation before starting a new one.
Cause: An attempt was made to specify a type of file to be backed-up or restored, but the current conversation cannot process this type of file. For example, an attempt was made to specify an archived log to be included in a datafile backup set. The specified file will not be included in the BACKUP or RESTORE operation.
Action: No action required - the conversation is still active, and more files can be specified.
Cause: This datafile is already specified for inclusion in this BACKUP or RESTORE conversation. A BACKUP or RESTORE conversation may process only a single instance of a datafile.
Action: No action required - the conversation is still active, and more files can be specified.
Cause: The controlfile is already specified for inclusion in this BACKUP or RESTORE conversation. A BACKUP or RESTORE conversation may process only a single instance of the controlfile.
Action: No action required - the conversation is still active, and more files can be specified.
Cause: The indicated archivelog has already been specified for inclusion in this backup conversation. A backup conversation may process only one copy of any archivelog.
Action: No action required - the conversation is still active, and more files can be specified.
Cause: An attempt was made to request that the snapshot controlfile be included in the backup set, but no snapshot controlfile has been created for this instance.
Action: Specify a different controlfile name, or call cfileMakeAndUseSnapshot to create the snapshot controlfile.
Cause: A file was specified for inclusion in a backup set but it has a logical block size different from the rest of the files in the backup set. All files in a backup set must have the same logical block size.
Action: Specify a file that has the same block size as the rest of the files in the backup set. The conversation is still active and more files can be specified.
Cause: No starting SCN was specified to backupDataFile or backupDataFileCopy, but the current backup conversation is for an incremental backup, which requires that a non-zero SCN be specified for all datafiles.
Action: The conversation is still active. Re-specify the datafile with a non-zero SCN.
Cause: A corrupt block was found in a controlfile, archivelog, or backup piece that is being read for a backup or copy. Corruption is not allowed in controlfiles, archivelogs, or backup pieces.
Action: None. The COPY or BACKUP operation fails. Note that in the case of a backup set, the conversation is still active and the piece may be retried.
Cause: This message identifies the input file for a failed copy operation. Both the file number and name (if the name has been determined) are shown.
Action: Other messages should display to help pinpoint the cause and the solution.
Cause: This message identifies the output file for a failed copy operation. The fields are as described in message 19600. When creating a new datafile copy, its controlfile record number may not have been determined when the message is printed. In that case, the record number shown is zero.
Action: Other messages should display to help pinpoint the cause and the solution.
Cause: An attempt was made to copy or backup a file that was not closed cleanly, and the database was in NOARCHIVELOG mode. This is not allowed because when restored, the file will require redo application before it is usable, and redo is not currently being saved beyond the contents of the online redo logs.
Action: Take the tablespace offline, clean or close the database, and retry the COPY or BACKUP operation.
Cause: A call was made to specify a file to be backed up or restored after the first backup piece has been processed.
Action: Do not specify more files to be processed during a BACKUP or RESTORE conversation after the first backup piece has been processed. If more files must be specified, begin a new conversation.
Cause: The input file name was not specified for a controlfile COPY operation.
Action: Specify an input filename and retry the operation.
Cause: A controlfile copy or restore operation specified the name of the snapshot controlfile as the output file. It is not permitted to overwrite the snapshot controlfile in this manner. Other methods are available to create the snapshot controlfile.
Action: Specify a different file name and retry the operation. If this is a RESTORE, then the RESTORE conversation remains active and more files can be specified.
Cause: A controlfile COPY, RESTORE, or BACKUP specified the name of a controlfile named in the INIT.ORA file as the input or output file.
Action: Specify a different file name and retry the operation. If this is a BACKUP or RESTORE conversation, then the conversation remains active and more files can be specified.
Cause: The specified file was not a backup piece produced by the DBMS_BACKUP_RESTORE package. Either the first block of the backup piece is corrupt or this file is not a backup piece.
Action: Specify a different file name and retry the operation.
Cause: The specified file was not from the backup set which is currently being processed. It is part of a different backup set. The identification of the set containing this piece is shown.
Action: Specify the correct backup piece and retry the operation.
Cause: The indicated directory block failed checksum validation. This backup piece is unusable.
Action: Supply another copy of the same backup piece, or terminate the RESTORE conversation.
Cause: This backup piece is out of sequence.
Action: Supply the correct backup piece.
Cause: The indicated file could not be restored, because all of its data blocks were not found in the backup piece.
Action: The restore conversation remains active, and the current piece must be re-processed. If the failure cannot be resolved by re-processing the current piece, then the RESTORE conversation must be cancelled.
Cause: The indicated file could not be restored, because it is not in this backup set. If the file number is zero, then this refers to the controlfile.
Action: This message is issued when the directory from the first backup piece is read and one or more files named for restoration were not found. The restore conversation is still active, but no data has been read and you must supply the first backup piece of a backup set that contains all of the requested files.
Cause: The indicated archived log file was named explicitly for restoration but is not contained in this backup set.
Action: This message is issued when the directory from the first backup piece is read and one or more files named for restoration were not found. The restore conversation is still active, but no data has been read and you must supply the first backup piece of a backup set that contains all of the requested files.
Cause: Some files that were specified for restoration were not found in the backup set directory. Message 19613 or 19614 is issued for each file not found.
Action: See the instructions for message 19613.
Cause: A datafile restore specified no target filename, but the database is not mounted. The database must be mounted when no target filename is specified, so that the target filename can be obtained from the controlfile.
Action: The restore conversation remains active. If you wish to restore datafiles without their target filenames, then mount the database before continuing. Otherwise, a target filename must be specified on all datafile restoration calls.
Cause: The indicated file contains resetlogs data which is different from the archived log files which are already included in the backup set. All archived log files in a backup set must have the same resetlogs data.
Action: The restore conversation remains active, and you may continue to specify archived log files for inclusion in the backup set.
Cause: A call was made to specify a file to restore from a backup set, but a previous call to restoreValidate has already been made.
Action: You must cancel and restart the conversation if you want to specify files to restore.
Cause: The restoreValidate operation was called after some files had already been specified for restoration.
Action: You must cancel and restart the conversation if you want to call restoreValidate.
Cause: You specified an archive log destination for restoreSetRedoLog which exceeds the system maximum.
Action: Retry the operation with a shorter archive log destination.
Cause: A range of logs has already been specified. Only one SCN range can be specified per conversation.
Action: The restore conversation remains active and more logs can be specified by thread and sequence number, if desired.
Cause: The indicated file could not be restored, because all of its data blocks were not found in the backup piece.
Action: The restore conversation remains active, and the current piece must be re-processed. If the failure cannot be resolved by re-processing the current piece, then the restore conversation must be cancelled.
Cause: A SwitchToCopy operation specified a datafile copy whose parent datafile is open.
Action: Take the owning tablespace offline or close the database, then retry the operation.
Cause: A BACKUP, RESTORE or IMAGE COPY operation failed with an I/O error. If the source of the I/O error can be corrected, then the operation may be retried.
Action: This message is used by recovery manager to decide whether to retry the operation.
Cause: A file specified as input to a COPY or BACKUP operation, or as the target for an incremental RESTORE, was not found.
Action: Specify an existing file and retry the operation.
Cause: The data in the backup set is not compatible with the current conversation.
Action: Either supply the first piece from a backup set that matches the current conversation or start a new RESTORE conversation which can process this backup set.
Cause: This is a controlfile RESTORE conversation, which is using the offline range information from one or more controlfiles to update datafile checkpoint data. Backup sets are not used during this type of conversation.
Action: The conversation is still active and more controlfiles can be applied.
Cause: The starting SCN for restoreRedoLogRange is greater than the ending SCN.
Action: Specify a starting SCN which is less than or equal to the ending SCN.
Cause: This backup set contains no files in the specified range.
Action: Either supply a backup set that contains files in the correct range or start a new conversation and specify a range which will select some files from this backup set.
Cause: While copying a backup piece from the OS native filesystem to an output device, the output device encountered end-of-volume.
Action: The copy fails. This could happen if a tape was used which is not large enough to hold the entire backup piece.
Cause: This archivelog record represents a switch into an active log that took place without archiving its prior contents. The prior contents of the log file are lost.
Action: Specify the RECID of an archivelog record that contains a file name. Fixed view V$ARCHIVED_LOG can be used to examine the archived logs.
Cause: The name passed to getFno was not found in the controlfile.
Action: Supply a valid filename and retry the operation.
Cause: The controlfile record describing the file to be deleted in a call to deletePiece, deleteDataFilecopy, or deleteRedoLog does not match the validation data supplied by recovery manager.
Action: Contact Oracle support.
Cause: The fname or handle parameter was not specified for deletePiece, deleteDataFileCopy, or deleteRedoLog.
Action: Specify the fname parameter when calling these functions.
Cause: Identical input and output file names were specified for a datafile copy operation.
Action: Specify an output file name which is different from the input file name.
Cause: The indicated archivelog has already been specified for inclusion in this RESTORE conversation. A RESTORE conversation may process only one copy of any archivelog.
Action: No action required - the conversation is still active, and more files can be specified.
Cause: The session device is currently allocated to disk, and so a file name is required.
Action: Supply a filename and retry the operation.
Cause: The checkpoint of the target for this incremental backup is less than the start of the incremental backup. If this backup were applied, then any changes made between the datafile checkpoint and the start of the incremental backup could be lost.
Action: Supply a backup set that can be applied and retry the operation.
Cause: The checkpoint of the target for this incremental backup is greater than or equal to the checkpoint of the file in the incremental backup set. This backup cannot advance the checkpoint of the target file, so there is no point in applying it.
Action: Supply a backup set that can be applied and retry the operation.
Cause: This message identifies the datafile checkpoint for a datafile that was too old to take an incremental backup from, or the target of an incremental restore that could not be applied.
Action: Examine the other messages which should be present to indicate the cause of the failure.
Cause: This message identifies the checkpoint of a datafile in an incremental backup set that could not be applied.
Action: Examine the other messages which should be present to indicate the cause of the failure.
Cause: This message identifies the starting SCN of an incremental backup that could not be applied.
Action: Examine the other messages which should be present to indicate the cause of the failure.
Cause: The incremental-start SCN which was specified when starting an incremental datafile backup is greater than the datafile checkpoint SCN, which could cause some blocks to be missed.
Action: Specify a smaller incremental-start SCN.
Cause: The incremental-start SCN which was specified when starting an incremental datafile backup is less than the resetlogs SCN.
Action: Specify a larger incremental-start SCN.
Cause: The incremental-start SCN which was specified when starting an incremental datafile backup is less than the datafile's creation SCN.
Action: Specify a larger incremental-start SCN.
Cause: The indicated file was resized before this incremental backup was taken, but the incremental backup failed to set the file to the new size.
Action: Examine the other messages which should be present to indicate the cause of the failure.
Cause: BackupSetDataFile was called with a non-zero BACKUP_LEVEL and a FALSE incremental indication.
Action: Either set incremental to TRUE or change BACKUP_LEVEL to zero.
Cause: The incremental-start SCN which was specified when starting an incremental datafile backup is equal to the datafile's checkpoint SCN. Since an incremental backup can only be applied to a datafile whose checkpoint SCN is between the backup set incremental-start SCN (inclusive) and the backup set checkpoint SCN (exclusive), there is no datafile that this backup set could ever be applied to.
Action: Specify a smaller incremental-start SCN.
Cause: applyOfflineRange was called with a recid/stamp which was not found in the indicated controlfile. This probably means that the specified controlfile is no longer the same controlfile that Recovery Manager thinks it is.
Action: Specify the recid/stamp of a record that exists in the controlfile copy.
Cause: This messages identifies the offline-clean SCN from the indicated offline-range record in the indicated file.
Action: See the accompanying error message.
Cause: applyOfflineRange cannot apply an offline-range record to a target datafile unless the datafile's checkpoint SCN exactly matches the offline-clean SCN in the specified offline-range record.
Action: Specify an offline-range record whose offline-clean SCN matches the target datafile's checkpoint.
Cause: The target datafile for an applyOfflineRange call is fuzzy.
Action: Specify a target datafile that is closed cleanly.
Cause: SwitchToCopy was called with a datafile copy for a datafile that was dropped prior to the time this controlfile was backed up.
Action: Restore and mount an earlier controlfile. It is acceptable to use a controlfile that was backed up prior to the creation of the specified datafile.
Cause: This switchToCopy operation is attempting to switch incarnations of a datafile, but the currently mounted controlfile is not a backup controlfile.
Action: Restore and mount a backup controlfile.
Cause: This switchToCopy operation is attempting to switch to a datafile which comes from a different resetlogs version of the database.
Action: Either restore a backup controlfile that was taken from the same database version as the target datafile-copy, or switch to a different datafile-copy.
Cause: The indicated log file is an active log. You can only backup, copy, or delete archived logs.
Action: The indicated log file cannot be processed - select another file.
Cause: The file being inspected is already part of the currently mounted database.
Action: None - the file is already part of the database.
Cause: The resetlogs data in the log file being inspected does not match that in the currently mounted controlfile.
Action: The indicated file cannot be processed - inspect another file.
Cause: This incremental backup cannot be applied to the specified datafile, because the datafile is from an earlier incarnation of the database, and its checkpoint would be advanced too far to be recoverable in the current incarnation of the database.
Action: This incremental cannot be applied to this datafile. To recover the file to the resetlogs SCN so that the database can be opened with the RESETLOGS option, use redo-log recovery, not incremental restore, to continue recovering this file.
Cause: A restore conversation was made to verify all the files in a backup set, and the files which were printed in messages 19661 or 19662 could not be verified because corrupt blocks for those files were found in the backup set.
Action: Unless the damage to the backup set can be repaired, the indicated files cannot be restored from this backup set.
Cause: Some data blocks for the indicated datafile were corrupt in the backup set.
Action: Unless the damage to the backup set can be repaired, the indicated datafile cannot be restored from this backup set.
Cause: Some data blocks for the indicated archived log were corrupt in the backup set.
Action: Unless the damage to the backup set can be repaired, the indicated archived log cannot be restored from this backup set.
Cause: An attempt was made to apply the current offline range to the specified datafile, but the datafile is either not current enough or is not at the correct SCN to apply the offline range.
Action: The datafile remains unchanged.
Cause: This message is issued to identify the file which is the subject of an error.
Action: None - this is an informational message. There should be other Oracle messages explaining the cause of the error.
Cause: The size of the file as indicated in the file header does not match the true size of the file. The two differing sizes are shown in units of logical blocks.
Action: This file is not usable - it has most likely been truncated.
Cause: The controlfile was included in an incremental restore conversation.
Action: If you wish to restore the controlfile, you must do a full restore of the controlfile.
Cause: The backup of the datafile is a full backup.
Action: If you wish to restore the datafile, you must do a full restore of the datafile.
Cause: The backup of the datafile is an incremental backup.
Action: If you wish to restore the datafile, you must do an incremental restore of the datafile.
Cause: The device type indicated is invalid.
Action: Supply a correct device type and retry the allocation.
Cause: The device name indicated is invalid.
Action: Supply a correct device name and retry the allocation.
Cause: The device parameter exceeds the port-specific maximum length.
Action: Correct the parameter and retry the operation.
Cause: The device command string exceeds maximum length.
Action: Correct the command and retry the operation.
Cause: The specified file name, which was a parameter to a COPY, BACKUP, or RESTORE operation, exceeds the maximum file name length for this operating system.
Action: Retry the operation with a shorter file name.
Cause: The specified file name, which was a parameter to a COPY, BACKUP, or RESTORE operation, exceeds the maximum file name length for this operating system.
Action: Retry the operation with a shorter file name.
Cause: During a BACKUP or COPY operation, the user supplied a tag value too long to fit in the file header.
Action: Supply a shorter tag and retry the operation.
Cause: The input SCN is either not a positive integer or too large.
Action: Check the input SCN and make sure it is a valid SCN.
Cause: The input number is either negative or too large.
Action: Check the input record block number and make sure it is a valid number clauses in the create database statement.
Cause: When starting a RESTORE conversation, a log restore destination longer than the port-specific maximum was specified.
Action: Supply a shorter destination and retry the operation.
Cause: A numeric parameter to an X$DBMS_BACKUP_RESTORE procedure is negative or contains a fractional portion.
Action: Supply a valid numeric parameter.
