83 ORA-19500 to ORA-19998
- ORA-19500: device block size string is invalid
-
Cause: the device block size returned by sequential I/O OSD is invalid
- ORA-19501: read error on file "string", block number string (block size=string)
-
Cause: read error on input file
- ORA-19502: write error on file "string", block number string (block size=string)
-
Cause: write error on output file
- ORA-19503: cannot obtain information on device, name="string", type="string", parms="string"
-
Cause: call to get device information returned an error
- ORA-19504: failed to create file "string"
-
Cause: call to create file returned an error
- ORA-19505: failed to identify file "string"
-
Cause: call to identify the file returned an error
- ORA-19506: failed to create sequential file, name="string", parms="string"
-
Cause: call to create the sequential file returned an error
- ORA-19507: failed to retrieve sequential file, handle="string", parms="string"
-
Cause: call to retrieve the sequential file returned an error
- ORA-19508: failed to delete file "string"
-
Cause: call to delete the file returned an error
- ORA-19509: failed to delete sequential file, handle="string", parms="string"
-
Cause: call to delete the sequential file returned an error
- ORA-19510: failed to set size of string blocks for file "string" (block size=string)
-
Cause: call to resize the file returned an error
- ORA-19511: non RMAN, but media manager or vendor specific failure, error text:\n string
-
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.
- ORA-19512: file search failed
-
Cause: Recovery manager or Oracle Server attempted to discover files that matched the specified pattern but failed.
- ORA-19513: failed to identify sequential file
-
Cause: Unable to identify the sequential file.
- ORA-19515: removal of a pattern from string not allowed
-
Cause: An existing pattern could not be removed from the named initialization parameter because it was being used to map from the primary file name to the standby file name.
- ORA-19525: tempfile for the clone database must be renamed
-
Cause: Opening a clone database failed because Oracle server forces the tempfile to be renamed, in order to avoid overwriting the primary tempfile.
- ORA-19526: only one location allowed for parameter string
-
Cause: A list of default locations was provided in an Oracle-managed files parameter.
- ORA-19527: physical standby redo log must be renamed
-
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.
- ORA-19528: redo logs being cleared may need access to files
-
Cause: The redo logs are being cleared. This procedure may need the files this operation is being applied to.
- ORA-19529: Pattern string in initialization parameter string has an Oracle Managed Files file name.
-
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.
- ORA-19550: cannot use backup/restore functions while using dispatcher
-
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.
- ORA-19551: device is busy, device type: string, device name: string
-
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.
- ORA-19552: device type string is invalid
-
Cause: The device type indicated is invalid.
- ORA-19553: device name string is invalid
-
Cause: The device name indicated is invalid.
- ORA-19554: error allocating device, device type: string, device name: string
-
Cause: The specified device could not be allocated.
- ORA-19555: invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value
-
Cause: The value of parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was not set within the valid range.
- ORA-19556: required destination LOG_ARCHIVE_DUPLEX_DEST currently is deferred
-
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.
- ORA-19557: device error, device type: string, device name: string
-
Cause: An error occurred in the platform-specific device code
- ORA-19558: error de-allocating device
-
Cause: The specified device could not be de-allocated.
- ORA-19559: error sending device command: string
-
Cause: An error occurred while sending the indicated command to the session device.
- ORA-19560: string is not a valid device limit name
-
Cause: An invalid name of device limit was specified in a call to DBMS_BACKUP_RESTORE.SETLIMIT.
- ORA-19561: string requires a DISK channel
-
Cause: The attempted command requires that a DISK device channel be allocated to the session, but a non-DISK device was found.
- ORA-19562: File string is empty.
-
Cause: The indicated file, which is an archived log, control, or data file, was found to be empty during a copy, backup, or scan operation.
- ORA-19563: string header validation failed for file string
-
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.
- ORA-19564: error occurred writing string bytes at block number string
-
Cause: An error occurred while writing to a file.
- ORA-19565: BACKUP_TAPE_IO_SLAVES not enabled when duplexing to sequential devices
-
Cause: An attempt was made to specify duplexing to sequential devices, but the BACKUP_TAPE_IO_SLAVES initialization parameter was not enabled.
- ORA-19566: exceeded limit of string corrupt blocks for file string
-
Cause: The user specified limit of allowable corrupt blocks was exceeded while reading the specified datafile for a datafile copy or backup.
- ORA-19567: cannot shrink file string because it is being backed up or copied
-
Cause: An ALTER statement attempted to reduce the size of the indicated file while the same file is being backed up or copied.
- ORA-19568: a device is already allocated to this session
-
Cause: A device cannot be allocated to a session if another device is already allocated.
- ORA-19569: no device is allocated to this session
-
Cause: An operation was attempted which requires a device to be allocated to the current session, and there is no device allocated.
- ORA-19570: file number string is outside valid range of 1 through string
-
Cause: A file number used in a copy, backup, or restore operation is not valid for the current database.
- ORA-19571: string RECID string STAMP string not found in control file
-
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.
- ORA-19572: cannot process file string, file is being being resized
-
Cause: The input file specified for a copy or backup operation could not be opened because the file is being resized.
- ORA-19573: cannot obtain string enqueue for datafile string
-
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.
- ORA-19574: output file name must be specified
-
Cause: This type of copy or restore requires an output file name.
- ORA-19575: expected string blocks in file string, found string
-
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.
- ORA-19576: datafile string not defined in control file
-
Cause: The specified file number was not found in the control file.
- ORA-19577: file string is MISSING
-
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.
- ORA-19578: end of volume while duplexing to sequential files, backup piece incomplete
-
Cause: An end of volume (EOV) condition was detected while duplexing to sequential files, and this condition cannot be handled currently.
- ORA-19579: archived log record for string not found
-
Cause: No archived log record corresponding to input file could be found in the control file.
- ORA-19580: string conversation not active
-
Cause: A backup or restore operation was attempted before a conversation was started.
- ORA-19581: no files have been named
-
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.
- ORA-19582: archived log file header validation for string failed
-
Cause: Archived log file header is corrupt and could not be validated.
- ORA-19583: conversation terminated due to error
-
Cause: An error occurred which forced the termination of the current backup or restore conversation.
- ORA-19584: file string already in use
-
Cause: The indicated file, which was specified as the target for a copy, restore, or delete operation is already in use by the database.
- ORA-19585: premature end of volume on piece string
-
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.
- ORA-19586: string k-byte limit is too small to hold piece directory
-
Cause: The user-specified limit for MAXPIECESIZE for this channel is not enough to hold the backup set control data.
- ORA-19587: error occurred reading string bytes at block number string
-
Cause: An error occurred while reading from a file.
- ORA-19588: string RECID string STAMP string is no longer valid
-
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.
- ORA-19589: string is not a snapshot or backup control file
-
Cause: The control file that is the source for a backup or copy operation is not a snapshot or backup control file.
- ORA-19590: conversation already active
-
Cause: You tried to begin a backup or restore conversation, but another conversation is already active in this session.
- ORA-19591: backup aborted because job time exceeded duration time
-
Cause: You tried to backup with duration option and the time provided was not sufficient to complete the backup.
- ORA-19592: wrong string conversation type
-
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.
- ORA-19593: datafile number string already included as string
-
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.
- ORA-19594: control file already included as string
-
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.
- ORA-19595: archived log string already included in backup conversation
-
Cause: The indicated archived log has already been specified for inclusion in this backup conversation.
- ORA-19596: SPFILE already included
-
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.
- ORA-19597: file string block size string does not match set block size of string
-
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.
- ORA-19598: can not backup SPFILE because the instance was not started with SPFILE
-
Cause: A backup command requested a backup of the SPFILE, but no SPFILE was used to startup the instance.
- ORA-19599: block number string is corrupt in string string
-
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.
- ORA-19600: input file is string string (string)
-
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.
- ORA-19601: output file is string string (string)
-
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.
- ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
-
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.
- ORA-19603: cannot backup or copy active file with KEEP .. UNRECOVERABLE option
-
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.
- ORA-19604: conversation file naming phase is over
-
Cause: A call was made to specify a file to be backed up or restored after the first backup piece has been processed.
- ORA-19605: input file name must be specified
-
Cause: The input file name was not specified for a control file copy operation.
- ORA-19606: Cannot copy or restore to snapshot control file
-
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.
- ORA-19607: string is an active 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.
- ORA-19608: string is not a backup piece
-
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.
- ORA-19609: string is from different backup set: stamp string count string
-
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.
- ORA-19610: directory block string is corrupt
-
Cause: The indicated directory block failed checksum validation. This backup piece is unusable.
- ORA-19611: backup piece out of order. Expected string but found string
-
Cause: This backup piece is out of sequence.
- ORA-19612: datafile string not restored due to string
-
Cause: The indicated file could not be restored, because all of its data blocks were not found in the backup piece.
- ORA-19613: datafile string not found in backup set
-
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.
- ORA-19614: archived log thread string sequence string not found in backup set
-
Cause: The indicated archived log file was named explicitly for restoration but is not contained in this backup set.
- ORA-19615: some files not found in 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.
- ORA-19616: output file name must be specified if database not mounted
-
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.
- ORA-19617: file string contains different RESETLOGS data
-
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.
- ORA-19618: cannot name files after RESTOREVALIDATE has been called
-
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.
- ORA-19619: cannot call RESTOREVALIDATE after files have been named
-
Cause: RESTOREVALIDATE was called after some files had already been specified for restoration.
- ORA-19620: string is not of string type
-
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.
- ORA-19621: archived log range has already been specified
-
Cause: A range of logs has already been specified. Only one SCN range may be specified per conversation.
- ORA-19622: archived log thread string sequence string not restored due to string
-
Cause: The indicated file could not be restored, because all of its data blocks were not found in the backup piece.
- ORA-19623: file string is open
-
Cause: A SWITCHTOCOPY operation specified a datafile copy whose parent datafile is open.
- ORA-19624: operation failed, retry possible
-
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.
- 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. 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.
- 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.
- 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.
- ORA-19628: invalid SCN range
-
Cause: The starting SCN for RESTOREREDOLOGRANGE was greater than the ending System Change Number (SCN).
- ORA-19629: no files in specified archived log SCN range
-
Cause: This backup set contains no files in the specified range.
- ORA-19630: end of volume encountered while copying backup piece
-
Cause: While copying a backup piece from the OS native file system to an output device, the output device encountered end-of-volume.
- ORA-19631: archived log record contains no file name
-
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.
- ORA-19632: file name not found in control file
-
Cause: The name passed to GETFNO was not found in the control file.
- 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.
- ORA-19634: file name required for this function
-
Cause: The FNAME or HANDLE parameter was not specified for DELETEPIECE, DELETEDATAFILECOPY, DELETEREDOLOG or PROXYDELETE.
- ORA-19635: input and output file names are identical: string
-
Cause: Identical input and output file names were specified for a datafile copy operation.
- ORA-19636: archived log thread string sequence string already included
-
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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-19646: cannot change size of datafile string from string to string
-
Cause: Restore needs to adjust the size of the file as indicated, but the file size adjustment failed.
- 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.
- 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.
- ORA-19649: offline-range record RECID string STAMP string not found in file string
-
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.
- 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.
- 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.
- ORA-19652: cannot apply offline-range record to datafile string: file is fuzzy
-
Cause: The target datafile for an APPLYOFFLINERANGE call is fuzzy.
- 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.
- 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.
- 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.
- 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.
- ORA-19657: cannot inspect current datafile string
-
Cause: The file being inspected is already part of the currently mounted database.
- 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.
- 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.
- 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.
- ORA-19661: datafile string could not be verified
-
Cause: Some data blocks for the indicated datafile were corrupt in the backup set.
- 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.
- 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.
- ORA-19664: file type: string, file name: string
-
Cause: This message is issued to identify the file which is the subject of an error.
- 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.
- ORA-19666: cannot do incremental restore of the control file
-
Cause: The control file was included in an incremental restore conversation
- ORA-19667: cannot do incremental restore of datafile string
-
Cause: The backup of the datafile is a full backup
- ORA-19668: cannot do full restore of datafile string
-
Cause: The backup of the datafile is an incremental backup
- 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.
- ORA-19670: file string already being restored
-
Cause: A proxy restore function has already named this file as a restore destination.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-19677: RMAN configuration name exceeds maximum length of string
-
Cause: The configuration name string exceeds maximum length.
- ORA-19678: RMAN configuration value exceeds maximum length of string
-
Cause: The configuration value string exceeds maximum length.
- ORA-19679: RMAN configuration number string is outside valid range of 1 through string
-
Cause: An invalid RMAN Configuration number was specified.
- ORA-19680: some blocks not recovered. See trace file for details
-
Cause: Some blocks are not recovered during block media recovery.
- ORA-19681: block media recovery on control file not possible
-
Cause: file number 0 specified in block media recovery
- ORA-19682: file string not in block media recovery context
-
Cause: Internal error
- ORA-19683: real and backup block size of file string are unequal
-
Cause: block size changed between backup & real file
- ORA-19684: block media recovery failed because database is suspended
-
Cause: Database is suspended, probably by an ALTER SYSTEM SUSPEND statement
- ORA-19685: SPFILE could not be verified
-
Cause: Some data blocks for the SPFILE were corrupt in the backup set.
- ORA-19686: SPFILE not restored due to string
-
Cause: The indicated file could not be restored, because some of its data blocks were not found in the backup piece.
- ORA-19687: SPFILE not found in backup set
-
Cause: The SPFILE could not be restored, because it is not in this backup set.
- ORA-19688: control file AUTOBACKUP format(string) for string does not have %F
-
Cause: control file AUTOBACKUP format must contain %F for the device.
- ORA-19689: cannot have more than one %F in control file AUTOBACKUP format(%0!s) for %1!s
-
Cause: control file AUTOBACKUP format contains more than one %F for the device.
- ORA-19690: backup piece release string incompatible with Oracle release string
-
Cause: The backup piece was created by incompatible software.
- ORA-19691: string is from different database: id=string, name=string
-
Cause: The database name or database id in backup piece header does not match the one in control file.
- ORA-19692: missing creation stamp on piece string
-
Cause: The backup piece doesn't have information about creation stamp.
- ORA-19693: backup piece string already included
-
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.
- ORA-19694: some changed blocks were not found in the change tracking file
-
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.
- ORA-19695: fixed table X$KRBMSFT has not been populated
-
Cause: This is an internal error. The fixed table X$KRBMAFT was not populated using the function DBMS_BACKUP_RESTORE.SEARCHFILES.
- ORA-19696: control file not found in backup set
-
Cause: The control file could not be restored because it is not in this backup set.
- ORA-19697: standby control file not found in backup set
-
Cause: The standby control file could not be restored because it is not in this backup set.
- ORA-19698: string is from different database: id=string, db_name=string
-
Cause: Catalog failed because the database id in file header does not match the one in control file.
- ORA-19699: cannot make copies with compression enabled
-
Cause: Image copies cannot be compressed.
- ORA-19700: device type exceeds maximum length of string
-
Cause: The device type indicated is invalid.
- ORA-19701: device name exceeds maximum length of string
-
Cause: The device name indicated is invalid.
- ORA-19702: device parameter exceeds maximum length of string
-
Cause: The device parameter exceeds the port-specific maximum length.
- ORA-19703: device command string exceeds maximum length of string
-
Cause: The device command string exceeds maximum length.
- ORA-19704: file name exceeds maximum length of string
-
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.
- ORA-19705: tag value exceeds maximum length of string characters
-
Cause: During a backup or copy operation, the user supplied a tag value too long to fit in the file header.
- ORA-19706: invalid SCN
-
Cause: The input SCN is either not a positive integer or too large.
- ORA-19707: invalid record block number - string
-
Cause: The input number is either negative or too large.
- ORA-19708: log destination exceeds maximum length of string characters
-
Cause: When starting a restore conversation, the user specified a log restore destination longer than the port-specific maximum.
- ORA-19709: numeric parameter must be non-negative integer
-
Cause: A numeric parameter to an DBMS_BACKUP_RESTORE procedure is negative or contains a fractional portion.
- ORA-19710: unsupported character set string
-
Cause: When the target database is not mounted, RMAN sets the target database character set to the value specified in the users environment.
- ORA-19711: cannot use RENORMALIZEALLFILENAMES while database is open
-
Cause: An attempt was made to re-normalize all the file names in the control file while the database is open.
- ORA-19712: table name exceeds maximum length of string
-
Cause: The table name string exceeds maximum length.
- ORA-19713: invalid copy number: string
-
Cause: The copy number is not in a valid range or you have reached maximum limit.
- ORA-19714: length for generated name longer than string
-
Cause: The specified format exceeds the maximum length for the piece name.
- ORA-19715: invalid format string for generated name
-
Cause: A restricted format or undefined format was used incorrectly.
- ORA-19716: error processing format string to generate name for backup
-
Cause: There were errors while processing the format to generate name for backup.
- ORA-19717: for non-OMF search the pattern must be specified
-
Cause: The procedure DBMS_BACKUP_RESTORE.SEARCHFILES was called with an empty pattern while the parameter OMF was set to FALSE.
- ORA-19718: length for command id longer than string
-
Cause: The specified command id exceeds the maximum length for command id.
- ORA-19719: length for operation name longer than string
-
Cause: The specified operation name exceeds the maximum length for operation name.
- ORA-19720: Error occurred when converting an OCI number into an SCN
-
Cause: This is most likely caused by an invalid SCN number that came from an external file, such as an export file.
- ORA-19721: Cannot find data file with absolute file number string in tablespace string
-
Cause: One of the data files that should have been in the pluggable set was not found. Alternatively, one of the data files in the pluggable set had already been plugged in from a previous import job and so was excluded from the pluggable set.
- ORA-19722: datafile string is an incorrect version
-
Cause: The datafile is an incorrect version. It contains either less or more changes then the desired version.
- ORA-19723: cannot re-create plugged in data file string
-
Cause: The data file was plugged in read only or plugged in as part of pluggable database creation or pluggable database plug-in. It cannot be re-created.
- ORA-19724: snapshot too old: snapshot time is before file string plug-in time
-
Cause: The snapshot SCN is before the SCN at which the referred datafile is plugged into the database.
- ORA-19725: can not acquire plug-in enqueue
-
Cause: There maybe another "ALTER DATABASE RESET COMPATIBILITY" command issued concurrently, preventing this process from acquiring the plug-in enqueue.
- ORA-19726: cannot plug data [string] at level string into database running at compatibility level string
-
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.
- ORA-19727: cannot plug data [string] at level string into database running Oracle string
-
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.
- ORA-19728: data object number conflict between table string and partition string in table string
-
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.
- ORA-19729: File string is not the initial version of the plugged in datafile
-
Cause: The file is not the initial version of the plugged in datafile.
- ORA-19730: can not convert offline plugged-in datafile string
-
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.
- ORA-19731: cannot apply change to unverified plugged-in datafile string
-
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.
- ORA-19732: incorrect number of datafiles for tablespace string
-
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.
- ORA-19733: COMPATIBLE parameter needs to be string or greater
-
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.
- ORA-19734: wrong creation SCN - control file expects converted 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 initial version of plugged-in datafile.
- ORA-19735: wrong creation SCN - control file expects initial 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.
- ORA-19736: can not plug a tablespace into a database using a different national character set
-
Cause: Oracle does not support plugging a tablespace into a database using a different national character set.
- ORA-19738: cannot find language information for character set: 'string'
-
Cause: The compatibility check failed because a character set name that was provided is not valid.
- ORA-19740: text is longer than string
-
Cause: The specified text exceeds the maximum length for text.
- ORA-19741: string exceeds maximum allowable length of string for parameter 'string'
-
Cause: The specified string exceeds the maximum allowable length for the parameter
- ORA-19742: control file is not a backup control file
-
Cause: This parameter could not be set because the control file was not a backup control file.
- ORA-19743: could not unmount volume string:string
-
Cause: The specified server and volume combination was not found and could not be unmounted.
- ORA-19744: Volume string:string is currently in use and cannot be unmounted.
-
Cause: The specified volume could not be unmounted because it was in use and had open files.
- ORA-19745: Invalid call to DBMS_BACKUP_RESTORE API, Reason: string.
-
Cause: The call to the DBMS_BACKUP_RESTORE API was invalid. The DBMS_BACKUP_RESTORE API was either called with invalid arguments or called without required parameters set.
- ORA-19750: change tracking file: 'string'
-
Cause: This message reports the name of a file involved in other messages.
- ORA-19751: could not create the change tracking file
-
Cause: It was not possible to create the change tracking file.
- ORA-19752: block change tracking is already enabled
-
Cause: The ALTER DATABASE ENABLE BLOCK CHANGE TRACKING command was issued, but block change tracking is already turned on for this database.
- ORA-19753: error writing to change tracking file
-
Cause: An I/O error occurred while writing to the change tracking file.
- ORA-19754: error reading from change tracking file
-
Cause: An I/O error occurred while reading from the change tracking file.
- ORA-19755: could not open change tracking file
-
Cause: The change tracking file could not be opened.
- ORA-19756: corrupt block number string found in change tracking file
-
Cause: The specified block number is corrupt in the change tracking file.
- ORA-19757: could not resize change tracking file to string blocks
-
Cause: An error occurred while trying to change the size of the change tracking file.
- ORA-19758: failed to enable/disable block change tracking: out of SGA memory
-
Cause: out of SGA memory
- ORA-19759: block change tracking is not enabled
-
Cause: A command was entered that requires block change tracking to be enabled, but block change tracking is not enabled.
- ORA-19760: error starting change tracking
-
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.
- ORA-19761: block size string is not valid for change tracking file
-
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.
- ORA-19762: invalid file type string
-
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.
- ORA-19763: compatibility version string is higher than maximum allowed: string
-
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.
- ORA-19764: database id string does not match database id string in control file
-
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.
- ORA-19765: mount id string does not match mount id string in control file
-
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.
- ORA-19766: missing CHANGE keyword
-
Cause: Syntax error.
- ORA-19767: missing TRACKING keyword
-
Cause: Syntax error.
- ORA-19768: USING clause only valid with ENABLE CHANGE TRACKING
-
Cause: The USING clause was specified with DISABLE CHANGE TRACKING
- ORA-19769: missing FILE keyword
-
Cause: Syntax error.
- ORA-19770: invalid change tracking file name
-
Cause: The USING clause was specified with ALTER DATABASE ENABLE BLOCK CHANGE TRACKING, but no file name was given.
- ORA-19771: cannot rename change tracking file while database is open
-
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.
- ORA-19772: change tracking file name exceeds limit of string characters
-
Cause: The name specified for the change tracking file is too long.
- ORA-19773: must specify change tracking file name
-
Cause: No file name was specified with the ALTER DATABASE ENABLE CHANGE TRACKING command, and the DB_CREATE_FILE_DEST parameter was not set.
- ORA-19776: PROXY restore to ASM disk group "string" is not supported.
-
Cause: An attempt was made to proxy restore a file to ASM disk group using RMAN command. This is not supported.
- ORA-19777: ASM file string cannot be proxy backed up.
-
Cause: An attempt was made to proxy backup a ASM file. This is not supported.
- ORA-19779: could not obtain resilvering status for change tracking file
-
Cause: An error occurred while obtaining the mirror resilvering status of the change tracking file.
- ORA-19780: Active Data Guard option not enabled
-
Cause: Change tracking at a standby database required the Active Data Guard option.
- ORA-19781: The PROXY option is not supported on sparse file string
-
Cause: The PROXY option was used with a sparse file. This is not supported.
- ORA-19784: error enabling change tracking due to ORA-4031
-
Cause: The change tracking writer could not get requested memory for buffer allocation.
- ORA-19800: Unable to initialize Oracle Managed Destination
-
Cause: The name given for an Oracle managed files destination cannot be initialized.
- ORA-19801: initialization parameter DB_RECOVERY_FILE_DEST is not set
-
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.
- ORA-19802: cannot use DB_RECOVERY_FILE_DEST without DB_RECOVERY_FILE_DEST_SIZE
-
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.
- ORA-19803: Parameter DB_RECOVERY_FILE_DEST_SIZE is out of range (1 - string)
-
Cause: Parameter DB_RECOVERY_FILE_DEST_SIZE specified was not valid.
- ORA-19804: cannot reclaim string bytes disk space from string bytes limit
-
Cause: Disk space of specified bytes from the DB_RECOVERY_FILE_DEST location for DB_RECOVERY_FILE_DEST_SIZE limit could not be reclaimed.
- ORA-19805: RECID string of string was deleted to reclaim disk space
-
Cause: The file described by the record in control file was deleted in order to reclaim disk space from recovery area for other operations or deleted by another RMAN session.
- ORA-19806: cannot make duplex backups in recovery area
-
Cause: Duplex backup to recovery area is not supported.
- ORA-19807: duplex number string is out of range: expected between 0 and string
-
Cause: The duplex number specified is outside of the expected range.
- ORA-19808: recovery destination parameter mismatch
-
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.
- ORA-19809: limit exceeded for recovery files
-
Cause: The limit for recovery files specified by the DB_RECOVERY_FILE_DEST_SIZE was exceeded.
- ORA-19810: Cannot create temporary control file string in DB_RECOVERY_FILE_DEST
-
Cause: An attempt was made to create a control file for a temporary purpose in DB_RECOVERY_FILE_DEST.
- ORA-19811: cannot have files in DB_RECOVERY_FILE_DEST with keep attributes
-
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.
- ORA-19812: cannot use string without DB_RECOVERY_FILE_DEST
-
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.
- ORA-19813: cannot have unavailable file string in DB_RECOVERY_FILE_DEST
-
Cause: An attempt was made to change a backup piece or image copy in recovery area to UNAVAILABLE.
- ORA-19815: WARNING: string of string bytes is string%% used, and has string remaining bytes available.
-
Cause: DB_RECOVERY_FILE_DEST is running out of disk space.
- ORA-19816: WARNING: Files may exist in string that are not known to database.
-
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.
- ORA-19820: database must be in NOARCHIVELOG mode to disable logging
-
Cause: Logging was disabled when ARCHIVELOG mode was used.
- ORA-19821: an intentionally corrupt log file was found
-
Cause: A log file that was intentionally corrupt for testing or benchmarking purposes was found and failed the operation.
- ORA-19827: Restoring preplugin files to a recovery area is not supported.
-
Cause: An attempt to resore a preplugin file in a recovery area failed. This is not supported.
- ORA-19830: error from target database: \nstring
-
Cause: This error should be followed by other errors indicating the cause of the problem.
- ORA-19831: incompatible string.string.string.string DBMS_BACKUP_RESTORE package: string.string.string.string required
-
Cause: This version of database was incompatible with the the indicated DBMS_BACKUP_RESTORE package installed in the database.
- ORA-19836: cannot use passphrase encryption for this backup
-
Cause: Passphrase encryption was attempted for a backup that contains encrypted tablespaces and uses compression.
- ORA-19837: invalid blocksize string in backup piece header
-
Cause: The blocksize of the backup piece obtained from the header was invalid.
- ORA-19838: cannot use this control file to mount or open database
-
Cause: This control file was restored by a DUPLICATE operation used only to restore and recover the data files of the new database. It is not meant to be used for mounting or opening the database, as allowing so might corrupt data files or online redo logs of the target database or both.
- ORA-19839: snapshot datafile checkpoint time is greater than snapshot time
-
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.
- ORA-19840: SNAPSHOT TIME recovery is not enabled
-
Cause: An attempt was made to use SNAPSHOT TIME recovery. But, the feature was not enabled.
- ORA-19841: Cross-platform backups require COMPATIBLE string or greater
-
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.
- ORA-19842: The current database incarnation changed during backup.
-
Cause: The backup failed because the current database incarnation was changed during the backup. One of these 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.
- ORA-19843: Cannot obtain datafile name for datafile string
-
Cause: While trying to obtain the file enqueue for the datafile the datafile name could not be obtained.
- ORA-19844: Remote database ID string is different from local database ID string.
-
Cause: The database ID on the remote site did not match the ID of the target database. This was caused by an incorrect service name for the remote connection.
- ORA-19845: error in string while communicating with remote database server
-
Cause: An error occurred while initiating backup on remote database server for network restore. Additional error messages will be issued to describe the failure.
- ORA-19846: cannot read header of datafile string from remote site
-
Cause: Unable to read the file header from remote site.
- ORA-19847: cannot read header of control file from remote site
-
Cause: Could not read the control file header from the remote site.
- ORA-19848: cross-platform backup piece requires COMPATIBLE string or greater
-
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.
- ORA-19849: error while reading backup piece from service string
-
Cause: This error should be followed by other errors indicating the cause of the problem.
- ORA-19850: backup piece constructed from service string is corrupt
-
Cause: This error indicates that the backup piece that was constructed from the service is corrupt.
- ORA-19851: OS error while managing auxiliary database string
-
Cause: An OS error was received while managing the automatic auxiliary instance.
- ORA-19852: error creating services for auxiliary instance string (error string)
-
Cause: An error was received while managing the services of the auxiliary instance.
- ORA-19853: error preparing auxiliary instance string (error string)
-
Cause: An error was received while managing the automatic auxiliary instance.
- ORA-19854: error obtaining connect string from target
-
Cause: Could not obtain the connect string from the target database
- ORA-19855: cannot use clone mounted control file to drop database
-
Cause: The clone mounted control file could not be used to drop the database because the names of the data files and online logs were not fixed using the RMAN DUPLICATE command. This could cause the original database files to be lost.
- ORA-19856: cannot use clone mounted control file to recover database
-
Cause: The clone mounted control file could not be used to recover the database because the names of the data files and online logs were not fixed using the Recovery Manager (RMAN) operation. This could result in the loss of original database files.
- ORA-19860: piece validation cannot be performed more than once
-
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.
- ORA-19861: additional backup pieces cannot be validated in this 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.
- ORA-19862: backup pieces must be validated before accessing results
-
Cause: The user tried to get validation results for backup pieces before the pieces were actually validated.
- ORA-19863: device block size string is larger than max allowed: string
-
Cause: The user specified a device BLKSIZE that is larger than the device BLKSIZE specified during compressed backup.
- ORA-19864: string
-
- ORA-19865: Backup piece string has no data
-
Cause: No data was returned for the specified backup piece.
- ORA-19866: error writing file header for datafile string
-
Cause: During a block recovery, the header of the datafile could not be updated.
- ORA-19867: backup piece string is from a different container identifier string; data file string
-
Cause: This backup piece container identifier did not match the supplied data file container identifier.
- ORA-19868: cannot recover block string for file number string
-
Cause: The specified block could not be cleared.
- ORA-19869: Input file name or destination is an empty string.
-
Cause: A valid string for the file name or destination was not provided.
- ORA-19870: error while restoring backup piece string
-
Cause: This error should be followed by other errors indicating the cause of the problem.
- ORA-19872: Unexpected end of file at block string while decompressing backup piece string
-
Cause: While reading a compressed backup piece, RMAN received an end-of-file without finding the end-of-compression stream.
- ORA-19873: cannot apply this backup section to file string
-
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.
- ORA-19874: cannot finish multisection restore or copy to file string
-
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.
- ORA-19875: multisection restore or copy not complete for file string
-
Cause: While completing a multisection restore or copy, it was found that all required sections for this file were not correctly applied.
- ORA-19880: corrupted space header for data file string at block string
-
Cause: A space header block of a data file was used by the unused block optimization feature. The space header block of the reported data file had corrupted information.
- ORA-19881: Corrupted space bitmap for datafile string, block string
-
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.
- ORA-19882: datafile string checkpoint string is ahead of space bitmap datafile string checkpoint string
-
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.
- ORA-19883: Unused Block Optimization stopped for data file string
-
Cause: Accompanying errors detail the problem that prevented Unused Block Optimization from being used.
- ORA-19884: datafile string is unable to use Unused Block Optimization because tablespace has been dropped
-
Cause: When attempting to find information about datafile that holds bitmaps of migrated tablespace, the tablespace was found to have been dropped.
- ORA-19885: Unused Block Optimization is not implemented for shadow data file string
-
Cause: Unused Block Optimization is not implemented for shadow data files.
- ORA-19887: all participating data files in the backup session were dropped by the database
-
Cause: All data files added to the backup session were dropped from the database before the backup session could checkpoint these files.
- ORA-19890: data file already in use
-
Cause: The file access enqueue could not be obtained for a file specified in restore operation. The file was an output file for a restore operation, which was attempting to overwrite the currently active version of that file. In this case, the file must be offline or the database must be closed.
- ORA-19891: cannot open backup piece string
-
Cause: When attempting to open the specified backup piece, an error was received.
- ORA-19892: failed to allocate buffer while reading backup piece
-
Cause: Internal error
- ORA-19893: sparse information block string is corrupt
-
Cause: The indicated sparse information block failed checksum validation. This backup piece was unusable.
- ORA-19899: missing incarnation information
-
Cause: Media recovery stopped because information of one or more ancestor incarnations of recovery target incarnation was not available.
- ORA-19900: RESETLOGS must be specified after recovery to new incarnation
-
Cause: Recovery was done to an incarnation after changing the destination incarnation using RMAN's RESET DATABASE command.
- ORA-19901: database needs more recovery to create new incarnation
-
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.
- ORA-19902: incarnation key string not found
-
Cause: The specified incarnation was not found in the control file.
- ORA-19903: test recovery not allowed when recovering to new incarnation
-
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.
- ORA-19904: test recovery not allowed for datafile string
-
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.
- ORA-19905: LOG_ARCHIVE_FORMAT must contain sequence %string, thread %string, and resetlogs ID %%r for files to be unique
-
Cause: The LOG_ARCHIVE_FORMAT initialization parameter was missing a mandatory format element. Starting with Oracle 10g, archived log file names must contain each of the elements sequence, thread and resetlogs id to ensure that all archived log file names are unique.
- ORA-19906: recovery target incarnation changed during recovery
-
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.
- ORA-19907: recovery time or SCN does not belong to recovered incarnation
-
Cause: A point-in-time recovery to an SCN or time stamp prior to the last RESETLOGS was requested.
- ORA-19908: datafile string has invalid checkpoint
-
Cause: The specified datafile has an invalid checkpoint.
- ORA-19909: datafile string belongs to an orphan incarnation
-
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.
- ORA-19910: can not change recovery target incarnation in control file
-
Cause: The RESET DATABASE TO INCARNATION or RESET PLUGGABLE DATABASE TO INCARNATION command was used while the database or pluggable database was open. This is not allowed.
- ORA-19911: datafile string contains future changes at the incarnation boundary
-
Cause: The file did not hit end backup marker redo during recovery at the incarnation boundary, hence may contain changes discarded by new incarnation.
- ORA-19912: cannot recover to target incarnation string
-
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.
- ORA-19913: unable to decrypt backup
-
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.
- ORA-19914: unable to encrypt backup
-
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.
- ORA-19915: Unable to encrypt files created prior to Oracle Database release 10.2.
-
Cause: An encrypted RMAN backup was requested that included one or more archived logs generated by an older Oracle release. These archived logs cannot be encrypted.
- ORA-19919: encrypted backups to tertiary storage require Oracle Secure Backup
-
Cause: RMAN was configured to create encrypted backups, but the channel is neither a DISK channel nor an Oracle Secure Backup channel.
- ORA-19920: RMAN does not support PKI-based master key for encryption.
-
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.
- ORA-19921: maximum number of string rows exceeded
-
Cause: The maximum number of rows in the V$RMAN_STATUS or V$RMAN_OUTPUT table has been exceeded.
- ORA-19922: there is no parent row with id string and level string
-
Cause: RMAN tried to add a new V$RMAN_STATUS row, but the parent row did not exist.
- ORA-19923: the session for row with id string is not active
-
Cause: RMAN tried to update an V$RMAN_STATUS row but the process which owns this row died.
- ORA-19924: there are no row with id string
-
Cause: RMAN tried to update an V$RMAN_STATUS row, but the row don't exist.
- ORA-19925: Internal error while cleaning memory used by V$RMAN_STATUS view
-
- ORA-19926: Database cannot be converted at this time
-
Cause: Another CONVERT DATABASE operation is already in progress.
- ORA-19927: CONVERT DATABASE operation cannot proceed
-
Cause: An error occurred earlier during CONVERT DATABASE operation.
- ORA-19928: CONVERT of data files with undo segments between different endian is not supported.
-
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.
- ORA-19929: no archive log registered
-
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.
- ORA-19930: file string has invalid checkpoint SCN string
-
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.
- ORA-19931: file string has invalid creation SCN string
-
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.
- ORA-19932: control file is not clone, standby or backup
-
Cause: The operation failed because the control file was not mounted as clone, standby or backup.
- ORA-19933: catalog backup piece string of data pump dump file is not supported
-
Cause: This backup piece contained data pump dump file. Cataloging such a backup piece is not supported.
- ORA-19934: cannot validate block 0
-
Cause: An attempt was made to validate block 0 of a datafile.
- ORA-19935: During the back up, the data file string is deleted, or is moved or rekeyed to string.
-
Cause: The data file was deleted, moved, or rekeyed.
- ORA-19936: some tablespaces were not found in backup set
-
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.
- ORA-19937: tablespace string was not found in backup set
-
Cause: The indicated tablespace could not be restored because it was not in this backup set.
- ORA-19938: can not backup Data Pump dump or PDB unplug XML file, requires COMPATIBLE string or higher.
-
Cause: An attempt was made to perform a Data Pump dump file or PDB unplug XML file backup with a database compatibility that was not high enough.
- ORA-19939: Data Pump dump file can only be included in a cross-platform backup
-
Cause: Data Pump dump file backup requested but the backup conversation is not a cross-platform conversation.
- ORA-19940: cannot use cross-platform backups to convert whole database to different endianess
-
Cause: Cross-platform backups or restores of whole database between different endianess was requested but it is not supported.
- ORA-19941: invalid blocksize in cross-platform datafile string
-
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.
- ORA-19942: datafile copy string not created with compatibility 10.0 or greater
-
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.
- ORA-19943: Data Pump dump file not found in backup set
-
Cause: The Data Pump dump file could not be restored because it was not in this backup set.
- ORA-19944: Specified platform: 'string' does not match piece header platform: 'string'
-
Cause: The backup piece did not belong to the platform specified in FROM PLATFORM.
- ORA-19945: file string already included to be restored to string
-
Cause: This file was already specified for inclusion in this restore conversation. The restore conversation may process only a single instance of a datafile.
- ORA-19946: Cannot determine block size of backup piece 'string' (string)
-
Cause: It was not possible to determine the cross-platform transportable backup piece block size.
- ORA-19947: Invalid block size string in backup piece 'string' from specified platform 'string'
-
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.
- ORA-19948: Backup piece does not contain a cross-platform datafile backup, reason=string
-
Cause: A cross-platform transportable restore was specified but the backup piece was not produced with the correct command.
- ORA-19949: Specified platform: 'string' has different endianess than piece 'string', cannot read
-
Cause: The backup piece had a different endianess than the platform specified in FROM PLATFORM.
- ORA-19950: tablespace string already included to be restored
-
Cause: This tablespace was already specified for inclusion in this restore conversation.
- ORA-19951: cannot modify control file until DBNEWID is completed
-
Cause: An operation requiring to modify the control file was attempted, but a NID change is in progress.
- ORA-19952: database should be mounted exclusively
-
Cause: The database was started in parallel mode. To change the DBID, the database must be mounted exclusively.
- ORA-19953: database should not be open
-
Cause: The database was open. To change the DBID, the database must be mounted exclusively.
- ORA-19954: control file is not current
-
Cause: The operation failed because a non-current, non-standby control file was mounted.
- ORA-19955: only one open thread is allowed to change the DBID
-
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.
- ORA-19956: database should have no offline immediate datafiles
-
Cause: The operation failed because the database had one or more datafiles that were in OFFLINE IMMEDIATE mode.
- ORA-19957: database should have no datafiles in unknown state
-
Cause: The operation failed because the database had one or more datafiles that were in an unknown state.
- ORA-19958: potential deadlock involving DIAG process
-
Cause: DIAG requested a control file operation that may lead to a deadlock
- ORA-19959: DBNEWID utility only allowed in CDB$ROOT
-
Cause: An attempt was made to use the DBNEWID utility in a pluggable database.
- ORA-19960: Internal use only
-
Cause: NID usage
- ORA-19961: compression algorithm string requires advanced compression option to be enabled
-
Cause: Requested compression algorithm in initialization parameter or by RMAN configuration requires that the advanced compression option be enabled and it was not.
- ORA-19962: Compression algorithm string is not valid with release string.
-
Cause: The specified compression algorithm in the initialization parameter requires an older compatibility than the one currently set.
- ORA-19963: error getting logical block size of file string
-
Cause: Error occurred when querying the logical block size of a file.
- ORA-19964: cannot set mirror side %0!s for file %1!s
-
Cause: An error occurred when trying to set the mirror side for a file. The specified mirror could be out of range.
- ORA-19965: ALTER DATABASE RECOVER STANDBY TABLESPACE has been deprecated
-
Cause: The STANDBY TABLESPACE clause of the ALTER DATABASE RECOVER statement (partial_database_recovery clause) has been deprecated.
- ORA-19966: ALTER DATABASE RECOVER STANDBY DATAFILE has been deprecated
-
Cause: The STANDBY DATAFILE clause of the ALTER DATABASE RECOVER statement (partial_database_recovery clause) has been deprecated.
- ORA-19970: multi-instance standby role transition in progress
-
Cause: ALTER DATABASE MOUNT failed because a multi-instance standby role transition was in progress.
- ORA-19971: event 10875 or 10879 is set
-
Cause: Event 10875 or event 10879 was set which prevented the operation from completing with multiple instances running in Oracle RAC.
- ORA-19972: ALTER DATABASE RECOVER TO LOGICAL requires one instance left
-
Cause: ALTER DATABASE RECOVER TO LOGICAL required only one instance to be left running.
- ORA-19973: flashback database is not enabled
-
Cause: Physical standby transition to snapshot standby required only one instance left running if flashback database logging was not enabled.
- ORA-19974: database name has changed
-
Cause: Physical standby role transition required only one instance left running if database name was changed and flashback database logging was enabled.
- ORA-19975: database must not be started in any other instance
-
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.
- ORA-19976: a concurrent standby role transition in progress
-
Cause: The standby role transition operation failed because a concurrent standby role transition was already in progress.
- ORA-19980: cannot open Data Pump dump file string
-
Cause: When attempting to open the specified dump file, an error was received.
- ORA-19981: cannot read header of Data Pump dump file string
-
Cause: When attempting to read the header of the specified dump file, an error was received.
- ORA-19982: file string is not a Data Pump dump file
-
Cause: The specified dump file did not contain data created by Data Pump.
- ORA-19983: Data Pump dump file could not be verified
-
Cause: Some data blocks for the Data Pump dump file were corrupt in the backup set.
- ORA-19984: foreign data file copy filename does not exist for file number string
-
Cause: Data files could not be restored from this backup set. A full backup restore may not have been performed.
- ORA-19985: Data Pump dump file can only be requested in a cross-platform restore
-
Cause: Data Pump dump file restore requested but the restore conversation is not a cross-platform conversation.
- ORA-19986: archived log backup piece found for cross-platform backup
-
Cause: A cross-platform backup was requested for a backup piece that contained archived logs.
- ORA-19987: unknown platform ID string
-
Cause: The platform ID obtained from a cross-platform backup was incorrect.
- ORA-19988: must specify FROM PLATFORM for cross-platform restore of backup sets with pre-12.1 compatibility
-
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.
- ORA-19990: restore from cross-platform encrypted backup is not supported
-
Cause: A cross-platform restore was requested from an encrypted backup set.
- ORA-19991: Cross-platform encrypted backups to a platform with a different endianness are not supported.
-
Cause: A cross-platform backup was requested for an encrypted backup to a platform with different endianness from the current platform.
- ORA-19992: cross-platform backup of encrypted backup piece with different endianess is not supported
-
Cause: A cross-platform backup was requested for an encrypted backup piece with different endianess from the current platform.
- ORA-19993: must specify FROM PLATFORM for cross-platform backup of backup pieces with compatibility set prior to 12.1
-
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.
- ORA-19994: cross-platform backup of compressed backups to different endianess is not supported
-
Cause: A cross-platform backup was requested for a compressed backup to a different endianess from the current platform.
- ORA-19995: controlfile cannot be restored from a cross-platform backup with different endianess
-
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.
- ORA-19996: cross-platform backup of backup pieces with pre-10.2 compatibility is not supported
-
Cause: A cross-platform backup was requested for a backup created with pre-10.2 compatibility.
- ORA-19997: backup pieces prior to 10.2 cannot be operated for cross-platform
-
Cause: A cross-platform operation was requested for a backup created with pre-10.2 compatibility.
- ORA-19998: data file string already included to be plugged
-
Cause: This data file was already specified for inclusion in this restore conversation.