PK jFJoa,mimetypeapplication/epub+zipPKjFJMETA-INF/container.xml PKYuPKjFJOEBPS/e19500.htm ORA-19500 to ORA-19976

14 ORA-19500 to ORA-19976

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", block number string (block size=string)
Cause: read error on input file
Action: check the file
ORA-19502: write error on file "string", block number string (block size=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, 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 if 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" (block size=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-19512: file search failed
Cause: Recovery manager or Oracle Server attempted to discover files that matched the specified pattern but failed.
Action: Check errors on the error stack for an explanation why the search for files could not be successfully executed.
ORA-19513: failed to identify sequential file
Cause: Unable to identify the sequential file.
Action: Check additional messages, and check if the file exists on media.
ORA-19525: tempfile for the clone database must be renamed
Cause: Opening a clone database failed because Oracle server forces the tempfile to be renamed, in order to avoid overwriting the primary tempfile.
Action: Rename the tempfiles manually or automatically by using the DB_FILE_NAME_CONVERT initialization parameter.
ORA-19526: only one location allowed for parameter string
Cause: A list of default locations was provided in an Oracle-managed files parameter.
Action: Edit the parameter to include a single location.
ORA-19527: physical standby redo log must be renamed
Cause: An attempt was made to clear redo log at a physical standby database. Clearing an OMF redo log will not work unless DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_LOG_DEST_n or DB_RECOVERY_FILE_DEST parameter is specified. Clearing a non-OMF (or user-defined) redo log file will not work unless the LOG_FILE_NAME_CONVERT initialization parameter is set.
Action: Set DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_LOG_DEST_n or DB_RECOVERY_FILE_DEST parameter for OMF redo log files and re-issue the operation that attempted to clear redo log. Set LOG_FILE_NAME_CONVERT parameter for non-OMF redo log files and re-issue the operation that attempted to clear redo log.
ORA-19528: redo logs being cleared may need access to files
Cause: The redo logs are being cleared. This procedure may need the files this operation is being applied to.
Action: Wait for the redo logs to be cleared.
ORA-19529: Pattern string in initialization parameter string has an Oracle Managed Files file name.
Cause: An attempt was made to convert a database file name to an Oracle Managed Files file name using DB_FILE_NAME_CONVERT or LOG_FILE_NAME_CONVERT initialization parameter. This was not a valid operation.
Action: Retry the operation with a pattern template instead of a full Oracle Managed Files file name.
ORA-19550: cannot use backup/restore functions while using dispatcher
Cause: Attempted to use backup/restore functions while connected to the dispatcher in a shared server. This is not allowed because the device that is used for backup and restore must remain allocated to a single process.
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 name
Cause: An invalid name of device limit was specified in a call to DBMS_BACKUP_RESTORE.SETLIMIT.
Action: Use one of the device limit names described in dbmsbkrs.sql
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 then retry the command.
ORA-19562: file string is empty
Cause: The indicated file, which is an archived log, control file, or datafile was found to be empty during a copy, backup, or scan] operation.
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, its header was not recognized as a valid file header for a file of the indicated type (datafile, archived log, or control file) belonging to the current database.
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: None. 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 control file
Cause: The input file specified for a copy or backup operation could not be opened because the record describing the file is not found in the control file.
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 file name 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: archived log record for string not found
Cause: No archived log record corresponding to input file could be found in the control file.
Action: Specify a valid archived 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: archived log file header validation for string failed
Cause: Archived log file header is corrupt and could not be validated.
Action: Provide a valid archived 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 for MAXPIECESIZE for this channel is not enough to hold the backup set control data.
Action: Allocate a channel specifying a larget valule for MAXPIECESIZE 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 control file
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: You tried 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-19591: backup aborted because job time exceeded duration time
Cause: You tried to backup with duration option and the time provided was not sufficient to complete the backup.
Action: Adjust the duration time and re-run the command. Or run the backup command without duration option.
ORA-19592: wrong string conversation type
Cause: You attempted to specify a type of file to be backed-up or restored, but the current conversation cannot process this type of file. For example, you specified an archived log to be included in a datafile backup set. The specified file will not be included in the backup or restore operation.
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: control file already included as string
Cause: The control file is already specified for inclusion in this backup or restore conversation. A backup or restore conversation may process only a single instance of the control file.
Action: No action required - the conversation is still active, and more files can be specified.
ORA-19595: archived log string already included in backup conversation
Cause: The indicated archived log has already been specified for inclusion in this backup conversation.
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 block size string does not match set block size of string
Cause: A file was specified for inclusion in a backup set but it has a logical block size different from the rest of the files in the backup set. All files in a backup set must have the same logical block size.
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 startup the instance.
Action: Create an SPFILE and re-start the instance using the SPFILE.
ORA-19599: block number string is corrupt in string string
Cause: A corrupt block was found in a control file, archived log, or backup piece that is being read for a backup or copy. Corruption shall not be tolerated in control files, archived logs, or backup pieces.
Action: None. 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 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: See other error message.
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: You tried to copy or backup a file that was not closed cleanly, and the database was in NOARCHIVELOG mode. This is not allowed because when restored, the file will require redo application before it is usable, and redo is not currently being saved beyond the contents of the online redo logs.
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 KEEP .. UNRECOVERABLE option. This is not allowed because when restored, the file will require redo application before it is usable, and redo will not be saved because of KEEP .. UNRECOVERABLE option.
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 file name 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 control file
Cause: A control file copy or restore operation specified the name of the snapshot control file as the output file. It is not permitted to overwrite the snapshot control file in this manner. Other methods are available to create the snapshot control file.
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 control file
Cause: A control file copy, restore, or backup specified the name of a control file named in the INIT.ORA file as the input or output file.
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 re-processed. If the failure cannot be resolved by re-processing 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: archived log thread string sequence string not found in backup set
Cause: The indicated archived log file was named explicitly for restoration but is not contained in this backup set.
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 file name must be specified if database not mounted
Cause: A datafile restore specified no target file name, but the database is not mounted. The database must be mounted when no target file name is specified, so that the target file name can be obtained from the control file.
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-19620: string is not of string type
Cause: When opening the file to be placed in a copy or backup set, to be inspected, or used as the target for an incremental restore, its header was not recognized as a valid file header for a file of the indicated type (datafile, archived log, or control file) belonging to the current database.
Action: The indicated file cannot be processed. Ensure that the correct files are being specified for the copy or backup operation.
ORA-19621: archived log range has already been specified
Cause: A range of logs has already been specified. Only one SCN range may be specified per conversation.
Action: The restore conversation remains active and more logs may be specified by thread and sequence number, if desired.
ORA-19622: archived log thread string sequence string not restored due to string
Cause: The indicated file could not be restored, because all of its data blocks were not found in the backup piece.
Action: The restore conversation remains active, and the current piece must be re-processed. If the failure cannot be resolved by re-processing 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 OS-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 control file application
Cause: This is a control file restore conversation, which is using the offline range information from one or more control files to update datafile checkpoint data. Backup sets are not used during this type of conversation.
Action: The conversation is still active and more control files may be applied.
ORA-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 archived log 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 OS 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: archived log record contains no file name
Cause: This archived log record represents a switch into an active log that took place without archiving its prior contents. The prior contents of the log file are lost.
Action: Specify the RECID of an archived 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 control file
Cause: The name passed to GETFNO was not found in the control file.
Action: Supply a valid file name.
ORA-19633: control file record string is out of sync with recovery catalog
Cause: The control file record describing the file to be deleted in a call to DELETEBACKUPPIECE, DELETEDATAFILECOPY, PROXYDELETE or DELETEARCHIVEDLOG does not match the validation data supplied by recovery manager.
Action: contact Oracle support
ORA-19634: file name 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 file names are identical: string
Cause: Identical input and output file names were specified for a datafile copy operation.
Action: Specify an output file name which is different from the input file name.
ORA-19636: archived log thread string sequence string already included
Cause: The indicated archived log has already been specified for inclusion in this restore conversation. A restore conversation may process only one copy of any archived log.
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: start SCN of incremental backup is string
Cause: This message identifies the starting SCN of an incremental backup that could not be applied.
Action: See other error message.
ORA-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: Restore needs to adjust the size of the file as indicated, but the file size adjustment failed.
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. NOTE that this message will usually only be encountered by the user while taking an incremental backup with Recovery Manager. Recovery Manager should intercept all usual cases of this error and simply ignore the incremental backup for this file. So, if you do encounter this error, please report it to Oracle Support.
ORA-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 control file to switch file incarnations
Cause: This SWITCHTOCOPY operation is attempting to switch incarnations of a datafile, but the currently mounted control file is not a backup control file.
Action: Restore and mount a backup control file.
ORA-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: None - 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: None - 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 control file
Cause: The control file was included in an incremental restore conversation
Action: If you wish to restore the control file, you must do a full restore of the control file
ORA-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 3rd-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.
ORA-19671: media management software returned invalid proxy handle
Cause: During a proxy backup or restore, the media management software returned an invalid file handle.
Action: This is an internal error in the media management software which is linked with Oracle to provide backup/restore services. 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.
Action: This is an internal error in the media management software which is linked with Oracle to provide backup/restore services. 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 on-line or otherwise modified while the proxy backup was in progress. This file was off-line or read-only when the backup began, so the file was not put into hot-backup mode, therefore no modifications are permitted while the backup is in progress.
Action: Take another backup of this file.
ORA-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 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 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 are 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 specified in block media recovery
Action: check file number
ORA-19682: file string not in block media recovery context
Cause: Internal error
Action: None
ORA-19683: real and backup block size of file string are unequal
Cause: block size changed between backup & real file
Action: use right 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-19685: SPFILE could not be verified
Cause: Some data blocks for the SPFILE were corrupt in the backup set.
Action: Unless the damage to the backup set can be repaired, the SPFILE cannot be restored from this backup set.
ORA-19686: SPFILE not restored due to string
Cause: The indicated file could not be restored, because some of its data blocks were not found in the backup piece.
Action: Unless the damage to the backup set can be repaired, the SPFILE cannot be restored from this backup set.
ORA-19687: SPFILE not found in backup set
Cause: The SPFILE could not be restored, because it is not 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 in the piece. You must supply the first backup piece of a backup set that contains the requested file.
ORA-19688: control file AUTOBACKUP format(string) for string does not have %F
Cause: control file AUTOBACKUP format must contain %F for the device.
Action: Change control file format using RMAN command CONFIGURE CONTROLFILE BACKUP FORMAT FOR DEVICE TYPE <type> TO <format>.
ORA-19689: cannot have more than one %F in control file AUTOBACKUP format(string) for string
Cause: control file AUTOBACKUP format contains more than one %F for the device.
Action: Change control file format using RMAN command CONFIGURE CONTROLFILE BACKUP FORMAT FOR DEVICE TYPE <type> TO <format>.
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-19691: string is from different database: id=string, name=string
Cause: The database name or database id in backup piece header does not match the one in control file.
Action: Supply the correct backup piece belonging to this database.
ORA-19692: missing creation stamp on piece string
Cause: The backup piece doesn't have information about creation stamp.
Action: Supply another backup piece which is created by oracle 9i or later version.
ORA-19693: backup piece string already included
Cause: This backup piece was already specified for inclusion in the restore conversation. A restore conversation may process only a single instance of a backup piece.
Action: Remove the specified duplicate backup piece in restore steps and restart the conversation.
ORA-19694: some changed blocks were not found in the change tracking file
Cause: A backup or copy found that some changed blocks had not been recorded in the change tracking file. The details of which files and blocks are affected will be in an Oracle trace file.
Action: This indicates that there is a problem with the change tracking feature. Disable change tracking and re-start the backup.
ORA-19695: fixed table X$KRBMSFT has not been populated
Cause: This is an internal error. The fixed table X$KRBMAFT was not populated using the function DBMS_BACKUP_RESTORE.SEARCHFILES.
Action: Internal error - contact Oracle Customer Support.
ORA-19696: control file not found in backup set
Cause: The control file could not be restored because it is not in this backup set.
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 in the piece. You must supply the first backup piece of a backup set that contains the requested file.
ORA-19697: standby control file not found in backup set
Cause: The standby control file could not be restored because it is not in this backup set.
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 in the piece. You must supply the first backup piece of a backup set that contains the requested file.
ORA-19698: string is from different database: id=string, db_name=string
Cause: Catalog failed because the database id in file header does not match the one in control file.
Action: Supply the correct file belonging to this database.
ORA-19699: cannot make copies with compression enabled
Cause: Datafile copies with compression are not supported.
Action: If the function DBMS_BACKUP_RESTORE.BACKUPPIECECREATE is called outside RMAN, then the incompatible values are being passed for the parameters DOCOMPRESS and IMAGCP. If this message occurs during an RMAN job, then this is an internal error in RMAN, and you should contact Oracle support.
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-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 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 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 maximum limit.
Action: Report the error and other information to support.
ORA-19714: length for generated 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 string for generated name
Cause: A restricted format or undefined format was used incorrectly.
Action: Change the format specified in the additional information by removing the restricted format.
ORA-19716: error processing format string to generate name for backup
Cause: There were errors while processing the format to generate name for backup.
Action: Change the format.
ORA-19717: for non-OMF search the pattern must be specified
Cause: The procedure DBMS_BACKUP_RESTORE.SEARCHFILES was called with an empty pattern while the parameter OMF was set to FALSE.
Action: Either specify the pattern or set the parameter OMF to TRUE.
ORA-19718: length for command id longer than string
Cause: The specified command id exceeds the maximum length for command id.
Action: Supply a shorter command id and retry the operation.
ORA-19719: length for operation name longer than string
Cause: The specified operation name exceeds the maximum length for operation name.
Action: Supply a shorter operation name and retry the operation.
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: Can not find one of the datafile 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 can not recreated.
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 "compatible" init.ora 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 can not exchange the table with the partition in this case.
Action: Use "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: Online the datafile 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: d 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 startup 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-19738: cannot find language information for character set: 'string'
Cause: The compatibility check failed because a character set name that was provided is not valid.
Action: Correct the character set name and retry.
ORA-19740: text is longer than string
Cause: The specified text exceeds the maximum length for text.
Action: Supply a shorter text and retry the operation.
ORA-19741: string exceeds maximum allowable length of string for parameter 'string'
Cause: The specified string exceeds the maximum allowable length for the parameter
Action: Supply a shorter string for the parameter and retry the operation.
ORA-19742: control file is not a backup control file
Cause: This parameter could not be set because the control file was not a backup control file.
Action: Do not use this call for this control file.
ORA-19750: change tracking file: 'string'
Cause: This message reports the name of a file involved in other messages.
Action: See associated error messages for a description of the problem.
ORA-19751: could not create the change tracking file
Cause: It was not possible to create the change tracking file.
Action: Check that there is sufficient disk space and no conflicts in file names and try to enable block change tracking again.
ORA-19752: block change tracking is already enabled
Cause: The ALTER DATABASE ENABLE BLOCK CHANGE TRACKING command was issued, but block change tracking is already turned on for this database.
Action: None, this is an informative message only.
ORA-19753: error writing to change tracking file
Cause: An I/O error occurred while writing to the change tracking file.
Action: There will be other messages on the error stack that show details of the problem.
ORA-19754: error reading from change tracking file
Cause: An I/O error occurred while reading from the change tracking file.
Action: There will be other messages on the error stack that show details of the problem.
ORA-19755: could not open change tracking file
Cause: The change tracking file could not be opened.
Action: There will be other messages on the error stack that show details of the problem.
ORA-19756: corrupt block number string found in change tracking file
Cause: The specified block number is corrupt in the change tracking file.
Action: There will be other messages on the error stack that show details of the problem. There will also be a trace file that contains a complete dump of the corrupt block.
ORA-19757: could not resize change tracking file to string blocks
Cause: An error occurred while trying to change the size of the change tracking file.
Action: There will be other messages on the error stack that show details of the problem.
ORA-19758: failed to enable/disable block change tracking: out of SGA memory
Cause: out of SGA memory
Action: Increase SGA and restart the instance.
ORA-19759: block change tracking is not enabled
Cause: A command was entered that requires block change tracking to be enabled, but block change tracking is not enabled.
Action: None, this is an informative message only.
ORA-19760: error starting change tracking
Cause: Change tracking is enabled, but a problem was encountered while enabling the change tracking subsystem in this instance. The alert log and the trace file from the CTWR process will contain more information about the error.
Action: Examine the trace and alert files. Correct the error if possible, otherwise disable change tracking.
ORA-19761: block size string is not valid for change tracking file
Cause: While opening the specified change tracking file, it was found that the file header did not contain a valid logical block size. This probably means that the file is corrupt.
Action: If the file can be repaired, do so, otherwise disable and re-enable change tracking to re-initialize the file.
ORA-19762: invalid file type string
Cause: An invalid file type was found in the change tracking file. Some other file was put in place of the change tracking file, or the file is corrupt.
Action: Disable then re-enable change tracking.
ORA-19763: compatibility version string is higher than maximum allowed: string
Cause: The compatibility version in the change tracking file is greater than what can be used by the current release of Oracle. This can happen when you upgrade, use change tracking with a new release, then downgrade.
Action: Disable then re-enable change tracking.
ORA-19764: database id string does not match database id string in control file
Cause: The change tracking file is not the correct one for this database. This can happen when the database ID for this database has been changed.
Action: Disable then re-enable change tracking.
ORA-19765: mount id string does not match mount id string in control file
Cause: d by having a change tracking file that cannot be consistently updated by all instances.
Action: In RAC, ensure that the name specified for the change tracking file truly represents the same disk location for all nodes in the cluster. Disable then re-enable change tracking.
ORA-19766: missing CHANGE keyword
Cause: Syntax error.
Action: Use the correct syntax: ENABLE/DISABLE BLOCK CHANGE TRACKING
ORA-19767: missing TRACKING keyword
Cause: Syntax error.
Action: Use the correct syntax: ENABLE/DISABLE BLOCK CHANGE TRACKING
ORA-19768: USING clause only valid with ENABLE CHANGE TRACKING
Cause: The USING clause was specified with DISABLE CHANGE TRACKING
Action: Correct the statement.
ORA-19769: missing FILE keyword
Cause: Syntax error.
Action: Use the correct syntax: ENABLE/DISABLE BLOCK CHANGE TRACKING
ORA-19770: invalid change tracking file name
Cause: The USING clause was specified with ALTER DATABASE ENABLE BLOCK CHANGE TRACKING, but no file name was given.
Action: Specify the change tracking file name, or omit the USING clause to allow Oracle to create a default name for the change tracking file.
ORA-19771: cannot rename change tracking file while database is open
Cause: The ALTER DATABASE RENAME FILE command was used to rename the change tracking file, and the database is open by one or more instances. The database must be mounted, and not open, to rename the change tracking file.
Action: Close the database and reissue the command.
ORA-19772: change tracking file name exceeds limit of string characters
Cause: The name specified for the change tracking file is too long.
Action: Specify a shorter change tracking file name.
ORA-19773: must specify change tracking file name
Cause: No file name was specified with the ALTER DATABASE ENABLE CHANGE TRACKING command, and the DB_CREATE_FILE_DEST parameter was not set.
Action: Either specify a file name, or set the DB_CREATE_FILE_DEST parameter.
ORA-19776: PROXY restore to ASM disk group "string" is not supported.
Cause: An attempt was made to proxy restore a file to ASM disk group using RMAN command. This is not supported.
Action: Use a different file name and reissue RMAN command.
ORA-19777: ASM file string cannot be proxy backed up.
Cause: An attempt was made to proxy backup a ASM file. This is not supported.
Action: Use a different file name and reissue RMAN command.
ORA-19779: could not obtain resilvering status for change tracking file
Cause: An error occurred while obtaining the mirror resilvering status of the change tracking file.
Action: Refer to other error messages shown for additional details of the problem.
ORA-19780: Active Data Guard option not enabled
Cause: Change tracking at a standby database required the Active Data Guard option.
Action: Enable the Active Data Guard option.
ORA-19800: Unable to initialize Oracle Managed Destination
Cause: The name given for an Oracle managed files destination cannot be initialized.
Action: , if possible, and retry the command or use a different name for destination.
ORA-19801: initialization parameter DB_RECOVERY_FILE_DEST is not set
Cause: An attempt was made to create a file in DB_RECOVERY_FILE_DEST when DB_RECOVERY_FILE_DEST was not set. There are number of possible causes of this error, including: 1) A LOG_ARCHIVE_DEST_n parameter was specified using a LOCATION attribute whose value was DB_RECOVERY_FILE_DEST and an archived log file creation was attempted. 2) STANDBY_ARCHIVE_DEST parameter was specified using a LOCATION attribute whose value was DB_RECOVERY_FILE_DEST and an archived log file creation was attempted.
Action: Specify a valid destination for DB_RECOVERY_FILE_DEST in initialization parameter file or with the ALTER SYSTEM SET command.
ORA-19802: cannot use DB_RECOVERY_FILE_DEST without DB_RECOVERY_FILE_DEST_SIZE
Cause: There are two possible cause for this error: 1) The DB_RECOVERY_FILE_DEST parameter was in use when no DB_RECOVERY_FILE_DEST_SIZE parameter was encountered while fetching initialization parameter. 2) An attempt was made to set DB_RECOVERY_FILE_DEST with the ALTER SYSTEM command when no DB_RECOVERY_FILE_DEST_SIZE was in use.
Action: Correct the dependency parameter definitions and retry the command.
ORA-19803: Parameter DB_RECOVERY_FILE_DEST_SIZE is out of range (1 - string)
Cause: Parameter DB_RECOVERY_FILE_DEST_SIZE specified was not valid.
Action: Specify a valid number within the range.
ORA-19804: cannot reclaim string bytes disk space from string limit
Cause: Oracle cannot reclaim disk space of specified bytes from the DB_RECOVERY_FILE_DEST_SIZE limit.
Action: There are five possible solutions: 1) Take frequent backup of recovery area using RMAN. 2) Consider changing RMAN retention policy. 3) Consider changing RMAN archived log deletion policy. 4) Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE. 5) Delete files from recovery area using RMAN.
ORA-19805: RECID string of string was deleted to reclaim disk space
Cause: The file described by the record in control file was deleted in order to reclaim disk space from recovery area for other operations.
Action: Wait and try again.
ORA-19806: cannot make duplex backups in recovery area
Cause: Duplex backup to recovery area is not supported.
Action: Remove duplex option and try again.
ORA-19808: recovery destination parameter mismatch
Cause: The value of parameters DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE must be same in all instances. instance. All databases must have same recovery destination parameters.
Action: Check DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE values in all instances.
ORA-19809: limit exceeded for recovery files
Cause: The limit for recovery files specified by the DB_RECOVERY_FILE_DEST_SIZE was exceeded.
Action: There are five possible solutions: 1) Take frequent backup of recovery area using RMAN. 2) Consider changing RMAN retention policy. 3) Consider changing RMAN archived log deletion policy. 4) Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE. 5) Delete files from recovery area using RMAN.
ORA-19810: Cannot create temporary control file string in DB_RECOVERY_FILE_DEST
Cause: An attempt was made to create a control file for a temporary purpose in DB_RECOVERY_FILE_DEST.
Action: Retry the operation with a new file name.
ORA-19811: cannot have files in DB_RECOVERY_FILE_DEST with keep attributes
Cause: An attempt was made to 1) Create a backup piece or image copy in the recovery area with KEEP option. 2) Update the KEEP attributes of an existing backup piece or image copy in the recovery area.
Action: Reissue RMAN command without KEEP options.
ORA-19812: cannot use string without DB_RECOVERY_FILE_DEST
Cause: There are three possible cause for this error: 1) The indicated parameter was in use when no DB_RECOVERY_FILE_DEST parameter was encountered while fetching the initialization parameter. 2) An attempt was made to set indicated the parameter with the ALTER SYSTEM command when no DB_RECOVERY_FILE_DEST was in use. 3) An attempt was made to clear DB_RECOVERY_FILE_DEST with the ALTER SYSTEM command when the indicated parameter was in use.
Action: Eliminate any incompatible parameter definitions.
ORA-19813: cannot have unavailable file string in DB_RECOVERY_FILE_DEST
Cause: An attempt was made to change a backup piece or image copy in recovery area to UNAVAILABLE.
Action: Correct and resubmit the RMAN command. Do not use messages 19814; it is used for simulating crash.
ORA-19815: WARNING: string of string bytes is string% used, and has string remaining bytes available.
Cause: DB_RECOVERY_FILE_DEST is running out of disk space.
Action: One of the following:

1. Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE.

2. Backup files to tertiary device using RMAN.

3. Consider changing RMAN retention policy.

4. Consider changing RMAN archived log deletion policy.

5. Delete files from recovery area using RMAN.

ORA-19816: WARNING: Files may exist in string that are not known to database.
Cause: One of the following events caused this:

1. A database crash happened during file creation.

2. A backup control file was restored.

3. The control file was re-created.

4. DB_RECOVERY_FILE_DEST has previously been enabled and then disabled.

Action: Use RMAN command CATALOG RECOVERY AREA to re-catalog any such files. If the file header is corrupted, then delete those files using an OS utility. Do not use messages 19817; it is used for simulating lock failure Do not use messages 19818; it is used for space reclamation before backup Do not use messages 19819; it is used to disable clearing file name
ORA-19820: database must be in NOARCHIVELOG mode to disable logging
Cause: Logging was disabled when ARCHIVELOG mode was used.
Action: Execute ALTER DATABASE NOARCHIVELOG in mount state.
ORA-19821: an intentionally corrupt log file was found
Cause: A log file that was intentionally corrupt for testing or benchmarking purposes was found and failed the operation.
Action: Remove such log files and retry or use the NOARCHIVELOG option if possible.
ORA-19830: error from target database: string
Cause: This error should be followed by other errors indicating the cause of the problem.
Action: No action required.
ORA-19831: incompatible string.string.string.string DBMS_BACKUP_RESTORE package: string.string.string.string required
Cause: This version of database was incompatible with the the indicated DBMS_BACKUP_RESTORE package installed in the database.
Action: If the database has been upgraded from an earlier version, ensure that the catxxxx.sql script has been run successfully. Re-install dbmsbkrs.sql and prvtbkrs.plb if necessary.
ORA-19836: cannot use passphrase encryption for this backup
Cause: Passphrase encryption was attempted for a backup that contains encrypted tablespaces and uses compression.
Action: Do not use passphrase encryption for this backup. Use transparent wallet-based encryption instead.
ORA-19837: invalid blocksize string in backup piece header
Cause: The blocksize of the backup piece obtained from the header was invalid.
Action: The backup piece is corrupted, a different backup piece should be used for restore.
ORA-19838: Cannot use this control file to open database
Cause: This control file was restored by a DUPLICATE operation used only to restore and recover the datafiles of the new database. It is not meant to be used for opening the database, as allowing so might corrupt datafiles or online redo logs of the target database or both.
Action: Re-create control file manually specifying all names of datafiles and online redo logs. Do not forget to use NID to change the name or DBID or both of the new database.
ORA-19843: Cannot obtain datafile name for datafile string
Cause: While trying to obtain the file enqueue for the datafile the datafile name could not be obtained.
Action: Examine the trace and alert files for possible causes. Fix underlying problem before attempting command again.
ORA-19851: OS error while managing auxiliary database string
Cause: An OS error was received while managing the automatic auxiliary instance.
Action: Check the accompanying errors.
ORA-19852: error creating services for auxiliary instance string (error string)
Cause: An error was received while managing the services of the auxiliary instance.
Action: Check the accompanying errors.
ORA-19853: error preparing auxiliary instance string (error string)
Cause: An error was received while managing the automatic auxiliary instance.
Action: Check the accompanying errors.
ORA-19854: error obtaining connect string from target
Cause: Could not obtain the connect string from the target database
Action: Check the accompanying errors.
ORA-19860: piece validation cannot be performed more than once
Cause: The user attempted to validate a list of backup pieces more than once. Validation may only be performed once for a given validation conversation.
Action: Do not attempt to validate the pieces more than once.
ORA-19861: additional backup pieces cannot be validated in this conversation
Cause: The user tried to add new pieces to the list of files being validated after the validation had already been performed. In a validation conversation, the list can only be validated once.
Action: Add all the backup pieces to the list before validating, or start a new validation conversation for the remaining pieces.
ORA-19862: backup pieces must be validated before accessing results
Cause: The user tried to get validation results for backup pieces before the pieces were actually validated.
Action: Validate the pieces before trying to access the results.
ORA-19863: device block size string is larger than max allowed: string
Cause: The user specified a device BLKSIZE that is larger than the device BLKSIZE specified during compressed backup.
Action: Change the device BLKSIZE to be smaller than the maximum allowed.
ORA-19865: Backup piece string has no data
Cause: No data was returned for the specified backup piece.
Action: This normally indicates a problem with the media management software which is linked with Oracle to provide backup and restore services. Contact the media management software vendor.
ORA-19866: error writing file header for datafile string
Cause: During a block recovery, the header of the datafile could not be updated.
Action: Contact Oracle Support Services.
ORA-19870: error while restoring backup piece string
Cause: This error should be followed by other errors indicating the cause of the problem.
Action: See other errors actions.
ORA-19872: Unexpected end of file at block string while decompressing backup piece string
Cause: While reading a compressed backup piece, RMAN received an end-of-file without finding the end-of-compression stream.
Action: This is most likely caused by a corrupted backup piece. Consider using a different backup piece for restore.
ORA-19873: cannot apply this backup section to file string
Cause: RMAN cannot restore a multi-section backup to the indicated file, because this section is not a backup of this file, or the file was not prepared correctly for this restore.
Action: If this error occurs while running RMAN, then it is an internal error and you should contact Oracle support.
ORA-19874: cannot finish multi-section restore to file string
Cause: During a multi-section restore, the file being restored is not a file in which a multi-section restore is in progress.
Action: If this error occurs while running RMAN, then it is an internal error and you should contact Oracle support.
ORA-19875: multi-section restore not complete for file string
Cause: While completing a multi-section restore, it was found that all required sections for this file were not correctly applied.
Action: If this error occurs while running RMAN, then it is an internal error and you should contact Oracle support.
ORA-19880: Corrupted space header for datafile string, block string
Cause: When reading the space header block to use Unused Block Optimization for the backup of the datafile, the space header block had corrupted information.
Action: The corrupt space header must be fixed before Unused Block Optimization can be used for this file. Note that you should fix the corruption in any case because it will affect the availability of the data in the file, beyond just taking backups.
ORA-19881: Corrupted space bitmap for datafile string, block string
Cause: When reading a space bitmap block to use Unused Block Optimization for the backup of the datafile, the space bitmap block had corrupted information.
Action: The corrupt space bitmap must be fixed before Unused Block Optimization can be used for this file. Note that you should fix the corruption in any case because it will affect the availability of the data in the file, beyond just taking backups.
ORA-19882: datafile string checkpoint string is ahead of space bitmap datafile string checkpoint string
Cause: When checkpointing the datafile containing the space bitmaps for the datafile being backed up in order to use Unused Block Optimization, the checkpoint of the datafile containing the space bitmaps did not advance.
Action: Examine the trace and alert files for possible causes. Fix underlying problem to use Unused Block Optimization for datafile's backup.
ORA-19883: Unused Block Optimization stopped for datafile string
Cause: Accompanying errors detail the problem that prevented Unused Block Optimization from being used.
Action: See accompanying errors for appropiate action.
ORA-19884: datafile string is unable to use Unused Block Optimization because tablespace has been dropped
Cause: When attempting to find information about datafile that holds bitmaps of migrated tablespace, the tablespace was found to have been dropped.
Action: None. This is an informational message.
ORA-19899: missing incarnation information
Cause: Media recovery stopped because information of one or more ancestor incarnations of recovery target incarnation was not available.
Action: Register logs from the missing incarnations and retry recovery.
ORA-19900: RESETLOGS must be specified after recovery to new incarnation
Cause: Recovery was done to an incarnation after changing the destination incarnation using RMAN's RESET DATABASE command.
Action: Open the database with the RESETLOGS option.
ORA-19901: database needs more recovery to create new incarnation
Cause: Recovery was done to an incarnation after changing the destination incarnation using RMAN's RESET DATABASE command, but one or more of the recovered datafiles still belongs to the parent incarnation. This usually happens when recovery is ended before any logs from the desired incarnation have been applied.
Action: Continue recovery.
ORA-19902: incarnation key string not found
Cause: The specified incarnation was not found in the control file.
Action: Resubmit request with known incarnation key. To see which incarnations are available for this target database, query V$DATABASE_INCARNATION or use RMAN's LIST INCARNATION command.
ORA-19903: test recovery not allowed when recovering to new incarnation
Cause: Either a new incarnation was set using RMAN's RESET DATABASE command for a control file that was CURRENT, or the control file is from a prior incarnation. As recovery to a new incarnation requires changing the control file, test recovery is not allowed.
Action: Perform actual recovery or RESET DATABASE to incarnation that was last opened using the control file to do test recovery.
ORA-19904: test recovery not allowed for datafile string
Cause: The specified datafile has been restored from a backup that was taken before the last RESETLOGS. Recovering this datafile will require a file header update that is incompatible with test recovery.
Action: Perform actual recovery.
ORA-19905: log_archive_format must contain %s, %t and %r
Cause: log_archive_format is missing a mandatory format element. Starting with Oracle 10i, archived log file names must contain each of the elements %s(sequence), %t(thread), and %r(RESETLOGS ID) to ensure that all archived log file names are unique.
Action: Add the missing format elements to log_archive_format.
ORA-19906: recovery target incarnation changed during recovery
Cause: While a media recovery was active, a new incarnation was detected by the server due to inspection or cataloging of archived logs or backup files.
Action: If you want recovery to use the new incarnation, restart recovery. This is the most common action on a standby database when RESETLOGS is done in primary. If you do not want recovery to use the new incarnation, change the recovery destination using RMAN's RESET DATABASE TO INCARNATION <incarnation#> command. To see which incarnations are available for this target database, query V$DATABASE_INCARNATION or use RMAN's LIST INCARNATION command.
ORA-19907: recovery time or SCN does not belong to recovered incarnation
Cause: A point-in-time recovery to an SCN or time stamp prior to the last RESETLOGS was requested.
Action: Either change the specified recovery time/SCN, or change the recovery destination using RMAN's RESET DATABASE command.
ORA-19908: datafile string has invalid checkpoint
Cause: The specified datafile has an invalid checkpoint.
Action: Restore the datafile from a backup.
ORA-19909: datafile string belongs to an orphan incarnation
Cause: Either the specified datafile was restored from a backup that was taken during a period of time that has already been discarded by a RESETLOGS operation, or Oracle cannot identify which database incarnation the file belongs to. The alert log contains more information.
Action: Restore a backup of this file that belongs to either the current or a prior incarnation of the database. If you are using RMAN to restore, RMAN will automatically select a correct backup.
ORA-19910: can not change recovery target incarnation in control file
Cause: The RESET DATABASE TO INCARNATION command was used while the database is open. This is not allowed.
Action: Close the database then re-issue the command.
ORA-19911: datafile string contains future changes at the incarnation boundary
Cause: The file did not hit end backup marker redo during recovery at the incarnation boundary, hence may contain changes discarded by new incarnation.
Action: Use older backup of the file and then re-issue the command.
ORA-19912: cannot recover to target incarnation string
Cause: The control file is not in the recovery path of the target incarnation, and does not contain enough information as to how to recover to the target incarnation.
Action: Restore the latest control file from the target incarnation and retry.
ORA-19913: unable to decrypt backup
Cause: A backup piece could not be decrypted. This message is accompanied with another message that indicates the name of the encrypted backup that could not be restored. The reason could be either that an invalid password was entered, or that, when using transparent decryption, the database external security device is not open.
Action: If password-based restore was enabled for this backup, then supply the correct password using the RMAN SET DECRYPTION command. If transparent restore was enabled for this backup, then ensure that the database external security device is open.
ORA-19914: unable to encrypt backup
Cause: RMAN could not create an encrypted backup. This message will be accompanied by other messages that give more details about why the encrypted backup could not be created. The most common reason for this message is that you are trying to create a backup that can be transparently decrypted, and the database external security device is not open.
Action: If the external security device is not open, then open it. If the external security device is not configured, then the only type of encrypted backup that you can create is a password-based backup.
ORA-19915: unable to encrypt pre-10.2 files
Cause: An RMAN encrypted backup was requested, but this backup includes one or more archived logs that were generated by an older release of Oracle. These archived logs cannot be encrypted.
Action: Back up the older logs without encryption. Logs created with Oracle release 10.2 and greater can be encrypted.
ORA-19916: string
Cause: An error occurred when processing user request.
Action: Do not use message 19917; it is used internally for testing purpose. Do not use message 19918; it is an internal event used by encryption.
ORA-19919: encrypted backups to tertiary storage require Oracle Secure Backup
Cause: RMAN was configured to create encrypted backups, but the channel is neither a DISK channel nor an Oracle Secure Backup channel.
Action: Allocate a DISK channel or an Oracle Secure Backup channel to use backup encryption.
ORA-19920: RMAN does not support PKI-based master key for encryption.
Cause: An attempt was made to use Oracle public key infrastructure (PKI) based master key algorithm. RMAN only supports Advanced Encryption Standard (AES) based encryption.
Action: Use AES based encryption.
ORA-19921: maximum number of string rows exceeded
Cause: The maximum number of rows in the V$RMAN_STATUS or V$RMAN_OUTPUT table has been exceeded.
Action: Close some of existing and unused RMAN connections and sessions.
ORA-19922: there is no parent row with id string and level string
Cause: RMAN tried to add a new V$RMAN_STATUS row, but the parent row did not exist.
Action: This is an internal error. Contact Oracle Support.
ORA-19923: the session for row with id string is not active
Cause: RMAN tried to update an V$RMAN_STATUS row but the process which owns this row died.
Action: This is an internal error. Contact Oracle Support.
ORA-19924: there are no row with id string
Cause: RMAN tried to update an V$RMAN_STATUS row, but the row don't exist.
Action: This is an internal error. Contact Oracle Support.
ORA-19926: Database cannot be converted at this time
Cause: Another CONVERT DATABASE operation is already in progress.
Action: Retry CONVERT DATABASE command later.
ORA-19927: CONVERT DATABASE operation cannot proceed
Cause: An error occurred earlier during CONVERT DATABASE operation.
Action: Retry CONVERT DATABASE command.
ORA-19928: CONVERT of data files with undo segments between different endian is not supported.
Cause: Conversion of data files with undo segments was not supported between endianess. The only time that data files with undo segments can be converted is between the same endianess as part of convert database. Convert database between different endian is not supported.
Action: Do not attempt to convert data files with undo segments between different endian.
ORA-19930: file string has invalid checkpoint SCN string
Cause: When opening the file to be placed in a copy or backup set, to be inspected, the file header was not recognized as a valid header because it contained a invalid checkpoint SCN. The indicated file cannot be processed.
Action: Ensure that the correct files are being specified for the catalog or backup operation.
ORA-19931: file string has invalid creation SCN string
Cause: When opening the file to be placed in a copy or backup set, to be inspected, the file header was not recognized as a valid header because it contained a invalid creation SCN. The indicated file cannot be processed.
Action: Ensure that the correct files are being specified for the catalog or backup operation.
ORA-19932: control file is not clone, standby or backup
Cause: The operation failed because the control file was not mounted as clone, standby or backup.
Action: Mount the database as clone, standby or backup and retry.
ORA-19941: invalid blocksize in cross platform datafile string
Cause: Blocksize in header of datafile copy being converted at target was invalid. Either datafile has not been made read/write with compatibility 10.0 or greater at source database or datafile copy is corrupted.
Action: Make a new datafile copy taken after tablespace has been made read/write with compatibility 10.0 at source database and retry conversion.
ORA-19942: datafile copy string not created with compatibility 10.0 or greater
Cause: The specified datafile copy to be converted at the target was not produced after making the tablespace in read/write mode with compatibility 10.0 or greater at the source database.
Action: Make a new datafile copy taken after tablespace has been made read/write with compatibility 10.0 at source database and retry conversion.
ORA-19943: The current database incarnation changed during backup
Cause: The backup failed because the current database incarnation was changed during the backup. One of the following events caused this incarnation change:

- The database was opened using ALTER DATABASE OPEN RESETLOGS statement.

- RMAN command RESET DATABASE TO INCARNATION was issued.

- If this happened on physical standby database, then redo apply has applied redo data from a new database incarnation.

Action: Re-try the backup.
ORA-19951: cannot modify control file until DBNEWID is completed
Cause: An operation requiring to modify the control file was attempted, but a NID change is in progress.
Action: Wait until NID completes before attempting the operation.
ORA-19952: database should be mounted exclusively
Cause: The database was started in parallel mode. To change the DBID, the database must be mounted exclusively.
Action: Shut down the database and start it in exclusive mode.
ORA-19953: database should not be open
Cause: The database was open. To change the DBID, the database must be mounted exclusively.
Action: Shut down the database and mount it in exclusive mode.
ORA-19954: control file is not current
Cause: The operation failed because a non-current, non-standby control file was mounted.
Action: Make the control file current and retry.
ORA-19955: only one open thread is allowed to change the DBID
Cause: The operation failed because there were active threads in the database. The most likely cause is that the database crashed the last time it was shut down.
Action: Ensure that all threads are closed before retrying the operation. Start and open the database to perform crash recovery, then shut down with the NORMAL or IMMEDIATE options to close it cleanly. Finally, try running the utility again.
ORA-19956: database should have no offline immediate datafiles
Cause: The operation failed because the database had one or more datafiles that were in OFFLINE IMMEDIATE mode.
Action: Drop the datafiles or recover them and bring them online.
ORA-19957: database should have no datafiles in unknown state
Cause: The operation failed because the database had one or more datafiles that were in an unknown state.
Action: Drop the datafiles or recover them and bring them online.
ORA-19958: potential deadlock involving DIAG process
Cause: DIAG requested a control file operation that may lead to a deadlock
Action: Try last operation later when the control file is released
ORA-19960: Internal use only
Cause: NID usage
Action: None
ORA-19961: compression algorithm string requires advanced compression option to be enabled
Cause: Requested compression algorithm in initialization parameter or by RMAN configuration requires that the advanced compression option be enabled and it was not.
Action: Change initialization parameter advanced_compression_option_usable to true or change RMAN configurations and retry the operation.
ORA-19962: compression algorithm string is not valid with release string
Cause: Algorithm in initialization parameter requires a lower compatibility that is currently set.
Action: Change algorithm in initialization parameter file or lower compatibility.
ORA-19963: error getting logical block size of file string
Cause: Error occurred when querying the logical block size of a file.
Action: None
ORA-19965: ALTER DATABASE RECOVER STANDBY TABLESPACE has been deprecated
Cause: The STANDBY TABLESPACE clause of the ALTER DATABASE RECOVER statement (partial_database_recovery clause) has been deprecated.
Action: If you want to recover the standby database to a consistent point, but no further, use the statement ALTER DATABASE RECOVER MANAGED STANDBY DATABASE UNTIL CONSISTENT.
ORA-19966: ALTER DATABASE RECOVER STANDBY DATAFILE has been deprecated
Cause: The STANDBY DATAFILE clause of the ALTER DATABASE RECOVER statement (partial_database_recovery clause) has been deprecated.
Action: If you want to recover the standby database to a consistent point, but no further, use the statement ALTER DATABASE RECOVER MANAGED STANDBY DATABASE UNTIL CONSISTENT.
ORA-19970: multi-instance standby role transition in progress
Cause: ALTER DATABASE MOUNT failed because a multi-instance standby role transition was in progress.
Action: Retry after the multi-instance standby role transition finishes.
ORA-19971: event 10875 or 10879 is set
Cause: Event 10875 or event 10879 was set which prevented the operation from completing with multiple instances running in Oracle RAC.
Action: Shutdown all but one instance, then retry the command.
ORA-19972: ALTER DATABASE RECOVER TO LOGICAL requires one instance left
Cause: ALTER DATABASE RECOVER TO LOGICAL required only one instance to be left running.
Action: Shutdown all but one instance, then retry the command.
ORA-19973: flashback database is not enabled
Cause: Physical standby transition to snapshot standby required only one instance left running if flashback database logging was not enabled.
Action: Shutdown all but one instance, then retry the command.
ORA-19974: database name has changed
Cause: Physical standby role transition required only one instance left running if database name was changed and flashback database logging was enabled.
Action: Shutdown all but one instance, then retry the command.
ORA-19975: database must not be started in any other instance
Cause: The physical standby role transition command failed because a certain condition required the database to be mounted in this instance and not started in any other instance.
Action: See associated error message for detailed explanation.
ORA-19976: a concurrent standby role transition in progress
Cause: The zstandby role transition operation failed because a concurrent standby role transition was already in progress.
Action: None
PKA6PKjFJOEBPS/prccmsg.htmh1 PRCC-01000 to PRCC-01020

81 PRCC-01000 to PRCC-01020

PRCC-01000: Parameter {0} value is not valid
Cause: This is an internal error. The value for the specified parameter is null or empty string.
Action: Contact Oracle Support Services.
PRCC-01001: Failed to retrieve install group: {0}
Cause: An attempt to retrieve the install group failed.
Action: Examine the accompanying error messages for details.
PRCC-01002: Failed to update install group: {0}
Cause: An attempt to set the install group failed.
Action: Examine the accompanying error messages for details.
PRCC-01003: Version for module {0} is not available
Cause: An attempt to retrieve the version information for specified module failed.
Action: Examine the accompanying error messages for details.
PRCC-01004: Unknown identifier {0} specified for checking result of operation
Cause: Failed to retrieve the result from the exception data using the specified identifier because the exception did not have the specified identifier.
Action: This is an internal error. Contact Oracle Support Services.
PRCC-01005: Parameter {0} is not an absolute path
Cause: The specified parameter is not an absolute directory path.
Action: Provide an absolute directory path.
PRCC-01006: Path {0} is not a directory
Cause: The specified path is not a directory.
Action: Provide a directory path.
PRCC-01007: Path {0} does not exist
Cause: The specified path did not exist.
Action: Provide an existing directory path.
PRCC-01008: Enumerated type {0} does not have a member with corresponding value of {1}
Cause: This is an internal error.
Action: Contact Oracle Support Services.
PRCC-01009: Parameter {0} cannot have null as a value
Cause: This is an internal error.
Action: Contact Oracle Support Services.
PRCC-01010: {0} was already enabled
Cause: Given entity was already enabled.
Action: No action needed. To re-enable the entity, first disable it and then retry.
PRCC-01011: {0} was already enabled on {1}
Cause: Given entity was already enabled on given nodes.
Action: No action needed. To re-enable the entity on given nodes, first disable it on these nodes and then retry.
PRCC-01012: {0} was already disabled
Cause: Given entity was already disabled.
Action: No action needed. To re-disable the entity, first enable it and then retry.
PRCC-01013: {0} was already disabled on {1}
Cause: Given entity was already disabled on given nodes.
Action: No action needed.
PRCC-01014: {0} was already running
Cause: Given entity is already running.
Action: No action needed. To re-start the entity, first stop it and then retry.
PRCC-01015: {0} was already running on {1}
Cause: Given entity was already running on given nodes.
Action: No action needed. To re-start the entity on given nodes, first stop it on these nodes and then retry.
PRCC-01016: {0} was already stopped
Cause: Given entity was already stopped.
Action: No action needed. To re-stop the entity, first start it and then retry.
PRCC-01017: {0} was already stopped on {1}
Cause: Given entity was already stopped on given nodes.
Action: No action needed. To re-stop the entity on given nodes, first start it on these nodes and then retry.
PRCC-01018: A request to retrieve private network addresses for node {0} found no addresses
Cause: A request to retrieve private network addresses by executing 'olsnodes -p' returned no private IP addresses.
Action: Check 'oifcfg getif' for cluster_interconnect networks and ensure this node has an IP address on the cluster_interconnect networks.
PRCC-01019: Parameter "{0}" value is not valid
Cause: This is an internal error.
Action: Contact Oracle Support Services.
PRCC-01020: Version {0} cannot be used to administer resource configuration of version {1} or later
Cause: This is an internal error.
Action: Contact Oracle Support Services.
PKw(Gm1h1PKjFJOEBPS/gipcus.htmb GIPC-00000 to GIPC-00020

66 GIPC-00000 to GIPC-00020

GIPC-00000: general success.
Cause: The operation succeeded.
Action: No action is required.
GIPC-00001: general failure.
Cause: A GIPC operation failed.
Action: Examine the trace and log files for the specific cause.
GIPC-00002: GIPC needs to be initialized.
Cause: The application failed to initialize GIPC prior to performing an operation.
Action: Initialize GIPC.
GIPC-00014: buffer not large enough to hold data.
Cause: The buffer provided by the application was not big enough to hold the data received.
Action: Use a larger buffer.
GIPC-00016: timeout waiting on request.
Cause: A wait call returned because the time expired.
Action: This error happens normally in most cases. If this error was not expected, examine the trace and log files for the reason.
GIPC-00017: waiting call has been posted.
Cause: A wait was interrupted by another thread posting it.
Action: This error happens normally in most cases. If this error was not expected, examine the trace and log files for the reason.
GIPC-00020: bind address already in use.
Cause: The application attempt to bind an endpoint to an address which has already been bound.
Action: Specify another address.
PK/.gbPKjFJOEBPS/kupus.htm KUP-00552 to KUP-11024

36 KUP-00552 to KUP-11024

KUP-00552: internal XAD package failed to load
Cause: An error was encountered while attempting to initialize the XAD package.
Action: This message should be accompanied by other error message(s) indicating the cause of the error.
KUP-00554: error encountered while parsing access parameters
Cause: The parser detected a syntax error.
Action: This message should be accompanied by other error message(s) indicating the cause of the error.
KUP-00561: invalid length for binary integer field string
Cause: An integer field was specified with an invalid length. The only supported lengths for binary integer fields are 1, 2, 4, and 8.
Action: None
KUP-00562: unknown escape sequence
Cause: An unknown escape sequence was specified to the parser. An escape sequence is a backslash followed by a character.
Action: Consult documentation for list of allowable control characters.
KUP-00600: internal error, arguments [string] [string] [string] [string] [string]
Cause: An internal XAD error occurred.
Action: Contact Oracle Support.
KUP-00601: fatal XAD error
Cause: A fatal error has occurred.
Action: This message should be accompanied by other error message(s) indicating the cause of the error.
KUP-01006: error signalled during parse of access parameters
Cause: An error was signalled during parsing of the access parameters.
Action: This message should be accompanied by other error message(s) indicating the cause of the error.
KUP-01007: at line number column number
Cause: This is an informational message indicating the line and column where a syntax error was detected.
Action: None
KUP-01008: the bad identifier was: string
Cause: This is an informational message indicating the identifier token that caused a syntax error.
Action: None
KUP-02000: wrong message file version (msg number not found)
Cause: The kupxx.msb file is not the correct version.
Action: Check that the installation was done correctly.
KUP-02001: unrecognized punctuation symbol "string"
Cause: An illegal punctuation character was encountered.
Action: Remove the illegal character.
KUP-02002: unexpected end of input file reached
Cause: This is probably caused by failure to supply the closing quote for a quoted string.
Action: Correct the input.
KUP-02003: unrecognized character: string
Cause: An input character that is neither an alpha, digit, or punctuation was encountered.
Action: Remove the character.
KUP-02004: quoted string too big
Cause: A quoted string longer than 2000 bytes was encountered.
Action: This may be caused by a missing close quote. If so, add the missing quote, otherwise shorten the string.
KUP-02005: token too big
Cause: A token longer than 1000 bytes was encountered
Action: Tokens must be separated by whitespace or punctuation. Either add the missing whitespace or punctuation, or shorten the token.
KUP-02006: script line too long
Cause: a line longer than 500 bytes was encountered
Action: break the line up into shorter lines
KUP-03001: fatal error during library cache pre-loading
Cause: This message should be accompanied by other error message(s) indicating the cause of the error.
Action: Check the accompanying errors.
KUP-03002: end position (number) <= start position (number) for field: string
Cause: Error in specifying position for the specified field in the access parameters."
Action: Check that the specified end position is greater than the specified start position.
KUP-03003: absolute end(number) - start(number) != fieldlength (number) for field string
Cause: The number of bytes occupied by the field as specified by the starting offset and ending offset of the field is not the same as the number of bytes specified for the datatype of the field.
Action: Verify the absolute begin/end position(s) specified match the length of the field.
KUP-03004: absolute end (number) specified with relative start (number) for field string
Cause: The position of field was specified with a relative start and an absolute end.
Action: Use relative end with relative start
KUP-03005: relative end (number) specified does not match fieldlen(number) for field string
Cause: The number of bytes specified by the relative end position for the field does not match the number of bytes in the datatype.
Action: Correct either the datatype length or the relative end position.
KUP-03006: error initializing handle for character set string
Cause: Error attempting to retrieve information for the character set.
Action: Verify that the character set name is valid.
KUP-03007: end position (number) is less than start position (number) for range
Cause: A byte range specified a start position that comes after the end position.
Action: Verify the start and end positions are correctly specified.
KUP-03008: OCI error getting column parameters.
Cause: An error occurred while trying to obtain column parameters.
Action: Contact Oracle Support.
KUP-03009: OCI error getting column name.
Cause: An error occurred while trying to obtain column name.
Action: Contact Oracle Support.
KUP-03010: OCI error getting database column type.
Cause: An error occurred while trying to obtain database column type.
Action: Contact Oracle Support.
KUP-03011: OCI error getting database column size.
Cause: An error occurred while trying to obtain database column size.
Action: Contact Oracle Support.
KUP-03012: OCI error getting database column precision.
Cause: An error occurred while trying to obtain database column precision.
Action: Contact Oracle Support.
KUP-03013: OCI error getting database column scale.
Cause: An error occurred while trying to obtain database column scale.
Action: Contact Oracle Support.
KUP-03014: OCI error getting datetime fsprecision.
Cause: An error occurred while trying to obtain a datetime column precision value."
Action: Contact Oracle Support.
KUP-03015: OCI error getting datetime lfprecision.
Cause: An error occurred while trying to obtain database column precision.
Action: Contact Oracle Support.
KUP-03016: length specified for FIXED records must be greater than 0
Cause: A record format of FIXED was specified with a length of 0.
Action: None
KUP-03017: length specified for VARIABLE records must be greater than 0
Cause: A record format of VARIABLE was specified with a length of 0.
Action: None
KUP-03018: invalid date mask "string" specified for column string
Cause: The date mask for the specified column is invalid.
Action: None
KUP-03019: directory object not specified in LOBFILE clause for field string
Cause: A LOBFILE clause was specified for the field, but no directory object was specified. When no directory object is specified, then the default directory specified for the external table is used, but no default directory was specified.
Action: Specify a directory object in the LOBFILE clause or specify a default directory for the external table.
KUP-03020: empty delimiter specified for record
Cause: An empty delimiter string was specified for a record delimiter.
Action: Specify the string used to delimiter records.
KUP-03021: clause references unknown field string
Cause: A WHEN, NULLIF or DEFAULTIF clause referenced a field that doesn't exist in the data file.
Action: None
KUP-03022: lob data could not be found for field string
Cause: The field specified in the data source that contains the name of the lob file for the record could not be identified.
Action: None
KUP-03023: string for TERMINATED BY or ENCLOSED BY clause for record is longer than maximum number
Cause: The string value for a TERMINATED BY or ENCLOSED BY clause is longer than the maximum number of bytes allowed. If the character set of the data file is different than the character set of the database, the string will be converted to the character set of the data file. If the length of the converted string is too large, then this error will also be returned.
Action: Use shorter delimiters in the data file and the access parameters.
KUP-03024: string for TERMINATED BY or ENCLOSED BY clause for column string is longer than maximum number
Cause: The string value for a TERMINATED BY or ENCLOSED BY clause for the columns is longer than the maximum number of bytes allowed. If the character set of the data file is different than the character set of the database, the string will be converted to the character set of the data file. If the length of the converted string is too large, then this error will also be returned.
Action: Use shorter delimiters in the data file and the access parameters.
KUP-03998: error number formatting KUP message number
Cause: error occured while attempting to format a KUP message.
Action: contact Oracle support.
KUP-03999: error occurred while processing a date format: ORA-number: string
Cause: Error converting a date format string into an internal representation.
Action: Verify that the date format strings specified in the access parameters are valid.
KUP-04000: error initializing IO state for file string in string
Cause: An unexpected error occurred while preparing the file.
Action: Contact Oracle support.
KUP-04001: error opening file string
Cause: An error occurred while attempting to open the specified file. This message should be followed by another message with more information about the error.
Action: See the error that follows to determine the action to be taken.
KUP-04002: error getting file size for file string
Cause: An error occurred while retrieving the number of bytes in the specified file.
Action: See the error that follows to determine the action to be taken.
KUP-04003: error while closing file string
Cause: An error occurred while closing the specified file.
Action: See the error that follows to determine the action to be taken.
KUP-04004: error while reading file string
Cause: An error occurred while reading the specified file.
Action: See the error that follows to determine the action to be taken.
KUP-04005: file operation successful
Cause: A file oepration succeeded.
Action: None
KUP-04006: file operation failed
Cause: An operation on a file failed. The file is named in the message preceeding this one.
Action: See subsequent message for more information about the error.
KUP-04007: end of file reached
Cause: The end of file was reached for a file. The file is named in the message preceding this one.
Action: See the message that follows this one for more information.
KUP-04008: access to file denied
Cause: Acess to a file was denied. The file is named in the message preceding this one.
Action: See the message that follows for more information. Verify that the correct files are being used and that the appropriate access is allowed to those files.
KUP-04009: invalid SLF handle
Cause: An internal error caused a data structure associated with the file to become corrupt.
Action: Contact Oracle support.
KUP-04010: file does not exist
Cause: A file operation failed because a file does not exist. The message preceding this message contains the name of the file.
Action: Verify that the correct file name was specified.
KUP-04011: file system is full
Cause: An operation on a file failed because the file system is full. The message preceding this one contains the name of the file.
Action: Free space on the file system or move the file to a different file system.
KUP-04012: file length is too large for output field
Cause: Size of a file is too large.
Action: Break the file up into smaller files.
KUP-04013: other system error
Cause: Internal component SLF was unable to complete an operation because of a system error.
Action: The message displayed before this message describes the operation that was being performed when the error occurred.
KUP-04014: invalid SLF parameter
Cause: An invalid parameter was passed in a call to internal component SLF.
Action: Contact Oracle support.
KUP-04015: internal SLF error
Cause: Internal component SLF encountered an internal error.
Action: Contact Oracle support.
KUP-04016: unknown SLF status code number
Cause: Internal component SLF returned an unknown error code.
Action: Contact Oracle support.
KUP-04017: OS message: string
Cause: An error occurred. This message contains the message associated with this error that was returned by the operating system. The message displayed before this one should indicate the operation that failed.
Action: None
KUP-04018: partial record at end of file string
Cause: An incomplete record was found at the end of the file.
Action: Verify the file is not corrupt or missing data.
KUP-04019: illegal length found for VAR record in file string
Cause: A record in a VAR file has an length field with either no numeric characters in it or with non numeric characters in it.
Action: Verify the records in the file have the correct length specified for them.
KUP-04020: found record longer than buffer size supported, number, in string
Cause: a record in the data source was longer than the maximum data size supported. The number reported is the maximum supported size of a record.
Action: None
KUP-04021: field formatting error for field string
Cause: There was an error trying to find the contents of the specified field in a record.
Action: This message should be followed by another message containing more specific information about the cause of the error.
KUP-04022: field start is before start of record
Cause: The position of the start of a field is before the start of a record. This can occur if a negative number is used to indicate the relative start of a field.
Action: Verify that the definition of the layout of fields in the data file is correct.
KUP-04023: field start is after end of record
Cause: This can happen when specifying either absolute or relative positioning for a field.
Action: Verify that the definition of the layout of fields in the data file is correct. If it is valid for fields at the end of the record to be missing, use the MISSING FIELD VALUES ARE NULL clause in the access parameters.
KUP-04024: field end is before field start
Cause: The end of the field comes after the start of the field. This can happen if the field is defined with a relative start position and an absolute end position.
Action: Verify that the definition of the layout of fields in the data file is correct.
KUP-04025: field extends beyond end of record
Cause: This can happen when specifying either absolute or relative positioning for a field.
Action: Verify that the definition of the layout of fields in the data file is correct.
KUP-04026: field too long for datatype
Cause: The character field in the record is larger than the maximum length specified.
Action: Make sure the definition of the layout of the fields in the data file is correct. Also make sure the correct maximum size was specified for a character datatype.
KUP-04027: file name check failed: string
Cause: The check of the filename failed. These checks are platform specific, but they can include verifying that there are no hard links in the file path, the file is not a soft link, the file specification includes a parent reference ("../" on Unix), or the file was modified between the time the check was made and the file was opened.
Action: Use a file location that does not violate any of the checks.
KUP-04028: conversion of character length to a number failed
Cause: The character length portion of the field could not be converted to a number. This message is followed by another message with information on why the conversion failed.
Action: Make sure the data is correct. Also verify the datatypes specified for the fields are correct.
KUP-04029: numeric field overflowed
Cause: An attempt to convert a character string to number failed because the value of the number in the string was too large.
Action: None
KUP-04030: invalid numeric data
Cause: An attempt to convert a character string to a number failed because non-numeric characters were found.
Action: None
KUP-04031: empty filename specified for LOB file in column string
Cause: The field in the data file that was supposed to contain the name of a LOB file was empty.
Action: Correct the data so that it contains a valid file name.
KUP-04032: internal error string while parsing field string:
Cause: An internal error occurred while parsing a field.
Action: Contact Oracle support.
KUP-04035: beginning enclosing delimiter not found
Cause: The beginning enclosure was not found for a field that is enclosed by delimiters.
Action: Verify that the data is correct. Also verify that the correct enclosing delimiters were specified and whether the enclosing delimiter should be optional.
KUP-04037: terminator not found
Cause: The terminator for the field is missing.
Action: Verify that the records are formatted correctly.
KUP-04038: internal error: string
Cause: an unexpected error condition was detected.
Action: contact Oracle customer support
KUP-04039: unexpected error while trying to find file string in string
Cause: An error occurred while trying to find path containing the file.
Action: This message should be followed by another message with more information about the error.
KUP-04040: file string in string not found
Cause: The file was not found in the directory specified
Action: Verify the correct file and directory names were specified.
KUP-04041: error generating full file name for string in string
Cause: Unexpected error occurred while trying to form a file name.
Action: None
KUP-04043: table column not found in external source: string
Cause: A column in the external table was not found in the access parameters that define the contents of the data source
Action: Verify that the external table is defined correctly and that the abstract parameters are also correct.
KUP-04044: error positioning file string
Cause: An attempt to position a file to an absolute file offset failed.
Action: See messages that follow for more information.
KUP-04045: unexpected OCI status string
Cause: An OCI call returned a status that cannot be handled.
Action: Contact Oracle support.
KUP-04047: error parsing record from external data source
Cause: An error occurred while trying to extract a record from the data source.
Action: Look in the log file for more messages about the error.
KUP-04048: internal error parsing record from external data source
Cause: An unexpected or unhandled error occurred while getting a record from the data source
Action: Contact Oracle support.
KUP-04049: record number discarded from file string
Cause: Informational message displayed whenever the WHEN clause has been satisfied. If a DISCARD file has been specified for the operation, the record will be written to that file.
Action: None
KUP-04050: error while attempting to allocate number bytes of memory
Cause: d by insufficient memory.
Action: Reconnect to the instance and retry the operation.
KUP-04051: error processing column string in row number for datafile string
Cause: an error occurred while trying to convert the data from the data file into the type of a column in the external table.
Action: See messages that follow for more details.
KUP-04052: error processing column string in a row for datafile string
Cause: an error occurred while trying to convert the data from the data file into the type of a column in the external table.
Action: See messages that follow for more details.
KUP-04053: record number number
Cause: This message identifies a record number in a file for a record that had an error. The message preceding this one contains information about the error and the name of the file.
Action: None
KUP-04054: internal error: invalid bad row number identified for bad column number
Cause: This is an internal error.
Action: Contact Oracle support.
KUP-04055: column string is both a field in the data file and a column transform
Cause: The specified column was in the list of fields in the data file and in the list of column transforms. The column should be in one list or the other, but not both.
Action: Determine whether the value for the field in the data file or the value for the field in the column transform should be loaded in to the table. If the value for the data file is to be loaded, then remove the column transform. If the value for the column transform is to be loaded, then rename the field in the data file so that it does not match the name of a field in the table.
KUP-04056: internal error: OCI error while fetching record: number
Cause: An OCI error occurred while processing the granule.
Action: Contact Oracle support.
KUP-04057: internal error: OCI error while fetching record.
Cause: An OCI error occurred while processing the granule.
Action: Contact Oracle support.
KUP-04058: unrecoverable error occurred, operation aborted.
Cause: An unrecoverable error occurred during processing.
Action: See preceding error messages for more information.
KUP-04059: found EOF in length portion of VARIABLE record in file string
Cause: The record parser was looking for the size portion of a file a record format of VARIABLE. It found EOF before finding all the bytes for the length.
Action: Correct the corruption in the file.
KUP-04060: field string referenced by lobfile column string not found
Cause: The LOBFILE transform for the named column referenced a field for either the directory object portion or the name portion of the LOBFILE. However, that field did not exist anywhere in the definition of the data file.
Action: Verify that the LOBFILE clause is specified correctly. Also verify that the field definitions for the data file are correct.
KUP-04061: directory object string specified for LOBFILE column string is not valid
Cause: The column being loaded from a LOBFILE specified the directory object containing the LOBFILE through another field in the data file. In this case, the LOBFILE clause in the access parameters must specify a list of all directory objects that will be used for this field. This error occurs because a field contains the name of a directory object that is not in this list.
Action: Verify that the data file contains the correct directory object and verify that the list of valid directory objects in the LOBFILE clause for this column is complete.
KUP-04062: no data source specified
Cause: No location for the data source of the external table was specified when the external table was created. An empty string is not valid.
Action: Specify the name of the data source in the LOCATION clause when creating an external table.
KUP-04063: unable to open log file string OS error string
Cause: An attempt to open the log file failed.
Action: Specify a different log file or use NO LOGFILE to disable logging.
KUP-04064: fatal error during initialization
Cause: An unexpected error occurred while initializing access to an external table.
Action: Contact Oracle support.
KUP-04065: error processing LOBFILE for field string
Cause: An error occured while opening or reading a LOBFILE for a column in a row.
Action: See message in log file for more information about the error.
KUP-04066: error initializing access to external table source
Cause: An error occurred while attempting to retrieve information about a data source.
Action: See messages preceding this one for more information about the error.
KUP-04067: internal error allocating handle type string
Cause: An attempt to create an internal object failed.
Action: Contact Oracle support.
KUP-04068: internal error fetching attribute string
Cause: An attempt to fetch information about an internal object failed.
Action: Contact Oracle support.
KUP-04069: error fetching data for external table
Cause: An error occurred while atempting to fetch data from an external table.
Action: See messages the precede this one for more information.
KUP-04070: field string referenced by column transform string not found
Cause: The column transform for the named column references a field that did not exist anywhere in the definition of the data file.
Action: Verify that the column transform clause is specified correctly. Also verify that the field definitions for the data file are correct.
KUP-04071: record discarded from file string
Cause: Informational message displayed whenever the WHEN clause has been satisfied. If a DISCARD file has been specified for the operation, the record will be written to that file. The record number in the source data file is not known because multiple servers are loading from the file.
Action: None
KUP-04072: error writing to file string
Cause: An error occurred while attempting to write to the named file.
Action: See messages that follow this message for more information about the error.
KUP-04073: record ignored because all referenced fields are null for a record
Cause: A record was rejected because all fields in the data file referenced by the query were NULL.
Action: None
KUP-04074: no write access to directory object string
Cause: The user does not have write access to the directory object used for a log, bad or reject file.
Action: None
KUP-04075: no read access to directory object string
Cause: The user does not have read access to the directory object used for a data file.
Action: None
KUP-04076: file name cannot contain a path specification: string
Cause: The name of a data file, log file, bad file or reject file contains a path specification.
Action: Use the name of a directory object to indicate where the file should be stored.
KUP-04077: unknown format specifier in file name string
Cause: A format specifier is a percent sign followed by a character. The percent sign and character are replaced by a value depending on the character. This error occurs when the character following the percent sign is not defined to have a value.
Action: See the documentation for information on valid format specifiers. If the file to be opened needs to have a percent sign in its name then use two pecent signs. They will get replaces by a single percent sign in the resulting file name.
KUP-04078: invalid file name specified: string
Cause: Attempt to parse the file name failed.
Action: Specify a valid file name.
KUP-04079: error fetching list of valid directories
Cause: An attempt to retrieve a list of valid directories that can be used by the user to open files failed. See messages that follow for more information.
Action: Contact Oracle support. As a workaround try specifing no log file, no discard files and no bad files.
KUP-04080: directory object string not found
Cause: The directory object specified for an input file or a log, bad or discard file does not exist in the database or the user has no privileges to access this directory.
Action: None
KUP-04081: field string used in concatenation for column string is not a character type
Cause: The specified field was part of a concatenation of strings used to create the value for the names column. However, the field was not of a character datatype. Only character fields may be used as part of concatenating fields.
Action: Verify the correct field was used in the CONCAT clause. Also verify that the correct datatype is specified for the field in the field list.
KUP-04082: error converting field string for LOBFILE column string
Cause: The LOBFILE column had either its directory object name or filename specified by a field in the data file and that field needed to be converted to the server's character set before it could be used. This message indicates that an attempt to convert the field failed.
Action: Verify that the data file has the correct value for the fields. Also verify that the correct character set was specified for the data file.
KUP-04083: no directory object specified in LOBFILE clause for column string
Cause: There was no directory object specified for the LOB files used to populate the named column and no default directory was specified for the external table.
Action: Either specify a directory name, or the name of a data field containing the name of the directory object that contains the files.
KUP-04084: The ORACLE_DATAPUMP access driver does not support the ROWID column.
Cause: A query of an external table of type ORACLE_DATAPUMP tried to reference the ROWID column. The ORACLE_DATAPUMP access driver does not support ROWIDs.
Action: Remove the ROWID from the query. If that is not possible, create a table in the database with the same columns as the external table, copy the data from the external table into the newly created table, and use that new table for the query.
KUP-04085: duplicate directory object string and file string specified for unload
Cause: A CREATE TABLE AS SELECT statement was executed for an external table of type ORACLE_DATAPUMP and the same directory object and filename combination was specified multiple times.
Action: Issue the CREATE TABLE AS SELECT command again but make sure the combination of directory objects and filenames is unique.
KUP-04086: length of file name exceeds platform maximum of number
Cause: The length of a filename is longer than the maximum length supported by Oracle on the server platform.
Action: Verify that the name is correct. If so, use a shorter file name.
KUP-04087: no execute access to directory object string
Cause: Execute access to the directory object used for a preprocessor file was not granted.
Action: Grant execute privilege on the directory object or specify a different directory which already has execute privilege enabled.
KUP-04088: data sampling is not supported by this access driver
Cause: A query of an external table requested a sample of the data returned. The access driver for the external table does not support sampling.
Action: Do not try to use sampling for this external table.
KUP-04089: column transform string is not the name of a table column
Cause: The specified column was in the list of column transforms but a column by that name does not exist in the table
Action: Verify that the correct name was specified in the column transform.
KUP-04090: big endian byte order mark found when little endian expected in string
Cause: A big endian byte order mark was found at the beginning of the specified file and either the access parameters specified the data was in little endian order or the byte order mark for a previous file was little endian.
Action: The file needs to be loaded separately. If a byte order was specified in the access parameters, make sure it is changed to be big endian.
KUP-04091: little endian byte order mark found when big endian expected in string
Cause: A little endian byte order mark was found at the beginning of the specified file and either the access parameters specified the data was in big endian order or the byte order mark for a previous file was big endian.
Action: The file needs to be loaded separately. If a byte order was specified in the access parameters, make sure it is changed to be little endian.
KUP-04092: attempt to audit directory object string returned internal error number
Cause: An error occurred while attempting to enable auditing for the specified directory object.
Action: Contact Oracle Support Services.
KUP-04094: preprocessing cannot be performed if Database Vault is installed
Cause: The Database Vault option did not permit the execution a program from an Oracle directory object.
Action: If preprocessing must be performed, then the Database Vault option must not be installed.
KUP-04095: preprocessor command string encountered error "string"
Cause: The specified preprocessor command encountered an error during execution.
Action: Verify that the preprocessor command along with any arguments are correct.
KUP-04097: RECORDS clause specified without a record format
Cause: The RECORDS clause was part of the external table access parameters but no record format type was provided.
Action: If the RECORDS clause is used, then it must be followed by one of the VARIABLE, FIXED, or DELIMITED BY clauses.
KUP-04100: record rejected in file string
Cause: A record in the data file was not loaded into the table because of an error while finding fields in the record. See the previous error for more information. The record will be written to the BAD file, if one is being used. The record number in the source data file is not known because multiple servers are loading from the file.
Action: None
KUP-04101: record number rejected in file string
Cause: A record in the data file was not loaded into the table because of an error while finding fields in the record. See the previous error for more information. The record will be written to the BAD file, if one is being used.
Action: None
KUP-04102: record number discarded from file string
Cause: Informational message displayed whenever the WHEN clause has been satisfied. If a DISCARD file has been specified for the operation, the record will be written to that file.
Action: None
KUP-04103: error converting zoned decimal field to number for string
Cause: An error occurred converting a zoned decimal number to an Oracle number.
Action: Verify that the zoned decimal number is formatted correctly.
KUP-04104: zoned decimal field has bad values for string
Cause: A zoned decimal number has an invalid format.
Action: Verify that the zoned decimal number is formatted correctly.
KUP-04105: zoned decimal to number conversion caused overflow for string
Cause: A zoned decimal number could not be converted to an Oracle number because the number is too big for an oracle number.
Action: Verify that the zoned decimal number is formatted correctly.
KUP-04106: precision for zoned decimal number is too large for string
Cause: The precision of a zoned decimal number is larger than the precision that can be stored in an Oracle number.
Action: Verify that the zoned decimal number is formatted correctly.
KUP-04108: unable to reread file string
Cause: The query that is executing requires that a data source for an external table be read multiple times. However, the data source is a sequential device that cannot be reread. Examples of this type of data source is a tape or pipe.
Action: There are a few ways around this problem. One is to rewrite the query so that the external table is referenced only once. Another option is to move the data source to a rereadable device such as a disk file. A third option is to load the data for the external table into a temporary table and change the query to reference the temporary table.
KUP-04109: specified path for directory object "string" is invalid
Cause: The default directory or a directory object specified for an input data file or an output dump, log, bad or discard file contains an invalid path name.
Action: Specify a valid path name for the directory object.
KUP-05004: Warning: Intra source concurrency disabled because parallel select was not requested.
Cause: Intra source concurrency can only be used when parallel select has been requested.
Action: No action is required this message is informational.
KUP-05005: Warning: Intra source concurrency disabled because a field of type RECNUM exists.
Cause: Intra source concurrency cannot be used with RECNUM fields.
Action: No action is required this message is informational.
KUP-05006: Warning: Intra source concurrency disabled because a complex terminator string is being used.
Cause: Intra source concurrency cannot be used with terminators where replicated substrings in the terminator could cause ambiguity during record parsing.\n\n"
Action: No action is required this message is informational.
KUP-05007: Warning: Intra source concurrency disabled because the preprocessor option is being used.
Cause: Intra source concurrency cannot be used with the PREPROCESSOR option.
Action: No action is required this message is informational.
KUP-05008: Warning: Intra source concurrency disabled because the input data is in DELIMITED record format and the characterset is neither fixed width nor UTF8.
Cause: Intra source concurrency cannot be used with the DELIMITED record format if the characterset is neither fixed width or UTF8.
Action: No action is required this message is informational.
KUP-05009: Warning: Intra source concurrency disabled because the input data is in VARIABLE record format.
Cause: Intra source concurrency cannot be used with the VARIABLE record format.
Action: No action is required this message is informational.
KUP-11000: file truncated error
Cause: A truncated file was used for the load operation.
Action: Verify unload operation completed successfully.
KUP-11001: files not from the same unload operation
Cause: Files used for the load operation were not from the same unload operation.
Action: Verify the files used are from the same unload operation.
KUP-11002: unable to read data chunk string
Cause: A read or seek to this data chunk was not possible. This chunk may not have existed.
Action: Verify the files used for the load operation are correct.
KUP-11003: bad data encountered while reading from file string
Cause: There was a datatype conversion error while attempting to convert the data in the data file to match the datatype of a column in the external table. The message that follows this one displays the name of the column and the start of the data for the column that could not be converted. The row containing the bad data is rejected and not included as a row in the external table.
Action: If the row containing the bad data should not be filtered out, then modify the definition of the external table so that the datatypes of the columns match the datatypes of the fields in the data file.
KUP-11004: requested version string not supported by ORACLE_DATAPUMP
Cause: This database version (defaulted to COMPATIBLE if not user-specified) was not supported by ORACLE_DATAPUMP external table access driver. Note: Database versions before 9.2 were not supported.
Action: Specify a supported version and rerun the operation.
KUP-11005: error seeking in file: string
Cause:3o An attempt to seek to the specified position in file failed.
Action: Review the error message. Resolve the problem and retry the the operation. Contact Oracle Support Services if the problem cannot be resolved.
KUP-11006: file truncated error in string
Cause: A truncated or incomplete file was used for the load operation.
Action: Verify unload operation completed successfully.
KUP-11007: conversion error loading table string.string
Cause: A row could not be loaded into the table because there was a conversion error for one or more columns in a row.
Action: See the message that follows for more information about the row that could not be loaded. To avoid this error, make sure the definition of the table being loaded matches the definition of the table being unloaded.
KUP-11008: conversion error loading table string.string partition string
Cause: A row could not be loaded into the table because there was a conversion error for one or more columns in a row.
Action: See the message that follows for more information about the row that could not be loaded. To avoid this error, make sure the definition of the table being loaded matches the definition of the table being unloaded.
KUP-11009: data for row: string
Cause: A conversion error occurred while loading data into a table. The message shows values for the field in the row that had the conversion error.
Action: None. This is only an informational message.
KUP-11010: unable to open at least one dump file for fetch
Cause: None of the files in the LOCATION clause can be opened for a fetch on an external table.
Action: A fetch operation on an external table in SQL mode requires that at least one file could be opened. Check that the directory object and file names to the dump files are correct.
KUP-11011: the following file is not valid for this load operation
Cause: This file could not be used for this load operation. See the following message for more information.
Action: Verify all the files in the LOCATION clause are from the same unload operation and that the unload was successful.
KUP-11012: file string in string already exists
Cause: The specified file could not be used for this unload because that would mean overwriting an existing file.
Action: Specify a file that does not currently exist.
KUP-11013: internal number in header in file string is not valid
Cause: The specified file could not be used for this operation because the internal number in the header was not valid.
Action: If the dump files were transferred over, verify the transfer operation was done correctly.
KUP-11014: internal metadata in file string is not valid
Cause: The specified file could not be used for this operation because the internal metadata stored in this file does not match the metadata stored in the first file piece set.
Action: Verify all the files in the LOCATION clause are the correct dump files to use.
KUP-11015: error in unloading or loading data
Cause: An error has occurred in a stream unload or load operation.
Action: Contact Oracle Support Services.
KUP-11016: database version in file string is not valid
Cause: The specified file could not be used for this fetch because its database version was not compatible with the database version in the other files in the LOCATION clause.
Action: Verify all the files in the LOCATION clause were populated with compatible database versions.
KUP-11017: file string not found
Cause: The file was not found.
Action: Verify the correct file (path and file name) was specified.
KUP-11018: file string not a valid dump file
Cause: This file did not have the correct file format. It could not be used for an external table fetch operation.
Action: Verify this file is from a SQL mode external table populate operation and that the operation was successful.
KUP-11019: the following file is not valid for this fetch operation
Cause: A file could not be used for this fetch. See the following message for more information.
Action: Verify all the files in the LOCATION clause are from successful populate operations. If the files were generated from various populate operations, then verify that those were done with common attributes such as with the same tables and compatible database versions.
KUP-11020: header in file string may not contain correct information
Cause: The header may be corrupted.
Action: Contact Oracle Support Servicess.
KUP-11021: header in file string has an incompatible version number
Cause: A dump file was specified for a load operation whose version number is incompatible with the dump file version currently produced by the Oracle server on the system. Usually this message indicates that the dump file was produced by a newer version of the Oracle server.
Action: Load this dump file using the same version of the Oracle server that created the file.
KUP-11022: specified file name "string" is invalid
Cause: The file name specified for a dump or log file was invalid or null.
Action: Specify a valid file name for the dump or log file.
KUP-11023: specified path for directory object "string" is invalid
Cause: The default directory or a directory object specified for a dump or log file contained an invalid path name or was null.
Action: Specify a valid path name for the directory object.
KUP-11024: This external table can only be accessed from within a Data Pump job.
Cause: An attempt was made to access a temporary external table that was created by Data Pump to be used internally during the execution of an export or import job.
Action: None
PK1KSmPKjFJOEBPS/vidus.htm"Z VID-00611 to VID-00721

114 VID-00611 to VID-00721

VID-00611: unable to access the BLOB for reading
Cause: The BLOB could not be opened for reading.
Action: Contact Oracle Support Services.
VID-00612: unable to open export destination file
Cause: The file could not be created or opened.
Action: Check that the file does not refer to an existing directory. Check that the file is not locked by another application.
VID-00613: export destination access denied
Cause: Permission to write to destination file was denied.
Action: Refer to the Oracle Multimedia documentation for information on granting privileges for the export() method.
VID-00614: I/O error during export
Cause: The export operation failed because of an I/O error.
Action: Check OS logs and contact Oracle Support Services.
VID-00702: unable to initialize video processing environment
Cause: The initalization of the video processing procedure failed.
Action: See the database administrator to make sure that enough memory has been allocated to JServer. If JServer does have enough memory, contact Oracle Support Services.
VID-00703: unable to read video data
Cause: An error occurred while accessing the video source.
Action: Make sure the video source is valid. For external sources, make sure all access priviliges are granted.
VID-00704: invalid input format or corrupted input data
Cause: The video data in the source was not in the format specified by the format field of the video object. In some unusal cases, the video data is actually corrupted.
Action: Provide a correct value in the format field. If the correct value is unknown, put NULL in the format field to invoke the DEFAULT format plug-in.
VID-00705: unsupported input format
Cause: The file format of the video data was not supported. This error can only occur in the DEFAULT format plug-in package.
Action: Refer to the Oracle Multimedia documentation for supported formats.
VID-00706: unsupported or corrupted input format
Cause: The video data was either corrupted or the file format was not supported.
Action: Refer to the Oracle Multimedia documentation for supported formats. If the video data is not corrupted and is in a supported file format, contact Oracle Support Services.
VID-00707: unable to read empty video data
Cause: There is no data in the video object.
Action: Refer to the Oracle Multimedia documentation for information on how to populate the video object with video data.
VID-00713: internal error while parsing video data
Cause: An internal error occurred during parsing.
Action: Contact Oracle Support Services.
VID-00714: internal error
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
VID-00721: unable to find format plug-in package ORDPLUGINS.ORDX_string_VIDEO
Cause: Custom video plug-in for user-specified format was not found.
Action: Ensure correct video format is specified or proper custom video plug-in package is installed.
PKImʪ""PKjFJOEBPS/prkcmsg.htmr_ PRKC-01000 to PRKC-01168

71 PRKC-01000 to PRKC-01168

PRKC-01000: No active nodes detected in the cluster
Cause: The active node list of the cluster could not be retrieved. This could occur if the operating system dependent clusterware was not functioning properly in one or more nodes in the cluster, or because there was no clusterware installed on the system.
Action: Check the state of the cluster by running 'lsnodes' binary from your ORACLE_HOME/bin and see if it prints the node list correctly.
PRKC-01001: Error submitting commands in the buffer
Cause: This is an internal error.
Action: Contact Oracle Support Services.
PRKC-01002: All the submitted commands did not execute successfully
Cause: Either a node failed in the middle of a manageability operation, or the communication between nodes was disrupted.
Action: Check the state of your cluster by running 'lsnodes' binary from your ORACLE_HOME/bin and see if it prints the node list correctly.
PRKC-01004: Problem in copying file to nodes
Cause: Attempted file copy operation(s) from the local node to one or more nodes in the cluster and one or multiple of those copy file operations failed. Possible causes: 1) One or more file copy operations to nodes in the cluster failed. 2) The destination directory did not have write permission for the user on one or more of the nodes .the source file did not exist. 3) The 'rcp' command to one or more nodes failed on UNIX platforms.
Action: 1) Check that the source file exists. 2) Check that all nodes in the cluster are up. 3) Check that destination directory has write permission for the user. 4) On UNIX based platforms check that user can do 'rcp' to all the nodes.
PRKC-01005: Problem in removing file from nodes
Cause: Attempted file remove operation(s) from the local node to one or more nodes in the cluster and one or multiple of those file remove operations failed. Possible causes: 1) One or more nodes failed during the operation. 2) The destination directory did not have write permission for the user on one or more of the nodes. 3) The source file did not exist. 4) The 'rcp' command to one or more nodes failed on UNIX platforms.
Action: Check the accompanying error messages for details.
PRKC-01006: Problem in moving file to nodes
Cause: Attempted file move operation(s) from the local node to one or more nodes in the cluster and one or multiple of those move file operations failed. Possible causes: 1) One or more nodes failed during the operation. 2) The destination directory did not have write permission for the user on one or more of the nodes. 3) The source file did not exist. 4) The 'rcp' command to one or more nodes failed on UNIX platforms.
Action: Check the accompanying error messages for details.
PRKC-01007: Problem in creating directories on the nodes
Cause: Attempted directory create operation(s) from the local node to one or more nodes in the cluster and one or multiple of those directory create operations failed. Possible causes: 1) One or more nodes failed during the operation. 2) The destination directory did not have write permission for the user on one or more of the nodes. 3) The 'rcp' command to one or more nodes failed on UNIX platforms.
Action: Check the accompanying error messages for details.
PRKC-01009: Failed to start the service on all nodes
Cause: The service failed to start on one or more nodes of the cluster.
Action: Check if all the nodes in cluster are up and look in the clusterware alert log.
PRKC-01010: Failed to stop the service on all nodes
Cause: The service failed to stop on one or more nodes of the cluster.
Action: Check if all the nodes in cluster are up and service is still up on failed nodes. Look in the clusterware alert log.
PRKC-01011: Failed to delete the service from all nodes
Cause: The service failed to be deleted on one or more nodes of the cluster.
Action: Check if all the nodes in cluster are up and service is still registered. Look in the clusterware alert log.
PRKC-01012: Failed to create the service on all nodes
Cause: The service failed to be created on one or more nodes of the cluster.
Action: Check if all the nodes in cluster are up. Look in the clusterware alert log.
PRKC-01016: Failed to retrieve value of the enviornment variable "{0}", {1}
Cause: Attempted to retrieve value of an environment variable which was not defined.
Action: Define the environment variable.
PRKC-01017: Problem restarting GSD
Cause: GSD (Global Services Daemon) could not be started on the local node. This could occur if the operating system dependent clusterware was not functioning properly or there is already a running GSD.
Action: Check the state of your clusterware by running 'lsnodes' from ORACLE_HOME/bin. It should list the nodes in the cluster. Try 'gsdctl stop' and then 'gsdctl start' again.
PRKC-01018: Error getting coordinator node
Cause: This could occur if the operating system dependent clusterware was not functioning properly.
Action: Use 'gsdctl stop' on each node to stop the GSDs. Use 'gsdctl start' on each node in the cluster.
PRKC-01019: Error creating handle to GSD daemon on the node {0}
Cause: Global Services Daemon was not running on the node.
Action: Use 'gsdctl stat' to check the status of the daemon. Use 'gsdctl start' to start it.
PRKC-01020: Exception while executing the operation on the remote node {0}
Cause: Attempted to execute an operation on the remote node when the Global Services Daemon was not up on the remote node {0}.
Action: Start the Global Services Daemon on the remote node using 'gsdctl start'.
PRKC-01021: Problem in the clusterware
Cause: The operating system dependent clusterware could not be contacted. This could occur because the operating system dependent clusterware was not functioning properly.
Action: Check the state of the operating system dependent clusterware.
PRKC-01022: Could not get node name for node {0} in {1}
Cause: The operating system dependent clusterware could not be contacted. This could occur because the operating system dependent clusterware was not functioning properly.
Action: Check the state of the operating system dependent clusterware using 'lsnodes -n'.
PRKC-01025: Failed to create a file under the filepath {0} because the filepath is not executable or writable
Cause: The directory of the specified filepath did not have execute or write permission. So the temporary file could not be created to test whether the filepath was shared among nodes.
Action: Make the directory of the specified filepath executable and writable.
PRKC-01141: Oracle Restart is not supported in version {0}. It is supported from version {1} onwards
Cause: This is an internal error.
Action: Contact Oracle Support Services.
PRKC-01144: File "{0}" not found.
Cause: The file was not found in the file system.
Action: Make sure that the file exists in the file system.
PRKC-01148: Failed to get host name for the local computer
Cause: An error occurred while attempting to retrieve the TCP/IP host name
Action: Correct the problem indicated by the accompanying error messages.
PRKC-01149: Failed to get OCR locations
Cause: An error occurred while attempting to retrieve the OCR locations, possibly due to missing or incorrrect OCR locations file, or incomplete OCR configuration, or due to missing or incorrect SRVM shared libraries.
Action: Verify that the Clusterware has been correctly installed and configured. Verify that the ocr.loc file is present and readable in the appropriate location for your platform.
PRKC-01150: Failed to get drive letters used on following nodes: "{0}"
Cause: An error occurred while attempting to retrieve used drive letters on one or more nodes.
Action: Look at the accompanying messages and fix the error(s). The messages typically relate to a node not being reachable, or the remote execution service not running on the node, or some permissions issue when attempting to use the remote execution service on the remote node.
PRKC-01151: The given path "{0}" does not exist
Cause: The specified path may not have been created or an incorrect path has been specified.
Action: Make sure that the given path exists by specifying a correct existing path.
PRKC-01152: The specified path "{0}" is not a directory
Cause: The specified path may be a file, not a directory, or an incorrect path may have been specified.
Action: Make sure to specify a path that is a valid directory path.
PRKC-01153: No directory is available on the remote node "{0}" to copy the binary RemoteExecService.exe
Cause: Either the path defined by value of registry key HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/OracleRemExecService is not available on the remote node, or the c:/temp/ directory is not available or not accessible on the specified remote node.
Action: Make sure that the required path is available on the remote node.
PRKC-01155: The node list provided had only one entry or had multiple entries that were duplicates of a single nodename entry
Cause: The list of nodes provided for the shared path check was either only one node, or the list included entries that were duplicates of the same single node.
Action: Please provide the correct nodelist for the cluster on which the check is being called, making sure that there are at least two distinct entries.
PRKC-01156: Failed to validate raw device "{0}" -- Details: {1}
Cause: The raw device was not an existing device that could be opened and recognized by the OS as a "raw/character" device type.
Action: Make sure the supplied value identifies a valid raw device that can be opened as a "raw/character" device type.
PRKC-01157: Failed to validate raw device "{0}"
Cause: The raw device was not an existing device that could be opened and recognized by the OS as a "raw/character" device type.
Action: Make sure the supplied value identifies a valid raw device that can be opened as a "raw/character" device type.
PRKC-01158: Failed to validate raw device "{0}" -- Details: {1}
Cause: The device was not an existing device that could be opened and recognized by the OS as either "raw/character" or a "block" device type.
Action: Make sure the supplied value identifies a valid device that can be opened as a "raw/character" or "block" device type.
PRKC-01159: Failed to validate device "{0}"
Cause: The device was not an existing device that could be opened and recognized by the OS as either "raw/character" or a "block" device type.
Action: Make sure the supplied value identifies a valid device that can be opened as a "raw/character" or "block" device type.
PRKC-01160: Failed to retrieve the value of environment variable "{0}" on following nodes: "{1}", [{2}]
Cause: An error occurred while attempting to retrieve value of environment variable on one or more nodes due to the node not being reachable, or the remote execution service not running on the node, or some permissions issue when attempting to use the remote execution service on the remote node.
Action: Look at the accompanying messages and respond accordingly.
PRKC-01161: Failed to retrieve the Windows domain on following nodes: "{0}"
Cause: An error occurred while attempting to retrieve the Windows domain on one or more nodes. The possible causes include:"

- A node is not reachable.

- Remote execution service is not running on the node.

- Permissions problems prevented use of remote execution service on a node.

Action: Look at the accompanying messages and respond accordingly.
PRKC-01162: "{0}" is not a file
Cause: The indicated object was expected to be a file, but it was not.
Action: Make sure that the indicated object is a file and not a directory.
PRKC-01163: {0} Exception occurred while determining validity of storage type.
Cause: An error occurred while getting storage type of the given path. Null arguments might have been passed.
Action: Make sure that the native api is passing non null arguments.
PRKC-01164: invalid command or arguments
Cause: This is an internal error.
Action: Contact Oracle Support Services.
PRKC-01165: Failed to set up Windows service OracleRemoteExecService on node '{0}'
Cause: An error occurred while setting up OracleRemoteExecService on the specified nodes."
Action: Look at the accompanying messages and respond accordingly.
PRKC-01166: Storage is partially shared. Details: {0}
Cause: A subset of the nodes provided shared the given filesystem path with the local node.
Action: Mount the NFS filesystem on the node(s) that do not share the filesystem path.
PRKC-01167: Failed to resolve the specified path "{0}" to its physical path on following nodes: "{1}", [{2}]
Cause: An error occurred while attempting to resolve the path on one or more nodes due to the node not being reachable, the remote execution service not running on the node, or some permissions issue when attempting to use the remote execution service on the remote node.
Action: Look at the accompanying messages and respond accordingly.
PRKC-01168: Failed to get sub-keys of registry key {0}
Cause: Could not find any sub-keys for the given registry key.
Action: Check manually via 'regedit' that the registry key exists and has sub keys under it. If so, retry. Otherwise, contact Oracle Support Services.
PK,rrPKjFJOEBPS/content.opf(K״ Oracle® Database Error Messages, 11g Release 2 (11.2) en-US E17766-03 Oracle Corporation Oracle Corporation Oracle® Database Error Messages, 11g Release 2 (11.2) 2013-07-16T14:30:22Z Describes error messages that may appear while using products that are part of Oracle Database. PKqP-K(KPKjFJOEBPS/e54500.htm ORA-54500 to ORA-56974

30 ORA-54500 to ORA-56974

ORA-54500: invalid combination of elements
Cause: The geometry did not start from the correct level in the hierarchy.
Action: Correct the hierarchy in the geometry.
ORA-54501: no holes expected
Cause: The geometry contained one or more unexpected holes.
Action: Remove any holes in the geometry.
ORA-54502: solid not closed
Cause: The solid geometry was not closed i.e., faces of solid are not 2-manifold due to incorrectly defined, oriented, or traversed line segment because each edge of a solid must be traversed exactly twice, once in one direction and once in the reverse direction.
Action: Correct the orientation of the edges of the neighboring polygons.
ORA-54503: incorrect solid orientation
Cause: The orientation of the solid was not correct.
Action: Correct the orientation or specification of the outer or inner solid geometry according to the geometry rules for such a solid.
ORA-54504: multiple outer geometries
Cause: The geometry contained more than one outer geometry.
Action: Remove all but one of the outer geometries.
ORA-54505: ring does not lie on a plane
Cause: The ring was not flat.
Action: Make sure all of the vertices of the ring are on the same plane.
ORA-54506: compound curve not supported for 3-D geometries
Cause: The 3-D geometry contained one or more compound curves, which are not supported for 3-D geometries.
Action: Remove all compound curves from the geometry.
ORA-54507: duplicate points in multipoint geometry
Cause: The multipoint geometry had two points that either had identical coordinates or were the same point considering the geometry tolerance.
Action: Make sure all points are different, considering the tolerance.
ORA-54508: overlapping surfaces in a multisolid geometry
Cause: The multisolid geometry contained one or more fully or partially overlapping surfaces.
Action: Ensure that the multisolid geometry contains no overlapping areas.
ORA-54509: solid not attached to composite solid
Cause: To connect solids in a composite solid geometry, at least one of the faces of a solid must be shared (fully or partially) with only another solid. However, at least one of the faces in this composite solid was not shared by exactly two solids only.
Action: Ensure that at least one face in a composite solid is shared by exactly two solids.
ORA-54510: no outer geometry expected
Cause: An outer geometry was found when only inner geometries were expected.
Action: Remove all outer geometries.
ORA-54511: edges of inner and outer solids intersect
Cause: An inner solid had a common edge with outer solid.
Action: Ensure that edges of inner and outer solids do not intersect.
ORA-54512: a vertex of an inner solid is outside corresponding outer solid
Cause: A solid geometry contained an inner solid with at least one vertex outside its corresponding outer solid.
Action: Ensure that all vertices of inner solids are not outside their corresponding outer solid.
ORA-54513: inner solid surface overlaps outer solid surface
Cause: One or more faces of an inner solid surface either fully or partially overlapped an outer solid surface.
Action: Ensure that inner and outer surfaces have no shared (fully or partially overlapping) faces.
ORA-54514: overlapping areas in multipolygon
Cause: A multipolygon geometry contained one or more common (shared, fully or partially overlapped) polygons.
Action: Ensure that no polygons in a multipolygon overlap.
ORA-54515: outer rings in a composite surface intersect
Cause: Outer rings, either on the same plane or different planes, in a composite surface intersected.
Action: Ensure that outer rings do not intersect. They can share edges.
ORA-54516: adjacent outer rings of composite surface cannot be on same plane
Cause: The conditional flag was set, and a composite surface had at least two outer rings sharing a common edge on the same plane.
Action: Change those outer rings into one larger outer ring.
ORA-54517: outer ring is on the same plane and overlaps another outer ring
Cause: An outer ring in a composite surface shared a common area with another outer ring.
Action: Ensure that no outer rings fully or partially overlap.
ORA-54518: shared edge of composite surface not oriented correctly
Cause: A shared edge (one shared by two polygons) in a composite surface was not correctly oriented. Each shared edge must be oriented in one direction with respect to its first polygon and then in the reverse direction with respect to its second polygon.
Action: Reverse one of the directions of the shared edge with respect to its polygons.
ORA-54519: polygon (surface) not attached to composite surface
Cause: Not all polygons of a surface had a common (fully or partially shared) edge.
Action: Ensure that each polygon is attached to the composite surface by one of its edges.
ORA-54520: inner ring not on the same plane as its outer ring
Cause: An inner ring was not on the same plane as its outer ring.
Action: Ensure that each inner ring is on the same plane as its outer ring.
ORA-54521: inner ring is not inside or is touching outer ring more than once
Cause: An inner ring either was not inside its outer ring or touched its outer ring more than once.
Action: Ensure that the inner ring is inside its outer ring and does not touch the outer ring more than once. If an inner ring touches its outer ring more than once, then the outer ring is no longer a topologically simple or singly connected polygon (ring).
ORA-54522: inner rings of same outer ring cannot intersect or share boundary
Cause: Two inner rings of the same outer ring intersected or shared a boundary.
Action: Ensure that line segments of an inner ring do not intersect or fully or partially coincide with line segments of another inner ring sharing the same outer ring.
ORA-54523: inner rings of same outer ring cannot touch more than once
Cause: Two inner rings of the same outer ring touched more than once.
Action: Ensure that inner rings of the same outer ring touch at no more than one point.
ORA-54524: inner ring cannot be inside another inner ring of same outer ring
Cause: An inner ring was inside another ring of the same outer ring.
Action: Ensure that no inner ring is inside another inner ring of the same outer ring.
ORA-54525: incorrect box volume due to wrong ordinates
Cause: The rectangular box in shortcut format did not have its first x,y,z coordinates either all greater or less than its second x,y,z coordinates.
Action: Make sure that the first x,y,z coordinates are either all greater or all less than the second x,y,z coordinates.
ORA-54526: multi or composite geometry must be decomposed before extraction
Cause: The extraction could not be performed because the multi or composite geometry must first be decomposed into simple geometries (with or without inner geometries). The multi or composite geometry had a gtype of GTYPE_MULTISOLID, GTYPE_MULTISURFACE, GTYPE_MULTICURVE, GTYPE_MULTIPOINT, or GTYPE_COLLECTION, or the geometry was a line string.
Action: Use the MULTICOMP_TOSIMPLE parameter to element extractor to decompose the multi or composite geometry to a simple geometry.
ORA-54527: operation not permitted on a simple geometry
Cause: A MULTICOMP_TOSIMPLE parameter to element extractor was attempted on a geometry that is already simple.
Action: Do not use the MULTICOMP_TOSIMPLE parameter to element extractor on simple geometries.
ORA-54528: inner composite surfaces or surfaces with inner ring(s) expected
Cause: An INNER_OUTER parameter to element extractor was attempted on a surface that was not simple or composite.
Action: Ensure that the etype of the geometry for the INNER_OUTER parameter to element extractor is ETYPE_SURFACE or ETYPE_COMPOSITESURFACE.
ORA-54529: geometry should have multi-level hierarchy (like triangle)
Cause: The geometry did not have the multi-level hierarchy required for this operation. For example, if the parameter to element extractor (hierarchy level) is not LOWER_LEVEL, but the geometry etype is ETYPE_SOLID and gtype is GTYPE_SOLID, an extract operation is not allowed, because a simple solid can only be decomposed into lower level geometries, such as composite surfaces.
Action: Ensure that the geometry has the appropriate hierarchy. For example, if the geometry etype is ETYPE_SOLID and gtype is GTYPE_SOLID, the parameter to element extractor (hierarchy level) should be LOWER_LEVEL.
ORA-54530: invalid etype for element at element offset
Cause: An invalid etype was encountered.
Action: Correct the etype of the geometry.
ORA-54531: invalid orientation for element at element offset
Cause: The orientation of the current geometry was not valid.
Action: Reverse the orientation of the geometry.
ORA-54532: incomplete composite surface
Cause: The end of composite surface was reached before all necessary surfaces were defined.
Action: Add more surfaces to match the geometry definition, or reduce the specified number of surfaces.
ORA-54533: invalid etype in composite surface of solid
Cause: The etype of the composite surface of a solid was not valid.
Action: Ensure that the etype is orient*1000+ETYPE_SOLID, where orient is 1 for outer solid and 2 for inner solid.
ORA-54534: incorrect box surface due to wrong specification
Cause: The elemInfo definition was not correct for the surface of the axis aligned box.
Action: Change the interpretation to 3 in the elemInfo definition.
ORA-54535: incorrect box surface because it is on arbitrary plane
Cause: The axis aligned box surface was not on the yz, xz, or xy plane.
Action: Ensure that the first and fourth coordinates, or the second and fifth coordinates, or the third and sixth coordinates are the same. This means that the surface is on the yz, xz or xy plane, respectively.
ORA-54536: axis aligned box surface not defined properly
Cause: The inner geometry etype did not start with 2, or the outer geometry etype did not start with 1, or both occurred.
Action: Use the correct etype for the inner and outer geometries.
ORA-54537: incorrect box surface due to wrong orientation
Cause: The rectangular surface in shortcut format did not have its first x,y,z coordinates all greater than or equal to or all less than or equal to its second x,y,z coordinates.
Action: Ensure that the first x,y,z coordinates are either all greater than or equal to or all less than or equal to the second x,y,z coordinates.
ORA-54538: unexpected gtype
Cause: The gtype of the geometry was not GTYPE_SOLID, GTYPE_SURFACE, GTYPE_CURVE or GTYPE_POINT.
Action: Correct the elemInfo array to fix any invalid gtype and etypes that violate the geometry hierarchy.
ORA-54539: cannot process the geometry(s) for this operation
Cause: The geometry had errors in it.
Action: Validate the geometry or geometries to ensure that each is valid.
ORA-54540: at least one element must be a surface or solid
Cause: One of the geometries had holes, and the geometries were neither (A) simple, composite, or multisurfaces, or (B) simple, composite, or multisolids. (Surfaces and solids are the only geometries that can have holes. Points and curves cannot have holes.)
Action: Ensure that each geometry having holes is a surface or solid (simple, composite, or multi).
ORA-54545: holes incorrectly defined
Cause: The holes were defined with incorrect etype.
Action: Ensure that the etype is correct in the definition of the inner geometry.
ORA-54546: volume of solid cannot be 0 or less
Cause: The solid geometry having one outer and multiple inner geometries had a negative or zero volume.
Action: Correct the orientation or specification of the outer solid geometry to obey outer geometry rules so that the outer geometry has a positive volume. Additionally, correct the orientation or specification of inner solid geometries to obey inner geometry rules so that each inner geometry has a negative volume.
ORA-54547: wrong input for COUNT_SHARED_EDGES
Cause: The COUNT_SHARED_EDGES parameter value was not 1 or 2.
Action: Ensure that the COUNT_SHARED_EDGES parameter value is either 1 or 2.
ORA-54548: input geometry gtype must be GTYPE_POLYGON for extrusion
Cause: The input geometry gtype was not GTYPE_POLYGON.
Action: Ensure that the gtype of the input polygon is GTYPE_POLYGON.
ORA-54549: input geometry has incorrect elemInfo
Cause: The input 2-D polygon did not have only one outer ring.
Action: Ensure that the input 2-D polygon has only one outer ring.
ORA-54550: input 2-D polygon not valid
Cause: The 2-D polygon violated the rules for polygons and rings.
Action: Correct the polygon definition.
ORA-54551: grdHeight and/or Height array sizes incorrect
Cause: The sizes of grdHeight and Height arrays were not equal to half the size of input 2-D polygon's ordinates array. As a result, each point in the 2-D polygon could not be extruded from the grdHeight entry to the Height entry.
Action: Ensure that the sizes of the grdHeight and Height arrays are half that of input 2-D polygon ordinates array.
ORA-54552: height entries must be >= to ground height entries
Cause: In the definition of a solid, the height values were less than the ground height.
Action: Ensure that that height values are greater than or equal to ground height values.
ORA-54553: incorrect geometry for appending
Cause: The geometry could not be appended to a homogeneous collection (for example, multi-geometry) or to a heterogeneous geometry (for example, collection). In other words, the gtype of the geometry to be appended was neither GYTPE_COLLECTION or GTYPE_MULTI-X (where X is point, curve, surface, or solid).
Action: Ensure that the geometries involved in the append operation have appropriate gtypes.
ORA-54554: arcs are not supported as defined
Cause: An arc was defined in a geometry type in which arcs are not supported. Arcs are supported for 2-D (circle) polygons, 2-D compound polygons, 2-D single arc, and 2-D compound (composite) curves only.
Action: Remove or simplify the arcs.
ORA-54555: invalid geometry dimension
Cause: The geometry did not have three dimensions.
Action: Ensure that geometry has three dimensions.
ORA-54556: operation is not supported for 3-D geometry
Cause: A 3-D geometry was passed into an operation that supports only 2-D geometries.
Action: Check the Spatial documentation for operations that are supported and not supported on 3-D geometries.
ORA-54557: incomplete composite solid
Cause: The end of composite solid was reached before all necessary solids were defined.
Action: Add more solids to match the geometry definition, or reduce the specified number of solids.
ORA-54558: 3D SRID is not found for the corresponding 2D SRID
Cause: In extruding a 2D polygon into a 3D geometry, the SRID conversion function did not find an equivalent 3D SRID of the 2D SRID.
Action: Specify a 2D SRID that has a 3D equivalent
ORA-54559: query element and source geometry cannot be the same
Cause: A query element geometry and a source geometry were the same, which prevented a label pointing query element in the source geometry from being output.
Action: Redefine the query element or the source geometry so that a label can be output.
ORA-54560: query element cannot be a collection or multitype geometry
Cause: A query element was a collection geometry or a multitype geometry. Such geometries are not permitted in a query element because they are at the top of the geometry hierarchy. A query element must be part of the source geometry.
Action: Redefine the query element or the source geometry so that a label can be output.
ORA-54601: CREATE_PC: invalid parameters for creation of Point Cloud
Cause: An invalid or unknown parameter was specified in the creation of Point Cloud.
Action: Check for valid set of parameters.
ORA-54602: CREATE_PC: input points table string does not exist
Cause: The specified table for loading points into a Point Cloud did not exist.
Action: Create the points table with appropriate columns, and then create the Point Cloud.
ORA-54603: CREATE_PC: specified total dimensionality cannot exceed 8
Cause: The specified total dimensionality for the Point Cloud exceeded the maximum limit of 8.
Action: Create the Point Cloud with fewer dimensions. You can store the rest in the output points table.
ORA-54604: CREATE_PC: input points table should not be empty
Cause: The input points table had no data.
Action: Insert data into the input points table and then create the Point Cloud.
ORA-54605: CREATE_PC: scratch-tables/views (string) exist and need to be dropped
Cause: Transient tables/views from a previous CREATE_PC operation were still in existence.
Action: Delete the invalid Point Cloud from the base table (for cleanup of scratch tables), and initialize and create the Point Cloud again. Alternately, use SDO_UTIL.DROP_WORK_TABLES with oidstring as the parameter.
ORA-54607: CREATE_PC: error fetching data from input points table
Cause: An internal read error occurred during Point Cloud creation.
Action: Contact Oracle Support Services with the error number reported.
ORA-54608: CREATE_PC: error writing Point Cloud LOB
Cause: An internal LOB write error occurred during Point Cloud creation. The cause might be lack of table space.
Action: Look for information from other errors in the stack, or contact Oracle Support Services with the error number reported.
ORA-54609: CREATE_PC: input extent cannot be null
Cause: The extent of the Point Cloud was null.
Action: Specify an extent for the Point Cloud that is not null.
ORA-54610: CREATE_PC: input extent cannot be more than 2-D for geodetic data
Cause: The extent of the Point Cloud was more than 2-D for geodetic data.
Action: Change the extent to 2-D (longitude, latitude).
ORA-54611: INIT: either invalid basetable/schema or they do not exist
Cause: The base table or schema, or both, were invalid strings; or the base table and schema combination did not exist.
Action: Ensure that the specified base table exists in the specified schema before performing the initialization operation.
ORA-54613: INIT: internal error creating DML trigger
Cause: The necessary privileges to create the trigger were not granted.
Action: Grant the necessary privileges to create the trigger. If necessary, contact Oracle Support Services for help with privileges for trigger creation.
ORA-54614: INIT: block table name has to be unique
Cause: The specified block table name was not unique. For example, it might have been used for another block table.
Action: Specify a different block table name.
ORA-54616: INIT: internal error [number, string]
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
ORA-54617: CLIP_PC: invalid Point Cloud; extent is empty
Cause: The input Point Cloud for the CLIP_PC operation was invalid.
Action: Specify a point cloud that was created using the CREATE_PC procedure.
ORA-54618: CLIP_PC: SRIDs of query and Point Cloud are incompatible
Cause: The Point Cloud and the query geometry had incompatible SRID values.
Action: Change the query SRID to be compatible with that of the Point Cloud.
ORA-54619: CLIP_PC: query and BLKID parameters cannot both be null
Cause: Both the query and BLKID parameters were null in the call to the CLIP_PC operation.
Action: Either specify a query geometry that is not null, or specify a BLKID for use as a query.
ORA-54620: CLIP_PC: internal error [number, string]
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
ORA-54621: TO_GEOMETRY: TOTAL_DIMENSIONALITY not same as in INIT operation
Cause: The specified TOTAL_DIMENSIONALITY was invalid.
Action: Ensure that the TOTAL_DIMENSIONALITY matches that specified in the call to the initialization operation.
ORA-54622: TO_GEOMETRY: internal error [number, string]
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
ORA-54623: CREATE_PC: internal error [number, string]
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
ORA-54640: PARTITION_TABLE utility: invalid input parameters [number, string]
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
ORA-54641: PARTITION_TABLE utility: scratch tables exist with oidstr = string
Cause: Scratch tables/views could not be created because they already existed.
Action: Use SDO_UTIL.DROP_WORK_TABLES with the specified oidstr parameter to clean up the scratch tables.
ORA-54642: PARTITION_TABLE utility: invalid SORT_DIMENSION specified
Cause: An invalid string was specified for the SORT_DIMENSION.
Action: Specify the SORT_DIMENSION as 'BEST_DIM', 'DIMENSION_1', 'DIMENSION_2', or 'DIMENSION_3'.
ORA-54643: PARTITION_TABLE utility: invalid WORKTABLESPACE parameter
Cause: An invalid string was specified for the WORKTABLESPACE parameter.
Action: Specify an existing valid tablespace for WORKTABLESPACE (to hold the scratch tables).
ORA-54644: PARTITION_TABLE utility: error in reading input, output tables
Cause: The names for the input/output tables were invalid, or the tables did not exist or did not have the right structure.
Action: Check the Spatial documentation for PARTITION_TABLE.
ORA-54651: CREATE_TIN: invalid parameters specified in creation of TIN
Cause: An invalid or unknown parameter was specified in the creation of the TIN.
Action: Check the Spatial documentation for CREATE_TIN.
ORA-54652: CREATE_TIN: input points table string does not exist
Cause: The specified table for loading points into a TIN did not exist.
Action: Create the points table with appropriate columns, and then create the TIN.
ORA-54653: CREATE_TIN: specified total dimensionality cannot exceed 8
Cause: The specified total dimensionality for the TIN exceeded the maximum limit of 8.
Action: Create the TIN with fewer dimensions. You can store the rest in the output points table.
ORA-54654: CREATE_TIN: input points table should not be empty
Cause: The input points table had no data.
Action: Insert data into the input points table, and then create the TIN.
ORA-54655: CREATE_TIN: scratch tables/views(string) exist and need to be dropped
Cause: Transient tables from previous CREATE_TIN operation still existed.
Action: Delete the invalid TIN from the base table (for cleanup of scratch tables), and initialize and create the TIN again. Alternately, use SDO_UTIL.DROP_WORK_TABLES with oidstring as its parameter.
ORA-54656: CREATE_TIN: error fetching data from input points table
Cause: An internal read error occurred during TIN creation.
Action: Contact Oracle Support Services with the error number reported.
ORA-54657: CREATE_TIN: error writing TIN LOB
Cause: An internal LOB write error occurred during TIN creation. The cause might be lack of table space.
Action: Look for information from other errors in the stack, or contact Oracle Support Services with the error number reported.
ORA-54658: CREATE_TIN: input extent cannot be null
Cause: The extent of the TIN was null.
Action: Specify an extent for the TIN that is not null.
ORA-54659: CREATE_TIN: input extent has to be 2-D for geodetic data
Cause: The extent of the TIN was more than 2-D for geodetic data.
Action: Change the extent to 2-D (longitude, latitude).
ORA-54660: CLIP_TIN: invalid Point Cloud; extent is empty
Cause: The input TIN for the CLIP_TIN operation was invalid.
Action: Specify a TIN that was created using the CREATE_TIN operation.
ORA-54661: CLIP_TIN: SRIDs of query and TIN are incompatible
Cause: The TIN and the query geometry had incompatible SRID values.
Action: Change the query geometry SRID to be compatible with that of TIN.
ORA-54662: CLIP_TIN: query and blkid parameters cannot both be null
Cause: Both the query and blkid parameters were null in the call to the CLIP_TIN operation.
Action: Either specify a query geometry that is not null, or specify a blkid for use as a query.
ORA-54663: CLIP_TIN: internal error [number, string]
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
ORA-54664: TO_GEOMETRY: internal error [number, string]
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
ORA-54665: CREATE_TIN: internal error [number, string]
Cause: An internal error occurred.
Action: Contact Oracle Support Services.
ORA-54666: query gtype is a superset of the source geometry
Cause: A query element geometry was at a higher level in the geometry hierarchy than the source geometry.
Action: Try replacing the source geometry with the query geometry.
ORA-54667: query element cannot be matched to an element in source geometry (string)
Cause: A query element geometry was not a part of the source geometry.
Action: Redefine the query element or the source geometry.
ORA-54668: a 2D SRID cannot be used with a 3D geometry
Cause: A 2D SRID was used with a 3D geometry.
Action: Replace the 2D SRID with an appropriate 3D SRID.
ORA-55200: Java exception from tag data translation java stack
Cause: Java exceptions.
Action: Turn on java output by calling dbms_java.set_output(OUTPUT_SIZE); Set java logging level by calling MGD_ID_UTL.setJavaLoggingLevel('INFO'); Analyze java logging messages.
ORA-55201: Tag data translation category not found
Cause: No matching category ID could be found.
Action: Make sure the input category name, category version or category ID is correct.
ORA-55202: Tag data translation scheme not found
Cause: No matching scheme could be found for the input data format.
Action: Make sure the input data format is supported and correct.
ORA-55203: Tag data translation level not found
Cause: No matching level could be found for the input data format.
Action: Make sure the input data format is supported and correct.
ORA-55204: Tag data translation option not found
Cause: No matching option could be found for the input data format.
Action: Make sure the input data format is supported and correct.
ORA-55205: Tag data translation field validation failed
Cause: Invalid field value.
Action: Make sure the field value of the input data is within the range specified in the tag data translation XML.
ORA-55206: Tag data translation field not found
Cause: Invalid input field.
Action: Make sure the spellings of the input fields are correct.
ORA-55207: Tag data translation rule evaluation failure
Cause: Error occurred when idcode translator tried to evaluate the rule specified in the tag data translation XML.
Action: Java proxy must be set in order to evaluate manager look up rules. Call MGD_ID_UTL.setProxy(PROXY_HOST, PROXY_PORT) to enable java proxy.
ORA-55208: Too many matching levels were found for the input data
Cause: Necessary field values were missing.
Action: Add additional field value pairs that are necessary to determine a unique matching level.
ORA-55300: model string does not exist
Cause: The specified model could not be found.
Action: Make sure that the model has been created.
ORA-55301: rulebase string does not exist
Cause: The specified rulebase could not be found.
Action: Make sure that the rulebase has been created.
ORA-55302: insufficient privileges string
Cause: Sufficient privileges were not granted.
Action: Ask the database administrator to grant the appropriate privileges.
ORA-55303: SDO_RDF_TRIPLE_S constructor failed: string
Cause: SDO_RDF_TRIPLE_S constructor failed.
Action: Check the stack trace for additional information.
ORA-55304: specified reuse-bNode model-id string != target model-id string
Cause: The reuse-bNode model-id specified for the SDO_RDF_TRIPLE_S constructor was neither 0 nor the model-id of the target model.
Action: Make sure that the reuse-bNode model is either 0 or the model-id of the target model.
ORA-55305: reification constructor functions not supported
Cause: Unsupported reification constructor functions were used.
Action: Insert each triple in the reification quad individually. See documentation for more information.
ORA-55306: internal error: invalid string: value_name=string value_type=string
Cause: The value type of this component of the RDF triple was invalid.
Action: This is an internal error. Contact Oracle Support Services.
ORA-55307: invalid value type for lexical value: string
Cause: The value type of this lexical value was invalid.
Action: Make sure that the lexical value format is correct. If this error occurs during bulk load from a staging table, then this may be an internal error. Contact Oracle Support Services.
ORA-55308: invalid time zone string for lexical value string
Cause: The time zone of this lexical value was invalid.
Action: Make sure that the lexical value format is correct. If this error occurs during bulk load from a staging table then this may be an internal error. Contact Oracle Support Services.
ORA-55309: hash collision resolution failed for lexical value string
Cause: Attempts to resolve hash collision exceeded the maximum retry count.
Action: This may be an internal error. Contact Oracle Support Services.
ORA-55310: parse failed for the string lexical value: string
Cause: Attempts to insert the specified lexical value failed.
Action: This may be an internal error. Contact Oracle Support Services.
ORA-55311: invalid value type string for long lexical value string
Cause: The value type of this long (length > 4000) lexical value was invalid.
Action: Make sure that the long value has a valid value type.
ORA-55312: parse failed for triple: id-form: string string string
Cause: Attempts to insert triple failed.
Action: This may be an internal error. Contact Oracle Support Services.
ORA-55313: SDO_RDF_TRIPLE_S constructor failed to process triple containing bNode
Cause: The SDO_RDF_TRIPLE_S constructor without bNode reuse option was invalid for triple containing bNode.
Action: Use SDO_RDF_TRIPLE_S constructor that allows bNode reuse.
ORA-55314: invalid temporary table name (string) for use with batch load
Cause: Specified temporary table name was not valid.
Action: See documentation for rules for temporary table name validity.
ORA-55315: batch load attempt failed: string
Cause: The batch load operation failed.
Action: This may be an internal error. Contact Oracle Support Services.
ORA-55316: model string does not match model string for table and column
Cause: This column of the table was not associated with the specified model.
Action: Make sure to use the correct target model.
ORA-55317: model string already exists
Cause: A model with the specified name was already present.
Action: Choose a different model name, or delete the existing model and create a new model with the specified name.
ORA-55318: column string in table string already contains data
Cause: At model creation time, the table column contained data.
Action: Ensure that the table column does not contain data before model creation.
ORA-55319: model string create attempt failed: string
Cause: The attempt to create the specified model did not succeed.
Action: This may be an internal error. Contact Oracle Support Services.
ORA-55320: model string drop attempt failed: string
Cause: The attempt to drop the specified model did not succeed.
Action: This may be an internal error. Contact Oracle Support Services.
ORA-55321: network already exists
Cause: Attempt to create the network failed because the network already existed.
Action: If necessary, drop the network before trying to recreate the network.
ORA-55322: model(s) exist
Cause: An attempt was made to drop a network that contained one or more models.
Action: Drop all the model(s) and then retry the operation.
ORA-55323: rulebase(s) exist
Cause: An attempt was made to drop a network that contained one or more rulebases.
Action: Drop all the rulebase(s) and then retry the operation.
ORA-55324: no rulebases specified
Cause: Rulebases for the operation were not specified.
Action: Specify at least one rulebase.
ORA-55325: rulebase or rules index string already exists string
Cause: A rulebase or rules index with the specified name already existed.
Action: Choose a different name, or delete the existing rulebase or rules index.
ORA-55326: rules index (string) create attempt failed: string
Cause: The attempt to create the specified rules index did not succeed.
Action: This may be an internal error. Contact Oracle Support Services.
ORA-55327: rule string yields a triple with a literal subject or predicate
Cause: The specified rule created an invalid triple containing a literal in the subject or predicate position.
Action: Check and modify the rule to avoid creation of invalid triple.
ORA-55328: literal value string insert attempt failed
Cause: The attempt to create the specified literal value failed.
Action: This may be an internal error. Contact Oracle Support Services.
ORA-55329: same model string specified more than once in the list of models
Cause: The specified model occurred more than once in the list of models.
Action: Eliminate duplicate occurrences of the model in the list of models.
ORA-55330: rulebase or rules index string is busy
Cause: The specified rulebase or rules index was busy and could not be used.
Action: Retry your operation later.
ORA-55331: user owns RDF objects
Cause: The user could not be dropped because it owns RDF objects.
Action: Drop the RDF objects and then retry.
ORA-55332: virtual model cannot be used in this context
Cause: A virtual model was used as input instead of a model.
Action: Use a model as input.
ORA-55333: virtual model string does not exist
Cause: The specified virtual model could not be found.
Action: Make sure that the virtual model has been created.
ORA-55334: virtual model name string is invalid
Cause: The specified virtual model name was not valid.
Action: Check Oracle documentation for valid virtual model names.
ORA-55335: at least one model must be specified
Cause: An empty list of models was specified as the set of models for a virtual model.
Action: Make sure at least one model appears in the set of models used to create a virtual model.
ORA-55336: insufficient privileges for using one or more of the models and rules indexes
Cause: An attempt was made to create a virtual model without the appropriate privileges.
Action: Ask the database administrator to perform the operation or to grant the required privileges.
ORA-55337: a virtual model or rules index with the name string already exists
Cause: A virtual model or rules index with the specified name was already present.
Action: Choose a different virtual model name.
ORA-55338: a model with the name string already exists
Cause: A model with the specified name was already present.
Action: Choose a different virtual model name.
ORA-55339: a virtual model already exists for the specified model-rulebase combination
Cause: A virtual model with identical components was already present.
Action: Choose a different set of components for the new virtual model.
ORA-55340: rules index does not exist for the specified model-rulebase combination
Cause: A rules index did not exist for the specified sets of models and rulebases.
Action: Make sure a rules index is created for the specified sets of models and rulebases.
ORA-55341: label index out-of-range
Cause: An attempt was made to use an out-of-range index for retrieving the label.
Action: Correct the input and try again.
ORA-55342: not a defined label in the policy
Cause: An attempt was made to use an undefined label.
Action: Correct the input and try again.
ORA-55343: invalid dependent component for custom label generator
Cause: An attempt was made to specify an invalid dependent component for the label generator.
Action: Correct the input and try again.
ORA-55344: invalid label generator implementation or use
Cause: An attempt was made to use an invalid label generator to generate labels for inferred data.
Action: Correct the input and try again.
ORA-55345: invalid use of label generator with no OLS policy
Cause: An attempt was made to use a label generator when Oracle Label Security (OLS) was not enabled for Resource Definition Framework (RDF) data.
Action: None
ORA-55346: invalid label generation option with user rules
Cause: An attempt was made to specify an invalid label generation option for entailment involving user rules.
Action: Correct the input and try again.
ORA-55347: missing proof for the specified label generation option
Cause: The chosen label generation option required proof, which was missing for the entailment.
Action: Correct the input and try again.
ORA-55348: label generator error: RDF data not enabled for string
Cause: An invalid label generator option was chosen for entailment.
Action: Correct the input and try again.
ORA-55349: OLS not installed or in an invalid state
Cause: Oracle Label Security (OLS) support for Resource Definition Framework (RDF) was not installed.
Action: Consult Oracle documentation to install the Oracle Label Security (OLS) support.
ORA-55350: RDF-OLS table option string not supported
Cause: An attempt was made to use an unsupported Oracle Label Security (OLS) option for Resource Definition Framework (RDF) data.
Action: Correct the input and try again.
ORA-55351: RDF secure access option not supported or is invalid
Cause: An attempt was made to use an unsupported secure access option for Resource Definition Framework (RDF).
Action: Correct the input and try again.
ORA-55352: insufficient privileges for policy administration
Cause: The necessary privileges needed to administer Oracle Label Security (OLS) or Oracle Virtual Private Database (VPD) policies for Resource Definition Framework (RDF) data were not specified.
Action: None
ORA-55353: invalid column name for label column string
Cause: An attempt was made to use an invalid column to maintain labels for Resource Definition Framework (RDF) data.
Action: Use CTXT2 as the label column.
ORA-55354: Policy string does not exist or is inaccessible
Cause: An attempt was made to use a nonexistent policy.
Action: Correct the input and try again.
ORA-55355: RDF network does not exist
Cause: An attempt was made to perform an operation that required Resource Definition Framework (RDF) network to be present.
Action: Create the Resource Definition Framework (RDF) network.
ORA-55356: OLS not enabled for RDF data
Cause: An attempt was made to perform an RDF-OLS-specific operation when Oracle Label Security (OLS) was not enabled for Resource Definition Framework (RDF) data.
Action: None
ORA-55357: insufficient privileges for the current operation
Cause: An attempt was made to perform a Resource Definition Framework (RDF) secure access operation with restricted privileges.
Action: See Oracle documentation.
ORA-55358: model "string" is not empty
Cause: An attempt was made to reset Oracle Label Security (OLS) labels for a model with some data.
Action: None
ORA-55359: unauthorized operation with policy string - string
Cause: An attempt was made to perform an unauthorized DML operation on OLS-enabled Resource Definition Framework (RDF) repository.
Action: None
ORA-55360: invalid value for resource position - string
Cause: An invalid value was specified for the resource position while setting labels.
Action: Correct the input and try again.
ORA-55361: duplicate specification for the namespace found
Cause: An attempt was made to use a namespace map that contained one or more duplicate specifications.
Action: Correct the input and try again.
ORA-55362: RDF VPD policy may not be created in the SYS schema
Cause: An attempt was made to create an Oracle Virtual Private Database (VPD) policy in the SYS schema.
Action: None
ORA-55363: context string does not exist
Cause: An attempt was made to specify a nonexistent context for the Oracle Virtual Private Database (VPD) policy.
Action: Create the context using CREATE CONTEXT command.
ORA-55364: invalid operation type string for VPD policy
Cause: An attempt was made to specify an invalid operation for the application of Oracle Virtual Private Database (VPD) policy.
Action: Specify ALL, QUERY, or DML for operation type.
ORA-55365: invalid metadata for VPD policy
Cause: An attempt was made to define invalid metadata elements for the Oracle Virtual Private Database (VPD) policy.
Action: See Oracle documentation for valid set of metadata elements.
ORA-55366: unknown namespace prefix "string"
Cause: An attempt was made to make use of an undefined namespace prefix in Oracle Virtual Private Database (VPD) metadata.
Action: Correct the input and try again.
ORA-55367: invalid maintenance operation for VPD metadata
Cause: An attempt was made to perform an invalid maintenance operation on Oracle Virtual Private Database (VPD) metadata.
Action: Specify ADD or DELETE for VPD metadata maintenance.
ORA-55368: empty match or apply pattern not allowed in a VPD constraint
Cause: An attempt was made to specify an empty match or apply pattern for a Oracle Virtual Private Database (VPD) constraint.
Action: Correct the input and try again.
ORA-55369: invalid identifier specified for the constraint group
Cause: An invalid SQL identifier was specified for the constraint group.
Action: Correct the input and try again.
ORA-55370: input parameter not a zero or positive integer
Cause: The input parameter was not zero or a positive integer.
Action: Change the input parameter to zero or a positive integer.
ORA-55371: RDF rules index 'string' exists for different model-rulebase combination
Cause: A rules index with the specified name has already been built for a different model-rulebase combination.
Action: Specify a different rules index name, or drop the existing rules index and then create a new rules index with that name.
ORA-55372: entailment (rules index) 'string' already exists
Cause: The entailed graph (rules index) already exists.
Action: Specify a different rules index name, or drop the existing rules index and then create a new rules index with that name.
ORA-55373: inference internal error: string
Cause: An unexpected internal error condition occurred.
Action: Check the error message and the stack trace.
ORA-55374: query constants not in the database; no rows selected
Cause: URIs or literals used in the query did not exist in the database.
Action: Check the query, and ensure that the URIs or literals do exist.
ORA-55375: cannot drop table 'string' because this table owns RDF objects
Cause: A table containing RDF data could not be dropped without first dropping its RDF model.
Action: Drop the corresponding RDF model or models, and then drop the table.
ORA-55376: cannot alter or drop column 'string' because this column owns RDF objects
Cause: A table column containing RDF data could not be altered or dropped without first dropping its RDF model.
Action: Drop the corresponding RDF model or models, and then alter or drop the column.
ORA-55377: number of triples less than 1 or null error indication marker
Cause: An internal error occurred during validation. The number of triples was less than 1 or the error indication marker was null.
Action: Check the input parameters, and ensure that the number of triples is 1 or greater and that the error indication marker is not null; or contact Oracle Support Services.
ORA-55378: invalid error code
Cause: An invalid error code was passed in during validation.
Action: Specify a valid error code.
ORA-55379: too many triples
Cause: An internal error occurred during validation. Too many triples were passed in.
Action: Specify a valid number of triples for the operation, or contact Oracle Support Services.
ORA-55430: query pattern is null
Cause: The query pattern specified in the SEM_MATCH query was null.
Action: Modify the query pattern to be non-null.
ORA-55441: insufficient privileges to drop virtual model string
Cause: An attempt was made to drop a virtual model without the appropriate privileges.
Action: Ask the database administrator to perform the operation or grant the required privileges.
ORA-55442: a virtual model cannot be used with other models in a SEM_MATCH query
Cause: The set of models used as input to a SEM_MATCH query contained a virtual model.
Action: Create a new virtual model with contents that are equivalent to the specified SEM_MATCH model set and query the new virtual model.
ORA-55443: a virtual model cannot be used with a rulebase in a SEM_MATCH query
Cause: A rulebase was specified in conjunction with a virtual model as input to a SEM_MATCH query.
Action: Create a new virtual model that expands the specified virtual model to include the specified rulebase and query the new virtual model.
ORA-55450: continually refreshed workspaces not supported with RDF
Cause: An attempt was made to use continually refreshed workspaces with Resource Definition Framework (RDF) data.
Action: None
ORA-55451: multi-parent workspaces not supported with RDF
Cause: An attempt was made to use multi-parent workspaces with Resource Definition Framework (RDF) data.
Action: None
ORA-55452: batch mode not allowed with version-enabled models
Cause: An attempt was made to batch load data into a version- enabled Resource Definition Framework (RDF) model. This is not supported.
Action: None
ORA-55453: OLS/VPD-enabled indexes must be created with CREATE_ENTAILMENT API
Cause: An attempt was made to create entailment for OLS/VPD-enabled models using unsupported API.
Action: Correct the input and try again.
ORA-55454: version-enabled indexes must be created with CREATE_ENTAILMENT API
Cause: An attempt was made to create entailment for version- enabled models using unsupported API.
Action: Correct the input and try again.
ORA-55455: rules index status not recognized ( string )
Cause: The specified rules index status was not recognized.
Action: Ensure that the rules index status is VALID, INCOMPLETE, or INVALID, and retry the operation.
ORA-55456: no valid rules index for this model-rulebase combination
Cause: A valid rules index did not exist for specified combination of models and rulebases.
Action: Create a rules index for the specified models and rulebases combination, or use a combination of models and rulebases for which a rules index exists, and retry the operation. Also ensure that the rules index status matches the status for the rules index specified in the query.
ORA-55457: predicate not found in model
Cause: The predicate value passed in as an argument to the semantic operator did not exist in the model.
Action: In the query using semantic operators, use a predicate value that exists in the model and retry the operation.
ORA-55458: object not found in model
Cause: The object value passed in as an argument to the semantic operator did not exist in the model.
Action: In the query using semantic operators, use an object value that exists in the model and retry the operation.
ORA-55459: invalid parameter string
Cause: The parameter string used in the creation of an index of type SEM_INDEXTYPE had invalid or malformed parameters.
Action: See the documentation for information on how to write a valid parameter string.
ORA-55460: incorrect usage of semantic operators
Cause: There was a syntax error in the call to the SEM_RELATED operator
Action: See the documentation for information on how to use the SEM_RELATED operator. Check that the value returned by SEM_RELATED is compared to 1 or 0.
ORA-55461: no distance information available
Cause: Distance information was not generated during rules index creation.
Action: Retry query without the SEM_DISTANCE operator and/or without specifying bounds in the SEM_RELATED operator. See the documentation for information on when distance information is generated.
ORA-55462: internal error
Cause: An internal error occurred during a semantic operator query or during the creation of an index of type SEM_INDEXTYPE.
Action: Contact Oracle Support Services.
ORA-55463: missing privileges for MDSYS schema for OLS-enabled entailment
Cause: An attempt was made to run entailment with insufficient privileges for MDSYS schema.
Action: Grant EXEMPT ACCESS POLICY to MDSYS.
ORA-55464: model "string" does not exist
Cause: An attempt was made to use a nonexistent Resource Definition Framework (RDF) model.
Action: Correct the input and try again.
ORA-55465: resource position string not secured with OLS policy
Cause: An attempt was made to associate labels with resource positions that were not secured with Oracle Label Security (OLS).
Action: Correct the input and try again.
ORA-55466: one or more triples have incompatible sensitivity label
Cause: An attempt was made to reset a label for a resource that participated in triples with incompatible label.
Action: Correct the input and try again.
ORA-55467: model-specific label for the resource is incompatible
Cause: An attempt was made to set a global label for a resource when an incompatible model-specific label already existed.
Action: Correct the input and try again.
ORA-55468: rule base "string" does not exist or is not accessible
Cause: An attempt was made to specify a rule base that did not exist.
Action: Correct the input and try again.
ORA-55469: rule "string" does not exist or is not accessible
Cause: An attempt was made to set a label for a rule that did not exist.
Action: Correct the input and try again.
ORA-55470: OLS may not be applied with one or more models VPD-enabled
Cause: An attempt was made to OLS-enable Resource Definition Framework (RDF) repository when one or more models is VPD-enabled.
Action: Oracle Label Security (OLS) and Oracle Virtual Private Database (VPD) may not be used simultaneously.
ORA-55471: OLS may not be applied to version-enabled RDF repository
Cause: An attempt was made to OLS-enable Resource Definition Framework (RDF) repository when one or more models is version-enabled.
Action: Oracle Label Security (OLS) may not be enabled when one or more models is version-enabled.
ORA-55472: Secure access policy already assigned to RDF data
Cause: An attempt was made to assign an Oracle Label Security (OLS) policy to Resource Definition Framework (RDF) data when some other policy was already in effect.
Action: None
ORA-55473: RDF model participating in a virtual model may not be version-enabled
Cause: An attempt was made to version-enable a Resource Definition Framework (RDF) model which participated in a virtual model.
Action: None
ORA-55474: internal error: [string],[string],[string]
Cause: There was an internal error with Resource Definition Framework (RDF) OLS/VPS support.
Action: Contact Oracle Support Services.
ORA-55475: policy with a matching name already exists
Cause: An attempt was made to specify a duplicate Oracle Virtual Private Database (VPD) policy name.
Action: Correct the input and try again.
ORA-55476: policy "string" does not exist
Cause: An attempt was made to use a nonexistent Oracle Virtual Private Database (VPD) policy.
Action: Correct the input and try again.
ORA-55477: policy with dependent models may not be dropped
Cause: An attempt was made to drop an Oracle Virtual Private Database (VPD) policy with dependent models.
Action: Remove the VPD policy from the models and try again.
ORA-55478: application table with multiple RDF models not suitable for VPD
Cause: An attempt was made to VPD-enable a model which shared the application table with another model.
Action: None
ORA-55479: a policy already assigned to the RDF model
Cause: An attempt was made to assign Oracle Virtual Private Database (VPD) policy to a model with a VPD policy already in effect.
Action: None
ORA-55480: model participating in a virtual model may not be VPD-enabled
Cause: An attempt was made to VPD-enable a model that participated in a virtual model.
Action: None
ORA-55481: VPD policy may not be applied for OLS-enabled RDF repository
Cause: An attempt was made to VPD-enable a model with an Oracle Label Security (OLS) policy already in effect.
Action: OLS and VPD may not be used simultaneously.
ORA-55482: VPD may not be applied to version-enabled RDF repository
Cause: An attempt was made to VPD-enable a version-enabled Resource Definition Framework (RDF) repository. This is not supported.
Action: None
ORA-55483: policy "string" not assigned to the model
Cause: An attempt was made to remove an Oracle Virtual Private Database (VPD) policy that was never assigned to the model.
Action: None
ORA-55484: circular dependency not allowed in RDF metadata
Cause: An attempt was made to define metadata elements that had a circular dependency for the Oracle Virtual Private Database (VPD) policy.
Action: Correct the input and try again.
ORA-55485: metadata may not be directly assigned to an equivalent property
Cause: An attempt was made to assign metadata directly to a property that was declared to be an equivalent of another.
Action: None
ORA-55486: metadata exists for the equivalent property
Cause: An attempt was made to make a property equivalent of another when some metadata already existed for this property.
Action: None
ORA-55487: VPD constraints exist for the equivalent property
Cause: An attempt was made to make a property equivalent of another when some Oracle Virtual Private Database (VPD) constraints already existed for this property.
Action: Correct the input and try again.
ORA-55488: metadata definition already exists for the policy
Cause: An attempt was made to add a duplicate metadata definition for an Oracle Virtual Private Database (VPD) policy.
Action: None
ORA-55489: conflicting metadata definition exists for the policy
Cause: An attempt was made to define conflicting metadata definitions for an Oracle Virtual Private Database (VPD) policy.
Action: Correct the input and try again.
ORA-55490: VPD constraint may not be assigned to an equivalent property
Cause: An attempt was made to assign an Oracle Virtual Private Database (VPD) constraint to a property declared to be an equivalent of another.
Action: Assign the VPD constraint to the property that is the target of the equivalent property.
ORA-55491: VPD policy constraint with matching name already exists
Cause: An attempt was made to specify a duplicate name for the Oracle Virtual Private Database (VPD) policy.
Action: Correct the input and try again.
ORA-55492: error creating VPD policy constraint: string
Cause: The Oracle Virtual Private Database (VPD) constraint had errors.
Action: See Oracle documentation.
ORA-55493: specified VPD policy constraint does not exist
Cause: An attempt was made to operate on an Oracle Virtual Private Database (VPD) constraint that did not exist.
Action: None
ORA-55494: input model set may only have a unique VPD policy
Cause: An attempt was made to execute a multi-model query where the models, as a set, did not have a unique Oracle Virtual Private Database (VPD) policy.
Action: Correct the input and try again.
ORA-55495: application table with multiple models may not be version-enabled
Cause: An attempt was made to version-enable an application table associated with multiple Resource Definition Framework (RDF) models.
Action: Correct the input and try again.
ORA-55496: unsupported versioning configuration (History/Valid time) for RDF data
Cause: An attempt was made to use an unsupported configuration for Resource Definition Framework (RDF) versioning.
Action: Correct the input and try again.
ORA-55497: RDF repository with an OLS policy may not be version-enabled
Cause: An attempt was made to version-enable a model with Oracle Label Security (OLS) policy.
Action: Versioning is not supported for OLS-enabled Resource Definition Framework (RDF) repository.
ORA-55498: VPD-enabled RDF model may not be version-enabled
Cause: An attempt was made to version-enable a model with an Oracle Virtual Private Database (VPD) policy in effect.
Action: Versioning of VPD-enabled Resource Definition Framework (RDF) models is not supported.
ORA-55501: Backing out live transaction
Cause: Flashback Transaction Backout was requested on a transaction that has not committed yet.
Action: Commit the transaction before using this feature.
ORA-55502: Specified input transaction by name has no SCN hint
Cause: The specified transaction names for Flashback Transaction Backout was missing an SCN hint.
Action: Provide an SCN hint, and guarantee that the named transactions start before the given SCN.
ORA-55503: Mining finished without seeing specified transactions
Cause: The SCN hit passed was not good. The SCN hit may have come after the start of any of the input transactions.
Action: Give a lesser and more conservative SCN hint, with greater probability of having seen the start of a transaction.
ORA-55504: Transaction conflicts in NOCASCADE mode
Cause: Transactions other than the ones specified conflicts with the specified transactions.
Action: Try using other options like NONCONFLICT_ONLY or CASCADE or NOCASCADE_FORCE.
ORA-55505: DDL done on an interesting object after mining start SCN
Cause: The Flashback Transaction Backout process encountered an interesting object which had its last DDL operation done on it after the mining start time. An interesting object is one that has been modified by either the specified transactions or any of their dependents.
Action: Specify transactions that have committed after the last DDL done on all the objects they touched.
ORA-55506: Transaction performed unsupported change
Cause: A transaction in the dependency DAG performed some
Action: The specified transaction cannot be backed out.
ORA-55507: Encountered mining error during Flashback Transaction Backout. function:string
Cause: Mining error.
Action: None
ORA-55508: Invalid input to Flashback Transaction Backout
Cause: Null varrays passed or invalid input specified
Action: Specify properly formed varrays and valid options
ORA-55509: Creation of dependencies could not finish
Cause: One or more input transaction or any of its dependents are not committed or have been aborted after more than 1 minute of calling the backout function.
Action: Commit all the active transactions associated with this table and try again.
ORA-55510: Mining could not start
Cause: Mining could not start for the following reasons.

1. A logminer session was processing

2. The database was not mounted or not opened for read and write

3. Minimum supplemental logging was not enabled

4. Archiving was not enabled

Action: Fix the mentioned problems and try again. Note that if you enable supplemental logging now, you will not be able to remove a transaction that has committed without supplemental logging.
ORA-55511: Flashback Transaction experienced error in executing undo SQL
Cause: There was a constraint violation exception when executing in NOCASCADE_FORCE mode. Users could also get this error if appropriate supplemental logging is not enabled causing constraint dependencies to go unnoticed.
Action: Either use CASCADE or NONCONFLICT_ONLY options or add appropriate level for supplemental logging.
ORA-55512: Backing out PDML or XA-RAC transaction
Cause: One of the transactions in the dependency graph was a PDML transaction or a local transaction which is a branch of a global XA transaction, spanning multiple RAC instances. Currently flashback transaction does not support this type of transaction.
Action: None
ORA-55513: Backing out an AQ transaction
Cause: One of the transactions in the dependency graph touched an AQ table. As AQ externalizes database information, these transactions are not backed out, as the entire effects of the transaction cannot be seen from inside the database.
Action: None
ORA-55514: Backing out a DDL transaction
Cause: One of the transactions in the dependency graph is a DDL transaction and could not be backed out.
Action: None
ORA-55515: Mining sees input transaction changes without seeing transaction start
Cause: The start SCN provided was higher than the transaction start but below the transaction commit. The result was only partial changes for the given transaction.
Action: Please provide a lower scn hint to flashback transaction.
ORA-55518: Mining across reset logs
Cause: Flashback Transaction Backout cannot work with missing changes. This error is thrown if we walk across a reset-logs branch, where we might have missed changes.
Action: If the user knows that the transaction happened in the current reset logs branch, then the SCN-hint is possibly incorrect. Provide an SCN in the current reset log branch.
ORA-55519: Supplemental logging not available for mining SCN range
Cause: Flashback Transaction cannot work if there are regions in the mining range where supplemental logging is not enabled.
Action: If you have provided a SCN/time hint which is approximate and far beyond the specified transaction start time, then readjust the SCN hint and try again. If the system has figured out the transaction start time or you are sure of the range, then the specified transaction cannot be backed out.
ORA-55520: Log record in compatibility lower than 11.0
Cause: The logical change record shows that the compatibility of the mined redo is lower than version 11.0. Flashback transaction works only on redo versions 11.0 and above.
Action: Advance the compatibility and try to back out transactions that have occurred after the compatibility increase.
ORA-55557: Trigger 4144 corruption
Cause: Above events used for testing corruption path
Action: None
ORA-55558: string is not a corrupted transaction
Cause: the given transaction is not in the corrupt list v$corrupt_xid_list
Action: check v$corrupt_xid_list
ORA-55563: number is not a valid undo segment number
Cause: the given usn is not a valid one
Action: check undo$
ORA-55564: string is not a valid transaction id
Cause: the given txn is not a valid one
Action: check txn id
ORA-55565: string is not a valid undo segment number
Cause: the given usn is not a valid one
Action: check undo$
ORA-55566: SQL statement issued when the database was not open for queries
Cause: Tried to access SMON time zone information when database was not open for queries.
Action: Reissue the SQL statement after the database is open for queries.
ORA-55567: The _highthreshold_undoretention value should be at least string based on the current undo retention settings.
Cause: The _highthreshold_undoretention value was not greater than or equal to the UNDO_RETENTION setting and the low threshold value used for tuning undo retention.
Action: Reissue the SQL statement with a higher value.
ORA-55568: The maximum query length (mql) value should be atmost string based on the current _highthreshold_undoretention setting.
Cause: The maximum query length (mql in minutes) was not less than or equal to half the _highthreshold_undoretention parameter setting.
Action: Reissue the SQL statement with a lower value for mql or increase the value of _highthreshold_undoretention parameter.
ORA-55569: The UNDO_RETENTION parameter value should be atmost string, the _highthreshold_undoretention setting.
Cause: The UNDO_RETENTION parameter value was not less than or equal to the _highthreshold_undoretention parameter setting.
Action: Reissue the SQL statement with a lower value for UNDO_RETENTION parameter or increase the value of _highthreshold_undoretention parameter.
ORA-55600: The table "string"."string" is already enabled for Flashback Archive
Cause: The specified table is already enabled for Flashback Archive.
Action: No action required.
ORA-55601: The table "string"."string" cannot be enabled for Flashback Archive
Cause: An attempt is made to enable Flashback Archive for a table which should never be enabled for Flashback Archive.
Action: Check the table name.
ORA-55602: The table "string"."string" is not enabled for Flashback Archive
Cause: An attempt was made to perform Flashback Archive operation on a table on which Flashback Archive is not enabled.
Action: Check the table name.
ORA-55603: Invalid Flashback Archive command
Cause: An invalid Flashback Archive command was specified.
Action: Check the SQL statement.
ORA-55604: Incorrect tablespace is specified
Cause: An incorrect tablespace is specified for the Flashback Archive.
Action: Check the SQL statement and verify the possible causes, 1, the tablespace that was already used by the Flashback Archive. 2, the tablespace was not used by the Flashback Archive. 3, the tablespace block size is less than 8K.
ORA-55605: Incorrect Flashback Archive is specified
Cause: An attempt was made to operate on a Flashback Archive that does not exist, or to create a Flashback Archive that already exists.
Action: Check the SQL statement.
ORA-55606: Event to modify archiver sleep time in seconds
Cause: 30 seconds is recommended as the archiver sleep time for tests.
Action: The default archiver sleep time is 300 seconds
ORA-55607: Event to enable debugging of archiver
Cause: The purpose of this event is for debugging.
Action: Attach to process specified.
ORA-55608: Default Flashback Archive does not exist
Cause: The default Flashback Archive did not exist.
Action: Create the default Flashback Archive first.
ORA-55609: Attempt to create duplicate default Flashback Archive
Cause: An attempt was made to create a default Flashback Archive while one already exists.
Action: No action required.
ORA-55610: Invalid DDL statement on history-tracked table
Cause: An attempt was made to perform certain DDL statement that is disallowed on tables that are enabled for Flashback Archive.
Action: No action required.
ORA-55611: No privilege to manage default Flashback Archive
Cause: An attempt was made to create, alter, or drop the default Flashback Archive.
Action: No action required.
ORA-55612: No privilege to manage Flashback Archive
Cause: An attempt was made to create, alter, or drop a Flashback Archive.
Action: No action required.
ORA-55613: Invalid Flashback Archive quota size
Cause: An attempt was made to specify invalid Flashback Archive quota size.
Action: Specify size in MB, GB, TB, PB, or EB.
ORA-55614: AUM needed for transactions on tracked tables
Cause: An attempt was made to execute DML on a tracked table without enabling Auto Undo Management.
Action: Disable tracking on the table or enable Auto Undo Management.
ORA-55615: Event to test archiver scheduled internal tasks
Cause: The purpose of this event is for testing.
Action: No action required.
ORA-55616: Transaction table needs Flashback Archiver processing
Cause: Too many transaction table slots were being taken by transactions on tracked tables.
Action: Wait for some amount of time before doing tracked transactions.
ORA-55617: Flashback Archive "string" runs out of space and tracking on "string" is suspended
Cause: Flashback archive tablespace quota is running out.
Action: Add tablespace or increase tablespace quota for the flashback archive.
ORA-55618: Insufficient privilege to grant Flashback Archive privilege
Cause: An attempt was made to grant Flashback Archive privilege.
Action: No action required.
ORA-55619: Invalid privilege to grant on Flashback Archive
Cause: An attempt was made to grant invalid privilege on a Flashback Archive object.
Action: Specify valid privilege.
ORA-55620: No privilege to use Flashback Archive
Cause: An attempt was made to enable Flashback Archive on a table without such privileges.
Action: No action required.
ORA-55621: User quota on tablespace "string" is not enough for Flashback Archive
Cause: An attempt was made to create or alter a Flashback Archive quota which is larger than the user's quota.
Action: No action required.
ORA-55622: DML, ALTER and CREATE UNIQUE INDEX operations are not allowed on table "string"."string"
Cause: An attempt was made to write to or alter or create unique index on a Flashback Archive internal table.
Action: No action required. Only Oracle is allowed to perform such operations on Flashback Archive internal tables.
ORA-55623: Flashback Archive "string" is blocking and tracking on all tables is suspended
Cause: Flashback archive tablespace has run out of space.
Action: Add tablespace or increase tablespace quota for the flashback archive.
ORA-55624: The table "string"."string" cannot be enabled for Flashback Archive at this point
Cause: An attempt was made to enable Flashback Archive again on a table which was just disabled.
Action: Try again later.
ORA-55625: Cannot grant Flashback Archive privilege to a role
Cause: An attempt was made to grant or revoke Flashback Archive privilege to a role.
Action: No action required.
ORA-55626: Cannot remove the Flashback Archive's primary tablespace
Cause: An attempt was made to remove the primary tablespace of the Flashback Archive.
Action: No action required.
ORA-55627: Flashback Archive tablespace must be ASSM tablespace
Cause: An attempt was made to add a tablespace that was not an ASSM tablespace.
Action: Add tablespace that is created with segment space management auto.
ORA-55628: Flashback Archive supports Oracle 11g or higher
Cause: An attempt was made to created a Flashback Archive with incorrect compatible mode or without auto undo management.
Action: Use compatible mode equal to 11.0 or higher, and use auto undo management.
ORA-55629: Event to test Flashback Archiver internal management tasks
Cause: The purpose of this event is for testing.
Action: No action required.
ORA-55630: Flashback Data Archive cannot be enabled on this object
Cause: An attempt was made to enable Flashback Data Archive on an object which is not supported by Flashback Data Archive.
Action: Do not use Flashback Archive clause for this object.
ORA-55631: Table has columns with data types that are not supported by Flashback Data Archive
Cause: An attempt was made to add a column of data type that is not supported by Flashback Data Archive. Or, the table on which Flashback Data Archive is being enabled contains column(s) with data types not supported by Flashback Data Archive.
Action: Do not use FLASHBACK ARCHIVE clause for this object. If adding column, do not use LONG or Nested Table column data type.
ORA-55632: Tablespace has Flashback Archive tables
Cause: An attempt was made to remove a tablespace that has Flashback Archive tables.
Action: No action required.
ORA-55633: Cannot do DDL on Flashback Data Archive enabled table
Cause: An attempt was made to do DDL on tracked tables while one DDL is runnning.
Action: Retry the DDL at a later time.
ORA-55634: Unable to disassociate or re-associate Flashback Data Archive table "string"."string"
Cause: Either an incorrect table name was used or an exclusive lock on the table could not be acquired.
Action: Check the table name and release locks on the table.
ORA-55635: Flashback Data Archive enabled table "string"."string" is disassociated
Cause: An attempt was made to perform operation on a Flashback Data Archive enabled table that is currently disassociated for DDL.
Action: Retry the operation at a later time.
ORA-55636: Flashback Data Archive enabled table "string"."string" has different definition from its history table
Cause: The Flashback Data Archive enabled table has different table definition from its history table.
Action: Fix the table definition.
ORA-55637: Flashback Data Archive enabled table "string"."string" is not in the correct compliance mode for this operation
Cause: An attempt was made to perform disassociation operation on a Flashback Data Archive enabled table that is in compliance mode. Or, DDL are not supported on tables in noncompliance mode.
Action: Disable compliance mode before retrying the disassociation operation.
ORA-55638: DDL operations on Flashback Data Archive-enabled table are not allowed at this point
Cause: Flashback Data Archive could not acquire resources to complete the operation on Oracle RAC.
Action: Retry the DDL at a later time.
ORA-55639: Flashback Data Archive internal SQL error
Cause: Flashback Data Archive encountered internal SQL error.
Action: No action required.
ORA-55640: Insufficient privilege to perform the Flashback Data Archive operation
Cause: An attempt was made to disassociate tables enabled for Flashback Data Archive without the required privilege.
Action: No action required.
ORA-55641: Cannot drop tablespace used by Flashback Data Archive
Cause: An attempt was made to drop a Flashback Data Archive tablespace.
Action: Remove the tablespace from Flashback Data Archive before retrying the operation.
ORA-55642: Table has column names that are reserved by Flashback Data Archive
Cause: The table on which Flashback Data Archive is being enabled contains column(s) with names that are reserved by Flashback Data Archive.
Action: Rename column name before retry.
ORA-55710: Unable to alter system parameter GLOBAL_TXN_PROCESSES at this time
Cause: The system was in the process of adjusting the number of global transaction background processes.
Action: Retry the operation at a later time.
ORA-55711: Unable to bind clusterwide global transactions to compatible undo
Cause: Undo tablespace was not onlined for automatic undo management.
Action: Create undo tablespace if it has not been created.
ORA-55712: XA transactions on RAC are not supported with GLOBAL_TXN_PROCESSES set to 0
Cause: The initialization parameter GLOBAL_TXN_PROCESSES was set to 0.
Action: Set the initialization parameter GLOBAL_TXN_PROCESSES to a value greater than 0.
ORA-55713: GLOBAL_TXN_PROCESSES cannot be set to 0 at runtime
Cause: An attempt was made to set initialization parameter GLOBAL_TXN_PROCESSES to 0 at runtime.
Action: Set the initialization parameter GLOBAL_TXN_PROCESSES to 0 before starting RAC instance to disable GTX background processes. Note that XA transactions are not supported on RAC database when GTX background processes are disabled.
ORA-55714: savepoint 'string' disabled with interleaved changes across Oracle RAC instances
Cause: After the savepoints were established, interleaved changes were made across Oracle RAC instances within the clusterwide global transaction.
Action: Do not make interleaved changes across Oracle RAC instances after savepoints are established.
ORA-55800: NLS errors while processing Oracle number
Cause: Error occurred when trying to convert Oracle number to an integer.
Action: Check the input parameters.
ORA-55801: Event to control CR activity
Cause: The bit values that we consider. 0x1: Remove fix for bug 3514835 which could potentially throw more 8177 errors We have conservatively blocked some serializability errors, where there could potentially be a dependency between a service transaction in an index and forward going transaction.
Action: Set event 55801 to 1 to disable the bug fix, thereby reducing 8177 error, although it might cause some internal errors instead.
ORA-56500: DRCP: Pool not found
Cause: The pool name passed was either null or an invalid pool name.
Action: Input a valid pool name.
ORA-56501: DRCP: Pool startup failed
Cause: The connection pool failed to start up.
Action: Check logs for details.
ORA-56502: DRCP: Pool is inactive
Cause: The operation is only supported on an active pool.
Action: Start the pool.
ORA-56503: DRCP: Pool is active
Cause: The operation is only supported on an inactive pool.
Action: Shutdown the pool.
ORA-56504: DRCP: Invalid pool configuration parameter name
Cause: The configuration paramter name is null or invalid input.
Action: Input a valid configuration parameter name.
ORA-56505: DRCP: Invalid pool configuration parameter value
Cause: The configuration paramter value is null or invalid input.
Action: Input a valid configuration parameter value.
ORA-56506: DRCP: Pool shutdown failed
Cause: Connection pool failed to shutdown.
Action: Check logs for details.
ORA-56507: DRCP: Pool alter configuration failed
Cause: Connection pool failed to configure pool.
Action: Check logs for details.
ORA-56508: DRCP: Pool startup failed
Cause: Connection Broker failed to startup the pool.
Action: Check logs for details.
ORA-56509: DRCP: Pool shutdown failed
Cause: Connection Broker failed to shutdown the pool.
Action: Check logs for details.
ORA-56510: DRCP: Pool alter configuration failed
Cause: Connection Broker failed to configure the pool.
Action: Check logs for details.
ORA-56511: DRCP: Cross instance synchronization failed
Cause: Publish message to all RAC instances failed.
Action: Check logs for details.
ORA-56512: DRCP: Failed to synchronize RAC instances [string]
Cause: Some of the RAC instances were not synchronized.
Action: Perform the same operations on all the failed instances.
ORA-56513: DRCP: Cannot perform requested operation using pooled connection
Cause: This operation was not supported using connections from a pool.
Action: Use a regular connection to perform this operation.
ORA-56514: DRCP: invalid value for maximum number of connections to Connection broker
Cause: The value passed exceeded the maximum allowed.
Action: No action required. The maximum number of connections was automatically set to the maximum allowed value.
ORA-56600: DRCP: Illegal call [string]
Cause: An illegal OCI function call was issued.
Action: Check the documentation for Database Resident Connection Pool (DRCP) usage.
ORA-56601: DRCP: Illegal connection class
Cause: Wrong value for connection class was given.
Action: Check the documentation for Database Resident connection pool usage.
ORA-56602: DRCP: Illegal purity
Cause: Wrong value for purity was provided.
Action: Check the documentation for Database Resident connection pool usage.
ORA-56603: DRCP: Internal error
Cause: Malformed input values.
Action: Input well-formed values.
ORA-56604: DRCP: Length[string] for string exceeded the MAX allowed
Cause: Length exceeded MAX for the value.
Action: Use a value within the MAX allowed.
ORA-56605: DRCP: Session switching and migration not allowed
Cause: Application tried to switch or migrate session across connections.
Action: This usage is irrelevant in the Database Resident connection pooling context and is not supported. Release existing session.
ORA-56606: DRCP: Client version does not support the feature
Cause: The client version is lower than 11g.
Action: Upgrade to a higher client version or turn off (SERVER=POOLED) in the connect string.
ORA-56607: DRCP: Connection is already authenticated
Cause: Attempt to reauthenticate the connection which is authenticated.
Action: Logoff the connection before reauthenticating.
ORA-56608: DRCP: Server Group feature is not supported
Cause: Server Group attribute was set on the server handle, connected to a Database Resident connection pool.
Action: Do not set Server Group attribute on server handles while using Database Resident connection pool.
ORA-56609: Usage not supported with DRCP
Cause: This usage was not supported on a DRCP connection.
Action: Use a dedicated connection to perform this task.
ORA-56700: plan string is a subplan and SUB_PLAN attribute cannot be modified
Cause: An attempt was made to modify the SUB_PLAN attribute of the specified plan.
Action: Do not attempt to modify the SUB_PLAN attribute.
ORA-56701: INTERNAL_USE attribute of consumer group string cannot be modified
Cause: An attempt was made to modify the INTERNAL_USE attribute of the specified consumer group.
Action: Do not attempt to modify the INTERNAL_USE attribute.
ORA-56702: consumer group string is for internal use only and cannot be a switch target
Cause: An attempt was made to specify an INTERNAL_USE consumer group as a switch target.
Action: Do not attempt to switch to INTERNAL_USE consumer groups.
ORA-56703: VKTM process died unexpectedly
Cause: An explicit kill or internal error caused the death of VKTM background process.
Action: Restart the instance.
ORA-56704: EXPLICIT consumer group mapping priority must be set to 1
Cause: An attempt was made to set the EXPLICIT mapping priority to a value other than 1.
Action: Set the mapping priorities to unique integers within the documented range with the EXPLICT priority set to 1.
ORA-56705: I/O calibration already in progress
Cause: An attempt was made to run a second instance of I/O Calibration
Action: Wait until the first I/O calibration run is complete; then, retry the operation.
ORA-56706: The specified Resource Manager plan is a subplan and cannot be set as a top-level plan
Cause: An attempt was made to set a subplan as a top-level plan.
Action: Do not attempt to set subplans as top-level plans.
ORA-56707: INTERNAL_QUIESCE plan cannot be specified as a top-level Resource Manager plan
Cause: An attempt was made to specify INTERNAL_QUIESCE as a top-level Resource Manager plan.
Action: Do not attempt to set INTERNAL_QUIESCE as a Resource Manager plan.
ORA-56708: Could not find any datafiles with asynchronous i/o capability
Cause: There are no datafiles which are asynchronous I/O capable.
Action: Make sure asynchronous i/o is permitted to datafiles.
ORA-56709: timed_statistics set to FALSE
Cause: timed_statistics parameter in database is set to FALSE. Needs to be enabled for calibration.
Action: set timed_statistics=TRUE in init.ora or "alter system set timed_statistics=TRUE"
ORA-56710: DBRM process died unexpectedly
Cause: An explicit kill or internal error caused the death of the DBRM background process.
Action: Restart the instance.
ORA-56711: string is an invalid string argument
Cause: The named argument is invalid.
Action: Specify a valid argument for this procedure.
ORA-56713: Insufficient Resource Manager privileges
Cause: An attempt was made to switch the consumer group of a user without the appropriate privilege.
Action: Ask the database administrator to perform the switch operation or grant switch or system privilege to the user.
ORA-56714: Plan name string exceeds the maximum length allowed
Cause: Plan name is greater than 30 characters long.
Action: Do not exceed 30 characters when naming a resource plan.
ORA-56715: string resource plan contains a reserved word
Cause: The specified plan name is prefixed with a reserved prefix such as FORCE or SCHED.
Action: Do not prefix resource plan name with FORCE or SCHED.
ORA-56716: Category string does not exist
Cause: A non-existent category was specified as an argument to a procedure in the package, DBMS_RESOURCE_MANAGER.
Action: Specify an existing category name or create a new category with this name.
ORA-56717: SWITCH_TIME is set without specifying SWITCH_GROUP
Cause: The plan directive specifies a SWITCH_TIME without a SWITCH_GROUP.
Action: Specify a SWITCH_GROUP parameter in the plan directive.
ORA-56718: Timeout occurred while setting resource plan
Cause: A timeout occurred while waiting for one or more RAC instances to set the resource plan.
Action: Since the resource plan may have actually been set successfully, first check the current resource plan for each instance by querying gv$rsrc_plan. If the resource plan was not successfully set on all instances, then retry the operation.
ORA-56719: Error spawning or communicating with calibration slave
Cause: An error occurred in calibration slave process - Calibration process aborted.
Action: Review trace files for errors.
ORA-56720: I/O data limit exceeded - call aborted
Cause: The Resource Manager SWITCH_IO_MEGABYTES limit was exceeded.
Action: Reduce the complexity of the update or query, or contact your database administrator for more information.
ORA-56721: I/O data limit exceeded - session terminated
Cause: The Resource Manager SWITCH_IO_MEGABYTES limit was exceeded.
Action: Reduce the complexity of the update or query, or contact your database administrator for more information.
ORA-56722: I/O request limit exceeded - call aborted
Cause: The Resource Manager SWITCH_IO_REQS limit was exceeded.
Action: Reduce the complexity of the update or query, or contact your database administrator for more information.
ORA-56723: I/O request limit exceeded - session terminated
Cause: The Resource Manager SWITCH_IO_REQS limit was exceeded.
Action: Reduce the complexity of the update or query, or contact your database administrator for more information.
ORA-56725: Could not spawn additional calibration slaves
Cause: An error occurred when spawning calibration slave process - Calibration process aborted.
Action: Check OS resources required for spawning processes
ORA-56726: Category string is referred to by a consumer group and cannot be deleted
Cause: An attempt was made to delete a category that is referred to by a consumer group.
Action: Modify or remove all consumer groups that use this category and then retry.
ORA-56727: Orion (string) must be invoked using its full, absolute path
Cause: Orion is spawning a child process and cannot determine the location of the executable.
Action: Use the full, absolute path for Orion.
ORA-56728: SQL blocks cannot be nested
Cause: An attempt was made to start an SQL block using DBMS_RESOURCE_MANAGER.BEGIN_SQL_BLOCK() while already inside an SQL block.
Action: Close the existing SQL block using DBMS_RESOURCE_MANAGER.BEGIN_SQL_BLOCK() or remove this call.
ORA-56729: Failed to bind the database instance to processor group string
Cause: Binding the database instance to the processor group specified by the PROCESSOR_GROUP_NAME parameter failed.
Action: Set the PROCESSOR_GROUP_NAME to a valid, configured processor group and restart the database instance.
ORA-56800: DSKM process died unexpectedly
Cause: An explicit kill or internal error caused the death of the DSKM background process.
Action: Restart the instance.
ORA-56840: LIBCELL API error in Master Diskmon
Cause: A LIBCELL operation in Master Diskmon failed.
Action: Look in the $ORA_CRS_HOME/log/<hostname>/diskmon/diskmon.log file for additional error information.
ORA-56841: Master Diskmon cannot connect to a CELL
Cause: A LIBCELL operation from Master Diskmon failed to create a network connection to the target CELL.
Action: Look in the $ORA_CRS_HOME/log/<hostname>/diskmon/diskmon.log file for additional error information.
ORA-56842: LIBCELL operation network error in Master Diskmon
Cause: A LIBCELL operation in Master Diskmon failed because of a network error.
Action: Look in the $ORA_CRS_HOME/log/<hostname>/diskmon/diskmon.log file for additional error information.
ORA-56843: LIBCELL SKGXP error in Master Diskmon
Cause: A LIBCELL operation from Master Diskmon failed because of an SKGXP network layer error.
Action: Look in the $ORA_CRS_HOME/log/<hostname>/diskmon/diskmon.log file for additional error information.
ORA-56864: Master Diskmon "stringstring" operation cannot complete because of a LIBCELL network error
Cause: A LIBCELL operation between Master Diskmon and a CELL failed because of a network error.
Action: Look in the $ORA_CRS_HOME/log/<hostname>/diskmon/diskmon.log file for additional error information.
ORA-56865: Invalid IP address in CELLINIT.ORA
Cause: One or more of the specified IP addresses in CELLINIT.ORA is not valid.
Action: Check that all IP addresses in CELLINIT.ORA are valid.
I ORA-56866: No IP parameter
Cause: No IP address is set in CELLINIT.ORA.
Action: Check that one or more valid IP addresses are set in CELLINIT.ORA.
ORA-56867: Cannot connect to Master Diskmon on pipe "string"
Cause: Master Diskmon was not running or the listening pipe was deleted.
Action: Look at the $ORA_CRS_HOME/log/<hostname>/diskmon/diskmon.log, $ORA_CRS_HOME/log/<hostname>/hasmsgs.log and $ORA_CRS_HOME/log/<hostname>/alert<hostname>.log for additional error information.
ORA-56868: Duplicate IP address in CELLINIT.ORA
Cause: One or more of the specified IP addresses in CELLINIT.ORA was repeated.
Action: Check that all IP addresses in CELLINIT.ORA are unique.
ORA-56870: Attempt to register dead cell with Master Diskmon
Cause: An attempt was made by a process to register a cell that is known to be down.
Action: None
ORA-56900: bind variable is not supported inside pivot|unpivot operation
Cause: Attempted to use bind variables inside pivot|unpivot operation.
Action: This is not supported.
ORA-56901: non-constant expression is not allowed for pivot|unpivot values
Cause: Attempted to use non-constant expression for pivot|unpivot values.
Action: Use constants for pivot|unpivot values.
ORA-56902: expect aggregate function inside pivot operation
Cause: Attempted to use non-aggregate expression inside pivot operation.
Action: Use aggregate function.
ORA-56903: sys_op_pivot function is not allowed here
Cause: invalid use of sys_op_pivot function.
Action: Remove sys_op_pivot function.
ORA-56904: pivot value must have datatype that is convertible to pivot column
Cause: Datatype of pivot value is not convertible to the datatype of pivot column.
Action: Check and correct pivot value.
ORA-56920: a prepare or upgrade window or an on-demand or datapump-job loading of a secondary time zone data file is in an active state
Cause: A prepare or upgrade window was started or an on-demand or datapump-job loading of a secondary time zone data file was done.
Action: Make sure there is no active prepare or upgrade window and no active on-demand or datapump-job loading of a secondary time zone data file.
ORA-56921: invalid time zone version
Cause: Invalid time zone version passed.
Action: Check and correct the time zone version.
ORA-56922: Starting a prepare window failed
Cause: Error(s) occurred when starting a prepare window.
Action: Check alert or trace file for error(s).
ORA-56923: database properties related to time zone version are not set up properly
Cause: There were no database properties related to time zone version in dictionary table sys.props$.
Action: Contact Oracle Support Services.
ORA-56924: prepare window does not exist
Cause: There was no active prepare window.
Action: None
ORA-56925: Ending a prepare window failed
Cause: Error(s) occurred when ending a prepare window.
Action: Check alert or trace file for error(s).
ORA-56926: database must be in UPGRADE mode in order to start an upgrade window
Cause: Database was not in UPGRADE mode.
Action: Restart database in UPGRADE mode.
ORA-56927: Starting an upgrade window failed
Cause: Error(s) occurred when starting an upgrade window.
Action: Check alert or trace file for error(s).
ORA-56928: upgrade window does not exist
Cause: There was no active upgrade window.
Action: None
ORA-56929: Ending an upgrade window failed
Cause: Ending an upgrade window failed or there were tables containing TSTZ data which have not been upgraded.
Action: Check alert or trace file for error(s) or complete upgrading of tables containing TSTZ data.
ORA-56930: database must be restarted before performing upgrade of user tables
Cause: Database was not restarted after starting an upgrade window.
Action: Restart database.
ORA-56931: inconsistent DST patching state found
Cause: DST patching was in an inconsistent state.
Action: Contact Oracle Support Services.
ORA-56932: "string"."string" does not exist
Cause: Specified table name was invalid.
Action: Check the existence of the specified table name.
ORA-56933: Table creation failed
Cause: Error(s) occurred when creating the table.
Action: Check the error.
ORA-56934: database property DST_UPGRADE_STATE for datapump job is in an inconsistent state
Cause: Database property DST_UPRGRADE_STATE was not recorded correctly.
Action: Check the alert file.
ORA-56935: existing datapump jobs are using a different version of time zone data file
Cause: An attempt was made from a datapump job to request a different version of time zone data file from the one used by existing datapump jobs.
Action: Wait until existing datapump jobs unload the secondary time zone data file.
ORA-56936: datapump jobs are utilizing secondary time zone data file
Cause: An on-demand loading of secondary time zone data file was requested when there was a secondary time zone data file already loaded in the database utilized by existing datapump jobs.
Action: Wait until existing datapump jobs unload the secondary time zone data file.
ORA-56937: failed to load the secondary time zone data file
Cause: Attempt to load the secondary timezone data file failed.
Action: Check alert or trace files for error(s).
ORA-56938: no secondary time zone data file being loaded by on-demand or a datapump job
Cause: There was no secondary timezone data file being loaded by on-demand or a datapump job.
Action: None
ORA-56939: failed to unload the secondary time zone data file
Cause: Attempt to unload the secondary timezone data file failed.
Action: Check alert or trace files for error(s).
ORA-56950: Invalid value for incident identifier
Cause: Invalid incident identifier argument passed.
Action: Check and correct the identifier
ORA-56971: Invalid set of export options
Cause: The options specified are inconsistent
Action: Check and a consistent set of option parameters
ORA-56972: referenced file not found
Cause: One of the file specified in the test case package is mising
Action: rebuild the SQL test case or make sure that all the referenced files are readable and located in the same directory as the SQL test case manifest.
ORA-56973: import options do not match export options
Cause: The import options specified do not match the export options
Action: Check that import is being invoked with the same values for options like export environment, export data and export metadata
ORA-56974: Invalid set of import options
Cause: The import options specified are inconsistent
Action: Check that import options are consistent and have valid values
PKꀼPKjFJOEBPS/clsmdnsus.htmi: CLSMDNS-00000 to CLSMDNS-02255

58 CLSMDNS-00000 to CLSMDNS-02255

CLSMDNS-00000: no error
Cause: A command completely successfully.
Action: No action is needed.
CLSMDNS-00001: GIPC endpoint creation failed.
Cause: An attempt to create a GIPC endpoint for use multicast operations failed.
Action: Examine the accompanying error (if any) and the log file for details as to why the operation failed.
CLSMDNS-00002: bind failed.
Cause: An attempt to bind an address to a GIPC endpoint failed.
Action: Examine the accompanying error (if any) and the log file for details as to why the operation failed.
CLSMDNS-00003: address creation failed.
Cause: An attempt to create a GIPC address failed.
Action: Examine the accompanying error (if any) and the log file for details as to why the operation failed.
CLSMDNS-00004: attribute setting failed.
Cause: An attempt to set an attribute on a GIPC endpoint or address failed.
Action: Examine the accompanying error (if any) and the log file for details as to why the operation failed.
CLSMDNS-00005: interface registration failed.
Cause: The registration of an interface with mDNS failed.
Action: Examine the accompanying error (if any) and the log file for details as to why the operation failed.
CLSMDNS-00006: failed to get name server list.
Cause: An attempt to get the list of available name servers failed.
Action: Examine the accompanying error (if any) and the log file for details as to why the operation failed.
CLSMDNS-00007: mDNS initialization failed.
Cause: The initialization of the mDNS subsystem failed.
Action: Examine the accompanying error (if any) and the log file for details as to why the operation failed.
CLSMDNS-00008: start of host query failed.
Cause: The query for hosts from mDNS failed to start.
Action: Examine the accompanying error (if any) and the log file for details as to why the operation failed.
CLSMDNS-00009: stop of host query failed.
Cause: Termination of the query for hosts from mDNS failed.
Action: Examine the accompanying error (if any) and the log file for details as to why the operation failed.
CLSMDNS-00010: Initialization of name server name retrieval failed.
Cause: The initialization of the retrieval of the names of the name servers used by multicast DNS failed.
Action: Examine the accompanying messages(s) that detail the platform error(s) for details about the exception.
CLSMDNS-00011: retrieval of name server name failed.
Cause: The retrieval of the name of a name server to be used by multicast DNS failed.
Action: Examine the accompanying messages(s) that detail the platform error(s) for details about the exception.
CLSMDNS-00012: no name servers found.
Cause: No name servers were found that could be used by multicast DNS.
Action: Check the system configuration and ensure that or more DNS name servers are configured, operating and accessible.
CLSMDNS-00013: Send of response to DNS server failed.
Cause: An attempt to send a response to a query from the DNS server failed.
Action: Examine accompanying exceptions for details about the exact error.
CLSMDNS-00015: invalid record type: number
Cause: The DNS server sent a record whose type is unknown.
Action: This is a warning message which can be ignored because the error should occur very infrequently. If the error occurs frequently, Oracle Customer Support should be contacted.
CLSMDNS-02000: unknown error.
Cause: An unknown error occurred. This error can occur when the multicast DNS server is not running.
Action: If the multicast server is not running, start it and try the operation again. If it is running, this is an internal error and Oracle Customer Support should be contacted with details about how and when the error occurred.
CLSMDNS-02001: no such name exists.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02002: memory allocation failure.
Cause: The allocation of process memory failed.
Action: If memory is low on the system, terminate other processes and/or threads and try the operation again. Otherwise, this is an internal error and Oracle Customer Support should be contacted.
CLSMDNS-02003: invalid parameter.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02004: invalid reference.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02005: invalid state.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02006: invalid flags.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02007: operation is unsupported.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02008: uninitialized.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02009: no cache.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02010: record or service is already registered.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02011: name conflict found.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02012: Invalid.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02013: Firewall.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02014: Incompatible.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02015: invalid interface.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02016: Refused.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02017: no such record.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02018: no authentication.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02019: no such key.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02020: error occurred while passing through NAT.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02021: double NAT encountered.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02022: invalid time.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02023: invalid signature.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02024: invalid key.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02025: transient error.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02250: connection pending.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02251: connection failed.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02252: connection established.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02253: more memory needed for cache.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02254: configuration changed.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
CLSMDNS-02255: memory free needed.
Cause: This error is internal and should not ordinarily be seen by the user.
Action: Contact Oracle Customer Support.
PKu)iiPKjFJOEBPS/prcnmsg.htm PRCN-02018 to PRCN-03018

85 PRCN-02018 to PRCN-03018

PRCN-02018: Current user {0} is not a privileged user
Cause: Current user did not have sufficient privileges to perform this operation.
Action: Make sure that the user has root privileges on Linux/Unix's and Administrator on Windows.
PRCN-02030: Subnet does not exist for resource {0}
Cause: An attempt was made to query subnet for a network resource configured with Oracle clusterware and it was not found.
Action: Internal error. Contact Oracle Support.
PRCN-02031: Unknown DHCP server name {0} found for resource {1}
Cause: The DHCP server type obtained for the network resource is not a valid server type.
Action: Internal error. Contact Oracle Support.
PRCN-02032: Failed to retrieve DHCP server type {0}
Cause: An attempt to query the DHCP server type for the network resource failed because its value could not be retrieved from the Oracle clusterware resource attributes.
Action: make sure Oracle clusterware is up and running. and also look at the help for the accompanying CRS error message.
PRCN-02033: Failed to update DHCP server type to {0} {1}
Cause: An attempt to update the DHCP server type for the network resource failed because its value could not be updated in the Oracle Clusterware resource attribute.
Action: Make sure that the Clusterware stack is up. Make sure that the user has enough permission to modify node applications. Examine the accompanying message for additional details.
PRCN-02034: Could not find dependent resource {0} for resource {1}: {2}
Cause: Could not get the resource associated with a given resource. Could not get the ASM resource associated with a given ASM disk group resource.
Action: Make sure that clusterware stack is up. Make sure that the network resource associated with this resource has not been removed. Make sure that the user has permission to perform this operation.
PRCN-02035: Port {0} is not available on node(s) or virtual host(s): {1}
Cause: The port specified is already being used by some other applications on the nodes or virtual hosts given.
Action: Stop the applications that are using these ports or specify a different port and try the command again.
PRCN-02036: Failed to retrieve port number(s) for {0}
Cause: An attempt to retrieve the port number(s) for the cluster resource failed.
Action: Make sure that the clusterware stack is up. Make sure that the resource you are querying has been configured. Also take a look at the help for the accompanying error message(s).
PRCN-02037: Failed to retrieve Oracle home for {0}
Cause: An attempt to retrieve Oracle home value for the listener resource failed.
Action: Make sure that the clusterware stack is up. Make sure that listener is configured. If node name is being specified in the command line make sure that the node name is a valid node name. Also look at help for the accompanying error message(s).
PRCN-02038: Failed to update Oracle home {0} for listener {1}
Cause: An attempt to update the Oracle home value for the listener resource failed.
Action: Make sure that the clusterware stack is up. Make sure that the listener is configured. If node name is being specified in the command line make sure that the node name is a valid node name. Make sure that user is a owner or has write permissions to modify the listener resource. Also look at the help for other errors listed in error stack.
PRCN-02039: Failed to retrieve Oracle home for {0} on node {1}
Cause: An attempt to retrieve Oracle home value for the listener resource on a the specified node failed.
Action: Make sure that the clusterware stack is up. Make sure that the listener is configured on the node. Make sure that the node name being passed in the command line is a valid node name. Also look at the help for the accompanying error message(s).
PRCN-02040: Failed to update Oracle home {0} for {1} on node {2}
Cause: Attempt to update value of attribute Oracle home for listener resource on the specified node failed.
Action: Make sure that the clusterware stack is up. Make sure that the listener is configured on the node. Make sure that the user has enough permission to modify the listener. Make sure that the node name being passed in the command line is a valid node name. Also look at the help for other errors listed in error stack.
PRCN-02041: Failed to retrieve properties of {0}
Cause: Failed to retrieve properties of the given entity.
Action: Make sure that user has permission to read resource attribute.
PRCN-02042: Failed to set properties {0} of {1}
Cause: Failed to update properties of the given entity.
Action: Make sure that user has permission to update resource attribute.
PRCN-02043: Multiple network resources {0} exist on the cluster
Cause: More than one network resource has been configured and the one to be used for creating this resource has not been specified.
Action: Use command line option -k <net_num> argument to specify the network to be used and retry the command again.
PRCN-02044: No listener exists
Cause: No listener has been configured.
Action: Use netca or srvctl to add/configure a listener.
PRCN-02045: No network exists
Cause: No network has been configured.
Action: Use 'srvctl add nodeapps' to add/configure network resource.
PRCN-02046: Netmask does not exist for resource {0}
Cause: An attempt to retrieve the subnet information for the network resource resulted in not finding subnet mask.
Action: Internal error. Contact Oracle Support.
PRCN-02047: VIP {0} exists
Cause: The VIP with specified name has been registered in CRS.
Action: Remove the existing VIP before registering it again.
PRCN-02048: The network number {0} is already registered for subnet ''{3}'' and adapters ''{4}''. Can not add network number {0} for the specified subnet ''{1}'' and adapters ''{2}''.
Cause: The network number is taken by a registered network resource.
Action: Use a different network number to add a new network resource with the specified subnet and adapters, or modify existing network using 'srvctl modify nodeapps'.
PRCN-02049: The network attributes specified (network number: {0}, subnet: {1}, adapters: {2}) conflict with an already registered network (network number: {3}, subnet: {4}, adapters: {5})
Cause: The network resource is registered with different network number
Action: Use the registered network resource with the registered network number or provide different subnet or adapters.
PRCN-02050: The requested VIP (nodename: {0}, VIP name: {1}, network number: {2}) has the same VIP name but different network number or preferred node than the registered VIP (nodename: {3}, VIP name: {4}, network number: {5}).
Cause: One VIP name (and IP address) can only be used by one VIP with the same network number on the same node.
Action: Use a different VIP name or IP address.
PRCN-02051: The requested VIP (nodename: {0}, VIP name: {1}, network number: {2}) has the same network number and the same preferred node but different VIP name with the registered VIP (nodename: {3}, VIP name: {4}, network number: {5}).
Cause: One network resource on one preferred node can have only one cluster VIP.
Action: Use different network number or preferred node to register different VIP.
PRCN-02052: Failed to modify Network resource (network number: {0}) to use (subnet: {1}, netmask {2} adapters: {3}).
Cause: CRS was unable to modify the network resource to use new subnet/netmask/interface
Action: Make sure that clusterware stack is up. Make sure that the subnet, netmask and adapters value are correct. Make sure that the interface being referred to is running. Make sure that the user who is trying to modify network resource has root privileges. Examine the accompanying message for additional details.
PRCN-02053: Failed to modify ONS listening port for local client connections to {0}
Cause: CRS unable to modify the ONS listening port for local connections
Action: Make sure that clusterware stack is up. If the port is in use by another application, try using a different port.
PRCN-02054: Failed to modify ONS listening port for remote client connections to {0}
Cause: CRS unable to modify the ONS listening port for remote client connections
Action: Make sure that clusterware stack is up. If the port is in use by another application, try using a different port.
PRCN-02055: Failed to update port number(s) to {0} for {1}
Cause: An attempt to update the listener port failed for the nodes of the cluster.
Action: The port could be in use. Try using different port. If node name was specified in the command line make sure that the node name is a valid node name. Also look at the help for the accompanying error message(s).
PRCN-02056: Invalid listener protocol type {0}
Cause: The specified listener protocol type is invalid.
Action: Provide a valid listener protocol type. It can be TCP, TCPS, IPC, NMP, or SDP.
PRCN-02057: Invalid listener protocol value {0}
Cause: The specified listener protocol value is invalid.
Action: Provide a valid listener protocol value. It cannot contain special characters ':,/'
PRCN-02058: Invalid listener protocol ENDPOINTS {0}. Delimiter is "{1}", invalid part is "{2}".
Cause: The specified listener ENDPOINTS are invalid.
Action: Provide valid listener protocol ENDPOINTS. It cannot contain invalid part.
PRCN-02059: Invalid listener port number {0}
Cause: The specified listener port number is invalid.
Action: Provide a valid listener port number.
PRCN-02060: Duplicated listener protocol value {0}
Cause: The specified listener protocol value is a duplication of another one.
Action: Remove duplicated listener protocol value.
PRCN-02061: Failed to add listener {0}
Cause: An attempt to add listener failed because endpoints were not specified correctly or other reasons.
Action: Review the underlying error messages that provide the details of which resources failed to create. Check the cause and action for the individual resource creation failure. If the endpoints were not specified correctly, correct endpoints.
PRCN-02062: The specified hostname or address {0} cannot be resolved.
Cause: An invalid IP address or unresolvable hostname was specified.
Action: If IP address is specified then make sure that it is of legal length. If a host name is specified than make sure that the host name resolves to an IP address.
PRCN-02063: Failed to modify OC4J listening port to {0}
Cause: CRS unable to modify the OC4J instances listening port.
Action: Make sure that clusterware stack is up. If the port is in use by another application, try using a different port.
PRCN-02064: Found {0} VIPs for {1}
Cause: A conflict was found in VIP resource definition: either more than one VIP is using the same name or address, or a VIP is using the same name or address as a real host.
Action: Ensure that each VIP is defined with a distinct name and address relative to other VIPs and hosts in the network.
PRCN-02065: Port(s) {0} are not available on the nodes given
Cause: The ports specified are already being used by some other applications on the nodes given.
Action: Stop the applications that are using these ports or specify different ports and try the command again.
PRCN-02066: Failed to retrieve cluster listener for {0} because it has the type of Single Client Access Name Listener
Cause: Failed to use cluster listener APIs or srvctl commands for specified listener.
Action: Use Single Client Access Name Listener (SCAN listener) APIs or srvctl commands (srvctl <verb> scan_listener) for specified listener name.
PRCN-02067: Port {0} is not available across node(s) "{1}"
Cause: The port specified is already being used by some other applications across the nodes given.
Action: Stop the application that is using this port or specify a different port and try the command again.
PRCN-02068: Failed to check the port availability
Cause: This is an internal error.
Action: Contact Oracle Support Services.
PRCN-02069: Unable to retrieve the list of nodes
Cause: This is an internal error.
Action: Contact Oracle Support Services.
PRCN-02070: Failed to validate network. No interface on {0} matches required network (subnet: {1}, netmask: {2} adapters: {3}).
Cause: The nodes don't have the configuration for the required network.
Action: Specify a subnet that exists on all nodes, or reconfigure the nodes to ensure that the specified subnet exists on all nodes.
PRCN-02071: Failed to update attribute USE_EVM to {0}
Cause: An attempt to update the attribute value of USE_EVM for ONS failed.
Action: Examine the accompanying error message(s) and respond accordingly.
PRCN-02072: Failed to get multicast port for events from EONS
Cause: An attempt to get multicast port for events from EONS failed.
Action: Examine the accompanying error message(s) and respond accordingly.
PRCN-02073: Failed to remove EONS
Cause: An attempt to remove EONS failed.
Action: Examine the accompanying error message(s) and respond accordingly.
PRCN-02074: Specified check interval of {0} minutes is below the minimum check interval {1} minutes
Cause: The CVU resource check interval specified was less than the minimum check interval.
Action: Retry the operation with a interval greater than or equal to the minimum check interval.
PRCN-02075: Failed to modify the CVU CHECK_INTERVAL attribute to {0}
Cause: CRS was unable to modify the CVU CHECK_INTERVAL attribute.
Action: Make sure that Clusterware stack is up. Make sure that user is an owner or has write permissions to modify the CVU resource. Check for and respond to any accompanying error messages.
PRCN-02076: Failed to retrieve the CVU CHECK_INTERVAL attribute for "{0}"
Cause: An attempt to retrieve the CHECK_INTERVAL for the CVU cluster resource failed.
Action: Make sure that the Clusterware stack is up. Make sure that the CVU resource has been configured. Check for and respond to any accompanying error messages.
PRCN-02077: Failed to modify the CVU CHECK_RESULTS attribute to "{0}"
Cause: CRS was unable to modify the CVU CHECK_RESULTS 5 attribute.
Action: Make sure that Clusterware stack is up. Make sure that the CVU resource has been configured. Check for and respond to any accompanying error messages.
PRCN-02078: Failed to retrieve the CVU CHECK_RESULTS for "{0}"
Cause: An attempt to retrieve the CHECK_RESULTS atribute for the CVU cluster resource failed.
Action: Make sure that the Clusterware stack is up. Make sure that the CVU resource has been configured. Check for and respond to any accompanying error messages.
PRCN-02079: Port {0} is out of the valid range, between 1 and 65535 and cannot be used on any of the nodes given
Cause: The port number that was provided was either less than 1 or greater than 65535.
Action: Make sure the port provided has a value between 1 and 65535.
PRCN-03000: The IPMI configuration failed on all nodes
Cause: The node names were invalid or were valid but had no IPMI device present.
Action: Make sure that all nodes are reachable and the IPMI device exists on those nodes.
PRCN-03001: The IPMI configuration failed on one or more nodes
Cause: There was at least one node with invalid name or with no IPMI device.
Action: Make sure that all nodes are reachable and the IPMI device exists on those nodes.
PRCN-03002: There is no network resource configured for the cluster
Cause: A request to add a listener was rejected due to the lack of a network resource.
Action: Use command 'srvctl add network' to configure the network first, then retry the command.
PRCN-03003: Failed to unregister EONS resource type
Cause: A request to unregister the EONS resource type failed because of the reason provided by an accompanying exception message.
Action: Examine the accompanying error message for details.
PRCN-03004: Listener {0} already exists
Cause: The specified listener was already created.
Action: Use 'srvctl modify listener' to modify attributes if needed.
PRCN-03005: Failed to add or use registered network {0} with network interfaces ''{1}'' because the network was already registered for network interfaces ''{2}''
Cause: The network resource was already registered with different interfaces.
Action: Use the same network interfaces as the one registered with network resource.
PRCN-03006: Failed to add or use registered network {0} with network interfaces ''{1}'' because the network was already registered with no interface specified
Cause: The network resource was already registered with no user specified interface.
Action: Do not specify network interface as the system decides the network interface.
PRCN-03007: Failed to add or use registered network {0} with network mask ''{1}'' because the network was already registered for network mask ''{2}''
Cause: The network resource was already registered with a different network mask.
Action: Use the same network mask as the one registered with network resource.
PRCN-03008: Failed to add or use registered network {0} with network subnet ''{1}'' because the network was already registered for network subnet ''{2}''
Cause: The network resource was already registered with a different network subnet.
Action: Use the same network subnet as the one registered with network resource.
PRCN-03009: Failed to retrieve log file attribute for {0} resource
Cause: An attempt to retrieve the log file attribute for the cluster resource failed.
Action: Make sure that the clusterware stack is up. Make sure that the resource you are querying has been configured. Refer also to any accompanying error messages for details.
PRCN-03010: Failed to retrieve log component attribute for {0} resource
Cause: An attempt to retrieve the log component attribute for the cluster resource failed.
Action: Make sure that the clusterware stack is up. Make sure that the resource you are querying has been configured. Refer also to any accompanying error messages for details.
PRCN-03011: Failed to retrieve debug file attribute for {0} resource
Cause: An attempt to retrieve the debug file attribute for the cluster resource failed.
Action: Make sure that the clusterware stack is up. Make sure that the resource you are querying has been configured. Refer also to any accompanying error messages for details.
PRCN-03012: Failed to retrieve debug component attribute for {0} resource
Cause: An attempt to retrieve the debug component attribute for the cluster resource failed.
Action: Make sure that the clusterware stack is up. Make sure that the resource you are querying has been configured. Refer also to any accompanying error messages for details.
PRCN-03013: Failed to update log file attribute of {0} resource
Cause: An attempt to update the attribute value of LOG_FILE for ONS failed.
Action: Examine the accompanying error message(s) and respond accordingly.
PRCN-03014: Failed to update log component attribute of {0} resource
Cause: An attempt to update the attribute value of LOG_COMP for ONS failed.
Action: Examine the accompanying error message(s) and respond accordingly.
PRCN-03015: Failed to update debug file attribute of {0} resource
Cause: An attempt to update the attribute value of DEBUG_FILE for ONS failed.
Action: Examine the accompanying error message(s) and respond accordingly.
PRCN-03016: Failed to update debug component attribute of {0} resource
Cause: An attempt to update the attribute value of DEBUG_COMP for ONS failed.
Action: Examine the accompanying error message(s) and respond accordingly.
PRCN-03017: Specified check interval of {0} minutes exceeds the maximum check interval {1} minutes
Cause: The CVU resource check interval specified was more than the maximum check interval.
Action: Retry the operation with an interval smaller than or equal to the maximum check interval.
PRCN-03018: Addition of listener version {0} is not allowed using srvctl version {1}
Cause: The versions of srvctl used and listener to be created did not match.
Action: Use the same version of srvctl as listener.
PKPKjFJOEBPS/nidus.htm NID-00001 to NID-00604

40 NID-00001 to NID-00604

NID-00001: Illegal command line syntax - parse error = (number)
Cause: Illegal operand on command line.
Action: Remove illegal operand.
NID-00002: Parse error: string
Cause: An error was encountered while parsing the command line.
Action: Remove offending operand.
NID-00010: Password:
Cause: Password was not specified in command line.
Action: Type password at this prompt.
NID-00100: Cannot open datafile "string"
Cause: The specified datafile could not be opened.
Action: Ensure that the specified datafile exists and is writable.
NID-00101: LOGFILE (string) not accessible
Cause: The specified log file could not be opened.
Action: Specify a log file that is writable.
NID-00102: Garbled target string
Cause: The supplied connect string could not be parsed. The connect string does not have the correct format.
Action: Refer to Oracle9i Database Concepts.
NID-00103: Missing password in connect string "string"
Cause: Could not find the password in the supplied connect string. The connect string does not have the correct format.
Action: Refer to Oracle9i Database Concepts.
NID-00104: Need to specify TARGET connection parameter in command line
Cause: The mandatory parameter TARGET was not specified.
Action: Specify TARGET=<username>/<password> when invoking this utility.
NID-00105: Need to specify "LOGFILE=<logfile>" when using APPEND=YES option
Cause: The APPEND parameter was specified without a LOGFILE.
Action: Specify APPEND=YES only when LOGFILE is also specified.
NID-00106: LOGIN to target database failed with Oracle error: string
Cause: An Oracle error was reported while attempting to log in to the target database.
Action: Follow the actions for the specified Oracle error.
NID-00107: File I/O error on datafile "string" during string operation (number/string)
Cause: An operating system error was reported while performing the specified operation in the specified file.
Action: Verify the datafile and check for operating system errors.
NID-00109: DBNAME string length number exceeds maximum length of number
Cause: The specified new database name exceeded the maximum size.
Action: Specify a shorter, valid name.
NID-00110: Cannot use REVERT and specify a database name at the same time
Cause: Conflicting options were specified in the command line.
Action: Choose only one of the options.
NID-00111: Oracle error reported from target database while executing string string
Cause: An Oracle error was reported when executing an OCI operation.
Action: Follow the actions for the specified Oracle error.
NID-00113: Error reading answer - aborting
Cause: Response caused an error.
Action: Retry the operation.
NID-00114: Must specify new database name when SETNAME is used
Cause: SETNAME=YES was specified but no DBNAME was provided.
Action: Specify DBNAME or remove the SETNAME=YES option.
NID-00115: Database should be mounted
Cause: The database was not mounted.
Action: Mount the database.
NID-00120: Database should be mounted exclusively
Cause: The database was started in parallel mode. To change the DBID, the database must be mounted exclusively.
Action: Shut down the database and start it in exclusive mode.
NID-00121: Database should not be open
Cause: The database was open. To change the DBID, the database must be mounted exclusively.
Action: Shutdown the database and mount it in exclusive mode.
NID-00122: Database should have no offline immediate datafiles
Cause: The database has one or more datafiles that are in OFFLINE IMMEDIATE mode.
Action: Drop the datafiles or recover them and bring them online.
NID-00123: Magic number for datafile "string" is incorrect
Cause: Block 0 header has an incorrect magic number for the specified datafile.
Action: Verify that the datafile is correct and retry the operation.
NID-00124: Mismatched dbid for datafile string, expected number, found number
Cause: The dbid of the datafile does not match the 'old' DBID or the 'new' DBID.
Action: Verify that this datafile belongs to the database. You may need to restore a backup of the datafile.
NID-00125: Database should have no disabled datafiles
Cause: The database has one or more datafiles that are disabled.
Action: Drop the datafiles or recover them and bring them online.
NID-00126: Database should have no datafiles in unknown state
Cause: The database has one or more datafiles that are in an unknown state.
Action: Drop the datafiles or recover them and bring them online.
NID-00127: All online files in the database must have the same checkpoint SCN
Cause: The database has one or more datafiles that have a checkpoint SCN that does not match the database checkpoint SCN.
Action: Restart the database and shut it down cleanly, then retry the operation.
NID-00128: Cannot revert change of database, change not in progress
Cause: The REVERT option was used, but the control file does not show that a change of DBID was in progress.
Action: Do not use the REVERT option, or possibly restore the control file that was in place when the utility was started.
NID-00129: Invalid DBID for datafile "string", expecting number, found number
Cause: A datafile header shows a different DBID from the rest of the database files.
Action: Ensure that the file belongs to this database.
NID-00130: Mismatched CHECKPOINT_CHANGE# in datafile "string", expecting string, found string
Cause: The datafile header does not match information in the control file.
Action: Revert the change, open the database, and verify that all datafiles are consistent. Then, shut down the database and retry the operation.
NID-00131: Control file is not current
Cause: A non-current control file is currently mounted.
Action: Perform necessary actions to make the control file current and retry.
NID-00132: CHECKPOINT_CHANGE# in datafile "string": string in the future of controlfile: string
Cause: The checkpoint in the datafile header is ahead of the checkpoint in the control file.
Action: Make the database consistent and retry.
NID-00133: Database should have only consistent datafiles
Cause: The database has one or more datafiles that are marked FUZZY in the control file.
Action: Restart the database and shut down consistently, then retry the operation.
NID-00134: Datafile "string" is not consistent
Cause: The datafile is marked as fuzzy in its header.
Action: Restart the database and shut down cleanly, then retry the operation.
NID-00135: There are number active threads
Cause: is that the database crashed the last time it was shut down.
Action: Ensure that all threads are closed before retrying the operation. Start and open the database to perform crash recovery, then shut down with the NORMAL or IMMEDIATE options to close it cleanly. Finally, try running the utility again.
NID-00137: All datafiles that are not dropped should be readable
Cause: The database had one or more files that could not be read.
Action: Restore the missing files and retry the operation.
NID-00138: Block verification failed for datafile string (number)
Cause: Block header checksum yields a nonzero value for the specified datafile.
Action: Verify that the datafile is correct and retry the operation.
NID-00139: Mismatched dbname for datafile string, expected string, found string
Cause: The dbname of the datafile does not match the 'old' dbname or the 'new' dbname.
Action: Verify that this datafile belongs to the database. You may need to restore a backup of the datafile.
NID-00140: Specified database name string does not match previous name used string
Cause: This is a continuation of a failed attempt. However in the failed attempt, the database name is different than the one used in the last attempt.
Action: Retry the command using the original database name.
NID-00141: No database name specified, previous attempt used string
Cause: This is a continuation of a failed attempt. However, in the failed attempt, a database name was provided.
Action: Retry the command using the original database name.
NID-00142: Only changing database name, previous attempt changed dbid to number
Cause: This is a continuation of a failed attempt. However, in the failed attempt, the database id was also being changed.
Action: Retry the command removing SETNAME=YES.
NID-00143: Mismatched controlfile string
Cause: A controlfile did not have the correct status.
Action: Shutdown the database, remove the mismatched controlfile, mount the database, and retry the operation.
NID-00144: New name for database string is the same as current name string
Cause: The specified name is the same as the current name of the database.
Action: Specify a different name or do not use the DBNAME option.
NID-00145: nls subsystem initialization failure for product=string, facility=string
Cause: The NLS product/facility error message file could not be located or properly initialized.
Action: Check that the error message directory and file(s) have been properly installed.
NID-00300: Connected to database string (DBID=number)
Cause: Informational message.
Action: No action required.
NID-00301: Datafile string - dbid changed, wrote new name
Cause: Informational message.
Action: No action required.
NID-00302: Datafile string - dbid changed
Cause: Informational message.
Action: No action required.
NID-00303: Datafile string - wrote new name
Cause: Informational message.
Action: No action required.
NID-00304: Datafile string - reverted
Cause: Informational message.
Action: No action required.
NID-00305: Datafile string - already changed
Cause: Informational message.
Action: No action required.
NID-00306: Datafile string - no revert needed
Cause: Informational message.
Action: No action required.
NID-00307: Control File string - dbid changed, wrote new name
Cause: Informational message.
Action: No action required.
NID-00308: Control File string - dbid changed
Cause: Informational message.
Action: No action required.
NID-00309: Control File string - wrote new name
Cause: Informational message.
Action: No action required.
NID-00310: Control File string - reverted
Cause: Informational message.
Action: No action required.
NID-00311: Control File string - modified
Cause: Informational message.
Action: No action required.
NID-00312: Connected to server version string
Cause: Informational message.
Action: No action required.
NID-00315: Operation already in progress, continuing
Cause: Informational message.
Action: No action required.
NID-00320: Operation cancelled at user request
Cause: Informational message.
Action: No action required.
NID-00321: Proceeding with operation
Cause: Informational message.
Action: No action required.
NID-00330: The following datafiles are offline immediate:
Cause: Informational message.
Action: No action required.
NID-00331: The following datafiles are disabled:
Cause: Informational message.
Action: No action required.
NID-00332: The following datafiles are in unknown state:
Cause: Informational message.
Action: No action required.
NID-00333: Cannot read the header of the following datafiles:
Cause: Informational message.
Action: No action required.
NID-00334: The following datafiles are not checkpointed to string:
Cause: Informational message.
Action: No action required.
NID-00335: The following datafiles are not consistent:
Cause: Informational message.
Action: No action required.
NID-00336: The following datafiles are offline clean:
Cause: Informational message.
Action: No action required.
NID-00337: The following datafiles are read-only:
Cause: Informational message.
Action: No action required.
NID-00338: Control Files in database:
Cause: Informational message.
Action: No action required.
NID-00350: string (number) string
Cause: Informational message.
Action: No action required.
NID-00351: string (number)
Cause: Informational message.
Action: No action required.
NID-00352: string (number), error: number
Cause: Informational message.
Action: No action required.
NID-00353: string
Cause: Informational message.
Action: No action required.
NID-00354: Instance shut down
Cause: Informational message.
Action: No action required.
NID-00370: Change database ID of database string? (Y/[N]) =>
Cause: Informational message.
Action: No action required.
NID-00371: Change database name of database string to string? (Y/[N]) =>
Cause: Informational message.
Action: No action required.
NID-00372: Change database ID and database name string to string? (Y/[N]) =>
Cause: Informational message.
Action: No action required.
NID-00373: Revert changes for database string (Y/[N]) =>
Cause: Informational message.
Action: No action required.
NID-00390: These files must be writable by this utility.
Cause: Informational message.
Action: No action required.
NID-00395: Reverting database name from string to string
Cause: Informational message.
Action: No action required.
NID-00396: Reverting database ID from number to number
Cause: Informational message.
Action: No action required.
NID-00397: Changing database name from string to string
Cause: Informational message.
Action: No action required.
NID-00398: Changing database ID from number to number
Cause: Informational message.
Action: No action required.
NID-00400: DBNEWID - Completed with errors.
Cause: Informational message.
Action: No action required.
NID-00401: Must finish REVERT changes before attempting any database operation.
Cause: Informational message.
Action: No action required.
NID-00402: Must finish change or REVERT changes before attempting any database operation.
Cause: Informational message.
Action: No action required.
NID-00403: DBNEWID - Completed with validation errors.
Cause: Informational message.
Action: No action required.
NID-00404: DBNEWID - Completed succesfully.
Cause: Informational message.
Action: No action required.
NID-00405: Reversion of database name and database ID failed.
Cause: Informational message.
Action: No action required.
NID-00406: Reversion of database name failed.
Cause: Informational message.
Action: No action required.
NID-00407: Reversion of database ID failed.
Cause: Informational message.
Action: No action required.
NID-00410: Reversion of database changes failed during validation - database is intact.
Cause: Informational message.
Action: No action required.
NID-00415: Change of database name and database ID failed.
Cause: Informational message.
Action: No action required.
NID-00416: Change of database name failed.
Cause: Informational message.
Action: No action required.
NID-00417: Change of database ID failed.
Cause: Informational message.
Action: No action required.
NID-00420: Change of database name and ID failed during validation - database is intact.
Cause: Informational message.
Action: No action required.
NID-00421: Change of database name failed during validation - database is intact.
Cause: Informational message.
Action: No action required.
NID-00422: Change of database ID failed during validation - database is intact.
Cause: Informational message.
Action: No action required.
NID-00425: Database name restored to string.
Cause: Informational message.
Action: No action required.
NID-00426: Database ID for database string restored to number.
Cause: Informational message.
Action: No action required.
NID-00430: Database is ready to be open or shut down.
Cause: Informational message.
Action: No action required.
NID-00431: DBNEWID - Reversion completed.
Cause: Informational message.
Action: No action required.
NID-00435: Database name changed to string.
Cause: Informational message.
Action: No action required.
NID-00436: Modify parameter file and generate a new password file before restarting.
Cause: Informational message.
Action: No action required.
NID-00440: Database ID for database string changed to number.
Cause: Informational message.
Action: No action required.
NID-00441: All previous backups and archived redo logs for this database are unusable.
Cause: Informational message.
Action: No action required.
NID-00442: Database has been shutdown, open database with RESETLOGS option.
Cause: Informational message.
Action: No action required.
NID-00450: Succesfully changed database name and ID.
Cause: Informational message.
Action: No action required.
NID-00451: Succesfully changed database name.
Cause: Informational message.
Action: No action required.
NID-00452: Succesfully changed database ID.
Cause: Informational message.
Action: No action required.
NID-00480: Database is intact - database is ready to be open or shut down.
Cause: Informational message.
Action: No action required.
NID-00481: DBNEWID - Cancelled.
Cause: Informational message.
Action: No action required.
NID-00482: Database is not aware of previous backups and archived logs in Recovery Area.
Cause: Because the database id was changed, previous backups and archived redo logs in recovery area are not managed by this database.
Action: This is the informational message only.
NID-00490: LOG being redirected to STDERR due to errors.
Cause: Could no write message to log file.
Action: None
NID-00500: Keyword Description (Default)
Cause: Informational message.
Action: No action required.
NID-00501: ----------------------------------------------------
Cause: Informational message.
Action: No action required.
NID-00502: TARGET Username/Password (NONE)
Cause: Informational message.
Action: No action required.
NID-00503: DBNAME New database name (NONE)
Cause: Informational message.
Action: No action required.
NID-00504: LOGFILE Output Log (NONE)
Cause: Informational message.
Action: No action required.
NID-00505: REVERT Revert failed change NO
Cause: Informational message.
Action: No action required.
NID-00506: SETNAME Set a new database name only NO
Cause: Informational message.
Action: No action required.
NID-00507: APPEND Append to output log NO
Cause: Informational message.
Action: No action required.
NID-00508: HELP Displays these messages NO
Cause: Informational message.
Action: No action required.
NID-00600: Internal Error - [number] [number] [number] [number]
Cause: This is the generic internal error number for program exceptions. This indicates that the program has encountered an exceptional condition.
Action: Report as a bug - the first argument is the internal error number
NID-00601: Internal Error - [number] [string] [number] [number]
Cause: This is the generic internal error number for program exceptions. This indicates that the program has encountered an exceptional condition.
Action: Report as a bug - the first argument is the internal error number
NID-00602: Could not allocate number bytes for "string"
Cause: Memory allocation failed.
Action: Free memory at the operating system level and retry operation.
NID-00603: No datafiles found in database
Cause: Controlfile has not datafiles recorded
Action: Report as a bug - the first argument is the internal error number
NID-00604: No control files found in database
Cause: Instance has no control files recorded
Action: Report as a bug - the first argument is the internal error number
PKu f PKjFJOEBPS/tnsus.htm TNS-00000 to TNS-12699

97 TNS-00000 to TNS-12699

TNS-00000: Not An Error
Cause: Everything is working as it should.
Action: Don't worry: Be happy.
TNS-00001: INTCTL: error while getting command line from the terminal
Cause: Improper standard input connection from the terminal.
Action: Normally not visible to the user. Start the INTCTL program again. If error persists, contact Oracle Customer Support.
TNS-00002: INTCTL: error while starting the Interchange
Cause: of the problem. Be sure to turn tracing off when the problem has been rectified.
Action: Check the Interchange configuration files (INTCHG.ORA, TNSNET.ORA and TNSNAV.ORA) for errors and confirm that no other programs are using the ADDRESS(es) specified. If error continues, turn on tracing in the Interchange components and examine the trace files to determine the
TNS-00003: INTCTL: error while sending request to the Interchange
Cause: Improper command sent to the Interchange or the Interchange is not responding. Not normally visible to the user.
Action: Verify that the command sent to the Interchange is valid. Also check that the Interchange is running by using the INTCTL STATUS command. If necessary, start the Interchange using the INTCTL START command.
TNS-00004: INTCTL: error while starting the Navigator
Cause: The Navigator could not be started.
Action: Check to make sure that executables for the Navigator (navgatr) are present in the ORACLE executable directory on your platform. Check the configuration files TNSNET.ORA and TNSNAV.ORA for errors. If error continues, turn on tracing in the Interchange components and examine the trace files to determine the cause of the problem. Be sure to turn tracing off when the problem has been rectified.
TNS-00005: INTCTL: error while sending request to the Navigator
Cause: The Navigator is not responding. Either the Navigator is not running or another process is responding.
Action: Check that the Navigator is running by using the STATUS command of the Interchange Control Utility. Verify that the correct addresses are listed in the TNSNAMES.ORA, TNSNET.ORA, and TNSNAV.ORA configuration files.
TNS-00006: INTCTL: HOST variable is not defined
Cause: The HOST variable was not set.
Action: Set the variable HOST properly and restart the INTCTL program.
TNS-00007: INTCTL: unknown host
Cause: The pointer HOST is set to an unknown hostname.
Action: Set the pointer HOST properly and restart INTCTL program.
TNS-00008: INTCTL: could not contact destination Navigator
Cause: Connection could not be properly established to a Navigator. This may be because the Navigator specified is not running or the Navigator addresses are incorrect.
Action: Check that the Navigator is running by using the STATUS command of the Interchange Control Utility; if necessary, start the Navigator using the START command of the Interchange Control Utility. If it is running and the error persists, contact Oracle Customer Support.
TNS-00009: INTCTL: could not contact destination Connection Manager
Cause: Connection could not be properly established to a Connection Manager. This may be because the Connection Manager (Interchange) specified is not running or the Connection Manager addresses are incorrect.
Action: Make sure the Connection Manager is running by using the STATUS command of the Interchange Control Utility; if necessary, start the Connection Manager using the START command of the Interchange Control Utility. If it is running and the error persists, contact Oracle Customer Support.
TNS-00010: Error while flushing NS context
Cause: Internal NS error; connection may be lost.
Action: Make sure the connection is properly established. If the error persists, then contact Oracle Customer Support.
TNS-00011: INTCTL: error while starting the Connection Manager
Cause: The Connection Manager could not be started.
Action: Assure that the executable can be found in the standard Oracle executable area. Check the configuration file INTCHG.ORA for errors and confirm that no other process is using the ADDRESS(es) for this Connection Manager as specified in TNSNET.ORA. Tracing can also be turned on in the Connection Manager and detailed information about the reason for the error determined. Consult the MultiProtocol Interchange Administrator's Guide and Chapter 2 of this manual for how to turn on tracing.
TNS-00012: INTCTL: error while processing Connection Manager request
Cause: An improper command was sent to the Connection Manager or it is not responding. Not normally visible to the user.
Action: Verify that the correct addresses are listed in the TNSNAMES.ORA, TNSNET.ORA, and TNSNAV.ORA configuration files. Also check that the Connection Manager is running by using the STATUS command of the Interchange Control Utility. If the error persists, contact Oracle Customer Support.
TNS-00013: INTCTL: error while performing NS disconnect command
Cause: Internal NS error. Error in closing down connections.
Action: Make sure the networking protocol being used is properly installed on the machine. If the error persists contact Oracle Customer Support.
TNS-00014: INTCTL: error while opening terminal input channel
Cause: Could not open standard terminal input. Internal error.
Action: Normally not visible to the user. Restart the INTCTL program. If error persists, contact Oracle Customer Support.
TNS-00015: INTCTL: error while closing terminal input channel
Cause: Could not close terminal input channel. Internal error.
Action: Normally not visible to the user. Restart the INTCTL program. If error persists, contact Oracle Customer Support.
TNS-00016: INTCTL: error while performing NS send command
Cause: Internal NS error. Connection may be lost.
Action: If the error persists contact Oracle Customer Support.
TNS-00017: INTCTL: error while performing NS receive command
Cause: Internal NS error. Connection may be lost.
Action: If the error persists contact Oracle Customer Support.
TNS-00018: INTCTL: TNS_ADMIN not defined
Cause: The TNS_ADMIN pointer is improperly set.
Action: No action necessary; TNS_ADMIN need only be set if you want to use a different network environment.
TNS-00019: INTCTL: error initializing the national language interface
Cause: The message file could not be found.
Action: Make sure that the ORACLE environment is set and that the message file is in the correct place.
TNS-00020: INTCTL: missing NAVIGATOR_DATA in TNSNAV.ORA
Cause: TNSNAV.ORA does not contain the NAVIGATOR_DATA component.
Action: Define the ADDRESS(es) for the Navigator, then restart the INTCTL program.
TNS-00021: INTCTL: missing INTERCHANGE_DATA in INTCHG.ORA
Cause: INTCHG.ORA does not contain an INTERCHANGE_DATA component.
Action: Define the correct data for the Connection Manager, then restart the INTCTL program.
TNS-00022: INTCTL: missing CMANAGER_NAME in INTCHG.ORA
Cause: INTCHG.ORA does not contain a CMANAGER_NAME component.
Action: Define the correct name for the CMANAGER_NAME, then restart the INTCTL program.
TNS-00023: INTCTL: missing ADDRESS(es) in config files
Cause: Configuration files do not contain an ADDRESS/ADDRESS_LIST component.
Action: Define the Connection Manager ADDRESS(es) in the TNSNET.ORA file and check the Navigator ADDRESS(es) in the TNSNAV.ORA file, then restart the INTCTL program.
TNS-00024: INTCTL: Unable to contact Navigator to obtain Connection Manager address
Cause: The Navigator is not running.
Action: Verify that the Navigator is running by doing a status request on the Navigator (use the Interchange Control Utility command STATUS). If necessaary, start the Navigator using the Interchange Control Utility. Verify that the network is properly configured; if the error persists, contact Worldwide Customer Support.
TNS-00025: INTCTL: The ORACLE environment is not set up correctly
Cause: The ORACLE environment is incorrectly set up.
Action: Refer to the Oracle operating system specific documentation for your platform for information on how the ORACLE environment should be set. Correct it and rerun INTCTL. Make sure the ORACLE environment includes the correct directories.
TNS-00026: INTCTL: TNS_ADMIN directory set, and is being used
Cause: The TNS_ADMIN environment variable is set properly. INTCTL will use the TNS_ADMIN directory. This is only an informative message. If you do not want it to be used, and want the default directory to be used instead, then unset TNS_ADMIN and reexecute.
Action: None
TNS-00027: INTCTL: Could not resolve Navigator's name/address
Cause: The Navigator's name to address definition is missing.
Action: Check TNSNAMES.ORA file and make sure to include a definition for the name specified.
TNS-00028: INTCTL: Could not resolve Connection Manager's name/address
Cause: The Connection Manager's name does not have a definition that the Navigator knows about, nor is the name/address available in the TNSNAMES.ORA file. The name may also be incorrect in the INTCHG.ORA file.
Action: Verify that the Connection Manager's name is in the TNSNET.ORA file read by the Navigator or in the TNSNAMES.ORA file. Be sure that INTCHG.ORA is correct.
TNS-00031: INTCTL: internal NT error
Cause: Problem interfacing to the protocol adapters installed.
Action: Normally not visible to the user. Try starting INTCTL again. If the error persists, check the product installation. If it is correct, contact Oracle Customer Support.
TNS-00032: INTCTL: internal NS error
Cause: Problem interfacing with TNS.
Action: Normally not visible to the user. Try starting INTCTL again. If the error persists, check the product installation. If it is correct, contact Oracle Customer Support.
TNS-00033: INTCTL: internal NL error
Cause: Problem with internal TNS module NL.
Action: Normally not visible to the user. Try starting INTCTL again. If the error persists, check the product installation. If it is correct, contact Oracle Customer Support.
TNS-00034: INTCTL: internal NR error
Cause: Problem with internal Interchange routines.
Action: Normally not visible to the user. Try starting INTCTL again. If the error persists, check the product installation. If it is correct, contact Oracle Customer Support.
TNS-00035: INTCTL: error while constructing full file name
Cause: Problem while constructing the full path for a file name because the path name to the file or the environment variables are incorrect. Files looked up include TNSNAMES.ORA, TNSNAV.ORA, INTCHG.ORA and the error files for the Navigator and Connection Manager.
Action: Check that all environment variables are defined correctly and that all configuration files exist in their correct places.
TNS-00036: INTCTL: error reading from Navigator or Connection Manager error files
Cause: Problem while reading from Navigator or Connection Manager error files generated by the Navigator or Connection Manager when they fail to start.
Action: Check that a standard Network Error directory exists and that all privileges on the directory are appropriate.
TNS-00037: INTCTL: error opening Navigator or Connection Manager error files
Cause: Failed to open Navigator or Connection Manager error files when they have failed to start.
Action: Check that a Network Error directory exists and that all privileges on the directory are appropriate.
TNS-00038: INTCTL: Poorly formed address or command string
Cause: An unacceptable string was encountered while attempting to send a message to either the Navigator or Connection Manager. The addresses provided for either the Navigator or Connection Manager may be incorrectly constructed.
Action: Check all address strings in configuration files (TNSNAMES.ORA, TNSNAV.ORA or TNSNET.ORA) and assure that they are properly formed. Regenerate the files, if possible. If all is correct, please contact Worldwide Customer Support.
TNS-00039: INTCTL: error while spawning a process
Cause: An error was encountered while spawning a process due to an internal operating system dependent problem. Machine resources may be limited.
Action: Retry command. Check permissions on Interchange executables and the current setting of the search path. If necessary, terminate other applications to free up machine resources. If the error persists, contact Oracle Customer Support.
TNS-00040: INTCTL: failed to initialize trace context- Continuing anyway
Cause: Problem while opening specified trace file because of errors in INTCHG.ORA or because the user has incorrect privileges, or the file does not exist.
Action: Check the privileges on the configuration files and ensure that all of them exist in their proper locations.
TNS-00041: INTCTL: Navigator already running. Start operation cancelled
Cause: There is a Navigator already running and listening on the same addresses.
Action: None; the Navigator is already running.
TNS-00042: INTCTL: CMANAGER already running. Start operation cancelled
Cause: There is a Connection Manager already running and listening on the same addresses.
Action: None; the Connection Manager is already running.
TNS-00043: The CMANAGER has active connections, do you still want to stop it (y/n)?
Cause: The CMANAGER that is being stopped has active connections going through. This is the confirmation message.
Action: Respond by pressing y or n. Answering y will cause the active database connection to be dropped; this is not generally recommended.
TNS-00044: INTCTL: You must have an INTCHG.ORA file to contact the Connection Manager
Cause: There was an attempt to contact a default Connection Manager (Interchange) where there was no INTCHG.ORA present in the correct directory.
Action: Create an INTCHG.ORA file. Make sure it is placed in the correct directory and includes the correct name for the Connection Manager you wish to contact.
TNS-00045: INTCTL: Could not contact the Navigator on address
Cause: There was an attempt to contact a Navigator on a specific address which is not responding.
Action: Check the TNSNAV.ORA file for that address. Or check that the Navigator is actually listening on that address.
TNS-00046: INTCTL: Could not contact the CMANAGER on address
Cause: There was an attempt to contact a CMANAGER on a specific address which is not responding.
Action: Verify that the TNSNET.ORA file contains that address. Also check that the CMANAGER is actually listening on that address by using the INTCTL STATUS command. If necessary, start the Connection Manager using the INTCTL START command.
TNS-00060: INTCTL: Bad command: only the STATUS command can be used on remote Interchanges
Cause: The user entered a command that does not exist, or the user tried to make a request other than STATUS to a remote Interchange.
Action: Check the MultiProtocol Interchange Administrator's Guide for a list of INTCTL commands or type HELP for a list of valid commands.
TNS-00061: INTCTL: Bad command or syntax error: You must specify a trace level
Cause: The user did not specify a trace level.
Action: Specify a trace level and retry command.
TNS-00062: INTCTL: Bad command or syntax error: For help type help/h/?
Cause: The user entered an invalid command.
Action: Check the MultiProtocol Interchange Administrator's Guide or type HELP for a list of valid commands.
TNS-00063: INTCTL: Failed to allocate memory for buffers
Cause: INTCTL was unable to allocate memory for internal buffers.
Action: Check the amount of available memory on your machine to ensure that there is enough memory to run this executable. If necessary, free up memory by running fewer programs, then try again.
TNS-00064: INTCTL: Failed to find CMANAGER_NAME in INTCHG.ORA
Cause: INTCTL was unable to find the CMANAGER_NAME parameter in INTCHG.ORA.
Action: Check that the INTCHG.ORA file is properly constructed.
TNS-00065: INTCTL: Command cannot be executed remotely
Cause: A command other than status and version has been attempted remotely.
Action: If you desire execute any command other than status and version, you must run intctl on the interchange machine.
TNS-00070: INTCTL usage: [intctl] <command> <process_name> [argument]
Cause: Help message displayed by INTCTL.
Action: None
TNS-00071: where <command> is one of following:
Cause: Help message displayed by INTCTL.
Action: None
TNS-00072: * start - start up process_name
Cause: Help message displayed by INTCTL.
Action: None
TNS-00073: * stop/abort - stop the process_name
Cause: Help message displayed by INTCTL.
Action: None
TNS-00074: * status - get statistics from the process_name
Cause: Help message displayed by INTCTL.
Action: None
TNS-00075: NOTE: the user may get the status info of a remote
Cause: Help message displayed by INTCTL.
Action: None
TNS-00076: component by specifying the component name in
Cause: Help message displayed by INTCTL.
Action: None
TNS-00077: the argument field
Cause: Help message displayed by INTCTL.
Action: None
TNS-00078: * log_on - ask process_name to turn logging on
Cause: Help message displayed by INTCTL.
Action: None
TNS-00079: * log_off - ask process_name to turn logging off
Cause: Help message displayed by INTCTL.
Action: None
TNS-00080: * force_log - ask process_name to dump its state
Cause: Help message displayed by INTCTL.
Action: None
TNS-00081: * trace_on - ask process name to turn tracing on
Cause: Help message displayed by INTCTL.
Action: None
TNS-00082: NOTE: the user MUST specify a trace level
Cause: Help message displayed by INTCTL.
Action: None
TNS-00083: (USER or ADMIN) in the argument field
Cause: Help message displayed by INTCTL.
Action: None
TNS-00084: * trace_off - ask process name to turn tracing off
Cause: Help message displayed by INTCTL.
Action: None
TNS-00085: * reread - ask the process name to reread parameter files
Cause: Help message displayed by INTCTL.
Action: None
TNS-00086: * reload - ask the Navigator to reload TNSNET.ORA
Cause: Help message displayed by INTCTL.
Action: None
TNS-00087: * version - ask the process name to display its version number
Cause: Help message displayed by INTCTL.
Action: None
TNS-00088: * exit - quit the Interchange controller
Cause: Help message displayed by INTCTL.
Action: None
TNS-00089: process_name is one of Interchange, CMANAGER, or Navigator
Cause: Help message displayed by INTCTL.
Action: None
TNS-00090: * Interchange - will ask the Interchange
Cause: Help message displayed by INTCTL.
Action: None
TNS-00091: * Navigator (or navgatr) - will ask the Navigator only
Cause: Help message displayed by INTCTL.
Action: None
TNS-00092: * CMANAGER (or intlsnr) - will ask the Cmanager only
Cause: Help message displayed by INTCTL.
Action: None
TNS-00093: argument is only supplied to either status or trace_on
Cause: Help message displayed by INTCTL.
Action: None
TNS-00094: * to status - argument is considered the remote process_name
Cause: Help message displayed by INTCTL.
Action: None
TNS-00095: * to trace_on - argument is considered the trace level
Cause: Help message displayed by INTCTL.
Action: None
TNS-00100: Unable to allocate memory
Cause: Out of memory on the machine.
Action: Add more memory or run fewer processes.
TNS-00101: File operation error
Cause: Error in accessing reading or writing a particular file.
Action: Check existence of or operating system access to the log and trace file locations.
TNS-00102: Keyword-Value binding operation error
Cause: Not normally visible to the user. May indicate a shortage of memory.
Action: If error persists contact Oracle Customer Support.
TNS-00103: Parameter file load error
Cause: Parameter file process failed.
Action: Check to make sure that all parameter files necessary for the Interchange are present (TNSNAV.ORA, TNSNET.ORA and INTCHG.ORA). If these files are present and properly configured, turn on tracing and repeat the operation. Turn off tracing when the trace is complete. Look in the trace file for errors in the parameter loading process. If error persists contact Oracle Customer Support.
TNS-00104: Data stream open/access error
Cause: Unable to open or access data stream for either log or trace files for the Interchange.
Action: Check read/write permissions on Oracle files and directories.
TNS-00105: Could not initialize tracing
Cause: The INTCHG.ORA file is improperly configured. Verify the trace parameters specified.
Action: If error persists contact Oracle Customer Support.
TNS-00106: Failed to open log file
Cause: Unable to access or obtain write permission to create log file.
Action: Check existence of or access to log file directory.
TNS-00107: Unable to initialize TNS global data
Cause: Not normally visible to the user.
Action: If error persists contact Oracle Customer Support.
TNS-00108: TNS_ADMIN not defined
Cause: TNS_ADMIN pointer is not set.
Action: Set the TNS_ADMIN pointer before running application
TNS-00109: Message could not be printed; not enough memory
Cause: Printing of message failed due to lack of memory. Not normally visible to user.
Action: Increase the resources on your machine. If error persists contact Oracle Customer Support.
TNS-00110: Could not initialize network from file TNSNET.ORA
Cause: Poorly formed network information in network file.
Action: Fix network configuration data to assure that at least one Interchange is defined in TNSNET.ORA.
TNS-00111: Failed to get configuration data from file
Cause: Poorly formed configuration information in network files TNSNET.ORA or TNSNAV.ORA.
Action: Check TNSNET.ORA and TNSNAV.ORA and confirm that they are correct.
TNS-00112: Failed to find configuration file name
Cause: Name specified for configuration file was incorrect.
Action: Check for presence of the configuration file.
TNS-00113: Failed to open error log file
Cause: Could not open log file during startup of Navigator or Connection Manager due to read or write permission problems or non-existent error directory.
Action: Create the standard error directory or assure that if one is present the Interchange executables can write to it.
TNS-00114: Internal error- Allocation of addresses not performed
Cause: Internal error. Should not normally occur.
Action: Contact Oracle Customer Support.
TNS-00115: Could not allocate pump global buffers
Cause: Not enough memory to allocate pump buffers.
Action: Decrease the number of PUMP_BUFFERS in INTCHG.ORA.
TNS-00116: Pump failed during initial bequeath
Cause: d by insufficient machine resources.
Action: Attempt the connection again. The pump should recover from such a failure. If machine resources appear to be the problem, add more resources // or shut down some active applications. If problem persists, contact Oracle Customer Support.
TNS-00117: Internal error- No data passed through pump
Cause: Internal error. Data expected has not arrived yet.
Action: If error persists, contact Oracle Customer Support.
TNS-00119: Missing PUMP_CONNECTIONS in INTCHG.ORA
Cause: No PUMP_CONNECTIONS parameter specified in INTCHG.ORA.
Action: Add PUMP_CONNECTIONS parameter to INTCHG.ORA.
TNS-00120: Missing PUMPS in INTCHG.ORA
Cause: No PUMPS parameter specified.
Action: Add an appropriate number of PUMPS to INTCHG.ORA.
TNS-00121: Missing CMANAGER_NAME in INTCHG.ORA
Cause: No CMANAGER_NAME parameter specified.
Action: Define the CMANAGER_NAME parameter in INTCHG.ORA; it must match the CMANAGER_NAME parameter used in TNSNET.ORA for that Interchange.
TNS-00122: Missing ADDRESS(es) in TNSNET.ORA file
Cause: No ADDRESS or ADDRESS_LIST parameter specified in TNSNET.ORA.
Action: Define a valid set of ADDRESSes for the Connection Manager in the TNSNET.ORA file.
TNS-00123: Unable to perform a listen on configured ADDRESS(es)
Cause: Another process is already listening on this address or the ADDRESS is incorrectly defined.
Action: Check the ADDRESS(es) defined in TNSNET.ORA (for the Connection Manager) for errors. Verify that another program is not using them.
TNS-00124: Internal error - Unable to create empty address
Cause: - Internal error. Should not normally occur.
Action: If problem persists contact Oracle Customer Support.
TNS-00125: Failed to get number of Interchanges in TNSNET.ORA
Cause: Error in the TNSNET.ORA file.
Action: Check the contents of TNSNET.ORA and eliminate errors. Regenerate the configuration files.
TNS-00126: Missing Connection Manager name and address in TNSNET.ORA
Cause: The Interchange name specified in INTCHG.ORA is not defined in the TNSNET.ORA file.
Action: Define one Connection Manager name and set of addresses for each Interchange in the network. Regenerate the configuration files.
TNS-00127: Missing Connection Manager name in TNSNET.ORA
Cause: One or more Connection Manager names are missing.
Action: Ensure that each Connection Manager name is defined in TNSNET.ORA. Regenerate TNSNET.ORA.
TNS-00128: Missing COMMUNITY in TNSNET.ORA
Cause: One or more ADDRESSes does not have a COMMUNITY assigned.
Action: Ensure that all addresses have a COMMUNITY defined in TNSNET.ORA.
TNS-00129: Internal error - Failed to create new community
Cause: Internal Error. Should not normally occur. There may be a resource limitation problem on the machine.
Action: Stop and restart Interchange. If possible, make more memory available on the machine. If problem persists, contact Oracle Customer Support.
TNS-00130: Failed to create Interchange's internal address
Cause: There is an error in one of the addresses listed in TNSNET.ORA.
Action: Check the file for errors in defining Interchanges.
TNS-00131: Missing COMMUNITY in COMMUNITY_COST_LIST in TNSNET.ORA
Cause: A COMMUNITY keyword-value pair is missing within the COMMUNITY_COST_LIST in TNSNET.ORA.
Action: Define the communities with a COMMUNITY name and associated COST in COMMUNITY_COST_LIST.
TNS-00132: COST value must be an integer greater than 0
Cause: A community has been defined in TNSNET.ORA with a COST of 0.
Action: Assign an alternate value that is greater than 0.
TNS-00133: Missing LOCAL_COMMUNITIES field in TNSNAV.ORA
Cause: Improperly configured TNSNAV.ORA file.
Action: Define the LOCAL_COMMUNITIES fields correctly in TNSNAV.ORA.
TNS-00134: Missing COMMUNITY component in addresses for the Navigator in TNSNAV.ORA
Cause: The addresses specified for the Navigator have no COMMUNITY name.
Action: Ensure that all addresses in the NAVIGATOR_ADDRESSES field have a COMMUNITY entry in the TNSNAV.ORA file.
TNS-00135: Missing TNS error message file
Cause: No error message file present.
Action: Ensure that the ORACLE environment is correctly set for your platform and that there is a message directory that contains the correct error message file.
TNS-00136: Did not register product/facility for TNS error message
Cause: Error message file error.
Action: Ensure that the ORACLE environment is correctly set for your platform and that there is a message directory that contains the correct error message file.
TNS-00137: Failed to get TNS error message file entry
Cause: No TNS error message file present.
Action: Ensure that the ORACLE environment is correctly set for your platform and that there is a message directory that contains the correct error message file.
TNS-00138: Failed to find ORACLE executable directory
Cause: The ORACLE environment is not correctly set.
Action: Ensure that the ORACLE environment is correctly set and the error messages file is in the correct place.
TNS-00139: Internal - Data passed from the Interchange listener is poorly formed
Cause: Internal error in Interchange.
Action: Check that you are using compatible components of the Interchange product, using the INTCTL VERSION command. If problem persists call Oracle Customer Support.
TNS-00140: Interchange specified was not found in network tables
Cause: Could not find the Interchange specified in a control request.
Action: Check that the Interchange specified is indeed in TNSNET.ORA.
TNS-00141: Failed to get file stream information
Cause: Error in the file stream package.
Action: None
TNS-00142: Community mismatch in TNSNAV.ORA
Cause: The communities in the LOCAL_COMMUNITIES entry in TNSNAV.ORA do not correspond with all the communities in the NAVIGATOR_ADDRESSES entry.
Action: Assure that all communities in the NAVIGATOR_ADDRESSES correspond to those in the LOCAL_COMMUNITIES component.
TNS-00143: Illegal PREFERRED_CMANAGERS entry in TNSNAV.ORA
Cause: PREFERRED_CMANAGERS entry in the TNSNAV.ORA used by the Connection Manager. There should only be a PREFERRED_NAVIGATORS entry in the TNSNAV.ORA on an Interchange.
Action: Remove the PREFERRED_CMANAGERS entry from TNSNAV.ORA and assure that either no PREFERRED_NAVIGATORS entry is present or that it is correct.
TNS-00144: PUMP_CONNECTIONS value in INTCHG.ORA is too large.
Cause: The number of PUMP_CONNECTIONS specified in INTCHG.ORA is too large to be supported on this platform.
Action: Consult the Oracle operating system specific manual for the maximum value for the number of PUMP_CONNECTIONS.
TNS-00145: PUMPS value in INTCHG.ORA is too large.
Cause: The number of PUMPS specified in INTCHG.ORA is too large to be supported on this platform.
Action: Consult the Oracle operating system specific manual for the maximum value for the number of PUMPS.
TNS-00146: Internal-- Retry data request withing pump.
Cause: The data space provided in order to receive data from the pump is to small.
Action: Operation must be retried with a larger buffer.
TNS-00147: Failed to start a pre-spawned pump.
Cause: The Connection Manager was unable to start a pump during startup.
Action: Check all configuration parameters and assure that they are correct. Turn on tracing to determine the area that the failure ocurred in.
TNS-00200: Unable to do nsanswer on context result=string
Cause: Requester of service may have aborted or options negotiation failed.
Action: Try making the connection again. If the problem persists call Oracle Customer Support.
TNS-00201: Unable to read answer connection data :string:
Cause: Improperly formed connect data sent to the Interchange listener.
Action: If problem persists, check the application using the Interchange (it may be closing down or crashing). Call Oracle Customer Support if the problem cannot be located.
TNS-00202: Failure in redirecting call : Original to string Redirect to string
Cause: Internal - error could not redirect call to a pump or other Interchange listener. The cause may be insufficient network or machine resources.
Action: Add resources or close some running applications in order to free up resources. If error persists, call Oracle Customer Support.
TNS-00203: Unable to start tracing in intlsnr
Cause: Failure in setting up tracing for Interchange listener.
Action: Check file permissions in Network trace directory also check to make sure that if trace file names and directories are specified in INTCHG.ORA, they are correct.
TNS-00204: Started tracing in intlsnr
Cause: Internal message- Successfully started tracing information.
Action: None
TNS-00205: Turning off tracing in intlsnr
Cause: Internal message - Turned off tracing in the Interchange listener.
Action: None
TNS-00206: Status Information for Interchange string:
Cause: Message sent back by Interchange as header for status request.
Action: None
TNS-00207: Uptime : number days number hr. number min. number sec
Cause: Part of status request.
Action: None
TNS-00208: Logging : string
Cause: Part of status request.
Action: None
TNS-00209: Tracing : string
Cause: Part of status request Interchange.
Action: None
TNS-00210: Total Pumps Available : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00211: Total Active Pumps : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00212: Total Pumps Started : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00213: Available Connections : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00214: Total Connections in Use : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00215: Total Successful Connections : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00216: Total Failed Connections : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00217: Total Bytes of Data : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00218: Current Bytes/Sec. : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00219: Pump Strategy : string
Cause: Part of status request.
Action: None
TNS-00220: Pump Breakdown --------------
Cause: Part of status request.
Action: None
TNS-00221: Pump Connections Total Data Bytes/Second
Cause: Part of status request.
Action: None
TNS-00222: -------------------------------------------------------------------
Cause: Part of status request.
Action: None
TNS-00223: numbernumbernumbernumber
Cause: Part of status request.
Action: None
TNS-00224: No more connections available
Cause: More connections were made to the Interchange than are configured in INTCHG.ORA.
Action: Wait until the Interchange is not as busy or change the number of connections allowed in INTCHG.ORA and restart the Interchange.
TNS-00225: Unable to bequeath connection to pump
Cause: Unable to start a pump because either the executable cannot be found or too many processes aare currently running on a particular machine.
Action: Reduce the number of processes on the machine or increase the resources on the machine.
TNS-00226: Unable to contact pump number to send broadcast message string
Cause: Could not call a particular pump.
Action: None, but if the problem persists call Oracle Customer Support.
TNS-00227: Unable to contact pump; Connection Manager declared pump dead
Cause: A pump became an orphaned process. A protocol adapter is not working properly or machine network resources are being over used.
Action: This error is not immediately fatal; the orphaned pump may continue to function. Restart the Interchange when convenient. If the problem persists, call Oracle Customer Support.
TNS-00228: Failure in finding pump data
Cause: Internal problem with data passed back from pump.
Action: None
TNS-00229: Error in call: unable to deliver message :string: string string string
Cause: Destination for call is unavailable.
Action: None
TNS-00230: Cannot start new pump process: string string Protocol Adapter errors:number
Cause: Unable to create a new process; possibly there are too many processes on the machine.
Action: Free machine resources by exiting other applications on the Interchange machine. If the problem continues you may need more memory on the machine. If you believe there are sufficient resources on the machine but the problem persists, contact Oracle Customer Support.
TNS-00231: Pump is alive
Cause: Pump log message sent to Interchange listener.
Action: None
TNS-00232: Unable to setup connection
Cause: Error log message sent from pump to indicate failure in initiating connection because of errors in the call string: network problem or resource limitations.
Action: None
TNS-00233: Interchange failed to make contact with destination with errors: string string string
Cause: Pump call to destination failed.
Action: Check destination.
TNS-00234: Connect data for failed call: CALL DATA = string RECEIVE DATA = :string:
Cause: Connect data supplied for error 00233.
Action: None
TNS-00235: Aborting connection: Protocol Apapter errors: string;number,number string;number,number
Cause: Pump aborting connection because connection has been up too long, or some other network error on the connection.
Action: None
TNS-00236: Failed to initialize tracing
Cause: Pump failed to initialize tracing.
Action: Check that INTCHG.ORA is properly configured.
TNS-00237: Failed to refuse connection
Cause: Connection may have aborted before error took place in Pump.
Action: None
TNS-00238: Pump number @: string:
Cause: Prepended message to all pump log messages.
Action: None
TNS-00239: Connection Manager has been stopped
Cause: Message sent back to control program from Interchange.
Action: None
TNS-00240: Connection Manager: Logging is now ON
Cause: Message sent back to control program from Interchange.
Action: None
TNS-00241: Connection Manager: Logging is now OFF
Cause: Message sent back to control program from Interchange.
Action: None
TNS-00242: Connection Manager: Tracing is now ON
Cause: Message sent back to control program from Interchange.
Action: None
TNS-00243: Connection Manager: Tracing is now OFF
Cause: Message sent back to control program from Interchange.
Action: None
TNS-00244: Connection Manager: Request Failed
Cause: Message sent back to control program from Interchange.
Action: None
TNS-00245: Connection Manager: Failed to open log file
Cause: Message sent back to control program from Interchange.
Action: None
TNS-00246: Connection Manager: Failed to start tracing
Cause: Message sent back to control program from Interchange.
Action: None
TNS-00247: Unable to allocate memory for configuration data from TNSNET.ORA file
Cause: Navigator failed to allocate enough memory for TNSNET.ORA configuration file.
Action: Increase machine resources available for running the Interchange or remove some other running applications from the machine.
TNS-00248: Unable to get information from file :string: Exiting with NR error:number
Cause: TNSNAV.ORA poorly configured or addresses provided are already being used by another application.
Action: Check the syntax of the TNSNAV.ORA file; if necessary, assign new addresses.
TNS-00249: Unable to read network configuration data from file string with error: string
Cause: Network configuration file TNSNET.ORA is missing or poorly configured.
Action: Check to make sure that TNSNET.ORA is properly configured.
TNS-00250: Navigator has been started
Cause: Message to log file on Navigator startup.
Action: None
TNS-00251: Failure in nstest:
Cause: NS test operation failed due to internal error.
Action: If the problem persists there may be a network problem or resource limitations on the machine. If these do not seem to be causing the problem, call Oracle Customer Support.
TNS-00252: Unable to handle route request: string
Cause: Command requested did not exist.
Action: None
TNS-00253: Error in reading network configuration data from file string with error string
Cause: TNSNET.ORA is poorly configured or nonexistent.
Action: Check to make sure that TNSNET.ORA is properly configured.
TNS-00254: Navigator has been stopped
Cause: Message sent to Interchange control program by Navigator confirming it has been stopped.
Action: None
TNS-00255: Closing down log, stopping Navigator
Cause: Log message when Navigator is stopped.
Action: None
TNS-00256: Status of Navigator:
Cause: Navigator status message component
Action: None
TNS-00257: Number of Successful Requests : number
Cause: Navigator status message component
Action: None
TNS-00258: Number of Failed Requests : number
Cause: Navigator status message component
Action: None
TNS-00259: Disabled Interchange list:
Cause: Navigator status message component
Action: None
TNS-00260: -------------------------------------------------------------------
Cause: Navigator status message component
Action: None
TNS-00261: Interchange Name Community Link Down Time Remaining (secs)
Cause: Navigator status message component
Action: None
TNS-00262: stringstringnumber
Cause: Navigator status message component
Action: None
TNS-00263: Navigator: Request Failed
Cause: Response from Navigator when a particular request failed.
Action: None
TNS-00264: Navigator: Failed to reload configuration data
Cause: Message sent to the Interchange control program when reload of network configuration failed. TNSNET.ORA Poorly configured or missing.
Action: None
TNS-00265: Navigator: Reloaded network configuration data
Cause: Message sent to Interchange control program when reload of network is successful.
Action: None
TNS-00266: Navigator: Unknown Request
Cause: Request was made to Navigator that it knows nothing about.
Action: None
TNS-00267: Navigator: Internal Error
Cause: Generated when a request was made to the Navigator it knows nothing about.
Action: None
TNS-00268: ON
Cause: On component of message.
Action: None
TNS-00269: OFF
Cause: Off component of message.
Action: None
TNS-00270: string: Terminal Error string
Cause: Message put out in error file of executable when it fails to start.
Action: None
TNS-00271: Connection Manager
Cause: Name of the Connection Manager.
Action: None
TNS-00272: Navigator
Cause: Name for the Navigator.
Action: None
TNS-00273: Navigator: Logging is now ON
Cause: Message sent back to control program from Navigator.
Action: None
TNS-00274: Navigator: Logging is now OFF
Cause: Message sent back to control program from Navigator.
Action: None
TNS-00275: Navigator: Tracing is now ON
Cause: Message sent back to control program from Navigator.
Action: None
TNS-00276: Navigator: Tracing is now OFF
Cause: Message sent back to control program from Navigator.
Action: None
TNS-00277: Navigator: Request Failed
Cause: Message sent back to control program from Navigator.
Action: None
TNS-00278: Navigator: Failed to Open Log file
Cause: Message sent back to control program from Navigator.
Action: None
TNS-00279: Navigator: Failed to Start Tracing
Cause: Message sent back to control program from Navigator.
Action: None
TNS-00280: Max Avg Bytes/Sec : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00281: Connection Manager: Forced Log output
Cause: Message sent back to control program from Connection Manager.
Action: None
TNS-00282: Connection Manager: Failed to force log, logging is off
Cause: Message sent back to control program from Connection Manager.
Action: None
TNS-00283: Listening on the following TNS addresses:
Cause: Message sent back to control program from Connection Manager.
Action: None
TNS-00284: Imm Max Avg Bytes/Sec : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00285: Avg Connect Time (secs) : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00286: Max Connect Time (secs) : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00287: Min Connect Time (secs) : number
Cause: Part of status request for Connection Manager.
Action: None
TNS-00288: Navigator: Failed to Disable Interchange
Cause: Message sent back to control program from Navigator.
Action: None
TNS-00289: Navigator: Disabled Interchange
Cause: Message sent back to control program from Navigator.
Action: None
TNS-00290: Navigator: Failed to Enable Interchange
Cause: Message sent back to control program from Navigator.
Action: None
TNS-00291: Navigator: Enabled Interchange
Cause: Message sent back to control program from Navigator.
Action: None
TNS-00292: Log File Name : string
Cause: Message sent back to control program showing log file name
Action: None
TNS-00293: Trace File Name : string
Cause: Message sent back to control program showing trace file name
Action: None
TNS-00294: Connection Manager: Security is enabled, you cannot STOP the Interchange
Cause: Message sent back to control program indicating that the connection manager is secure.
Action: None
TNS-00295: Navigator: Security is enabled, you cannot STOP the Navigator
Cause: Message sent back to control program indicating that the Navigator is secure.
Action: None
TNS-00296: Stoppable : string
Cause: Message sent back to control program indicating whether program can be stopped.
Action: None
TNS-00297: Logging Level : string
Cause: Message sent back to control program indicating whether program can be stopped.
Action: None
TNS-00298: Request to Navigator: string
Cause: Log entry for request to Navigator.
Action: None
TNS-00299: Response from Navigator: string
Cause: Log entry for request to Navigator.
Action: None
TNS-00300: ***Disabling Interchange : string
Cause: Log entry for disabling a particular Interchange.
Action: None
TNS-00301: ***Enabling Interchange : string
Cause: Log entry for disabling a particular Interchange.
Action: None
TNS-00302: Connection Manager: Unknown Request
Cause: Request sent by Interchange control program is unknown.
Action: None
TNS-00303: Connection Manager: Reread parameter data
Cause: Request sent by control manager to control programming indicating that parameter data was read.
Action: None
TNS-00304: Status Information for Connection Manager:
Cause: Message sent back by Interchange as header for status request.
Action: None
TNS-00305: The Navigator encountered an invalid/unknown trace level
Cause: Message sent back by the Navigator indicating an invalid trace level.
Action: Reattempt the request with a correct trace level.
TNS-00306: Connection Manager encountered an invalid/unknown trace level
Cause: Message sent back by the Connection Manager indicating an invalid trace level.
Action: Reattempt the request with a correct trace level.
TNS-00307: Navigator: Reread parameter data
Cause: Request sent by the Navigator to control program indicating that parameter data was read.
Action: None
TNS-00308: Navigator: Failed to open log while rereading parameter data
Cause: Request sent by the Navigator to control program indicating that it could not reopen log file after rereading parameter data.
Action: None
TNS-00309: Connection Manager: Failed to open log while re-reading parameter data
Cause: Request sent by the Connection Manager to control program indicating that it could not reopen log file after rereading parameter data.
Action: None
TNS-00310: Navigator: Failed to start tracing after rereading parameter data
Cause: Message sent back to control program from Navigator.
Action: None
TNS-00311: Connection Manager: Failed to start tracing after rereading parameter data
Cause: Message sent back to control program from Connection Manager.
Action: None
TNS-00312: Connection Manager: Failed to get version information
Cause: Message sent back to control program from Connection Manager.
Action: None
TNS-00313: Navigator: Failed to get version information
Cause: Message sent back to control program from Connection Manager.
Action: None
TNS-00314: Protocol Adapter Errors: number,number
Cause: Protocol Adapter errors which go with message 233
Action: None
TNS-00315: Failed to allocate larger connect data area for getting pump data: number
Cause: Could not allocate a large enough area to get pump statistics; continue without them.
Action: None
TNS-00316: Ran out of data buffers in the pump
Cause: The Interchange is resource limited by having too few data buffers in the pump.
Action: If the problem persists (that is, there are a lot of log messages), increase the number of pump buffers by increasing the value of the parameter PUMP_BUFFERS in INTCHG.ORA. Then shutdown and restart the Interchange to make the changes take effect.
TNS-00317: Failed to contact Connection Manager
Cause: Connection Manager is not running.
Action: Start the Connection Manager and retry
TNS-00501: Cannot allocate memory
Cause: Sufficient memory could not be allocated to perform the desired activity.
Action: Either free some resource for TNS or add more memory to the machine. For further details, turn on tracing and reexecute the operation.
TNS-00502: Invalid argument
Cause: An internal function received an invalid parameter.
Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-00503: Illegal ADDRESS parameters
Cause: An illegal set of protocol adapter parameters was specified.
Action: Check the parameters within the ADDRESS section of the TNSNAMES.ORA file. It may be helpful to turn on tracing and look at the addresses specified in the trace file, checking for spelling or other errors. Be sure to turn tracing off when the trace is complete.
TNS-00504: Operation not supported
Cause: An internal function received a request to perform an operation that is not supported (on this machine).
Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-00505: Operation timed out
Cause: The requested operation could not be completed within the timeout period.
Action: For further details, turn on tracing and reexecute the operation.
TNS-00506: Operation would block
Cause: An internal operation did not commence because to do so would block the current process and the user has requested that operations be non-blocking.
Action: None needed; this is an information message.
TNS-00507: Connection closed
Cause: Normal "end of file" condition has been reached; partner has disconnected.
Action: None needed; this is an information message.
TNS-00508: No such protocol adapter
Cause: The protocol adapter requested for this connection does not exist.
Action: Install the protocol adapter or use one that is available. Be sure that the correct protocols are listed in the configuration files.
TNS-00509: Buffer overflow
Cause: Too much data for buffer.
Action: Reexecute with larger receive buffer or smaller send buffer.
TNS-00510: Internal limit restriction exceeded
Cause: Too many files or sockets open simultaneously (or some other resource has been depleted).
Action: For further details, trace the operation for protocol details.
TNS-00511: No listener
Cause: The connect request could not be completed because no application is listening on the address specified, or the application is unable to service the connect request in a sufficiently timely manner.
Action: Ensure that the supplied destination address matches one of the addresses used by the listener - compare the TNSNAMES.ORA entry with appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to go by way of an Interchange. Start the listener on the remote machine.
TNS-00512: Address already in use
Cause: Specified listener address is already being used.
Action: Start your listener with an unused address.
TNS-00513: Destination host unreachable
Cause: Contact cannot be made with remote party.
Action: Make sure the network driver is functioning and the network is up.
TNS-00514: Contexts have different wait/test functions
Cause: Two protocol adapters have conflicting wait/test functions.
Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-00515: Connect failed because target host or object does not exist
Cause: The address specified is not valid, or the program being connected to does not exist.
Action: Ensure the ADDRESS parameters have been entered correctly; the most likely incorrect parameter is the node name. Ensure that the executable for the server exists (perhaps "oracle" is missing.)
TNS-00516: Permission denied
Cause: User has insufficient privileges to perform the requested operation.
Action: Acquire necessary privileges and try again.
TNS-00517: Lost contact
Cause: Partner has unexpectedly gone away.
Action: Investigate partner application for abnormal termination.
TNS-00518: Incomplete read or write
Cause: A data send or receive failed.
Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-00519: Operating system resource quota exceeded
Cause: The current user has exceeded the allotted resource assigned in the operating system.
Action: Acquire more operating system resource, or perform a different function.
TNS-00520: Syntax error
Cause: The supplied connect descriptor contains illegal syntax.
Action: Check the syntax of the connect descriptor for correct syntax.
TNS-00521: Missing keyword
Cause: The supplied connect descriptor is missing one or more TNS keywords.
Action: Check the syntax, and ensure all required keywords are present.
TNS-00522: Operation was interrupted
Cause: An internal operation was interrupted and could not complete.
Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-00523: Previous operation was busy
Cause: Operation tried could not be successfully completed because the requested resource was busy.
Action: Attempt the operation again. If error persists, contact Oracle Customer Support.
TNS-00524: Current operation is still in progress
Cause: Internal operation is still in progress but will complete.
Action: None; wait for operation to complete.
TNS-00525: Insufficient privilege for operation
Cause: Operating system failed to complete operation because user lacked sufficient privileges.
Action: Check your platform-specific privileges.
TNS-00526: No caller (false async event)
Cause: Internal error.
Action: For further details, turn on tracing and reexecute the operation.
TNS-00527: Protocol Adapter not loadable
Cause: On some platforms (for example OS/2) protocol adapters are loaded at run-time. If the shared library (or DLL) for the protocol adapter is missing or one of its supporting libraries is missing, then this error is returned.
Action: For further details, turn on tracing and reexecute the operation. The trace file will have the name of the shared library (or DLL) that could not be loaded.
TNS-00528: Protocol Adapter not loaded
Cause: On some platforms (for example OS/2) protocol adapters are loaded at run-time. If the shared library (or DLL) for the protocol adapter has not been loaded, then this error is returned.
Action: For further details, turn on tracing and reexecute the operation. The trace file will have the name of the shared library (or DLL) that has not been loaded.
TNS-00530: Protocol adapter error
Cause: A generic protocol adapter error occurred.
Action: For further details, turn on tracing and reexecute the operation.
TNS-00532: No previous async operation to wait on
Cause: Internal protocol adapter error.
Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-00533: Connection dissolved or not yet made
Cause: Internal protocol adapter error.
Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-00534: Failed to grant connection ownership to child
Cause: Internal protocol adapter error.
Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-00535: Failed to send or receive disconnect message
Cause: Internal protocol adapter error.
Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-00536: Connection entered inappropriate state
Cause: Internal protocol adapter error.
Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-00537: Index into protocol adapter table is out of legal range
Cause: Internal protocol adapter error.
Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-00539: Network or Protocol services are down
Cause: The Network services on or from your node are not running or have stopped running.
Action: Restart your network or protocol services on this platform. If error persists, contact Oracle Customer Support.
TNS-00540: SSL protocol adapter failure
Cause: The SSL protocol adapter encountered an error.
Action: In most cases, this error should only be pair with a more meaningful ORA- error.
TNS-00541: underlying transport does not exist.
Cause: The SSL protocol adapter was unable to locate an adapter for the protocol that it is going to use as the data transport.
Action: In most cases, the underlying transport is TCP. Make sure that the Oracle Net TCP/IP adapter was installed.
TNS-00542: SSL Handshake failed
Cause: The SSL protocol adapter was unable to connect to another process.
Action: This error can be caused by a variety of problems including the termination of the peer process. Enable Oracle Net tracing and attempt the connection again. The trace file should give some clues as to what the exact problem is.
TNS-00543: internal error
Cause: The SSL protocol adapter encountered an unexpected error.
Action: This error is not normally visible to users. Enable Oracle Net tracing and attempt to reproduce the error. If it occurs, contact Oracle customer support.
TNS-00544: unsupported operation
Cause: The SSL adapter could not perform a given command.
Action: This error is not normally visible to users. Enable Oracle Net tracing and attempt to reproduce the error. If it occurs, contact Oracle customer support.
TNS-00545: parameter retrieval failure
Cause: The SSL protocol adapter was not able to retrieve a configuration parameter for some reason.
Action: This error is not normally visible to users. Enable Oracle Net tracing and attempt to reproduce the error. If it occurs, contact Oracle customer support.
TNS-00546: control failure
Cause: The SSL protocol adapter was unable to perform a command.
Action: This error is not normally visible to users. Enable Oracle Net tracing and attempt to reproduce the error. If it occurs, contact Oracle customer support.
TNS-00547: user information retrieval failed
Cause: The SSL protocol adapter was unable to retrieve information about the remote user.
Action: Examine the first error in the error stack. It should describe the error in more detail.
TNS-00548: value specified for client authentication parameter is not boolean
Cause: The value specified for the parameter that specifies that SSL client authentication is to be used was not boolean.
Action: Specify a correct value for the parameter.
TNS-00549: value specified for the SSL version is not valid
Cause: The value specified for the SSL version is not valid.
Action: Specify a valid value for the SSL version.
TNS-00550: disconnection error
Cause: The SSL protocol adapter encountered an error when the underlying transport disconnected.
Action: This error is not normally visible to users. Enable Oracle Net tracing and attempt to reproduce the error. If it occurs, contact Oracle customer support.
TNS-00551: underlying transport connection failed
Cause: The underlying transport adapter used by the SSL adapter failed to connect.
Action: Enable Oracle Net tracing and try the connection again. If the connection fails, examine the trace file to determine the cause.
TNS-00552: no valid cipher suites were specified
Cause: SSL cipher specs were specified, but none were valid.
Action: Specify correct cipher suites.
TNS-00553: read failed
Cause: The SSL adapter failed to read data from its connection.
Action: Examine the contents of sqlnet.log for more information. Enable Oracle Net tracing and try the connection again. If the connection fails, examine the trace file to determine the cause.
TNS-00554: write failed
Cause: The SSL adapter failed to send data over its connection.
Action: Examine the contents of sqlnet.log for more information. Enable Oracle Net tracing and try the connection again. If the connection fails, examine the trace file to determine the cause.
TNS-00555: no directory specified for wallet resource locator
Cause: It was specified that a file was to be used from which to retrieve a wallet, but no directory was specified for the wallet.
Action: Specify the directory where the wallet is located.
TNS-00556: no method specified for wallet retrieval
Cause: A wallet resource locator was specified, but no method was given for the retrieval of the wallet.
Action: Specify the method by which the method is to be retrieved.
TNS-00557: unsupported wallet retrieval method
Cause: The method specified for wallet retrieval is not supported. Currently, only files are supported for wallet retrieval.
Action: Specify "FILE" as the wallet retrieval method.
TNS-00558: Entrust login failed
Cause: Entrust failed to authenticate the username, password, and/or profile name that was presented.
Action: Specify correct values for the username, password or profile name. If no data was prompted for, contact Oracle support.
TNS-00559: load of Entrust certificate failed
Cause: An error occurred while attempting to validate the provided Entrust certificate.
Action: This error is not normally visible to users. Enable Oracle Net tracing and attempt to reproduce the error. If it occurs, contact Oracle customer support.
TNS-00560: extraction of name from Entrust certificate failed
Cause: An error occurred while attempting to extract a name from an Entrust certificate.
Action: This error is not normally visible to users. Enable Oracle Net tracing and attempt to reproduce the error. If it occurs, contact Oracle customer support.
TNS-00580: Read failed due to closed or invalid transport connection
Cause: Read attempt was made on a transport connection which was previously terminated or is somehow deemed to be invalid.
Action: Indicates a substantial transport level failure. Check the O/S configuration for the particular transport or contact the transport provider. For further details, turn on tracing and reexecute the operation.
TNS-00581: Send failed due to timeout
Cause: The send operation did not complete within the allowed time interval.
Action: Error is informational. Note, repeated receipt of this error could indicate an attempted Denial-Of-Service attack. Also, if the receipt of this error interferes w/ a customer's normal operations, the customer may wish to lengthen the timeout.
TNS-00582: Receive failed due to timeout
Cause: The receive operation did not complete within the allowed time interval.
Action: Error is informational. Note, repeated receipt of this error could indicate an attempted Denial-Of-Service attack. Also, if the receipt of this error interferes w/ a customer's normal operations, the customer may wish to lengthen the timeout.
TNS-00583: Valid node checking: unable to parse configuration parameters
Cause: Valid node checking was unable to parse the configuration due to syntactical errors.
Action: Ensure that the configuration syntax matches the Oracle reference manual documented syntax. For further details, turn on tracing and reexecute the operation.
TNS-00584: Valid node checking configuration error
Cause: Valid node checking specific Oracle Net configuration is invalid.
Action: Ensure the hosts specified in the "invited_nodes" and "excluded_nodes" are valid. For further details, turn on tracing and reexecute the operation.
TNS-01000: spawn [<listener_name>] <spawn_alias> [<(ARGUMENTS='arg0, arg1,...')>]
Cause: Control program usage message.
Action: None
TNS-01001: start [<listener_name>] : start listener
Cause: Control program usage message.
Action: None
TNS-01002: stop [<listener_name>] : stop listener
Cause: Control program usage message.
Action: None
TNS-01003: status [<listener_name>] : get the status of listener
Cause: Control program usage message.
Action: None
TNS-01004: reload [<listener_name>] : reload the parameter files and SIDs
Cause: Control program usage message.
Action: None
TNS-01005: trace OFF | USER | ADMIN | SUPPORT [<listener_name>] : set tracing to the specified level
Cause: Control program usage message.
Action: None
TNS-01006: set password : set the password for subsequent calls
Cause: Control program usage message.
Action: None
TNS-01007: quit | exit : exit LSNRCTL
Cause: Control program usage message.
Action: None
TNS-01008: version [<listener_name>] : get the version information of the listener
Cause: Control program usage message.
Action: None
TNS-01009: service [<listener_name>] : get the service information of the listener
Cause: Control program usage message.
Action: None
TNS-01013: set|show trc_{ } [<value>]: set|show trace parameters of current listener
Cause: Control program usage message.
Action: None
TNS-01014: set|show log_{ } [<value>]: set|show log parameters of current listener
Cause: Control program usage message.
Action: None
TNS-01015: set|show parm_name [<value>]: sets|shows current listener parm values
Cause: Control program usage message.
Action: None
TNS-01016: change_password [<listener_name>]: changes the password of the listener
Cause: Control program usage message.
Action: None
TNS-01017: set|show current_listener [<listener_name>]: sets|shows current listener
Cause: Control program usage message.
Action: None
TNS-01018: save_config [<listener_name>]: saves configuration changes to parameter file
Cause: Control program usage message.
Action: None
TNS-01019: set rawmode ON | OFF: set output mode for services and status commands
Cause: Control program usage message.
Action: None
TNS-01020: STATUS of the LISTENER
Cause: Control program status message.
Action: None
TNS-01021: ------------------------
Cause: Control program status message.
Action: None
TNS-01022: Alias string
Cause: Control program status message.
Action: None
TNS-01023: Version string
Cause: Control program status message.
Action: None
TNS-01024: Trace Level string
Cause: Control program status message.
Action: None
TNS-01025: Security string
Cause: Control program status message.
Action: None
TNS-01026: Start Date string
Cause: Control program status message.
Action: None
TNS-01027: Listener Trace File string
Cause: Control program status message.
Action: None
TNS-01028: Listener Log File string
Cause: Control program status message.
Action: None
TNS-01029: Services Summary...
Cause: Control program status message.
Action: None
TNS-01030: The listener supports no services
Cause: Control program status message.
Action: None
TNS-01033: Listener Parameter File string
Cause: Control program status message.
Action: None
TNS-01034: Uptime number days number hr. number min. number sec
Cause: Control program status message.
Action: None
TNS-01036: string established:string refused:string
Cause: Control program status message.
Action: None
TNS-01037: "string" established:string refused:string
Cause: Control program status message.
Action: None
TNS-01038: string established:string refused:string current:string max:string state:string
Cause: Control program status message.
Action: None
TNS-01039: string has string service handler(s)
Cause: Control program status message.
Action: None
TNS-01040: SNMP string
Cause: Control program status message.
Action: None
TNS-01041: string parameter "string" set to string
Cause: Control program status message.
Action: None
TNS-01042: Current Listener is string
Cause: Control program status message.
Action: None
TNS-01043: Password changed for string
Cause: Control program status message.
Action: None
TNS-01044: string(Registered) has string service handler(s)
Cause: Control program status message.
Action: None
TNS-01045: string(Not Registered) has string service handler(s)
Cause: Control program status message.
Action: None
TNS-01046: Saved string configuration parameters.
Cause: Control program status message.
<span class="msgactionkw">Action: None
TNS-01047: Old Parameter File string
Cause: Control program status message.
Action: None
TNS-01048: No changes to save for string.
Cause: Control program status message.
Action: None
TNS-01049: string (string) has string service handler(s)
Cause: Control program status message.
Action: None
TNS-01050: string
Cause: Control program general message.
Action: None
TNS-01052: The command completed successfully
Cause: Control program general message.
Action: None
TNS-01053: Connecting to string
Cause: Control program general message.
Action: None
TNS-01054: Contacted the listener successfully
Cause: Control program general message.
Action: None
TNS-01055: Successfully stopped the listener
Cause: Control program general message.
Action: None
TNS-01057: Program name: string
Cause: Control program general message.
Action: None
TNS-01058: Arguments : string
Cause: Control program general message.
Action: None
TNS-01059: Environment : string
Cause: Control program general message.
Action: None
TNS-01060: The password has has been set to: string
Cause: Control program general message.
Action: None
TNS-01061: The password has not been set
Cause: Control program general message.
Action: None
TNS-01062: The db subagent is already running.
Cause: Control program general message.
Action: None
TNS-01063: The db subagent is not started.
Cause: Control program general message.
Action: None
TNS-01064: Listener configuration changes will not be persistent
Cause: Configuration changes to the listener will not be visible when the listener starts up again as the check-pointing has been turned off in listener.ora
Action: Edit LISTENER.ORA setting USE_CKPFILE_LISTENER=true
TNS-01065: Raw mode is string
Cause: Control program general message.
Action: None
TNS-01066: Presentation: string
Cause: Listener starting message.
Action: None
TNS-01067: Service display mode is string
Cause: Control program general message.
Action: None
TNS-01070: Starting string: please wait...
Cause: Listener starting message.
Action: None
TNS-01071: string is set to string
Cause: Listener starting message.
Action: None
TNS-01072: Started at string
Cause: Listener starting message.
Action: None
TNS-01073: Listening on: string
Cause: Listener starting message.
Action: None
TNS-01074: Error listening on: string
Cause: Listener starting message.
Action: None
TNS-01075: Opened log file: string
Cause: Listener starting message.
Action: None
TNS-01076: Opened trace file: string
Cause: Listener starting message.
Action: None
TNS-01077: Opened parameter file: string
Cause: Listener starting message.
Action: None
TNS-01078: Opened name lookup file: string
Cause: Listener starting message.
Action: None
TNS-01079: Attempted to bequeath: string
Cause: Listener starting message.
Action: None
TNS-01080: Listener failed to start. See the error message(s) above...
Cause: Listener starting message.
Action: None
TNS-01081: Started with pid=string
Cause: Listener starting message.
Action: None
TNS-01082: Running in PROXY mode
Cause: Listener starting message.
Action: None
TNS-01090: No longer listening on: string
Cause: Listener logging message.
Action: None
TNS-01091: Listener(VNCR option number) rejected Registration request from destination string
Cause: Listener logging message.
Action: None
TNS-01093: string * string * number
Cause: Listener logging message.
Action: None
TNS-01094: string * number
Cause: Listener logging message.
Action: None
TNS-01095: string * string * string * number
Cause: Listener logging message.
Action: None
TNS-01096: string * string * string * string * string * number
Cause: Listener logging message.
Action: None
TNS-01097: TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
Cause: Listener logging message.
Action: None
TNS-01098: TIMESTAMP * CONNECT DATA * ADDRESS * [PRESENTATION *] COMMAND * ERROR TIMESTAMP * [INSTANCE NAME *] [ADDRESS *] [PRESENTATION *] COMMAND * ERROR -------------------------------------------------------------------------------
Cause: Listener logging message.
Action: None
TNS-01099: string * string * string * string * number
Cause: Listener logging message.
Action: None
TNS-01100: TNS returned error number when attempting to start the listener
Cause: d by the fact that the TNSLSNR executable cannot be found in the place expected in your platform's ORACLE environment. Verify that the full pathname of the TNSLSNR executable as displayed by LSNRCTL is correct.
Action: If NS error code 12538 is also returned then the BEQ driver is not installed; call Oracle Worldwide Support as the BEQ driver should always be installed. If this is not the problem then the error is probably
TNS-01101: Could not find service name string
Cause: The ervice name could not be resolved by name-lookup.
Action: Verify that the listener name or service name specified to LSNRCTL has the correct name and address defined in LISTENER.ORA or in TNSNAMES.ORA.
TNS-01102: TNS application contacted was not the listener
Cause: Another TNS application such as the Interchange was listening at the address contacted. There may be another TNS application listening at the address contacted and the data returned is not in the appropriate format.
Action: Verify that the listener name or service name specified to LSNRCTL has the correct name and address defined in LISTENER.ORA or in TNSNAMES.ORA.
TNS-01103: Protocol specific component of the address is incorrectly specified
Cause: The ADDRESS used to contact the listener is not correctly specified. This error occurs because the address fails to specify the destination of the listener. The address is well formed (for example, there are no missing parentheses) but it is missing a protocol specific component. For example, this is the error returned when the HOST component is missing from a TCP/IP address string.
Action: Edit the ADDRESS in LISTENER.ORA to include the required protocol-specific keywords. For more information about the keywords required by different protocol adapters, see the Oracle operating system specific documentation for your platform.
TNS-01106: Listener using listener name string has already been started
Cause: Another listener is already listening on one of the ADDRESSes specified.
Action: Shutdown the previous listener specified by the listener name before starting this one.
TNS-01107: A valid trace level was not specified
Cause: Failed to specify a valid trace level for the LSNRCTL trace command.
Action: Specify one of OFF, USER, ADMIN, or SUPPORT. Type "LSNRCTL help trace" for more information or consult Chapter 2 of this manual for an introduction to the concepts of tracing.
TNS-01108: Listener password prompt failed
Cause: Password not entered via tty
Action: Enter the listener password on a tty device
TNS-01109: Listener password encryption failed
Cause: Possibly garbled password entered
Action: Re-enter the listener password, using valid ASCII characters. If problem persists, contact Oracle Customer Support.
TNS-01110: Mismatch - password unchanged
Cause: New password and reentered new password are different"
Action: Re-enter the listener password, make sure that New password and reentered new password are the same
TNS-01111: Log status can either be ON or OFF
Cause: Failed to specify a log status value for the LSNRCTL log_status command.
Action: Specify one of ON or OFF. Type "LSNRCTL help set log_status" for more information or consult Chapter 2 of this manual for an introduction to the concepts of logging.
TNS-01112: Plug and play can either be ON or OFF
Cause: Failed to specify a valid value for the LSNRCTL use_plugandplay command.
Action: Specify one of ON or OFF. Type "LSNRCTL help set use_plugandplay" for more information.
TNS-01113: save_config_on_stop can either be ON or OFF
Cause: Failed to specify a valid value for the LSNRCTL save_config_on_stop command.
Action: Specify one of ON or OFF. Type "LSNRCTL help set save_config_on_stop" for more information.
TNS-01114: LSNRCTL could not perform local OS authentication with the listener
Cause: LSNRCTL failed to obtain system resources (heap memory, or shared memory) needed to perform local OS authentication with the listener.
Action: Make sure that system resources like shared memory and heap memory are available for LSNRCTL tool to execute properly.
TNS-01115: OS error string creating shared memory segment of string bytes with key string
Cause: The shared memory segment could not be created as requested. For example, a segment with the provided key may already exist, or the size may be outside of system allowed range.
Action: Use the error code to determine the exact cause of the problem. In certain cases the problem may be resolved by adjusting the system-imposed limits such as the maximum number of allowed shared memory segments, or their maximum and minimum sizes. In other cases, resources need to be freed up first for the operation to succeed.
TNS-01116: Listener alias name given as connect identifier is too long
Cause: The listener alias name you were attempting to resolve was too long.
Action: The maximum length of a listener alias name is 255 bytes; this limit has been exceeded. Use a smaller listener alias name.
TNS-01150: The address of the specified listener name is incorrect
Cause: The address on which the listener attempted to listen contains a syntax error.
Action: For the listener name or service name specified to LSNRCTL, check that the address or connect descriptor is well-formed. You can find the listener name in LISTENER.ORA, or you can access the listener through the service name is TNSNAMES.ORA.
TNS-01151: Missing listener name, string, in LISTENER.ORA
Cause: The listener could not find the listener name specified.
Action: Make sure valid addresses on which to listen are specified for the listener name in LISTENER.ORA.
TNS-01152: All addresses specified for the listener name, string, failed
Cause: The listener failed to listen on any of the specified addresses.
Action: Make sure that another application is not listening on the addresses specified or check that the appropriate protocol adapters are installed. Turn on tracing and execute again for more information.
TNS-01153: Failed to process string: string
Cause: The string specified is not well-formed.
Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.
TNS-01154: SID detected in old format that is no longer supported
Cause: One of the SIDs was specified in an obsolete format.
Action: Check LISTENER.ORA for a line of the form: <sid> = (SID=(ORACLE_HOME=<oracle_home>)) OR <sid> = (SID_DESC=(ORACLE_HOME=<oracle_home>)) The above format is no longer supported and SID_LIST_<listener_name> format described in the Oracle9i Net Services Reference Guide should be used. For example, SID_LIST_LISTENER = (SID_LIST=(SID_DESC=(SID_NAME=<sid>)(ORACLE_HOME=<oracle_home>)))
TNS-01155: Incorrectly specified SID_LIST_string parameter in LISTENER.ORA
Cause: SID_LIST_<listener_name> in LISTENER.ORA has an error in it.
Action: Be sure this parameter is specified as described in the Oracle9i Net Services Reference Guide. For example, SID_LIST_LISTENER = (SID_LIST=(SID_DESC=(SID_NAME=<sid>)(ORACLE_HOME=<oracle_home>)))
TNS-01156: Missing or inappropriate PROTOCOL, TIMEOUT or POOL_SIZE parameter from PRESPAWN_DESC
Cause: PRESPAWN_DESC in each SID_DESC does not have required fields.
Action: Be sure the parameters required for PRESPAWN_DESC are specified in each SID_DESC. For example, SID_LIST_LISTENER = (SID_LIST=(SID_DESC=(SID_NAM