67 OCI-00601 to OCI-64495
- OCI-00601: cleanup lock conflict
-
Cause: PMON process runs into lock conflict trying to recover processes.
- OCI-00602: internal programming exception
-
Cause: Internal programming exception.
- OCI-00972: identifier is too long
-
Cause: An identifier with more than 30 characters was specified.
- OCI-01841: (full) year must be between -4713 and +9999, and not be 0
-
Cause: Illegal year entered
- OCI-01854: julian date must be between 1 and 5373484
-
Cause: An invalid Julian date was entered.
- OCI-01858: a non-numeric character was found where a numeric was expected
-
Cause: The input data to be converted using a date format model was incorrect. The input data did not contain a number where a number was required by the format model.
- OCI-01859: a non-alphabetic character was found where an alphabetic was expected
-
Cause: The input data to be converted using a date format model was incorrect. The input data did not contain a letter where a letter was required by the format model.
- OCI-01861: literal does not match format string
-
Cause: Literals in the input must be the same length as literals in the format string (with the exception of leading whitespace). If the "FX" modifier has been toggled on, the literal must match exactly, with no extra whitespace.
- OCI-01862: wrong number of digits for this format item
-
Cause: The number of digits used for this format item is not equal to the number necessary for this format when specifying Format eXact ("FX") for this item.
- OCI-01864: the date is out of range for the current calendar
-
Cause: Your calendar doesn't extend to the specified date.
- OCI-01865: not a valid era
-
Cause: Era input does not match a known era.
- OCI-01867: the interval was invalid
-
Cause: The character string you specified is not a valid interval.
- OCI-01868: the leading precision of the interval was too small
-
Cause: The leading precision of the interval is too small to store the specified interval.
- OCI-01870: the intervals or datetimes were not mutually comparable
-
Cause: The intervals or datetimes are not mutually comparable.
- OCI-01871: the number of seconds must be less than 60
-
Cause: The number of seconds specified was greater than 59.
- OCI-01873: the leading precision of the interval was too small
-
Cause: The leading precision of the interval is too small to store the specified interval.
- OCI-01874: time zone hour must be between -12 and 14
-
Cause: The time zone hour specified was not in the valid range.
- OCI-01875: time zone minute must be between -59 and 59
-
Cause: The time zone minute specified was not in the valid range.
- OCI-01876: year must be at least -4713
-
Cause: The specified year was not in range.
- OCI-01878: specified field not found in datetime or interval
-
Cause: The specified field was not found in the datetime or interval.
- OCI-01879: the hh25 field must be between 0 and 24
-
Cause: The specified hh25 field was not in the valid range.
- OCI-01880: the fractional seconds must be between 0 and 999999999
-
Cause: The specified fractional seconds were not in the valid range.
- OCI-01881: time zone region ID is invalid
-
Cause: The region ID referenced an invalid region.
- OCI-01882: time zone region not found
-
Cause: The specified region name was not found.
- OCI-01883: overlap was disabled during a region transition
-
Cause: The region was changing state and the overlap flag was disabled.
- OCI-01884: divisor is equal to zero
-
Cause: An attempt was made to divide by zero.
- OCI-01890: NLS error detected
-
Cause: An NLS error was detected.
- OCI-01898: too many precision specifiers
-
Cause: While trying to truncate or round dates, extra data was found in the date format picture
- OCI-02083: database name has illegal character 'string'
-
Cause: Supplied database name can contain only A-Z, 0-9, '_', '#', '$' '.' and '@' characters.
- OCI-02084: database name is missing a component
-
Cause: Supplied database name cannot contain a leading '.', trailing '.' or '@', or two '.' or '@' in a row.
- OCI-04020: deadlock detected while trying to lock object stringstringstringstringstring
-
Cause: While trying to lock a library object, a deadlock is detected.
- OCI-04021: timeout occurred while waiting to lock object stringstringstringstringstring
-
Cause: While waiting to lock a library object, a timeout is occurred.
- OCI-04022: nowait requested, but had to wait to lock dictionary object
-
Cause: Had to wait to lock a library object during a nowait request.
- OCI-04028: cannot generate diana for object stringstringstringstringstring
-
Cause: Cannot generate diana for an object because of lock conflict.
- OCI-04029: error ORA-string occurred when querying stringstringstring
-
Cause: The table or view being queried might be missing. The error number indicates the error.
- OCI-04030: out of process memory when trying to allocate string bytes (string,string)
-
Cause: Operating system process private memory has been exhausted
- OCI-04031: unable to allocate string bytes of shared memory ("string","string","string")
-
Cause: More shared memory is needed than was allocated in the shared pool.
- OCI-04054: database link string does not exist
-
Cause: During compilation of a PL/SQL block, an attempt was made to use a non-existent database link.
- OCI-04060: insufficient privileges to execute string
-
Cause: Attempt to execute a stored procedure without sufficient privileges.
- OCI-04061: existing state of string has been invalidated
-
Cause: Attempt to resume the execution of a stored procedure using the existing state which has become invalid or inconsistent with the stored procedure because the procedure has been altered or dropped.
- OCI-04062: timestamp of string has been changed
-
Cause: Attempt to execute a stored procedure to serve an RPC stub which specifies a timestamp that is different from the current timestamp of the procedure.
- OCI-04063: string has errors
-
Cause: Attempt to execute a stored procedure or use a view that has errors. For stored procedures, the problem could be syntax errors or references to other, non-existent procedures. For views, the problem could be a reference in the view's defining query to a non-existent table.
- OCI-04064: not executed, invalidated string
-
Cause: Attempt to execute a stored procedure that has been invalidated.
- OCI-04065: not executed, altered or dropped string
-
Cause: Attempt to execute a stored procedure that has been altered or dropped thus making it not callable from the calling procedure.
- OCI-04066: non-executable object, string
-
Cause: Attempt to execute a non-procedure.
- OCI-04067: not executed, string does not exist
-
Cause: Attempt to execute a non-existent stored procedure.
- OCI-04068: existing state of packagesstringstringstring has been discarded
-
Cause: One of errors 4060 - 4067 when attempt to execute a stored procedure.
- OCI-19200: Invalid column specification
-
Cause: All input arguments must be valid columns
- OCI-19201: Datatype not supported
-
Cause: The particular datatype is not supported in the XMLGEN operator
- OCI-19202: Error occurred in XML processingstring
-
Cause: An error occurred when processing the XML function
- OCI-19203: Error occurred in DBMS_XMLGEN processingstring
-
Cause: An error occurred when processing the DBMS_XMLGEN functions
- OCI-19204: Non-scalar value 'string' is marked as XML attribute
-
Cause: Only scalar values (i.e. values which are not of object or collection type) can be marked as XML attribute,i.e. is prefixed by '@'. In this case, a non-scalar value was prefixed with '@'
- OCI-19205: Attribute 'string' qualifies a non-scalar value in the select list
-
Cause: The attribute immediately follows a value of object or collection type in the select list or type definition.
- OCI-19206: Invalid value for query or REF CURSOR parameter
-
Cause: The queryString argument passed to DBMS_XMLGEN.newContext was not a valid query, or REF CURSOR.
- OCI-19207: scalar parameter string of XMLELEMENT cannot have an alias.
-
Cause: The scalar parameter to XMLELEMENT has been qualified with an alias.
- OCI-19208: parameter string of function string must be aliased
-
Cause: The indicated parameter of the XML generation function has not been aliased, although it is an expression.
- OCI-19209: invalid or unsupported formatting argument
-
Cause: An invalid or unsupported formatting argument was supplied
- OCI-19210: column 'string', specified to be a key or update column for DBMS_XMLSTORE, does not not exist in table 'string'
-
Cause: The column specified using setKeyColumn()/setUpdateColumn() did not exist in the table.
- OCI-19211: column 'string', specified as key using DBMS_XMLSTORE.setKeyColumn() , must be of scalar type
-
Cause: The column specified using setKeyColumn() was a non-scalar type column.
- OCI-19212: no key columns specified before call to DBMS_XMLSTORE.updateXML()
-
Cause: No columns were specified as key columns before the call to DBMS_XMLSTORE.updateXML.
- OCI-21300: objects option not installed
-
Cause: The objects option is not installed at this site. Object types and other object features are, therefore, unavailable.
- OCI-21301: not initialized in object mode
-
Cause: This function requires the oci process to be initialized in object mode.
- OCI-21500: internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
-
Cause: This is the generic error number for the OCI environment (client-side) internal errors. This indicates that the OCI environment has encountered an exceptional condition.
- OCI-21501: program could not allocate memory
-
Cause: The operating system has run out of memory.
- OCI-21503: program terminated by fatal error
-
Cause: A program is in an unrecoverable error state.
- OCI-21520: database server driver not installed
-
Cause: User attempted to access a database server through an object-mode OCI environment but the necessary driver for supporting such access to the database server is not installed or linked in.
- OCI-21521: exceeded maximum number of connections in OCI (object mode only)
-
Cause: User exceeded the maximum number of connections (255) that can be supported by an OCI environment in object mode.
- OCI-21522: attempted to use an invalid connection in OCI (object mode only)
-
Cause: User attempted to use an invalid connection or a connection that has been terminated in an OCI environment (object mode), or user attempted to dereference a REF obtained from a connection which has been terminated.
- OCI-21523: functionality not supported by the server (object mode only)
-
Cause: User attempted to use a functionality that the server does not support.
- OCI-21524: object type mismatch
-
Cause: The object type of the object is different from what is specified.
- OCI-21525: attribute number (or collection element at index) string violated its constraints
-
Cause: Attribute value or collection element value violated its constraint.
- OCI-21526: initialization failed
-
Cause: The initialization sequence failed. This can happen, for example, if an environment variable such as NLS_DATE_FORMAT is set to an invalid value.
- OCI-21527: internal OMS driver error
-
Cause: A process has encountered an exceptional condition. This is the generic internal error number for Oracle object management services exceptions.
- OCI-21560: argument string is null, invalid, or out of range
-
Cause: The argument is expecting a non-null, valid value but the argument value passed in is null, invalid, or out of range. Examples include when the LOB/FILE positional or size argument has a value outside the range 1 through (4GB - 1), or when an invalid open mode is used to open a file, etc.
- OCI-21562: column string has unsupported data type string
-
Cause: A data type was specified which is currently unsupported.
- OCI-21563: Error string while calling string for column string with datatype string
-
Cause: OCI Error encountered while performing data type conversion.
- OCI-21570: current string LCR has unreceived chunk data
-
Cause: The client did not receive all the chunk data for the current LCR.
- OCI-21571: must provide a LOB WRITE, LOB TRIM or LOB ERASE LCR in string call (input LCR=string)
-
Cause: An attempt was made to invoke the specified function without providing a piece-wise LOB LCR (for example, LOB WRITE, LOB TRIM or LOB ERASE LCR).
- OCI-21572: Invalid LCR type (string) in string call
-
Cause: An attempt was made to invoke the specified function with an incorrect logical change record (LCR) type.
- OCI-21573: Invalid command type (string) when sending a chunk.
-
Cause: An attempt was made to send a chunk when the command type for the current LCR was not INSERT, UPDATE, or LOB WRITE.
- OCI-21574: Invalid data type (string) specified for LOB chunk.
-
Cause: Invalid data type specified for LOB chunk in OCIXStreamInChunkSend call.
- OCI-21577: Input string LCR has no LOB column.
-
Cause: An attempt was made to invoke OCILCRLobInfoGet call with an LCR that had no LOB column.
- OCI-21578: Only one LOB column allowed per string LCR.
-
Cause: An attempt was made to set multiple LOB columns on a piece-wise LOB LCR.
- OCI-21579: Input LCR must have at least one old or new column.
-
Cause: An attempt was made to call OCIXStreamInChunkSend with an LCR that had empty column lists.
- OCI-21580: The LOB operation length (value=string) for column (string) must be an even number of bytes.
-
Cause: An attempt was made to call OCIXStreamInChunkSend with an odd number of bytes for a column flagged as AL16UTF16 or NCLOB.
- OCI-21583: invalid XStream server name 'string'
-
Cause: An attempt was made to attach to an XStream server with a nonexistent server name.
- OCI-21600: path expression too long
-
Cause: The path expression that is supplied by the user is too long. The path expression is used to specify the position of an attribute in an object. This error occurs when one of the intermediate elements in the path expression refers to an attribute of a built-in type. Thus, the OCI function cannot proceed on to process the rest of the elements in the path expression.
- OCI-21601: attribute is not an object
-
Cause: The user attempts to perform an operation (that is valid only for an object) to an attribute of a built-in type. An example of such an illegal operation is to dynamically set a null structure to an attribute of a built-in type.
- OCI-21602: operation does not support the specified typecode
-
Cause: The user attempts to perform an operation that does not support the specified typecode.
- OCI-21603: property id [string] is invalid
-
Cause: The specified property id is invalid.
- OCI-21604: property [string] is not a property of transient or value instances
-
Cause: Trying to get a property which applies only to persistent objects.
- OCI-21605: property [string] is not a property of value instances
-
Cause: Trying to get a property which applies only to persistent and transient objects.
- OCI-21606: can not free this object
-
Cause: Trying to free an object that is persistent and dirty and the OCI_OBJECTFREE_FORCE flag is not specified.
- OCI-21607: memory cartridge service handle not initialized
-
Cause: Attempt to use the handle without initializing it.
- OCI-21608: duration is invalid for this function
-
Cause: Attempt to use a duration not valid for this function.
- OCI-21609: memory being resized without being allocated first
-
Cause: Attempt to resize memory without allocating it first.
- OCI-21610: size [string] is invalid
-
Cause: Attempt to resize memory with invalid size.
- OCI-21611: key length [string] is invalid
-
Cause: Attempt to use an invalid key length.
- OCI-21612: key is already being used
-
Cause: Attempt to use a key that is already used.
- OCI-21613: key does not exist
-
Cause: Attempt to use a non-existent key
- OCI-21700: object does not exist or is marked for delete
-
Cause: User attempted to perform an inappropriate operation to an object that is non-existent or marked for delete. Operations such as pinning, deleting and updating cannot be applied to an object that is non-existent or marked for delete.
- OCI-21701: attempt to flush objects to different servers
-
Cause: User attempted to flush objects to different servers in one function call. These objects are obtained by calling a callback functions provided by the program.
- OCI-21702: object is not instantiated or has been de-instantiated in cache
-
Cause: User attempted to perform an inappropriate operation to a transient object that is not instantiated in the object cache. Operations that cannot be applied to a not-instantiated transient object include deleting or pinning such an object.
- OCI-21703: cannot flush an object that is not modified
-
Cause: See the error message.
- OCI-21704: cannot terminate cache or connection without flushing first
-
Cause: See the error message.
- OCI-21705: service context is invalid
-
Cause: The service context that is supplied by the user is not valid.
- OCI-21706: duration does not exist or is invalid
-
Cause: The duration number that is supplied by the user is not valid.
- OCI-21707: pin duration is longer than allocation duration
-
Cause: The pin duration supplied by the user is longer than the allocation duration. This affects operations such as pinning and setting default parameters.
- OCI-21708: inappropriate operation on a transient object
-
Cause: User attempted to perform an inappropriate operation on a transient object. Operations that cannot be applied to a transient object include flushing and locking.
- OCI-21709: cannot refresh an object that has been modified
-
Cause: User attempted to refresh an object that has been marked for delete, update or insert (new).
- OCI-21710: argument is expecting a valid memory address of an object
-
Cause: The object memory address that is supplied by the user is invalid. The user may have passed in a bad memory address to a function that is expecting a valid memory address of an object.
- OCI-21779: duration not active
-
Cause: User is trying to use a duration that has been terminated.
- OCI-22053: overflow error
-
Cause: This operation's result is above the range of Oracle number.
- OCI-22054: underflow error
-
Cause: This operation's result is below the range of Oracle number.
- OCI-22055: unknown sign flag value [string]
-
Cause: Signed flag used is not OCI_NUMBER_SIGNED or OCI_NUMBER_UNSIGNED.
- OCI-22056: value [string] is divided by zero
-
Cause: Given value is divied by zero.
- OCI-22057: bad integer length [string]
-
Cause: The length of the integer (ie number of bytes) to be converted to or from an Oracle number is invalid.
- OCI-22059: buffer size [string] is too small - [string] is needed
-
Cause: The buffer to hold the resulting text string is too small.
- OCI-22060: argument [string] is an invalid or uninitialized number
-
Cause: An invalid or uninitialized number is passed in.
- OCI-22061: invalid format text [string]
-
Cause: The numeric format string for converting characters to or from an Oracle number is invalid.
- OCI-22062: invalid input string [string]
-
Cause: The text string for converting to numbers is invalid.
- OCI-22063: reading negative value [string] as unsigned
-
Cause: Attempt to convert a negative number to an unsigned integer.
- OCI-22064: invalid NLS parameter string [string]
-
Cause: The NLS parameter string for converting characters to or from an Oracle number is invalid.
- OCI-22065: number to text translation for the given format causes overflow
-
Cause: Rounding done due to the given string format causes overflow.
- OCI-22130: buffer size [string] is less than the required size [string]
-
Cause: The size of the buffer into which the hexadecimal REF string is to be written is too small.
- OCI-22131: hexadecimal string length is zero
-
Cause: The given hexadecimal string length must be greater than zero.
- OCI-22132: hexadecimal string does not correspond to a valid REF
-
Cause: The given hexadecimal string is invalid.
- OCI-22140: given size [string] must be in the range of 0 to [string]
-
Cause: The given resize size is invalid.
- OCI-22141: given size [string] must be even in UTF-16 environment
-
Cause: The given resize size is odd. In a UTF-16 environment, all characters are 2 bytes in length.
- OCI-22150: variable-length array has not been initialized
-
Cause: An un-initialized variable-length array is being operated upon.
- OCI-22151: cannot resize non-zero variable-length array to zero elements
-
Cause: Trying to resize a non-zero variable-length array to 0 elements.
- OCI-22152: destination variable-length array is not initialized
-
Cause: The variable-length array on the right-hand-side of an assignment or the destination array of an append is not initialized.
- OCI-22153: source variable-length array is not initialized
-
Cause: The variable-length array on the left-hand-side of an assignment or the source array of an append is not initialized.
- OCI-22160: element at index [string] does not exist
-
Cause: Collection element at the given index does not exist.
- OCI-22161: type code [string] is not valid
-
Cause: Given type code is not valid.
- OCI-22162: element at index [string] has been previously deleted
-
Cause: Trying to delete a non-existent collection element.
- OCI-22163: left hand and right hand side collections are not of same type
-
Cause: Left hand and right side collections are not of same type.
- OCI-22164: delete element operation is not allowed for variable-length array
-
Cause: Trying to delete an element of a variable-length array.
- OCI-22165: given index [string] must be in the range of [string] to [string]
-
Cause: Given index is not in the required range.
- OCI-22166: collection is empty
-
Cause: Given collection is empty.
- OCI-22167: given trim size [string] must be less than or equal to [string]
-
Cause: Given trim size is greater than the current collection size.
- OCI-22275: invalid LOB locator specified
-
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.
- OCI-22276: invalid locator for LOB buffering
-
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
- OCI-22277: cannot use two different locators to modify the same LOB
-
Cause: LOB buffering is enabled and an attempt was made to modify the LOB using two different LOB locators.
- OCI-22278: must update the LOB only through the LOB buffers
-
Cause: LOB buffering is enabled for this LOB and there are buffers for this LOB in the buffer pool. Thus, updating the LOB through means other than the LOB buffers is not allowed.
- OCI-22279: cannot perform operation with LOB buffering enabled
-
Cause: The operation attempted is not allowed when LOB buffering is enabled.
- OCI-22280: no more buffers available for operation
-
Cause: There are two causes: (1) All buffers in the buffer pool have been used up by previous operations (2) Attempt to flush a LOB without any previous buffered update operations.
- OCI-22281: cannot perform operation with an updated locator
-
Cause: The input locator has buffering enabled and was used to update the LOB value through the LOB buffering subsystem. The modified buffer has not been flushed since the write that was performed by the the input locator; thus, the input locator is considered an updated locator. Updated locators cannot be the source of a copy operation. Only one locator per LOB may be used to modify the LOB value through the LOB buffering subsystem.
- OCI-22282: non-contiguous append to a buffering enabled LOB not allowed
-
Cause: The buffered write operation has an input offset value more than one byte or character past the end of the LOB.
- OCI-22285: non-existent directory or file for string operation
-
Cause: Attempted to access a directory that does not exist, or attempted to access a file in a directory that does not exist.
- OCI-22286: insufficient privileges on directory or file to perform string operation
-
Cause: The user does not have the necessary access privileges on the directory alias and/or the file for the operation.
- OCI-22287: invalid or modified directory occurred during string operation
-
Cause: The directory alias used for the current operation is not valid if being accessed for the first time, or has been modified by the DBA since the last access.
- OCI-22288: file operation string failed\nstring
-
Cause: The operation attempted on the file failed.
- OCI-22289: cannot perform string operation on an unopened file
-
Cause: The file is not open for the required operation to be performed.
- OCI-22290: operation would exceed the maximum number of opened files
-
Cause: The number of open files has reached the maximum limit.
- OCI-22303: type "string"."string" not found
-
Cause: The user is trying to obtain information for a type that cannot be found.
- OCI-22305: attribute/method/parameter "string" not found
-
Cause: Type element with the given name is not found in the type.
- OCI-22306: type "string"."string" already exists
-
Cause: The user is trying to create a type that already exists.
- OCI-22307: type to alter is not a user-defined type
-
Cause: The user is trying to alter a built-in type.
- OCI-22309: attribute with name "string" already exists
-
Cause: The user is attempting to create an object type where more than one attributes have the same name.
- OCI-22311: type for attribute "string" does not exist
-
Cause: The type of the attribute does not exist.
- OCI-22313: cannot use two versions of the same type "string"
-
Cause: The version of this type conflicts with the version of this type used by another library that was linked in with the application. An application may only use one version of a type.
- OCI-22314: method information mismatch in ALTER TYPE
-
Cause: The number of methods or the method signature do not match that of the original type declaration. This is not supported.
- OCI-22315: type "string" does not contain a map or order function
-
Cause: The input type does not contain a map or order function so one cannot be returned.
- OCI-22316: input type is not a collection type
-
Cause: The user is trying to obtain information for collection types on a non-named collection type.
- OCI-22317: typecode number is not legal as a number type
-
Cause: The user is trying to use a number typecode that is not valid.
- OCI-22318: input type is not an array type
-
Cause: The user is trying to obtain the number of elements for a non-array type.
- OCI-22319: type attribute information altered in ALTER TYPE
-
Cause: The type attribute information does not match that of the original type declaration when altering type. Attributes cannot be altered during ALTER TYPE. Only new methods can be added.
- OCI-22321: method does not return any result
-
Cause: OCITypeResult() was called on a method that does not return any results.
- OCI-22337: the type of accessed object has been evolved
-
Cause: The type of the accessed object has been altered and the client's object is based on an earlier type definition.
- OCI-22351: This API is not supported by the ORACLE server.
-
Cause: An attempt was made to call an API which is not supported by the Oracle server.
- OCI-22352: Type is unsupported or contains an unsupported attribute or element.
-
Cause: A PL/SQL package type was not supported on the client or contained an attribute or element that was not supported on the client. Unsupported types include index by VARCHAR2 collections, remote types and MLSLABELs.
- OCI-22369: invalid parameter encountered in method string
-
Cause: An invalid parameter is being passed to this method of SYS.RowType or SYS.RowSet.
- OCI-22370: incorrect usage of method string
-
Cause: This method of SYS.RowType or SYS.RowSet is being used inappropriately.
- OCI-22600: encountered 8.0.2 (Beta) VARRAY data that cannot be processed
-
Cause: Production Oracle8 (8.0.3 and beyond) encounters some VARRAY data which was created and stored by Oracle8 8.0.2 (Beta 2). Production Oracle8 cannot understand or process such VARRAY data.
- OCI-22601: pickler TDS context [string] is not initialized
-
Cause: Attempt to use the pickler TDS context without initializing it.
- OCI-22602: pickler TDS handle [string] is not well-formed
-
Cause: Attempt to use the pickler TDS handle without initializing/ constructing it.
- OCI-22603: cannot add an attribute to the already generated TDS handle
-
Cause: Attempt to add an attribute to the already constructed TDS.
- OCI-22604: TDS handle already generated
-
Cause: Attempt to geneate TDS that is already genearated.
- OCI-22605: FDO handle [string] is not initialized
-
Cause: Attempt to use an uninitialized FDO handle.
- OCI-22606: pickler image handle [string] is not well-formed
-
Cause: Attempt to use the image handle without initializing/ constructing it.
- OCI-22607: image handle already generated
-
Cause: Attempt to geneate image that is already genearated.
- OCI-22608: cannot add an attribute to the already generated image handle
-
Cause: Attempt to add an attribute to the already constructed image.
- OCI-22609: error string during initialization of FDO
-
Cause: Error during FDO initialization.
- OCI-22626: Type Mismatch while constructing or accessing OCIAnyData
-
Cause: Type supplied is not matching the type of the AnyData. If piece wise construction or access is being attempted, the type supplied is not matching the type of the current attribute.
- OCI-22700: object access trace event number
-
Cause: N/A
- OCI-22975: cannot create a PRIMARY KEY-based REF to this object view
-
Cause: The object view specified in the MAKE_REF function does not have a PRIMARY KEY-based object identifier. A PRIMARY KEY-based REF cannot be created for such a view.
- OCI-22976: incorrect number of arguments to MAKE_REF
-
Cause: Number of arguments for MAKE_REF is different from the number of PRIMARY KEY attributes of the object view.
- OCI-29783: GPnP attribute SET failed with error [string]
-
Cause: An attempt to set the Grid Plug and Play (GPnP) attribute failed. See the brackets for the reason.
- OCI-29785: GPnP attribute GET failed with error [string]
-
Cause: An attempt to get the Grid Plug and Play (GPnP) attribute failed. See the brackets for the reason.
- OCI-29786: SIHA attribute GET failed with error [string]
-
Cause: An attempt to get the Single-Instance High Availability (SIHA) attribute failed. See the brackets for the reason.
- OCI-29787: SIHA attribute SET failed with error [string]
-
Cause: An attempt to set the Single-Instance High Availability (SIHA) attribute failed. See the brackets for the reason.
- OCI-30100: internal error [number]
-
Cause: An internal error has occurred.
- OCI-30101: unknown parameter name 'string'
-
Cause: You have misspelled the parameter name.
- OCI-30102: 'string' is not in the legal range for 'string'
-
Cause: The value of the parameter is not within the legal range.
- OCI-30103: 'string' contains an illegal integer radix for 'string'
-
Cause: An illegal integer radix specification was found.
- OCI-30104: 'string' is not a legal integer for 'string'
-
Cause: The value is not a valid integer.
- OCI-30105: 'string' is not a legal boolean for 'string'
-
Cause: The value is not a valid boolean.
- OCI-30106: reserved for future use
-
Cause: None.
- OCI-30107: parameter name abbreviation 'string' is not unique
-
Cause: The abbreviation given was not unique.
- OCI-30108: invalid positional parameter value 'string'
-
Cause: An invalid positional parameter value has been entered.
- OCI-30109: could not open parameter file 'string'
-
Cause: The parameter file does not exist.
- OCI-30110: syntax error at 'string'
-
Cause: A syntax error was detected.
- OCI-30111: no closing quote for value 'string'
-
Cause: A quoted string was begun but not finished.
- OCI-30112: multiple values not allowed for parameter 'string'
-
Cause: You attempted to specify multiple values for a parameter which can take only one value.
- OCI-30113: error when processing file 'string'
-
Cause: A problem occurred when processing this file.
- OCI-30114: error when processing from command line
-
Cause: A problem occurred when processing the command line.
- OCI-30115: error when processing an environment variable
-
Cause: A problem occurred when processing an environment variable.
- OCI-30116: syntax error at 'string' following 'string'
-
Cause: A syntax error was detected.
- OCI-30117: syntax error at 'string' at the start of input
-
Cause: A syntax error was detected.
- OCI-30118: syntax error at 'string' at the end of input
-
Cause: A syntax error was detected.
- OCI-30119: unable to obtain a valid value for 'string'
-
Cause: No valid value was obtained for this parameter.
- OCI-30120: 'string' is not a legal oracle number for 'string'
-
Cause: The value is not a valid oracle number.
- OCI-30121: 'string' is not an allowable value for 'string'
-
Cause: The value is not a legal value for this parameter.
- OCI-30122: value 'string' for 'string' must be between 'number' and 'number'
-
Cause: The value of the parameter is not within the legal range.
- OCI-30129: invalid function argument received
-
Cause: A function received an invalid argument
- OCI-30130: invalid parameter key type received
-
Cause: A function received an invalid parameter key type
- OCI-30131: number of keys being set exceeds allocation
-
Cause: Number of parameter keys being set exceeds allocation
- OCI-30132: invalid key index supplied
-
Cause: The key index specified was not within bounds
- OCI-30133: reserved for future use
-
Cause: None.
- OCI-30134: reserved for future use
-
Cause: None.
- OCI-30135: OCI Thread operation fails
-
Cause: An OCI Thread function call has failed.
- OCI-30150: Invalid argument passed to OCIFile function
-
Cause: An invalid argument is passed to the OCIFile function. The most common cause is that a NULL pointer is passed where a non-NULL pointer is expected.
- OCI-30151: File already exists
-
Cause: Tried to open a file with OCI_FILE_EXCL flag and the file already exists.
- OCI-30152: File does not exist
-
Cause: The OCIFile function requires the file to exist, but it does not.
- OCI-30153: An invalid File Object is passed to the OCIFile function
-
Cause: An invalid File Object is passed to the OCIFile function.
- OCI-30154: The memory address given as buffer for OCIFileRead/Write is invalid
-
Cause: An invalid memory address is given as the buffer pointer for OCIFileRead/Write.
- OCI-30155: An I/O Error occured during an OCIFile function call
-
Cause: An I/O error occurred at the system level.
- OCI-30156: Out of disk space
-
Cause: The disks associated with the underlying file system are full.
- OCI-30157: An invalid argument was given to operating system call
-
Cause: The OS call was called with an invalid argument.
- OCI-30158: The OCIFileWrite causes the file to exceed the maximum allowed size
-
Cause: There is no space to write to the file. Its size is at the maximum limit.
- OCI-30159: OCIFileOpen: Cannot create the file or cannot open in the requested mode
-
Cause: The create flag was specified in OCIFileOpen such that the file was to be created. But unable to do so. Or the file already exists and the permissions on it doesn't allow the file to be opened in in the requested open mode
- OCI-30160: Unable to access the file
-
Cause: The function was unable to access the existing the file.
- OCI-30161: A system error occurred during the OCIFile function call
-
Cause: A system error occured while executing the OCIFile function.
- OCI-30162: The OCIFile context is not initialzed
-
Cause: The function OCIFileInit need to be called before calling any other OCIFile function to initialize the OCIFile context.
- OCI-30163: The thread safety initialization failed
-
Cause: The call to SlgInit failed in OCIFileInit.
- OCI-30175: invalid type given for an argument
-
Cause: There is an argument with an invalid type in the argument list.
- OCI-30176: invalid format code used in the format string
-
Cause: There is an invalid format code in the format string.
- OCI-30177: invalid flag used in a format specification
-
Cause: There is an invalid flag in a format specification.
- OCI-30178: duplicate flag used in a format specification
-
Cause: There is a duplicate flag in a format specification.
- OCI-30179: invalid argument index used in a format code
-
Cause: Zero or negative argument index or index not following (."
- OCI-30180: argument index is too large
-
Cause: An argument index exceeds actual number of arguments supplied.
- OCI-30181: integer in argument index is not immediately followed by )
-
Cause: Missing closing parenthesis in argument index.
- OCI-30182: invalid precision specifier
-
Cause: Period in format specification not followed by valid format.
- OCI-30183: invalid field width specifier
-
Cause: Invalid field width supplied.
- OCI-30184: argument type not compatible with a format code
-
Cause: Bad argument type given for a format code.
- OCI-30185: output too large to fit in the buffer
-
Cause: The buffer is not large enough to hold the entire output string.
- OCI-30186: reserved for future use
-
Cause: None.
- OCI-30187: reserved for future use
-
Cause: None.
- OCI-30188: reserved for future use
-
Cause: None.
- OCI-30189: reserved for future use
-
Cause: None.
- OCI-30190: reserved for future use
-
Cause: None.
- OCI-30191: missing argument list
-
Cause: No argument list supplied.
- OCI-30192: reserved for future use
-
Cause: None.
- OCI-30193: reserved for future use
-
Cause: None.
- OCI-30194: reserved for future use
-
Cause: None.
- OCI-30195: reserved for future use
-
Cause: None.
- OCI-30196: reserved for future use
-
Cause: None.
- OCI-30197: reserved for future use
-
Cause: None.
- OCI-30198: reserved for future use
-
Cause: None.
- OCI-30199: reserved for future use
-
Cause: None.
- OCI-30930: XML node 'string' (type=string) does not support this operation
-
Cause: The given node's type is not supported for this operation. For example, trying to add children to an attribute node, or passing in a document node as a child, are unsupported operations.
- OCI-30931: Element 'string' cannot contain mixed text
-
Cause: XML elements must be declared mixed to contain multiple text nodes
- OCI-30932: Reference node 'string' not contained in specified parent node 'string'
-
Cause: When using a reference node, it must have the specified parent node
- OCI-30933: Element 'string' may not appear at this point within parent 'string'
-
Cause: The ordering specified by the content model of the parent does not allow for this element to occur at this position.
- OCI-30934: 'string' (string node) cannot be inserted in parent 'string' (string node)
-
Cause: The schema does not allow a child node of this type to be inserted into a parent node of this type. For example, only element nodes may only be inserted into a document
- OCI-30935: XML maxoccurs value (string) exceeded
-
Cause: An attempt was made to insert more than maxoccurs values into a schema-based XML document.
- OCI-30936: Maximum number (string) of 'string' XML node elements exceeded
-
Cause: An attempt was made to insert more than the allowed number of elements (specified by the maxoccurs facet) into an XML document.
- OCI-30937: No schema definition for 'string' (namespace 'string') in parent 'string'
-
Cause: The schema definition for the parent node being processed does not allow for the specified child node in its content model. Note that any typecasting via xsi:type must occur before the schema definitions for the new type can be used.
- OCI-30938: No prefix defined for namespace 'string' (particle string)
-
Cause: An XML namespace mapping (xmlns:prefix=namespace URL) must be defined for each particle (element or attribute) stored in an schema-constrained XMLType document.
- OCI-30939: Order violation: Element 'string' may not follow element 'string'
-
Cause: The XML schema specifies a content model that is sequential, where the order of nodes in the instance must follow the order specified by the schema, and this instance relies on the schema validity to avoid maintaining instance order information
- OCI-30940: Cannot resolve prefix 'string' for QName node 'string'
-
Cause: An attempt was made to store a QName value without having a valid namespace in scope for that prefix.
- OCI-30941: Cannot specify empty URI for non-default namespace 'string'
-
Cause: An attempt was made to insert a namespace declaration for a non-default namespace using an empty URI string.
- OCI-30942: XML Schema Evolution error for schema 'string' table string column 'string'
-
Cause: The given XMLType table/column which conforms to the given schema had errors during evolution. For more information, see the more specific error below this one
- OCI-30943: XML Schema 'string' is dependent on XML schema 'string'
-
Cause: Not all dependent schemas were specified and/or the schemas were not specified in dependency order, i.e., if schema S1 is dependent on schema S, S must appear before S1.
- OCI-30944: Error during rollback for XML schema 'string' table string column 'string'
-
Cause: The given XMLType table/column which conforms to the given schema had errors during a rollback of XML schema evolution. For more information, see the more specific error below this one
- OCI-30945: Could not create mapping table 'string'
-
Cause: A mapping table could not be created during XML schema evolution. For more information, see the more specific error below this one
- OCI-30946: XML Schema Evolution warning: temporary tables not cleaned up
-
Cause: An error occurred after the schema was evolved while cleaning up temporary tables. The schema evolution was successful
- OCI-30951: Element or attribute at Xpath string exceeds maximum length
-
Cause: An attempt was made to insert a node of length exceeding the maximum length (specified by the maxLength facet) into an XML document.
- OCI-30990: insufficient privileges to change owner of resource string
-
Cause: An attempt was made to change the Owner field of an XML DB resource without sufficient privileges to do so.
- OCI-30991: cannot use DOM to add special attribute to schema-based parent
-
Cause: An attempt was made to add or remove an xsi:schemaLocation, xsi:noNamespaceSchemaLocation, xsi:type, or xsi:nil attribute to or from a schema-based XML node using DOM.
- OCI-31000: Resource 'string' is not an XDB schema document
-
Cause: The given schema URL does not refer to a registered XDB schema
- OCI-31001: Invalid resource handle or path name "string"
-
Cause: An invalid resource handle or path name was passed to the XDB hierarchical resolver.
- OCI-31002: Path name string is not a container
-
Cause: XDB expected the given path name to represent a container.
- OCI-31003: Parent string already contains child entry string
-
Cause: An attempt was made to insert a duplicate child into the XDB hierarchical resolver.
- OCI-31004: Length string of the BLOB in XDB$H_INDEX is below the minimum string
-
Cause: In the XDB$H_INDEX table, the CHILDREN column, a BLOB, must have a certain minimum length without being chained. The calculated length of the LOB was less than the stated minimum.
- OCI-31005: Path name length string exceeds maximum length string
-
Cause: The length of a path name passed to the XDB hierarchical resolver exceeded the maximum length.
- OCI-31006: Path name segment length string exceeds maximum length string
-
Cause: The length of a path name segment passed to the XDB hierarchical resolver exceeded the maximum length of a path name segment.
- OCI-31007: Attempted to delete non-empty container string/string
-
Cause: An attempt was made to delete a non-empty container in the XDB hierarchical resolver.
- OCI-31009: Access denied for property string
-
Cause: An attempt was made to access a property you don't have access to
- OCI-31010: XML element index string exceeds maximum insertion index string
-
Cause: An attempt was made to insert an XML element at an invalid index location in the node.
- OCI-31011: XML parsing failed
-
Cause: XML parser returned an error while trying to parse the document.
- OCI-31012: Given XPATH expression not supported
-
Cause: XPATH expression passed to the function is currently unsupported.
- OCI-31013: Invalid XPATH expression
-
Cause: XPATH expression passed to the function is invalid.
- OCI-31014: Attempted to delete the root container
-
Cause: An attempt was made to delete the root container in the hierarchical index.
- OCI-31015: Attempted to insert entry without name
-
Cause: An attempt was made to insert an entry into the hierarchical resolver without a child name.
- OCI-31016: Attempted to delete entry without name
-
Cause: An attempt was made to delete an entry from the hierarchical resolver without a child name.
- OCI-31017: Error generating unique OID for XML document
-
Cause: An error occurred while generating a globally unique OID for storing an XML document.
- OCI-31018: Error deleting XML document
-
Cause: The XMLType object pointed to by the given REF could not be deleted because either the REF was invalid or it pointed to a non-existent table.
- OCI-31019: Recursive deletion snapshot too old for string/string
-
Cause: Changes were made to the structure of a directory while it was being recursively deleted.
- OCI-31020: The operation is not allowed, Reason: string
-
Cause: The operation attempted is not allowed
- OCI-31021: Element definition not found
-
Cause: The element definition was not found.
- OCI-31022: Element not found
-
Cause: The element was not found.
- OCI-31023: Index size error
-
Cause: The index is greater than the allowed value.
- OCI-31025: Invalid document element
-
Cause: An attempt was made to replace the data at an invalid index number in the XML document
- OCI-31027: Path name or handle string does not point to a resource
-
Cause: An attempt was made to retrieve a resource based on a path name or resource handle that points to an entity other than a resource.
- OCI-31028: Resource metadata length string exceeded maximum length string
-
Cause: An attempt was made to insert resource metadata that exceeded the maximum length of that type of metadata.
- OCI-31029: Cannot bind to unsaved resource
-
Cause: An attempt was made to bind to a resource that had not been saved to disk.
- OCI-31030: Unable to retrieve XML document
-
Cause: The resource had an invalid (dangling) REF to an XML document.
- OCI-31033: Requested number of XML children string exceeds maximum string
-
Cause: An attempt was made to add more than the maximum number of allowable children in an XML element.
- OCI-31035: Could not bind locked resource to path string/string
-
Cause: An attempt was made to bind an existing resource to a new location in the hierarchy, but a lock could not be obtained on the resource.
- OCI-31037: Invalid XML attribute name string
-
Cause: The attribute name in the XML document did not match anything in the associated schema.
- OCI-31038: Invalid string value: "string"
-
Cause: The text in the XML document did not represent a valid value given the datatype and other constraints in the schema.
- OCI-31039: XML namespace length string exceeds maximum string
-
Cause: The length of the disk-formatted XML namespace exceeded the maximum.
- OCI-31040: Property string: XML type (string) not compatible with internal memory type (string)
-
Cause: The XML datatype given is inconsistent with the database datatype, and a conversion cannot be made.
- OCI-31041: Property string: Memory type (string) not compatible with database type (string)
-
Cause: The memory type associated with this property is mapped to an incompatible database type, and a conversion cannot be made.
- OCI-31042: Too many properties in type 'string'
-
Cause: The type can only have the same number of properties (elements and attributes) as a table can have columns.
- OCI-31043: Element 'string' not globally defined in schema 'string'
-
Cause: The specified element name has not been defined at the top level of the XML schema (i.e. globally). Elements must be defined globally to be the root of an XMLType object.
- OCI-31044: Top-level prefix length string exceeds maximum string
-
Cause: An attempt was made to save to disk a top-level XML namespace prefix whose length exceeded the maximum.
- OCI-31045: Cannot store more than string extras outside the root XML node
-
Cause: An attempt was made to store more than the maximum number of XML extras (e.g. comments and processing instructions) either before or after the document's root node.
- OCI-31046: Incorrect argument(s) specified in the operator
-
Cause: One or more of the arguments specified in the operator in the query are incorrect
- OCI-31047: Could not retrieve resource data at path string
-
Cause: An error occurred while retrieving the contents and/or metadata of a resource.
- OCI-31048: Unsaved resources cannot be updated
-
Cause: An attempt was made to update a resource that was never saved to disk.
- OCI-31050: Access denied
-
Cause: The requested access privileges have not been granted to the current user. User must be granted privileges prior to resource access.
- OCI-31051: Requested access privileges not supported
-
Cause: The requested access privileges are not supported for the specified resource.
- OCI-31052: Cannot delete ACL with other references
-
Cause: The requested deletion of an ACL resource cannot proceed. The ACL is in use by other resources.
- OCI-31053: The value of the depth argument in the operator cannot be negative
-
Cause: The value of the depth argument passed to the primary operator is not a positive integer
- OCI-31054: The string operator cannot have an ancillary operator
-
Cause: An ancillary operator was used with an operator which does not does not support ancillary operators
- OCI-31055: A null XMLType element cannot be inserted into RESOURCE_VIEW
-
Cause: The element which is being inserted into the RESOURCE_VIEW is NULL
- OCI-31056: The document being inserted does not conform to string
-
Cause: The XMLType element being inserted into the RESOURCE_VIEW does not conform to the specified Schema
- OCI-31057: Display Name of the element being inserted is null
-
Cause: The Display Name of the element which is being inserted into the RESOURCE_VIEW is null
- OCI-31058: cannot modify read-only XOBs
-
Cause: Read-Only XOBs cannot be modified.
- OCI-31059: Cannot insert root XML document node if it already exists
-
Cause: An attempt was made to insert a root node into an XML document that already had a root node.
- OCI-31060: Resource at path string could not be deleted
-
Cause: An error occurred while deleting the named resource. The specific error can be found one lower on the error stack.
- OCI-31061: XML event error
-
Cause: The specified error occurred in XDB.
- OCI-31062: Cannot delete an unsaved resource
-
Cause: An attempt was made to delete a resource that had not been saved to disk.
- OCI-31065: Cannot modify read-only property [string]
-
Cause: An attempt was made to modify an immutable XML node.
- OCI-31066: Insertion of string into string creates a cycle
-
Cause: An attempt was made to insert a link into the XDB hierarchy that would create a cycle in the tree.
- OCI-31067: XML nodes must be updated with nodes of the same type
-
Cause: An attempt was made to use updateXML to update an XML node with a node of another type.
- OCI-31068: updateXML expected data format [string] instead of [string]
-
Cause: An attempt was made to use updateXML to update data with a node of the incorrect type. Text and attribute nodes must be updated with string data, whereas element nodes must be updated with XMLType data.
- OCI-31069: Cannot apply typed changes to non-schema-based XMLType nodes
-
Cause: An attempt was made to insert, delete, or update a non-schema-based XMLType node using an XML schema definition.
- OCI-31070: Invalid database user ID string
-
Cause: An attempt was made set an invalid user ID into an XDB resource metadata property.
- OCI-31071: Invalid database username or GUID string
-
Cause: An attempt was made to set an invalid username or GUID into an XDB resource metadata property.
- OCI-31072: Too many child nodes in XMLType fragment for updateXML
-
Cause: An attempt was made to pass an XMLType fragment with multiple children as new data for the updateXML operator.
- OCI-31073: Resource not retrieved using path name
-
Cause: An attempt was made to access the path name of a resource that was either never saved to disk or was loaded using a method other than with its path name.
- OCI-31075: invalid string declaration in XML Schema
-
Cause: The XML schema contains an invalid declaration identified by the message.
- OCI-31076: required attribute "string" not specified
-
Cause: The XML schema does not specify a required attribute.
- OCI-31077: invalid attribute "string" specified
-
Cause: The XML schema specifies an invalid attribute.
- OCI-31078: error in SQL mapping information
-
Cause: There is an error in the SQL type and table specification within the XML Schema.
- OCI-31079: unable to resolve reference to string "string"
-
Cause: The identified type or attribute or element could not be resolved.
- OCI-31080: type not specified for attribute or element "string"
-
Cause: The identified attribute or element does not have a type.
- OCI-31081: name not specified for global declaration
-
Cause: The XML schema does not specify the name for the global declaration of attribute or element or simpleType or complexType.
- OCI-31082: invalid attribute "string" specified in declaration of "string"
-
Cause: The XML schema specifies an invalid attribute.
- OCI-31083: error while creating SQL type "string"."string"
-
Cause: An error occurred while trying to create the SQL type based on the specification of a complex type.
- OCI-31084: error while creating table "string"."string" for element "string"
-
Cause: An error occurred while trying to create the table based on the declaration for the identified element.
- OCI-31085: schema "string" already registered
-
Cause: An attempt was made to register a schema with the same URL as a previously registered schema.
- OCI-31086: insufficient privileges to register global schema "string"
-
Cause: An attempt was made to register a global schema without sufficient privileges.
- OCI-31087: insufficient privileges to delete schema "string"
-
Cause: An attempt was made to delete a schema resource without sufficient privileges.
- OCI-31088: object "string"."string" depends on the schema
-
Cause: An attempt was made to delete a schema which has dependent objects.
- OCI-31089: schema "string" does not target namespace "string"
-
Cause: The schema document contains references (via include and import definitions) to other schemas that do not belong to valid namespaces.
- OCI-31090: invalid database schema name "string"
-
Cause: The XML schema document contains an invalid database schema name For example, the value of attribute SQLSchema
- OCI-31091: empty string specified as a SQL name
-
Cause: The XML schema document contains a null SQL name. For example, the values of attributes SQLName, SQLType, defaultTable.
- OCI-31092: invalid SQL name "string"
-
Cause: The XML schema document contains an invalid SQL name. For example, the values of attributes SQLName, SQLType, defaultTable.
- OCI-31093: null or invalid value specified for parameter : string
-
Cause: The argument value passed for the given parameter is null or invalid.
- OCI-31094: incompatible SQL type "string" for attribute or element "string"
-
Cause: The SQL type information provided in the XML schema is not compatible with the XML datatype for the specified attribute or element.
- OCI-31095: cannot generate string : "string.string" already exists
-
Cause: The type/table name specified in the XML schema document cannot be generated because it is already being used.
- OCI-31096: validation failed for schema
-
Cause: The XML Schema could not be validated.
- OCI-31097: Hierarchical Index not empty
-
Cause: An attempt was made to rebuild the hierarchical index which is not empty.
- OCI-31099: XDB Security Internal Error
-
Cause: An XDB Security internal error has occurred.
- OCI-31100: XDB Locking Internal Error
-
Cause: An XDB Locking Internal error has occurred.
- OCI-31101: Token "string" not given while locking resource "string"
-
Cause: Locking attempted on resource when the pricipal already owns a lock given by the token above.
- OCI-31102: Already locked in exclusive mode. Cannot add lock.
-
Cause: The resource is already locked in exclusive mode. Cannot add another lock.
- OCI-31103: Resource locked in shared mode. Cannot add exclusive lock
-
Cause: The resource is locked in shared mode. Cannot add a shared lock.
- OCI-31104: Cannot find lock with token "string" on "string" for unlock
-
Cause: The lock may have been unlock or it may have expired.
- OCI-31105: User does not own lock "string"
-
Cause: The lock to be unlocked is not owned by the user.
- OCI-31107: Action failed as resource "string" is locked by name lock
-
Cause: Lock requests cause the whole request URI to be locked
- OCI-31108: Action failed as resource string is locked
-
Cause: Delete/Rename failed because of an existing lock
- OCI-31109: Action failed as parent resource string is locked
-
Cause: Delete/Rename failed because of an lock on parent resource
- OCI-31110: Action failed as resource string is locked by name
-
Cause: Delete/Rename failed because one of the children is locked.
- OCI-31111: table string cannot be hierarchically enabled
-
Cause: Trigger tabname_xdb_pitrigger already exists
- OCI-31112: fail to string for string port using xdb configuration
-
Cause: port number for the defined presentation is not valid
- OCI-31113: XDB configuration may not be updated with non-schema compliant data
-
Cause: An attempt was made to update the XDB configuration resource with non-schema or non-schema compliant data.
- OCI-31114: XDB configuration has been deleted or is corrupted
-
Cause: The XDB configuration resource has been deleted or corrupted.
- OCI-31115: XDB configuration error: string
-
Cause: An error related to XDB configuration has occurred.
- OCI-31116: Tablespace not specified correctly
-
Cause: XDB cannot be moved to the specified tablespace.
- OCI-31121: The string operator can not be FALSE
-
Cause: The value of the operator that is specified is FALSE
- OCI-31122: The string operator has incorrect RHS value
-
Cause: The right hand side value that has been specified for the operator does not evaluate to TRUE
- OCI-31151: Cyclic definition encountered for string: "string"
-
Cause: The schema definition for this type has cycles.
- OCI-31153: Cannot create schema URL with reserved prefix "http://xmlns.oracle.com/xdb/schemas/"
-
Cause: This prefix is reserved for XDB extended schema URLs and cannot be used in a user specified URL.
- OCI-31154: invalid XML document
-
Cause: The XML document is invalid with respect to its XML Schema.
- OCI-31155: attribute string not in XDB namespace
-
Cause: The specified attribute should be prefixed with XDB's namespace.
- OCI-31157: Invalid Content-Type charset
-
Cause: HTTP Content-Type header had a charset that Oracle does not understand.
- OCI-31158: schema "string" currently being referenced
-
Cause: The specified schema URL is currently being referenced by the same session. This could happen because of PLSQL XMLType variables still in scope.
- OCI-31159: XML DB is in an invalid state
-
Cause: XML DB's internal tables are in an invalid state, probably because the database was not upgraded or the upgrade was not successful
- OCI-31160: max substitution group size string exceeded by "string" (string) for head element "string" (string)
-
Cause: The maximum limit on nested substitution groups has been exceeded by an element.
- OCI-31161: element or attribute "string" cannot be stored out of line
-
Cause: An element or attribute of a simple type has SQLInline=false
- OCI-31162: element or attribute "string" has no SQLType specified
-
Cause: Schema registration was invoked with GENTYPES=false without specifying a SQLType for some element or attribute
- OCI-31163: element or attribute "string" has invalid attribute value "string" (should be "string")
-
Cause: An element or attribute for a complextype derived by restriction has an attribute whose value is different from that in the base type
- OCI-31164: cannot load object-relational XML attribute using direct path \n
-
Cause: The table being loaded contains a xml column with object-relational storage. The xmltype column contains a type with subtypes. This type of attribute cannot be loaded with direct path.
- OCI-31165: cannot load object-relational XML attribute using direct path \n
-
Cause: The table being loaded contains a xml column with object-relational storage. The xmltype column either contains an out-of-line partitioned table or the table itself is partitioned by one of the attributes of xmltype. This type of table cannot be loaded with direct path.
- OCI-31167: XML nodes over 64K in size cannot be inserted
-
Cause: An attempt was made to insert an XML Text Node with a size greater than 64K. This is not supported.
- OCI-31168: Node localname and namespace values should be less than 64K
-
Cause: An attempt was made to specify an XML Node with localname or namespace value greater than or equal to 64K. This is not supported.
- OCI-31180: DOM Type mismatch in invalid PL/SQL DOM handle
-
Cause: The specified PL/SQL DOM handle is referencing a DOM Node whose DOM Type that does not match the one available in the session. This could happen because the pl/sql handle was reused, or the original document is no longer available.
- OCI-31181: PL/SQL DOM handle accesses node that is no longer available
-
Cause: The specified pl/sql handle is referencing a node in a DOM Document that is no longer available.
- OCI-31182: Too many PL/SQL DOM handles specified
-
Cause: An attempt was made to create a PL/SQL DOM handle that exceeded the maximum allowable number of PL/SQL DOM handles.
- OCI-31185: DOM Nodes do not belong to the same DOM Document
-
Cause: The specified PL/SQL DOM Node does not belong to the parent DOM Document of the referring DOM Node.
- OCI-31190: Resource string is not a version-controlled resource
-
Cause: Either one of the following is the cause: - Checkout is requested for a resource that isn't under version control". Only version-controlled resource can be checked out. - Checkout is requested for a row of a non-versioned table.
- OCI-31191: Resource string is already checked out
-
Cause: Either one of the following is the cause: - Checkout is requested for a resource that is already checked out to the workspace by the same of different user.
- OCI-31192: Resource string has not been checked out
-
Cause: Either one of the following is the cause: - Checkin or uncheckout is requested for a resource that has not been checked out to the workspace by any user in a workspace
- OCI-31193: This versioning feature isn't supported for resource string
-
Cause: Either one of the following is the cause: - Container cannot be put under version-controlled.
- OCI-31194: Resource string is already deleted
-
Cause: Access a version-controlled resource that is already deleted.
- OCI-31195: XML node 'string' (type=string) does not support this operation
-
Cause: The given node's type is not supported for this operation. For example, trying to add children to an attribute node, or passing in a document node as a child, are unsupported operations.
- OCI-31196: XML nodes over string in size cannot be printed
-
Cause: An attempt was made to use an XML Text Node with a size greater than 64K, or an XML Comment Node with a size greater than 4K. These cannot be printed. For example, trying to add children to an attribute node, or passing in a document node as a child, are unsupported operations.
- OCI-31197: Error in processing file string
-
Cause: An error occurred while operating on the specifed file. The possible causes are the file header is corrupt or check the next error on stack
- OCI-31198: Mismatch in number of bytes transferred due to non-binary mode
-
Cause: An error occurred while reading the specifed file. The most probable cause is that the transfer was initiated in ASCII mode.
- OCI-31199: Warning in processing file string
-
Cause: A warning was raised while operating on the specifed file. However, the current operation was completed successfully.
- OCI-64495: XQuery data model has to be allowed.
-
Cause: XQuery data model was not allowed.