Cause: The skip_row procedure was called which raises this error

Cause: The stored procedure 'raise_application_error' was called which causes this error to be generated.

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: The object snapshot operation failed. Additional details are provided in the error message.

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 format of the image passed to the pickler is incorrect and cannot be understood.

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: The handles passed in may not be valid

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: An attempt was made 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: Constraints on the attribute were violated

Cause: see following message

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 typically happens if there is infinite recursion in the PL/SQL function that is being executed.

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; (5) the locator is for a BFILE/BLOB and the routine expects a CLOB/NCLOB locator; (6) the locator is for a CLOB/NCLOB and the routine expects a BFILE/BLOB locator;

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: Filename contains a path "../" which references a parent directory

Cause: LOB access layer could not handle duplicate LONG binds.

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 or LOB failed.

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

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

Cause: An attempt was made to commit a transaction with open LOBs at transaction commit time.

Cause: An attempt was made to open a LOB in read-write mode before a transaction was started.

Cause: An attempt was made to open a LOB that already is open in this transaction.

Cause: An attempt was made to write to or update a LOB opened in read-only mode.

Cause: An attempt was made to bind data more than 4000 bytes of data to both LOB and LONG columns in the same insert or update statement. You can bind more than 4000 bytes of data to either a LONG column or one or more LOB columns but not both.

Cause: An attempt was made to specify ALTER TABLE options which are disallowed during conversion of LONG datatype to LOB. The only ALTER TABLE options allowed during conversion of LONG datatype to LOB are the default clause and LOB storage clause for the column being converted to LOB.

Cause: An attempt was made to commit a transaction with open LOBs at transaction commit time.

Cause: The length of directory alias name or file name given for a BFILE is too long.

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

Cause: The user is trying to obtain the supertype information for a non-object type.

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: attempt to perform an operation that is allowed only on a user-defined type, and the type is not a user-defined type.

Cause: An attempt was made to replace a type whose attribute definition been been altered.

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

Cause: An invalid alter type statement was submitted.

Cause: The type of the attribute does not exist.

Cause: An attempt was made to alter a type which has a dependent type or table without specifying the CASCADE or INVALIDATE option.

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: The VERSION option is specified without a user version string.

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

Cause: The specified error table does not have the expected table structure.

Cause: The error table does not exist.

Cause: The use of the ALTER TYPE statement caused a compilation error.

Cause: An attempt was made to change a type with subtypes to FINAL.

Cause: An attempt was made to change a type with dependent tables to NOT INSTANTIABLE.

Cause: Altering the target type causes errors in its dependent object.

Cause: An attempt was made to execute ALTER TYPE on a non-object type.

Cause: An attempt was made to perform ALTER TYPE on an invalid type.

Cause: An attempt was made to perform ALTER TYPE on an incomplete type.

Cause: Altering the target type causes errors in its dependent object.

Cause: An attempt was made to reset the type version with invalid dependent types and tables.

Cause: An attempt was made to reset the type version when the data in the dependent table has not been upgraded to the latest type version.

Cause: A pre 8.2 client has requested a type that has been altered on the server.

Cause: One of the following: 1) An attempt was made to alter a type with a dependent table in 8.0 image format and the NOT INCLUDING TABLE DATA option was specified. 2) An attempt was made to upgrade a table in 8.0 image format with the NOT INCLUDING DATA option specified.

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 alter the final property of a type with dependent table(s) without specifying the CASCADE INCLUDING DATA . option.

Cause: An attempt was made to alter a type to not final when its embedded attribute is defined as substitutable in some tables. Note, this is a restriction in 9.0 version because when a type is altered to not final, column of that type is set to not substitutable at all levels; thus, it is an error if one of its embedded attribute column is already marked substitutable.

Cause: An attempt was made to reset the version, drop or alter a type when the data in dependent table has not been upgraded to the latest version.

Cause: An attempt was made to assign or copy a supertype instance to a container (destination) that can only hold a subtype instance.

Cause: An attempt was made to alter a type (add or modify attribute) which causes the size of its dependent VARRAY column to exceed the maximum inline column size. However, the VARRAY column was not specified to be stored as LOB at the table level when the table was created.

Cause: Compilation failed for a type which was invalidated by ALTER TYPE. We throw this error and rollback the compilation effort so that the user may be able to fix whatever is causing the compilation error and try again. It is important that we do not chnage status here and modify the dependency information as this will affect the creation of versions.

Cause: An attempt was made to specify CONVERT TO SUBSTITUTABLE option for ALTER TYPE other than NOT FINAL change.

Cause: An attempt was made to perform an operation which requires the specified datatype to be valid, but the datatype is invalid

Cause: An attempt was made to alter a type which has a cyclical dependency, with invalidate option.

Cause: The ALTER TYPE does not contain any changes to the type.

Cause: The object type DDL was not supported in an Editioned schema.

Cause: An attempt was made to get PL/SQL package type description information from a version of the Oracle server that does not support the description of PL/SQL package types.

Cause: An incomplete SYS.AnyType or SYS.AnyData or SYS.AnyDataSet is being used inappropriately.

Cause: An attempt was made to call an Oracle Call Interface (OCI) API which is not supported by this version of 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.AnyType ,SYS.AnyData or SYS.AnyDataSet

Cause: This method of SYS.AnyType or SYS.AnyData or SYS.AnyDataSet is being used inappropriately.

Cause: Some of the older versions of the type may have got deleted because one or more of the types it were referencing was dropped.

Cause: This is an internally used event for type dictionary upgrades from 8.0 to 8.1.

Cause: An older version HC is encountered when creating a new version hahscode. Currently this is handled internally.

Cause: The type for which reset version was requested has table dependents.

Cause: This event is used to check for subtypes in complete type tree without any restriction on depth in the fix for bug# 12430142.

Cause: A public type synonym was qualified with a schema which may lead to incorrect name resolution. This issue has been resolved. However, this event allows you to use the old behavior if desired.

Cause: An attribute column has been referenced in the 'modify_opaque_type' clause.

Cause: An attempt to ALTER TYPE [ADD | DROP | MODIFY] ATTRIBUTE on a type with synonym dependents defined on a FINAL type, which has table dependents, failed.

Cause: This event is used to bypass the error "ORA-39779" during the import of table data which occurs because of the mismatch in the hashcodes of a user-defined type between the source and the target databases. The event has to be used when the source database has an improper hashcode for the user-defined type.

Cause: This event is used to bypass regenerating dependencies during upgrade while running ALTER TABLE MOVE on type dictionary tables to enable storage in row. This happens on the upgrade path from 10.1.

Cause: An attempt was made to ALTER TYPE COMPILE when the type collation was different from the current active collation. This is not allowed.

Cause: This event is used to allow types in status 6 to recompile with current environment settings. The standard behavior is to reuse the current compiled settings. This is made available so that users can change the hashcodes of types created under different NLS_LANGUAGE_SEMANTICS.

Cause: An attempt was made to create a persistable type with a non-persistable user-defined type (UDT) attribute.

Cause: An attempt was made to create a column or table of a non-persistable type

Cause: This event is used to abort the unnecessary INSERT or DELETE of rows in the nested table storage table when the nested table column in the parent table does not qualify for update in the current row.

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: Error while adding a scalar attribute to the image handle

Cause: Incorrect TDS handle is passed

Cause: collection construct/access routines are being on an image but the TDS does not describe that a collection TDS

Cause: buflen is incorrect

Cause: Error during the construction of collection

Cause: collection routine is invoked upon a non-collection attribute

Cause: The function being invoked is applicable only for 8.1 images

Cause: Error while accessing collection in the image handle

Cause: attribute in question is probably the attribute of a null embedded image

Cause: Accessing a collection element after all the collection elements are already accessed

Cause: Buffer size is not enough to hold the value. Most likely while doing the character set conversion, a bigger buffer is needed.

Cause: Any error returned from pickler routines on the agent side.

Cause: Attempt to use the OCIAnyData without initializing constructing it.

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: Type code is not that of object/varray/nested table

Cause: Attempt to add attributes to OCIAnyData that is already constructed.

Cause: Attempting an operation that is not valid on null OCIAnyData

Cause: Passing an attribute that is null or not well-formed

Cause: Passing an attribute that is not well-formed or does not match the input type.

Cause: The AnyDataSet parameter is null or it is somehow invalid for the current operation.

Cause: AnyDataSet that is passed in may not be valid.

Cause: Current instance in the AnyDataSet has not been fully constructed.

Cause: OCIAnyData did not support conversion of time stamp with time zone when the version of time zone files differ.

Cause: An attempt was made to convert a corrupted image.

Cause: An attempt was made to insert or update an object column with transformed data. Preventing unexpected data from being written to disk is an internal error.

Cause: An attempt was made to use an incomplete type as a constructor.

Cause: The specified object row variable is not available in the scope of name resolution.

Cause: Remote type reference was not supported with user-defined aggregate function.

Cause: An attempt was made to create or specify a column or constructor of an object type that has no attributes. Only object types that have at least one attribute are allowed in this context.

Cause: An attempt was made to perform queries or DML operations on remote object tables or on remote table columns whose type is one of object, REF, nested table or VARRAY.

Cause: An attempt was made to insert a NULL object into an object table or a Nested Table.

Cause: An attempt was made to extract an attribute from an item that is neither an object nor a REF.

Cause: Invalid use of a non-scalar (for example, object type) item.

Cause: An attempt was made to access an object type's attributes by dereferencing a REF item.

Cause: An attempt was made to access a non-existent attribute of an object type.

Cause: An attempt was made to modify the attributes an object by dereferencing a REF column in an UPDATE statement.

Cause: An attempt to access the nested table column's storage table is not allowed in the given context.

Cause: Object or Collection value was too large. The size of the value might have exceeded 30k in a SORT context, or the size might be too big for available memory.

Cause: Value provided for the object type attribute or collection element exceeded the size specified in the type declaration.

Cause: RETURNING clause is currently not supported for object type columns, LONG columns, remote tables, INSERT with subquery, and INSTEAD OF Triggers.

Cause: An attempt was made to use a subquery in the column default clause expression.

Cause: An attempt was made to use a subquery expression where these are not supported.

Cause: An attempt to operate on a REF value scoped to a different table than the expected one

Cause: An attempt was made to use a non instantiable type as a constructor.

Cause: Value provided for the pattern or replacement string in the form of VARCHAR2 or CLOB for LOB SQL functions exceeded the 32K size limit.

Cause: An attempt was made to use the transient type in the query result.

Cause: An attempt was made to convert CLOB to CHAR or BLOB to RAW, where the LOB size was bigger than the buffer limit for CHAR and RAW types. Note that widths are reported in characters if character length semantics are in effect for the column, otherwise widths are reported in bytes.

Cause: An attempt was made to use relational hint or keyword in user- level DML.

Cause: An attempt was made to update SYS_NC columns directly.

Cause: A LOB storage option (CHUNK, PCTVERSION, CACHE, NOCACHE, TABLESPACE, STORAGE, INDEX, SECUREFULE/BASICFILE, [A]SYNC) was specified more than once.

Cause: The specified CHUNK LOB storage option value must be an integer.

Cause: The specified PCTVERSION LOB storage option value must be an integer.

Cause: A LOB storage option was not specified

Cause: A valid LOB store index option was not specified.

Cause: The optional name for LOB storage segment was specified with multiple columns in the column list.

Cause: An attempt was made to add columns to an object table. Object tables cannot be altered to add columns since its definition is based on an object type.

Cause: An attempt was made to alter the object table by modifing existing columns. An object table cannot be altered to modify existing columns since it is based on an object type. The table definition must be in sync with the corresponding type.

Cause: An attempt was made to modify the column type to object, REF, nested table, VARRAY or LOB type.

Cause: An attempt was made to modify an object, REF, VARRAY, nested table, or LOB column type.

Cause: An attempt was made to create an object table using a non- object type, or to create a column that is a REF to a non-object type.

Cause: An attempt was made to create a column or object table of a non- existent type.

Cause: An attempt was made to specify an object identifier for the type that does not match the existing identifier of the incomplete type of the same name.

Cause: A synonym specification for a datatype is not supported

Cause: An attempt was made to ALTER or DROP a LOB index.

Cause: An attempt was made to specify multiple columns where only one is allowed.

Cause: An attempt was made to replace a type that has table dependents.

Cause: An attempt was made to drop a tablespace which contains the segment(s) for the LOB columns of a table but does not contain the table segment.

Cause: The type dependency hierarchy was structured to have depth greater than 1024.

Cause: attempt to perform ALTER TYPE with REPLACE option a non-object type

Cause: An attempt to perform ALTER TYPE with REPLACE option for a pure incomplete type

Cause: An attempt to create an OID INDEX on a table with primary key based object identifiers.

Cause: An attempt to create a primary key based object table without specifying a primary key

Cause: Attribute specified in the user_defined clause is not an attribute of the REF type

Cause: An attempt to drop the primary key of an object table which has a primary key based object identifier

Cause: An attempt to create a kind of user-defined type which is not allowed, or an attempt to create table columns or use default constructor with a type on which these are not supported.

Cause: One or more invalid options were encountered while parsing the physical attributes of a LOB partition or subpartition. Either the LOB partition is in a table partitioned using the HASH method, or the LOB subpartition is in a table subpartitioned using the HASH method. TABLESPACE is the only valid option for a HASH partition or subpartition.

Cause: An attempt was made to specify a partition or subpartition that has already been specified for the LOB column.

Cause: An attempt was made to specify a LOB INDEX clause in a CREATE TABLE or ALTER TABLE statement for a partitioned table.

Cause: An invalid REF was accessed.

Cause: The object corresponding to the REF that was accessed does not exist.

Cause: The object cannot be created in the database.

Cause: The object could not be deleted from the database.

Cause: The object could not be modified in the database.

Cause: An attempt was made to get a REF for something other than an object in an object table. REFs can only be taken for objects in object tables.

Cause: The scoped table specified for a REF column is not an object table.

Cause: The type specified for the REF column and the type specified for the scope table are different.

Cause: Multiple SCOPE clauses were specified for a single REF column.

Cause: An attempt was made to insert a REF value that does not point to the scoped table.

Cause: An attempt was made to specify a constraint name for a constraint on a REF column.

Cause: An attempt was made to specify multiple columns in a single REF constraint.

Cause: The scoped table specified for a REF column does not exist.

Cause: The constraint specified does not apply to non-REF columns.

Cause: An attempt was made to add a constraint to existing unscoped REF columns of a table which contains one or more rows.

Cause: The referenced table specified for a REF column is not an object table.

Cause: REF column has both a referential and a scope constraint. A referential constraint implies a scope constraint.

Cause: User-defined REF column does not have a scope constraint.

Cause: Table mentioned in the referential integrity constraint is different from the scope table of the REF column.

Cause: An attempt was made to specify both a scope and a rowid constraint on a REF column.

Cause: The THE subquery must SELECT a nested table or VARRAY item.

Cause: Comparison of VARRAY or LOB attributes of an object type was attempted in the absence of a MAP or ORDER method.

Cause: CURSOR on a subquery is allowed only in the top-level SELECT list of a query.

Cause: MULTISET expressions are allowed only inside a CAST to a nested table or VARRAY type.

Cause: invalid use of a nested table column

Cause: attempt to access rows of an item whose type is not known at parse time or that is not of a nested table type

Cause: Attempted to perform a DML on an expression or on a nested table view column where a nested table column of a base table is expected.

Cause: Attempted to CAST to a type that is not a nested table or VARRAY

Cause: The evaluation of the THE subquery or nested table column resulted in a NULL value implying a NULL table instance. The THE subquery or nested table column must identify a single non-NULL table instance.

Cause: The total number of elements used in VARRAY construction exceeds the specified VARRAY limit.

Cause: Table name was qualified with schema name in the nested table column's (or attribute's) storage clause.

Cause: The storage clause is specified more than once for the NESTED TABLE column.

Cause: The storage clause is specified for a column or attribute that is not a nested table column or attribute.

Cause: The storage clause is not specified for a nested table column or attribute.

Cause: Attempted to DROP a nested table.

Cause: An attempt was made to ADD or MODIFY columns of a nested table's storage table.

Cause: Exact FETCH on a query was specified which is not allowed if the query returns any cursors.

Cause: Not using VARRAY to define storage clause for VARRAY column or attribute.

Cause: Attemp to define a VARRAY storage clause for a column or attribute which is not VARRAY type.

Cause: The error could be one of the following. The object corresponding to the REF does not exist or the object was locked by another user and the lock with nowait request failed.

Cause: The row containing the LOB value must be locked before updating the LOB value.

Cause: The buffer length is not big enough to hold the amount of data requested.

Cause: The LOB value associated with the input locator does not exist. The information in the locator does not refer to an existing LOB.

Cause: Trying to write LOB value via the streaming mechanism (i.e. unlimited write) but the input amount of data to stream was specified as 0. Thus, the user is trying to write 0 bytes to the LOB value.

Cause: The version of the LOB value needed for the consistent read was already overwritten by another writer.

Cause: An attempt was made to write too much data to the LOB value. LOB size is limited to (4 gigabytes - 1) * DB_BLOCK_SIZE.

Cause: The input length for which to trim the LOB value to is greater than the current length of the LOB value.

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: An attempt was made to grant or revoke an invalid privilege on a directory.

Cause: The required directory name is invalid or missing.

Cause: Attempt to access a directory that does not exist.

Cause: Attempt to replace, drop or rename an object with type or table dependents.

Cause: An attempt was made to replace a system predefined type.

Cause: an object type must have a MAP or ORDER method defined for all comparisons other than equality and inequality comparisons.

Cause: ORDER method used to compare two object values returned NULL which is not allowed.

Cause: Nested Table equality was tried where the element ADT did not have a map method defined on it.

Cause: The cardinality of the input nested table to the powermultiset should not exceed 32 elements

Cause: The multiset operation attempted was not supported for the nested table element type.

Cause: The cardinality parameter has to be greater than 1 and less than or equal to the cardinality of the input.

Cause: An empty set was given as input to the powermultiset function.

Cause: NULL was given as input to the powermultiset or COLLECT function.

Cause: An invalid operation is used in a check constraint or trigger

Cause: Either the expression is not a view name or the name specified does not correspond to an object view.

Cause: When creating an object view, the datatype of an expression in the WITH OBJECT OID clause is not allowed for PRIMARY KEY-based OID.

Cause: A value constituting the PRIMARY KEY-based object identifier is NULL.

Cause: Size of the PRIMARY KEY-based object identifier of an object view exceeds the maximum size of 4000 bytes.

Cause: WITH OBJECT OID clause is not specified when creating an 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.

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

Cause: Either the attribute name is missing in the WITH OBJECT OID clause or it is invalid.

Cause: Attempted to specify a Nested attribute in the WITH OBJECT OID clause.

Cause: Attempt to insert an object view REF or user-defined REF in a REF column created to store system generated REF values"

Cause: The WITH OBJECT OID DEFAULT clause was used, but the underlying view or table does not have a OID.

Cause: The super-view is based on a table/view having the system generated OID and the sub-view must also be based on a similar table/view.

Cause: The view derives its OID from a table/view having primary key based OID and sub-views cannot be created under such views.

Cause: Attempt to use a system generated REF value where a user-defined REF value should be used.

Cause: The query defining the view contains references to a super-view of the view being created.

Cause: A LOB locator selected in one transaction cannot be used in a different transaction.

Cause: The data to be returned in the argument is greater than the amount of space allocated for the argument.

Cause: A remote LOB column cannot be referenced.

Cause: (1) For LOB write, the amount of data received is different from the amount that was indicated would be sent. (2) For LOB copy and loadfromfile, the end of the source LOB/FILE value was reached before the specified input amount was copied/loaded.

Cause: The source offset for a LOB COPY or LOB LOADFROMFILE is beyond the end of the source LOB.

Cause: TABLESPACE DEFAULT option can be specified for LOB columns only in the following contexts: - at the table level for a partitioned table - at the partition level for a composite partition. An attempt was made to use the TABLESPACE DEFAULT option in a different context.

Cause: An attempt was made to create or alter a LOB segment so that its NEXT extent size was less than the LOB chunksize

Cause: An attempt was made to specify a VARRAY|OPAQUE column to be stored as LOB at the partition/subpartition/template level. However the VARRAY|OPAQUE column was not specified to be stored as LOB at the table level when the table was created.

Cause: A CLOB or NCLOB in a fixed-width or varying-width multibyte character set was passed to a SQL character function which does not support multibyte LOB data.

Cause: CLOB or NCLOB contains invalid character data. One possible cause is that the wrong csid was specified for the external file when calling DBMS_LOB.LOADCLOBFROMFILE or DBMS_XSLPROCESSOR.READ2CLOB to load CLOB or NCLOB data from external files.

Cause: ALTER TABLE RENAME COLUMN/CONSTRAINT operation was given in conjunction with another ALTER TBALE Operation. This is not allowed.

Cause: Tried to rename a column of a non-base table, like object table/ nested table/ materialized view table.

Cause: The given constraint name does not exist.

Cause: The column participates in a join index.

Cause: The stored procedure 'raise_system_error' was called which causes this error to be generated.

Cause: Replication catalog determined deferred RPC destinations were mixed with destination determined by other mechanisms in the same transaction.

Cause: An application declared a communication failure during a defered RPC.

Cause: An application declared a generic failure during a defered RPC.

Cause: A deferred RPC call was issued without the correct number of arguments as determined by the count parameter to dbms_defer.call

Cause: An internal error occurred in deferred rpc.

Cause: The schema name was null or misspelled, or the schema does not exist locally.

Cause: The given database already replicates the given schema.

Cause: The given name was null or misspelled, the given type was wrong, the object does not exist as a valid database object, or the object does not exist as a replicated object with the appropriate status.

Cause: An object in the same namespace exists, perhaps with a different type or shape, or the same object has already been registered as an repobject in another object group.

Cause: The requested operation requires the object group to be suspended.

Cause: The group name is null, the group name is misspelled, the invocation or given database is not the masterdef, or one of the masters does not believe the invocation database is the masterdef.

Cause: The group name is null, the group name is misspelled, the invocation database is not a master, or the invocation database does not believe the given database is a master.

Cause: The invocation database is not a materialized view database for the given object group.

Cause: Either incompatible repcat versions are used, or a repcatlog record has been corrupted.

Cause: The requested operation is not permitted on a masterdef site.

Cause: The remote database is inaccessible.

Cause: User-supplied or system-generated ddl did not execute successfully.

Cause: The given value of a parameter is either null, misspelled, or not supported.

Cause: A missing ddl record for a repcatlog record, or inconsistency in repcat views.

Cause: You called dbms_pipe with a null pipe name.

Cause: You either tried to create a pipe that already existed and belonged to someone else, or remove a pipe that you were not authorized to use, or put a message into a pipe that you were not authorized for, or get a message from a pipe that you were not authorized for.

Cause: A deferred rpc parameter was longer than the deferred rpc limits of 4000 bytes for char/varchar2 parameters and 2000 bytes for raw parameters.

Cause: The given error was encountered while attempting to create a deferor entry for the give error code and the give database.

Cause: A conflict resolution priority function was given a type different than the type assigned to the priority group; or the priority group has no type assigned or a function; or dbms_defer_sys_query was called to retrieve a deferred rpc parameter from the deferred rpc queue, but the type of the parameter does not match the return type of the function.

Cause: Either suspend_master_activity has been called before the object group has resumed normal operation or a (deferred) rpc operation was attempted while the object group was quiesced.

Cause: Deferred rpc queues were imported from a database with a different global name or operating system than importing database.

Cause: When creating a materialized view through repcat, the materialized view base table name did not match a replicated table name at the master.

Cause: The DDL provided by the user to create a materialized view was executed without error, but materialized view does not exist.

Cause: The column group was already registered in the object group.

Cause: The given column group is either null, misspelled or not registered.

Cause: The given column group or priority group is being used to resolve conflicts.

Cause: Attempted to add a column to a column group when the column was already a member of a column group.

Cause: The given column is either null, misspelled or is not part of the given table or column group.

Cause: The priority group was already registered in the object group.

Cause: The priority group was already registered in the object group.

Cause: The specified value or priority has not been registered as part of the priority group.

Cause: The specified value or priority has already been registered as part of the priority group.

Cause: The specified combination of column group, sequence, conflict type and/or parameter table name, parameter column name, and parameter sequence number has already been registered.

Cause: User function is specified when conflict resolution method was not "USER FUNCTION" or specified resolution method is not one of the predefined methods.

Cause: A NULL user function was specified for the "USER FUNCTION" method.

Cause: The parameter column name is null or misspelled, the invocation database is not a master, or is of the wrong type for the specified conflict resolution method.

Cause: The specified combination of column group, sequence, conflict type has not been registered (e.g., for adding a comment).

Cause: A null, misspelled or nonexistent constraint was specified when registering a uniqueness conflict.

Cause: A procedure that deals with conflict resolution statistics-gathering was called for a table that was not registered to collect statistics.

Cause: Trying to generate replication support for a table or materialized view without a primary key (as defined by a constraint or dbms_repcat.set_columns) or an object ID.

Cause: The table has a column whose datatype is not supported by repcat.

Cause: Trying to generate replication support for a package that has a procedure with OUT or IN OUT parameters.

Cause: Trying to generate replication support for a package that has a public function, or for a stand-alone function.

Cause: This usually occurs when trying to resolve conflicts in a table while concurrent updates to the same row create more conflicts.

Cause: The procedure has a parameter whose datatype is not supported by repcat.

Cause: A duplicate destination was specified for a deferred transaction either in a dbms_defer.call call or an earlier dbms_defer.transaction call or a dbms_defer_sys.add_default_dest call.

Cause: The requested action cannot be performed until the queue is empty for the given object group

Cause: Deferred RPC can not be executed at the destination with the specified catchup value because their propogation has been disabled.

Cause: The given name was null or misspelled, the given type was wrong, the object does not exist as a valid database object at the master site, or the object does not exist as a replicated object with the appropriate status.

Cause: Possibly drop_master_repgroup was run at a master site but remove_master_databases was not run at master definition site for that master.

Cause: The propagator does not exist.

Cause: The local user does not match the remote user connected via a database link.

Cause: The userid in the repcatlog record does not match the userid of the connected user.

Cause: Trying to create more than one materialized view on a given master table in the same rep group.

Cause: The materialized view does not exist at the master site for offline instantiation of the materialized view.

Cause: The given user does not exist.

Cause: The name of the base table of the materialized view at the master site is different from the base table at the materialized view site. This error may arise during offline instantiation of materialized views.

Cause: The Advanced Replication feature is not enabled at this site. Updatable materialized views, deferred RPCs, and other replication features are, therefore, unavailable.

Cause: site specified in argument "reference_site" or argument "comparison_site" in call to "differences()" routine or "rectify()" routine does not name an existing site.

Cause: Value of argument "max_missing" to routine "differences()" cannot be less than 1. Value of argument "commit_rows" to routines "differences()" and "rectify()" cannot be less than 1.

Cause: Table specified in argument "oname1" or "oname2" in call to "differences()" routine does not contain either a primary key or a virtual primary key (defined through dbms_repcat package under symmetric replication).

Cause: Argument "sname1," "sname2," "oname1," "oname2," "missing_rows_sname," "missing_rows_oname1," "missing_rows_oname2" to "differences()" or "rectify()" cannot be NULL or '' (empty string).

Cause: Argument "max_missing" to "differences()" routine cannot be NULL.

Cause: The tables specified are not shape equivalent, which means intuitively that the number of columns, the names, their datatypes and lengths are not the same. Specifically, problem is in the parentheses and is one of the following: the number of columns are not equal, datatypes of columns with same name in different tables are different, lengths of varchar2 and char columns are not equal, precision and scale of number datatypes are not equal.

Cause: Some column in "array_columns" argument (or "column_list" argument) to "differences()" routine does not correspond to a column in the specified table.

Cause: Certain types in the table comparison utility are not supported.

Cause: The group name was null or misspelled, or the group does not exist locally.

Cause: The given database already replicates the given object group. A materialized view repgroup cannot be created at a given site where a master repgroup with the same name already exists.

Cause: A feature not compatible with the specified database was used

Cause: A feature not compatible with the remote database was used

Cause: An attempt was made to use the name of the reference site table as the name of the missing_rows_oname1 argument.

Cause: The connection qualifier used in the database link for the specified object group does not match the qualifier specified for the group in create_master_repgroup.

Cause: The maximum length of a database link, including the connection qualifier, is 128 bytes.

Cause: The specified propagation may be misspelled, or is not supported. For materialized view sites, all materialized view object groups at the same materialized view site with the same master object group must all have the same propagation method.

Cause: The system generated object(s) for the specified base object do not exist at the specified site. The current operation requires the base object to have generated replication support.

Cause: The materialized view repgroup is not currently registered at the master and so cannot be unregistered.

Cause: Insertion into local repschema table failed.

Cause: Specified numeric argument to dbms_defer_sys.push is invalid.

Cause: Specified string argument to dbms_defer_sys.push is invalid.

Cause: An error was occurred while creating slave processes for parallel push.

Cause: An attempt to dequeue a deferred transaction failed while trying to assign a new queue batch number.

Cause: An error occurred during parallel push while trying to update the high-water-mark information in system.def$_destination.

Cause: dbms_repcat.switch_mview_master is no longer supported.

Cause: Could not find materialized view associated with a trigger or index that is being pulled from the master site.

Cause: The given user is already the current propagator.

Cause: More than one valid propagator exist.

Cause: The given name was null or misspelled, the given type was wrong, the object does not exist as a valid database object, or the object does not exist as a replicated object with the appropriate status.

Cause: the database link does not exist in the schema of the replication propagator or has not been scheduled.

Cause: the database link name at the local node does not match the global name of the database that the link accesses.

Cause: the user name of the replication administration user at the local node and the user name at the node corresponding to the database link are not the same. Symmetric replication expects the two users to be the same.

Cause: Replication support for the specified object has not been generated or the generation process is not yet complete.

Cause: A null, misspelled, or badly formed materialized view name was given to dbms_mview.refresh.

Cause: A materialized view name was given to dbms_mview.refresh that is not in sys.snap$ or its associated views.

Cause: There are outstanding conflicts logged in the DefError table at the materialized view's master.

Cause: Making a new refresh group when there is already a group of the same name in sys.rgroup$.

Cause: A refresh group name was given that is not in sys.rgroup$.

Cause: A refresh group number was given that is not in sys.rgroup$.

Cause: The caller is not the owner of the materialized view and does not have ALTER ANY MATERIALIZED VIEW privileges.

Cause: The object name (e.g., the rollback segment, the materialized view name, the refresh group) was incorrectly specified.

Cause: operation is not supported if the object group is replicated at a pre-V8 node.

Cause: 1000 consecutive refresh group numbers, as defined by the rgroupseq number, were already used by rows in sys.rgroup$.

Cause: A materialized view of the same name is already in a refresh group.

Cause: The specified materialized view is not in the specified refresh group.

Cause: The master table's primary key constraint was modified after the primary key materialized view was created.

Cause: The fast refresh can not be performed because the master table does not contain a materialized view log.

Cause: A rowid materialized view is being fast refreshed, but the materialized view log does not record rowid information.

Cause: A primary key materialized view is being fast refreshed, but the materialized view log does not record primary key information.

Cause: The master table does not constaint a primary key constraint or the primary key constraint has been disabled.

Cause: A fast refresh is being performed on a materialized view of an unknown or unsupported type.

Cause: The propagator is currently used in propagating replication RPCs.

Cause: There are tables in the object group that require regeneration of replication support.

Cause: The parameter "interval" evaluates to a time earlier than SYSDATE.

Cause: There is no job visible to the caller with the given job number.

Cause: Oracle Server could not generate a job number that was not used to identify another job.

Cause: The given job number is less than 1.

Cause: The specified materialized view has not be successfully registered at this site.

Cause: The argument provided to dbms_mview.purge_mview_from_log is an invalid materialized view identifer or it does not identify an Oracle 8 fast refreshable materialized view or the materialized view has been already purged.

Cause: The requested action cannot be performed until the queue is empty for the given site/dblink

Cause: Specified numeric argument to dbms_defer_sys.purge_queue is invalid.

Cause: A job is associated with an instance that is not running.

Cause: The caller has provided an argument whose value cannot be NULL or the empty string.

Cause: The routine was executed against a replicated object group that was in the wrong state.

Cause: An attempt was made to instantiate a replicated object group at a master site that was already a part of the object group.

Cause: An attempt was made to execute the routine at a site that is different from the site specified in the argument of the routine.

Cause: The site name given as an argument to a routine was not already known to the replicated object group.

Cause: The propagation of LOB data from materialized view sites to the master site requires a primary key on the replicated table. Thus updatable ROWID materialized views that contain LOB columns are not supported.

Cause: The specified template authorization does not exist.

Cause: The specified user already has been authorized to use the specified refresh group template.

Cause: The specified refresh group template does not exist.

Cause: The specified refresh group template already exists.

Cause: The public template parameter is not 'Y', 'N' or NULL.

Cause: The specified object does not exist in the refresh group template.

Cause: The specified object already exists in the refresh group template.

Cause: The specified template parameter does not exist.

Cause: The template parameter already exists for the specified refresh group template.

Cause: The template site specified by the site name, user name and refresh group template name does not exist.

Cause: The template site specified by the site name, user name and refresh group template name already exists.

Cause: The user parameter value specified by the user name, parameter name and refresh group template name does not exist.

Cause: The user parameter value specified by the user name, parameter name and refresh group template name already exists.

Cause: The user specified by the user name parameter does not exist in the database.

Cause: The flavor already contains the specified object.

Cause: The given object group already contains a (possibly unpublished) definition of the specified flavor.

Cause: The given object group already contains a (published) definition of the specified flavor.

Cause: The TOP flavor has a NULL name and may not be directly defined or deleted.

Cause: The given object group does not contain a (published) definition of the specified flavor.

Cause: The given flavor contains the object to be dropped.

Cause: The flavor does not contain the given object, column, or attribute.

Cause: The given flavor ID is invalid.

Cause: The given flavor at the given database prevents the operation from succeeding.

Cause: The flavor must contain the given object, column, or attribute.

Cause: before resolving conflicts, some values necessary resolving conflicts are not available, or after resolving conflicts, some values necessary for re-trying of the SQL are not available

Cause: The given flavor cannot be deleted because it is being used at the given site.

Cause: An existing flavor includes the specified object with an incompatible type.

Cause: The flavor includes some columns of an object group but not all the required columns.

Cause: The flavor includes the specified column which is being added.

Cause: The flavor includes the specified object which does not exist

Cause: The flavor does not include the specified object which is being dropped.

Cause: The template is missing the object with the specified key.

Cause: The values for the specified columns are different in each template for the same key values.

Cause: The status should be DELETED, INSTALLING or INSTALLED. Any other status is invalid.

Cause: The refresh template is private and the user has not been authorized to instantiate the template.

Cause: Non-atomic refresh is not supported for the specified materialized view.

Cause: The processing of replication RPCs for the object group that contains this object is disabled. This includes RPCs in the error queue.

Cause: The current columns in the specified table and their column types do not match the columns and column types when replication support was last generated.

Cause: The specified column is a key column and must be sent and compared during replication propagation.

Cause: This object was imported from a database with a different global name than the importing database.

Cause: The propagation method of a materialized view object group can only be altered when no other object groups with the same master object group are sharing the materialized view site.

Cause: There is at least one other materialized view repgroup at the local site with the same group name but a different master site.

Cause: The column is either not a top-level column or is not present in the table or materialized view.

Cause: The column is of Object Type.

Cause: The specified operation does not support the given object.

Cause: An internal error occurred in internet Application Server.

Cause: The column group doesn't contain only one numeric column.

Cause: The specified two object groups do not have the same connection qualifier.

Cause: This operation does not support the specified dblink in the above propagation mode.

Cause: The specified value is duplicated in the parameter list.

Cause: The specified operation is not allowed for the extension request with the specified status.

Cause: The specified database does not have a valid extension request.

Cause: There is no new site with the specified extension request.

Cause: The specified extension request does not include the specified site as a new site.

Cause: The specified destination has too many rows in system.def$_destination table.

Cause: The sites involved may be in the process of adding a new site without quiescing.

Cause: The disabled status for this site is set internally for synchronization during adding a new master without quiescing.

Cause: The array of Repgroup names contains a null value.

Cause: The Repgroup names specified do not have the same masters.

Cause: An attempt was made to switch master for a materialized view repgroup when its parent repgroup is also a materialized view repgroup. This is not allowed.

Cause: Instantiation of a refresh template is not supported for database compatibility 8.0 or less.

Cause: An attempt was made to offline instantiate to a directory which is not specified or null.

Cause: An attempt was made to instantiate a IAS site. Error occurred during IAS instantiation.

Cause: The list of columns passed as a parameter does not match the columns to be added to the table.

Cause: The specified object does not exist.

Cause: The arguments passed to the online redefinition API were invalid or missing.

Cause: An attempt was made to drop a tablespace which contains materialized views and/or their indices.

Cause: Site owner for the template already exists.

Cause: Tables belonging to the same replication group were specified to be cached with different synchronization mechanisms.

Cause: An attempt was made to cache an object which is not supported.

Cause: After import, the materialized view container table has missing columns.

Cause: An attempt was made to set a new non-null back end database for an iAS site.

Cause: The object may have been dropped or renamed at the back end after dbms_ias_inst.start_ias_inst was executed.

Cause: This function or procedure is restricted to the backend or middle tier site

Cause: An attempt was made to explicitly refresh a NEVER REFRESH MV.

Cause: An attempt was made to redefine a table which is currently involved in an ongoing redefinition.

Cause: An attempt was made to continue or complete a redefinition which was not defined or initiated.

Cause: An attempt was made to continue or complete a redefinition by providing different tables than those used while defining or initiating the redefinition.

Cause: An attempt was made to register an already registered dependent object to an ongoing redefinition.

Cause: There was an error while creating the materialized view log and the log is currently in an inconsistent state. A possible cause could be that schema redefinition has occurred on the master table while the log was being created. Another possible cause could be that there were DMLs being applied on the master table concurrently in another session at the time the materialized view log creation started and those DML transactions haven't committed even after a very long period of time.

Cause: The online partition mover could not create a rowid mappping table.

Cause: The value for dml_lock_timeout was out of the permitted range of 0 to 1,000,000.

Cause: An attempt was made to redefine a table which is currently involved in reference partitioning.

Cause: An attempt was made to redefine a table where the interim table has identity columns that appear in column mapping.

Cause: An attempt was made to update primary key columns of an index-organized table.

Cause: An attempt was made to redefine a table that has interval partitioning with ILM policy defined on it.

Cause: Synonym mismatch occurred during the import of materialized views when REMAP_SCHEMA option was specified.

Cause: An attempt was made to alter the contents of a staging log table.

Cause: The propagate_name already exists.

Cause: Propagation does not exist.

Cause: Specified GoldenGate, XStream or Streams process type is not valid.

Cause: An attempt to enqueue a GoldenGate, XStream or Streams message was aborted because ORACLE is running low on memory allotted.

Cause: An attempt was made to specify an invalid parameter value.

Cause: An attempt was made to specify an invalid object.

Cause: An invalid column was specified in the column list.

Cause: An invalid column was specified as the resolution column. The resolution column must belong to the list of columns specified in the 'column_list' parameter.

Cause: There was no entry in ALL_DIRECTORIES corresponding to the specified directory.

Cause: Streams detected an erroneous result.

Cause: The specified tablespace had more than one data file and hence did not qualify as a simple tablespace.

Cause: Either the tablespace did not exist, or the current user did not have sufficient privileges on the tablespace.

Cause: A script for the specified invoking package already existed.

Cause: The named script did not exist.

Cause: The specified block number did not exist for the script.

Cause: The execution of specified block failed.

Cause: The specified block was already executed.

Cause: Script generation for the specified script was not completed in a prior invocation.

Cause: A non-Oracle database has returned an error message to STREAMS when attempting to apply a DML statement. The non-Oracle system error message is a parameter to this Oracle error.

Cause: In a PL/SQL CALL to a stored procedure, the bind string size exceeded 4K.

Cause: The script was already being run in a different session or was terminated before status for the script was updated to ERROR or EXECUTED.

Cause: An attempt was made to execute a procedure which was being executed in a parallel session or failed execution.

Cause: DBMS_COMPARISON detected an erroneous result.

Cause: Another session was already performing an operation on this object.

Cause: Table shapes of local and remote tables to compare did not match.

Cause: Table did not have an eligible index to use for comparison.

Cause: A comparison object by the specified name already exists.

Cause: A generated query for comparison was too long.

Cause: The specified index was not an eligible index to use for comparison.

Cause: Could not switch to apply-state checkpoint mode, or already in apply-state checkpoint mode.

Cause: Could not switch to checkpoints because apply-state checkpoint mode was set.

Cause: The capture process was in apply-state checkpoint mode.

Cause: The capture was running in apply-state checkpoint mode and had to run in combined capture and apply mode also.

Cause: The capture process was in apply-state checkpoint mode.

Cause: The tablespaces were already in existence in the target database when the streams MAINTAIN_TTS APIs were called."

Cause: The tablespace name was either NULL or too long when the streams MAINTAIN_TTS APIs were called.

Cause: Capture was cloned from a capture in apply-state checkpoint mode.

Cause: Switch to apply-state checkpoint mode was prevented by a previous error.

Cause: Switch to checkpoints was prevented by a previous error.

Cause: Capture or Apply did not exist.

Cause: Capture or Apply were not running.

Cause: Capture was for Change Data Capture, and checkpoints were required.

Cause: Capture was for Audit Vault, and checkpoints were required.

Cause: Capture was not capturing changes.

Cause: Capture was already in the desired mode.

Cause: The oldest SCN was not updated before the switch was performed.

Cause: LogMiner session did not exist.

Cause: The new value for the oldest SCN was not computed correctly.

Cause: The function was invoked with a negative SCN range.

Cause: The GoldenGate, XStream or Streams process could not be stopped or started.

Cause: The converted file was already in existence. CONVERT FILE call does not overwrite the existing file.

Cause: The conversion between two character sets for the column in the given table is not supported.

Cause: The conversion between two character sets failed because a source column value is too large for the destination column.

Cause: It may be caused by invalid NLS environment setting.

Cause: There's no such capture process

Cause: The length of an insert, update, or delete subset rule computed from the DML condition input exceeded the maximum allowed length.

Cause: The view was based either on another view or multiple tables or views.

Cause: The view was based either on another view or multiple tables or views.

Cause: The DML conflict handler was not found for modification or removal.

Cause: A default column group was found for the specified Apply name, operation name, and conflict type.

Cause: The column was already in the column group of another conflict handler for the specified Apply name, operation name, and conflict type.

Cause: The specified column did not have a numeric data type. Delta conflict resolution requires numeric columns.

Cause: A DML conflict handler with the specified name was found.

Cause: The specified value was duplicated in the column group list.

Cause: A default column group was not specified. The specified Apply name, operation name, and conflict type is only supported on default column groups.

Cause: The specified table contained a column that was not specified as part of a column group.

Cause: The specified resolution column was not valid.

Cause: The specified table or the LCR contained a null value in one of the columns belonging to a delta conflict group.

Cause: The specified OPERATION_NAME, CONFLICT_TYPE, and METHOD_NAME was not a valid set of parameters.

Cause: The local table did not have an eligible index to use for comparison.

Cause: The remote table did not have an eligible index to use for comparison.

Cause: The specified index was not eligible for comparison.

Cause: The specified index was not eligible for comparison.

Cause: An invalid value was specified for the paramerter.

Cause: The queue table already exists in the queueing system.

Cause: Queue_table not exist.

Cause: The queue table index has not yet been successfully imported.

Cause: Invalid column name was specified in the SORT_LIST.

Cause: An attempt was made to use the SQL command DROP TABLE or TRUNCATE TABLE or ALTER TABLE on queue metadata or tables.

Cause: The queue requested to be created already exists.

Cause: An invalid value was specified for MAX_RETRIES.

Cause: An error was detected when dropping a queue table in a cluster, tablespace, or schema.

Cause: Invalid queue type parameter

Cause: The specified queue does not exist.

Cause: The queue has not been stopped i.e. either enqueue or dequeue is still enabled.

Cause: A queue exists in the queue table which has not been dropped. All queues need to be dropped first.

Cause: A negative value was specified for RETRY_DELAY.

Cause: Queue retention was specified, but the retention time was specified to be less than zero.

Cause: An invalid QUEUE_PAYLOAD_TYPE specified during create_queue_table.

Cause: An invalid object type specified for QUEUE_PAYLOAD_TYPE during create_queue_table.

Cause: User tried to enable enqueueing to an exception queue.

Cause: There were outstanding transactions on the queue, and WAIT was set to false, so STOP_QUEUE was unsucessful in stopping the queue.

Cause: The identifier specified is too long.

Cause: Internal Error occured in the package DBMS_AQ_IMPORT_INTERNAL.

Cause: The queue definition is not updated because the queue table was not imported properly

Cause: The parameter combination will not cause the queue to be started or stoped.

Cause: Internal Error occured in the package DBMS_AQ_EXP_INTERNAL.

Cause: Internal Error occured in the package DBMS_AQ_IMP_INTERNAL.

Cause: Parameter queue_payload_type has invalid value.

Cause: An attempt was made to enqueue, dequeue or administer a queue which has errors.

Cause: AQ propagation's HTTP request to the propagation servlet at the specified address encountered an error

Cause: Tried to create a reciever non-repudiable single consumer queue

Cause: Tried an operation not allowed on a single-consumer queue.

Cause: Specified both a rule and rule-set for the operation.

Cause: Parameter is NULL.

Cause: Oracle AQ tried to create an index with the name specified in the error message. The index could not be created for the specified queue table because a object exists with the same name.

Cause: An enqueue was performed on a queue that has been set up for multiple dequeuers but there were neither explicit recipients specified in the call nor were any queue subscribers determined to be recipients for this message.

Cause: An application name that was already a subscriber for the queue was specified in the dbms_aq.subscribe call.

Cause: An AQ agent that was not a subscriber for the queue was specified.

Cause: The create queue table command was issued with message_grouping set to TRANSACTIONAL and a sort order column other than priority. Only the priority column can be specified in the sort order for queue tables with transactional grouping.

Cause: The schema specified in the QUEUE_NAME parameter of CREATE_QUEUE is not the same as the schema specified in the QUEUE_TABLE parameter.

Cause: The CREATE_QUEUE or ALTER_QUEUE command was issued with a non-zero RETRY_DELAY and a QUEUE_TABLE that was created for multiple consumers and with COMPATIBLE parameter set to '8.0'.

Cause: Either an ADD_SUBSCRIBER, ALTER_SUBSCRIBER, or REMOVE_SUBSCRIBER procedure, or an ENQUEUE with a non-empty recipient list, was issued on a queue that was not created for multiple consumers.

Cause: A SCHEDULE_PROPAGATION was issued for a queue and destination pair which has an existing propagation schedule.

Cause: AN UNSCHEDULE_PROPAGATION was issued for a queue and destination pair which has no existing propagation schedule.

Cause: An attempt was made to specify a reserved name for a destination.

Cause: A message recipient's queue has a different object structure than the sender's queue. The message cannot be propagated.

Cause: An invalid value was specified for the agent address parameter.

Cause: The protocol attribute of the AQ agent object type is reserved for future use.

Cause: An invalid value was specified for the agent name parameter.

Cause: An attempt was made to issue the CREATE_QUEUE_TABLE command, but the user who issued the command does not have access to internal AQ object types.

Cause: An attempt was made to use a reserved prefix in the agent name.

Cause: An ADD_SUBSCRIBER, ALTER_SUBSCRIBER, or REMOVE_SUBSCRIBER procedure was issued on a queue that was created as an EXCEPTION_QUEUE.

Cause: An ADD_SUBSCRIBER or ENQUEUE procedure with a non-NULL address field in the agent type was issued on a queue whose payload has a REF attribute. Propagation of object type payloads that have a REF attribute currently is not supported.

Cause: The recipient of a message with LOB attributes was using an Oracle 8.0 release. Propagation of LOB attributes is supported only in Oracle 8.1 and higher releases.

Cause: One of PRIMARY_INSTANCE or SECONDARY_INSTANCE was negative.

Cause: The recipient of a message was using an Oracle 8.0.3 release or lower release. Propagation is supported only in Oracle 8.0.4 and higher releases.

Cause: An attempt was made to use the internal administration procedure to delete status rows from the SYS.AQ$_PROPAGATION_STATUS table that were in the prepared state.

Cause: The sequence numbers used in the SYS.AQ$_PROPAGATION_STATUS table were inconsistent for the given queue and destination.

Cause: An ADD_SUBSCRIBER or ALTER_SUBSCRIBER procedure with a rule was issued on a queue for which rule based subscribers are not supported. Rule based subscribers currently are supported only for NORMAL (persistent) multi-consumer queues created using an Oracle release 8.1.0 or higher compatible queue table.

Cause: An attempt was made to downgrade the queue table when there were messages being propagated that were in the prepared state.

Cause: An invalid compatible parameter was specified in the DBMS_AQADM procedure. The parameter setting must be of the form '8.x.y' where x is the release number and y is the update number.

Cause: The source queue table in the DBMS_AQADM procedure is compatible with the specified COMPATIBLE parameter setting.

Cause: A non-zero value was specified for SECONDARY_INSTANCE when PRIMARY_INSTANCE was zero.

Cause: The subscriber table has not yet been successfully imported.

Cause: An attempt was made to downgrade the queue table when there were queues on which rule based subscribers are defined.

Cause: An ENABLE_SCHEDULE_PROPAGATION command was issued for a queue and destination pair whose propagation schedule already was enabled.

Cause: A DISABLE_SCHEDULE_PROPAGATION command was issued for a queue and destination pair whose propagation schedule already was disabled.

Cause: An invalid privilege is specified for granting or revoking privilege

Cause: An attempt was made to add new subscribers to the specified, but the number of subscribers for this queue has exceeded the maximum number (1024) of subscribers allowed per queue.

Cause: An attempt was made to start a queue in a queue table that is being migrated.

Cause: An attempt was made to downgrade a queue table, but a previous command to upgrade the queue table has not yet completed successfully.

Cause: An attempt was made to upgrade a queue table, but a previous command to downgrade the queue table has not yet completed succesfully.

Cause: An attempt was made to perform an operation on a queue in a queue table that is being migrated.

Cause: An attempt was made to upgrade or downgrade a queue table using the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure, but the user who executed the procedure does not own the queue.

Cause: An attempt was made to create or alter an exception queue by specifying a non-zero RETENTION_TIME.

Cause: The CREATE_QUEUE or ALTER_QUEUE command was issued with a non-zero RETRY_DELAY and an exception queue.

Cause: An ADD_SUBSCRIBER or enqueue was attemoted with an agent that had a NULL address and a non-NULL protocol.

Cause: One of the operations, SCHEDULE_PROPAGATION, ALTER_QUEUE, LISTEN, DEQUEUE was issued for a NON_PERSISTENT queue.

Cause: A SCHEDULE_PROPAGATION was issued for an EXCEPTION queue. Propagation schedules can be created only for NORMAL queues.

Cause: A non-NULL value was specified for SECONDARY_INSTANCE when PRIMARY_INSTANCE was NULL.

Cause: An attempt was made to use a reserved prefix for the object name.

Cause: A propagation administration command was issued for a queue and destination pair whose propagation is being unscheduled.

Cause: The compatible parameter was not high enough to allow the operation.

Cause: The snapshot process executing the propagation schedule did not respond to the disable propagation command.

Cause: An add_subscriber call with a non-null address field was issued on a queue which does not support remote subscribers. Remote subscribers are not supported for NON_PERSISTENT QUEUES.

Cause: Advanced Queuing requires that the agent's dblink name should be unique within the first 24 bytes (for 8.0 compatible queuetables)

Cause: An attempt was made to enqueue, dequeue or administer a queue which is invalid. This could have occured because the payload type of the queue's queue table was dropped or rules associated with queue subscribers got altered or dropped.

Cause: An attempt was made to create a 8.0 compatible queue table and enable a feature that is supported only on 8.1 style queue tables

Cause: An invalid database username was specified

Cause: This AQ Agent does not exist

Cause: This AQ agent has already been created

Cause: No protocol was enabled for aq agent

Cause: Propagation cannot be scheduled when the destination queue is the same as the source queue.

Cause: A queue, queue table, rule, or ruleset name that requires double quotes was specifed when the database compatibility was less than 10.0.

Cause: The specified AQ agent does not have privileges of the specified database user

Cause: The target type of the transformation specified was different from the type of the queue.

Cause: The source type of the transformation specified was different from the type of the queue.

Cause: Invalid value is specified for message state

Cause: A negative value or NULL was specified for the parameter.

Cause: An Invalid value or NULL was specified for the parameter.

Cause: The specified operation is only supported for queues with compatibility 8.1 or greater

Cause: There is an error in the Transaction layer test ICDs

Cause: One of the arguments of the requested operation contained a list of scheduler objects. While processing this list an error was encountered with the specified item.

Cause: generate_job_name was called with a prefix longer than 18 characters or a prefix ending in a digit.

Cause: The job failed to be enabled after creation.

Cause: An invalid parameter was passed to the specified DBMS_REPAIR procedure.

Cause: Both cascade and a block range were specified in a call to DBMS_REPAIR.CHECK_OBJECT.

Cause: An incorrect block range was specified.

Cause: An attempt was made to use the specified feature, but the feature is not yet implemented.

Cause: An invalid ACTION parameter was specified.

Cause: An attempt was made to fix corrupt blocks on an object that has been dropped or truncated since DBMS_REPAIR.CHECK_OBJECT was run.

Cause: CASCADE_FLAG was specified for an object that is not a table.

Cause: The TABLESPACE parameter can only be used with CREATE_ACTION.

Cause: A partition name was specified for an object that is not partitioned.

Cause: An attempt was made to pass a table name parameter without the specified prefix.

Cause: An attempt was made to specify a map, repair, or sync table that does not exist.

Cause: An attempt was made to specify a map, repair, or sync table that does not have a correct definition.

Cause: An attempt was made to specify a table name is greater than 30 characters long"

Cause: An attempt was made to specify a Global Temporary Table (GTT) table name while using DBMS_REPAIR.CHECK_OBJECT.

Cause: An attempt to access or modify a ruleset was made, which failed because the ruleset does not exist.

Cause: An attempt to create a ruleset with an invalid name was made. The ruleset name can not be NULL, and can not be more than 26 characters, unless a rules_table_name is also specified, in which case the ruleset name may be up to 30 characters.

Cause: An attempt to create a rule/ruleset on an invalid evaluation name was made. The evaluation_context can not be more than 30 characters. The evaluation context with the name specified must exist.

Cause: An internal error occurred in the rules engine. This indicates that the rules engine has encountered an exception condition.

Cause: An evaluation context of the given name already exists

Cause: A rule of the given name already exists

Cause: The rule of the given name does not exist

Cause: The rule still belongs to some rulesets, cannot be dropped

Cause: An attempt to create a rule with an invalid name was made. The rule name can not be NULL, and can not be more than 30 characters

Cause: The evaluation context of the given name does not exist

Cause: Whening adding a rule to a rule set, either the rule or the rule set must have an evaluation context associated with it

Cause: The evaluation context still belongs to some rules or rule sets, cannot be dropped

Cause: A rule set of the given name already exists

Cause: a rule can be added to a rule set only once

Cause: the rule to be removed from the rule set is not in the rule set

Cause: there is a table alias of the same name in the evaluation context

Cause: there is a variable of the same name in the evaluation context

Cause: table alias name or base table name is not specified in the table alias definiton

Cause: variable name or variable type is not specified in the variable definiton

Cause: there is already a name-value pair with the same name in the NVlist

Cause: there is not such a name-value pair in the NVlist

Cause: The NVList is full (1024 elements) and cannot hold more elements

Cause: the object name has a database link in it, which is not supported

Cause: no such system privilege number for rule engine objects

Cause: no such object privilege number for rule engine objects

Cause: The table aliases and the variable types specified in the evaluation context could not be resolved.

Cause: there are rule engine objects in the database that cannot be downgraded.

Cause: If a rule is added to a rule set with more than one evaluation contexts, it must not have an evaluation context itself.

Cause: The rule references variables not in the evaluation context.

Cause: This object is created by AQ, thus cannot be dropped directly

Cause: user specified not null creation properties when creating rules engine objects, which are not for external use

Cause: The rule references variables not in the evaluation context.

Cause: user specified nested query in rule condition.

Cause: Number of tables or variables were more than the defined upper limit.

Cause: Upper limit of tables or variable per evaluation context exceeded as there exists at least one nonsimple rule condition.

Cause: The transformation expression does not evaluate to the target type or the target type's specified attribute.

Cause: The source or destination type for the transformation does not exist

Cause: The target type of the transformation does not have the attribute number specified in the ADD_ATTRIBUTE_TRANSFORMATION command

Cause: The transformation specified is invalid because the source or the target type have been dropped/modified.

Cause: The named transformation already exists.

Cause: The specified transformation does not exist.

Cause: The object type of the message to be transformed does not match the source type of the specified transfomation.

Cause: the length of payload being taken exceeds the limit of varchar2 or raw.

Cause: the property name being set has existed.

Cause: the property name cannot be null.

Cause: the property valus being set exceeds the valid range.

Cause: According to JMS specification, some type conversions were not allowed.

Cause: The GET_NAMES function returns the names in a varray with a size limit of 1024.

Cause: StreamMessage and BytesMessage could not be read when they were in write only mode and vice versa.

Cause: The JAVA stored procedure threw some exceptions that could not be catergorized.

Cause: An attempt was made to use an invalid operation ID to access messages.

Cause: An attemp was made to access too many messages at the same time.

Cause: Attempted to add a publisher to the queue again.

Cause: Attempted to alter or drop a non existent publisher from a queue.

Cause: An operation attempt was made to a queue table which has errors.

Cause: A propagation administrative interface was called when the existing propagation schedules were running in different mode (10.2/11g).

Cause: An attempt was made to use a feature that is not supported for sharded queues.

Cause: An attempt to add a new nondurable subscriber to the queue failed because the number of nondurable subscribers has exceeded the maximum limit.

Cause: An attempt to add a new nondurable subscriber on the specified queue was aborted because of memory constraints.

Cause: An attempt was made to use a sharded queue API on a non-sharded queue.

Cause: An attempt was made to create a nondurable subscriber with a rule condition, but the condition had compilation errors.

Cause: An attempt was made to start or stop a queue operation on a queue which is already enabled or disabled for that operation.

Cause: There was an invalid setting of REPLICATION_MODE in the queue creation call.

Cause: An attempt was made to run a user operation on a replicated queue.

Cause: An attempt to replicate enqueue failed.

Cause: An attempt to replicate enqueue failed.

Cause: An attempt was made to modify REPLICATION_MODE on a queue open to user operations.

Cause: An attempt was made to create a sharded queue with an ADT type which was not supported in the queue_payload_type.

Cause: An Oracle Client application was linked with Oracle Java Message Service (JMS) libraries with version earlier than 19c.

Cause: The input supplied to DBMS_DDL.WRAP or DBMS_DDL.CREATE_WRAPPED did not specify a legal PL/SQL package specification, package body, type specification, type body, function or procedure. This error can occur if you used incorrect syntax in the CREATE OR REPLACE statement or specified a unit that cannot be wrapped (e.g., a trigger or anonymous block).

Cause: The specified Database Access Descriptor (DAD) did not exist.

Cause: The specified Embedded PL/SQL Gateway attribute was not known.

Cause: One or more input arguments to the DBMS_UTILITY.VALIDATE routine was not legal. This error occurred because the object name or owner or namespace arguments (if specified) were NULL or illegal.

Cause: The specified PL/SQL object in a DBMS_PREPROCESSOR subprogram did not exist or you did not have the privileges necessary to view its source.

Cause: The specified object type was not appropriate.

Cause: The input source text supplied to a DBMS_PREPROCESSOR subprogram was empty.

Cause: This error occurred because the p_object_id argument passed to the DBMS_UTILITY.INVALIDATE routine was NULL, there was no object with the specified object id, or the user calling the routine did not have sufficient privileges to invalidate the object.

Cause: This error occurred because the p_plsql_object_settings argument passed to the DBMS_UTILITY.INVALIDATE routine was NULL or malformed.

Cause: A call to the DBMS_UTILITY.INVALIDATE routine failed. This error occurred because the object type of the object specified by the p_object_id argument is not one of the types that can be handled by this routine. Alternately, the object was an object type specification with table dependents, or the object was the specification of the STANDARD, DBMS_STANDARD, DBMS_UTILITY package, or the body of the DBMS_UTILITY package.

Cause: The specified Database Access Descriptor (DAD) name was invalid.

Cause: The input source text supplied to a DBMS_PREPROCESSOR subprogram was in wrapped format.

Cause: An attempt to allow anonymous access through a dynamically authenticated Database Access Descriptor (DAD) was prohibited.

Cause: An access control entry (ACE) for the principal with the same grant or deny attribute in the IS_GRANT argument already existed.

Cause: The host or port to which the access control list (ACL) was assigned was invalid.

Cause: The network privilege being added to the access control list (ACL) was invalid.

Cause: An attempt was made to store an empty access control list (ACL).

Cause: No access control list (ACL) has been assigned to the target host or the privilege necessary to access the target host has not been granted to the user in the access control list.

Cause: XML DB extensible security necessary for this operation has not been installed.

Cause: An unsupported authentication scheme was used.

Cause: A supported authentication scheme was not found.

Cause: EXPAND_SQL_TEXT supports only SELECT statements.

Cause: An attempt was made to access a SQL translation profile that either did not exist or for which the current user did not have privileges on.

Cause: An attempt to translate a SQL statement or error code or to change a SQL or error code translation failed because the translation was not found.

Cause: An attempt to translate a SQL statement or error code failed because either a SQL translation profile was not set or the profile could not translate the given SQL syntax.

Cause: An attempt to register or use a translated SQL statement failed because the number or the order of bind variables were changed in the statement.

Cause: See the string parameter at the end of the message.

Cause: The database role was not a primary database or a physical standby database.

Cause: Either a file with the same name as the specified output file name already exists, or file creation failed.

Cause: Slave process or processes failed to operate properly for one of the following reasons: - Inadequate SGA size. - Slave pool could not be initialized. - Slave process or processes were abnormally terminated.

Cause: Remote database or databases were not available due to network connection failures.

Cause: The remote database was unable to read the data file.

Cause: The data file on the local database could not be accessed.

Cause: The server address on the public key certificate of the remote server did not match the address used to access the target server.

Cause: An attempt was made to access the data file outside of the current container.

Cause: A DDL operation was attempted on a SQL profile by a session without the proper privileges.

Cause: A call was made to create a new row in the specified table. A row already exists in the table with the specified values.

Cause: The translation type parameter is not a T, S or an M. A value other than T, S or M was specified.

Cause: The initialization value must be either F or T. A value other than F or T was specified.

Cause: If a translation type of T or S is specified, translation text must be supplied.

Cause: A call was made to update a row that does not exist or a foreign key value supplied to create a table does not exist.

Cause: The function <pkgname.funcname> was called with a parameter parmname that was null, 0 length, or had an invalid value.

Cause: The function <pkgname.funcname> computed a value for the output parmname that exceeded the maximum allowed. This can occur when multiple input parameters, each valid separately, combine to specify an invalid result. For example, when a length parameter multiplied by a copies parameter yields a total length exceeding the maximum for the output datatype.

Cause: The database link did not exist.

Cause: The table did not exist in the remote database.

Cause: The view was not created by CREATE_OR_REPLACE_VIEW API.