Cause: the device block size returned by sequential I/O OSD is invalid

Cause: read error on input file

Cause: write error on output file

Cause: call to get device information returned an error

Cause: call to create file returned an error

Cause: call to identify the file returned an error

Cause: call to create the sequential file returned an error

Cause: call to retrieve the sequential file returned an error

Cause: call to delete the file returned an error

Cause: call to delete the sequential file returned an error

Cause: call to resize the file returned an error

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.

Cause: Recovery manager or Oracle Server attempted to discover files that matched the specified pattern but failed.

Cause: Unable to identify the sequential file.

Cause: Opening a clone database failed because Oracle server forces the tempfile to be renamed, in order to avoid overwriting the primary tempfile.

Cause: A list of default locations was provided in an Oracle-managed files parameter.

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.

Cause: The redo logs are being cleared. This procedure may need the files this operation is being applied to.

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.

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.

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.

Cause: The device type indicated is invalid.

Cause: The device name indicated is invalid.

Cause: The specified device could not be allocated.

Cause: The value of parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was not set within the valid range.

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.

Cause: An error occurred in the platform-specific device code

Cause: The specified device could not be de-allocated.

Cause: An error occurred while sending the indicated command to the session device.

Cause: An invalid name of device limit was specified in a call to DBMS_BACKUP_RESTORE.SETLIMIT.

Cause: The attempted command requires that a DISK device channel be allocated to the session, but a non-DISK device was found.

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.

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.

Cause: An error occurred while writing to a file.

Cause: An attempt was made to specify duplexing to sequential devices, but the BACKUP_TAPE_IO_SLAVES initialization parameter was not enabled.

Cause: The user specified limit of allowable corrupt blocks was exceeded while reading the specified datafile for a datafile copy or backup.

Cause: An ALTER statement attempted to reduce the size of the indicated file while the same file is being backed up or copied.

Cause: A device cannot be allocated to a session if another device is already allocated.

Cause: An operation was attempted which requires a device to be allocated to the current session, and there is no device allocated.

Cause: A file number used in a copy, backup, or restore operation is not valid for the current database.

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.

Cause: The input file specified for a copy or backup operation could not be opened because the file is being resized.

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.

Cause: This type of copy or restore requires an output file name.

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.

Cause: The specified file number was not found in the control file.

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.

Cause: An end of volume (EOV) condition was detected while duplexing to sequential files, and this condition cannot be handled currently.

Cause: No archived log record corresponding to input file could be found in the control file.

Cause: A backup or restore operation was attempted before a conversation was started.

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.

Cause: Archived log file header is corrupt and could not be validated.

Cause: An error occurred which forced the termination of the current backup or restore 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.

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.

Cause: The user-specified limit for MAXPIECESIZE for this channel is not enough to hold the backup set control data.

Cause: An error occurred while reading from a file.

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.

Cause: The control file that is the source for a backup or copy operation is not 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.

Cause: You tried to backup with duration option and the time provided was not sufficient to complete the backup.

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.

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.

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.

Cause: The indicated archived log has already been specified for inclusion in this backup conversation.

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.

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.

Cause: A backup command requested a backup of the SPFILE, but no SPFILE was used to startup the instance.

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.

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.

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.

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.

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.

Cause: A call was made to specify a file to be backed up or restored after the first backup piece has been processed.

Cause: The input file name was not specified for a control file copy 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.

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.

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.

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.

Cause: The indicated directory block failed checksum validation. This backup piece is unusable.

Cause: This backup piece is out of sequence.

Cause: The indicated file could not be restored, because all of its data blocks were not found in the backup piece.

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.

Cause: The indicated archived log file was named explicitly for restoration but is not contained in this backup set.

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.

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.

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.

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.

Cause: RESTOREVALIDATE was called after some files had already been specified for restoration.

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.

Cause: A range of logs has already been specified. Only one SCN range may be specified per conversation.

Cause: The indicated file could not be restored, because all of its data blocks were not found in the backup piece.

Cause: A SWITCHTOCOPY operation specified a datafile copy whose parent datafile is open.

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.

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.

Cause: The data in the backup set is not compatible with the current conversation.

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.

Cause: The starting SCN for RESTOREREDOLOGRANGE is greater than the ending SCN.

Cause: This backup set contains no files in the specified range.

Cause: While copying a backup piece from the OS native file system to an output device, the output device encountered end-of-volume.

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.

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

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.

Cause: The FNAME or HANDLE parameter was not specified for DELETEPIECE, DELETEDATAFILECOPY, DELETEREDOLOG or PROXYDELETE.

Cause: Identical input and output file names were specified for a datafile copy operation.

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.

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

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.

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.

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.

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

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

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.

Cause: The incremental-start SCN which was specified when starting an incremental datafile backup is less than the RESETLOGS SCN.

Cause: The incremental-start SCN which was specified when starting an incremental datafile backup is less than the datafile's creation SCN.

Cause: Restore needs to adjust the size of the file as indicated, but the file size adjustment failed.

Cause: BACKUPSETDATAFILE was called with a non-zero backup_level and a FALSE incremental indication.

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.

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.

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

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.

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

Cause: SWITCHTOCOPY was called with a datafile copy for a datafile that was dropped prior to the time this control file was backed up.

Cause: This SWITCHTOCOPY operation is attempting to switch incarnations of a datafile, but the currently mounted control file is not 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.

Cause: The indicated log file is an active log. You can only backup, copy, or delete archived logs.

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

Cause: The RESETLOGS data in the log file being inspected does not match that in the currently mounted control 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.

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.

Cause: Some data blocks for the indicated datafile were corrupt in the backup set.

Cause: Some data blocks for the indicated archived log were corrupt in the 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.

Cause: This message is issued to identify the file which is the subject of an 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.

Cause: The control file was included in an incremental restore conversation

Cause: The backup of the datafile is a full backup

Cause: The backup of the datafile is an incremental backup

Cause: A proxy copy procedure was called, but the device which is allocated to the current session has type DISK.

Cause: A proxy restore function has already named this file as a restore destination.

Cause: During a proxy backup or restore, the media management software returned an invalid file handle.

Cause: During a proxy backup or restore, the media management software returned an invalid file status.

Cause: During a proxy backup or restore, an error occurred while copying this file, but other files may have been copied successfully.

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.

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.

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.

Cause: The configuration name string exceeds maximum length.

Cause: The configuration value string exceeds maximum length.

Cause: An invalid RMAN Configuration number was specified.

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

Cause: file number 0 specified in block media recovery

Cause: Internal error

Cause: block size changed between backup & real file

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

Cause: Some data blocks for the SPFILE were corrupt in the backup set.

Cause: The indicated file could not be restored, because some of its data blocks were not found in the backup piece.

Cause: The SPFILE could not be restored, because it is not in this backup set.

Cause: control file AUTOBACKUP format must contain %F for the device.

Cause: control file AUTOBACKUP format contains more than one %F for the device.

Cause: The backup piece was created by incompatible software.

Cause: The database name or database id in backup piece header does not match the one in control file.

Cause: The backup piece doesn't have information about creation stamp.

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.

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.

Cause: This is an internal error. The fixed table X$KRBMAFT was not populated using the function DBMS_BACKUP_RESTORE.SEARCHFILES.

Cause: The control file could not be restored because it is not in this backup set.

Cause: The standby control file could not be restored because it is not in this backup set.

Cause: Catalog failed because the database id in file header does not match the one in control file.

Cause: Datafile copies with compression are not supported.

Cause: The device type indicated is invalid.

Cause: The device name indicated is invalid.

Cause: The device command string exceeds maximum length.

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.

Cause: During a backup or copy operation, the user supplied a tag value too long to fit in the file header.

Cause: The input SCN is either not a positive integer or too large.

Cause: The input number is either negative or too large.

Cause: When starting a restore conversation, the user specified a log restore destination longer than the port-specific maximum.

Cause: A numeric parameter to an DBMS_BACKUP_RESTORE procedure is negative or contains a fractional portion.

Cause: When the target database is not mounted, RMAN sets the target database character set to the value specified in the users environment.

Cause: An attempt was made to re-normalize all the file names in the control file while the database is open.

Cause: The table name string exceeds maximum length.

Cause: The copy number is not in a valid range or you have reached maximum limit.

Cause: The specified format exceeds the maximum length for the piece name.

Cause: A restricted format or undefined format was used incorrectly.

Cause: There were errors while processing the format to generate name for backup.

Cause: The procedure DBMS_BACKUP_RESTORE.SEARCHFILES was called with an empty pattern while the parameter OMF was set to FALSE.

Cause: The specified command id exceeds the maximum length for command id.

Cause: The specified operation name exceeds the maximum length for operation name.

Cause: This is most likely caused by an invalid SCN number that came from an external file, such as an export file.

Cause: Can not find one of the datafile that should be in the Pluggable Set.

Cause: The datafile is an incorrect version. It contains either less or more changes then the desired version.

Cause: The datafile is plugged in read only. It can not recreated.

Cause: The snapshot SCN is before the SCN at which the referred datafile is plugged into the database.

Cause: There maybe another "ALTER DATABASE RESET COMPATIBILITY" command issued concurrently, preventing this process from acquiring the plug-in enqueue.

Cause: Some of the data in the pluggable set requires a compatibility level higher than what is currently allowed by the database. The string in square bracket is the name of the compatibility type associated with the data.

Cause: Some of the data in the pluggable set requires a compatibility level higher than the release level of the Oracle executable. The string in square bracket is the name of the compatibility type associated with the data.

Cause: The non-partitioned table has the same data object number as one of the partitions in the partitioned table. One can not exchange the table with the partition in this case.

Cause: The file is not the initial version of the plugged in datafile.

Cause: As part of making a tablespace read-write, we need to convert datafiles that are plugged in read-only. The file must be online.

Cause: Recovery was not able to verify the referred datafile according to information in the control file. Before encountering this change vector for this file, somehow recovery did not encounter the file conversion redo that is supposed to verify the file. This may happen due to corrupted or incorrect control file used for media recovery.

Cause: The number of datafiles in the export file for the referred tablespace is not the same as expected. This is most likely caused by a user editing the export file.

Cause: The COMPATIBLE initialization parameter is not high enough to allow the operation. Allowing the command would make the database incompatible with the release specified by the current COMPATIBLE parameter.

Cause: When a tablespace is plugged into a database, the tablespace is initially read-only. Oracle converts the header of the plugged-in datafiles (assign them a new creation SCN) when the tablespace is first made read-write. This error occurs when the creation SCN in the file header is different from the creation SCN in the control file, possibly because this is the initial version of plugged-in datafile.

Cause: When a tablespace is plugged into a database, the tablespace is initially read-only. Oracle converts the header of the plugged-in datafiles (assign them a new creation SCN) when the tablespace is first made read-write. This error occurs when the creation SCN in the file header is different from the creation SCN in the control file, possibly because this is the converted datafile.

Cause: Oracle does not support plugging a tablespace into a database using a different national character set.

Cause: The compatibility check failed because a character set name that was provided is not valid.

Cause: The specified text exceeds the maximum length for text.

Cause: The specified string exceeds the maximum allowable length for the parameter

Cause: This parameter could not be set because the control file was not a backup control file.

Cause: This message reports the name of a file involved in other messages.

Cause: It was not possible to create the change tracking file.

Cause: The ALTER DATABASE ENABLE BLOCK CHANGE TRACKING command was issued, but block change tracking is already turned on for this database.

Cause: An I/O error occurred while writing to the change tracking file.

Cause: An I/O error occurred while reading from the change tracking file.

Cause: The change tracking file could not be opened.

Cause: The specified block number is corrupt in the change tracking file.

Cause: An error occurred while trying to change the size of the change tracking file.

Cause: out of SGA memory

Cause: A command was entered that requires block change tracking to be enabled, but block change tracking is not enabled.

Cause: Change tracking is enabled, but a problem was encountered while enabling the change tracking subsystem in this instance. The alert log and the trace file from the CTWR process will contain more information about the error.

Cause: While opening the specified change tracking file, it was found that the file header did not contain a valid logical block size. This probably means that the file is corrupt.

Cause: An invalid file type was found in the change tracking file. Some other file was put in place of the change tracking file, or the file is corrupt.

Cause: The compatibility version in the change tracking file is greater than what can be used by the current release of Oracle. This can happen when you upgrade, use change tracking with a new release, then downgrade.

Cause: The change tracking file is not the correct one for this database. This can happen when the database ID for this database has been changed.

Cause: The change tracking file does not match the one that was present when this instance was opened. In RAC, this error is most likely caused by having a change tracking file that cannot be consistently updated by all instances.

Cause: Syntax error.

Cause: Syntax error.

Cause: The USING clause was specified with DISABLE CHANGE TRACKING

Cause: Syntax error.

Cause: The USING clause was specified with ALTER DATABASE ENABLE BLOCK CHANGE TRACKING, but no file name was given.

Cause: The ALTER DATABASE RENAME FILE command was used to rename the change tracking file, and the database is open by one or more instances. The database must be mounted, and not open, to rename the change tracking file.

Cause: The name specified for the change tracking file is too long.

Cause: No file name was specified with the ALTER DATABASE ENABLE CHANGE TRACKING command, and the DB_CREATE_FILE_DEST parameter was not set.

Cause: An attempt was made to proxy restore a file to ASM disk group using RMAN command. This is not supported.

Cause: An attempt was made to proxy backup a ASM file. This is not supported.

Cause: An error occurred while obtaining the mirror resilvering status of the change tracking file.

Cause: Change tracking at a standby database required the Active Data Guard option.

Cause: The name given for an Oracle managed files destination cannot be initialized.

Cause: An attempt was made to create a file in DB_RECOVERY_FILE_DEST when DB_RECOVERY_FILE_DEST was not set. There are number of possible causes of this error, including: 1) A LOG_ARCHIVE_DEST_n parameter was specified using a LOCATION attribute whose value was DB_RECOVERY_FILE_DEST and an archived log file creation was attempted. 2) STANDBY_ARCHIVE_DEST parameter was specified using a LOCATION attribute whose value was DB_RECOVERY_FILE_DEST and an archived log file creation was attempted.

Cause: There are two possible cause for this error: 1) The DB_RECOVERY_FILE_DEST parameter was in use when no DB_RECOVERY_FILE_DEST_SIZE parameter was encountered while fetching initialization parameter. 2) An attempt was made to set DB_RECOVERY_FILE_DEST with the ALTER SYSTEM command when no DB_RECOVERY_FILE_DEST_SIZE was in use.

Cause: Parameter DB_RECOVERY_FILE_DEST_SIZE specified was not valid.

Cause: Oracle cannot reclaim disk space of specified bytes from the DB_RECOVERY_FILE_DEST_SIZE limit.

Cause: The file described by the record in control file was deleted in order to reclaim disk space from recovery area for other operations.

Cause: Duplex backup to recovery area is not supported.

Cause: The value of parameters DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE must be same in all instances. instance. All databases must have same recovery destination parameters.

Cause: The limit for recovery files specified by the DB_RECOVERY_FILE_DEST_SIZE was exceeded.

Cause: An attempt was made to create a control file for a temporary purpose in DB_RECOVERY_FILE_DEST.

Cause: An attempt was made to 1) Create a backup piece or image copy in the recovery area with KEEP option. 2) Update the KEEP attributes of an existing backup piece or image copy in the recovery area.

Cause: There are three possible cause for this error: 1) The indicated parameter was in use when no DB_RECOVERY_FILE_DEST parameter was encountered while fetching the initialization parameter. 2) An attempt was made to set indicated the parameter with the ALTER SYSTEM command when no DB_RECOVERY_FILE_DEST was in use. 3) An attempt was made to clear DB_RECOVERY_FILE_DEST with the ALTER SYSTEM command when the indicated parameter was in use.

Cause: An attempt was made to change a backup piece or image copy in recovery area to UNAVAILABLE.

Cause: DB_RECOVERY_FILE_DEST is running out of disk space.

Cause: One of the following events caused this: 1. A database crash happened during file creation. 2. A backup control file was restored. 3. The control file was re-created. 4. DB_RECOVERY_FILE_DEST has previously been enabled and then disabled.

Cause: Logging was disabled when ARCHIVELOG mode was used.

Cause: A log file that was intentionally corrupt for testing or benchmarking purposes was found and failed the operation.

Cause: This error should be followed by other errors indicating the cause of the problem.

Cause: This version of database was incompatible with the the indicated DBMS_BACKUP_RESTORE package installed in the database.

Cause: Passphrase encryption was attempted for a backup that contains encrypted tablespaces and uses compression.

Cause: The blocksize of the backup piece obtained from the header was invalid.

Cause: This control file was restored by a DUPLICATE operation used only to restore and recover the datafiles of the new database. It is not meant to be used for opening the database, as allowing so might corrupt datafiles or online redo logs of the target database or both.

Cause: The snapshot time which was specified when starting the recovery less than data file's checkpoint time. The snapshot recovery is only possible with data file's whose checkpoint time is less than snapshot time.

Cause: An attempt was made to use SNAPSHOT TIME recovery. But, the feature was not enabled.

Cause: An attempt to create a cross-platform backup was made but the COMPATIBLE parameter was not set to a high enough value to allow this.

Cause: The backup failed because the current database incarnation was changed during the backup. One of the following events caused this incarnation change: - The database was opened using ALTER DATABASE OPEN RESETLOGS statement. - RMAN command RESET DATABASE TO INCARNATION was issued. - If this happened on physical standby database, then redo apply has applied redo data from a new database incarnation.

Cause: While trying to obtain the file enqueue for the datafile the datafile name could not be obtained.

Cause: The database ID on the remote site did not match the ID of the target database. This is most likely caused by a wrong service name for the remote connection.

Cause: An error occurred while initiating backup on remote database server for network restore. Additional error messages will be issued to describe the failure.

Cause: Unable to read the file header from remote site.

Cause: Could not read the control file header from the remote site.

Cause: An attempt was made to perform a cross-platform operation from a backup piece created with a higher compatibility than the current COMPATIBLE parameter.

Cause: This error should be followed by other errors indicating the cause of the problem.

Cause: This error indicates that the backup piece that was constructed from the service is corrupt.

Cause: An OS error was received while managing the automatic auxiliary instance.

Cause: An error was received while managing the services of the auxiliary instance.

Cause: An error was received while managing the automatic auxiliary instance.

Cause: Could not obtain the connect string from the target database

Cause: The user attempted to validate a list of backup pieces more than once. Validation may only be performed once for a given validation conversation.

Cause: The user tried to add new pieces to the list of files being validated after the validation had already been performed. In a validation conversation, the list can only be validated once.

Cause: The user tried to get validation results for backup pieces before the pieces were actually validated.

Cause: The user specified a device BLKSIZE that is larger than the device BLKSIZE specified during compressed backup.

Cause: No data was returned for the specified backup piece.

Cause: During a block recovery, the header of the datafile could not be updated.

Cause: This backup piece container identifier did not match the supplied data file container identifier.

Cause: This error should be followed by other errors indicating the cause of the problem.

Cause: While reading a compressed backup piece, RMAN received an end-of-file without finding the end-of-compression stream.

Cause: RMAN cannot restore a multi-section backup to the indicated file, because this section is not a backup of this file, or the file was not prepared correctly for this restore.

Cause: During a multisection restore or copy, the file being restored was not a file in which a multisection restore or copy was in progress.

Cause: While completing a multisection restore or copy, it was found that all required sections for this file were not correctly applied.

Cause: When reading the space header block to use Unused Block Optimization for the backup of the datafile, the space header block had corrupted information.

Cause: When reading a space bitmap block to use Unused Block Optimization for the backup of the datafile, the space bitmap block had corrupted information.

Cause: When checkpointing the datafile containing the space bitmaps for the datafile being backed up in order to use Unused Block Optimization, the checkpoint of the datafile containing the space bitmaps did not advance.

Cause: When attempting to find information about datafile that holds bitmaps of migrated tablespace, the tablespace was found to have been dropped.

Cause: Media recovery stopped because information of one or more ancestor incarnations of recovery target incarnation was not available.

Cause: Recovery was done to an incarnation after changing the destination incarnation using RMAN's RESET DATABASE command.

Cause: Recovery was done to an incarnation after changing the destination incarnation using RMAN's RESET DATABASE command, but one or more of the recovered datafiles still belongs to the parent incarnation. This usually happens when recovery is ended before any logs from the desired incarnation have been applied.

Cause: The specified incarnation was not found in the control file.

Cause: Either a new incarnation was set using RMAN's RESET DATABASE command for a control file that was CURRENT, or the control file is from a prior incarnation. As recovery to a new incarnation requires changing the control file, test recovery is not allowed.

Cause: The specified datafile has been restored from a backup that was taken before the last RESETLOGS. Recovering this datafile will require a file header update that is incompatible with test recovery.

Cause: log_archive_format is missing a mandatory format element. Starting with Oracle 10i, archived log file names must contain each of the elements %s(sequence), %t(thread), and %r(RESETLOGS ID) to ensure that all archived log file names are unique.

Cause: While a media recovery was active, a new incarnation was detected by the server due to inspection or cataloging of archived logs or backup files.

Cause: A point-in-time recovery to an SCN or time stamp prior to the last RESETLOGS was requested.

Cause: The specified datafile has an invalid checkpoint.

Cause: Either the specified datafile was restored from a backup that was taken during a period of time that has already been discarded by a RESETLOGS operation, or Oracle cannot identify which database incarnation the file belongs to. The alert log contains more information.

Cause: The RESET DATABASE TO INCARNATION command was used while the database is open. This is not allowed.

Cause: The file did not hit end backup marker redo during recovery at the incarnation boundary, hence may contain changes discarded by new incarnation.

Cause: The control file is not in the recovery path of the target incarnation, and does not contain enough information as to how to recover to the target incarnation.

Cause: A backup piece could not be decrypted. This message is accompanied with another message that indicates the name of the encrypted backup that could not be restored. The reason could be either that an invalid password was entered, or that, when using transparent decryption, the database external security device is not open.

Cause: RMAN could not create an encrypted backup. This message will be accompanied by other messages that give more details about why the encrypted backup could not be created. The most common reason for this message is that you are trying to create a backup that can be transparently decrypted, and the database external security device is not open.

Cause: An RMAN encrypted backup was requested, but this backup includes one or more archived logs that were generated by an older release of Oracle. These archived logs cannot be encrypted.

Cause: An error occurred when processing user request.

Cause: RMAN was configured to create encrypted backups, but the channel is neither a DISK channel nor an Oracle Secure Backup channel.

Cause: An attempt was made to use Oracle public key infrastructure (PKI) based master key algorithm. RMAN only supports Advanced Encryption Standard (AES) based encryption.

Cause: The maximum number of rows in the V$RMAN_STATUS or V$RMAN_OUTPUT table has been exceeded.

Cause: RMAN tried to add a new V$RMAN_STATUS row, but the parent row did not exist.

Cause: RMAN tried to update an V$RMAN_STATUS row but the process which owns this row died.

Cause: RMAN tried to update an V$RMAN_STATUS row, but the row don't exist.

Cause: Another CONVERT DATABASE operation is already in progress.

Cause: An error occurred earlier during CONVERT DATABASE operation.

Cause: Conversion of data files with undo segments was not supported between endianess. The only time that data files with undo segments can be converted is between the same endianess as part of convert database. Convert database between different endian is not supported.

Cause: An error occurred during ALTER DATABASE RECOVER with the FORCE START AT option because there were no archive logs registered in the control file covering the specified start SCN or time.

Cause: When opening the file to be placed in a copy or backup set, to be inspected, the file header was not recognized as a valid header because it contained a invalid checkpoint SCN. The indicated file cannot be processed.

Cause: When opening the file to be placed in a copy or backup set, to be inspected, the file header was not recognized as a valid header because it contained a invalid creation SCN. The indicated file cannot be processed.

Cause: The operation failed because the control file was not mounted as clone, standby or backup.

Cause: This backup piece contained data pump dump file. Cataloging such a backup piece is not supported.

Cause: An attempt was made to validate block 0 of a datafile.

Cause: Some tablespaces that were specified for restoration were not found in the backup set directory. Message 19937 is issued for each file that was not found.

Cause: The indicated tablespace could not be restored because it was not in this backup set.

Cause: Data Pump dump file backup requested but COMPATIBLE did not allow it.

Cause: Data Pump dump file backup requested but the backup conversation is not a cross-platform conversation.

Cause: Cross-platform backups or restores of whole database between different endianess was requested but it is not supported.

Cause: Blocksize in header of datafile copy being converted at target was invalid. Either datafile has not been made read/write with compatibility 10.0 or greater at source database or datafile copy is corrupted.

Cause: The specified datafile copy to be converted at the target was not produced after making the tablespace in read/write mode with compatibility 10.0 or greater at the source database.

Cause: The Data Pump dump file could not be restored because it was not in this backup set.

Cause: The backup piece did not belong to the platform specified in FROM PLATFORM.

Cause: This file was already specified for inclusion in this restore conversation. The restore conversation may process only a single instance of a datafile.

Cause: It was not possible to determine the cross-platform transportable backup piece block size.

Cause: The block size obtained from the backup piece using the specified platform was not valid. Either the piece is corrupted or the specified platform is incorrect.

Cause: A cross-platform transportable restore was specified but the backup piece was not produced with the correct command.

Cause: The backup piece had a different endianess than the platform specified in FROM PLATFORM.

Cause: This tablespace was already specified for inclusion in this restore conversation.

Cause: An operation requiring to modify the control file was attempted, but a NID change is in progress.

Cause: The database was started in parallel mode. To change the DBID, the database must be mounted exclusively.

Cause: The database was open. To change the DBID, the database must be mounted exclusively.

Cause: The operation failed because a non-current, non-standby control file was mounted.

Cause: The operation failed because there were active threads in the database. The most likely cause is that the database crashed the last time it was shut down.

Cause: The operation failed because the database had one or more datafiles that were in OFFLINE IMMEDIATE mode.

Cause: The operation failed because the database had one or more datafiles that were in an unknown state.

Cause: DIAG requested a control file operation that may lead to a deadlock

Cause: An attempt was made to use the DBNEWID utility in a pluggable database.

Cause: NID usage

Cause: Requested compression algorithm in initialization parameter or by RMAN configuration requires that the advanced compression option be enabled and it was not.

Cause: Algorithm in initialization parameter requires a lower compatibility that is currently set.

Cause: Error occurred when querying the logical block size of a file.

Cause: The STANDBY TABLESPACE clause of the ALTER DATABASE RECOVER statement (partial_database_recovery clause) has been deprecated.

Cause: The STANDBY DATAFILE clause of the ALTER DATABASE RECOVER statement (partial_database_recovery clause) has been deprecated.

Cause: ALTER DATABASE MOUNT failed because a multi-instance standby role transition was in progress.

Cause: Event 10875 or event 10879 was set which prevented the operation from completing with multiple instances running in Oracle RAC.

Cause: ALTER DATABASE RECOVER TO LOGICAL required only one instance to be left running.

Cause: Physical standby transition to snapshot standby required only one instance left running if flashback database logging was not enabled.

Cause: Physical standby role transition required only one instance left running if database name was changed and flashback database logging was enabled.

Cause: The physical standby role transition command failed because a certain condition required the database to be mounted in this instance and not started in any other instance.

Cause: The standby role transition operation failed because a concurrent standby role transition was already in progress.

Cause: When attempting to open the specified dump file, an error was received.

Cause: When attempting to read the header of the specified dump file, an error was received.

Cause: The specified dump file did not contain data created by Data Pump.

Cause: Some data blocks for the Data Pump dump file were corrupt in the backup set.

Cause: Data Pump dump file restore requested but COMPATIBLE did not allow it.

Cause: Data Pump dump file restore requested but the restore conversation is not a cross-platform conversation.

Cause: A cross-platform backup was requested for a backup piece that contained archived logs.

Cause: The platform ID obtained from a cross-platform backup was incorrect.

Cause: A cross-platform restore was requested from a backup piece created with pre-12.1 compatibility without providing the platform name that created it.

Cause: A cross-platform restore was requested from an encrypted backup set with different endianess from the current platform.

Cause: A cross-platform backup was requested for an encrypted backup to a different endianess from the current platform.

Cause: A cross-platform backup was requested for an encrypted backup piece with different endianess from the current platform.

Cause: A cross-platform backup was requested for a backup piece created with compatibility prior to 12.1 without providing the platform name that created it.

Cause: A cross-platform backup was requested for a compressed backup to a different endianess from the current platform.

Cause: A restore of the controlfile was requested from a cross-platform backup, but the backup did not have the same endianess and restore was not possible.

Cause: A cross-platform backup was requested for a backup created with pre-10.2 compatibility.

Cause: A cross-platform operation was requested for a backup created with pre-10.2 compatibility.