ORA-19400 System type conflict with object SYS.string
-
Cause: The user had an object with the same name as one of the system types. The system types were not initialized properly.
-
Action: Remove the conflicting object and re-run migration.
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 Error received from media manager layer, error text: 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 shared server. This is not allowed because the device that is used for backup and restore must remain allocated to a single process.
-
Action: Connect directly to the instance then re-execute the backup or restore function.
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 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.
-
Action: Deallocate the current device and allocate a DISK channel, then retry the command.
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-19579 archivelog record for string not found
-
Cause: No archived log record corresponding to the input file could be found in the control file.
-
Action: Specify a valid archive log file name and retry the operation.
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-19582 archivelog file header validation for string failed
-
Cause: The archived log file header is corrupt and could not be validated.
-
Action: Provide a valid archive log file and 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 string already included in backup conversation
-
Cause: The indicated archive log has already been specified for inclusion in this backup conversation.
-
Action: No action required. The conversation is still active, and more files can be specified.
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.
-
Action: No action required. The conversation is still active, and more files can be specified.
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 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 start up the instance.
-
Action: Create an SPFILE and restart the instance using the SPFILE.
ORA-19599 block number string is corrupt in string string
-
Cause: A corrupt block was found in a controlfile, archivelog, or backup piece that is being read for a backup or copy. Corruption is not tolerated in controlfiles, archivelogs, 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.
- 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 V$DATAFILE_COPY view.
- For a datafile-copy, the file number refers to the copy's control file record number as shown in the RECID column of the V$DATAFILE_COPY view.
- For an archived log, the file number refers to the log's control file record number as shown in the RECID column of the V$ARCHIVED_LOG view.
-
Action: 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-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 the 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 the KEEP .. UNRECOVERABLE option.
-
Action: Take the tablespace offline cleanly, 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 Support Services.
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 Support Services.
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-19677 RMAN configuration name exceeds maximum length of string
-
Cause: The configuration name string exceeds the maximum length.
-
Action: Supply a correct configuration name and retry the function.
ORA-19678 RMAN configuration value exceeds maximum length of string
-
Cause: The configuration value string exceeds the maximum length.
-
Action: Supply a correct configuration value and retry the operation.
ORA-19679 RMAN configuration number string is outside valid range of 1 through string
-
Cause: An invalid RMAN Configuration number was specified.
-
Action: Specify a correct datafile number and retry the operation.
ORA-19680 some blocks not recovered. See trace file for details
-
Cause: Some blocks were not recovered during block media recovery.
-
Action: See trace files for details of the problem.
ORA-19681 block media recovery on control file not possible
-
Cause: File number 0 was specified in block media recovery.
-
Action: Check file number.
ORA-19683 real and backup blocksize of file string are unequal
-
Cause: The block size changed between the backup & the real file.
-
Action: Use the correct backup.
ORA-19684 block media recovery failed because database is suspended
-
Cause: Database is suspended, probably by an ALTER SYSTEM SUSPEND statement.
-
Action: Execute ALTER SYSTEM RESUME then retry block media recovery.
ORA-19690 backup piece release string incompatible with Oracle release string
-
Cause: The backup piece was created by incompatible software.
-
Action: Either restart with a compatible software release or create another backup using the current release.
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-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.
-
Action: Specify a valid character set in the environment. This is usually done via the NLS_LANG environment variable.
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.
-
Action: Close the database before using the reNormalizeAllFileNames procedure.
ORA-19712 table name exceeds maximum length of string
-
Cause: The table name string exceeds the maximum length.
-
Action: Retry the operation with a shorter table name.
ORA-19713 invalid copy number: string
-
Cause: The copy number is not in a valid range or you have reached the maximum limit.
-
Action: Report the error and other information to support.
ORA-19714 length for generated piece name longer than string
-
Cause: The specified format exceeds the maximum length for the piece name.
-
Action: Change the format to create shorter piece names.
ORA-19715 invalid format for piece name
-
Cause: A restricted format was used incorrectly.
-
Action: Change the format by removing the restricted format.
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-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.
-
Action: Use import/export or unload/load to move data instead.
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 Support Services 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 Support Services. 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 Support Services.
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-21561 OID generation failed
-
Cause: The handles passed in may not be valid.
-
Action: Check the validity of the env, svc handles.
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 was passed in.
-
Action: Use a valid number. To initialize a number, call OCINumberSetZero().
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: There are several causes:
- The LOB locator was never initialized
- The locator is for a BFILE and the routine expects a BLOB/CLOB/NCLOB locator
- The locator is for a BLOB/CLOB/NCLOB and the routine expects a BFILE locator
- Trying to update the LOB in a trigger body -- LOBs in trigger bodies are read-only
- The locator is for a BFILE/BLOB and the routine expects a CLOB/NCLOB locator
- The locator is for a CLOB/NCLOB and the routine expects a BFILE/BLOB locator
-
Action: For (1), initialize the LOB locator by selecting into the locator variable or by setting the LOB locator to empty. For (2),(3), (5), and (6),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:
- The locator was never enabled for buffering.
- It is not an updated locator but is being used for a write/flush operation.
-
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:
- All buffers in the buffer pool have been used up by previous operations.
- An attempt was made to flush a LOB without any previous buffered update operations.
-
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-22283 filename contains characters that refer to parent directory
-
Cause: Filename contains a path "../" which references a parent directory.
-
Action: Ensure that the filename does not contain characters which reference a parent directory.
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 failed string
-
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
-
Cause: An attempt was made to open a LOB that already is open in this transaction.
-
Action: Close the LOB before attempting to reopen it.
ORA-22294 cannot update a LOB opened in read-only mode
-
Cause: An attempt was made to write to or update a LOB opened in read-only mode.
-
Action: Close the LOB and reopen it in read-write mode before attempting to write to or update the LOB.
ORA-22295 cannot bind more than 4000 bytes data to LOB and LONG columns in 1 statement
-
Cause: An attempt was made to bind more than 4000 bytes of data to both LOB and LONG columns in the same insert or update statement. You can bind more than 4000 bytes of data to either a LONG column or one or more LOB columns, but not both.
-
Action: Bind more than 4000 bytes of data to either the LONG column or one or more LOB columns, but not both.
ORA-22296 invalid ALTER TABLE option for conversion of LONG datatype to LOB
-
Cause: An attempt was made to specify ALTER TABLE options which are disallowed during conversion of LONG datatype to LOB. The only ALTER TABLE options allowed during conversion of LONG datatype to LOB are the default clause and LOB storage clause for the column being converted to LOB.
-
Action: Remove the disallowed options.
ORA-22297 warning: Open LOBs exist at transaction commit time
-
Cause: An attempt was made to commit a transaction with open LOBs at transaction commit time.
-
Action: This is just a warning. The transaction was commited successfully, but any domain or functional indexes on the open LOBs were not updated. You may want to rebuild those indexes.
ORA-22303 type "string"."string" not found
-
Cause: An attempt was made to obtain information for a type that cannot be found.
-
Action: Check that the schema is correct and that the type has been created correctly.
ORA-22304 input type is not an object type
-
Cause: An attempt was made to obtain the supertype information for a non-object type.
-
Action: Pass in only an object type.
ORA-22305 attribute/method/parameter "string" not found
-
Cause: Type element with the given name is not found in the type.
-
Action: Check to make sure that the type element exists.
ORA-22306 type "string"."string" already exists
-
Cause: An attempt was made to create a type that already exists.
-
Action: Check to make sure that the type has not been created prior to this.
ORA-22307 operation must be on a user-defined type
-
Cause: An attempt was made to perform an operation that is allowed only on a user-defined type, and the type is not a user-defined type.
-
Action: Check to make sure that only user-defined types are being operated on.
ORA-22308 operation not allowed on evolved type
-
Cause: An attempt was made to replace a type whose attribute definition has been altered.
-
Action: Submit ALTER TYPE ADD/DROP statement instead of ALTER TYPE REPLACE.
ORA-22309 attribute with name "string" already exists
-
Cause: An attempt was made to create an object type where more than one attributes have the same name.
-
Action: Check to make sure that all attribute names are unique.
ORA-22310 ALTER TYPE error. Refer to table "string"."string" for errors
-
Cause: An invalid alter type statement was submitted.
-
Action: Correct the errors listed in the specified table and resubmit the statement.
ORA-22311 type for attribute "string" does not exist
-
Cause: The type of the attribute does not exist.
-
Action: No types were created/modified for this DDL transaction. Redo the DDL transaction and add the creation of the attribute's type in the DDL transaction.
ORA-22312 must specify either CASCADE or INVALIDATE option
-
Cause: An attempt was made to alter a type which has a dependent type or table without specifying the CASCADE or INVALIDATE option.
-
Action: Resubmit the statement with either the CASCADE or INVALIDATE option. Specify CASCADE if you want to cascade the type change to dependent types and tables; otherwise, specify INVALIDATE to invalidate all dependents.
ORA-22313 cannot use two versions of the same type "string"
-
Cause: The version of this type conflicts with the version of this type used by another library that was linked in with the application. An application may only use one version of a type.
-
Action: Check that the libraries being linked with this application and use the same versions of the type.
ORA-22314 method information mismatch in ALTER TYPE
-
Cause: The number of methods or the method signature do not match that of the original type declaration. This is not supported.
-
Action: Make sure the method signature stay identical for the previously declared method. Do not drop existing methods.
ORA-22315 type "string" does not contain a map or order function
-
Cause: The input type does not contain a map or order function so one cannot be returned.
-
Action: Add a map or order function to the type or catch this error.
ORA-22316 input type is not a collection type
-
Cause: An attempt was made to obtain information for collection types on a non-named collection type.
-
Action: Use a named collection type for the function.
ORA-22317 typecode number is not legal as a number type
-
Cause: An attempt was made to use a number type code that is not valid.
-
Action: Use only OCI_TYPECODE_SMALLINT, OCI_TYPECODE_INTEGER, OCI_TYPECODE_REAL, OCI_TYPECODE_DOUBLE, OCI_TYPECODE_FLOAT, OCI_TYPECODE_NUMBER, or OCI_TYPECODE_DECIMAL.
ORA-22318 input type is not an array type
-
Cause: An attempt was made to obtain the number of elements for a non-array type.
-
Action: Pass in only a named collection type which is an array.
ORA-22319 type attribute information altered in ALTER TYPE
-
Cause: The type attribute information does not match that of the original type declaration when altering type. Attributes cannot be altered during ALTER TYPE. Only new methods can be added.
-
Action: Check that all type alterations are legal.
ORA-22320 missing user version string
-
Cause: The VERSION option is specified without a user version string.
-
Action: Resubmit the statement with the version string following the VERSION keyword.
ORA-22321 method does not return any result
-
Cause: OCITypeResult() was called on a method that does not return any results.
-
Action: Check that you are passing in the correct method descriptor, or that your method creation was done correctly.
ORA-22322 error table "string"."string" has incorrect structure
-
Cause: The specified error table does not have the expected table structure.
-
Action: Execute the DBMS_UTILITY.CREATE_ALTER_TYPE_ERROR_TABLE procedure to create an error table, then resubmit the statement using the new error table.
ORA-22323 error table "string"."string" does not exist
-
Cause: The error table does not exist.
-
Action: Resubmit the statement with a correct error table name.
ORA-22324 altered type has compilation errors
-
Cause: The use of the ALTER TYPE statement caused a compilation error.
-
Action: Correct the error reported and resubmit the statement.
ORA-22326 cannot change a type to FINAL if it has subtypes
-
Cause: An attempt was made to change a type with subtypes to FINAL.
-
Action: Drop all subtypes of the target type before changing it to FINAL.
ORA-22327 cannot change a type to NOT INSTANTIABLE if it has dependent tables
-
Cause: An attempt was made to change a type with dependent tables to NOT INSTANTIABLE.
-
Action: Drop all dependent tables of the target type and resubmit the statement.
ORA-22328 object "string"."string" has errors. string
-
Cause: Altering the target type causes errors in its dependent object.
-
Action: Correct the problem in the dependent object and resubmit the statement.
ORA-22329 cannot alter a non-object type
-
Cause: An attempt was made to execute ALTER TYPE on a non-object type.
-
Action: Drop the non-object type first, then re-create it as an object type.
ORA-22330 cannot alter a type that is not valid
-
Cause: An attempt was made to perform ALTER TYPE on an invalid type.
-
Action: Use the CREATE OR REPLACE TYPE command to modify the type.
ORA-22331 cannot alter an incomplete type
-
Cause: An attempt was made to perform ALTER TYPE on an incomplete type.
-
Action: Use CREATE TYPE to completely define the original type before executing the ALTER TYPE.
ORA-22332 a dependent object in schema "string" has errors. string
-
Cause: Altering the target type causes errors in its dependent object.
-
Action: Correct the problem in the dependent object and resubmit the statement.
ORA-22333 cannot reset type "string"."string" due to invalid dependent types and tables
-
Cause: An attempt was made to reset the type version with invalid dependent types and tables.
-
Action: Use the ALTER TYPE COMPILE statement to compile all invalid dependent types and use the ALTER TABLE UPGRADE INCLUDING DATA statement to upgrade all the dependent tables, then resubmit the statement.
ORA-22334 cannot reset type "string"."string". Dependent tables must be upgraded to latest version.
-
Cause: An attempt was made to reset the type version when the data in the dependent table has not been upgraded to the latest type version.
-
Action: Use the ALTER TABLE UPGRADE INCLUDING DATA statement to upgrade the data in the dependent tables then resubmit the statement.
ORA-22335 The client cannot work with an altered type
-
Cause: A pre 9.0.0 client has requested a type that has been altered on the server.
-
Action: Only 9.0.0 and higher clients can access altered types.
ORA-22336 table contained 8.0 image format, must specify INCLUDING DATA
-
Cause: One of the following:
- An attempt was made to alter a type with a dependent table in 8.0 image format and the NOT INCLUDING TABLE DATA option was specified.
- An attempt was made to upgrade a table in 8.0 image format with the NOT INCLUDING DATA option specified.
-
Action: Resubmit the statement with the INCLUDING DATA option.
ORA-22337 the type of accessed object has been evolved
-
Cause: The type of the accessed object has been altered and the client's object is based on an earlier type definition.
-
Action: The user needs to exit the application and modify the application to accommodate the type change. From SQL/PLUS, reconnect and resubmit the statement.
ORA-22338 must specify CASCADE INCLUDING DATA when altering the final property
-
Cause: An attempt was made to alter the final property of a type with dependent tables without specifying the CASCADE INCLUDING DATA option.
-
Action: Resubmit the statement with the CASCADE INCLUDING DATA option.
ORA-22339 cannot alter to not final since its attribute column is substitutable
-
Cause: An attempt was made to alter a type to not final when its embedded attribute is defined as substitutable in some tables. Note, this is a restriction in 9.0 version because when a type is altered to not final, column of that type is set to not substitutable at all levels; thus, it is an error if one of its embedded attribute column is already marked substitutable.
-
Action: Recreate the table and specify NOT SUBSTITUTABLE AT ALL LEVELS for all columns of non final type. Then resubmit the ALTER TYPE statement.
ORA-22340 cannot string type "string"."string". Dependent tables must be upgraded to latest version
-
Cause: An attempt was made to reset the version, drop or alter a type when the data in dependent table has not been upgraded to the latest version.
-
Action: Use the ALTER TABLE UPGRADE INCLUDING DATA statement to upgrade the data in the dependent tables then resubmit the statement.
ORA-22341 cannot assign supertype instance to subtype
-
Cause: An attempt was made to assign or copy a supertype instance to a container (destination) that can only hold a subtype instance.
-
Action: Make sure the runtime type of the source of the assignment or copy is the same type as the destination or is a subtype of the destination type.
ORA-22342 dependent VARRAY column exceeds the maximum inline column size
-
Cause: An attempt was made to alter a type (add or modify attribute) which causes the size of its dependent VARRAY column to exceed the maximum inline column size. However, the VARRAY column was not specified to be stored as LOB at the table level when the table was created.
-
Action: Specify the VARRAY column to be stored as LOB at the table level when the table is created.
ORA-22343 Compilation error for type invalidated by ALTER TYPE
-
Cause: Compilation failed for a type which was invalidated by ALTER TYPE.
-
Action: Check what is causing the compilation error, correct it, and try again.
ORA-22344 can not specify CONVERT TO SUBSTITUTABLE option for ALTER TYPE other than NOT FINAL change
-
Cause: An attempt was made to specify CONVERT TO SUBSTITUTABLE option for ALTER TYPE other than NOT FINAL change.
-
Action: Specify CONVERT TO SUBSTITUTABLE option only for ALTER TYPE NOT FINAL change.
ORA-22345 recompile type string.string before attempting this operation
-
Cause: An attempt was made to perform an operation which requires the specified datatype to be valid, but the datatype is invalid.
-
Action: Recompile the specified type and retry the operation.
ORA-22369 invalid parameter encountered in method string
-
Cause: An invalid parameter is being passed to this method of SYS.AnyType, SYS.AnyData, or SYS.AnyDataSet.
-
Action: Check the parameters being passed to this method and make sure that the parameters are allowed.
ORA-22370 incorrect usage of method string
-
Cause: This method of SYS.AnyType, SYS.AnyData, or SYS.AnyDataSet is being used inappropriately.
-
Action: Check the documentation for correct usage.
ORA-22371 Table contains data of type string.string, version string, which does not exist
-
Cause: Some of the older versions of the type may have been deleted because one or more of the referenced types was dropped.
-
Action: These data could not be read as the whole ADT. Read the data at individual scalar attribute level.
ORA-22600 encountered 8.0.2 (Beta) VARRAY data that cannot be processed
-
Cause: Production Oracle8 (8.0.3 and beyond) encountered some VARRAY data which was created and stored by Oracle8 8.0.2 (Beta 2). Production Oracle8 cannot understand or process such VARRAY data.
-
Action: Delete the VARRAY data from the table by dropping the table, deleting the rows, or nulling out the VARRAY columns, and then reinsert the VARRAY data. There is no provided script or tool to help automate this conversion.
ORA-22601 pickler TDS context [string] is not initialized
-
Cause: An attempt was made to use the pickler TDS context without initializing it.
-
Action: Use OCIPicklerTdsCtxInit to initialize the context.
ORA-22602 pickler TDS handle [string] is not well-formed
-
Cause: An attempt was made to use the pickler TDS handle without initializing or constructing it.
-
Action: Use OCIPicklerTdsInit to initialize the handle before it is constructed. Use OCIPicklerTdsGenerate to generate the TDS before its attributes can be accessed.
ORA-22603 cannot add an attribute to the already generated TDS handle
-
Cause: An attempt was made to add an attribute to the already constructed TDS.
-
Action: Use a TDS handle that is initialized but not yet constructed.
ORA-22604 TDS handle already generated
-
Cause: An attempt was made to generate TDS that is already generated.
-
Action: Use a TDS handle that is initialized but not yet generated.
ORA-22605 FDO handle [string] is not initialized
-
Cause: An attempt was made to use an uninitialized FDO handle.
-
Action: Use OCIPicklerFdoInit to initialize FDO handle.
ORA-22606 pickler image handle [string] is not well-formed
-
Cause: An attempt was made to use the image handle without initializing/ constructing it.
-
Action: Use OCIPicklerImageInit to initialize the handle before it is constructed. Use OCIPicklerImageGenerate to generate the image before its attributes can be accessed.
ORA-22607 image handle already generated
-
Cause: An attempt was made to generate image that is already generated.
-
Action: Use a image handle that is initialized but not yet generated.
ORA-22608 cannot add an attribute to the already generated image handle
-
Cause: An attempt was made to add an attribute to the already constructed image.
-
Action: Use a image handle that is initialized but not yet constructed.
ORA-22609 error string during initialization of FDO
-
Cause: An error occurred during FDO initialization.
-
Action: Take an action based on the specified error.
ORA-22610 error while adding a scalar to the image handle
-
Cause: An error occurred while adding a scalar attribute to the image handle.
-
Action: Make sure image handle is initialized before adding scalar.
ORA-22611 TDS version is not recognized
-
Cause: Incorrect TDS handle is passed.
-
Action: Make sure image handle is initialized with the correct TDS.
ORA-22612 TDS does not describe a collection TDS
-
Cause: Collection construct/access routines are being on an image but the TDS does not describe that a collection TDS.
-
Action: Make sure a collection TDS is used before invoking collection routines on the image handle.
ORA-22613 buflen does not match the size of the scalar
-
Cause: BUFLEN is incorrect.
-
Action: Make sure BUFLEN is correct and matches the size of the scalar.
ORA-22614 error while construction the collection in the image
-
Cause: An error occurred during the construction of collection.
-
Action: Make sure image handle is initialized and OCIPicklerImageCollBegin is called to begin collection.
ORA-22615 attribute is not a collection
-
Cause: Collection routine is invoked upon a non-collection attribute.
-
Action: Make sure attribute is a collection.
ORA-22616 image is not of Oracle 8.1 format
-
Cause: The function being invoked is applicable only for 8.1 images.
-
Action: Make sure image is of 8.1 format.
ORA-22617 error while accessing the image handle collection
-
Cause: An error occurred while accessing collection in the image handle.
-
Action: Make sure image is initialized correctly and the collection is constructed properly.
ORA-22618 attribute is a BAD NULL in the image handle
-
Cause: The attribute in question is probably the attribute of a null embedded image.
-
Action: Make sure attribute number is valid or it is NULL or NOT NULL.
ORA-22619 all collection elements have already been accessed
-
Cause: An attempt was made to access a collection element after all the collection elements are already accessed.
-
Action: This function should not be invoked any more.
ORA-22620 buffer size too small to hold the value
-
Cause: Buffer size is not enough to hold the value. Most likely while doing the character set conversion, a bigger buffer is needed.
-
Action: Pass in a bigger buffer. If the client character set format differs from that of server, doing the conversion may result in 4X expansion.
ORA-22621 error transfering an object from the agent
-
Cause: An error was returned from the pickler routines on the agent side.
-
Action: Contact Oracle Support Services.
ORA-22625 OCIAnyData is not well-formed
-
Cause: Attempt to use the OCIAnyData without initializing constructing it.
-
Action: Use OCIAnyDataBeginConstruct to initialize the handle before it is adding attributes. Use OCIAnyDataEndConstruct to complete the construction. Or use OCIAnyDataConvert to do the construction. MAke sure it is properly constructed before accessing attributes.
ORA-22626 Type Mismatch while constructing or accessing OCIAnyData
-
Cause: Type supplied is not matching the type of the AnyData. If piece wise construction or access is being attempted, the type supplied is not matching the type of the current attribute.
-
Action: Make sure the type supplied matches the type of object to be constructed or accessed.
ORA-22627 tc [string] must be that of object/varray/nested table
-
Cause: Type code is not that of object/varray/nested table
-
Action: Make sure the type code is OCI_TYPECODE_OBJECT, OCI_TYPECODE_VARRAY, or OCI_TYPECODE_TABLE
ORA-22628 OCIAnyData already constructed
-
Cause: Attempt to add attributes to OCIAnyData that is already constructed.
-
Action: Use the OCIAnyData that is initialized but not yet constructed.
ORA-22629 OCIAnyData is null
-
Cause: Attempting an operation that is not valid on null OCIAnyData.
-
Action: Make sure OCIAnyData is not null.
ORA-22630 attribute [string] is null or it is not well-formed
-
Cause: Passing an attribute that is null or not well-formed.
-
Action: Make sure the attribute is not null or is well-formed.
ORA-22631 attribute [string] is is not well-formed or does not match the type
-
Cause: Passing an attribute that is not well-formed or does not match the input type.
-
Action: Make sure the attribute is well-formed and matches the type specified.
ORA-22632 AnyDataSet parameter is not valid for the current operation
-
Cause: The AnyDataSet parameter is null or invalid for the current operation.
-
Action: Check the documentation for the current operation.
ORA-22633 Error freeing AnyDataSet
-
Cause: AnyDataSet that is passed in may not be valid.
-
Action: Check all the AnyDataSet parameters.
ORA-22634 Error adding new instance to AnyDataSet
-
Cause: Current instance in the AnyDataSet has not been fully constructed.
-
Action: Make sure that the current instance is fully constructed before adding new instance.
ORA-22800 invalid user-defined type
-
Cause: An attempt was made to use an incomplete type as a constructor.
-
Action: Complete the type definition before using it in a query.
ORA-22801 invalid object row variable
-
Cause: The specified object row variable is not available in the scope of name resolution.
-
Action: Verify the specified object row variable is correct, or use an object row variable visible in scope.
ORA-22803 object type contains zero attributes
-
Cause: An attempt was made to create or specify a column or constructor of an object type that has no attributes. Only object types that have at least one attribute are allowed in this context.
-
Action: Specify a valid object type.
ORA-22804 remote operations not permitted on object tables or user-defined type columns
-
Cause: An attempt was made to perform queries or DML operations on remote object tables or on remote table columns whose type is one of object, REF, nested table or VARRAY.
-
Action: Remove the reference to remote tables in the statement.
ORA-22805 cannot insert NULL object into object tables or nested tables
-
Cause: An attempt was made to insert a NULL object into an object table or a Nested Table.
-
Action: Ensure that a non-NULL object is inserted into the table or insert an object with attributes whose values are NULL.
ORA-22806 not an object or REF
-
Cause: An attempt was made to extract an attribute from an item that is neither an object nor a REF.
-
Action: Use an object type or REF type item and retry the operation.
ORA-22807 cannot resolve to a scalar type or a collection type
-
Cause: Invalid use of a non-scalar (for example, object type) item.
-
Action: Change the item's data type and retry the operation.
ORA-22808 REF dereferencing not allowed
-
Cause: An attempt was made to access an object type's attributes by de-referencing a REF item.
-
Action: Make the item an object type instead of a REF to an object type.
ORA-22809 nonexistent attribute
-
Cause: An attempt was made to access a non-existent attribute of an object type.
-
Action: Check the attribute reference to see if it is valid. Then retry the operation.
ORA-22810 cannot modify object attributes with REF dereferencing
-
Cause: An attempt was made to modify the attributes an object by de-referencing a REF column in an UPDATE statement.
-
Action: Update the table containing the object that the REF points to, or change the REF column to an object type column.
ORA-22812 cannot reference nested table column's storage table
-
Cause: An attempt to access the nested table column's storage table is not allowed in the given context.
-
Action: Issue the statement against the parent table containing the nested table column.
ORA-22813 operand value exceeds system limits
-
Cause: Object or Collection value was too large. The size of the value might have exceeded 30k in a SORT context, or the size might be too big for available memory.
-
Action: Choose another value and retry the operation.
ORA-22814 attribute or element value is larger than specified in type
-
Cause: Value provided for the object type attribute or collection element exceeded the size specified in the type declaration.
-
Action: Choose another value and retry the operation.
ORA-22816 unsupported feature with RETURNING clause
-
Cause: RETURNING clause is currently not supported for object type columns, LONG columns, remote tables, INSERT with subquery, and dereferencing inside returning clause.
-
Action: Use separate SELECT statements to get the values.
ORA-22817 subquery not allowed in the default clause
-
Cause: An attempt was made to use a subquery in the column default clause expression.
-
Action: Remove the subquery from the default clause.
ORA-22818 subquery expressions not allowed here
-
Cause: An attempt was made to use a subquery expression where these are not supported.
-
Action: Rewrite the statement without the subquery expression.
ORA-22819 scope of input value does not correspond to the scope of the target
-
Cause: An attempt was made to operate on a REF value scoped to a different table than the expected one.
-
Action: Use a REF which is scoped to the expected table and retry the operation.
ORA-22826 cannot construct an instance of a non instantiable type
-
Cause: An attempt was made to use a non instantiable type as a constructor.
-
Action: None.
ORA-22828 input pattern or replacement parameters exceed 32K size limit
-
Cause: Value provided for the pattern or replacement string in the form of VARCHAR2 or CLOB for LOB SQL functions exceeded the 32K size limit.
-
Action: Use a shorter pattern or process a long pattern string in multiple passes.
ORA-22850 duplicate LOB storage option specificed
-
Cause: A LOB storage option (CHUNK, PCTVERSION, CACHE, NOCACHE, TABLESPACE, STORAGE, INDEX) was specified more than once.
-
Action: Specify all LOB storage options only once.
ORA-22851 invalid CHUNK LOB storage option value
-
Cause: The specified CHUNK LOB storage option value must be an integer.
-
Action: Choose an appropriate integer value and retry the operation.
ORA-22852 invalid PCTVERSION LOB storage option value
-
Cause: The specified PCTVERSION LOB storage option value must be an integer.
-
Action: Choose an appropriate integer value and retry the operation.
ORA-22853 invalid LOB storage option specification
-
Cause: A LOB storage option was not specified.
-
Action: Specify one of CHUNK, PCTVERSION, CACHE, NOCACHE, TABLESPACE, STORAGE, INDEX as part of the LOB storage clause.
ORA-22854 invalid option for LOB storage index
-
Cause: A valid LOB store index option was not specified.
-
Action: Specify one of (INITTRANS, MAXTRANS, TABLESPACE, STORAGE) as part of the LOB storage index.
ORA-22855 optional name for LOB storage segment incorrectly specified
-
Cause: The optional name for LOB storage segment was specified with multiple columns in the column list.
-
Action: Specify each column LOB storage only with optional name(s).
ORA-22856 cannot add columns to object tables
-
Cause: An attempt was made to add columns to an object table. Object tables cannot be altered to add columns since its definition is based on an object type.
-
Action: Create a new type with additional attributes, and use the new type to create an object table. The new object table will have the desired columns.
ORA-22857 cannot modify columns of object tables
-
Cause: An attempt was made to alter the object table by modifying existing columns. An object table cannot be altered to modify existing columns since it is based on an object type. The table definition must be in sync with the corresponding type.
-
Action: Create a new type with the desired attribute types and use it to create an object table. The new object table will have the desired columns.
ORA-22858 invalid alteration of datatype
-
Cause: An attempt was made to modify the column type to object, REF, nested table, VARRAY or LOB type.
-
Action: Create a new column of the desired type and copy the current column data to the new type using the appropriate type constructor.
ORA-22859 invalid modification of columns
-
Cause: An attempt was made to modify an object, REF, VARRAY, nested table, or LOB column type.
-
Action: Create a new column of the desired type and copy the current column data to the new type using the appropriate type constructor.
ORA-22860 object type expected
-
Cause: An attempt was made to create an object table using a non- object type, or to create a column that is a REF to a non-object type.
-
Action: Use a valid object type in the table or column definition.
ORA-22861 invalid user-defined type
-
Cause: An attempt was made to create a column or object table of a non-existent type.
-
Action: Specify a valid type in the table or column definition.
ORA-22862 specified object identifier doesn't match existing object identifier
-
Cause: An attempt was made to specify an object identifier for the type that does not match the existing identifier of the incomplete type of the same name.
-
Action: Specify the correct object identifier or leave it out of the statement.
ORA-22863 synonym for datatype string.string not allowed
-
Cause: A synonym specification for a datatype is not supported.
-
Action: Do not use the synonym for the datatype.
ORA-22864 cannot ALTER or DROP LOB indexes
-
Cause: An attempt was made to ALTER or DROP a LOB index.
-
Action: Do not operate directly on the system-defined LOB index. Perform operations on the corresponding LOB column.
ORA-22865 more than one column specified
-
Cause: An attempt was made to specify multiple columns where only one is allowed.
-
Action: Specify a single column and retry the operation.
ORA-22866 default character set is of varying width
-
Cause: A character LOB was defined but the default character set is not fixed width.
-
Action: Ensure that the character set is of fixed width before defining character LOBs.
ORA-22868 table with LOBs contains segments in different tablespaces
-
Cause: An attempt was made to drop a tablespace which contains the segment(s) for the LOB columns of a table but does not contain the table segment.
-
Action: Find table(s) with LOB columns which have non-table segments in this tablespace. Drop these tables and reissue drop tablespace.
ORA-22869 depth of type dependency hierarchy exceeds maximum limit
-
Cause: The type dependency hierarchy was structured to have depth greater than 1024.
-
Action: Restructure the type dependency hierarchy to a shorter depth.
ORA-22870 ALTER TYPE with REPLACE option a non-object type
-
Cause: An attempt was made to perform ALTER TYPE with REPLACE option a non-object type.
-
Action: Drop the non-object type first, then re-create it as an object type.
ORA-22871 ALTER TYPE with REPLACE is not allowed for pure incomplete types
-
Cause: An attempt was made to perform ALTER TYPE with REPLACE option for a pure incomplete type.
-
Action: Completely define the original type, before using the ALTER TYPE with REPLACE option.
ORA-22872 OID INDEX clause not allowed on tables with primary key based object identifiers
-
Cause: An attempt was made to create an OID INDEX on a table with primary key-based object identifiers.
-
Action: Remove the OID INDEX clause.
ORA-22873 primary key not specified for primary key based object table
-
Cause: An attempt was made to create a primary key based object table without specifying a primary key.
-
Action: Specify a primary key and retry the operation.
ORA-22874 attribute "string" is not part of the type "string"
-
Cause: Attribute specified in the USER_DEFINED clause is not an attribute of the REF type.
-
Action: Ensure that the name specified in the USER_DEFINED clause is the name of a valid attribute of the REF type.
ORA-22875 cannot drop primary key of an object table whose object identifier is primary key based
-
Cause: An attempt was made to drop the primary key of an object table which has a primary key based object identifier.
-
Action: Remove the drop primary key clause.
ORA-22876 this user-defined type is not allowed or it cannot be used in this context
-
Cause: An attempt was made to create a kind of user-defined type which is not allowed, or an attempt to create table columns or use default constructor with a type on which these are not supported.
-
Action: Ensure that the type is permitted in this context.
ORA-22877 invalid option specified for a HASH partition or subpartition of a LOB column
-
Cause: One or more invalid options were encountered while parsing the physical attributes of a LOB partition or subpartition. Either the LOB partition is in a table partitioned using the HASH method, or the LOB subpartition is in a table subpartitioned using the HASH method. TABLESPACE is the only valid option for a HASH partition or subpartition.
-
Action: Remove the invalid option(s).
ORA-22878 duplicate LOB partition or subpartition specified
-
Cause: An attempt was made was made to specify a partition or subpartition that has already been specified for the LOB column.
-
Action: Remove the duplicate specification.
ORA-22879 cannot use the LOB INDEX clause for partitioned tables
-
Cause: An attempt was made to specify a LOB INDEX clause in a CREATE TABLE or ALTER TABLE statement for a partitioned table.
-
Action: Remove the LOB INDEX clause.
ORA-22880 invalid REF
-
Cause: An invalid REF was accessed.
-
Action: Modify the REF and retry the operation.
ORA-22881 dangling REF
-
Cause: The object corresponding to the REF that was accessed does not exist.
-
Action: Ensure that the REF value is pointing to an existing object.
ORA-22882 object creation failed
-
Cause: The object cannot be created in the database.
-
Action: Check to see if the object table exists and the object size is not too big. Then retry the operation.
ORA-22883 object deletion failed
-
Cause: The object could not be deleted from the database.
-
Action: Check to see if the object table exists. Then retry the operation.
ORA-22884 object modification failed
-
Cause: The object could not be modified in the database.
-
Action: Check to see if the object table exists and the object size is not too big. Then retry the operation.
ORA-22885 cannot get REF to a non-persistent object
-
Cause: An attempt was made to get a REF for something other than an object in an object table. REFs can only be taken for objects in object tables.
-
Action: Rewrite the query to obtain REF values from object tables.
ORA-22886 scoped table "string" in schema "string" is not an object table
-
Cause: The scoped table specified for a REF column is not an object table.
-
Action: Ensure that the scoped table is an object table. Then retry the operation.
ORA-22887 type of REF column is not the same as that of its scoped table
-
Cause: The type specified for the REF column and the type specified for the scope table are different.
-
Action: Ensure that the types of a REF column and its scoped table are the same.
ORA-22888 duplicate SCOPE clauses for a REF column
-
Cause: Multiple SCOPE clauses were specified for a single REF column.
-
Action: Remove the duplicate SCOPE clauses and retry the operation.
ORA-22889 REF value does not point to scoped table
-
Cause: An attempt was made to insert a REF value that does not point to the scoped table.
-
Action: Ensure that the REF values point to the scoped table.
ORA-22890 cannot specify name for REF column constraint
-
Cause: An attempt was made to specify a constraint name for a constraint on a REF column.
-
Action: Remove the constraint name and retry the operation.
ORA-22891 cannot have multiple columns in REF constraint
-
Cause: An attempt was made to specify multiple columns in a single REF constraint.
-
Action: Specify separate constraints for each column and retry the operation.
ORA-22892 scoped table "string" does not exist in schema "string"
-
Cause: The scoped table specified for a REF column does not exist.
-
Action: Ensure that the scoped table exists and retry the operation.
ORA-22893 constraint can be specified only for REF columns
-
Cause: The constraint specified does not apply to non-REF columns.
-
Action: Remove the constraint and retry the operation.
ORA-22894 cannot add constraint on existing unscoped REF columns of non-empty tables
-
Cause: An attempt was made to add a constraint to existing unscoped REF columns of a table which contains one or more rows.
-
Action: Remove the constraint specification or add the constraint after emptying the table.
ORA-22895 referenced table "string" in schema "string" is not an object table
-
Cause: The referenced table specified for a REF column is not an object table.
-
Action: Ensure that the referenced table is an object table. Then retry the operation.
ORA-22896 cannot have both scope and referential constraint on REF column "string"
-
Cause: REF column has both a referential and a scope constraint. A referential constraint implies a scope constraint.
-
Action: Remove either the referential or scope constraint and then retry the operation.
ORA-22897 no scope clause specified for user-defined REF column "string"
-
Cause: User-defined REF column does not have a scope constraint.
-
Action: Specify a scope constraint for the user-defined REF column and retry the operation.
ORA-22898 existing scope clause on "string" points to a table other than the one mentioned in the referential constraint
-
Cause: Table mentioned in the referential integrity constraint is different from the scope table of the REF column.
-
Action: Specify the scope table of the REF column in the referential integrity constraint and then retry the operation.
ORA-22899 cannot specify both scope and rowid constraint on ref column
-
Cause: An attempt was made to specify both a scope and a ROWID constraint on a REF column.
-
Action: Remove either the ROWID or scope constraint and then retry the operation.
ORA-22900 the SELECT list item of THE subquery is not a collection type
-
Cause: The THE subquery must SELECT a nested table or VARRAY item.
-
Action: Change the subquery to SELECT a nested table or VARRAY item.
ORA-22901 cannot compare nested table or VARRAY or LOB attributes of an object type
-
Cause: Comparison of nested table or VARRAY or LOB attributes of an object type was attempted in the absence of a MAP or ORDER method.
-
Action: Define a MAP or ORDER method for the object type.
ORA-22902 CURSOR expression not allowed
-
Cause: CURSOR on a subquery is allowed only in the top-level SELECT list of a query.
-
Action: Remove the CURSOR expression and retry the operation.
ORA-22903 MULTISET expression not allowed
-
Cause: MULTISET expressions are allowed only inside a CAST to a nested table or VARRAY type.
-
Action: put the MULTISET (subquery) expression inside a CAST to a nested table or VARRAY type.
ORA-22904 invalid reference to a nested table column
-
Cause: An invalid reference was made to a nested table column.
-
Action: Remove invalid reference to the nested table column and retry the operation.
ORA-22905 cannot access rows from a non-nested table item
-
Cause: An attempt was made to access rows of an item whose type is not known at parse time or that is not of a nested table type.
-
Action: Use CAST to cast the item to a nested table type.
ORA-22906 cannot perform DML on expression or on nested table view column
-
Cause: An attempt was made to perform a DML on an expression or on a nested table view column where a nested table column of a base table is expected.
-
Action: Only nested table column of a base table is allowed in the DML.
ORA-22907 invalid CAST to a type that is not a nested table or VARRAY
-
Cause: An attempt was made to CAST to a type that is not a nested table or VARRAY.
-
Action: Respecify CAST to a nested table or VARRAY type.
ORA-22908 reference to NULL table value
-
Cause: The evaluation of the THE subquery or nested table column resulted in a NULL value implying a NULL table instance. The THE subquery or nested table column must identify a single non-NULL table instance.
-
Action: Ensure that the evaluation of the THE subquery or nested table column results in a single non-null table instance. If happening in the context of an INSERT statement where the THE subquery is the target of an insert, then ensure that an empty nested table instance is created by updating the nested table column of the parent table's row specifying an empty nested table constructor.
ORA-22909 exceeded maximum VARRAY limit
-
Cause: The total number of elements used in VARRAY construction exceeds the specified VARRAY limit.
-
Action: Do not use the more than the specified limit of elements for VARRAY construction.
ORA-22910 cannot specify schema name for nested tables
-
Cause: Table name was qualified with schema name in the nested table column's (or attribute's) storage clause.
-
Action: Respecify the nested table item's storage clause without the schema name qualification. By default, the storage table for the nested table item is created in the same schema as the containing table.
ORA-22911 duplicate storage specification for the nested table item
-
Cause: The storage clause is specified more than once for the NESTED TABLE column.
-
Action: Remove the duplicate storage specification.
ORA-22912 specified column or attribute is not a nested table type
-
Cause: The storage clause is specified for a column or attribute that is not a nested table column or attribute.
-
Action: Specify a valid nested table column or attribute.
ORA-22913 must specify table name for nested table column or attribute
-
Cause: The storage clause is not specified for a nested table column or attribute.
-
Action: Specify the nested table storage clause for the nested table column or attribute.
ORA-22914 DROP of nested tables not supported
-
Cause: An attempt was made to DROP a nested table.
-
Action: Nested tables cannot be explicitly dropped. nested tables can only be dropped by dropping their containing parent table.
ORA-22915 cannot ALTER nested tables to ADD/MODIFY columns
-
Cause: An attempt was made to ADD or MODIFY columns of a nested table. Columns cannot be added or modified for a nested table.
-
Action: Instead, alter the parent table's nested table column to cause any such change.
ORA-22916 cannot do an exact FETCH on a query with Nested cursors
-
Cause: Exact FETCH on a query was specified which is not allowed if the query returns any cursors.
-
Action: Do not use an exact FETCH.
ORA-22917 use VARRAY to define the storage clause for this column or attribute
-
Cause: Not using VARRAY to define storage clause for VARRAY column or attribute.
-
Action: Specify VARRAY before the column storage clause and resubmit the statement.
ORA-22918 specified column or attribute is not a VARRAY type
-
Cause: An attempt was made to define a VARRAY storage clause for a column or attribute which is not VARRAY type.
-
Action: Specify VARRAY storage clause for a VARRAY column or attribute.
ORA-22919 dangling REF error or lock object failed for no wait request
-
Cause: The error could be one of the following: the object corresponding to the REF does not exist or the object was locked by another user and the lock with nowait request failed.
-
Action: Ensure that the REF value is pointing to an existing object or issue a lock request without the nowait option.
ORA-22920 row containing the LOB value is not locked
-
Cause: The row containing the LOB value must be locked before updating the LOB value.
-
Action: Lock the row containing the LOB value before updating the LOB value.
ORA-22921 length of input buffer is smaller than amount requested
-
Cause: The buffer length is not big enough to hold the amount of data requested.
-
Action: Verify that the number of bytes/characters specified in the input amount parameter is not bigger than the number of bytes specified in the input buffer length parameter. Allocate more space for the input buffer if necessary.
ORA-22922 nonexistent LOB value
-
Cause: The LOB value associated with the input locator does not exist. The information in the locator does not refer to an existing LOB.
-
Action: Repopulate the locator by issuing a SELECT statement and retry the operation.
ORA-22923 amount of data specified in streaming LOB write is 0
-
Cause: An attempt was made to write LOB value via the streaming mechanism (that is, unlimited write) but the input amount of data to stream was specified as 0. Thus, the user is trying to write 0 bytes to the LOB value.
-
Action: Write more than 0 bytes to the LOB value.
ORA-22924 snapshot too old
-
Cause: The version of the LOB value needed for the consistent read was already overwritten by another writer.
-
Action: Use a larger version pool.
ORA-22925 operation would exceed maximum size allowed for a LOB value
-
Cause: An attempt was made to write too much data to the LOB value. LOB size is limited to 4 gigabytes.
-
Action: Either start writing at a smaller LOB offset or write less data to the LOB value.
ORA-22926 specified trim length is greater than current LOB value's length
-
Cause: The input length for which to trim the LOB value to is greater than the current length of the LOB value.
-
Action: May not need to trim the LOB value because it's already smaller than the trim length specified. Or, if trimming the LOB value really is required, use a smaller trim length.
ORA-22927 invalid LOB locator specified
-
Cause: One of the following:
- The LOB locator was never initialized.
- The locator is for a BFILE and the routine expects a BLOB/CLOB/NCLOB locator.
- The locator is for a BLOB/CLOB/NCLOB and the routine expects a BFILE locator.
- An attempt was made to update the LOB in a trigger body -- LOBs in trigger bodies are read only.
-
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-22928 invalid privilege on directories
-
Cause: An attempt was made to grant or revoke an invalid privilege on a directory.
-
Action: Only CREATE, DELETE, READ and WRITE privileges can be granted or revoked on directories. Do not grant or revoke other privileges.
ORA-22929 invalid or missing directory name
-
Cause: The required directory name is invalid or missing.
-
Action: Specify a valid name.
ORA-22930 directory does not exist
-
Cause: An attempt was made to access a directory that does not exist.
-
Action: Make sure the name is correct.
ORA-22931 MOVE of nested table to a different tablespace not supported
-
Cause: An attempt was made to move a nested table to a different tablespace.
-
Action: Nested tables always collocate in the same tablespace as the parent. A nested table can be moved to a different tablespace only by moving its containing table to the target tablespace.
ORA-22933 cannot change object with type or table dependents
-
Cause: An attempt was made to replace, drop, or rename an object with type or table dependents.
-
Action: Drop depending objects or use FORCE option if available.
ORA-22950 cannot ORDER objects without MAP or ORDER method
-
Cause: An object type must have a MAP or ORDER method defined for all comparisons other than equality and inequality comparisons.
-
Action: Define a MAP or ORDER method for the object type.
ORA-22951 NULL returned by ORDER method
-
Cause: ORDER method used to compare two object values returned NULL which is not allowed.
-
Action: Redefine the ORDER method to not return a NULL.
ORA-22970 name does not correspond to an object view
-
Cause: Either the expression is not a view name or the name specified does not correspond to an object view.
-
Action: Replace the expression with the name of an object view.
ORA-22971 invalid datatype for PRIMARY KEY-based object identifier
-
Cause: When creating an object view, the datatype of an expression in the WITH OBJECT OID clause is not allowed for PRIMARY KEY-based OID.
-
Action: Replace the expression with one of appropriate scalar datatype.
ORA-22972 NULL value not allowed in PRIMARY KEY-based object identifier
-
Cause: A value constituting the PRIMARY KEY-based object identifier is NULL.
-
Action: Ensure the expressions in MAKE_REF system function or attributes in the WITH OBJECT OID clause of an object view do not evaluate to NULL.
ORA-22973 size of object identifier exceeds maximum size allowed
-
Cause: Size of the PRIMARY KEY-based object identifier of an object view exceeded the maximum size of 1000 bytes.
-
Action: Specify fewer or smaller PRIMARY KEY attributes in the WITH object OID clause when creating the object view.
ORA-22974 missing WITH OBJECT OID clause
-
Cause: WITH OBJECT OID clause was not specified when creating an object view.
-
Action: Specify the WITH OBJECT OID clause.
ORA-22975 cannot create a PRIMARY KEY-based REF to this object view
-
Cause: The object view specified in the MAKE_REF function does not have a PRIMARY KEY-based object identifier. A PRIMARY KEY-based REF cannot be created for such a view.
-
Action: Specify an object view that has a PRIMARY KEY-based object identifier in the MAKE_REF function.
ORA-22976 incorrect number of arguments to MAKE_REF
-
Cause: Number of arguments for MAKE_REF is different from the number of PRIMARY KEY attributes of the object view.
-
Action: Specify all the necessary arguments for MAKE_REF.
ORA-22977 missing or invalid attribute
-
Cause: Either the attribute name is missing in the WITH OBJECT OID clause or it is invalid.
-
Action: Specify a valid attribute of the object type of the object view.
ORA-22978 only simple attribute name is allowed in the WITH OBJECT OID clause
-
Cause: An attempt was made to specify a Nested attribute in the WITH OBJECT OID clause.
-
Action: Specify a top-level attribute of the object type of the object view.
ORA-22979 cannot INSERT object view REF or user-defined REF
-
Cause: An attempt was made to insert an object view REF or user-defined REF in a REF column created to store system generated REF values.
-
Action: Make sure the REF to be inserted is not from an object view or from a user-defined REF column
ORA-22980 must specify a set of attributes for the WITH OBJECT OID clause
-
Cause: The WITH OBJECT OID DEFAULT clause was used, but the underlying view or table does not have a OID.
-
Action: Specify attributes for the WITH OBJECT OID clause to create a primary key based object identifier for the object view.
ORA-22981 must specify a table/view having system generated OID
-
Cause: The super-view is based on a table/view having the system generated OID and the sub-view must also be based on a similar table/view.
-
Action: Specify a table/view having the system generated OID and retry the operation.
ORA-22982 cannot create sub-view under this view
-
Cause: The view derives its OID from a table/view having primary key based OID and sub-views cannot be created under such views.
-
Action: Specify a view having the system generated OID or a view created with the specification of attributes in the WITH OBJECT ID clause and retry the operation.
ORA-22983 not a user-defined REF
-
Cause: Attempt to use a system generated REF value where a user-defined REF value should be used.
-
Action: Make sure the REF value is user-defined.
ORA-22984 view query cannot contain references to a super view
-
Cause: The query defining the view contains references to a super-view of the view being created.
-
Action: Make sure that the view query does not reference a super-view.
ORA-22990 LOB locators cannot span transactions
-
Cause: A LOB locator selected in one transaction cannot be used in a different transaction.
-
Action: Reselect the LOB locator and retry the operation.
ORA-22991 insufficient space allocated for argument string
-
Cause: The data to be returned in the argument is greater than the amount of space allocated for the argument.
-
Action: Allocate more space for the argument.
ORA-22992 cannot use LOB locators selected from remote tables
-
Cause: A remote LOB column cannot be referenced.
-
Action: Remove references to LOBs in remote tables.
ORA-22993 specified input amount is greater than actual source amount
-
Cause:
- For LOB write, the amount of data received is different from the amount that was indicated would be sent.
- For LOB copy and load from file, the end of the source LOB/FILE value was reached before the specified input amount was copied/loaded.
-
Action: (1) will happen when using OCI's piecewise mechanism with polling or with a callback function. Modify the code either to send the amount specified or to pass 0 as the input amount so that any amount of data can be sent. (2) will happen if the specified input amount is too large for the source LOB/FILE given the starting source offset. Either decrease the starting source offset, or decrease the amount to copy/load.
ORA-22994 source offset is beyond the end of the source LOB
-
Cause: The source offset for a LOB COPY or LOB LOADFROMFILE is beyond the end of the source LOB.
-
Action: Check the length of the LOB and then adjust the source offset.
ORA-22995 TABLESPACE DEFAULT option is invalid in this context
-
Cause: TABLESPACE DEFAULT option can be specified for LOB columns only in the following contexts:
- at the table level for a partitioned table
- at the partition level for a composite partition
An attempt was made to use the TABLESPACE DEFAULT option in a different context.
-
Action: Remove the TABLESPACE DEFAULT option.
ORA-22996 NEXT extent size is smaller than LOB chunksize
-
Cause: An attempt was made to create or alter a LOB segment so that its NEXT extent size was less than the LOB chunk size.
-
Action: Specify a NEXT extent size that is greater than or equal to the LOB chunk size.
ORA-22997 VARRAY | OPAQUE stored as LOB is not specified at the table level
-
Cause: An attempt was made to specify a VARRAY|OPAQUE column to be stored as LOB at the partition/subpartition/template level. However, the VARRAY|OPAQUE column was not specified to be stored as LOB at the table level when the table was created.
-
Action: Specify the VARRAY | OPAQUE column to be stored as LOB at the table level when the table is created. Alternatively, do not specify the VARRAY | OPAQUE column to be stored as LOB at the partition/subpartition/template level if it is not specified at the table level when the table is created.
ORA-22998 CLOB or NCLOB in multibyte character set not supported
-
Cause: A CLOB or NCLOB in a fixed-width or varying-width multibyte character set was passed to a SQL character function which does not support multibyte LOB data.
-
Action: Use DBMS_LOB functions such as DBMS_LOB.INSTR() and DBMS_LOB.SUBSTR() or use PLSQL DBMS_LOB.READ/WRITE to access LOB data.
ORA-23290 This operation may not be combined with any other operation
-
Cause: An ALTER TABLE RENAME [COLUMN | CONSTRAINT] operation was given in conjunction with another ALTER TABLE Operation. This is not allowed.
-
Action: Ensure that RENAME COLUMN/RENAME CONSTRAINT is the only operation specified in the ALTER TABLE statement.
ORA-23291 Only base table columns may be renamed
-
Cause: An attempt was made to rename a column of a non-base table, such as an object table, nested table, or materialized view table. This is not allowed.
-
Action: No action required.
ORA-23292 The constraint does not exist
-
Cause: The given constraint name does not exist.
-
Action: Give an existing constraint's name.
ORA-23293 Cannot rename a column which is part of a join index
-
Cause: The column participates in a join index.
-
Action: If you need to rename the column, then you need to drop the join index.
ORA-23300 string
-
Cause: The stored procedure RAISE_SYSTEM_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-23301 mixed use of deferred rpc destination modes
-
Cause: Replication catalog determined deferred RPC destinations were mixed with destination determined by other mechanisms in the same transaction.
-
Action: Do not mix destination types in the same transaction.
ORA-23302 application raised communication failure during deferred RPC
-
Cause: An application declared a communication failure during a deferred RPC.
-
Action: Retry the application when communication is restored.
ORA-23303 application raised generic exception during deferred RPC
-
Cause: An application declared a generic failure during a deferred RPC.
-
Action: Determined by the application.
ORA-23304 malformed deferred rpc at arg string of string in call string, in tid string
-
Cause: A deferred RPC call was issued without the correct number of arguments as determined by the count parameter to DBMS_DEFER.CALL.
-
Action: Be sure the number of arguments matches the count.
ORA-23305 internal deferred RPC error: string
-
Cause: An internal error occurred in deferred RPC.
-
Action: Report the error and other information to support.
ORA-23306 schema string does not exist
-
Cause: The schema name was null or misspelled, or the schema does not exist locally.
-
Action: Specify the schema correctly, or create it with CREATE USER.
ORA-23307 replicated schema string already exists
-
Cause: The given database already replicates the given schema.
-
Action: Choose a different schema or a different database.
ORA-23308 object string.string does not exist or is invalid
-
Cause: The given name was null or misspelled, the given type was wrong, the object does not exist as a valid database object, or the object does not exist as a replicated object with the appropriate status.
-
Action: Ensure the object is valid in the database, is visible to the user, and, if appropriate, is a valid object in ALL_REPOBJECT.
ORA-23309 object string.string of type string exists
-
Cause: An object in the same name space exists, perhaps with a different type or shape, or the same object has already been registered as an REPOBJECT in another object group.
-
Action: Remove the offending object with the SQL DROP command, unregister the offending object with DBMS_REPCAT.DROP_MASTER_REPOBJECT(), or reinvoke the request using TRUE for a boolean parameter such as retry or USE_EXISTING_OBJECT.
ORA-23310 object group "string"."string" is not quiesced
-
Cause: The requested operation requires the object group to be suspended.
-
Action: Invoke SUSPEND_MASTER_ACTIVITY at the REPGROUP's MASTERDEF, wait until the status has changed to quiesced, and then retry the original request.
ORA-23312 not the masterdef according to string
-
Cause: The group name is null, the group name is misspelled, the invocation or given database is not the MASTERDEF, or one of the masters does not believe the invocation database is the MASTERDEF.
-
Action: If the given group name and MASTERDEF were both correct, connect to the MASTERDEF and retry the request, or relocate the MASTERDEF at the (errant) databases using RELOCATE_MASTERDEF.
ORA-23313 object group "string"."string" is not mastered at string
-
Cause: The group name is null, the group name is misspelled, the invocation database is not a master, or the invocation database does not believe the given database is a master.
-
Action: If the given group name was correct, connect to a current master and retry the request, make the invocation database a master with ADD_MASTER_DATABASE, or use SWITCH_MVIEW_MASTER if the invocation database is a materialized view site.
ORA-23314 database is not a materialized view site for "string"."string"
-
Cause: The invocation database is not a snapshot database for the given object group.
-
Action: Connect to the desired materialized view database and retry the request, or make the invocation database a materialized view site with CREATE_MVIEW_REPSCHEMA or CREATE_MVIEW_REPGROUP.
ORA-23315 repcatlog version or request string is not supported by version string
-
Cause: Either incompatible REPCAT versions are used, or a REPCATLOG record has been corrupted.
-
Action: Convert the master to a compatible version of REPCAT or retry the request.
ORA-23316 the masterdef is string
-
Cause: The requested operation is not permitted on a MASTERDEF site.
-
Action: Relocate the MASTERDEF to another master and retry the operation.
ORA-23317 a communication failure has occurred
-
Cause: The remote database is inaccessible.
-
Action: Ensure the remote database is running, the communications network is functioning, and the appropriate database links are present.
ORA-23318 a ddl failure has occurred
-
Cause: User-supplied or system-generated DDL did not execute successfully.
-
Action: Examine DDL, database state, REPCATLOG, and ALL_ERRORS to determine why the failure occurred.
ORA-23319 parameter value string is not appropriate
-
Cause: The given value of a parameter is either null, misspelled, or not supported.
-
Action: Refer to the documentation and use parameter values that are appropriate for the given situation.
ORA-23320 the request failed because of values string and string
-
Cause: A missing DDL record for a REPCATLOG record, or inconsistency in REPCAT views.
-
Action: Retry the request, or make the views consistent.
ORA-23321 Pipename may not be null
-
Cause: You called DBMS_PIPE with a null pipe name.
-
Action: Find out the name of the pipe and call function with non-null pipe name.
ORA-23322 Privilege error accessing pipe
-
Cause: You either tried to create a pipe that already existed and belonged to someone else, or remove a pipe that you were not authorized to use, or put a message into a pipe that you were not authorized for, or get a message from a pipe that you were not authorized for.
-
Action: You may have to use a different pipe name.
ORA-23323 parameter length exceeds deferred RPC limits
-
Cause: A deferred RPC parameter was longer than the deferred RPC limits of 4000 bytes for char/varchar2 parameters and 2000 bytes for raw parameters.
-
Action: Use smaller parameters.
ORA-23324 error string, while creating deferror entry at "string" with error string
-
Cause: The given error was encountered while attempting to create a DEFERROR entry for the give error code and the give database.
-
Action: Correct the cause of the given error.
ORA-23325 parameter type is not string
-
Cause: A conflict resolution priority function was given a type different than the type assigned to the priority group; or the priority group has no type assigned or a function; or DBMS_DEFER_SYS_QUERY was called to retrieve a deferred RPC parameter from the deferred RPC queue, but the type of the parameter does not match the return type of the function.
-
Action: Use the function corresponding to the parameter type.
ORA-23326 object group "string"."string" is quiesced
-
Cause: Either SUSPEND_MASTER_ACTIVITY has been called before the object group has resumed normal operation or a (deferred) RPC operation was attempted while the object group was quiesced.
-
Action: If SUSPEND_MASTER_ACTIVITY has been called and a RESUME_MASTER_ACTIVITY request is pending, wait until it completes, and then reinvoke SUSPEND_MASTER_ACTIVITY. Otherwise, resume database activity with the RESUME_MASTER_ACTIVITY call.
ORA-23327 imported deferred rpc data does not match string of importing db
-
Cause: Deferred RPC queues were imported from a database with a different global name or operating system than importing database.
-
Action: Deferred RPC data should only be imported into a database with the same global name and hardware and operating system.
ORA-23328 mview base table "string"."string" differs from master table "string"."string"
-
Cause: When creating a materialized view through REPCAT, the materialized view base table name did not match a replicated table name at the master.
-
Action: Change the materialized view DDL to use the same base table as the replicated table name at the master.
ORA-23329 successful user-provided ddl but no materialized view "string"."string"
-
Cause: The DDL provided by the user to create a materialized view was executed without error, but materialized view does not exist.
-
Action: Manually back-out the DDL, and reregister with matching DDL and materialized view.
ORA-23330 column group string already exists
-
Cause: The column group was already registered in the object group.
-
Action: Use a column group name not yet registered in the replicated object group.
ORA-23331 column group string does not exist
-
Cause: The given column group is either null, misspelled or not registered.
-
Action: Use a registered column group.
ORA-23332 group string is in use; cannot drop
-
Cause: The given column group or priority group is being used to resolve conflicts.
-
Action: Call DBMS_REPCAT procedures DROP_UPDATE_RESOLUTION, DROP_DELETE_RESOLUTION, DROP_UNIQUE_RESOLUTION so that the column group or priority group is no longer in use before dropping.
ORA-23333 column string is already part of a column group
-
Cause: An attempt was made to add a column to a column group when the column was already a member of a column group.
-
Action: Drop the column from its existing column group before trying to add it to another.
ORA-23334 column string does not exist in table or column group
-
Cause: The given column is either null, misspelled or is not part of the given table or column group.
-
Action: Use a column that is a member of the table or column group.
ORA-23335 priority group string already exists
-
Cause: The priority group was already registered in the object group.
-
Action: Use a column group name not yet registered in the object group.
ORA-23336 priority group string does not exist
-
Cause: The priority group was already registered in the object group.
-
Action: Use a priority group name not yet registered in the object group.
ORA-23337 priority or value not in priority group string
-
Cause: The specified value or priority has not been registered as part of the priority group.
-
Action: Either specify a different value or priority that is already part of the priority group, or add the value to the priority group.
ORA-23338 priority or value already in priority group string
-
Cause: The specified value or priority has already been registered as part of the priority group.
-
Action: Either specify a different value or priority that not already part of the priority group, or drop the value to the priority group.
ORA-23339 duplicate conflict resolution information
-
Cause: The specified combination of column group, sequence, conflict type and/or parameter table name, parameter column name, and parameter sequence number has already been registered.
-
Action: Verify that additional conflict resolution information needs to be added and provide a new sequence number. If modifying existing information, the existing information must be dropped first.
ORA-23340 incorrect resolution method string
-
Cause: User function is specified when conflict resolution method was not "USER FUNCTION" or specified resolution method is not one of the predefined methods.
-
Action: If user function is specified when conflict resolution method was not "USER FUNCTION", either reregister function with method as "USER FUNCTION" or specify a NULL user function. Otherwise, specify one of the documented supported conflict resolution methods.
ORA-23341 user function required
-
Cause: A NULL user function was specified for the "USER FUNCTION" method.
-
Action: Provide user function name (for example, "schema"."package"."function") that conforms to the documented user function specifications or specify one of the documented supported conflict resolution methods.
ORA-23342 invalid parameter column string
-
Cause: The parameter column name is null or misspelled, the invocation database is not a master, or is of the wrong type for the specified conflict resolution method.
-
Action: Specify a parameter column from the specified column group that has a correct type for the conflict resolution method.
ORA-23343 no match for specified conflict resolution information
-
Cause: The specified combination of column group, sequence, conflict type has not been registered (for example, for adding a comment).
-
Action: Specify a combination of column group, sequence, conflict type has been registered.
ORA-23344 constraint (string.string) does not exist
-
Cause: A null, misspelled or non-existent constraint was specified when registering a uniqueness conflict.
-
Action: Register a named constraint for the specified table.
ORA-23345 table "string"."string" not registered to collect statistics
-
Cause: A procedure that deals with conflict resolution statistics-gathering was called for a table that was not registered to collect statistics.
-
Action: Call DBMS_REPCAT.REGISTER_STATISTICS to register the table.
ORA-23346 primary key or object ID is undefined for table or materialized view string
-
Cause: An attempt was made to generate replication support for a table or materialized view without a primary key (as defined by a constraint or DBMS_REPCAT.SET_COLUMNS) or an object ID.
-
Action: For a table, add a primary key constraint or define a primary key using DBMS_REPCAT.SET_COLUMNS or use object tables. For a ROWID materialized view, set min_communication to false or use primary key or object ID materialized views.
ORA-23347 datatype string for column string table string not supported
-
Cause: The table has a column whose datatype is not supported by REPCAT.
-
Action: Remove the column from the table, or alter the column to have one of the supported datatypes.
ORA-23348 cannot replicate procedure string; only IN parameters supported
-
Cause: An attempt was made to generate replication support for a package that has a procedure with OUT or IN OUT parameters.
-
Action: Remove the procedure from the package, or remove the OUT or IN OUT parameters from the procedure.
ORA-23349 cannot generate replication support for functions
-
Cause: An attempt was made to generate replication support for a package that has a public function, or for a standalone function.
-
Action: Remove the public function from the package, or alter the function to be a procedure.
ORA-23350 maximum number of recursive calls exceeded
-
Cause: This usually occurs when trying to resolve conflicts in a table while concurrent updates to the same row create more conflicts.
-
Action: Re-execute the deferred transaction from DefError using DBMS_DEFER_SYS.EXECUTE_ERROR.
ORA-23351 parameter datatype string for procedure string not supported
-
Cause: The procedure has a parameter whose datatype is not supported by REPCAT.
-
Action: Remove the parameter from the procedure, or alter the parameter to have one of the supported datatypes.
ORA-23352 duplicate destination for deferred transaction
-
Cause: A duplicate destination was specified for a deferred transaction either in a DBMS_DEFER.CALL call or an earlier DBMS_DEFER.TRANSACTION call or a dbms_defer_sys.add_default_dest call.
-
Action: Remove the duplicate entry.
ORA-23353 deferred RPC queue has entries for object group "string"."string"
-
Cause: The requested action cannot be performed until the queue is empty for the given object group.
-
Action: Use DBMS_DEFER_SYS.EXECUTE or DBMS_DEFER_SYS.DELETE_TRAN to empty the queue.
ORA-23354 deferred RPC execution disabled for "string" with "string"
-
Cause: Deferred RPC cannot be executed at the destination with the specified catchup value because their propagation has been disabled.
-
Action: Enable deferred RPC execution with the DBMS_DEFER_SYS.SET_DISABLED call.
ORA-23355 object string.string does not exist or is invalid at master site
-
Cause: The given name was null or misspelled, the given type was wrong, the object does not exist as a valid database object at the master site, or the object does not exist as a replicated object with the appropriate status.
-
Action: Ensure the object is valid in the master database, and is visible to the user, and, if appropriate, is a valid object in ALL_REPOBJECT.
ORA-23356 masterdef recognizes a master which does not recognize the masterdef
-
Cause: Possibly DROP_MASTER_REPGROUP was run at a master site but REMOVE_MASTER_DATABASES was not run at master definition site for that master.
-
Action: Run REMOVE_MASTER_DATABASES from master definition site to remove the appropriate master (see associated error messages).
ORA-23357 the propagator does not exist
-
Cause: The propagator does not exist.
-
Action: Register a new propagator.
ORA-23358 invalid remote user
-
Cause: The local user does not match the remote user connected via a database link.
-
Action: Drop and re-create the identified database link with the connect-to user identical to the owner of the database link.
ORA-23359 error on creating a ddl record for a repcatlog record
-
Cause: The USERID in the REPCATLOG record does not match the USERID of the connected user.
-
Action: Retry the operation with a different user.
ORA-23360 only one materialized view for master table "string" can be created
-
Cause: An attempt was made to create more than one materialized view on a given master table in the same rep group.
-
Action: Create these other materialized views in a different rep group at another site.
ORA-23361 materialized view "string" does not exist at master site
-
Cause: The materialized view does not exist at the master site for offline instantiation of the materialized view.
-
Action: The correct procedure is to create the materialized view in a different schema at the master site, and then follow the instructions for offline instantiation of materialized views.
ORA-23362 invalid user
-
Cause: The given user does not exist.
-
Action: Enter the name of a valid user and retry the operation.
ORA-23363 mismatch of mview base table "string" at master and mview site
-
Cause: The name of the base table of the materialized view at the master site is different from the base table at the materialized view site. This error may arise during offline instantiation of materialized views.
-
Action: Retry offline instantiation with a materialized view name less than 24 bytes.
ORA-23364 Feature not enabled: Advanced replication
-
Cause: The Advanced Replication feature is not enabled at this site. Updatable materialized views, deferred RPCs, and other replication features are, therefore, unavailable.
-
Action: Do not attempt to use this feature. Contact Oracle Support Services if the Advanced Replication feature has been purchased but not enabled.
ORA-23365 site string does not exist
-
Cause: site specified in argument REFERENCE_SITE or argument COMPARISON_SITE in call to DIFFERENCES() routine or RECTIFY() routine does not name an existing site.
-
Action: Make sure that database sites specified really do exist, and rerun the routine.
ORA-23366 integer value string is less than 1
-
Cause: Value of argument MAX_MISSING to routine DIFFERENCES() cannot be less than 1. Value of argument COMMIT_ROWS to routines DIFFERENCES() and RECTIFY() cannot be less than 1.
-
Action: Choose an integer value for those arguments to be 1 or greater.
ORA-23367 table string is missing the primary key
-
Cause: Table specified in argument "oname1" or "oname2" in call to "differences()" routine does not contain either a primary key or a virtual primary key (defined through DBMS_REPCAT package under symmetric replication).
-
Action: Make sure the tables specified have a primary key defined.
ORA-23368 name string cannot be null or the empty string
-
Cause: Argument SNAME1, SNAME2, ONAME1, ONAME2, MISSING_ROWS_SNAME, MISSING_ROWS_ONAME1, MISSING_ROWS_ONAME2 to DIFFERENCES() or RECTIFY() cannot be NULL or '' (empty string).
-
Action: Change argument to non-null or non-empty string.
ORA-23369 value of "string" argument cannot be null
-
Cause: Argument MAX_MISSING to DIFFERENCES() routine cannot be NULL.
-
Action: Legal values for MAX_MISSING are integers 1 or greater.
ORA-23370 table string and table string are not shape equivalent (string)
-
Cause: The tables specified are not shape equivalent, which means intuitively that the number of columns, the names, their datatypes and lengths are not the same. Specifically, problem is in the parentheses and is one of the following: the number of columns are not equal, datatypes of columns with same name in different tables are different, lengths of varchar2 and char columns are not equal, precision and scale of number datatypes are not equal.
-
Action: Make sure the two tables being compared have the same number of columns, same column names, and same datatypes.
ORA-23371 column string unknown in table string
-
Cause: Some column in ARRAY_COLUMNS argument (or COLUMN_LIST argument) to DIFFERENCES() routine does not correspond to a column in the specified table.
-
Action: Make sure that all the columns in either ARRAY_COLUMNS or COLUMN_LIST are present in the specified table.
ORA-23372 type string in table string is unsupported
-
Cause: Certain types in the table comparison utility are not supported.
-
Action: Make sure that the types of columns in the tables to be compared are the ones supported by symmetric replication.
ORA-23373 object group "string"."string" does not exist
-
Cause: The group name was null or misspelled, or the group does not exist locally.
-
Action: Specify the group correctly, or create it with DBMS_REPCAT.CREATE_MASTER_REPGROUP().
ORA-23374 object group "string"."string" already exists
-
Cause: The given database already replicates the given object group. A materialized view repgroup cannot be created at a given site where a master repgroup with the same name already exists.
-
Action: Choose a different group or a different database.
ORA-23375 feature is incompatible with database version at string
-
Cause: A feature not compatible with the specified database was used.
-
Action: Set or raise the value of the COMPATIBLE initialization parameter to match the necessary compatibility level.
ORA-23376 node string is not compatible with replication version "string"
-
Cause: A feature not compatible with the remote database was used.
-
Action: Upgrade the remote database and retry the operation.
ORA-23377 bad name string for missing_rows_oname1 argument
-
Cause: An attempt was made to use the name of the reference site table as the name of the missing_rows_oname1 argument.
-
Action: Provide a separately created table with a different name for MISSING_ROWS_ONAME1 argument. The separately created table will contain the differences between the tables being compared.
ORA-23378 connection qualifier "string" is not valid for object group "string"."string"
-
Cause: The connection qualifier used in the database link for the specified object group does not match the qualifier specified for the group in CREATE_MASTER_REPGROUP.
-
Action: Use or create a database link which contains the correct connection qualifier.
ORA-23379 connection qualifier "string" is too long
-
Cause: The maximum length of a database link, including the connection qualifier, is 128 bytes.
-
Action: Use a shorter connection qualifier, or shorten the name of the database link
ORA-23380 propagation mode "string" is not valid
-
Cause: The specified propagation is misspelled, or is not supported. For materialized view sites, all materialized view object groups at the same materialized view site with the same master object group must all have the same propagation method.
-
Action: Refer to Oracle9i Replication for valid propagation modes. For materialized view sites, also ensure that the propagation modes of all materialized view object groups with the same master object group are the same.
ORA-23381 generated object for base object string.string@string does not exist
-
Cause: The system generated object(s) for the specified base object do not exist at the specified site. The current operation requires the base object to have generated replication support.
-
Action: Ensure that the generated replication object(s) for the base object exist and are valid at the specified site. If the generated object(s) do not exist, then the procedure DBMS_REPCAT.GENERATE_REPLICATION_SUPPORT() needs to be called from the master definition site for the base object. missing_rows_oname1 argument. The separately created table will contain the differences between the tables being compared.
ORA-23382 materialized view repgroup "string"."string" is not registered at site string
-
Cause: The materialized view REPGROUP is not currently registered at the master and so cannot be unregistered.
-
Action: No action required.
ORA-23383 registration for materialized view repgroup "string"."string" failed at site string
-
Cause: Insertion into local REPSCHEMA table failed.
-
Action: No action required.
ORA-23384 replication parallel push string argument out of range
-
Cause: Specified numeric argument to DBMS_DEFER_SYS.PUSH is invalid.
-
Action: Fix the argument value and try again.
ORA-23385 replication parallel push string argument not valid
-
Cause: Specified string argument to DBMS_DEFER_SYS.PUSH is invalid.
-
Action: Fix the argument value and try again.
ORA-23386 replication parallel push cannot create slave processes
-
Cause: An error was occurred while creating slave processes for parallel push.
-
Action: If the PARALLEL_MAX_SERVERS initialization parameter is zero, reconfigure the parameter to be greater than zero. Otherwise, contact Oracle Support Services.
ORA-23387 replication parallel push dequeue error
-
Cause: An attempt to dequeue a deferred transaction failed while trying to assign a new queue batch number.
-
Action: Contact Oracle Support Services.
ORA-23388 replication parallel push watermark error
-
Cause: An error occurred during parallel push while trying to update the high-water-mark information in SYSTEM.DEF$_DESTINATION.
-
Action: Contact Oracle Support Services.
ORA-23389 obsolete procedure; drop objects and recreate using new master
-
Cause: DBMS_REPCAT.SWITCH_MVIEW_MASTER is no longer supported.
-
Action: Drop the objects in the object group and re-create them using the new master.
ORA-23392 could not find materialized view to be associated with "string"."string"
-
Cause: Could not find materialized view associated with a trigger or index that is being pulled from the master site.
-
Action: Ensure that materialized view, master, and master index or trigger are registered as replicated objects.
ORA-23393 the user is already the propagator
-
Cause: The given user is already the current propagator.
-
Action: No action required.
ORA-23394 duplicate propagator
-
Cause: More than one valid propagator exists.
-
Action: Unregister any duplicate propagator.
ORA-23395 object "string"."string" of type "string" does not exist or is invalid
-
Cause: The given name was null or misspelled, the given type was wrong, the object does not exist as a valid database object, or the object does not exist as a replicated object with the appropriate status.
-
Action: Ensure the object is valid in the database, is visible to the user, and, if appropriate, is a valid object in ALL_REPOBJECT.
ORA-23396 database link "string" does not exist or has not been scheduled
-
Cause: The database link does not exist in the schema of the replication propagator or has not been scheduled.
-
Action: Ensure that the database link exists in the database, is accessible and is scheduled for execution.
ORA-23397 global name "string" does not match database link name "string"
-
Cause: The database link name at the local node does not match the global name of the database that the link accesses.
-
Action: Ensure that global names is set to true and the link name matches the global name.
ORA-23398 user name "string" at database link "string" does not match local user name "string"
-
Cause: The user name of the replication administration user at the local node and the user name at the node corresponding to the database link are not the same. Symmetric replication expects the two users to be the same.
-
Action: Ensure that the user ID of the replication administration user at the local node and the user ID at the node corresponding to the database link are the same.
ORA-23399 generation of replication support for "string"."string" is not complete
-
Cause: Replication support for the specified object has not been generated or the generation process is not yet complete.
-
Action: Ensure that replication support has been generated for the object. Use DBMS_REPCAT.GENERATE_REPLICATION_SUPPORT() to generate replication support for the object.
ORA-23400 invalid materialized view name "string"
-
Cause: A null, misspelled, or badly formed materialized view name was given to DBMS_MVIEW.REFRESH.
-
Action: Provide a valid materialized view name to DBMS_MVIEW.REFRESH.
ORA-23401 materialized view "string"."string" does not exist
-
Cause: A materialized view name was given to DBMS_MVIEW.REFRESH that is not in SYS.SNAP$ or its associated views.
-
Action: Provide a materialized view name that is in SYS.SNAP$, ALL_MVIEWS or USER_MVIEWS.
ORA-23402 refresh was aborted because of conflicts caused by deferred txns
-
Cause: There are outstanding conflicts logged in the DefError table at the materialized view's master.
-
Action: Resolve the conflicts in the master DefError table and refresh again after the table is empty. Alternatively, refresh with REFRESH_AFTER_ERRORS set to TRUE, which will proceed with the refresh even if there are conflicts in the master's DefError table. Proceeding despite conflicts can result with an updatable materialized view's changes appearing to be temporarily lost (until a refresh succeeds after the conflicts are resolved).
ORA-23403 refresh group "string"."string" already exists
-
Cause: Making a new refresh group when there is already a group of the same name in SYS.RGROUP$.
-
Action: Choose a different refresh group name.
ORA-23404 refresh group "string"."string" does not exist
-
Cause: A refresh group name was given that is not in SYS.RGROUP$.
-
Action: Provide a refresh group name that is in SYS.RGROUP$ or DBS_RGROUP.
ORA-23405 refresh group number string does not exist
-
Cause: A refresh group number was given that is not in SYS.RGROUP$.
-
Action: Provide a refresh group number that is in SYS.RGROUP$ or DBS_RGROUP.
ORA-23406 insufficient privileges on user "string"
-
Cause: The caller is not the owner of the materialized view and does not have ALTER ANY MATERIALIZED VIEW privileges.
-
Action: Perform the operation as the owner of the materialized view or as a user with ALTER ANY MATERIALIZED VIEW privileges.
ORA-23407 object name string must be shaped like "schema"."object" or "object"
-
Cause: The object name (for example, the rollback segment, the materialized view name, the refresh group) was incorrectly specified.
-
Action: Retry the operation with the object name properly specified (like "schema"."object" or "object").
ORA-23408 this replication operation is not supported in a mixed configuration
-
Cause: Operation is not supported if the object group is replicated at a pre-V8 node.
-
Action: Ensure that all nodes of the replicated object group are V8.
ORA-23409 could not find an unused refresh group number
-
Cause: 1000 consecutive refresh group numbers, as defined by the RGROUPSEQ number, were already used by rows in SYS.RGROUP$.
-
Action: Alter the sequence number to be within a legal unused range and destroy unneeded refresh groups.
ORA-23410 materialized view "string"."string" is already in a refresh group
-
Cause: A materialized view of the same name is already in a refresh group.
-
Action: Subtract the materialized view from the current refresh group and add it to its new refresh group, or combine the two refresh groups into a single refresh group.
ORA-23411 materialized view "string"."string" is not in refresh group "string"."string"
-
Cause: The specified materialized view is not in the specified refresh group.
-
Action: Try again with the proper materialized view and refresh group names.
ORA-23412 master table's primary key columns have changed
-
Cause: The master table's primary key constraint was modified after the primary key materialized view was created.
-
Action: Drop and re-create the primary key materialized view.
ORA-23413 table "string"."string" does not have a materialized view log
-
Cause: The fast refresh cannot be performed because the master table does not contain a materialized view log.
-
Action: Use the CREATE MATERIALIZED VIEW LOG command to create a materialized view log on the master table.
ORA-23414 materialized view log for "string"."string" does not record rowid values
-
Cause: A ROWID materialized view is being fast refreshed, but the materialized view log does not record ROWID information.
-
Action: Use the CREATE MATERIALIZED VIEW LOG...ADD ROWID command to begin recording ROWID information in the materialized view log.
ORA-23415 materialized view log for "string"."string" does not record the primary key
-
Cause: A primary key materialized view is being fast refreshed, but the materialized view log does not record primary key information.
-
Action: Use the CREATE MATERIALIZED VIEW LOG...ADD PRIMARY KEY command to begin recording primary key information in the materialized view log.
ORA-23416 table "string"."string" does not contain a primary key constraint
-
Cause: The master table does not contain a primary key constraint or the primary key constraint has been disabled.
-
Action: Create a primary key constraint on the master table or enable the existing constraint.
ORA-23417 unknown materialized view type: string
-
Cause: A fast refresh is being performed on a materialized view of an unknown or unsupported type.
-
Action: Check ALL_MVIEWS and ensure that the materialized view being refreshed is a valid materialized view.
ORA-23418 cannot unregister the propagator who is currently in use
-
Cause: The propagator is currently used in propagating replication RPCs.
-
Action: Try again later when there is no transaction active in propagating replication RPCs.
ORA-23419 regenerate replication support before resuming master activity
-
Cause: There are tables in the object group that require regeneration of replication support.
-
Action: Check the GENERATION_STATUS column in the ALL_REPOBJECT view. Regenerate replication support for any table in the object group with a 'NEEDSGEN' status. Resume master activity.
ORA-23420 interval must evaluate to a time in the future
-
Cause: The parameter INTERVAL evaluates to a time earlier than SYSDATE.
-
Action: Choose an expression that evaluates to a time later than SYSDATE.
ORA-23421 job number string is not a job in the job queue
-
Cause: There is no job visible to the caller with the given job number.
-
Action: Choose the number of a job visible to the caller.
ORA-23422 Oracle Server could not generate an unused job number
-
Cause: Oracle Server could not generate a job number that was not used to identify another job.
-
Action: Retry the operation.
ORA-23423 job number string is not positive
-
Cause: The given job number is less than 1.
-
Action: Choose a positive integer.
ORA-23424 materialized view "string"."string" at string not registered
-
Cause: The specified materialized view has not been successfully registered at this site.
-
Action: Register the materialized view manually at either the master site or the materialized view site.
ORA-23425 invalid materialized view identifier string
-
Cause: The argument provided to DBMS_MVIEW.PURGE_MVIEW_FROM_LOG is an invalid materialized view identifier or it does not identify an Oracle8 fast refreshable materialized view or the materialized view has already been purged.
-
Action: If the materialized view is an Oracle8 fast refreshable materialized view then provide PURGE_MVIEW_FROM_LOG with its valid materialized view identifier.
ORA-23426 deferred RPC queue has entries for string
-
Cause: The requested action cannot be performed until the queue is empty for the given site/database link.
-
Action: Use DBMS_DEFER_SYS.PUSH, DBMS_DEFER_SYS.PURGE_QUEUE or DBMS_DEFER_SYS.DELETE_TRAN to empty the queue.
ORA-23427 deferred purge queue argument string out of range
-
Cause: Specified numeric argument to DBMS_DEFER_SYS.PURGE_QUEUE is invalid.
-
Action: Fix the argument value and try again.
ORA-23428 job associated instance number string is not valid
-
Cause: A job is associated with an instance that is not running.
-
Action: Choose a running instance for job affinity, or set force parameter to TRUE.
ORA-23430 argument "string" cannot be NULL or empty string
-
Cause: The caller has provided an argument whose value cannot be NULL or the empty string.
-
Action: Check that the varchar2 value provided is not NULL or the empty string, and retry the call.
ORA-23431 wrong state: string
-
Cause: The routine was executed against a replicated object group that was in the wrong state.
-
Action: Make sure that the replicated object group is in the state given in the error message.
ORA-23432 master site string already exists
-
Cause: An attempt was made to instantiate a replicated object group at a master site that was already a part of the object group.
-
Action: If you were trying to add this site, do nothing because it already exists; otherwise, pick the name of another site, and rerun the routine.
ORA-23433 executing against wrong master site string
-
Cause: An attempt was made to execute the routine at a site that is different from the site specified in the argument of the routine.
-
Action: Provide an argument to the routine that correctly indicates the site against which the routine should be executing.
ORA-23434 master site string not known for object group
-
Cause: The site name given as an argument to a routine was not already known to the replicated object group.
-
Action: Execute the DBMS_OFFLINE_OG.BEGIN_INSTANTIATION() routine to add a new site to the replicated object group.
ORA-23435 cannot create an updatable ROWID materialized view with LOB columns
-
Cause: The propagation of LOB data from materialized view sites to the master site requires a primary key on the replicated table. Thus updatable ROWID materialized views that contain LOB columns are not supported.
-
Action: Create a primary key materialized view instead of a ROWID materialized view. If the materialized view already exists, it can be converted to a primary key materialized view using the ALTER MATERIALIZED VIEW DDL command.
ORA-23436 missing template authorization for user
-
Cause: The specified template authorization does not exist.
-
Action: Check the values for user name and refresh template name to ensure a valid row exists in the DBA_REPCAT_USER_AUTHORIZATIONS view.
ORA-23437 template authorization already exists for user
-
Cause: The specified user already has been authorized to use the specified refresh group template.
-
Action: Check the values for user name and refresh template name or query the DBA_REPCAT_USER_AUTHORIZATIONS view to ensure that the correct values were passed as parameters.
ORA-23438 missing refresh group template
-
Cause: The specified refresh group template does not exist.
-
Action: Verify that the refresh group template does not exist by querying the DBA_REPCAT_REFRESH_TEMPLATES view.
ORA-23439 refresh group template already exists
-
Cause: The specified refresh group template already exists.
-
Action: Verify that the refresh group template exists by querying the DBA_REPCAT_REFRESH_TEMPLATES view.
ORA-23440 incorrect public template value
-
Cause: The public template parameter is not 'Y', 'N' or NULL.
-
Action: Correct the value of the public template parameter. It must be 'Y','N' or NULL.
ORA-23441 object does not exist for refresh group template
-
Cause: The specified object does not exist in the refresh group template.
-
Action: Correct the object name and object type parameters. Check the DBA_REPCAT_TEMPLATE_OBJECTS view to verify the correct name and type of the object.
ORA-23442 object already exists for the refresh group template
-
Cause: The specified object already exists in the refresh group template.
-
Action: Change the object name and object type parameters. Query the DBA_REPCAT_REMPLATE_OBJECTS view to verify the correct name and type of the object.
ORA-23443 missing template parameter
-
Cause: The specified template parameter does not exist.
-
Action: Correct the template parameter value and execute the procedure again. Use the DBA_REPCAT_TEMPLATE_PARMS view to verify the name of the refresh group template and parameter name.
ORA-23444 duplicate template parameter
-
Cause: The template parameter already exists for the specified refresh group template.
-
Action: Correct the template parameter value and execute the procedure again. Use the DBA_REPCAT_TEMPLATE_PARMS view to verify the name of the refresh group template and parameter name.
ORA-23445 missing template site
-
Cause: The template site specified by the site name, user name and refresh group template name does not exist.
-
Action: Correct the invalid parameter and execute the procedure again. Use the DBA_REPCAT_TEMPLATE_SITES view to query the existing template sites.
ORA-23446 duplicate template site
-
Cause: The template site specified by the site name, user name and refresh group template name already exists.
-
Action: Correct the invalid parameter and execute the procedure again. Use the DBA_REPCAT_TEMPLATE_SITES view to query the existing template sites.
ORA-23447 missing user parameter value
-
Cause: The user parameter value specified by the user name, parameter name and refresh group template name does not exist.
-
Action: Correct the invalid parameter and execute the procedure again. Use the DBA_REPCAT_USER_PARM_VALUES view to query the existing user parameters.
ORA-23448 duplicate user parameter value
-
Cause: The user parameter value specified by the user name, parameter name and refresh group template name already exists.
-
Action: Correct the invalid parameter and execute the procedure again. Use the DBA_REPCAT_USER_PARM_VALUES view to query the existing user parameters.
ORA-23449 missing user name
-
Cause: The user specified by the user name parameter does not exist in the database.
-
Action: Correct an invalid user name or create the user in the master database. Use the DBA_USERS view to select the valid database users.
ORA-23450 flavor already contains object "string"."string"
-
Cause: The flavor already contains the specified object.
-
Action: Check that the specified object is correct. To add all columns of a table object, delete the object from the flavor and then add it again.
ORA-23451 flavor string already defined for object group "string"."string"
-
Cause: The given object group already contains a (possibly unpublished) definition of the specified flavor.
-
Action: Check the spelling of the flavor name. Check for an unpublished flavor of the desired name.
ORA-23452 flavor string of object group "string"."string" is already published
-
Cause: The given object group already contains a (published) definition of the specified flavor.
-
Action: Check the spelling of the flavor name.
ORA-23453 requested operation is not supported on top flavor
-
Cause: The TOP flavor has a NULL name and may not be directly defined or deleted.
-
Action: Supply the name of a flavor other than the TOP flavor or use DBMS_REPCAT routines to implicitly change the TOP flavor.
ORA-23454 flavor string not defined for object group "string"."string"
-
Cause: The given object group does not contain a (published) definition of the specified flavor.
-
Action: Check the spelling of the flavor name. Ensure the flavor has been defined (and published) for the object group.
ORA-23455 flavor string contains object "string"
-
Cause: The given flavor contains the object to be dropped.
-
Action: Purge the flavor or choose another object to drop.
ORA-23456 flavor string does not contain "string"
-
Cause: The flavor does not contain the given object, column, or attribute.
-
Action: Either drop the flavor or choose a different object, column, or attribute.
ORA-23457 invalid flavor ID string
-
Cause: The given flavor ID is invalid.
-
Action: Make sure this flavor has been instantiated. If the flavor ID is outside the range (-2147483647, 2147483647), contact Oracle Support Services.
ORA-23458 inappropriate flavor string at string
-
Cause: The given flavor at the given database prevents the operation from succeeding.
-
Action: Either change the database flavor or choose a different operation.
ORA-23459 flavor string must contain "string"
-
Cause: The flavor must contain the given object, column, or attribute.
-
Action: Either choose a different database flavor or ensure the object, column, or attribute is available.
ORA-23460 missing value for column string in resolution method "string" for "string"."string"."string"
-
Cause: Before resolving conflicts, some values necessary for resolving conflicts are not available; or, after resolving conflicts, some values necessary for retrying the SQL are not available.
-
Action: define appropriate flavors, provide necessary values through availability vector in USER FLAVOR FUNCTION for conflict resolution.
ORA-23461 fail to resolve conflict for "string"."string"."string"
ORA-23462 flavor string in use at site string
-
Cause: The given flavor cannot be deleted because it is being used at the given site.
-
Action: Change the flavor of the site, or unregister it if it is a materialized view site.
ORA-23463 flavor incompatible with object "string"."string"
-
Cause: An existing flavor includes the specified object with an incompatible type.
-
Action: Change the type of the object, or delete the flavor if it is not in use.
ORA-23464 flavor lacks column string of "string"."string"
-
Cause: The flavor includes some columns of an object group but not all the required columns.
-
Action: Change the flavor definition to include all required columns.
ORA-23465 flavor already includes column string of "string"."string"
-
Cause: The flavor includes the specified column which is being added.
-
Action: Check that the specified column is correct.
ORA-23466 flavor requires missing object "string"."string"
-
Cause: The flavor includes the specified object which does not exist.
-
Action: Check that the specified object name is correct, and create the object if appropriate.
ORA-23467 flavor lacks object "string"."string"
-
Cause: The flavor does not include the specified object which is being dropped.
-
Action: Check that the specified object is correct.
ORA-23468 missing string string
-
Cause: The template is missing the object with the specified key.
-
Action: Add the object to the template.
ORA-23469 string is different between templates
-
Cause: The values for the specified columns are different in each template for the same key values.
-
Action: Correct the column values to make the templates the same.
ORA-23470 invalid status
-
Cause: The status should be DELETED, INSTALLING or INSTALLED. Any other status is invalid.
-
Action: Check that the specified status value is correct.
ORA-23471 template not authorized for user
-
Cause: The refresh template is private and the user has not been authorized to instantiate the template.
-
Action: Authorize the user to use the template.
ORA-23472 materialized view "string"."string" must be atomically refreshed
-
Cause: Non-atomic refresh is not supported for the specified materialized view.
-
Action: Set the value of the ATOMIC parameter to FALSE in the refresh procedure being used or remove the specified materialized view from the set of materialized views being refreshed.
ORA-23473 replication RPC processing for "string"."string" is disabled
-
Cause: The processing of replication RPCs for the object group that contains this object is disabled. This includes RPCs in the error queue.
-
Action: Processing of replication RPCs is disabled when the object group is being offline instantiated. Wait until offline instantiation is finished.
ORA-23474 definition of "string"."string" has changed since generation of replication support
-
Cause: The current columns in the specified table and their column types do not match the columns and column types when replication support was last generated.
-
Action: Regenerate replication support for the affected table. All flavors that include the specified table should be checked for validity. Types for any UDT columns should also be checked for validity.
ORA-23475 key column string must be sent and compared
-
Cause: The specified column is a key column and must be sent and compared during replication propagation.
-
Action: Make sure every key column is sent and compared.
ORA-23476 cannot import from string to string
-
Cause: This object was imported from a database with a different global name than the importing database.
-
Action: Only import this object into a database with the same global name.
ORA-23477 unable to alter propagation mode for object group "string"."string"
-
Cause: The propagation method of a materialized view object group can only be altered when no other object groups with the same master object group are sharing the materialized view site.
-
Action: Ensure that there are no other materialized view object groups at the local site with the same master object group.
ORA-23478 object group string is already mastered at string
-
Cause: There is at least one other materialized view repgroup at the local site with the same group name but a different master site.
-
Action: Ensure that all materialized view repgroups at the local site with the same group name have the same master.
ORA-23480 Column string is not a top-level column of "string"."string".
-
Cause: The column is either not a top-level column or is not present in the table or materialized view.
-
Action: Ensure only valid top-level columns are used.
ORA-23482 column string of "string"."string": object types not allowed.
-
Cause: The column is of Object Type.
-
Action: Ensure that all the columns are not of Object Type.
ORA-23483 object "string"."string" not allowed in this operation.
-
Cause: The specified operation does not support the given object.
-
Action: Do not invoke the operation for this object.
ORA-23484 internal internet Application Server error: string
-
Cause: An internal error occurred in internet Application Server.
-
Action: Report the error and other information to support.
ORA-23485 Column group "string" must consist of a single numeric column only
-
Cause: The column group doesn't contain only one numeric column.
-
Action: Use a column group containing a single numeric column.
ORA-23487 object groups "string"."string" and "string"."string" do not have the same connection qualifier
-
Cause: The specified two object groups do not have the same connection qualifier.
-
Action: Do not invoke the operation on the above object groups, or ensure they have the same connection qualifier.
ORA-23488 propagation mode "string" for "string" is not allowed for this operation
-
Cause: This operation does not support the specified dblink in the above propagation mode.
-
Action: Do not invoke the operation for this dblink, or change the propagation mode for this dblink.
ORA-23489 duplicate entry "string"
-
Cause: The specified value is duplicated in the parameter list.
-
Action: Remove duplicated entries in the parameter list.
ORA-23490 extension request "string" with status "string" not allowed in this operation
-
Cause: The specified operation is not allowed for the extension request with the specified status.
-
Action: Ensure the extension request has the appropriate status before retrying this operation.
ORA-23491 no valid extension request at "string"
-
Cause: The specified database does not have a valid extension request.
-
Action: Ensure there is a valid extension request in the DBA_REPEXTENSIONS view before retrying this operation.
ORA-23492 no new sites for extension request "string"
-
Cause: There is no new site with the specified extension request.
-
Action: Ensure there is at least one new site in the DBA_REPSITES_NEW view for this request before retrying this operation.
ORA-23493 "string" is not a new site for extension request "string"
-
Cause: The specified extension request does not include the specified site as a new site.
-
Action: Ensure the specified site is a new site for this extension request before retrying this operation.
ORA-23494 too many rows for destination "string"
-
Cause: The specified destination has too many rows in the system.def$_destination table.
-
Action: Ensure the specified destination has at most two valid rows before retrying this operation.
ORA-23495 serial propagation can not be used for "string"
-
Cause: The sites involved may be in the process of adding a new site without quiescing.
-
Action: Check the def$_destination table for this destination and try parallel propagation.
ORA-23496 can not change disabled status for "string" and "string"
-
Cause: The disabled status for this site is set internally for synchronization during adding a new master without quiescing.
-
Action: Ensure adding a new master without quiescing finished before invoking this procedure.
ORA-23500 cannot switch master for a multi-tier materialized view repgroup "string"."string"
-
Cause: An attempt was made to switch master for a materialized view repgroup when its parent repgroup is also a materialized view repgroup. This is not allowed.
-
Action: Drop and recreate the materialized view repgroup based on a proper parent repgroup.
ORA-23501 refresh template cannot be instantiated for database with compatibility equal to or less than 8.0
-
Cause: Instantiation of a refresh template is not supported for database compatibility equal to or less than 8.0.
-
Action: Be sure the database compatibility is equal to 8.1 or higher.
ORA-23502 valid directory for offline instantiation is not specified
-
Cause: An attempt was made to offline instantiate to a directory which is not specified or null.
-
Action: There are two ways to specify the directory:
- As a parameter OFFLINE_DIRPATH to the API
- As an initialization parameter named UTL_FILE_DIR
Make sure you have specified an appropriate directory in which the offline file can be created.
ORA-23503 error occurred during IAS instantiation
-
Cause: An attempt was made to instantiate a IAS site. Error occurred during IAS instantiation.
-
Action: See the other errors on the error stack to look for the source of the problem. If the error still persists, contact Oracle Support Services.
ORA-23504 columns added to table do not match list of columns to be added
-
Cause: The list of columns passed as a parameter does not match the columns to be added to the table.
-
Action: Correct the DDL string or list of columns and rexecute.
ORA-23505 Object "string"."string" is missing.
-
Cause: The specified object does not exist.
-
Action: Check that the specified object is correct.
ORA-23514 invalid or incorrect number of arguments
-
Cause: The arguments passed to the online redefinition API were invalid or missing.
-
Action: Call the online redefinition API with the right number of valid arguments.
ORA-23515 materialized views and/or their indices exist in the tablespace
-
Cause: An attempt was made to drop a tablespace which contains materialized views and/or their indices.
-
Action: Drop the materialized views in this tablespace. Also, find indices belonging to materialized views in this tablespace and drop then. Then try dropping the tablespace.
ORA-23531 site owner already exists in the template
-
Cause: Site owner for the template already exists.
-
Action: Do not create multiple siteowners for this template.
ORA-23532 tables with different synchronization mechanisms are in the same group
-
Cause: Tables belonging to the same replication group were specified to be cached with different synchronization mechanisms.
-
Action: Do not specify different synchronization mechanisms while caching tables belonging to the same replication group.
ORA-23533 object "string"."string" can not be cached
-
Cause: An attempt was made to cache an object which is not supported.
-
Action: Do not cache an object which is not supported.
ORA-23534 missing column in materialized view container table "string"."string"
-
Cause: After import, the materialized view container table has missing columns.
-
Action: Check if materialized view container table was imported correctly.
ORA-23535 instantiating templates from multiple back ends is not allowed
-
Cause: An attempt was made to set a new non-null back end database for an iAS site.
-
Action: Call dbms_ias_configure.set_back_end_db procedure with null dblink. Then, call the same procedure with the new non-null dblink.
ORA-23536 the object "string"."string" is not cached at the middle tier as expected.
-
Cause: The object may have been dropped or renamed at the back end after dbms_ias_inst.start_ias_inst was executed.
-
Action: Check the validity of the object at the back end and retry the instantiation.
ORA-23537 function or procedure string is not allowed to be invoked from this site.
-
Cause: This function or procedure is restricted to the backend or middle tier site.
-
Action: Connect to the proper site before calling this function or procedure.
ORA-23538 cannot explicitly refresh a NEVER REFRESH materialized view ("string")
-
Cause: An attempt was made to explicitly refresh a NEVER REFRESH materialized view.
-
Action: Do not perform this refresh operation or remove the materialized views from the list.
ORA-23600 cannot create PROPAGATION, string already exists
-
Cause: The propagate_name already exists.
-
Action: Drop the propagate_name using DROP_PROPAGATE command or specify propagate_name.
ORA-23601 PROPAGATION_NAME string does not exist
-
Cause: Propagation does not exist.
-
Action: Query the DBA_PROPAGATION view to find existing propagation_name.
ORA-23602 Invalid streams process type string
-
Cause: Specified streams process type is not valid.
-
Action: Specify either capture or apply.
ORA-23605 invalid value "string" for STREAMS parameter string
-
Cause: An attempt was made to specify an invalid parameter value.
-
Action: Specify a valid value for the parameter. Check the documentation for valid parameter values.
ORA-23606 invalid object string
-
Cause: An attempt was made to specify an invalid object.
-
Action: Specify a valid object.
ORA-23607 invalid column "string"
-
Cause: An invalid column was specified in the column list.
-
Action: Check the columns in the object and specify the right column name.
ORA-23608 invalid resolution column "string"
-
Cause: An invalid column was specified as the resolution column. The resolution column must belong to the list of columns specified in the 'column_list' parameter.
-
Action: Check the columns in the column_list and specify the right resolution column name.
ORA-23619 non-Oracle system error: string
-
Cause: A non-Oracle database has returned an error message to STREAMS when attempting to apply a DML statement. The non-Oracle system error message is a parameter to this Oracle error.
-
Action: Corrective action may or may not be possible (depending on the non-Oracle system error). If corrective action is possible, then correct the problem and try applying the transaction again.
ORA-24000 invalid value string, string should be of the form [SCHEMA.]NAME
-
Cause: An invalid value was specified for the parameter.
-
Action: Specify a string of the form [SCHEMA.]NAME.
ORA-24001 cannot create QUEUE_TABLE, string already exists
-
Cause: The queue table already exists in the queueing system.
-
Action: Drop the table first using the DROP_QUEUE_TABLE() command or specify another table.
ORA-24002 QUEUE_TABLE string does not exist
-
Cause: QUEUE_TABLE does not exist.
-
Action: Query on the user view USER_QUEUE_TABLES to find out existing queue tables.
ORA-24003 Queue table index string inconsistent with queue table string
-
Cause: The queue table index has not yet been successfully imported.
-
Action: Import the queue table index before attempting to use the queue table. If the import failed, correct the problem and try to import the queue table index again.
ORA-24004 invalid column name string in SORT_LIST, should be ENQ_TIME or PRIORITY
-
Cause: Invalid column name was specified in the SORT_LIST.
-
Action: The valid column names are ENQ_TIME and PRIORITY.
ORA-24005 must use DBMS_AQADM.DROP_QUEUE_TABLE to drop queue tables
-
Cause: An attempt was made to use the SQL command DROP TABLE for queue tables, but DROP TABLE is not supported for queue tables.
-
Action: Use the DBMS_AQADM.DROP_QUEUE_TABLE procedure instead of the DROP TABLE command.
ORA-24006 cannot create QUEUE, string already exists
-
Cause: The queue requested to be created already exists.
-
Action: Specify another queue name. Query USER_QUEUES for all the existing queues in the users's schema.
ORA-24007 invalid value string, MAX_RETRIES should be non-negative integer
-
Cause: An invalid value was specified for MAX_RETRIES.
-
Action: Specify a non-negative integer.
ORA-24008 queue table string.string must be dropped first
-
Cause: An error was detected when dropping a queue table in a cluster, tablespace, or schema.
-
Action: Use the DBMS_AQADM.DROP_QUEUE_TABLE procedure to drop the specified queue table first; then, retry the operation.
ORA-24009 invalid value string, QUEUE_TYPE should be NORMAL_QUEUE or EXCEPTION_QUEUE
-
Cause: Invalid queue type parameter.
-
Action: Valid values are NORMAL_QUEUE for normal queue and EXCEPTION_QUEUE for exception queue.
ORA-24010 QUEUE string does not exist
-
Cause: The specified queue does not exist.
-
Action: Specify a valid queue. Query USER_QUEUES for all the valid queues.
ORA-24011 cannot drop QUEUE, string should be stopped first
-
Cause: The queue has not been stopped. That is, either enqueue or dequeue is still enabled.
-
Action: Stop the queue first using the STOP_QUEUE command and disable it from both enqueueing and dequeueing.
ORA-24012 cannot drop QUEUE_TABLE, some queues in string have not been dropped
-
Cause: A queue exists in the queue table which has not been dropped. All queues need to be dropped first.
-
Action: Drop all queues belonging to this queue table using the DROP_QUEUE() command. Be sure to stop the queues appropriately before dropping them. Alternately, use the force option in DROP_QUEUETABLE.
ORA-24013 invalid value string, RETRY_DELAY should be non-negative
-
Cause: A negative value was specified for RETRY_DELAY.
-
Action: Specify a non-negative value for RETRY_DELAY.
ORA-24014 invalid value string, RETENTION_TIME should be FOREVER or non-negative
-
Cause: Queue retention was specified, but the retention time was specified to be less than zero.
-
Action: Specify the retention time to be non-negative or FOREVER. Alternately do not specify retention.
ORA-24015 cannot create QUEUE_TABLE, QUEUE_PAYLOAD_TYPE string.string does not exist
-
Cause: An invalid QUEUE_PAYLOAD_TYPE specified during CREATE_QUEUE_TABLE.
-
Action: The QUEUE_PAYLOAD_TYPE should be RAW or an object type that already exists in the database.
ORA-24016 cannot create QUEUE_TABLE, user string does not have execute privileges on QUEUE_PAYLOAD_TYPE string.string
-
Cause: An invalid object type specified for QUEUE_PAYLOAD_TYPE during CREATE_QUEUE_TABLE.
-
Action: Make sure you have execute privileges on the object type specified for the queue.
ORA-24017 cannot enable enqueue on QUEUE, string is an exception queue
-
Cause: An attempt was made to enable enqueueing to an exception queue.
-
Action: No action required.
ORA-24018 STOP_QUEUE on string failed, outstanding transactions found
-
Cause: There were outstanding transactions on the queue, and WAIT was set to false, so STOP_QUEUE was unsuccessful in stopping the queue.
-
Action: Set WAIT to TRUE and try STOP_QUEUE again. It will hang till all outstanding transactions are completed.
ORA-24019 identifier for string too long, should not be greater than string characters
-
Cause: The identifier specified is too long.
-
Action: Try again with a shorter identifier.
ORA-24020 Internal error in DBMS_AQ_IMPORT_INTERNAL, string
-
Cause: An internal error occurred in the package. DBMS_AQ_IMPORT_INTERNAL.
-
Action: Contact Oracle Support Services.
ORA-24021 queue table definition not imported for string.string
-
Cause: The queue definition is not updated because the queue table was not imported properly.
-
Action: Import the queue table again.
ORA-24022 the specified parameters has no effect on the queue
-
Cause: The parameter combination will not cause the queue to be started or stopped.
-
Action: No action required. This is a warning.
ORA-24023 Internal error in DBMS_AQ_EXP_INTERNAL.string [string] [string]
-
Cause: An internal error occurred in the package DBMS_AQ_EXP_INTERNAL.
-
Action: Contact Oracle Support Services.
ORA-24024 Internal error in DBMS_AQ_IMP_INTERNAL.string [string] [string]
-
Cause: An internal error occurred in the package DBMS_AQ_IMP_INTERNAL.
-
Action: Contact Oracle Support Services.
ORA-24025 invalid value string, QUEUE_PAYLOAD_TYPE should be RAW or an object type
-
Cause: Parameter QUEUE_PAYLOAD_TYPE has invalid value.
-
Action: Specify a valid object type or RAW.
ORA-24026 operation failed, queue string.string has errors
-
Cause: An attempt was made to enqueue, dequeue or administer a queue which has errors.
-
Action: Drop the queue table setting the force option to true.
ORA-24027 AQ HTTP propagation encountered error, status-code string, string
-
Cause: AQ propagation's HTTP request to the propagation servlet at the specified address encountered an error.
-
Action: Specify a valid address in the connect string of the propagation destination dblink, the dblink user has the correct permissions, check if the AQ propagation servlet was properly installed.
ORA-24028 cannot create a reciever non-repudiable single consumer queue
-
Cause: Tried to create a reciever non-repudiable single consumer queue.
-
Action: This feature is not supported.
ORA-24029 operation not allowed on a single-consumer queue
-
Cause: Tried an operation not allowed on a single-consumer queue.
-
Action: Specify the operation on a multi-consumer queue.
ORA-24030 Only one of rule or rule-set must be specified
-
Cause: Specified both a rule and rule-set for the operation.
-
Action: Specify only one of rule or rule-set.
ORA-24031 invalid value, string should be non-NULL
-
Cause: Parameter is NULL.
-
Action: Specify a non-NULL value for the parameter.
ORA-24032 object string exists, index could not be created for queue table string
-
Cause: Oracle AQ tried to create an index with the name specified in the error message. The index could not be created for the specified queue table because a object exists with the same name.
-
Action: Drop the object specified in the error message and retry the command. You can also choose a different name for the queue table.
ORA-24033 no recipients for message
-
Cause: An enqueue was performed on a queue that has been set up for multiple dequeuers but there were neither explicit recipients specified in the call nor were any queue subscribers determined to be recipients for this message.
-
Action: Either pass a list of recipients in the enqueue call or add subscribers to the queue for receiving this message.
ORA-24034 application string is already a subscriber for queue string
-
Cause: An application name that was already a subscriber for the queue was specified in the DBMS_AQ.SUBSCRIBE call.
-
Action: Choose another application name and retry the call.
ORA-24035 AQ agent string is not a subscriber for queue string
-
Cause: An AQ agent that was not a subscriber for the queue was specified.
-
Action: Check the name and/or address of the agent and retry the call.
ORA-24036 invalid SORT_ORDER column string specified for queue table
-
Cause: The CREATE QUEUE TABLE command was issued with MESSAGE_GROUPING set to TRANSACTIONAL and a sort order column other than priority. Only the priority column can be specified in the sort order for queue tables with transactional grouping.
-
Action: Change the sort order list in the CREATE QUEUE TABLE command and retry the call.
ORA-24037 schema string in QUEUE_NAME is not same as schema string in QUEUE_TABLE
-
Cause: The schema specified in the QUEUE_NAME parameter of CREATE_QUEUE is not the same as the schema specified in the QUEUE_TABLE parameter.
-
Action: Use the same schema name for both the QUEUE_NAME and QUEUE_TABLE parameters and retry the command.
ORA-24038 RETRY_DELAY and MAX_RETRIES cannot be used for a 8.0 compatible multiple consumer queue
-
Cause: The CREATE_QUEUE or ALTER_QUEUE command was issued with a non-zero RETRY_DELAY and a QUEUE_TABLE that was created for multiple consumers and with COMPATIBLE parameter set to '8.0'.
-
Action: Either set the RETRY_DELAY to zero or upgrade the queue table to 8.1 compatible using the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure.
ORA-24039 Queue string not created in queue table for multiple consumers
-
Cause: Either an ADD_SUBSCRIBER, ALTER_SUBSCRIBER, or REMOVE_SUBSCRIBER procedure, or an ENQUEUE with a non-empty recipient list, was issued on a queue that was not created for multiple consumers.
-
Action: Create the queue in a queue table that was created for multiple consumers and retry the call.
ORA-24041 propagation schedule exists for QUEUE string and DESTINATION string
-
Cause: A SCHEDULE_PROPAGATION was issued for a queue and destination pair which has an existing propagation schedule.
-
Action: Issue UNSCHEDULE_PROPAGATION to remove the existing schedule and then reissue the SCHEDULE_PROPAGATION call.
ORA-24042 no propagation schedule exists for QUEUE string and DESTINATION string
-
Cause: AN UNSCHEDULE_PROPAGATION was issued for a queue and destination pair which has no existing propagation schedule.
-
Action: Verify the spelling of the specified QUEUE and DESTINATION and then reissue the call with the correct spelling.
ORA-24043 destination string uses a reserved name, names with AQ$_ prefix are not valid
-
Cause: An attempt was made to specify a reserved name for a destination.
-
Action: Enter a different value or NULL for the local destination. Then retry the operation.
ORA-24044 source string and destination string object types do not match
-
Cause: A message recipient's queue has a different object structure than the sender's queue. The message cannot be propagated.
-
Action: Either remove the recipient from the subscriber's list for the sender's queue or create the destination queue with an object type that matches the source queue's object type.
ORA-24045 invalid agent address string, agent address should be of the form [SCHEMA.]NAME[@DATABASE LINK]
-
Cause: An invalid value was specified for the agent address parameter.
-
Action: Specify a string of the form [SCHEMA.]NAME[@DATABASE LINK].
ORA-24046 protocol attribute reserved for future use
-
Cause: The protocol attribute of the AQ agent object type is reserved for future use.
-
Action: Do not specify the protocol attribute in the agent object type.
ORA-24047 invalid agent name string, agent name should be of the form NAME
-
Cause: An invalid value was specified for the agent name parameter.
-
Action: Specify a string of the form NAME. Then retry the operation.
ORA-24048 cannot create QUEUE_TABLE, user does not have access to AQ object types
-
Cause: An attempt was made to issue the CREATE_QUEUE_TABLE command, but the user who issued the command does not have access to internal AQ object types.
-
Action: Use the DBMS_AQADM.GRANT_TYPE_ACCESS procedure to grant the user access to the AQ object types.
ORA-24049 invalid agent name string, names with AQ$_ prefix are not valid
-
Cause: An attempt was made to use a reserved prefix in the agent name.
-
Action: Enter a different value for the agent name. Then, retry the operation.
ORA-24050 subscribers are not supported for exception queue string
-
Cause: An ADD_SUBSCRIBER, ALTER_SUBSCRIBER, or REMOVE_SUBSCRIBER procedure was issued on a queue that was created as an EXCEPTION_QUEUE.
-
Action: Specify a NORMAL_QUEUE in the procedure.
ORA-24051 cannot propagate object type payloads that have a REF or BFILE attribute
-
Cause: An ADD_SUBSCRIBER or ENQUEUE procedure with a non-NULL address field in the agent type was issued on a queue whose payload has a REF or BFILE attribute. Propagation of object type payloads that have a REF or BFILE attribute currently is not supported.
-
Action: Specify an agent with a NULL address field so that the agent can dequeue from the same queue. Or, change the object type definition to one that does not use REF or BFILE attributes.
ORA-24052 cannot propagate object type payloads with LOB attributes to an 8.0 release
-
Cause: The recipient of a message with LOB attributes was using an Oracle 8.0 release. Propagation of LOB attributes is supported only in Oracle 8.1 and higher releases.
-
Action: Upgrade the target release to Oracle 8.1 and retry. Or, change the object type definition to one that does not use LOBs.
ORA-24053 PRIMARY_INSTANCE and SECONDARY_INSTANCE must be non-negative
-
Cause: One of PRIMARY_INSTANCE or SECONDARY_INSTANCE was negative.
-
Action: Specify non-negative integers for PRIMARY_INSTANCE and SECONDARY_INSTANCE.
ORA-24054 cannot propagate to an Oracle 8.0.3 release or lower release
-
Cause: The recipient of a message was using an Oracle 8.0.3 release or lower release. Propagation is supported only in Oracle 8.0.4 and higher releases.
-
Action: Upgrade the target release to Oracle 8.0.4 or higher and retry.
ORA-24055 cannot delete propagation status rows that are in prepared state
-
Cause: An attempt was made to use the internal administration procedure to delete status rows from the SYS.AQ$_PROPAGATION_STATUS table that were in the prepared state.
-
Action: Wait for the propagation to complete successfully before retrying the operation.
ORA-24056 internal inconsistency for QUEUE string and destination string
-
Cause: The sequence numbers used in the SYS.AQ$_PROPAGATION_STATUS table were inconsistent for the given queue and destination.
-
Action: Contact Oracle Support Services.
ORA-24057 cannot define subscriber with rule for queue string
-
Cause: An ADD_SUBSCRIBER or ALTER_SUBSCRIBER procedure with a rule was issued on a queue for which rule based subscribers are not supported. Rule based subscribers currently are supported only for NORMAL (persistent) multi-consumer queues created using an Oracle release 8.1.0 or higher compatible queue table.
-
Action: Create a NORMAL multi-consumer queue in an Oracle release 8.1.0 or higher compatible queue table, and retry the call. Or, if the queue is a normal (persistent) multi-consumer queue, convert the queue table to Oracle 8.1.0 or higher compatibility and retry.
ORA-24058 cannot downgrade QUEUE_TABLE that has propagation in a prepared state
-
Cause: An attempt was made to downgrade the queue table when there were messages being propagated that were in the prepared state.
-
Action: Wait for the propagation to complete before retrying the operation.
ORA-24059 invalid COMPATIBLE parameter setting string specified in DBMS_AQADM.string
-
Cause: An invalid compatible parameter was specified in the DBMS_AQADM procedure. The parameter setting must be of the form '8.x.y' where x is the release number and y is the update number.
-
Action: Specify a valid COMPATIBLE parameter setting, and retry the operation.
ORA-24060 cannot convert QUEUE_TABLE, string already is compatible with release string
-
Cause: The source queue table in the DBMS_AQADM procedure is compatible with the specified COMPATIBLE parameter setting.
-
Action: Choose a different COMPATIBLE parameter setting to convert the queue table to the desired compatibility.
ORA-24061 cannot specify non-zero SECONDARY_INSTANCE if PRIMARY_INSTANCE was zero
-
Cause: A non-zero value was specified for SECONDARY_INSTANCE when PRIMARY_INSTANCE was zero.
-
Action: Specify a non-zero primary instance before you specify a non-zero secondary instance.
ORA-24062 Subscriber table string inconsistent with queue table string
-
Cause: The subscriber table has not yet been successfully imported.
-
Action: Import the subscriber table before attempting to use the queue table. If the import failed, correct the problem and try to import the subscriber table again.
ORA-24063 cannot downgrade QUEUE_TABLE that has queues with rule-based subscribers
-
Cause: An attempt was made to downgrade the queue table when there were queues on which rule-based subscribers are defined.
-
Action: Remove the rule-based subscribers for all queues in this queue table and retry.
ORA-24064 propagation for QUEUE string and DESTINATION string already enabled
-
Cause: An ENABLE_SCHEDULE_PROPAGATION command was issued for a queue and destination pair whose propagation schedule already was enabled.
-
Action: Make sure the QUEUE and DESTINATION are correct when you issue the ENABLE_SCHEDULE_PROPAGATION command.
ORA-24065 propagation for QUEUE string and DESTINATION string already disabled
-
Cause: A DISABLE_SCHEDULE_PROPAGATION command was issued for a queue and destination pair whose propagation schedule already was disabled.
-
Action: Make sure the QUEUE and DESTINATION are correct when you issue the DISABLE_SCHEDULE_PROPAGATION command.
ORA-24066 invalid privilege specified
-
Cause: An invalid privilege is specified for granting or revoking privilege.
-
Action: Specify a valid privilege.
ORA-24067 exceeded maximum number of subscribers for queue string
-
Cause: An attempt was made to add new subscribers to the specified, but the number of subscribers for this queue has exceeded the maximum number (1024) of subscribers allowed per queue.
-
Action: Remove existing subscribers before trying to add new subscribers.
ORA-24068 cannot start queue string, queue table string is being migrated
-
Cause: An attempt was made to start a queue in a queue table that is being migrated.
-
Action: Complete the queue table migration, and retry the operation.
ORA-24069 cannot downgrade queue table string while it is being upgraded
-
Cause: An attempt was made to downgrade a queue table, but a previous command to upgrade the queue table has not yet completed successfully.
-
Action: Complete the upgrade of the queue table by re-executing the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure. Then, downgrade the queue table.
ORA-24070 cannot upgrade queue table string while it is being downgraded
-
Cause: An attempt was made to upgrade a queue table, but a previous command to downgrade the queue table has not yet completed successfully.
-
Action: Complete the downgrade of the queue table by re-executing the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure. Then, upgrade the queue table.
ORA-24071 cannot perform operation string, queue table string is being migrated
-
Cause: An attempt was made to perform an operation on a queue in a queue table that is being migrated.
-
Action: Complete the queue table migration, and retry the operation.
ORA-24072 cannot execute MIGRATE_QUEUE_TABLE procedure; must own queue table
-
Cause: An attempt was made to upgrade or downgrade a queue table using the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure, but the user who executed the procedure does not own the queue.
-
Action: Reconnect as the owner of the queue table, and then execute the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure.
ORA-24073 cannot specify RETENTION_TIME on exception queue string.string
-
Cause: An attempt was made to create or alter an exception queue by specifying a non-zero RETENTION_TIME.
-
Action: Use the default RETENTION_TIME parameter value for exception queues.
ORA-24074 RETRY_DELAY and MAX_RETRIES cannot be used for exception queue string
-
Cause: The CREATE_QUEUE or ALTER_QUEUE command was issued with a non-zero RETRY_DELAY and an exception queue.
-
Action: Do not specify RETRY_DELAY or MAX_RETRIES for exception queues.
ORA-24075 cannot specify agent with NULL address and non-NULL protocol
-
Cause: An ADD_SUBSCRIBER or enqueue was attempted with an agent that had a NULL address and a non-NULL protocol.
-
Action: Either specify a non-NULL address or set the protocol to NULL.
ORA-24076 cannot perform operation string for NON_PERSISTENT queue string.string
-
Cause: One of the operations, SCHEDULE_PROPAGATION, ALTER_QUEUE, LISTEN, DEQUEUE was issued for a NON_PERSISTENT queue.
-
Action: Do not specify a NON_PERSISTENT queue for these operations.
ORA-24077 cannot create propagation schedule for EXCEPTION queue string.string
-
Cause: A SCHEDULE_PROPAGATION was issued for an EXCEPTION queue. Propagation schedules can be created only for NORMAL queues.
-
Action: To propagate messages from a queue, specify the queue type as NORMAL.
ORA-24078 cannot specify a non-NULL SECONDARY_INSTANCE if PRIMARY_INSTANCE was NULL
-
Cause: A non-NULL value was specified for SECONDARY_INSTANCE when PRIMARY_INSTANCE was NULL.
-
Action: Specify a non-NULL primary instance before you specify a non-NULL secondary instance.
ORA-24079 invalid name string, names with AQ$_ prefix are not valid for string
-
Cause: An attempt was made to use a reserved prefix for the object name.
-
Action: Enter a different name for this object. Then, retry the operation.
ORA-24080 unschedule_propagation pending for QUEUE string and DESTINATION string
-
Cause: A propagation administration command was issued for a queue and destination pair whose propagation is being unscheduled.
-
Action: Do not issue propagation administration commands for a propagation schedule on which there is a pending unschedule request.
ORA-24081 compatible parameter needs to be string or greater
-
Cause: The value of the COMPATIBLE parameter was not high enough to allow the operation.
-
Action: Shut down and restart with a higher compatibility setting.
ORA-24082 propagation may still be happening for the schedule for QUEUE string and DESTINATION string
-
Cause: The snapshot process executing the propagation schedule did not respond to the disable propagation command.
-
Action: Make sure that the job for the propagation schedule has been ended.
ORA-24083 cannot specify remote subscribers for string QUEUE string
-
Cause: An ADD_SUBSCRIBER call with a non-null address field was issued on a queue which does not support remote subscribers. Remote subscribers are not supported for NON_PERSISTENT QUEUES.
-
Action: Specify a null address field and retry the call.
ORA-24084 DBLINK name in address field of agent string is not unique within the first 24 bytes"
-
Cause: Advanced Queuing requires that the agent's DBLINK name should be unique within the first 24 bytes (for 8.0 compatible queue tables)
-
Action: Specify a DBLINK name that is unique within the first 24 bytes or migrate to 8.1 compatible queue tables where this restriction is not there.
ORA-24085 operation failed, queue string is invalid
-
Cause: An attempt was made to enqueue, dequeue or administer a queue which is invalid. This could have occurred because the payload type of the queue's queue table was dropped.
-
Action: Drop the queue table setting the force option to true.
ORA-24086 cannot create an 8.0 compatible string queue
-
Cause: An attempt was made to create an 8.0 compatible queue table and enable a feature that is supported only on 8.1 style queue tables.
-
Action: This feature is not supported.
ORA-24087 Invalid database user string
-
Cause: An invalid database username was specified.
-
Action: Specify a valid database user.
ORA-24088 AQ Agent string does not exist
-
Cause: This AQ Agent does not exist.
-
Action: Specify a valid AQ agent. Check the DBA_AQ_AGENTS view for a list of valid aq agents.
ORA-24089 AQ Agent string already exists
-
Cause: This AQ agent has already been created.
-
Action: Specify another agent name or use the ALTER api to modify the agent.
ORA-24090 at least one protocol must be enabled
-
Cause: No protocol was enabled for aq agent.
-
Action: Enable one of the protocols by setting one of the enable parameters to true.
ORA-24093 AQ agent string not granted privileges of database user string
-
Cause: The specified AQ agent does not have privileges of the specified database user.
-
Action: Specify a valid combination of AQ agent and database user. Check the DBA_AQ_AGENT_PRIVS or USER_AQ_AGENT_PRIVS view for user/agent mappings.
ORA-24094 invalid transformation, target type does not match that of the queue
-
Cause: The target type of the transformation specified was different from the type of the queue.
-
Action: Provide a valid transformation whose target type is the same as the queue type.
ORA-24095 invalid transformation, source type does not match that of the queue
-
Cause: The source type of the transformation specified was different from the type of the queue.
-
Action: Provide a valid transformation whose source type is the same as the queue type.
ORA-24096 invalid message state specified
-
Cause: Invalid value was specified for message state.
-
Action: Provide a valid message state as specified in the documentation.
ORA-24097 Invalid value string, string should be non-negative
-
Cause: A negative value or NULL was specified for the parameter.
-
Action: Specify a non-negative integer.
ORA-24098 invalid value string for string
-
Cause: An Invalid value or NULL was specified for the parameter.
-
Action: Check the documentation for valid values.
ORA-24099 operation not allowed for 8.0 compatible queues
-
Cause: The specified operation is only supported for queues with compatibility equal to 8.1 or higher.
-
Action: Upgrade the 8.0 compatible queue to release 8.1 using DBMS_AQADM.MIGRATE_QUEUE_TABLE or specify a queue with compatibility euqal to 8.1 or higher.
ORA-24100 error in ktz testing layer
-
Cause: There is an error in the Transaction layer test ICDs.
ORA-24120 invalid string parameter passed to DBMS_REPAIR.string procedure
-
Cause: An invalid parameter was passed to the specified DBMS_REPAIR procedure.
-
Action: Specify a valid parameter value or use the parameter's default.
ORA-24121 both cascade and a block range passed to DBMS_REPAIR.CHECK_OBJECT procedure
-
Cause: Both cascade and a block range were specified in a call to DBMS_REPAIR.CHECK_OBJECT.
-
Action: Use either cascade or a block range, or do not use either one.
ORA-24122 invalid block range specification
-
Cause: An incorrect block range was specified.
-
Action: Specify correct values for the BLOCK_START and BLOCK_END parameters.
ORA-24123 feature string is not yet implemented
-
Cause: An attempt was made to use the specified feature, but the feature is not yet implemented.
-
Action: Do not attempt to use the feature.
ORA-24124 invalid ACTION parameter passed to DBMS_REPAIR.string procedure
-
Cause: An invalid ACTION parameter was specified.
-
Action: Specify CREATE_ACTION, PURGE_ACTION or DROP_ACTION for the ACTION parameter.
ORA-24125 Object string.string has changed
-
Cause: An attempt was made to fix corrupt blocks on an object that has been dropped or truncated since DBMS_REPAIR.CHECK_OBJECT was run.
-
Action: Use DBMS_REPAIR.ADMIN_TABLES to purge the repair table and run DBMS_REPAIR.CHECK_OBJECT to determine whether there are any corrupt blocks to be fixed.
ORA-24126 invalid CASCADE_FLAG passed to DBMS_REPAIR.string procedure
-
Cause: CASCADE_FLAG was specified for an object that is not a table.
-
Action: Use CASCADE_FLAG only for tables.
ORA-24127 TABLESPACE parameter specified with an ACTION other than CREATE_ACTION
-
Cause: The TABLESPACE parameter can only be used with CREATE_ACTION.
-
Action: Do not specify TABLESPACE when performing actions other than CREATE_ACTION.
ORA-24128 partition name specified for a non-partitioned object
-
Cause: A partition name was specified for an object that is not partitioned.
-
Action: Specify a partition name only if the object is partitioned.
ORA-24129 table name string does not start with string prefix
-
Cause: An attempt was made to pass a table name parameter without the specified prefix.
-
Action: Pass a valid table name parameter.
ORA-24130 table string does not exist
-
Cause: An attempt was made to specify a map, repair, or sync table that does not exist.
-
Action: Specify a valid table name parameter.
ORA-24131 table string has incorrect columns
-
Cause: An attempt was made to specify a map, repair, or sync table that does not have a correct definition.
-
Action: Specify a table name that refers to a properly created table.
ORA-24132 table name string is too long
-
Cause: An attempt was made to specify a table name is greater than 30 characters long.
-
Action: Specify a valid table name parameter.
ORA-24141 rule set string.string does not exist
-
Cause: An attempt to access or modify a ruleset was made, which failed because the ruleset does not exist.
-
Action: Only access or modify existing rulesets.
ORA-24142 invalid ruleset name
-
Cause: An attempt to create a ruleset with an invalid name was made. The ruleset name cannot be NULL, and cannot be more than 26 characters, unless a RULES_TABLE_NAME is also specified, in which case the ruleset name may be up to 30 characters.
-
Action: Retry the create with a valid ruleset name.
ORA-24143 invalid evaluation context name
-
Cause: An attempt to create a rule/ruleset on an invalid evaluation name was made. The evaluation_context can not be more than 30 characters. The evaluation context with the name specified must exist.
-
Action: Retry the create with a valid evaluation context name.
ORA-24144 rules engine internal error, arguments: [string], [string]
-
Cause: An internal error occurred in the rules engine. This indicates that the rules engine has encountered an exception condition.
-
Action: Contact Oracle Support Services. The first argument is the error and the second argument is the package.
ORA-24145 evaluation context string.string already exists
-
Cause: An evaluation context of the given name already exists.
-
Action: Specify another name for the evaluation context being created.
ORA-24146 rule string.string already exists
-
Cause: A rule of the given name already exists.
-
Action: Specify another name for the rule being created.
ORA-24147 rule string.string does not exist
-
Cause: The rule of the given name does not exist.
-
Action: Create the rule or specify one that exists.
ORA-24148 cannot drop rule string.string with dependents
-
Cause: The rule still belongs to some rulesets, cannot be dropped.
-
Action: Do not drop a rule that belongs to rulesets without force option.
ORA-24149 invalid rule name
-
Cause: An attempt to create a rule with an invalid name was made.
-
Action: The rule name can not be NULL, and can not be more than 30 characters.
ORA-24150 evaluation context string.string does not exist
-
Cause: The evaluation context of the given name does not exist.
-
Action: Create the evaluation context or specify one that exists.
ORA-24151 no evaluation context is associated with rule string.string or rule set string.string
-
Cause: When adding a rule to a rule set, either the rule or the rule set must have an evaluation context associated with it.
-
Action: Do not add a rule without an evaluation context to a ruleset that does not have a default evaluation context.
ORA-24152 cannot drop evaluation context string.string with dependents
-
Cause: The evaluation context still belongs to some rules or rule sets, cannot be dropped.
-
Action: Do not drop an evaluation context with dependents without force option.
ORA-24153 rule set string.string already exists
-
Cause: A rule set of the given name already exists.
-
Action: Specify another name for the rule set being created.
ORA-24154 rule string.string already in rule set string.string
-
Cause: A rule can be added to a rule set only once.
-
Action: Do not add a rule to a rule set that already contains this rule.
ORA-24155 rule string.string not in rule set string.string
-
Cause: The rule to be removed from the rule set is not in the rule set.
-
Action: Do not remove a rule from a rule set that does not contain the rule.
ORA-24156 duplicate table alias string
-
Cause: There is a table alias of the same name in the evaluation context.
-
Action: Do not add two table aliases of the same name to an evaluation context.
ORA-24157 duplicate variable name string
-
Cause: There is a variable of the same name in the evaluation context.
-
Action: Do not add two variables of the same name to an evaluation context.
ORA-24158 invalid table alias
-
Cause: Table alias name or base table name is not specified in the table alias definition.
-
Action: Specify both alias name and alias base table in the table alias structure.
ORA-24159 invalid variable definition
-
Cause: Variable name or variable type is not specified in the variable definition.
-
Action: Specify both variable name and variable type in the variable definition structure.
ORA-24160 name string already exists in the name value pair list
-
Cause: There is already a name-value pair with the same name in the NVlist.
-
Action: Try another name.
ORA-24161 name string does not exist in the name value pair list
-
Cause: There is not such a name-value pair in the NVlist.
-
Action: Check that the name-value pair exists in the NVList.
ORA-24162 name value pair list is full, cannot add another entry
-
Cause: The NVList is full (1024 elements) and cannot hold more elements.
-
Action: Do not add elements to a full list.
ORA-24163 dblink is not supported in rules engine DDLs
-
Cause: The object name has a database link in it, which is not supported.
-
Action: Do not specify remote objects in rules engine DDLs.
ORA-24164 invalid rule engine system privilege: string
-
Cause: No such system privilege number for rule engine objects.
-
Action: Check specification of dbms_rule_adm for valid system privilege numbers.
ORA-24165 invalid rule engine object privilege: string
-
Cause: No such object privilege number for rule engine objects.
-
Action: Check specification of dbms_rule_adm for valid object privilege numbers.
ORA-24166 evaluation context string.string has errors
-
Cause: Cannot resolve the table aliases and the variable types specified in the evaluation context.
-
Action: Make sure all base tables exist and all variable types are correct.
-
Action: ORA-24167 incompatible rule engine objects, cannot downgrade
-
Cause: There are rule engine objects in the database that cannot be downgraded.
-
Action: Check utlincmp.sql and remove all incompatible rules engine objects before downgrading.
ORA-24168 rule string.string cannot have default evaluation context
-
Cause: If a rule is added to a rule set with more than one evaluation context, then it must not have an evaluation context itself.
-
Action: Do not set the evaluation context of such rules to a non-null value.
ORA-24169 rule condition has unrecognized variables
-
Cause: The rule references variables not in the evaluation context.
-
Action: Modify the rule condition to remove illegal reference.
ORA-24180 invalid transformation expression, the transformation expression does not evaluate to the target type/attribute
-
Cause: The transformation expression does not evaluate to the target type or the target type's specified attribute.
-
Action: Provide valid transformation expression which evaluates to the target type or the target type's specified attribute.
ORA-24181 The type string does not exist
-
Cause: The source or destination type for the transformation does not exist
-
Action: Create the type or specify one that exists.
ORA-24182 attribute number specified does not exist
-
Cause: The target type of the transformation does not have the attribute number specified in the ADD_ATTRIBUTE_TRANSFORMATION command.
-
Action: check the target type definition and specify a valid attribute number.
ORA-24183 invalid transformation
-
Cause: The transformation specified is invalid because the source or the target type have been dropped/modified.
-
Action: Drop and recreate the transformation.
ORA-24184 transformation string.string, already exists
-
Cause: A transformation of the given name already exists.
-
Action: Specify another name for the transformation being created.
ORA-24185 Transformation string.string, does not exist
-
Cause: The transformation being specified does not exist.
-
Action: Create the transformation before using it or specify an existing transformation.
ORA-24186 wrong object type, could not transform message
-
Cause: The object type of the message to be transformed does not match the source type of the specified transfomation.
-
Action: Specify another transformation or specify a message of the correct type.
ORA-24190 length of payload excceeds string
-
Cause: The length of payload being taken excceeds the limit of varchar2 or raw.
-
Action: Use clob type or blob type to call get_text or get_bytes.
ORA-24191 the property name string has existed
-
Cause: The property name being set has existed.
-
Action: Use another property name.
ORA-24192 the property name cannot be null
-
Cause: The property name cannot be null.
-
Action: Make sure the property name is not null.
ORA-24193 the property value exceeds the valid range string
-
Cause: The property values being set exceeds the valid range.
-
Action: Make sure the property value is within the valid range.
ORA-24201 duplicate publisher, publisher already added to the queue
-
Cause: Attempted to add a publisher to the queue again.
-
Action: Specify another publisher or use DBMS_AQADM.ALTER_PUBLISHER to alter the publisher's properties.
ORA-24202 publisher does not exist for the queue
-
Cause: Attempted to alter or drop a non existent publisher from a queue.
-
Action: Specify another publisher.
ORA-24270 a row already exists in the string table for these parameters
-
Cause: A call was made to create a new row in the specified table. A row already exists in the table with the specified values.
-
Action: Delete the existing row using the appropriate API or check the parameters used to create the row.
ORA-24271 translation type must be either T, S or M
-
Cause: The translation type parameter is not a T, S or an M. A value other than T, S or M was specified.
-
Action: Correct the translation type and re-execute the API call.
ORA-24272 initialization value must be either F or T
-
Cause: The initialization value must be either F or T. A value other than F or T was specified.
-
Action: Correct the initialization value and re-execute the API call.
ORA-24273 translation text is required if translation type is T or S
-
Cause: If a translation type of T or S is specified, translation text must be supplied.
-
Action: Provide translation text and re-execute the API call.
ORA-24274 no row exists in the string table for these parameters
-
Cause: A call was made to update a row that does not exist or a foreign key value supplied to create a table does not exist.
-
Action: Create the row using the appropriate API or check the parameters used to create the new row to ensure that all specified values exist.
ORA-24275 function 'string' parameter 'string' missing or invalid
-
Cause: The function pkgname.funcname was called with a parameter parmname that was null, 0 length, or had an invalid value.
-
Action: Correct the parameter to supply values that comply with its datatype and limits as specified in the documentation.
ORA-24276 function 'string' output 'string' maximum value exceeded
-
Cause: The function pkgname.funcname computed a value for the output parmname that exceeded the maximum allowed. This can occur when multiple input parameters, each valid separately, combine to specify an invalid result. For example, when a length parameter multiplied by a copies parameter yields a total length exceeding the maximum for the output datatype.
-
Action: Correct the input values to produce a result that will comply with the limits as specified in the documentation.
Oracle - PL/SQL 
을 누르고, 
메뉴를 선택한 다음
메뉴를 선택하시구요..... 
를 선택합니다. 
