ORA-19684: block media recovery failed because database is suspended

ORA-19684: block media recovery failed because database is suspended

Cause: Database is suspended, probably by an ALTER SYSTEM SUSPEND statement

Action: Execute ALTER SYSTEM RESUME then retry block media recovery

ORA-19683: real and backup blocksize of file string are unequal

ORA-19683: real and backup blocksize of file string are unequal

Cause: block size changed between backup real file

Action: use right backup

ORA-19682: file string not in block media recovery context

ORA-19682: file string not in block media recovery context

Cause: Internal error

Action: none

ORA-19681: block media recovery on control file not possible

ORA-19681: block media recovery on control file not possible

Cause: filenumber 0 specified in block media recovery

Action: check filenumber

ORA-19680: some blocks not recovered. See trace file for details

ORA-19680: some blocks not recovered. See trace file for details

Cause: Some blocks are not recovered during block media recovery.

Action: See trace files for details of the problem.

ORA-19679: RMAN configuration number string is outside valid range of 1 through string

ORA-19679: RMAN configuration number string is outside valid range of 1 through string

Cause: An invalid RMAN Configuration number was specified.

Action: Specify a correct datafile number and retry the operation.

ORA-19678: RMAN configuration value exceeds maximum length of string

ORA-19678: RMAN configuration value exceeds maximum length of string

Cause: The configuration value string exceeds maximum length.

Action: Supply a correct configuration value and retry the operation.

ORA-19677: RMAN configuration name exceeds maximum length of string

ORA-19677: RMAN configuration name exceeds maximum length of string

Cause: The configuration name string exceeds maximum length.

Action: Supply a correct configuration name and retry the function.

ORA-19676: one or more files failed during proxy backup or restore

ORA-19676: one or more files failed during proxy backup or restore

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.

ORA-19675: file string was modified during proxy copy

ORA-19675: file string was modified during proxy copy

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.

ORA-19674: file string is already being backed up with proxy copy

ORA-19674: file string is already being backed up with proxy copy

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.

ORA-19673: error during proxy copy of file string

ORA-19673: error during proxy copy of file string

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.

ORA-19672: media management software returned invalid file status

ORA-19672: media management software returned invalid file status

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 or restore services. Contact the media management software vendor.

ORA-19671: media management software returned invalid proxy handle

ORA-19671: media management software returned invalid proxy handle

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 or restore services. Contact the media management software vendor.

ORA-19670: file string already being restored

ORA-19670: file string already being restored

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.

ORA-19669: proxy copy functions cannot be run on DISK channel

ORA-19669: proxy copy functions cannot be run on DISK channel

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 or restore feature.

ORA-19668: cannot do full restore of datafile string

ORA-19668: cannot do full restore of datafile string

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

ORA-19667: cannot do incremental restore of datafile string

ORA-19667: cannot do incremental restore of datafile string

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

ORA-19666: cannot do incremental restore of the control file

ORA-19666: cannot do incremental restore of the control file

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

ORA-19665: size string in file header does not match actual file size of string

ORA-19665: size string in file header does not match actual file size of string

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.

ORA-19664: file type: string, file name: string

ORA-19664: file type: string, file name: string

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.

ORA-19663: cannot apply current offline range to datafile string

ORA-19663: cannot apply current offline range to datafile string

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.

ORA-19662: archived log thread string sequence string could not be verified

ORA-19662: archived log thread string sequence string could not be verified

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.

ORA-19661: datafile string could not be verified

ORA-19661: datafile string could not be verified

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.

ORA-19660: some files in the backup set could not be verified

ORA-19660: some files in the backup set could not be verified

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.

ORA-19659: incremental restore would advance file string past resetlogs

ORA-19659: incremental restore would advance file string past resetlogs

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.

ORA-19658: cannot inspect string - file is from different resetlogs

ORA-19658: cannot inspect string - file is from different resetlogs

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.

ORA-19657: cannot inspect current datafile string

ORA-19657: cannot inspect current datafile string

Cause: The file being inspected is already part of the currently mounted database.

Action: None - the file is already part of the database.

ORA-19656: cannot backup, copy, or delete online log string

ORA-19656: cannot backup, copy, or delete online log string

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.

ORA-19655: cannot switch to incarnation with different resetlogs data

ORA-19655: cannot switch to incarnation with different resetlogs data

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.

ORA-19654: must use backup control file to switch file incarnations

ORA-19654: must use backup control file to switch file incarnations

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.

ORA-19653: cannot switch to older file incarnation

ORA-19653: cannot switch to older file incarnation

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.

ORA-19652: cannot apply offline-range record to datafile string: file is fuzzy

ORA-19652: cannot apply offline-range record to datafile string: file is fuzzy

Cause: The target datafile for an applyOfflineRange call is fuzzy.

Action: Specify a target datafile that is closed cleanly.

ORA-19651: cannot apply offline-range record to datafile string: SCN mismatch

ORA-19651: cannot apply offline-range record to datafile string: SCN mismatch

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.

ORA-19650: Offline-range record recid string stamp string in file string has SCN string

ORA-19650: Offline-range record recid string stamp string in file string has SCN string

Cause: This messages identifies the offline-clean SCN from the indicated offline-range record in the indicated file.

Action: See other error message.

ORA-19649: offline-range record recid string stamp string not found in file string

ORA-19649: offline-range record recid string stamp string not found in file string

Cause: applyOfflineRange was called with a recid or 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 or stamp of a record that exists in the control file copy.

ORA-19648: datafile string: incremental-start SCN equals checkpoint SCN

ORA-19648: datafile string: incremental-start SCN equals checkpoint SCN

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.

ORA-19647: non-zero LEVEL cannot be specified when INCREMENTAL is FALSE

ORA-19647: non-zero LEVEL cannot be specified when INCREMENTAL is FALSE

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.

ORA-19646: cannot change size of datafile string from string to string

ORA-19646: cannot change size of datafile string from string to string

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.

ORA-19645: datafile string: incremental-start SCN is prior to creation SCN string

ORA-19645: datafile string: incremental-start SCN is prior to creation SCN string

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.

ORA-19644: datafile string: incremental-start SCN is prior to resetlogs SCN string

ORA-19644: datafile string: incremental-start SCN is prior to resetlogs SCN string

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.

ORA-19643: datafile string: incremental-start SCN is too recent

ORA-19643: datafile string: incremental-start SCN is too recent

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.

ORA-19642: start SCN of incremental backup is string

ORA-19642: start SCN of incremental backup is string

Cause: This message identifies the starting SCN of an incremental backup that could not be applied.

Action: See other error message.

ORA-19641: backup datafile checkpoint is SCN string time string

ORA-19641: backup datafile checkpoint is SCN string time string

Cause: This message identifies the checkpoint of a datafile in an incremental backup set that could not be applied.

Action: See other error message.

ORA-19640: datafile checkpoint is SCN string time string

ORA-19640: datafile checkpoint is SCN string time string

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.

ORA-19639: file string is more current than this incremental backup

ORA-19639: file string is more current than this incremental backup

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.

ORA-19638: file string is not current enough to apply this incremental backup

ORA-19638: file string is not current enough to apply this incremental backup

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.

ORA-19637: backupPieceCreate requires file name when using DISK device

ORA-19637: backupPieceCreate requires file name when using DISK device

Cause: The session device is currently allocated to disk, and so a file name is required.

Action: Supply a filename and retry the operation.

ORA-19636: archivelog thread string sequence string already included

ORA-19636: archivelog thread string sequence string already included

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.

ORA-19635: input and output filenames are identical: string

ORA-19635: input and output filenames are identical: string

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.

ORA-19634: filename required for this function

ORA-19634: filename required for this function

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.

ORA-19633: control file record string is out of sync with recovery catalog

ORA-19633: control file record string is out of sync with recovery catalog

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

ORA-19632: file name not found in control file

ORA-19632: file name not found in control file

Cause: The name passed to getFno was not found in the control file.

Action: Supply a valid filename.

ORA-19631: archivelog record contains no file name

ORA-19631: archivelog record contains no file name

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.

ORA-19630: end of volume encountered while copying backup piece

ORA-19630: end of volume encountered while copying backup piece

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.

ORA-19629: no files in specified archivelog SCN range

ORA-19629: no files in specified archivelog SCN range

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.

ORA-19628: invalid SCN range

ORA-19628: invalid SCN range

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.

ORA-19627: cannot read backup pieces during control file application

ORA-19627: cannot read backup pieces during control file application

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.

ORA-19626: backup set type is string - can not be processed by this conversation

ORA-19626: backup set type is string - can not be processed by this conversation

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.

ORA-19625: error identifying file string

ORA-19625: error identifying file string

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. An OS-specific error accompanies this error to help pinpoint the problem.

Action: Specify an different file and retry the operation.