Oracle 12c R2 Error Codes and Solution Suggestions from ORA-19500 to ORA-19700
- ORA-19500: device block size string is invalid
Cause: the device block size returned by sequential I/O OSD is invalid
Action: If the block size was set by using the PARMS option of the Recovery Manager ALLOCATE CHANNEL command, then the specified block size must be changed. If no PARMS option was specified on the ALLOCATE CHANNEL command, then this is an internal error that should be reported to Oracle.
Cause: read error on input file
Action: check the file
Cause: write error on output file
Action: check the file
Cause: call to get device information returned an error
Action: check device name, type and parameters
Cause: call to create file returned an error
Action: check additional messages, check access permissions.
Cause: call to identify the file returned an error
Action: check additional messages, and check if the file exists.
Cause: call to create the sequential file returned an error
Action: check additional messages, check access permissions.
Cause: call to retrieve the sequential file returned an error
Action: check additional messages, and check if the file exists.
Cause: call to delete the file returned an error
Action: check additional messages.
Cause: call to delete the sequential file returned an error
Action: check additional messages.
Cause: call to resize the file returned an error
Action: check additional messages.
Cause: An error occurred in the media management software which is linked with the Oracle server to perform backup and restore in cooperation with Recovery Manager.
Action: If the text of message 19511 does not provide enough information to resolve the problem, then you should contact the vendor of the media management software.
Cause: Recovery manager or Oracle Server attempted to discover files that matched the specified pattern but failed.
Action: Check errors on the error stack for an explanation why the search for files could not be successfully executed.
Cause: Unable to identify the sequential file.
Action: Check additional messages, and check if the file exists on media.
Cause: Opening a clone database failed because Oracle server forces the tempfile to be renamed, in order to avoid overwriting the primary tempfile.
Action: Rename the tempfiles manually or automatically by using the DB_FILE_NAME_CONVERT initialization parameter.
Cause: A list of default locations was provided in an Oracle-managed files parameter.
Action: Edit the parameter to include a single location.
Cause: An attempt was made to clear redo log at a physical standby database. Clearing an OMF redo log will not work unless DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_LOG_DEST_n or DB_RECOVERY_FILE_DEST parameter is specified. Clearing a non-OMF (or user-defined) redo log file will not work unless the LOG_FILE_NAME_CONVERT initialization parameter is set.
Action: Set DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_LOG_DEST_n or DB_RECOVERY_FILE_DEST parameter for OMF redo log files and re-issue the operation that attempted to clear redo log. Set LOG_FILE_NAME_CONVERT parameter for non-OMF redo log files and re-issue the operation that attempted to clear redo log.
Cause: The redo logs are being cleared. This procedure may need the files this operation is being applied to.
Action: Wait for the redo logs to be cleared.
Cause: An attempt was made to convert a database file name to an Oracle Managed Files file name using DB_FILE_NAME_CONVERT, PDB_FILE_NAME_CONVERT or LOG_FILE_NAME_CONVERT initialization parameter. This was not a valid operation.
Action: Retry the operation with a pattern template instead of a full Oracle Managed Files file name.
Cause: Attempted to use backup/restore functions while connected to the dispatcher in a shared 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 value of parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was not set within the valid range.
Action: Specify a correct value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST. If the archive log parameters LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST are in use, set parameter LOG_ARCHIVE_MIN_SUCCEED_DEST to either 1 or 2.
Cause: The destination for parameter LOG_ARCHIVE_DUPLEX_DEST was deferred when it was required to be enabled. The destination was deferred automatically when an ALTER SYSTEM command for parameter LOG_ARCHIVE_DEST defined a destination which duplicated an existing LOG_ARCHIVE_DUPLEX_DEST parameter destination.
Action: Change the destination value for the LOG_ARCHIVE_DUPLEX_DEST parameter.
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 name of device limit was specified in a call to DBMS_BACKUP_RESTORE.SETLIMIT.
Action: Use one of the device limit names described in dbmsbkrs.sql
Cause: The attempted command requires that a DISK device channel be allocated to the session, but a non-DISK device was found.
Action: Deallocate the current device and allocate a DISK channel, then then retry the command.
Cause: The indicated file, which is an archived log, control file, or datafile was found to be empty during a copy, backup, or scan] 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, to be inspected, or used as the target for an incremental restore, its header was not recognized as a valid file header for a file of the indicated type (datafile, archived log, or control file) belonging to the current database.
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: An attempt was made to specify duplexing to sequential devices, but the BACKUP_TAPE_IO_SLAVES initialization parameter was not enabled.
Action: Specify BACKUP_TAPE_IO_SLAVES=TRUE in the INIT.ORA file, or do not specify duplexing to sequential devices.
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: A device cannot be allocated to a session if another device is already allocated.
Action: Deallocate the current device
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.
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 control file.
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 backup, copy or restore 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. If the type is ‘read-only’, then you are attempting to back up or copy this file while the database is in NOARCHIVELOG mode.
Action: Wait until the conflicting operation is complete, then retry the copy or backup. If the database is in NOARCHIVELOG mode, then all files being backed up must be closed cleanly.
Cause: This type of copy or restore requires an output file name.
Action: Specify an output file name and retry the copy.
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 exists of the file that is being restored, 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, RESTOREDATAFILETO or PROXYRESTOREDATAFILE function specified a file number but no output file name, indicating that the output file name should be taken from the control file. However, the control file 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 control file cannot be used for restoration.
Action: Either specify an output file name or issue a SQL RENAME command to enter a valid name for this file in the control file.
Cause: An end of volume (EOV) condition was detected while duplexing to sequential files, and this condition cannot be handled currently.
Action: Before retrying the backup, make sure the backup pieces will fit in the volume, or disable duplexing.
Cause: No archived log record corresponding to input file could be found in the control file.
Action: Specify a valid archived log file name and retry the operation.
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: Archived log file header is corrupt and could not be validated.
Action: Provide a valid archived log file and 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, restore, or delete operation is already in use by the database.
Action: Specify a different name and retry the 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 for MAXPIECESIZE for this channel is not enough to hold the backup set control data.
Action: Allocate a channel specifying a larget valule for MAXPIECESIZE 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 wish to copy, then inspect it and then retry the copy specifying the new RECID.
Cause: The control file that is the source for a backup or copy operation is not a snapshot or backup control file.
Action: Specify the name of a snapshot or backup control file.
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: You tried to backup with duration option and the time provided was not sufficient to complete the backup.
Action: Adjust the duration time and re-run the command. Or run the backup command without duration option.
Cause: You attempted to specify a type of file to be backed-up or restored, but the current conversation cannot process this type of file. For example, you specified 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 control file is already specified for inclusion in this backup or restore conversation. A backup or restore conversation may process only a single instance of the control file.
Action: No action required – the conversation is still active, and more files can be specified.
Cause: The indicated archived log has already been specified for inclusion in this backup conversation.
Action: No action required – the conversation is still active, and more files can be specified.
Cause: The SPFILE is already specified for inclusion in this backup or restore conversation. A backup or restore conversation may process only a single instance of the SPFILE.
Action: No action required – the conversation is still active, and more files can be specified.
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: A backup command requested a backup of the SPFILE, but no SPFILE was used to startup the instance.
Action: Create an SPFILE and re-start the instance using the SPFILE.
Cause: A corrupt block was found in a control file, archived log, or backup piece that is being read for a backup or copy. Corruption shall not be tolerated in control files, archived logs, 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. For a datafile, the file number refers to the datafile’s absolute file number as shown in the DBA_DATA_FILES view. For a datafile copy, the file number refers to the copy’s control file record number as shown in the RECID column of the V$DATAFILE_COPY view. For an archived log, the file number refers to the log’s control file record number as shown in the RECID column of the V$ARCHIVED_LOG view.
Action: See other error message.
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 control file record number may not have been determined when the message is printed. In that case, the record number shown is zero.
Action: See other error message.
Cause: You tried 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.
Cause: The user tried to copy or backup a file that was not closed cleanly, with KEEP .. UNRECOVERABLE option. This is not allowed because when restored, the file will require redo application before it is usable, and redo will not be saved because of KEEP .. UNRECOVERABLE option.
Action: Take the tablespace offline cleanly, or close the database and retry the copy or backup.
Cause: A call was made to specify a file to be backed up or restored after the first backup piece has been processed.
Action: You cannot 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, you must begin a new conversation.
Cause: The input file name was not specified for a control file copy operation.
Action: Specify an input file name and retry the operation.
Cause: A control file copy or restore operation specified the name of the snapshot control file as the output file. It is not permitted to overwrite the snapshot control file in this manner. Other methods are available to create the snapshot control file.
Action: Specify a different file name and retry the operation. If this is a restore, then the restore conversation remains active and more files may be specified.
Cause: A control file copy, restore, or backup specified the name of a control file 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 may be specified.
Cause: The specified file is 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 is 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 control file.
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 that was not found.
Action: See the instructions for message 19613.
Cause: A datafile restore specified no target file name, but the database is not mounted. The database must be mounted when no target file name is specified, so that the target file name can be obtained from the control file.
Action: The restore conversation remains active. If you wish to restore datafiles without their target file names, then mount the database before continuing. Otherwise, a target file name 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 wish to specify files to restore.
Cause: RESTOREVALIDATE was called after some files had already been specified for restoration.
Action: You must cancel and restart the conversation if you wish to call RESTOREVALIDATE.
Cause: When opening the file to be placed in a copy or backup set, to be inspected, or used as the target for an incremental restore, its header was not recognized as a valid file header for a file of the indicated type (datafile, archived log, or control file) belonging to the current database.
Action: The indicated file cannot be processed. Ensure that the correct files are being specified for the copy or backup operation.
Cause: A range of logs has already been specified. Only one SCN range may be specified per conversation.
Action: The restore conversation remains active and more logs may 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 or not to retry the operation.
Cause: A file specified as input to a copy or backup operation, or as the target for an incremental restore, could not be identified as an Oracle file. The file may have been deleted or moved so that it is no longer accessible to RMAN. An operating system-specific error accompanies this error to help pinpoint the problem.
Action: Specify a different file and retry the operation. If the problem file has simply been deleted or moved, you can run crosscheck to allow RMAN to update its metadata with the correct file status.
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 control file restore conversation, which is using the offline range information from one or more control files to update datafile checkpoint data. Backup sets are not used during this type of conversation.
Action: The conversation is still active and more control files may 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 file system 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 archived log 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 archived log 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 control file.
Action: Supply a valid file name.
Cause: The control file record describing the file to be deleted in a call to DELETEBACKUPPIECE, DELETEDATAFILECOPY, PROXYDELETE or DELETEARCHIVEDLOG 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, DELETEREDOLOG or PROXYDELETE.
Action: Specify the FNAME or HANDLE 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 archived log has already been specified for inclusion in this restore conversation. A restore conversation may process only one copy of any archived log.
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 file name 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: See other error message.
Cause: This message identifies the checkpoint of a datafile in an incremental backup set that could not be applied.
Action: See other error message.
Cause: This message identifies the starting SCN of an incremental backup that could not be applied.
Action: See other error message.
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: Restore needs to adjust the size of the file as indicated, but the file size adjustment failed.
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. NOTE that this message will usually only be encountered by the user while taking an incremental backup with Recovery Manager. Recovery Manager should intercept all usual cases of this error and simply ignore the incremental backup for this file. So, if you do encounter this error, please report it to Oracle Support.
Cause: APPLYOFFLINERANGE was called with a RECID/STAMP which was not found in the indicated control file. This probably means that the specified control file is no longer the same control file that Recovery Manager thinks it is.
Action: Specify the RECID/STAMP of a record that exists in the control file copy.
Cause: This messages identifies the offline-clean SCN from the indicated offline-range record in the indicated file.
Action: See other 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 control file was backed up.
Action: Restore and mount an earlier control file. It is acceptable to use a control file 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 control file is not a backup control file.
Action: Restore and mount a backup control file.
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 control file 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 control file.
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. If you wish to recover the file to the RESETLOGS SCN so that the database can be opened with the RESETLOGS option, then you must 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 control file was included in an incremental restore conversation
Action: If you wish to restore the control file, you must do a full restore of the control file
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: A proxy copy procedure was called, but the device which is allocated to the current session has type DISK.
Action: Allocate a non-DISK channel and retry the operation. Note that proxy copy requires a 3rd-party media management software product that supports the this backup/restore feature.
Cause: A proxy restore function has already named this file as a restore destination.
Action: Use a different file name. If this message occurs during a recovery manager job, then this is an internal error in recovery manager, and you should contact Oracle support.
Cause: During a proxy backup or restore, the media management software returned an invalid file handle.
Action: This is an internal error in the media management software which is linked with Oracle to provide backup/restore services. Contact the media management software vendor.
Cause: During a proxy backup or restore, the media management software returned an invalid file status.
Action: This is an internal error in the media management software which is linked with Oracle to provide backup/restore services. Contact the media management software vendor.
Cause: During a proxy backup or restore, an error occurred while copying this file, but other files may have been copied successfully.
Action: There should be other errors on the error stack which explain why the file could not be successfully copied.
Cause: Recovery manager attempted to back up the specified file with proxy copy, but the file is already being backed up by another recovery manager job.
Action: Wait until the other recovery manager backup of this file is complete, then retry the backup.
Cause: A proxy backup of the specified file failed because the file was brought on-line or otherwise modified while the proxy backup was in progress. This file was off-line or read-only when the backup began, so the file was not put into hot-backup mode, therefore no modifications are permitted while the backup is in progress.
Action: Take another backup of this file.
Cause: During a proxy backup or restore, errors were encountered while processing some files. The files for which no error messages are shown were processed successfully.
Action: Examine the messages regarding the specific files to determine the cause of the problems.
Cause: The configuration name string exceeds maximum length.
Action: Supply a correct configuration name and retry the function.
Cause: The configuration value string exceeds maximum length.
Action: Supply a correct configuration value and retry the operation.
Cause: An invalid RMAN Configuration number was specified.
Action: Specify a correct datafile number and retry the operation.
Cause: Some blocks are not recovered during block media recovery.
Action: See trace files for details of the problem.
Cause: file number 0 specified in block media recovery
Action: check file number
Cause: Internal error
Action: n/a
Cause: block size changed between backup & real file
Action: use right backup
Cause: Database is suspended, probably by an ALTER SYSTEM SUSPEND statement
Action: Execute ALTER SYSTEM RESUME then retry block media recovery
Cause: Some data blocks for the SPFILE were corrupt in the backup set.
Action: Unless the damage to the backup set can be repaired, the SPFILE cannot be restored from this backup set.
Cause: The indicated file could not be restored, because some of its data blocks were not found in the backup piece.
Action: Unless the damage to the backup set can be repaired, the SPFILE cannot be restored from this backup set.
Cause: The SPFILE could not be restored, because it is not 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 in the piece. You must supply the first backup piece of a backup set that contains the requested file.
Cause: control file AUTOBACKUP format must contain %F for the device.
Action: Change control file format using RMAN command CONFIGURE CONTROLFILE BACKUP FORMAT FOR DEVICE TYPE type TO format.
Cause: control file AUTOBACKUP format contains more than one %F for the device.
Action: Change control file format using RMAN command CONFIGURE CONTROLFILE BACKUP FORMAT FOR DEVICE TYPE type TO format.
Cause: The backup piece was created by incompatible software.
Action: Either restart with a compatible software release or create another backup using the current release.
Cause: The database name or database id in backup piece header does not match the one in control file.
Action: Supply the correct backup piece belonging to this database.
Cause: The backup piece doesn’t have information about creation stamp.
Action: Supply another backup piece which is created by oracle 9i or later version.
Cause: This backup piece was already specified for inclusion in the restore conversation. A restore conversation may process only a single instance of a backup piece.
Action: Remove the specified duplicate backup piece in restore steps and restart the conversation.
Cause: A backup or copy found that some changed blocks had not been recorded in the change tracking file. The details of which files and blocks are affected will be in an Oracle trace file.
Action: This indicates that there is a problem with the change tracking feature. Disable change tracking and re-start the backup.
Cause: This is an internal error. The fixed table X$KRBMAFT was not populated using the function DBMS_BACKUP_RESTORE.SEARCHFILES.
Action: Internal error – contact Oracle Customer Support.
Cause: The control file could not be restored because it is not 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 in the piece. You must supply the first backup piece of a backup set that contains the requested file.
Cause: The standby control file could not be restored because it is not 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 in the piece. You must supply the first backup piece of a backup set that contains the requested file.
Cause: Catalog failed because the database id in file header does not match the one in control file.
Action: Supply the correct file belonging to this database.
Cause: Datafile copies with compression are not supported.
Action: If the function DBMS_BACKUP_RESTORE.BACKUPPIECECREATE is called outside RMAN, then the incompatible values are being passed for the parameters DOCOMPRESS and IMAGCP. If this message occurs during an RMAN job, then this is an internal error in RMAN, and you should contact Oracle support.
Cause: The device type indicated is invalid.
Action: Supply a correct device type and retry the allocation.
4,480 total views, 5 views today
Follow