Cause: PMON process runs into lock conflict trying to recover processes.

Cause: Internal programming exception.

Cause: An identifier with more than 30 characters was specified.

Cause: Illegal year entered

Cause: An invalid Julian date was entered.

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.

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.

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.

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.

Cause: Your calendar doesn't extend to the specified date.

Cause: Era input does not match a known era.

Cause: The character string you specified is not a valid interval.

Cause: The leading precision of the interval is too small to store the specified interval.

Cause: The intervals or datetimes are not mutually comparable.

Cause: The number of seconds specified was greater than 59.

Cause: The leading precision of the interval is too small to store the specified interval.

Cause: The time zone hour specified was not in the valid range.

Cause: The time zone minute specified was not in the valid range.

Cause: The specified year was not in range.

Cause: The specified field was not found in the datetime or interval.

Cause: The specified hh25 field was not in the valid range.

Cause: The specified fractional seconds were not in the valid range.

Cause: The region ID referenced an invalid region.

Cause: The specified region name was not found.

Cause: The region was changing state and the overlap flag was disabled.

Cause: An attempt was made to divide by zero.

Cause: An NLS error was detected.

Cause: While trying to truncate or round dates, extra data was found in the date format picture

Cause: Supplied database name can contain only A-Z, 0-9, '_', '#', '$' '.' and '@' characters.

Cause: Supplied database name cannot contain a leading '.', trailing '.' or '@', or two '.' or '@' in a row.

Cause: While trying to lock a library object, a deadlock is detected.

Cause: While waiting to lock a library object, a timeout is occurred.

Cause: Had to wait to lock a library object during a nowait request.

Cause: Cannot generate diana for an object because of lock conflict.

Cause: The table or view being queried might be missing. The error number indicates the error.

Cause: Operating system process private memory has been exhausted

Cause: More shared memory is needed than was allocated in the shared pool.

Cause: During compilation of a PL/SQL block, an attempt was made to use a non-existent database link.

Cause: Attempt to execute a stored procedure without sufficient privileges.

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.

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.

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.

Cause: Attempt to execute a stored procedure that has been invalidated.

Cause: Attempt to execute a stored procedure that has been altered or dropped thus making it not callable from the calling procedure.

Cause: Attempt to execute a non-procedure.

Cause: Attempt to execute a non-existent stored procedure.

Cause: One of errors 4060 - 4067 when attempt to execute a stored procedure.

Cause: All input arguments must be valid columns

Cause: The particular datatype is not supported in the XMLGEN operator

Cause: An error occurred when processing the XML function

Cause: An error occurred when processing the DBMS_XMLGEN functions

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 '@'

Cause: The attribute immediately follows a value of object or collection type in the select list or type definition.

Cause: The queryString argument passed to DBMS_XMLGEN.newContext was not a valid query, or REF CURSOR.

Cause: The scalar parameter to XMLELEMENT has been qualified with an alias.

Cause: The indicated parameter of the XML generation function has not been aliased, although it is an expression.

Cause: An invalid or unsupported formatting argument was supplied

Cause: The column specified using setKeyColumn()/setUpdateColumn() did not exist in the table.

Cause: The column specified using setKeyColumn() was a non-scalar type column.

Cause: No columns were specified as key columns before the call to DBMS_XMLSTORE.updateXML.

Cause: The objects option is not installed at this site. Object types and other object features are, therefore, unavailable.

Cause: This function requires the oci process to be initialized in object mode.

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.

Cause: The operating system has run out of memory.

Cause: A program is in an unrecoverable error state.

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.

Cause: User exceeded the maximum number of connections (255) that can be supported by an OCI environment in object mode.

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.

Cause: User attempted to use a functionality that the server does not support.

Cause: The object type of the object is different from what is specified.

Cause: Attribute value or collection element value violated its constraint.

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.

Cause: A process has encountered an exceptional condition. This is the generic internal error number for Oracle object management services exceptions.

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.

Cause: A data type was specified which is currently unsupported.

Cause: OCI Error encountered while performing data type conversion.

Cause: The client did not receive all the chunk data for the current LCR.

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).

Cause: An attempt was made to invoke the specified function with an incorrect logical change record (LCR) type.

Cause: An attempt was made to send a chunk when the command type for the current LCR was not INSERT, UPDATE, or LOB WRITE.

Cause: Invalid data type specified for LOB chunk in OCIXStreamInChunkSend call.

Cause: An attempt was made to invoke OCILCRLobInfoGet call with an LCR that had no LOB column.

Cause: An attempt was made to set multiple LOB columns on a piece-wise LOB LCR.

Cause: An attempt was made to call OCIXStreamInChunkSend with an LCR that had empty column lists.

Cause: An attempt was made to call OCIXStreamInChunkSend with an odd number of bytes for a column flagged as AL16UTF16 or NCLOB.

Cause: An attempt was made to attach to an XStream server with a nonexistent server name.

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.

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.

Cause: The user attempts to perform an operation that does not support the specified typecode.

Cause: The specified property id is invalid.

Cause: Trying to get a property which applies only to persistent objects.

Cause: Trying to get a property which applies only to persistent and transient objects.

Cause: Trying to free an object that is persistent and dirty and the OCI_OBJECTFREE_FORCE flag is not specified.

Cause: Attempt to use the handle without initializing it.

Cause: Attempt to use a duration not valid for this function.

Cause: Attempt to resize memory without allocating it first.

Cause: Attempt to resize memory with invalid size.

Cause: Attempt to use an invalid key length.

Cause: Attempt to use a key that is already used.

Cause: Attempt to use a non-existent key

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.

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.

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.

Cause: See the error message.

Cause: See the error message.

Cause: The service context that is supplied by the user is not valid.

Cause: The duration number that is supplied by the user is not valid.

Cause: The pin duration supplied by the user is longer than the allocation duration. This affects operations such as pinning and setting default parameters.

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.

Cause: User attempted to refresh an object that has been marked for delete, update or insert (new).

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.

Cause: User is trying to use a duration that has been terminated.

Cause: This operation's result is above the range of Oracle number.

Cause: This operation's result is below the range of Oracle number.

Cause: Signed flag used is not OCI_NUMBER_SIGNED or OCI_NUMBER_UNSIGNED.

Cause: Given value is divied by zero.

Cause: The length of the integer (ie number of bytes) to be converted to or from an Oracle number is invalid.

Cause: The buffer to hold the resulting text string is too small.

Cause: An invalid or uninitialized number is passed in.

Cause: The numeric format string for converting characters to or from an Oracle number is invalid.

Cause: The text string for converting to numbers is invalid.

Cause: Attempt to convert a negative number to an unsigned integer.

Cause: The NLS parameter string for converting characters to or from an Oracle number is invalid.

Cause: Rounding done due to the given string format causes overflow.

Cause: The size of the buffer into which the hexadecimal REF string is to be written is too small.

Cause: The given hexadecimal string length must be greater than zero.

Cause: The given hexadecimal string is invalid.

Cause: The given resize size is invalid.

Cause: The given resize size is odd. In a UTF-16 environment, all characters are 2 bytes in length.

Cause: An un-initialized variable-length array is being operated upon.

Cause: Trying to resize a non-zero variable-length array to 0 elements.

Cause: The variable-length array on the right-hand-side of an assignment or the destination array of an append 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.

Cause: Collection element at the given index does not exist.

Cause: Given type code is not valid.

Cause: Trying to delete a non-existent collection element.

Cause: Left hand and right side collections are not of same type.

Cause: Trying to delete an element of a variable-length array.

Cause: Given index is not in the required range.

Cause: Given collection is empty.

Cause: Given trim size is greater than the current collection size.

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.

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

Cause: LOB buffering is enabled and an attempt was made to modify the LOB using two different LOB locators.

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.

Cause: The operation attempted is not allowed when LOB buffering is enabled.

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.

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.

Cause: The buffered write operation has an input offset value more than one byte or character past the end of the LOB.

Cause: Attempted to access a directory that does not exist, or attempted to access a file in a directory that does not exist.

Cause: The user does not have the necessary access privileges on the directory alias and/or the file for the 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.

Cause: The operation attempted on the file failed.

Cause: The file is not open for the required operation to be performed.

Cause: The number of open files has reached the maximum limit.

Cause: The user is trying to obtain information for a type that cannot be found.

Cause: Type element with the given name is not found in the type.

Cause: The user is trying to create a type that already exists.

Cause: The user is trying to alter a built-in type.

Cause: The user is attempting to create an object type where more than one attributes have the same name.

Cause: The type of the attribute does not exist.

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.

Cause: The number of methods or the method signature do not match that of the original type declaration. This is not supported.

Cause: The input type does not contain a map or order function so one cannot be returned.

Cause: The user is trying to obtain information for collection types on a non-named collection type.

Cause: The user is trying to use a number typecode that is not valid.

Cause: The user is trying to obtain the number of elements for a non-array 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.

Cause: OCITypeResult() was called on a method that does not return any results.

Cause: The type of the accessed object has been altered and the client's object is based on an earlier type definition.

Cause: An attempt was made to call an API which is not supported by the Oracle server.

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.

Cause: An invalid parameter is being passed to this method of SYS.RowType or SYS.RowSet.

Cause: This method of SYS.RowType or SYS.RowSet is being used inappropriately.

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.

Cause: Attempt to use the pickler TDS context without initializing it.

Cause: Attempt to use the pickler TDS handle without initializing/ constructing it.

Cause: Attempt to add an attribute to the already constructed TDS.

Cause: Attempt to geneate TDS that is already genearated.

Cause: Attempt to use an uninitialized FDO handle.

Cause: Attempt to use the image handle without initializing/ constructing it.

Cause: Attempt to geneate image that is already genearated.

Cause: Attempt to add an attribute to the already constructed image.

Cause: Error during FDO initialization.

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.

Cause: N/A

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.

Cause: Number of arguments for MAKE_REF is different from the number of PRIMARY KEY attributes of the object view.

Cause: An attempt to set the Grid Plug and Play (GPnP) attribute failed. See the brackets for the reason.

Cause: An attempt to get the Grid Plug and Play (GPnP) attribute failed. See the brackets for the reason.

Cause: An attempt to get the Single-Instance High Availability (SIHA) attribute failed. See the brackets for the reason.

Cause: An attempt to set the Single-Instance High Availability (SIHA) attribute failed. See the brackets for the reason.

Cause: An internal error has occurred.

Cause: You have misspelled the parameter name.

Cause: The value of the parameter is not within the legal range.

Cause: An illegal integer radix specification was found.

Cause: The value is not a valid integer.

Cause: The value is not a valid boolean.

Cause: None.

Cause: The abbreviation given was not unique.

Cause: An invalid positional parameter value has been entered.

Cause: The parameter file does not exist.

Cause: A syntax error was detected.

Cause: A quoted string was begun but not finished.

Cause: You attempted to specify multiple values for a parameter which can take only one value.

Cause: A problem occurred when processing this file.

Cause: A problem occurred when processing the command line.

Cause: A problem occurred when processing an environment variable.

Cause: A syntax error was detected.

Cause: A syntax error was detected.

Cause: A syntax error was detected.

Cause: No valid value was obtained for this parameter.

Cause: The value is not a valid oracle number.

Cause: The value is not a legal value for this parameter.

Cause: The value of the parameter is not within the legal range.

Cause: A function received an invalid argument

Cause: A function received an invalid parameter key type

Cause: Number of parameter keys being set exceeds allocation

Cause: The key index specified was not within bounds

Cause: None.

Cause: None.

Cause: An OCI Thread function call has failed.

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.

Cause: Tried to open a file with OCI_FILE_EXCL flag and the file already exists.

Cause: The OCIFile function requires the file to exist, but it does not.

Cause: An invalid File Object is passed to the OCIFile function.

Cause: An invalid memory address is given as the buffer pointer for OCIFileRead/Write.

Cause: An I/O error occurred at the system level.

Cause: The disks associated with the underlying file system are full.

Cause: The OS call was called with an invalid argument.

Cause: There is no space to write to the file. Its size is at the maximum limit.

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

Cause: The function was unable to access the existing the file.

Cause: A system error occured while executing the OCIFile function.

Cause: The function OCIFileInit need to be called before calling any other OCIFile function to initialize the OCIFile context.

Cause: The call to SlgInit failed in OCIFileInit.

Cause: There is an argument with an invalid type in the argument list.

Cause: There is an invalid format code in the format string.

Cause: There is an invalid flag in a format specification.

Cause: There is a duplicate flag in a format specification.

Cause: Zero or negative argument index or index not following (."

Cause: An argument index exceeds actual number of arguments supplied.

Cause: Missing closing parenthesis in argument index.

Cause: Period in format specification not followed by valid format.

Cause: Invalid field width supplied.

Cause: Bad argument type given for a format code.

Cause: The buffer is not large enough to hold the entire output string.

Cause: None.

Cause: None.

Cause: None.

Cause: None.

Cause: None.

Cause: No argument list supplied.

Cause: None.

Cause: None.

Cause: None.

Cause: None.

Cause: None.

Cause: None.

Cause: None.

Cause: None.

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.

Cause: XML elements must be declared mixed to contain multiple text nodes

Cause: When using a reference node, it must have the specified parent node

Cause: The ordering specified by the content model of the parent does not allow for this element to occur at this position.

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

Cause: An attempt was made to insert more than maxoccurs values into a schema-based XML document.

Cause: An attempt was made to insert more than the allowed number of elements (specified by the maxoccurs facet) into an XML document.

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.

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.

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

Cause: An attempt was made to store a QName value without having a valid namespace in scope for that prefix.

Cause: An attempt was made to insert a namespace declaration for a non-default namespace using an empty URI 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

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.

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

Cause: A mapping table could not be created during XML schema evolution. For more information, see the more specific error below this one

Cause: An error occurred after the schema was evolved while cleaning up temporary tables. The schema evolution was successful

Cause: An attempt was made to insert a node of length exceeding the maximum length (specified by the maxLength facet) into an XML document.

Cause: An attempt was made to change the Owner field of an XML DB resource without sufficient privileges to do so.

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.

Cause: The given schema URL does not refer to a registered XDB schema

Cause: An invalid resource handle or path name was passed to the XDB hierarchical resolver.

Cause: XDB expected the given path name to represent a container.

Cause: An attempt was made to insert a duplicate child into the XDB hierarchical resolver.

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.

Cause: The length of a path name passed to the XDB hierarchical resolver exceeded the maximum length.

Cause: The length of a path name segment passed to the XDB hierarchical resolver exceeded the maximum length of a path name segment.

Cause: An attempt was made to delete a non-empty container in the XDB hierarchical resolver.

Cause: An attempt was made to access a property you don't have access to

Cause: An attempt was made to insert an XML element at an invalid index location in the node.

Cause: XML parser returned an error while trying to parse the document.

Cause: XPATH expression passed to the function is currently unsupported.

Cause: XPATH expression passed to the function is invalid.

Cause: An attempt was made to delete the root container in the hierarchical index.

Cause: An attempt was made to insert an entry into the hierarchical resolver without a child name.

Cause: An attempt was made to delete an entry from the hierarchical resolver without a child name.

Cause: An error occurred while generating a globally unique OID for storing an 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.

Cause: Changes were made to the structure of a directory while it was being recursively deleted.

Cause: The operation attempted is not allowed

Cause: The element definition was not found.

Cause: The element was not found.

Cause: The index is greater than the allowed value.

Cause: An attempt was made to replace the data at an invalid index number in the XML document

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.

Cause: An attempt was made to insert resource metadata that exceeded the maximum length of that type of metadata.

Cause: An attempt was made to bind to a resource that had not been saved to disk.

Cause: The resource had an invalid (dangling) REF to an XML document.

Cause: An attempt was made to add more than the maximum number of allowable children in an XML element.

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.

Cause: The attribute name in the XML document did not match anything in the associated schema.

Cause: The text in the XML document did not represent a valid value given the datatype and other constraints in the schema.

Cause: The length of the disk-formatted XML namespace exceeded the maximum.

Cause: The XML datatype given is inconsistent with the database datatype, and a conversion cannot be made.

Cause: The memory type associated with this property is mapped to an incompatible database type, and a conversion cannot be made.

Cause: The type can only have the same number of properties (elements and attributes) as a table can have columns.

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.

Cause: An attempt was made to save to disk a top-level XML namespace prefix whose length exceeded the maximum.

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.

Cause: One or more of the arguments specified in the operator in the query are incorrect

Cause: An error occurred while retrieving the contents and/or metadata of a resource.

Cause: An attempt was made to update a resource that was never saved to disk.

Cause: The requested access privileges have not been granted to the current user. User must be granted privileges prior to resource access.

Cause: The requested access privileges are not supported for the specified resource.

Cause: The requested deletion of an ACL resource cannot proceed. The ACL is in use by other resources.

Cause: The value of the depth argument passed to the primary operator is not a positive integer

Cause: An ancillary operator was used with an operator which does not does not support ancillary operators

Cause: The element which is being inserted into the RESOURCE_VIEW is NULL

Cause: The XMLType element being inserted into the RESOURCE_VIEW does not conform to the specified Schema

Cause: The Display Name of the element which is being inserted into the RESOURCE_VIEW is null

Cause: Read-Only XOBs cannot be modified.

Cause: An attempt was made to insert a root node into an XML document that already had a root node.

Cause: An error occurred while deleting the named resource. The specific error can be found one lower on the error stack.

Cause: The specified error occurred in XDB.

Cause: An attempt was made to delete a resource that had not been saved to disk.

Cause: An attempt was made to modify an immutable XML node.

Cause: An attempt was made to insert a link into the XDB hierarchy that would create a cycle in the tree.

Cause: An attempt was made to use updateXML to update an XML node with a node of another type.

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.

Cause: An attempt was made to insert, delete, or update a non-schema-based XMLType node using an XML schema definition.

Cause: An attempt was made set an invalid user ID into an XDB resource metadata property.

Cause: An attempt was made to set an invalid username or GUID into an XDB resource metadata property.

Cause: An attempt was made to pass an XMLType fragment with multiple children as new data for the updateXML operator.

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.

Cause: The XML schema contains an invalid declaration identified by the message.

Cause: The XML schema does not specify a required attribute.

Cause: The XML schema specifies an invalid attribute.

Cause: There is an error in the SQL type and table specification within the XML Schema.

Cause: The identified type or attribute or element could not be resolved.

Cause: The identified attribute or element does not have a type.

Cause: The XML schema does not specify the name for the global declaration of attribute or element or simpleType or complexType.

Cause: The XML schema specifies an invalid attribute.

Cause: An error occurred while trying to create the SQL type based on the specification of a complex type.

Cause: An error occurred while trying to create the table based on the declaration for the identified element.

Cause: An attempt was made to register a schema with the same URL as a previously registered schema.

Cause: An attempt was made to register a global schema without sufficient privileges.

Cause: An attempt was made to delete a schema resource without sufficient privileges.

Cause: An attempt was made to delete a schema which has dependent objects.

Cause: The schema document contains references (via include and import definitions) to other schemas that do not belong to valid namespaces.

Cause: The XML schema document contains an invalid database schema name For example, the value of attribute SQLSchema

Cause: The XML schema document contains a null SQL name. For example, the values of attributes SQLName, SQLType, defaultTable.

Cause: The XML schema document contains an invalid SQL name. For example, the values of attributes SQLName, SQLType, defaultTable.

Cause: The argument value passed for the given parameter is null or invalid.

Cause: The SQL type information provided in the XML schema is not compatible with the XML datatype for the specified attribute or element.

Cause: The type/table name specified in the XML schema document cannot be generated because it is already being used.

Cause: The XML Schema could not be validated.

Cause: An attempt was made to rebuild the hierarchical index which is not empty.

Cause: An XDB Security internal error has occurred.

Cause: An XDB Locking Internal error has occurred.

Cause: Locking attempted on resource when the pricipal already owns a lock given by the token above.

Cause: The resource is already locked in exclusive mode. Cannot add another lock.

Cause: The resource is locked in shared mode. Cannot add a shared lock.

Cause: The lock may have been unlock or it may have expired.

Cause: The lock to be unlocked is not owned by the user.

Cause: Lock requests cause the whole request URI to be locked

Cause: Delete/Rename failed because of an existing lock

Cause: Delete/Rename failed because of an lock on parent resource

Cause: Delete/Rename failed because one of the children is locked.

Cause: Trigger tabname_xdb_pitrigger already exists

Cause: port number for the defined presentation is not valid

Cause: An attempt was made to update the XDB configuration resource with non-schema or non-schema compliant data.

Cause: The XDB configuration resource has been deleted or corrupted.

Cause: An error related to XDB configuration has occurred.

Cause: XDB cannot be moved to the specified tablespace.

Cause: The value of the operator that is specified is FALSE

Cause: The right hand side value that has been specified for the operator does not evaluate to TRUE

Cause: The schema definition for this type has cycles.

Cause: This prefix is reserved for XDB extended schema URLs and cannot be used in a user specified URL.

Cause: The XML document is invalid with respect to its XML Schema.

Cause: The specified attribute should be prefixed with XDB's namespace.

Cause: HTTP Content-Type header had a charset that Oracle does not understand.

Cause: The specified schema URL is currently being referenced by the same session. This could happen because of PLSQL XMLType variables still in scope.

Cause: XML DB's internal tables are in an invalid state, probably because the database was not upgraded or the upgrade was not successful

Cause: The maximum limit on nested substitution groups has been exceeded by an element.

Cause: An element or attribute of a simple type has SQLInline=false

Cause: Schema registration was invoked with GENTYPES=false without specifying a SQLType for some element or attribute

Cause: An element or attribute for a complextype derived by restriction has an attribute whose value is different from that in the base type

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.

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.

Cause: An attempt was made to insert an XML Text Node with a size greater than 64K. This is not supported.

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.

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.

Cause: The specified pl/sql handle is referencing a node in a DOM Document that is no longer available.

Cause: An attempt was made to create a PL/SQL DOM handle that exceeded the maximum allowable number of PL/SQL DOM handles.

Cause: The specified PL/SQL DOM Node does not belong to the parent DOM Document of the referring DOM Node.

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.

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.

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

Cause: Either one of the following is the cause: - Container cannot be put under version-controlled.

Cause: Access a version-controlled resource that is already deleted.

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.

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.

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

Cause: An error occurred while reading the specifed file. The most probable cause is that the transfer was initiated in ASCII mode.

Cause: A warning was raised while operating on the specifed file. However, the current operation was completed successfully.

Cause: XQuery data model was not allowed.