Release 8.1.5
A67785-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8i Error Messages Release 8.1.5 A67785-01 |
|
ORA-19500 device block size string is invalid
Cause: The device block size returned by sequential I/O OSD is invalid.
Action: If the block size was set by using the PARMS option of the Recovery Manager ALLOCATE CHANNEL command, then the specified block size must be changed. If no PARMS option was specified on the ALLOCATE CHANNEL command, then this is an internal error that should be reported to Oracle.
ORA-19501 read error on file "string", blockno string (blocksize=string)
Cause: Read error on input file.
Action: Check the file.
ORA-19502 write error on file "string", blockno string (blocksize=string)
Cause: Write error on output file.
Action: Check the file.
ORA-19503 cannot obtain information on device, name="string", type="string", parms="string"
Cause: Call to get device information returned an error.
Action: Check device name, type, and parameters.
ORA-19504 failed to create file "string"
Cause: Call to create file returned an error.
Action: Check additional messages and check access permissions.
ORA-19505 failed to identify file "string"
Cause: Call to identify the file returned an error.
Action: Check additional messages, and check whether the file exists.
ORA-19506 failed to create sequential file, name="string", parms="string"
Cause: Call to create the sequential file returned an error.
Action: Check additional messages, check access permissions.
ORA-19507 failed to retrieve sequential file, handle="string", parms="string"
Cause: Call to retrieve the sequential file returned an error.
Action: Check additional messages, and check if the file exists.
ORA-19508 failed to delete file "string"
Cause: Call to delete the file returned an error.
Action: Check additional messages.
ORA-19509 failed to delete sequential file, handle="string", parms="string"
Cause: Call to delete the sequential file returned an error.
Action: Check additional messages.
ORA-19510 failed to set size of string blocks for file "string" (blocksize=string)
Cause: Call to resize the file returned an error.
Action: Check additional messages.
ORA-19511 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.
Action: If the text of message 19511 does not provide enough information to resolve the problem, then you should contact the vendor of the media management software.
ORA-19550 cannot use backup/restore functions while using dispatcher
Cause: An attempt was made to use backup/restore functions while connected to the dispatcher in a multi-threaded server. This is not allowed because the device that is used for backup and restore must remain allocated to a single process.
Action: Connect directly to the instance then re-execute the backup or restore function.
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.
Action: Either attempt to allocate another device or wait until the required device is no longer busy.
ORA-19552 device type string is invalid
Cause: The device type indicated is invalid.
Action: Supply a correct device type and retry the allocation.
ORA-19553 device name string is invalid
Cause: The device name indicated is invalid.
Action: Supply a correct device name and retry the allocation.
ORA-19554 error allocating device, device type: string, device name: string
Cause: The specified device could not be allocated.
Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.
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.
Action: Specify a correct value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST. If the archive log parameters LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST are in use, set parameter LOG_ARCHIVE_MIN_SUCCEED_DEST to either 1 or 2.
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.
Action: Change the destination value for the LOG_ARCHIVE_DUPLEX_DEST parameter.
ORA-19557 device error, device type: string, device name: string
Cause: An error occurred in the platform-specific device code.
Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.
ORA-19558 error de-allocating device
Cause: The specified device could not be de-allocated.
Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.
ORA-19559 error sending device command: string
Cause: An error occurred while sending the indicated command to the session device.
Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.
ORA-19560 string is not a valid device limit
Cause: An invalid type of device limit was specified in a call to X$DBMS_BACKUP_RESTORE.SETLIMIT.
Action: Use one of the documented limits: KBYTES, READRATE, or PARALLEL.
ORA-19561 string requires null session device
Cause: The attempted datafile, archive log, or control file copy requires that a null device be allocated to the session, but a non-null device was found.
Action: Deallocate the current device and allocate a null device to the session, then retry the copy.
ORA-19562 file string is empty
Cause: The indicated file, which is an archive log, control file, or datafile was found to be empty during a copy, backup, or scan] operation.
Action: Ensure that the correct files are being specified for the copy or backup operation.
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, the header was not recognized as a valid file header for a file of the indicated type (datafile, archived log, or control file), belonging to the current database.
Action: Ensure that the correct files are being specified for the copy or backup operation.
ORA-19564 error occurred writing string bytes at block number string
Cause: An error occurred while writing to a file.
Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error if possible, then retry the copy, backup, or restore operation.
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.
Action: Specify BACKUP_TAPE_IO_SLAVES=TRUE in the INIT.ORA file, or do not specify duplexing to sequential devices.
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.
Action: No action required. The copy or backup operation fails. The session trace file contains detailed information about which blocks were corrupt.
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.
Action: Retry the resize after the backup or copy is complete.
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.
Action: Deallocate the current device.
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.
Action: Allocate a device then retry the operation.
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.
Action: Specify a valid file number.
ORA-19571 string recid string stamp string not found in controlfile
Cause: The input file specified for a copy or backup operation could not be opened because the record describing the file is not found in the control file.
Action: Specify a correct RECID/stamp and retry the copy or backup.
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.
Action: Wait for the resize to complete then retry the copy or backup.
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.
Action: Wait until the conflicting operation is complete, then retry the copy or backup. If the database is in NOARCHIVELOG mode, then all files being backed up must be closed cleanly.
ORA-19574 output filename must be specified
Cause: This type of copy or restore requires an output file name.
Action: Specify an output file name and retry the copy.
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.
Action: The input copy or backup piece is probably corrupt. If another backup or copy exists of the file that is being restored, then the corrupt file can be deleted from the recovery catalog and the operation can be restarted.
ORA-19576 datafile string not defined in control file
Cause: The specified file number was not found in the control file.
Action: Specify a correct file number and retry the operation.
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.
Action: Either specify an output file name or issue a SQL RENAME command to enter a valid name for this file in the control file.
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.
Action: Before retrying the backup, make sure the backup pieces will fit in the volume, or disable duplexing.
ORA-19580 string conversation not active
Cause: A backup or restore operation was attempted before a conversation was started.
Action: Start a conversation then retry the operation.
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.
Action: Specify some files then retry the operation.
ORA-19583 conversation terminated due to error
Cause: An error occurred which forced the termination of the current backup or restore conversation.
Action: There should be other error messages to help identify the cause of the problem. Correct the error and begin another conversation.
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.
Action: Specify a different name and retry the operation.
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.
Action: Retry the piece with a larger piece of output media.
ORA-19586 string k-byte limit is too small to hold piece directory
Cause: The user-specified limit of k-bytes per backup piece is not enough to hold the backup set control data.
Action: Use the setLimit procedure to increase the k-byte limit and retry the operation.
ORA-19587 error occurred reading string bytes at block number string
Cause: An error occurred while reading from a file.
Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error then retry the copy, backup, or restore operation.
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.
Action: If you know the name of the file you wish to copy, then inspect it and then retry the copy specifying the new RECID.
ORA-19589 string is not a snapshot or backup controlfile
Cause: The control file that is the source for a backup or copy operation is not a snapshot or backup control file.
Action: Specify the name of a snapshot or backup control file.
ORA-19590 conversation already active
Cause: An attempt was made to begin a backup or restore conversation, but another conversation is already active in this session.
Action: Either continue the current conversation, or call backupCancel or restoreCancel to end the current conversation before starting a new one.
ORA-19592 wrong string conversation type
Cause: An attempt was made to specify a type of file to be backed-up or restored, but the current conversation cannot process this type of file. For example, you specified an archived log to be included in a datafile backup set. The specified file will not be included in the backup or restore operation.
Action: No action required. The conversation is still active, and more files can be specified.
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.
Action: No action required. The conversation is still active, and more files can be specified.
ORA-19594 controlfile 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.
Action: No action required. The conversation is still active, and more files can be specified.
ORA-19595 archivelog thread string sequence string already included as string
Cause: The indicated archive log has already been specified for inclusion in this backup conversation. A backup conversation may process only one copy of any archive log.
Action: No action required. The conversation is still active, and more files can be specified.
ORA-19596 snapshot controlfile has not been created
Cause: You requested that the snapshot control file be included in the backup set, but no snapshot control file has been created for this instance.
Action: Specify a different control file name, or call cfileMakeAndUseSnapshot to create the snapshot control file.
ORA-19597 file string blocksize string does not match set blocksize 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.
Action: Specify a file that has the same block size as the rest of the files in the backup set. The conversation is still active and more files can be specified.
ORA-19598 starting SCN must be specified for incremental backup
Cause: No starting SCN was specified to backupDataFile or backupDataFileCopy, but the current backup conversation is for an incremental backup, which requires that a non-zero SCN be specified for all datafiles.
Action: The conversation is still active. Respecify the datafile with a non-zero SCN.
ORA-19599 block number string is corrupt in string string
Cause: A corrupt block was found in a control file, archive log, or backup piece that is being read for a backup or copy. Corruption shall not be tolerated in control files, archive logs, or backup pieces.
Action: No action required. The copy or backup operation fails. Note that in the case of a backup set, the conversation is still active and the piece may be retried.
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.
Action: Other messages should display to help pinpoint the cause and the solution.
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.
Action: See other error message.
ORA-19602 cannot backup or copy active file in NOARCHIVELOG mode
Cause: An attempt was made to copy or backup a file that was not closed cleanly, and the database was in NOARCHIVELOG mode. This is not allowed because when restored, the file will require redo application before it is usable, and redo is not currently being saved beyond the contents of the online redo logs.
Action: Take the tablespace offline clean or close the database and retry the copy or backup.
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.
Action: You cannot specify more files to be processed during a backup or restore conversation after the first backup piece has been processed. If more files must be specified, you must begin a new conversation.
ORA-19605 input filename must be specified
Cause: The input file name was not specified for a control file copy operation.
Action: Specify an input file name and retry the operation.
ORA-19606 Cannot copy or restore to snapshot controlfile
Cause: A control file copy or restore operation specified the name of the snapshot control file as the output file. It is not permitted to overwrite the snapshot control file in this manner. Other methods are available to create the snapshot control file.
Action: Specify a different file name and retry the operation. If this is a restore, then the restore conversation remains active and more files may be specified.
ORA-19607 string is an active controlfile
Cause: A control file copy, restore, or backup specified the name of a control file named in the INIT.ORA file as the input or output file.
Action: Specify a different file name and retry the operation. If this is a backup or restore conversation, then the conversation remains active and more files may be specified.
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.
Action: Specify a different file name and retry the operation.
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.
Action: Specify the correct backup piece and retry the operation.
ORA-19610 directory block string is corrupt
Cause: The indicated directory block failed checksum validation. This backup piece is unusable.
Action: Supply another copy of the same backup piece, or terminate the restore conversation.
ORA-19611 backup piece out of order. Expected string but found string
Cause: This backup piece is out of sequence.
Action: Supply the correct backup piece.
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.
Action: The restore conversation remains active, and the current piece must be reprocessed. If the failure cannot be resolved by reprocessing the current piece, then the restore conversation must be cancelled.
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.
Action: This message is issued when the directory from the first backup piece is read and one or more files named for restoration were not found. The restore conversation is still active, but no data has been read and you must supply the first backup piece of a backup set that contains all of the requested files.
ORA-19614 archivelog 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.
Action: This message is issued when the directory from the first backup piece is read and one or more files named for restoration were not found. The restore conversation is still active, but no data has been read and you must supply the first backup piece of a backup set that contains all of the requested files.
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.
Action: See the instructions for message 19613.
ORA-19616 output filename 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.
Action: The restore conversation remains active. If you wish to restore datafiles without their target file names, then mount the database before continuing. Otherwise, a target file name must be specified on all datafile restoration calls.
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.
Action: The restore conversation remains active, and you may continue to specify archived log files for inclusion in the backup set.
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.
Action: You must cancel and restart the conversation if you wish to specify files to restore.
ORA-19619 cannot call restoreValidate after files have been named
Cause: restoreValidate was called after some files had already been specified for restoration.
Action: You must cancel and restart the conversation if you wish to call restoreValidate.
ORA-19621 archivelog range has already been specified
Cause: A range of logs has already been specified. Only one SCN range may be specified per conversation.
Action: The restore conversation remains active and more logs may be specified by thread and sequence number, if desired.
ORA-19622 archivelog 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.
Action: The restore conversation remains active, and the current piece must be reprocessed. If the failure cannot be resolved by reprocessing the current piece, then the restore conversation must be cancelled.
ORA-19623 file string is open
Cause: A SwitchToCopy operation specified a datafile copy whose parent datafile is open.
Action: Take the owning tablespace offline or close the database, then retry the operation.
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.
Action: This message is used by Recovery Manager to decide whether or not to retry the operation.
ORA-19625 error identifying file string
Cause: A file specified as input to a copy or backup operation, or as the target for an incremental restore, could not be identified as an Oracle file. An operating system-specific error accompanies this error to help pinpoint the problem.
Action: Specify an different file and retry the operation.
ORA-19626 backup set type is string - can not be processed by this conversation
Cause: The data in the backup set is not compatible with the current conversation.
Action: Either supply the first piece from a backup set that matches the current conversation or start a new restore conversation which can process this backup set.
ORA-19627 cannot read backup pieces during controlfile application
Cause: This is a control file restore conversation, which is using the offline range information from one or more control files to update datafile checkpoint data. Backup sets are not used during this type of conversation.
Action: The conversation is still active and more control files may be applied.
ORA-19628 invalid SCN range
Cause: The starting SCN for restoreRedoLogRange is greater than the ending SCN.
Action: Specify a starting SCN which is less than or equal to the ending SCN.
ORA-19629 no files in specified archivelog SCN range
Cause: This backup set contains no files in the specified range.
Action: Either supply a backup set that contains files in the correct range or start a new conversation and specify a range which will select some files from this backup set.
ORA-19630 end of volume encountered while copying backup piece
Cause: While copying a backup piece from the operating system native file system to an output device, the output device encountered end-of-volume.
Action: The copy fails. This could happen if a tape was used which is not large enough to hold the entire backup piece.
ORA-19631 archivelog record contains no file name
Cause: This archive log record represents a switch into an active log that took place without archiving its prior contents. The prior contents of the log file are lost.
Action: Specify the RECID of an archive log record that contains a file name. Fixed view V$ARCHIVED_LOG can be used to examine the archived logs.
ORA-19632 file name not found in controlfile
Cause: The name passed to getFno was not found in the control file.
Action: Supply a valid file name.
ORA-19633 controlfile record string is out of sync with recovery catalog
Cause: The control file record describing the file to be deleted in a call to deleteBackupPiece, deleteDataFilecopy, proxyDelete or deleteArchivedLog does not match the validation data supplied by Recovery Manager.
Action: contact Oracle Customer Support.
ORA-19634 filename required for this function
Cause: The FNAME or handle parameter was not specified for deletePiece, deleteDataFileCopy, deleteRedoLog or proxyDelete.
Action: Specify the FNAME or handle parameter when calling these functions.
ORA-19635 input and output filenames are identical
Cause: Identical input and output file names were specified for a datafile copy operation.
Action: Specify an output file name which is different from the input file name.
ORA-19636 archivelog thread string sequence string already included
Cause: The indicated archive log has already been specified for inclusion in this restore conversation. A restore conversation may process only one copy of any archive log.
Action: No action required. The conversation is still active, and more files can be specified.
ORA-19637 backupPieceCreate requires file name when using DISK device
Cause: The session device is currently allocated to disk, and so a file name is required.
Action: Supply a file name and retry the operation.
ORA-19638 file string is not current enough to apply this incremental backup
Cause: The checkpoint of the target for this incremental backup is less than the start of the incremental backup. If this backup were applied, then any changes made between the datafile checkpoint and the start of the incremental backup could be lost.
Action: Supply a backup set that can be applied and retry the operation.
ORA-19639 file string is more current than this incremental backup
Cause: The checkpoint of the target for this incremental backup is greater than or equal to the checkpoint of the file in the incremental backup set. This backup cannot advance the checkpoint of the target file, so there is no point in applying it.
Action: Supply a backup set that can be applied and retry the operation.
ORA-19640 datafile checkpoint is SCN string time string
Cause: This message identifies the datafile checkpoint for a datafile that was too old to take an incremental backup from, or the target of an incremental restore that could not be applied.
Action: See other error message.
ORA-19641 backup datafile checkpoint is SCN string time string
Cause: This message identifies the checkpoint of a datafile in an incremental backup set that could not be applied.
Action: See other error message.
ORA-19642 incremental-start SCN is string
Cause: This message identifies the starting SCN of an incremental backup that could not be applied.
Action: See other error message.
ORA-19643 datafile string: incremental-start SCN is too recent
Cause: The incremental-start SCN which was specified when starting an incremental datafile backup is greater than the datafile checkpoint SCN, which could cause some blocks to be missed.
Action: Specify a smaller incremental-start SCN.
ORA-19644 datafile string: incremental-start SCN is prior to resetlogs SCN string
Cause: The incremental-start SCN which was specified when starting an incremental datafile backup is less than the resetlogs SCN.
Action: Specify a larger incremental-start SCN.
ORA-19645 datafile string: incremental-start SCN is prior to creation SCN string
Cause: The incremental-start SCN which was specified when starting an incremental datafile backup is less than the datafile's creation SCN.
Action: Specify a larger incremental-start SCN.
ORA-19646 cannot change size of datafile string from string to string
Cause: The indicated file was resized before this incremental backup was taken, but the incremental backup failed to set the file to the new size.
Action: Examine the other messages which should be present to indicate the cause of the failure.
ORA-19647 non-zero LEVEL cannot be specified when INCREMENTAL is FALSE
Cause: BackupSetDataFile was called with a non-zero BACKUP_LEVEL and a FALSE incremental indication.
Action: Either set incremental to TRUE or change BACKUP_LEVEL to zero.
ORA-19648 datafile string: incremental-start SCN equals checkpoint SCN
Cause: The incremental-start SCN which was specified when starting an incremental datafile backup is equal to the datafile's checkpoint SCN. Since an incremental backup can only be applied to a datafile whose checkpoint SCN is between the backup set incremental-start SCN (inclusive) and the backup set checkpoint SCN (exclusive), there is no datafile that this backup set could ever be applied to.
Action: Specify a smaller incremental-start SCN.
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.
Action: Specify the RECID/stamp of a record that exists in the control file copy.
ORA-19650 Offline-range record recid string stamp string in file string has SCN string
Cause: This messages identifies the offline-clean SCN from the indicated offline-range record in the indicated file.
Action: See other error message.
ORA-19651 cannot apply offline-range record to datafile string: SCN mismatch
Cause: applyOfflineRange cannot apply an offline-range record to a target datafile unless the datafile's checkpoint SCN exactly matches the offline-clean SCN in the specified offline-range record.
Action: Specify an offline-range record whose offline-clean SCN matches the target datafile's checkpoint.
ORA-19652 cannot apply offline-range record to datafile string: file is fuzzy
Cause: The target datafile for an applyOfflineRange call is fuzzy.
Action: Specify a target datafile that is closed cleanly.
ORA-19653 cannot switch to older file incarnation
Cause: SwitchToCopy was called with a datafile copy for a datafile that was dropped prior to the time this control file was backed up.
Action: Restore and mount an earlier control file. It is acceptable to use a control file that was backed up prior to the creation of the specified datafile.
ORA-19654 must use backup controlfile to switch file incarnations
Cause: This switchToCopy operation is attempting to switch incarnations of a datafile, but the currently mounted control file is not a backup control file.
Action: Restore and mount a backup control file.
ORA-19655 cannot switch to incarnation with different resetlogs data
Cause: This switchToCopy operation is attempting to switch to a datafile which comes from a different resetlogs version of the database.
Action: Either restore a backup control file that was taken from the same database version as the target datafile-copy, or switch to a different datafile-copy.
ORA-19656 cannot backup, copy, or delete online log string
Cause: The indicated log file is an active log. You can only backup, copy, or delete archived logs.
Action: The indicated log file cannot be processed. Select another file.
ORA-19657 cannot inspect current datafile string
Cause: The file being inspected is already part of the currently mounted database.
Action: No action required. The file is already part of the 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.
Action: The indicated file cannot be processed; inspect another 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.
Action: This incremental cannot be applied to this datafile. If you wish to recover the file to the resetlogs SCN so that the database can be opened with the RESETLOGS option, then you must use redo-log recovery, not incremental restore, to continue recovering this file.
ORA-19660 some files in the backup set could not be verified
Cause: A restore conversation was made to verify all the files in a backup set, and the files which were printed in messages 19661 or 19662 could not be verified because corrupt blocks for those files were found in the backup set.
Action: Unless the damage to the backup set can be repaired, the indicated files cannot be restored from this backup set.
ORA-19661 datafile string could not be verified
Cause: Some data blocks for the indicated datafile were corrupt in the backup set.
Action: Unless the damage to the backup set can be repaired, the indicated datafile cannot be restored from this backup set.
ORA-19662 archived log thread string sequence string could not be verified
Cause: Some data blocks for the indicated archived log were corrupt in the backup set.
Action: Unless the damage to the backup set can be repaired, the indicated archived log cannot be restored from this backup set.
ORA-19663 cannot apply current offline range to datafile string
Cause: An attempt was made to apply the current offline range to the specified datafile, but the datafile is either not current enough or is not at the correct SCN to apply the offline range.
Action: The datafile remains unchanged.
ORA-19664 file type: string, file name: string
Cause: This message is issued to identify the file which is the subject of an error.
Action: No action required. This is an informational message. There should be other Oracle messages explaining the cause of the 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.
Action: This file is not usable; it has most likely been truncated.
ORA-19666 cannot do incremental restore of the controlfile
Cause: The control file was included in an incremental restore conversation
Action: If you wish to restore the control file, you must do a full restore of the control file.
ORA-19667 cannot do incremental restore of datafile string
Cause: The backup of the datafile is a full backup.
Action: If you wish to restore the datafile, you must do a full restore of the datafile.
ORA-19668 cannot do full restore of datafile string
Cause: The backup of the datafile is an incremental backup.
Action: If you wish to restore the datafile, you must do an incremental restore of the datafile.
ORA-19669 proxy copy functions cannot be run on DISK channel
Cause: A proxy copy procedure was called, but the device which is allocated to the current session has type DISK.
Action: Allocate a non-DISK channel and retry the operation. Note that proxy copy requires a third-party media management software product that supports the this backup/restore feature.
ORA-19670 file string already being restored
Cause: A proxy restore function has already named this file as a restore destination.
Action: Use a different file name. If this message occurs during a Recovery Manager job, then this is an internal error in Recovery Manager, and you should contact Oracle Customer Support.
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. This is an internal error in the media management software which is linked with Oracle to provide backup/restore services.
Action: Contact the media management software vendor.
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. This is an internal error in the media management software which is linked with Oracle to provide backup/restore services.
Action: Contact the media management software vendor.
ORA-19673 error during proxy copy of file string
Cause: During a proxy backup or restore, an error occurred while copying this file, but other files may have been copied successfully.
Action: There should be other errors on the error stack which explain why the file could not be successfully copied.
ORA-19674 file string is already being backed up with proxy copy
Cause: Recovery Manager attempted to back up the specified file with proxy copy, but the file is already being backed up by another Recovery Manager job.
Action: Wait until the other Recovery Manager backup of this file is complete, then retry the backup.
ORA-19675 file string was modified during proxy copy
Cause: A proxy backup of the specified file failed because the file was brought online or otherwise modified while the proxy backup was in progress. This file was offline or read only when the backup began, so the file was not put into hot-backup mode, therefore no modifications are permitted while the backup is in progress.
Action: Take another backup of this file.
ORA-19676 one or more files failed during proxy backup or restore
Cause: During a proxy backup or restore, errors were encountered while processing some files. The files for which no error messages are shown were processed successfully.
Action: Examine the messages regarding the specific files to determine the cause of the problems.
ORA-19700 device type exceeds maximum length of string
Cause: The device type indicated is invalid.
Action: Supply a correct device type and retry the allocation.
ORA-19701 device name exceeds maximum length of string
Cause: The device name indicated is invalid.
Action: Supply a correct device name and retry the allocation.
ORA-19702 device parameter exceeds maximum length of string
Cause: The device parameter exceeds the port-specific maximum length.
Action: Correct the parameter and retry the operation.
ORA-19703 device command string exceeds maximum length of string
Cause: The device command string exceeds maximum length.
Action: Correct the command and retry the operation.
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.
Action: Retry the operation with a shorter file name.
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.
Action: Supply a shorter tag and retry the operation.
ORA-19706 invalid SCN
Cause: The input SCN is either not a positive integer or too large.
Action: Check the input SCN and make sure it is a valid SCN.
ORA-19707 invalid record block number - string
Cause: The input number is either negative or too large.
Action: Check the input record block number and make sure it is a valid number clauses in the CREATE DATABASE statement.
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.
Action: Supply a shorter destination and retry the operation.
ORA-19709 numeric parameter must be non-negative integer
Cause: A numeric parameter to an X$DBMS_BACKUP_RESTORE procedure is negative or contains a fractional portion.
Action: Supply a valid numeric parameter.
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.
Action: See other errors on the error stack to look for the source of the problem.
ORA-19721 Cannot find datafile with absolute file number string in tablespace string
Cause: Cannot find one of the data files that should be in the pluggable set.
Action: Make sure all datafiles are specified via import command line option or parameter files.
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.
Action: Make sure the right datafiles are transported. Make sure the datafile is copied while its tablespace is read only.
ORA-19723 Cannot recreate plugged in read-only datafile string
Cause: The datafile is plugged in read only. It cannot re-created.
Action: Use ALTER DATABASE RENAME FILE command instead.
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.
Action: retry the query.
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.
Action: Retry the operation.
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.
Action: Raise the value of the COMPATIBLE initialization parameter and retry the operation.
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.
Action: Upgrade Oracle and retry the operation.
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 cannot exchange the table with the partition in this case.
Action: Use the ALTER TABLE MOVE PARTITION command to move the offending partition, so that the partition will get a new data object number. Retry the operation then.
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.
Action: Use the correct 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.
Action: Bring the datafile online and retry the operation.
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.
Action: Use the correct control file and continue 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.
Action: Use the correct export file and retry the operation.
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.
Action: Shutdown and restart with a higher compatibility setting.
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.
Action: Either restore the converted datafile or continue recovering the 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.
Action: Either restore the initial version of the plugged-in datafile, or continue database recovery, which will recover the control file.
ORA-19999 skip_row procedure was called
Cause: The SKIP_ROW procedure was called which raises this error.
Action: SKIP_ROW should only be called within a trigger or a procedure called by a trigger.
ORA-20000 string
Cause: The stored procedure RAISE_APPLICATION_ERROR was called which causes this error to be generated.
Action: Correct the problem as described in the error message or contact the application administrator or database administrator for more information.
ORA-21000 error number argument to raise_application_error of stringstring is out of range
Cause: An attempt was made to specify a number not in the allowed range.
Action: Use an error number in the range of -20000 to -20999, inclusive.
ORA-21001 error number argument to raise_system_error of stringstring is out of range
Cause: An attempt was made to specify a number not in the allowed range.
Action: Use an error number in the range of -23300 to -24299, or -29300 to -29399, inclusive.
ORA-21300 objects option not installed
Cause: The objects option is not installed at this site. object types and other object features are, therefore, unavailable.
Action: Install the objects option. The objects option is not part of the Oracle Server product and must be purchased separately. Contact Oracle Customer Support if the objects option needs to be purchased.
ORA-21301 not initialized in object mode
Cause: This function requires the OCI process to be initialized in object mode.
Action: Specify OCI_OBJECT mode when calling OCIInitialize().
ORA-21500 internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
Cause: This is the generic error number for the OCI environment (client-side) internal errors. This indicates that the OCI environment has encountered an exceptional condition.
Action: Report to Oracle Customer Support. The first argument is the internal error number.
ORA-21501 program could not allocate memory
Cause: The operating system has run out of memory.
Action: Take action to make more memory available to the program.
ORA-21503 program terminated by fatal error
Cause: A program is in an unrecoverable error state.
Action: Report to Oracle Customer Support.
ORA-21520 database server driver not installed
Cause: User attempted to access a database server through an object-mode OCI environment but the necessary driver for supporting such access to the database server is not installed or linked in.
Action: Check if the driver corresponding to the database server has been installed/linked in and entered in the server driver table.
ORA-21521 exceeded maximum number of connections in OCI (object mode only)
Cause: User exceeded the maximum number of connections (255) that can be supported by an OCI environment in object mode.
Action: Close some of existing and unused connections before opening more connections.
ORA-21522 attempted to use an invalid connection in OCI (object mode only)
Cause: User attempted to use an invalid connection or a connection that has been terminated in an OCI environment (object mode), or user attempted to de-reference a REF obtained from a connection which has been terminated.
Action: Ensure that the connection exists and is still valid.
ORA-21523 functionality not supported by the server (object mode only)
Cause: User attempted to use a functionality that the server does not support.
Action: Upgrade the server.
ORA-21524 object type mismatch
Cause: The object type of the object is different from what is specified.
Action: Check the type of the object and correct it.
ORA-21525 attribute number or (collection element at index) string violated its constraints
Cause: Attribute value or collection element value violated its constraint.
Action: Change the value of the attribute or collection element such that it meets its constraints. The constraints are specified as part of the attribute or collection element's schema information.
ORA-21526 initialization failed
Cause: The initialization sequence failed. This can happen, for example, if an environment variable such as NLS_DATE_FORMAT is set to an invalid value.
Action: Check that all NLS environment variables are well-formed.
ORA-21560 argument string is null, invalid, or out of range
Cause: The argument is expecting a non-null, valid value but the argument value passed in is null, invalid, or out of range. Examples include when the LOB/FILE positional or size argument has a value outside the range 1 through (4GB - 1), or when an invalid open mode is used to open a file, and so on.
Action: Check your program and correct the caller of the routine to not pass a null, invalid or out-of-range argument value.
ORA-21600 path expression too long
Cause: The path expression that is supplied by the user is too long. The path expression is used to specify the position of an attribute in an object. This error occurs when one of the intermediate elements in the path expression refers to an attribute of a built-in type. Thus, the OCI function cannot proceed on to process the rest of the elements in the path expression.
Action: Pass in the correct path expression to locate the attribute.
ORA-21601 attribute is not an object
Cause: The user attempts to perform an operation (that is valid only for an object) to an attribute of a built-in type. An example of such an illegal operation is to dynamically set a null structure to an attribute of a built-in type.
Action: Avoid performing such operation to an attribute of built-in type.
ORA-21602 operation does not support the specified typecode
Cause: The user attempts to perform an operation that does not support the specified type code.
Action: Use the range of valid type codes that are supported by this operation.
ORA-21603 property id [string] is invalid
Cause: The specified property ID is invalid.
Action: Specify a valid property ID. Valid property IDs are enumerated by OCIObjectPropId.
ORA-21604 property [string] is not a property of transient or value instances
Cause: An attempt was made to get a property which applies only to persistent objects.
Action: Check the lifetime and only get this property for persistent objects.
ORA-21605 property [string] is not a property of value instances
Cause: An attempt was made to get a property which applies only to persistent and transient objects.
Action: Check the lifetime and only get this property for persistent and transient objects.
ORA-21606 can not free this object
Cause: An attempt was made to free an object that is persistent and dirty and the OCI_OBJECTFREE_FORCE flag is not specified.
Action: Either flush the persistent object or set the flag to OCI_OBJECTFREE_FORCE
ORA-21607 memory cartridge service handle not initialized
Cause: Attempt to use the handle without initializing it.
Action: Initialize the memory cartridge service handle.
ORA-21608 duration is invalid for this function
Cause: Attempt to use a duration not valid for this function.
Action: Use a valid duration: a previously created user duration or OCI_DURATION_STATEMENT or OCI_DURATION_SESSION. For callout duration or external procedure duration, use OCIExtProcAllocCallMemory.
ORA-21609 memory being resized without being allocated first
Cause: Attempt to resize memory without allocating it first.
Action: Allocate the memory first before resizing it.
ORA-21610 size [string] is invalid
Cause: Attempt to resize memory with invalid size.
Action: Pass in a valid size (must be a positive integer).
ORA-21611 key length [string] is invalid
Cause: Attempt to use an invalid key length.
Action: Key length is invalid and valid range is 0 to 64.
ORA-21612 key is already being used
Cause: Attempt to use a key that is already used.
Action: Use a new key that is not yet being used.
ORA-21613 key does not exist
Cause: Attempt to use a non-existent key.
Action: Use a key that already exists.
ORA-21614 constraint violation for attribute number string
Cause: Constraints on the attribute were violated.
Action: Correct the value (of the attribute) so that it satisfies constraints.
ORA-21615 copy of an OTS (named or simple) instance failed
Cause: See following message.
Action: Check that no attribute value violates constraints.
ORA-21700 object does not exist or is marked for delete
Cause: User attempted to perform an inappropriate operation to an object that is non-existent or marked for delete. Operations such as pinning, deleting and updating cannot be applied to an object that is non-existent or marked for delete.
Action: Re-initialize the reference to reference an existent object or unmark the object.
ORA-21701 attempt to flush objects to different servers
Cause: User attempted to flush objects to different servers in one function call. These objects are obtained by calling a callback functions provided by the program.
Action: Avoid performing this operation.
ORA-21702 object is not instantiated or has been de-instantiated in cache
Cause: User attempted to perform an inappropriate operation to a transient object that is not instantiated in the object cache. Operations that cannot be applied to a not-instantiated transient object include deleting or pinning such an object.
Action: Check their code to see if they are performing such an operation without instantiating the object first, or performing such an operation after the allocation duration of the object has expired.
ORA-21703 cannot flush an object that is not modified
Cause: See the error message.
Action: The object should not be flushed.
ORA-21704 cannot terminate cache or connection without flushing first
Cause: See the error message.
Action: The transaction should be aborted or committed before terminating the cache or connection.
ORA-21705 service context is invalid
Cause: The service context that is supplied by the user is not valid.
Action: Establish the service context.
ORA-21706 duration does not exist or is invalid
Cause: The duration number that is supplied by the user is not valid.
Action: Establish the duration or use a correct predefined duration.
ORA-21707 pin duration is longer than allocation duration
Cause: The pin duration supplied by the user is longer than the allocation duration. This affects operations such as pinning and setting default parameters.
Action: Use a shorter pin duration or use the null duration.
ORA-21708 inappropriate operation on a transient object
Cause: An attempt was made to perform an inappropriate operation on a transient object. Operations that cannot be applied to a transient object include flushing and locking.
Action: Avoid performing such operations on a transient object.
ORA-21709 cannot refresh an object that has been modified
Cause: An attempt was made to refresh an object that has been marked for delete, update or insert (new).
Action: Unmark the object before refreshing it.
ORA-21710 argument is expecting a valid memory address of an object
Cause: The object memory address that is supplied by the user is invalid. The user may have passed in a bad memory address to a function that is expecting a valid memory address of an object.
Action: Pass in a valid memory address of an object to the function.
ORA-21779 duration not active
Cause: An attempt was made to use a duration that has been terminated.
Action: Avoid performing such operation.
ORA-22053 overflow error
Cause: This operation's result is above the range of Oracle number.
Action: Decrease the input value(s) so that the result is in the range of Oracle number.
ORA-22054 underflow error
Cause: This operation's result is below the range of Oracle number.
Action: Increase the input value(s) so that the result is in the range of Oracle number.
ORA-22055 unknown sign flag value [string]
Cause: Signed flag used is not OCI_NUMBER_SIGNED or OCI_NUMBER_UNSIGNED.
Action: Use either OCI_NUMBER_SIGNED or OCI_NUMBER_UNSIGNED as sign flag.
ORA-22056 value [string] is divided by zero
Cause: Given value is divided by zero.
Action: Modify divisor value to be non-zero.
ORA-22057 bad integer length [string]
Cause: The length of the integer (that is, number of bytes) to be converted to or from an Oracle number is invalid.
Action: Use integer length 1, 2, 4 or 8 bytes only.
ORA-22059 buffer size [string] is too small - [string] is needed
Cause: The buffer to hold the resulting text string is too small.
Action: Provide a buffer of the required size.
ORA-22060 argument [string] is an invalid or uninitialized number
Cause: An invalid or uninitialized number is passed in.
Action: Use a valid number. To initialize number, call OCINumberInit().
ORA-22061 invalid format text [string]
Cause: The numeric format string for converting characters to or from an Oracle number is invalid.
Action: Use valid format string as documented in the Oracle Call Interface Programmer's Guide.
ORA-22062 invalid input string [string]
Cause: The text string for converting to numbers is invalid.
Action: Use a valid input string as documented in the Oracle Call Interface Programmer's Guide.
ORA-22063 reading negative value [string] as unsigned
Cause: An attempt was made to convert a negative number to an unsigned integer.
Action: Use the sign flag ORLTSB to convert a signed number.
ORA-22064 invalid NLS parameter string [string]
Cause: The NLS parameter string for converting characters to or from an Oracle number is invalid.
Action: Use valid format string as documented in the Oracle Call Interface Programmer's Guide.
ORA-22065 number to text translation for the given format causes overflow
Cause: Rounding done due to the given string format causes overflow.
Action: Change the string format such that overflow does not occur.
ORA-22130 buffer size [string] is less than the required size [string]
Cause: The size of the buffer into which the hexadecimal REF string is to be written is too small.
Action: Provide a buffer of the required size.
ORA-22131 hexadecimal string length is zero
Cause: The given hexadecimal string length must be greater than zero.
Action: Specify a length greater than zero.
ORA-22132 hexadecimal string does not correspond to a valid REF
Cause: The given hexadecimal string is invalid.
Action: Provide a valid hexadecimal string which was previously returned by a call to OCIRefToHex().
ORA-22140 given size [string] must be in the range of 0 to [string]
Cause: The given resize size is invalid.
Action: Ensure that the given size is in the required range.
ORA-22150 variable-length array has not been initialized
Cause: An un-initialized variable-length array is being operated upon.
Action: Initialize the variable-length array prior to calling this function.
ORA-22151 cannot resize non-zero variable-length array to zero elements
Cause: An attempt was made to resize a non-zero variable-length array to 0 elements.
Action: Specify a non-zero size.
ORA-22152 destination variable-length array is not initialized
Cause: The variable-length array on the right-hand-side of an assignment or the destination array of an append is not initialized.
Action: Initialize the destination variable-length array prior to calling this function.
ORA-22153 source variable-length array is not initialized
Cause: The variable-length array on the left-hand-side of an assignment or the source array of an append is not initialized.
Action: Initialize the destination variable-length array prior to calling this function.
ORA-22160 element at index [string] does not exist
Cause: Collection element at the given index does not exist.
Action: Specify the index of an element which exists.
ORA-22161 type code [string] is not valid
Cause: Given type code is not valid.
Action: Use one of the type codes enumerated in OCITypeCode.
ORA-22162 element at index [string] has been previously deleted
Cause: An attempt was made to delete a non-existent collection element.
Action: Check for the existence of the element prior to calling this function.
ORA-22163 left hand and right hand side collections are not of same type
Cause: Left hand and right side collections are not of same type.
Action: Ensure that the same collection type is passed for both left hand and right hand side of this function.
ORA-22164 delete element operation is not allowed for variable-length array
Cause: An attempt was made to delete an element of a variable-length array.
Action: Ensure that the collection is not a variable-length array prior to calling this function.
ORA-22165 given index [string] must be in the range of 0 to [string]
Cause: Given index is not in the required range.
Action: Ensure that the given index is in the required range.
ORA-22166 collection is empty
Cause: Given collection is empty.
Action: Test if collection is empty prior to invoking this function.
ORA-22167 given trim size [string] must be less than or equal to [string]
Cause: Given trim size is greater than the current collection size.
Action: Ensure that the given size is less than or equal to the collection size prior to calling this function.
ORA-22275 invalid LOB locator specified
Cause: One of the following:
Action: For (1), initialize the LOB locator by selecting into the locator variable or by setting the LOB locator to empty. For (2) and (3), pass the correct type of locator into the routine. For (4), remove the trigger body code that updates the LOB value.
ORA-22276 invalid locator for LOB buffering
Cause: One of the following:
Action: For (1) enable the locator for buffering; (2) ensure that only an updated locator is used for a LOB update operation.
ORA-22277 cannot use two different locators to modify the same LOB
Cause: LOB buffering is enabled and an attempt was made to modify the LOB using two different LOB locators.
Action: When using LOB buffering, modify the LOB through one LOB locator only.
ORA-22278 must update the LOB only through the LOB buffers
Cause: LOB buffering is enabled for this LOB and there are buffers for this LOB in the buffer pool. Thus, updating the LOB through means other than the LOB buffers is not allowed.
Action: Update the LOB through the LOB buffers using the locator that has LOB buffering enabled. If this operation is required, buffers associated with this LOB should either be flushed as necessary or buffering should be disabled. Once this is done, reissue the command.
ORA-22279 cannot perform operation with LOB buffering enabled
Cause: The operation attempted is not allowed when LOB buffering is enabled.
Action: If the operation is required, LOB buffering should not be used. In this case, flush buffers associated with the input LOB locator as necessary, disable buffering on the input LOB locator and reissue the command.
ORA-22280 no more buffers available for operation
Cause: One of the following:
Action: For (1), flush the LOB(s) through the locator that is being used to update the LOB. For (2), write to the LOB through a locator enabled for buffering before attempting to flush buffers.
ORA-22281 cannot perform operation with an updated locator
Cause: The input locator has buffering enabled and was used to update the LOB value through the LOB buffering subsystem. The modified buffer has not been flushed since the write that was performed by the input locator; thus, the input locator is considered an updated locator. Updated locators cannot be the source of a copy operation. Only one locator per LOB may be used to modify the LOB value through the LOB buffering subsystem.
Action: Depending on whether the modifications made through the input locator to the LOB buffering subsystem should be written to the server, either flush the buffer to write the modifications, or, disable buffering on the locator to discard the modifications. Then, reissue the command.
ORA-22282 non-contiguous append to a buffering enabled LOB not allowed
Cause: The buffered write operation has an input offset value more than one byte or character past the end of the LOB.
Action: Specify an input offset value which is exactly one character or byte greater than the length of the LOB that you are attempting to update through a buffered write operation.
ORA-22285 non-existent directory or file for string operation
Cause: An attempt was made to access a directory that does not exist, or attempted to access a file in a directory that does not exist.
Action: Ensure that a system object corresponding to the specified directory exists in the database dictionary, or make sure the name is correct.
ORA-22286 insufficient privileges on file or directory to perform string operation
Cause: The user does not have the necessary access privileges on the directory alias and/or the file for the operation.
Action: Ask the database/system administrator to grant the required privileges on the directory alias and/or the file.
ORA-22287 invalid or modified directory occurred during string operation
Cause: The directory alias used for the current operation is not valid if being accessed for the first time, or has been modified by the database administrator since the last access.
Action: If you are accessing this directory for the first time, provide a valid directory name. If you have been already successful in opening a file under this directory before this error occurred, then close the file and retry the operation with a valid directory alias as modified by your database administrator. Oracle recommends that directories should be modified only during quiescent periods.
ORA-22288 file or LOB operation string failedstring
Cause: The operation attempted on the file or LOB failed.
Action: See the next error message in the error stack for more detailed information. Also, verify that the file or LOB exists and that the necessary privileges are set for the specified operation. If the error still persists, report the error to the database administrator.
ORA-22289 cannot perform string operation on an unopened file or LOB
Cause: The file or LOB is not open for the required operation to be performed.
Action: Precede the current operation with a successful open operation on the file or LOB.
ORA-22290 operation would exceed the maximum number of opened files or LOBs
Cause: The number of open files or LOBs has reached the maximum limit.
Action: Close some of the opened files or LOBs and retry the operation.
ORA-22291 Open LOBs exist at transaction commit time
Cause: An attempt was made to commit a transaction with open LOBs at transaction commit time.
Action: Close the LOBs before committing the transaction.
ORA-22292 Cannot open a LOB in read-write mode without a transaction
Cause: An attempt was made to open a LOB in read-write mode before a transaction was started.
Action: Start a transaction before opening the LOB in read-write mode. Ways to start a transaction include issuing a SQL DML or SELECT FOR UPDATE command. Opening the LOB in read-only mode does not require a transaction.
ORA-22293 LOB already opened in the same transaction<