Release 8.0
A54625_01
 Library |
 Product |
 Contents |
| Oracle8
Error Messages Release 8.0 A54625_01 |
|
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 controlfile record number may not have been determined when the message is printed. In that case, the record number shown is zero.
Action: Other messages should display to help pinpoint the cause and the solution.
Cause: An attempt was made to copy or backup a file that was not closed cleanly, and the database was in NOARCHIVELOG mode. This is not allowed because when restored, the file will require redo application before it is usable, and redo is not currently being saved beyond the contents of the online redo logs.
Action: Take the tablespace offline, clean or close the database, and retry the COPY or BACKUP operation.
Cause: A call was made to specify a file to be backed up or restored after the first backup piece has been processed.
Action: Do not 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, begin a new conversation.
Cause: The input file name was not specified for a controlfile COPY operation.
Action: Specify an input filename and retry the operation.
Cause: A controlfile copy or restore operation specified the name of the snapshot controlfile as the output file. It is not permitted to overwrite the snapshot controlfile in this manner. Other methods are available to create the snapshot controlfile.
Action: Specify a different file name and retry the operation. If this is a RESTORE, then the RESTORE conversation remains active and more files can be specified.
Cause: A controlfile COPY, RESTORE, or BACKUP specified the name of a controlfile 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 can be specified.
Cause: The specified file was 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.
Cause: The specified file was 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.
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.
Cause: This backup piece is out of sequence.
Action: Supply the correct backup piece.
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.
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 controlfile.
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.
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.
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 not found.
Action: See the instructions for message 19613.
Cause: A datafile restore specified no target filename, but the database is not mounted. The database must be mounted when no target filename is specified, so that the target filename can be obtained from the controlfile.
Action: The restore conversation remains active. If you wish to restore datafiles without their target filenames, then mount the database before continuing. Otherwise, a target filename must be specified on all datafile restoration calls.
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.
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 want to specify files to restore.
Cause: The restoreValidate operation was called after some files had already been specified for restoration.
Action: You must cancel and restart the conversation if you want to call restoreValidate.
Cause: You specified an archive log destination for restoreSetRedoLog which exceeds the system maximum.
Action: Retry the operation with a shorter archive log destination.
Cause: A range of logs has already been specified. Only one SCN range can be specified per conversation.
Action: The restore conversation remains active and more logs can be specified by thread and sequence number, if desired.
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.
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.
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 to retry the operation.
Cause: A file specified as input to a COPY or BACKUP operation, or as the target for an incremental RESTORE, was not found.
Action: Specify an existing file and retry the operation.
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.
Cause: This is a controlfile RESTORE conversation, which is using the offline range information from one or more controlfiles to update datafile checkpoint data. Backup sets are not used during this type of conversation.
Action: The conversation is still active and more controlfiles can be applied.
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.
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.
Cause: While copying a backup piece from the OS native filesystem 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.
Cause: This archivelog 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 archivelog record that contains a file name. Fixed view V$ARCHIVED_LOG can be used to examine the archived logs.
Cause: The name passed to getFno was not found in the controlfile.
Action: Supply a valid filename and retry the operation.
Cause: The controlfile record describing the file to be deleted in a call to deletePiece, deleteDataFilecopy, or deleteRedoLog does not match the validation data supplied by recovery manager.
Action: Contact Oracle support.
Cause: The fname or handle parameter was not specified for deletePiece, deleteDataFileCopy, or deleteRedoLog.
Action: Specify the fname parameter when calling these functions.
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.
Cause: The indicated archivelog has already been specified for inclusion in this RESTORE conversation. A RESTORE conversation may process only one copy of any archivelog.
Action: No action required - the conversation is still active, and more files can be specified.
Cause: The session device is currently allocated to disk, and so a file name is required.
Action: Supply a filename and retry the operation.
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.
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.
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: Examine the other messages which should be present to indicate the cause of the failure.
Cause: This message identifies the checkpoint of a datafile in an incremental backup set that could not be applied.
Action: Examine the other messages which should be present to indicate the cause of the failure.
Cause: This message identifies the starting SCN of an incremental backup that could not be applied.
Action: Examine the other messages which should be present to indicate the cause of the failure.
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.
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.
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.
Cause: The indicated file was resized before this incremental backup was taken, but the incremental backup failed to set the file to the new size.
Action: Examine the other messages which should be present to indicate the cause of the failure.
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.
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.
Cause: applyOfflineRange was called with a recid/stamp which was not found in the indicated controlfile. This probably means that the specified controlfile is no longer the same controlfile that Recovery Manager thinks it is.
Action: Specify the recid/stamp of a record that exists in the controlfile copy.
Cause: This messages identifies the offline-clean SCN from the indicated offline-range record in the indicated file.
Action: See the accompanying error message.
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.
Cause: The target datafile for an applyOfflineRange call is fuzzy.
Action: Specify a target datafile that is closed cleanly.
Cause: SwitchToCopy was called with a datafile copy for a datafile that was dropped prior to the time this controlfile was backed up.
Action: Restore and mount an earlier controlfile. It is acceptable to use a controlfile that was backed up prior to the creation of the specified datafile.
Cause: This switchToCopy operation is attempting to switch incarnations of a datafile, but the currently mounted controlfile is not a backup controlfile.
Action: Restore and mount a backup controlfile.
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 controlfile that was taken from the same database version as the target datafile-copy, or switch to a different datafile-copy.
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.
Cause: The file being inspected is already part of the currently mounted database.
Action: None - the file is already part of the database.
Cause: The resetlogs data in the log file being inspected does not match that in the currently mounted controlfile.
Action: The indicated file cannot be processed - inspect another file.
Cause: This incremental backup cannot be applied to the specified datafile, because the datafile is from an earlier incarnation of the database, and its checkpoint would be advanced too far to be recoverable in the current incarnation of the database.
Action: This incremental cannot be applied to this datafile. To recover the file to the resetlogs SCN so that the database can be opened with the RESETLOGS option, use redo-log recovery, not incremental restore, to continue recovering this file.
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.
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.
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.
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.
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.
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.
Cause: The device type indicated is invalid.
Action: Supply a correct device type and retry the allocation.
Cause: The device name indicated is invalid.
Action: Supply a correct device name and retry the allocation.
Cause: The device parameter exceeds the port-specific maximum length.
Action: Correct the parameter and retry the operation.
Cause: The device command string exceeds maximum length.
Action: Correct the command and retry the operation.
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.
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.
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.
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.
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.
Cause: When starting a RESTORE conversation, a log restore destination longer than the port-specific maximum was specified.
Action: Supply a shorter destination and retry the operation.
Cause: A numeric parameter to an X$DBMS_BACKUP_RESTORE procedure is negative or contains a fractional portion.
Action: Supply a valid numeric parameter.
For more Stored Procedure messages, see "04040-04059: Stored Procedure Messages" on page 2¬313.
Cause: This message is raised when the SKIP_ROW procedure is called.
Action: This procedure should be called only within a trigger or a procedure called by a trigger.
Cause: The stored procedure RAISE_APPLICATION_ERROR was called, which causes this message to be generated.
Action: Correct the problem as described in the message or contact the application administrator or database administrator for more information.
Cause: An attempt was made to specify a number not in the range of -20000 to -20999.
Action: The valid range for user-specified error numbers is -20000 to -20999 inclusively. Do not specify numbers outside this range.
Cause: An attempt was made to specify a number not in the range of -23300 to -24299, or -29300 to -29399, inclusive.
Action: Use an error number in the range of -23300 to -24299, or -29300 to -29399, inclusive.
Internal messages are not documented in this manual.
Cause: The objects option was not installed at this site. Object types and other object features were, therefore, unavailable.
Action: Install the objects option. The objects option is not part of the Oracle Server product and must be purchased separately. Contact an Oracle sales representative if the objects option needs to be purchased.
Cause: This function requires the OCI process to be initialized in object mode.
Action: Specify OCI_OBJECT mode when calling OCIInitialize().
Cause: This is the generic error number for the user-side Oracle Runtime Environment for Objects (OREO) internal errors. This indicates that the runtime environment has encountered an exceptional condition.
Action: Report as a bug to Oracle Support - the first argument is the internal error number.
Cause: A program is in an unrecoverable state.
Action: Report as a bug to Oracle Support.
Cause: An attempted was made to connect to a persistent store driver that is not linked in.
Action: Check the server name supplied in origrgc(). Check if the driver corresponding to this server name has been linked in and entered in the server table.
Cause: An attempted was made to exceed the maximum number of connections allowed (255) per OMS instance.
Action: Close some of the existing connections using origurg() before requesting more connections.
Cause: There is no connection entry corresponding to this connection number.
Action: Check the connection number and ensure that the connection exists.
Cause: The type of the object is different from what was specified.
Action: Check the type of the object and correct it.
Cause: Attribute value or collection element value violated its constraint.
Action: Change the value of the attribute or collection element such that it meets its constraints. The constraints are specified as part of the attribute or collection element's schema information.
Cause: The argument is expecting a non-NULL, valid value but the argument value passed in is NULL, invalid, or out of range. Examples include when the LOB/FILE positional or size argument has a value outside the range 1 through (4GB - 1), or when an invalid open mode is used to open a file, etc.
Action: Check your program and correct the caller of the routine to not pass a NULL, invalid, or out-of-range argument value.
Cause: The path expression that was entered is too long. The path expression specifies the position of an attribute in an object. When the ORI* function retrieves the attribute using the path expression, it encounters an attribute of primitive type before finishing to consume the all the elements in the expression.
Action: Pass in the correct path expression to locate the attribute.
Cause: An attempt was made to perform an operation (that is valid only for an object type) to an attribute of primitive type. The operation includes dynamically setting a null structure to an attribute of primitive type.
Action: Avoid performing this operation on an attribute of primitive type.
Cause: The user attempts to perform an operation that does not support the specified typecode.
Action: User should use the range of valid typecodes that are supported by this function.
Cause: An attempt was made to perform an inappropriate operation to a deleted or non-existent object that is referenced by a dangling reference. Operations that cannot be applied to a non-existent or deleted object include deleting, updating and allocating memory.
Action: Re-initialize the reference in order to reference an existent object before performing the operation.
Cause: An attempt was made to perform an inappropriate operation to an object that is marked purged. The actual object could have been modified in the database. Operations that cannot be applied to a purged object includes updating, deleting and flushing.
Action: Pin the object again to get the new data.
Cause: An attempt was made to perform an inappropriate operation to a transient object that is not instantiated in the object cache. Operations that cannot be applied to a not-instantiated transient object include deleting or pinning such an object.
Action: Check the code to see if operations are being performed without instantiating the object first, or operations are being performed after the allocation duration of the object has expired.
Cause: The object could not be flushed because it has not been modified.
Action: The object should not be flushed.
Action: The transaction should be aborted or committed before terminating the cache or connection.
Cause: An attempt was made to supply a service context that is not valid.
Action: Establish the service context and retry the operation.
Cause: An attempt was made to supply a duration number that is not valid.
Action: Establish the duration or use a correct predefined duration.
Cause: An attempt was made to supply a pin duration that is longer than the allocation duration. This affects operations such as pinning and setting default parameters.
Action: Use a shorter pin duration or use the null duration.
Cause: An attempt was made to perform an inappropriate operation on a transient object. Operations that cannot be applied to a transient object include flushing and locking.
Action: Avoid performing operations such as flushing and locking on a transient object.
Cause: An attempt was made to perform an inappropriate operation on a not-current object. Operations that cannot be applied to a not-current object include locking, updating, deleting and flushing.
Action: Avoid performing locking, updating, deleting or flushing operations on a not-current object.
Cause: An attempt was made to supply an invalid object. A bad pointer might have been passed to the object or else a value might have been passed to a function that is expecting an object.
Action: Ensure that a valid pointer or a valid value is passed to the function.
Cause: An attempt was made to use a duration that has been terminated.
Action: Do not use terminated durations in operations.
Cause: An attempt was made to pass a variable-length string which is outside the valid range.
Action: Specify a string size which is within the valid range and retry the operation.
Cause: The number is too large to be represented by Oracle number.
Action: The operation is beyond the range of Oracle number.
Cause: Number is too small to be represented by Oracle number.
Action: The operation is beyond the range of Oracle number.
Cause: The signed flag that was used is not ORLTSB or ORLTUB as defined in ORL.H.
Action: Use either ORLTSB or ORLTUB as the sign flag.
Cause: A divide by zero operation has occurred.
Action: Modify the invalid operation and reissue the command.
Cause: An attempt was made to convert an integer of invalid length (that is, number of bytes) to or from an Oracle number.
Action: Use an integer length of 1, 2, 4 or 8 bytes only.
Cause: The buffer to hold the text string which wa to be converted from an Oracle number is too small.
Action: Use a buffer size at least that suggested in the error message and retry the operation.
Cause: An invalid or uninitialized number was passed to a function.
Action: Call kolnini() to initialize a number before using it.
Cause: An invalid numeric format string was used to convert characters to or from an Oracle number.
Action: See format specification in the description of the TO_NUMBER conversion function in the PL/SQL User's Guide and Reference.
Cause: An invalid text string was used for converting to numbers.
Action: Use a valid input string and retry the operation.
Cause: An attempt was made to convert a negative number to an unsigned integer.
Action: Use the sign flag ORLTSB to convert a signed number.
Cause: An invalid parameter string was used to convert characters to or from an Oracle number.
Action: See format specification under the TO_NUMBER conversion function in the PL/SQL User's Guide and Reference.
Cause: Rounding done due to the given string format causes overflow.
Action: Change the string format such that overflow does not occur.
Cause: An attempt was made to write a hexadecimal REF string into a buffer which is too small.
Action: Provide a buffer of the required size and retry the operation.
Cause: An attempt was made to give a hexadecimal string a length of zero or less.
Action: Specify a hexadecimal string length greater than zero.
Cause: The given hexadecimal string is invalid.
Action: Use the orlr2h() function for the value to obtain a valid hexadecimal string. Then retry the operation.
Cause: The given resize size is invalid.
Action: Ensure that the given size is in the required range.
Cause: An attempt was made to operate on an un-initialized variable-length array.
Action: Use the kolaini() function to initialize the variable-length array before performing an operation on it.
Cause: An attempt was made to resize a non-zero variable-length array to 0 elements.
Action: Do not perform this operation on a non-zero variable-length array.
Cause: An attempt was made to use a non-initialized variable-length array on the right-hand-side of an assignment (kolasg()) or as the destination array of an append.
Action: Use the kolaini() function to initialize the variable-length array, then retry the operation.
Cause: An attempt was made to use a non-initialized variable-length array on the left-hand-side of an assignment (kolasg()) or the as the source array of an append (kolapp()).
Action: Use the kolaini() function to initialize the variable-length array, then retry the operation.
Cause: An attempt was made to use a collection element at an index which does not exist.
Action: Specify the index of an element which exists, then retry the operation.
Cause: An invalid type code was used.
Action: Consult the ORO.H file for valid type codes.
Cause: An attempt was made to access a collection element which does not exist at the given index.
Action: Check for the existence of the element prior to calling the function. Then retry the function.
Cause: An attempt was made to use left hand and right hand side collections that are not of the same type.
Action: Ensure that the same collection type is passed for both left hand and right hand side of the operation (for example, ASSIGNMENT).
Cause: An attempt was made to delete an element of a VARRAY.
Action: Do not perform the DELETE ELEMENT operation on collections of type VARRAY. Ensure that the collection is not of type VARRAY prior to calling this function. Then retry the function.
Cause: An attempt was made to use an index not in the required range.
Action: Change the index so that it is in the required range, then retry the operation.
Cause: An attempt was made to use an empty collection.
Action: Test to see if the collection is empty prior to invoking this function.
Cause: An attempt was made to use a trim size which is greater than the current collection size.
Action: Assign a trim size less than or equal to the collection size, then retry this function.
Cause: There are several causes: (1) the LOB locator was never initialized; (2) the locator is for a BFILE and the routine expects a BLOB/CLOB/NCLOB locator; (3) the locator is for a BLOB/CLOB/NCLOB and the routine expects a BFILE locator; (4) trying to update the LOB in a trigger body -- LOBs in trigger bodies are read only.
Action: For (1), initialize the LOB locator by selecting into the locator variable or by setting the LOB locator to empty. For (2) and (3), pass the correct type of locator into the routine. For (4), remove the trigger body code that updates the LOB value.
Cause: There are several causes: (1) the locator was never enabled for buffering (2) it is not an updated locator but is being used for a write/flush operation.
Action: For (1) enable the locator for buffering; (2) ensure that only an updated locator is used for a LOB update operation
Cause: LOB buffering is enabled and an attempt was made to modify the same LOB using two different LOB locators.
Action: When using LOB buffering, modify the LOB through one LOB locator only.
Cause: LOB buffering is enabled for this LOB and there are buffers for this LOB in the buffer pool. Thus, updating the LOB through means other than the LOB buffers is not allowed.
Action: Update the LOB through the LOB buffers using the locator that has LOB buffering enabled. If this operation is required, buffers associated with this LOB should either be flushed as necessary or buffering should be disabled. Once this is done, reissue the command.
Cause: The operation attempted is not allowed when LOB buffering is enabled.
Action: If the operation is required, LOB buffering should not be used. In this case, flush buffers associated with the input LOB locator as necessary, disable buffering on the input LOB locator and reissue the command.
Cause: There are two causes:
Action: For Case 1: Flush the LOB(s) through the locator that is being used to update the LOB. The current LOB usage indicates the number of buffers being held for the LOB relevant to the current operation.
Cause: The input locator has buffering enabled and was used to update the LOB value through the LOB buffering subsystem. The modified buffer has not been flushed since the write that was performed by the input locator; thus the input locator is considered an updated locator. Updated locators cannot be the source of a copy operation. Only one locator per LOB can be used to modify the LOB value through the LOB buffering subsystem.
Action: Depending on whether the modifications made through the input locator to the LOB buffering subsystem should be written to the server, either flush the buffer to write the modifications, or, disable buffering on the locator to discard the modifications. Then, reissue the command.
Cause: The buffered write operation has an input offset value more than one byte or character past the end of the LOB.
Action: Specify an input offset value which is exactly one character or byte greater than the length of the LOB that you are attempting to update through a buffered write operation.
Cause: Attempted to access a directory that does not exist, or attempted to access a file in a directory that does not exist.
Action: Ensure that a system object corresponding to the specified directory exists in the database dictionary, or make sure the name is correct.
Cause: The user does not have the necessary access privileges on the directory alias and/or the file for the operation.
Action: Ask the database/system administrator to grant the required privileges on the directory alias and/or the file.
Cause: The directory alias used for the current operation is not valid if being accessed for the first time, or has been modified by the DBA since the last access.
Action: If you are accessing this directory for the first time, provide a valid directory name. If you have been already successful in opening a file under this directory before this error occurred, then close the file and retry the operation with a valid directory alias as modified by your DBA. Oracle recommends that directories should be modified only during quiescent periods.
Cause: The operation attempted on the file failed.
Action: Verify that the file exists and that the necessary privileges are set for the specified operation. If the error still persists, report the error to the DBA.
Cause: The file is not open for the required operation to be performed.
Action: Check that the current operation is preceded by a successful file open operation.
Cause: The number of open files has reached the maximum limit.
Action: Close some of the opened files and retry the operation.
Cause: An attempt was made to obtain information for a type that cannot be found.
Action: Make sure that the type has been committed successfully, and the schema information has been supplied correctly. Then retry the operation.
Cause: An attempt was made to use an invalid input name. The name does not exist in the type.
Action: Modify the program to have the caller of the routine pass a name that is valid for the function being called.
Cause: An attempt was made to create a schema name, type name pair that matches a schema name, type name pair that already exists.
Action: Modify the program to have the caller of the routine pass a schema name, type name pair that does not already exist.
Cause: An attempt was made to use an input type which is not a user-defined type. User-defined types can only be altered.
Action: Modify the program to have the caller of the routine pass a user-defined type as input.
Cause: An input name was used that is not a unique name in the type.
Action: Modify the program to have the caller of the routine pass a name that does not already exist in the type.
Cause: A type which does not exist was used for the attribute.
Action: No types were created/modified for this DDL transaction. Redo the DDL transaction and add the creation of the attribute's type in the DDL transaction.
Cause: The version of this type conflicts with the version of this type used by another library that was linked in with the application. An application may only use one version of a type.
Action: Check that the libraries being linked with this application use the same versions of the type.
Cause: The number of methods or the method signature does not match that of the original type declaration. This is not supported.
Action: Make sure the method signatures stay identical for the previously declared method. Do not drop existing methods.
Cause: The input type cannot be returned because it does not contain a map or order function.
Action: Add a map or order function to the type and retry the operation.
Cause: An attempt was made to obtain NPT-specific information on a non-named primitive type.
Action: Use a named primitive type for the function then retry the operation.
Cause: An attempt was made to use a number typecode that is not valid.
Action: Use only these number typecodes OROTCSML, OROTCINT, OROTCSHO,OROTCUSH, OROTCLON, OROTCULO, OROTCREA, OROTCDOU, OROTCFLO, OROTCNUM, or OROTCDEC.
Cause: An attempt was made to obtain the number of elements for a non-array type.
Action: Pass in only a named collection type which is an array.
Cause: The type attribute information that was entered does not match that of the original type declaration when altering type.
Action: You cannot alter any type information other than to add new methods when altering a type.
Cause: The ortgrbp() function was called on a method that does not return any results.
Action: Check that you are passing in the correct method descriptor, or that your method creation was done correctly.
Cause: Production Oracle8 (8.0.3 and beyond) encountered some VARRAY data which was created and stored by Oracle8 8.0.2 (Beta 2). Production Oracle8 cannot understand or process such VARRAY data.
Action: Delete the VARRAY data from the table by dropping the table, deleting the rows, or nulling out the VARRAY columns, and then re-insert the VARRAY data. There is no provided script or tool to help automate this conversion.
Cause: An attempt was made to use an incomplete type as a constructor.
Action: Complete the type definition before using it in a query.
Cause: The specified object row variable is not available in the scope of name resolution.
Action: Verify the specified row object variable is correct, or use a valid row object variable visible in scope.
Cause: An attempt was made to create or specify a column or constructor of an object type that has no attributes. Only object types that have at least one attribute are allowed in this context.
Action: Specify a valid object type and retry the operation.
Cause: An attempt was made to perform queries or DML operations on remote object tables or on remote table columns whose type is one of object, REF, nested table or VARRAY.
Action: Remove the reference to remote tables in the statement.
Cause: An attempt was made to insert a NULL object into an object table or a Nested Table.
Action: Ensure that a non-NULL object is inserted into the table or insert an object with attributes whose values are NULL.
Cause: An attempt was made to extract an attribute from an item that is neither an object nor a REF.
Action: Use an object type or REF type item and retry the operation.
Cause: Invalid use of a non-scalar (for example, object type) item.
Action: Change the item's data type and retry the operation.
Cause: An attempt was made to access a type's attributes by dereferencing a REF item.
Action: Make the item an object type instead of a REF to an object type.
Cause: An attempt was made to access a non-existent attribute of an object type.
Action: Check the attribute reference to see if it is valid. Then retry the operation.
Cause: An attempt was made to modify attributes of an object by dereferencing a REF column in an UPDATE statement.
Action: Update the table containing the object that the REF points to, or change the REF column to an object type column.
Cause: An attempt to access the nested table column's storage table is not allowed in the given context.
Action: Issue the statement against the parent table containing the NESTED TABLE column.
Cause: Object or Collection value was too large. The size of the value might have exceeded 30k in a SORT context, or the size may be too big for available memory.
Action: Choose another value and retry the operation.
Cause: Value provided for the object type attribute or collection element exceeded the size specified in the type declaration.
Action: Choose another value and retry the operation.
Cause: RETURNING clause is currently not supported for object type columns, LONG columns, remote tables and INSERT with subquery.
Action: Use separate SELECT statement to get the values.
Cause: A LOB store option (CHUNK, PCTVERSION, CACHE, NOCACHE, TABLESPACE, STORAGE, INDEX) was specified more than once.
Action: Specify all LOB store options only once.
Cause: The specified CHUNK LOB storage option value must be an integer.
Action: Choose an appropriate integer value and retry the operation.
Cause: The specified PCTVERSION LOB store option value must be an integer.
Action: Choose an appropriate integer value and retry the operation.
Cause: A LOB storage option was not specified.
Action: Specify one of (CHUNK, PCTVERSION, CACHE, NOCACHE, TABLESPACE, STORAGE, INDEX) as part of the LOB storage clause.
Cause: A valid LOB store index option was not specified.
Action: Specify one of (INITTRANS, MAXTRANS, TABLESPACE, STORAGE) as part of the LOB storage index.
Cause: The optional name for LOB storage segment was specified with multiple columns in the column list.
Action: Specify each column LOB storage only with optional name(s).
Cause: An attempt was made to add columns to an object table. Object tables cannot be altered to add columns since its definition is based on an object type.
Action: Create a new type with additional attributes, and use the new type to create a object table. The new object table will have the desired columns.
Cause: An attempt was made to alter the object table by modifying existing columns. An object table cannot be altered to modify existing columns since it is based on an object type. The table definition must be in sync with the corresponding type.
Action: Create a new type with additional attributes, and use the new type to create an object table. The new object table will have the desired columns.
Cause: An attempt was made to modify the column type to object, REF, nested table, VARRAY or LOB type.
Action: Create a new column of the desired type and copy the current column data to the new type using the appropriate type constructor.
Cause: An attempt was made to modify an object, REF, VARRAY, nested table, or LOB column type.
Action: Create a new column of the desired type and copy the current column data to the new type using the appropriate type constructor.
Cause: An attempt was made to create an object table using a non-object type, or to create a column that is a REF to a non-object type.
Action: Use a valid object type in the table or column definition.
Cause: An attempt was made to create a column or object table of a non-existent type
Action: Specify a valid type in table or column definition.
Cause: An attempt was made to specify an object identifier for the type that does not match the existing identifier of the incomplete type of the same name.
Action: Specify the correct object identifier or leave it out of the statement.
Cause: An attempt was made to use a synonym specification for a datatype.
Action: Do not use the synonym specification for the data type.
Cause: An attempt was made to ALTER or DROP a LOB index.
Action: Do not operate directly on the system-defined lob index. Perform operations on the corresponding LOB column.
Cause: An attempt was made to specify multiple columns where only one is allowed.
Action: Specify a single column and retry the operation.
Cause: A character LOB was defined but the default character set is not fixed width.
Action: Ensure that the character set is of fixed width before defining character LOBs.
Cause: An attempt was made to drop a tablespace which contains the segment(s) for the LOB columns of a table but does not contain the table segment.
Action: Find table(s) with LOB columns which have non-table segments in this tablespace. Drop these tables and reissue drop tablespace.
Cause: The type dependency hierarchy was structured to have depth greater than 1024.
Action: Re-structure the type dependency hierarchy to a shorter depth.
Cause: An attempt was made to perform ALTER TYPE with REPLACE option a non-object type.
Action: First drop the non-object type, then re-create it as an object type.
Cause: An invalid REF was accessed.
Action: Modify the REF and retry the operation.
Cause: The object corresponding to the REF that was accessed does not exist.
Action: Ensure that the REF value is pointing to an existing object.
Cause: The object cannot be inserted in the database.
Action: Check to see if the object table exists and that the object size is not too big. Then retry the operation.
Cause: The object could not be deleted from the database.
Action: Check to see if the table exists. Then retry the operation.
Cause: The object could not be modified in the database.
Action: Check to see if the object table exists and the object size is not too big. Then retry the operation.
Cause: An attempt was made to get a REF for something other than an object in an object table. REFs can only be taken for objects in object tables.
Action: Rewrite the query to obtain REF values from object tables.
Cause: The scoped table specified for a REF column is not an object table.
Action: Ensure that the scope table is an object table. Then retry the operation.
Cause: The type specified for the REF column and the type specified for the scoped table are different.
Action: Ensure that the types of a REF column and its scoped table are the same.
Cause: Multiple SCOPE clauses were specified for a single REF column.
Action: Remove the duplicate scope clauses and retry the operation.
Cause: An attempt was made to insert a REF value that does not point to the scoped table.
Action: Ensure that the REF values point to the scoped table.
Cause: An attempt was made to specify a constraint name for a constraint on a REF column.
Action: Remove the constraint name and retry the operation.
Cause: An attempt was made to specify multiple columns in a single REF constraint.
Action: Specify separate constraints for each column and retry the operation.
Cause: The scope table specified for a REF column does not exist.
Action: Ensure that the scope table exists and retry the operation.
Cause: The constraint specified does not apply to non-REF columns.
Action: Remove the constraint.
Cause: An attempt was made to add a constraint to existing REF columns of a table which contains one or more rows.
Action: Remove the constraint specification or add the constraint after emptying the table.
Cause: The subquery within THE operator must select a collection item.
Action: Change the subquery to select a collection item, then retry the operation.
Cause: An attempt was made to compare nested table, VARRAY, or LOB attributes of an object type in the absence of a MAP or ORDER method.
Action: Define a MAP or ORDER method for the type of the object type then retry the operation.
Cause: CURSOR on a subquery is allowed only in the top-level SELECT list of a query.
Action: Remove the CURSOR expression and retry the operation.
Cause: An attempt was made to use the MULTISET expression outside of a CAST to a nested table or VARRAY type.
Action: Put the MULTISET(subquery) expression inside a CAST to a nested table or VARRAY type.
Cause: An invalid reference was made to a nested table column.
Action: Remove invalid reference to the nested table column and retry the operation.
Cause: An attempt was made to access rows of an item whose type is not known at parse time or that is not of a nested table type.
Action: Use the CAST operator to cast the item to a nested table type.
Cause: An attempt was made to perform a DML on a nested table view column where a nested table column of a base table is expected.
Action: Remove the DML statements on nested table view columns and retry the operation.
Cause: The CAST to a type was performed on something other than a nested table or VARRAY type.
Action: CAST only to a nested table or VARRAY type then retry the operation.
Cause: The evaluation of the THE subquery resulted in a NULL value implying a NULL table instance. The THE subquery must result in a single non-NULL table instance.
Action: Ensure that the evaluation of the THE subquery results in a single non-null table instance. If the error occurs in the context of an insert statement where the THE subquery was the target of an insert, then ensure that an empty nested table instance is created by updating the nested table column of the parent table's row specifying an empty nested table constructor.
Cause: The total number of elements used in VARRAY construction exceeds the specified VARRAY limit.
Action: Don't use the more than the specified limit of elements for VARRAY construction.
Cause: Table name was qualified with schema name in the nested table storage clause.
Action: Respecify the nested table storage clause without the schema name qualification. By default, the store table for the nested table is created in the same schema as the containing table.
Cause: The storage clause is specified more than once for the nested table column.
Action: Remove the duplicate storage specification.
Cause: The storage clause is specified for a column or attribute that is not a nested table column or attribute.
Action: Specify a valid nested table column or attribute.
Cause: The storage clause is not specified for a column or attribute that is a nested table column or attribute.
Action: Specify a table name using the Nested Table storage clause.
Cause: Attempt was made to DROP a nested table.
Action: Nested tables cannot be explicitly dropped. Nested tables can only be dropped by dropping their containing parent table.
Cause: Attempt was made to ADD or MODIFY columns of a nested table.
Action: Columns cannot be added or modified for a nested table. You must ALTER the parent table's nested table column to cause any such change.
Cause: Exact FETCH on a query is not allowed if the query returns any cursors.
Action: Do not use an exact FETCH.
Cause: The row containing the LOB was not locked before the lob was updated.
Action: Lock the row containing the LOB before updating the LOB data.
Cause: The buffer length was not big enough to hold the amount of data requested.
Action: Verify that the number of bytes/characters specified in the input amount parameter is not bigger than the number of bytes specified in the input buffer length parameter. Allocate more space for the input buffer if necessary.
Cause: The lob associated with the input locator does not exist. The information in the locator does not refer to an existing LOB.
Action: Repopulate the locator by issuing a SELECT statement and retry the operation.
Cause: An attempt was made to write LOB data by the streaming mechanism (that is, unlimited write) but the input amount of data to stream was specified as 0. This means that an attempt is being made to write 0 bytes to the LOB data.
Action: Write more than 0 bytes to the LOB data.
Cause: The version of the LOB data needed for the consistent read was already overwritten by another writer.
Action: Use a larger version pool then retry the operation.
Cause: An attempt was made to write too much data to the LOB. LOB size is limited to 4 gigabytes.
Action: Either start writing at a smaller LOB offset or write less data to the LOB.
Cause: The input trim length to which the LOB data will be trimmed was specified to be greater than the current length of the LOB data.
Action: Might not need to trim the LOB data because it is already smaller than the trim length specified. Or, if trimming the LOB data really is required, use a smaller trim length.
Cause: An invalid input LOB locator was used; it was never initialized.
Action: Initialize the input LOB locator and pass the initialized LOB locator to the function.
Cause: An attempt was made to grant or revoke an invalid privilege on a directory.
Action: Only CREATE, DELETE, READ and WRITE privileges can be granted or revoked on directories. Do not grant or revoke other privileges.
Cause: The required directory name is invalid or missing.
Cause: Attempt to access a directory that does not exist.
Action: Make sure the name is correct.
Cause: Object types must have map or order methods defined for all comparisons other than equality and inequality comparisons.
Action: Define a map or order method for the object type.
Cause: Order method used to compare two object values returned NULL.
Action: Redefine the order method to not return a NULL.
Cause: Either the expression that was entered is not a view name or the name specified does not correspond to an object view.
Action: Replace the expression with the name of an object view and retry the operation.
Cause: When creating a typed view, the datatype of an expression in the WITH OID clause was not allowed for primary key-based OID.
Action: Replace the expression with one of appropriate scalar datatype and retry the operation.
Cause: A value constituting the primary key-based OID evaluated to NULL.
Action: Ensure the expressions in MAKE_REF system function or WITH OID clause of CREATE VIEW do not evaluate to NULL.
Cause: The size of the primary key-based OID of a typed view was too large.
Action: Specify fewer or smaller primary key columns in the WITH OID clause when creating the typed view.
Cause: WITH OID clause was not specified when creating a typed view.
Action: Specify the WITH OID clause, or create an untyped view instead, or create a typed view on a single typed table or view.
Cause: The object view specified in the MAKE_REF function did not have a primary key-based OID. A primary key-based REF cannot be created for such a view.
Action: Specify an object view that has a primary key-based OID in the MAKE_REF function.
Cause: Number of arguments for MAKE_REF was different from the number of primary key attributes of the object view.
Action: Specify all the necessary arguments for MAKE_REF.
Cause: Either the attribute name is missing in the WITH OBJECT OID clause or it is invalid.
Action: Specify a valid attribute of the object type of the object view.
Cause: Attempted to specify a Nested attribute in the WITH OBJECT OID clause.
Action: Specify a top-level attribute of the object type of the object view.
Cause: Attempt to insert a REF selected from an object view into the REF column of a table. Currently, such a REF cannot be stored in the database.
Action: Make sure the REF to be inserted into a REF column is selected from a table.
Cause: A LOB locator selected in one transaction cannot be used in a different transaction.
Action: Re-select the LOB locator and retry the operation.
Cause: The data to be returned in the argument is greater than the amount of space allocated for the argument.
Action: Allocate more space for the argument.
Cause: A remote LOB column cannot be referenced.
Action: Remove references to LOBs in remote tables.
Cause: Case 1: For LOB write, the amount of data received is different from the amount that was indicated would be sent.
Action: For Case 1: This will happen when using OCI's piecewise mechanism with polling or with a callback function. Modify the code either to send the amount specified or to pass 0 as the input amount so that any amount of data can be sent.
This section lists messages generated by the DBMS_SYS_ERROR package.
Cause: The stored procedure RAISE_SYSTEM_ERROR was called to generate this message.
Action: Correct the problem described in the message or contact the application programmer or database administrator for more information.
Cause: Replication catalog determined deferred remote procedure call destinations were mixed with destination determined by other mechanisms in the same transaction.
Action: Do not mix destination types in the same transaction.
Cause: An application declared a communication failure during a deferred remote procedure call.
Action: Retry the application when communication is restored.
Cause: An application declared a generic failure during a deferred remote procedure call.
Action: Dependent on application.
Cause: A deferred remote procedure call was issued without the correct number of arguments as determined by the count parameter DBMS_DEFER.CALL.
Action: Ensure the number of arguments matches the count.
Cause: An internal error occurred in the deferred remote procedure call.
Action: Contact customer support.
Cause: The schema name was null or misspelled, or the schema does not exist locally.
Action: Specify the schema correctly, or create it with CREATE USER.
|
 Copyright © 1997 Oracle Corporation. All Rights Reserved. |
|
