Cause: The parameter has been provided a negative, out of range, or NULL input value.

Cause: The value of positional or size parameters exceeded the maximum allowed LOB size of (4 Gigabytes - 1) * DB_BLOCK_SIZE.

Cause: A sorted hash cluster only supports a maximum of 2 tables

Cause: Sorted hash clusters have a maximum key size

Cause: Parameters or their values were specified incorrectly in the configuration file.

Cause: An undefined mode value was specified.

Cause: An HDA was not specified in the logon call while running in a thread safe environment.

Cause: An attempt was made to use the host connection while it was in use by another thread.

Cause: One of the calls that is supported in deferred mode linkage exclusively was invoked when the client was linked non-deferred.

Cause: Data of this datatype cannot be sent or fetched in pieces.

Cause: The call was executed on a cursor for which this is invalid.

Cause: A zero length buffer or a null buffer pointer was provided.

Cause: The length of the piece exceeded the maximum possible size.

Cause: Call to modify attributes was done for a non-existent position

Cause: This server handle is already attached to a server.

Cause: The connect string is null, but a length was specified for it.

Cause: Cannot initialize user memory.

Cause: An illegal size or null pointer was specified for user memory.

Cause: A user has already been authenticated on this service handle.

Cause: The server context does not done exist.

Cause: An illegal attribute type was specified for the handle.

Cause: An illegal handle type was specified.

Cause: A define was done with an existing handle on a different position.

Cause: This call is valid only for object types.

Cause: Process was unable to allocate memory to store diagnostics.

Cause: An attempt to initialize a mutex failed.

Cause: One of the three memory function pointers is null or non-null.

Cause: An attempt to delete an initialized mutex failed.

Cause: A null value or a bogus value was passed in for a mandatory parameter.

Cause: An attempt was made to use an improper service context handle.

Cause: An attempt was made to use a context handle outside its scope.

Cause: An attempt was made to pass an initialized handle.

Cause: A server context must be initialized before creating a session.

Cause: The attribute value passed in is illegal.

Cause: The character set identifier specifed is invalid

Cause: An internal OCI error has occurred.

Cause: The user buffer to contain the output data is too small.

Cause: An invalid object type is requested for the describe call.

Cause: An iteration count of zero was specified for the statement

Cause: The application is trying to get a descriptor from a handle for an illegal position.

Cause: The number of columns exceeds the maximum number supported.

Cause: The result set descriptor should have valid data fetched into it before it can be converted to a statement handle

Cause: A statement cannot be executed before making preparing a request.

Cause: A fetch or describe was attempted before executing a statement handle.

Cause: An attempt was made to set the server group in a server handle after connecting to the server. However, once the connection is established to a server, the server group name cannot be set anymore.

Cause: The number of columns exceeds maximum supported by the server.

Cause: OCI_ENV_NO_MUTEX mode was specified for a non-threaded client.

Cause: An attempt to destroy a mutex failed.

Cause: The only valid return value for a user defined callback function is OCI_CONTINUE or OCI_ROWCBK_DONE. Any other value will cause this error.

Cause: A sql/plsql compilation error occurred.

Cause: A truncation or a null fetch error"

Cause: None of the bind variables in the SQL statement are bound.

Cause: A null column was processed by an aggregate function

Cause: An update or delete was executed without where clause

Cause: One of the following occurred: -The attribute in OCIAttrGet was used incorrectly. -The version of the database used does not support this feature -There was an error in the array DML for all of the iterations.

Cause: OCI used is not permitted from external procedures.

Cause: A bad date was passed into one of the OCI calls.

Cause: A bad COBOL display type was passed into one of the OCI calls.

Cause: User supplied buffer for a COBOL display type was too small to accommodate fetched number.

Cause: The number fetched was beyond the range that can be displayed.

Cause: An attempt was made to convert a negative number into an unsigned display type.

Cause: An internal error was encountered during conversion to COBOL display type.

Cause: An internal error was encountered during conversion to OCIDate type.

Cause: OCIBindObject was not invoked resulting in an incomplete bind specification for a Object Type or Reference.

Cause: OCIDefineObject was not invoked resulting in an incomplete bind specification for a Object Type or Reference.

Cause: Type Descriptor Object is a mandatory parameter for Object Types Binds and Defines.

Cause: One of the basic bind calls was not invoked on this bind handle before performing an advanced bind call.

Cause: When the character count flag is set, then the maximum size of the buffer in the server should be specified as a non-zero value.

Cause: Measurements in characters instead of bytes are illegal if either the server's or client's character set is varying width.

Cause: An internal error has occurred while attempting to blank pad string data. This error should not occur normally.

Cause: This usually occurs during conversion of a multibyte character data when the source data is abnormally terminated in the middle of a multibyte character.

Cause: This occurs during user authentication, a migratable user handle has been set in the service handle.

Cause: This occurs during authentication of a migratable user. the service handle has not been set with non-migratable user handle.

Cause: This is an internal OCI error.

Cause: No callbacks have been registered for one or more of the bind handles which are part of the RETURNING clause.

Cause: Data of a certain datatype that does not support piecewise operation is being sent or fetched in pieces.

Cause: An internal OCI error has occurred.

Cause: The object to be described is not valid. It either has compilation or authorization errors.

Cause: The length specified for the statement is either 0 or too large.

Cause: The application did not define output variables for data being fetched before issuing a fetch call or invoking a fetch by specifying a non-zero row count in an execute call.

Cause: V6 syntax is no longer supported in V8 server.

Cause: A user callback registration or get was attempted on a handle which is not an environment handle.

Cause: An invalid function code was used.

Cause: An attempt was made to register a user callback for an OCI call for which it not allowed to register user callbacks.

Cause: An invalid type of user callback was specified.

Cause: The mode parameter in an OCI call is invalid

Cause: One or more rows failed in the DML.

Cause: The Statement handle was executed or described successfuly before.

Cause: The name specified in the OCIDescribeAny call referred to an IOT overflow segment.

Cause: The size of the application context must be initialized before populating each context element.

Cause: The size or index of the application context must be non-zero and non-negative.

Cause: This is an internal OCI error.

Cause: Trying to attach using the wrong driver

Cause: Feature not supported in fast path mode

Cause: All the requested rows in this fetch could not be received.

Cause: The scrollable cursor execute or fetch has failed.

Cause: Scrollable cursor operation requested with non-scrollable cursor.

Cause: OCIServerAttach called in OCI_POOL mode but no connection pool found to associate the server handle.

Cause: Mode specified in OCIConnectionPoolCreate is invalid.

Cause: Mode specified in OCIConnectionPoolDestroy is invalid.

Cause: OCIConnectionPoolCreate was not called in OCI_DEFAULT mode for this pool handle.

Cause: Attribute OCI_ATTR_NONBLOCKING_MODE has been set on the server handle and attached in OCI_POOL mode. Connection pooling does not support non blocking mode.

Cause: An internal error occured while trying to free connections.

Cause: A connection pool has already been created for the specified pool handle.

Cause: An invalid combination of minimum, maximum and increment number of connections was specified in the OCIConnectionPoolCreate call.

Cause: The database link specified in OCIConnectionPoolCreate might be an invalid one.

Cause: Sufficient number of connections are not present in the pool to execute the call. No new connections can be opened as the connMax parameter supplied in OCIConnectionPoolCreate has been reached.

Cause: The username and password specified in OCIConnectionPoolCreate might be invalid.

Cause: Some connections in the pool were busy when an attempt to destroy the connection pool was made.

Cause: An attempt was made to use the connection pool before creating it.

Cause: An internal error occured while creating connections in the pool.

Cause: A mode switch from OCI8 to OCI7 was attempted in a callback.

Cause: A connection pool has already been created for the specified pool name.

Cause: An internal error occured while generating unique server group name.

Cause: The client cannot process all the new features in the object.

Cause: Result set size exceeded the max limits.

Cause: A session pool has already been created for the specified pool handle.

Cause: OCISessionPoolCreate was not called in OCI_DEFAULT mode for this pool handle.

Cause: An invalid combination of minimum, maximum, max per shard and increment number of sessions was specified in the OCISessionPoolCreate call.

Cause: The number of sessions specified by the minSess parameter of OCISessionPoolCreate could not be started, possibly because the value supplied was larger than that supported by the server."

Cause: Username and password must be specified when pool is created in this mode.

Cause: An attempt was made to use a Session Pool that does not exist.

Cause: The number of sessions has exceeded the maximum size of the Session Pool.

Cause: A proxy session was requested for from a Session Pool which does not support proxy sessions.

Cause: The session was retrieved using OCISessionGet, and an attempt has been made to release it using a call other than OCISessionRelease.

Cause: The session was not retrieved using OCISessionGet, and an attempt has been made to release it using OCISessionRelease.

Cause: An attempt was made to destroy the session pool while some sessions in the pool were busy.

Cause: An attempt was made to set the implicit ROWID attribute.

Cause: An invalid attempt was made to call OCIDefineByPos for position 0.

Cause: An invalid mode was passed to OCIDefineByPos.

Cause: Some of the attributes set on the user handle were not allowed in pooled mode.

Cause: A session with SYSDBA privileges was requested from a Session Pool which does not support sessions with SYSDBA privileges.

Cause: An externally authenticated session was requested from a Session Pool which does not support external authentication.

Cause: An attempt was made to call OCIStmtPrepare2 and neither sqltext nor key were specified.

Cause: The statement that was requested for does not exist in the statement cache.

Cause: A tagged statement was requested for, but an untagged statement has been returned.

Cause: A statement that was earlier prepared using OCIStmtPrepare2 is now being reprepared using OCIStmtPrepare."

Cause: An attempt was made to release a statement without first preparing it using OCIStmtPrepare2.

Cause: The statement was prepared using a service context that is different from the one specified in OCIStmtExecute.

Cause: OCIHandleFree called on a statement that was prepared using OCIstmtPrepare2.

Cause: An attempt was made to execute a statement without first preparing it using OCIStmtPrepare2.

Cause: The statement was prepared using an authentication handle that is different from the one specified in OCIStmtExecute.

Cause: A plsql compilation warning occurred.

Cause: An internal OCI error has occurred.

Cause: An internal OCI error has occurred.

Cause: An attempt was made to transfer a system change number (SCN) to an Oracle database or client that is older than Release 12.2 and the SCN exceeds the maximum value that such a system can handle.

Cause: The database security policy configuration did not allow the specified Two-Task Common (TTC) RPC.

Cause: The database security policy configuration did not allow object types as input parameters (including IN bind variables) in Two-Task Common (TTC) RPCs.

Cause: An error occured during statement pre-processing. E.g., SQL statement has invalid usage of N' or Q' literals.

Cause: Your program has too many levels of recursion.

Cause: value_sz specified in OCIBindByPos2, OCIBindByName2 or OCIDefineByPos2 exceeds SB4MAXVAL and is not supported in this release.

Cause: The number of application context settings supplied during authentication exceeded the specified limit.

Cause: The network host name in files like /etc/hosts was not set.

Cause: The contention on OCI Session Pool is high.

Cause: OCISessionGet() could not find a free session to the appropriate shard in the specified timeout period. No new sessions can be opened to the shard either as the number of connections open to the shard is already at the value specified by OCI_ATTR_SPOOL_MAX_PER_SHARD.

Cause: The OCISessionGet() timeout expired waiting for OCI Session Pool to create new sessions

Cause: Internal error .

Cause: An attempt was made to invoke OCI API with an invalid mode.

Cause: Operating system did not support multithreaded mode.

Cause: Pool size must be positive in shared mode.

Cause: Invalid parameters were passed into the environment creation call. Check the passed in parameters for the following conditions: -envp should not be NULL -xtramem_sz should not be negative -Either both xtramem_sz and usrmempp have to be provided. Or, neither should be provided.

Cause: An attempt was made to set the authentication handle on session pool handle after OCISessionPoolCreate.

Cause: Some of the attributes set on the authentication handle being set on the session pool handle are invalid.

Cause: Some attributes could not be set both on the authentication handle passed to OCISessionGet and the authentication handle set on session pool handle.

Cause: Some of the properties or their values provided during OCISessionGet with mode OCI_SESSGET_MULTIPROPERTY_TAG were invalid.

Cause: Some of the properties or their values provided during OCISessionRelease with mode OCI_SESSRLS_MULTIPROPERTY_TAG were invalid.

Cause: A reserved Oracle Call Interface (OCI) error has occurred.

Cause: There was a mismatch in the shard keys or group keys with the corresponding connect string.

Cause: An unexpected error was encountered while building and processing sharding-related information.

Cause: An attempt to initialize the shard library failed.

Cause: An unexpected error was encountered while processing sharding-related information.

Cause: An invalid column value was passed.

Cause: There was no instance available with a writable chunk for the specified shard key at the time the OCISessionGet() request was issued. This may be a transient condition due to chunk migration.

Cause: There was no free connection as the pool reached its maximum and all connections were in use at the time the request was issued.

Cause: The PL/SQL fix up callback name was too long.

Cause: OCIShardingKey was set on user handle passed to OCISessionBegin().

Cause: UTF16 mode is allowed only at environment handle creation time.

Cause: Non-UTF16 string is passed in while UTF16 string is expected

Cause: Returned buffer has more codepoints than allowed

Cause: Accumulated codepoint length exceeds allowed codepoint length

Cause: Incoming data larger than receiving buffer

Cause: Attempts to change character set id on non-environment handles

Cause: Attempts to change character set id after other handles have been allocated from the env handle

Cause: Attempts to set one character set id as zero

Cause: Alignment error ocurred in buffer when converting between character sets.

Cause: Attempt to call an OCI function that was not supported in OCI_UTF16ID mode.

Cause: Column security is enabled and column value is not authorized.

Cause: Column security is unknown for the column.

Cause: Column security is unknown for one or more columns.

Cause: PRELIM mode logon was attempted to a pluggable database.

Cause: An instance startup or shutdown operation was attempted when connected to a pluggable database.

Cause: An instance startup failed because an instance of the Oracle RAC One Node database was already running on one of the cluster nodes.

Cause: Serious error: signal received

Cause: A second-level error occurred in an Oracle server process that required that process to exit.

Cause: The Oracle Client library used to communicate with the database failed to initialize correctly.

Cause: A valid buffer was not provided for the bind call.

Cause: A column was being fetched while not in fetch state.

Cause: Transaction ID attribute size is incorrect.

Cause: Application attempted to start a local transaction without using OCI_TRANS_NEW.

Cause: An attempt to detach a local transaction was made.

Cause: An attempt to start a new transaction was made when there was an active transaction.

Cause: These flags are currently not supported.

Cause: An invalid transaction identifier or context was used or the transaction has completed.

Cause: An attempt was made to start a new transaction with an identifier already in use by an existing transaction.

Cause: An attempt was made to detach or complete a transaction that is not the current transaction.

Cause: An invalid transaction start flag was passed.

Cause: An invalid isolation level flag was passed.

Cause: An internal error has occured in the server commit protocol.

Cause: The commit or rollback cannot be performed now because the session cannot switch to the specified transaction.

Cause: The transaction is read-only, or this is the outcome of an optimization for two-phase commit protocol.

Cause: Transaction identifier refers to an active transaction.

Cause: Transaction identifier refers to a prepared transaction.

Cause: Service handle contains a local transaction context.

Cause: Application attempted to start a transaction with a global transaction identifier and a wrong option.

Cause: OCI_TRANS_TIGHT or OCI_TRANS_LOOSE mode was not specified.

Cause: The transaction specified in the call refers to a transaction created by a different user.

Cause: An attempt was made to detach the transaction with a non-zero lock value.

Cause: An attempt was made to start a new transaction when session was already attached to an existing transaction.

Cause: The transaction, which needs to be migratable between sessions, tried to access a remote database from a non-multi threaded server process.

Cause: The migratable transaction tried to access a remote database when the session itself had opened connections to remote database(s).

Cause: The migratable transaction tried to detach from the current session while having an open remote cursor.

Cause: An attempt was made to commit or roll back a transaction while in a different transaction, and the transaction for which the action is requested is in a recovery state (this happens if it is idle too long).

Cause: The list of xids passed into kpotxmp() don't have the same gtrid

Cause: An attempt was made to detach from a non-migrateable transaction.

Cause: An attempt was made to prepare/commit a txn different from current.

Cause: An attempt was made to start a transaction, while attached to a non-migrateable transaction

Cause: An attempt was made to resume a non-migrateable transaction.

Cause: The current transaction has been completed by another process.

Cause: The previous operation did not close all the remote cursors it opened. Since separated transactions are enabled, this is not allowed.

Cause: The transaction specified was created by a shared server and the requestor is a dedicated server, or the transaction was created by a dedicated server and the requestor is a shared server.

Cause: Oracle RM will not start/resume a branch in a recursive call

Cause: An attempt was made to change the isolation level of an existing transaction.

Cause: An invalid transaction start flag was passed.

Cause: Oracle RM will not serve global (distributed) transaction requests if branches are created using different services

Cause: Oracle RM will not serve global (distributed) transaction requests until DTP services are configured in RAC. It is possible that a service was stopped while transactions were in-flight.

Cause: An illegal attempt was made to commit/rollback current transaction

Cause: The commit, rollback, or prepare completed successfully, but the current transaction for this thread was rolled back.

Cause: An illegal attempt was made to promote the current transaction.

Cause: An attempt was made to resume a distributed transaction branch that is physically located on another RAC instance.

Cause: One of the parameter values in the OCI lob function is illegal.

Cause: The only valid return value for a user defined lob read callback function is OCI_CONTINUE. Any other value will cause this error.

Cause: Internal error .

Cause: Internal error.

Cause: When copying or appending LOB locators, both source and desctination LOB locators should be of the same type.

Cause: When reading from or writing into LOBs, the character set form of the user buffer should be same as that of the LOB.

Cause: When copying or appending LOBs, both source and desctination LOB locators should have the same character set form.

Cause: Attempted to stream lob data via the polling mode or a callback when lob buffering was enabled for the input lob locator.

Cause: LOB buffering is enabled for the input lob locator so buffering will be used. However, the amount of lob data to read or write is larger than what the lob buffers can hold.

Cause: While writing into a LOB, more data was supplied than indicated.

Cause: While writing into a LOB, less data was provided than indicated.

Cause: If the database character set is varying-width, the CLOB/NCLOB value is implicitly converted to or from UCS2. This implicit conversion failed.

Cause: An attempt was made to send a LOB across the network, but either the server does not support the LOB sent by the client, or the client does not support the LOB sent by the server. This error usually occurs when the client and server are running different versions of Oracle.

Cause: Temporary LOB locators are not allowed in the operation. For example: OCILobAssign only takes persistent LOB locators as parameters, not temporary LOBs.

Cause: An invalid character set form was passed into an OCI LOB function. For example, the only valid cs form for OCILobCreateTemporary() is OCI_DEFAULT(0), SQLCS_IMPLICIT(1) or SQLCS_NCHAR(2).

Cause: A Bind value of length potentially > 4000 bytes follows binding for LOB or LONG.

Cause: The given size is increased to accomodate the number of bytes from server due to varying width db char/nchar set.

Cause: Abstract LOB locators were not allowed in the operation. For example, OCILobAssign only takes persistent LOB locators as parameters, not Abstract (i.e., client-side created) LOBs.

Cause: Internal error.

Cause: An attempt was made to execute a new OCI LOB call while another OCI LOB call was in progress.

Cause: A very large LOB prefetch size was specified during a query.

Cause: While attempting to initialize OCI in shared mode, a problem was encountered in starting up the shared subsystem.

Cause: While attempting to initialize OCI in shared mode, a problem was encountered in connecting the process to the shared subsystem.

Cause: An internal protocol error occurred while receiving describe data from the server during execution of a statement.

Cause: While attempting to initialize OCI in shared mode, a problem was encountered in connecting the thread to the shared subsystem.

Cause: While making the first call to write LOB data, an invalid pieceinfo value provided.

Cause: There was an attempt to send a LOB locator over a database link which was different from the one on which it was obtained.

Cause: The mode parameter passed into the OCI Client Notification call is incorrect.

Cause: All handles passed into an OCI call should belong to the same environment. In the call that returned this error, handles belonging to different environments were passed in.

Cause: The subscription handle passed into the OCI call does not have a proper name or name-length attribute.

Cause: The subscription handle passed into the OCI call does not have a proper namespace attribute.

Cause: The subscription handle passed into the OCI call does not have a proper callback attribute.

Cause: The subscription handle passed into the OCI call did not have a proper recipient protocol attribute.

Cause: The subscription handle passed into the OCI call did not have a proper recipient attribute.

Cause: The subscription handle passed into the OCI call can't have both the callback defined and a recipient protocol other than OCI_SUBSCR_PROTO_OCI at the same time.

Cause: The subscription handle passed into the OCI call does not have a valid recipient presentation attribute.

Cause: The OCI call was invoked when another call on the connection was in progress.

Cause: Thread already running at a different port.

Cause: Thread listening for event notification exited because of an error. The error encountered is appended to the error message.

Cause: N/A

Cause: N/A

Cause: Thread was already listening at a different IP address.

Cause: An attempt was made to use OCI_ATTR_SUBSCR_IPADDR attribute before release 11.2 compatible notifications.

Cause: N/A

Cause: An attempt was made to use OCI_SECURE_NOTIFICATION before release 12.0 compatible notifications.

Cause: An error occurred while subscribing to Fast Application Notification. This could be due to problems in the Oracle clusterware configuration.

Cause: Client attempted to fetch a column whose size is larger than the maximum size that can be handled by the client.

Cause: An attempt was made to send or receive a high value system change number (SCN) over the network, but either the sever or client does not support such a high value SCN. This error usually occurs when either the server or client compatibility is lower than 12.2.

Cause: An invalid combination of namespace, presentation and receive protocol was specified during notification registration. Currently, only AQ namespace is supported with XML presentation. Non-AQ namespace is not supported for e-mail and HTTP receive protocols.

Cause: An invalid combination of notification grouping attributes was specified. Currently, only TIME notification grouping class is supported. If notification grouping class is zero, all other notification grouping attributes must be zero.

Cause: An attempt was made to use notification grouping on before release 11.0 compatible notifications.

Cause: An attempt was made to use notification grouping with e-mail or HTTP receive protocol or XML presentation or payload delivery or reliable QoS. Currently, only OCI and PLSQL receive protocols and default presentation are supported with notification grouping.

Cause: An attempt was made to use timeout or grouping with ANONYMOUS namespace. Currently, timeout and grouping are supported only with AQ and DBCHANGE namespaces.

Cause: An attempt was made to use context, QOS and timeout attributes of notification on lower than 10.2 compatible notifications.

Cause: An attempt was made to use a reserved callback for notification registration.

Cause: An attempt was made to register with invalid namespace attribute.

Cause: The maximum number of registrations already existed for this subscription.

Cause: The registration that was asked to be unregistered could not be found.

Cause: N/A

Cause: The register, unregister or post function was invoked with a collection that was smaller than the size specified by the parameter to the function.

Cause: The user attempted to pass an attribute that is too long

Cause: The address portion of the connect string could not be parsed. The client may be using a format of the connect string that the server does not understand.

Cause: An attempt to switch to a PDB with different settings such as character set, time zone or time zone file version on an Oracle 12c Release 1 (12.1) or earlier client failed.

Cause: This statement was not supported with iteration count greater than one.

Cause: This is an internal error.

Cause: System-defined shared memory limits are inadequate for Oracle.

Cause: The process failed to attach to deferred SGA segments.

Cause: This is an internal error.

Cause: A bind variable was used in the when clause of a trigger.

Cause: INSTEAD OF triggers can be created on any view which is not an Editioning View, while BEFORE and AFTER triggers may only be created on Editioning Views.

Cause: Only BEFORE or AFTER triggers can be created on a table.

Cause: Attempt to change NEW trigger variables of datatype object, REF, nested table, VARRAY or LOB datatype which is not supported.

Cause: WHEN clause is specified in an INSTEAD OF trigger.

Cause: attempt to create an INSTEAD OF trigger on a view created with read-only option. The view cannot be updated using INSTEAD OF triggers.

Cause: Attempt to create a trigger on update of a column whose datatype is disallowed in the clause, such as LOB and nested table.

Cause: PLSQL function call or method invocation is not allowed in the WHEN clause when creating a trigger.

Cause: When inserting or updating a view using instead-of trigger, the new value for a LOB view column is of a different datatype.

Cause: Triggers on nested tables can only be created on view columns using INSTEAD OF triggers.

Cause: The column name specified in the nested table clause of an INSTEAD OF trigger does not correspond to a nested table column.

Cause: An attempt was made to try to create a trigger on a table that is used internally to support the Advanced Queueing (AQ) feature.

Cause: The referencing clause specifies identical values for PARENT and OLD.

Cause: The referencing clause specifies identical values for OLD and PARENT.

Cause: Parent values can only be read and not changed.

Cause: DML cannot be performed on a nested table view column except through an INSTEAD OF trigger

Cause: A column list cannot be specified for inserts into the nested table view column.

Cause: NEW ROWID was referenced in a before row trigger which is defined on an index-organized table, or a partitioned table with enabled movement of rows. The ROWID cannot be computed in a before row update trigger because it depends on the actual values of the row

Cause: Conflicting instead of DDL trigger on schema/database already exists.

Cause: cannot pin the database/schema because of too much concurrency

Cause: renaming system triggers is not allowed

Cause: Referenced trigger in the FOLLOWS clause was defined on another table.

Cause: Referenced trigger in the FOLLOWS or PRECEDES clause was either a different type or not a compound trigger.

Cause: A cycle of trigger dependency can be formed.

Cause: The FOLLOWS clause was specified when creating the REVERSE CROSSEDITION trigger.

Cause: The PRECEDES clause was specified when creating a FORWARD CROSSEDITION trigger or a regular trigger.

Cause: FOR EACH ROW is not allowed with compound triggers.

Cause: Compound trigger was defined as system trigger.

Cause: Regular triggers body should start with BEGIN/DECLARE etc .

Cause: Compound trigger body was started with incorrect keyword.

Cause: An attempt was made to create a crossedition trigger in a schema where triggers were not editionable.

Cause: The trigger specified was not a crossedition trigger.

Cause: An attempt was made to create crossedition trigger in the ORA$BASE edition.

Cause: An attempt was made to execute a trigger when the session was almost finished.

Cause: An attempt was made to do DML from a crossedition trigger on an object that has a non-crossedition trigger owned by another user. DML from a crossedition trigger bypasses the running of non-crossedition triggers; this cannot be allowed for triggers owned by other users.

Cause: An attempt was made to do DML from a crossedition trigger that would modify data in a remote database. DML from a crossedition trigger has special rules applied regarding what triggers will fire as part of that DML; these special rules cannot be applied across database links and therefore the DML cannot be allowed.

Cause: The TABLESPACE option to ALTER INDEX was used without the REBUILD option.

Cause: The REBUILD option to ALTER INDEX is specified more than once.

Cause: The PARALLEL option to ALTER INDEX was used without the REBUILD option.

Cause: The NOPARALLEL option to ALTER INDEX was used without the REBUILD option.

Cause: The UNRECOVERABLE option to ALTER INDEX was used without the REBUILD option.

Cause: The RECOVERABLE option to ALTER INDEX was used without the REBUILD option.

Cause: PARALLEL was specified more than once, NOPARALLEL was specified more than once, or both PARALLEL and NOPARALLEL were specified in an ALTER INDEX REBUILD statement.

Cause: the TABLESPACE was specified more than once in an ALTER INDEX REBUILD statement.

Cause: The lock name space for the standby database exceeded the maximum string length.

Cause: An invalid lock name space was specified for the standby database. The lock name space for the standby database can only contain A-Z, 0-9, '_', '#', '$', '.' and '@' characters.

Cause: An attempt was made to create a bitmap index using the NOSORT option.

Cause: An attempt was made to create a cluster index with the BITMAP attribute.

Cause: Too many columns were specified for the index.

Cause: An attempt was made to create a bitmap index using the GLOBAL option.

Cause: An invalid file number was used in dumping a datafile or tempfile.

Cause: BLOCK (MIN/MAX) was specified more than once in the DUMP DATAFILE/TEMPFILE command.

Cause: An invalid block number was used in dumping a datafile or tempfile.

Cause: A value other than MIN/MAX, or a block number was entered in the DUMP DATAFILE/TEMPFILE command.

Cause: An invalid option was specified for the DUMP DATAFILE/TEMPFILE command.

Cause: In CREATE TABLESPACE, the LOGGING and/or NOLOGGING options were specified more than once.

Cause: In CREATE TABLESPACE, the MINIMUM EXTENT option was specified more than once.

Cause: In CREATE/ALTER TABLESPACE, the value specified for the MINIMUM EXTENT option was greater than the maximum extent size.

Cause: An attempt was made to create a global bitmap index on a partioned table.

Cause: Specifying more components to a name than allowed.

Cause: Specifying a database link name when it is not permitted.

Cause: An attempt was made to specify the BUFFER_POOL, FLASH_CACHE, or CELL_FLASH_CACHE storage option. This option may only be specified during - CREATE or ALTER TABLE - CREATE or ALTER CLUSTER - CREATE or ALTER INDEX

Cause: The name of the cache hints specified by was invalid. The only valid names for BUFFER_POOL are KEEP, RECYCLE and DEFAULT. The only valid names for FLASH_CACHE and CELL_FLASH_CACHE are KEEP, NONE and DEFAULT.

Cause: An attempt to set RELY on for NOT NULL constraint.

Cause: Try to insert/update/delete on table with DISABLE VALIDATE constraint.

Cause: the named constraint does not exist for this table.

Cause: Attempted to modify a primary key that is not defined for the table.

Cause: attempted to modify a unique key that is not deined for the table.

Cause: cannot ALTER TABLE EXCHANGE PARTITION when the partition and the table have a disabled and validated unique constraints AND the unique keys in the partion is not mutually exclusive from the rest of the table.

Cause: The SINGLE TABLE option was specified more than once.

Cause: The keyword TABLE is missing from the SINGLE TABLE option.

Cause: The SINGLE TABLE option is only valid for hash clusters.

Cause: An attempt was made to store more than one table in a cluster that was created with the SINGLE TABLE option.

Cause: Value from cast operand is larger than cast target size.

Cause: An obsolete initialization parameter has been specified

Cause: An invalid option appears.

Cause: An invalid option appears.

Cause: An invalid option appears for EXTENT MANAGEMENT clause

Cause: default storage clause was specified twice for create tablespace

Cause: default storage clause was specified for a tablespace with AUTOALLOCATE or UNIFORM policy

Cause: An invalid option appears.

Cause: In CREATE TABLESPACE, the allocation policy was specified more than once, for example, AUTOALLOCATE and UNIFORM.

Cause: In CREATE TABLESPACE, the EXTENT MANAGEMENT option was specified more than once.

Cause: In CREATE/ALTER TABLESPACE, the value specified for the UNIFORM SIZE option was greater than the maximum extent size.

Cause: An attempt was made to specify ONLINE for ALTER TABLE MOVE on a table that is not index-organized. The ONLINE option is currently supported only for index-organized tables.

Cause: An attempt was made to create an index on a column of UROWID type

Cause: An attempt was made to alter the extent parameters for a segment in a tablespace with autoallocate or uniform extent allocation policy.

Cause: An attempt was made to create a rollback segment in a tablespace with autoallocate extent allocation policy.

Cause: An attempt was made to drop a TEMPFILE being used by online users

Cause: An attempt was made to use space in a temporary tablespace with no files.

Cause: Columns that are used for a named-join (either a NATURAL join or a join with a USING clause) cannot have an explicit qualifier.

Cause: Columns that are used for a named-join (either a NATURAL join or a join with a USING clause) cannot have an explicit qualifier.

Cause: When a query block uses ANSI style joins, the old notation for specifying outer joins (+) cannot be used.

Cause: An attempt was made to create a tablespace with a block size which is not supported.

Cause: RELY is specified for the foreign key contraint, when the associated primary key constraint is NORELY.

Cause: A valid tablespace number was missing.

Cause: A valid relative data block address was missing.

Cause: Both the DBA and RDBA options were passed to ALTER SYSTEM DUMP REDO.

Cause: Only one RDBA option was passed to ALTER SYSTEM DUMP REDO.

Cause: The relative data block adress is invalid for the given tablespace number or the table space number is invalid.

Cause: The statement tag value was not specified using a simple expression.

Cause: The SQL statement had more passwords than the maximum limit allowed.

Cause: A PRIMARY KEY constraint must be defined for a table with this organization

Cause: Storage parameters cannot be defined for a PRIMARY KEY constraint for a table with this organization

Cause: The UNRECOVERABLE option may not be specified for a primary key for a table with this organization

Cause: The storage option PCTTHRESHOLD is specified more than once.

Cause: The specified value must be a positive integer.

Cause: PCTTHRESHOLD can only be specified for tables with certain organizations.

Cause: ON keyword required to specify nested index column nest

Cause: An attempt was made to use one or more of the following feature(s) not currently supported for index-organized tables: CREATE TABLE with LOB/BFILE/VARRAY columns, partitioning/PARALLEL/CREATE TABLE AS SELECT options, ALTER TABLE with ADD/MODIFY column options, CREATE INDEX

Cause: An attempt was made to drop a tablespace which contains an index only table's overflow segment but not the top index segment"

Cause: A column name is not present where required by the CREATE TABLE for specifying last column to be included in the index segment of the index-organized table

Cause: An index column name other than the last is specified as including column

Cause: INCLUDING clause of a CREATE TABLE is an valid option only for index-organized tables with OVERFLOW clause (at creation time) or if an OVERFLOW segment already exists (at ALTER time).

Cause: The specified table does not have the proper field definitions.

Cause: While altering an index-organized table, an attempt was made to enter either the PCTFREE or PCTUSED value for IOT top index segment.

Cause: ALTER TABLE statement attempted to combine an index-organized table maintenance operation (e.g. changing physical attributes) with some other operation (e.g. ADD constraint) which is illegal

Cause: An attempt to directly access the overflow table of an index-organized table

Cause: An attempt to specify one or more of the following options for an index-organized table: [NO]CACHE, NO LOGGING, CLUSTER

Cause: An attempt to use COMPRESS option on single column key

Cause: The specified value must be a positive integer less than the number of key columns

Cause: An attempt to specify one or more of the following options for index on an IOT: BITMAP, REVERSE, PCTUSED

Cause: MOVE specified after one/more other ALTER options

Cause: An attempt was made to ADD OVERFLOW segment on an index-organized table that already has an overflow segment

Cause: An unsupported partitioning method was specified.

Cause: An attempt to specify a partitioning key which is not a prefix of the primary key of the index-organized table

Cause: A NULL parameter was specified for QUEUE_NAME.

Cause: An invalid value specified for parameter VISIBILITY.

Cause: A NULL value was specified for the parameter.

Cause: A negative value or NULL was specified for DELAY.

Cause: An invalid SEQUENCE_DEVIATION was specified.

Cause: The specified queue does not exist.

Cause: An attempt was made to enqueue to an exception queue.

Cause: The queue has been stopped to prevent any further enqueueing.

Cause: A relative message identifier should be specified if sequence deviation is specified as BEFORE.

Cause: The expiration is less than zero or NULL.

Cause: No message inm the queue with the msgid equal to the specified RELATIVE_MSGID.

Cause: The DELAY specified in the enqueue is greater than the delay of the message with the given relative message id.

Cause: The PRIORITY specified in the enqueue is less than the priority of the message with the given relative message id.

Cause: The message specified by the RELATIVE_MSGID field in the sequence deviation BEFORE option has been dequeued.

Cause: A message was enqueued to the exception queue with either delay or expiration specified.

Cause: A user tries to enqueue an object to a queue that was created for objects of different type.

Cause: Both attributes, NAME and ADDRESS, were specified null for one of the recipients in the recipient list.

Cause: An attempt was made to enqueue to a non-persistent queue without setting visibility to IMMEDIATE.

Cause: An attempt was made to enqueue to a non-persistent queue with delay greater than zero seconds.

Cause: An attempt was made to enqueue to a non-persistent queue with sequence deviation specified.

Cause: An attempt was made to enqueue to a non-repudiable queue without specifying the signature

Cause: An attempt was made to enqueue to a queue specifying the signature for a queue not supporting non-repudiation

Cause: An attempt was made to enqueue to a queue without giving the complete sender information (name) for a queue supporting non-repudiation

Cause: An attempt was made to enqueue data into a non persistent queue that is of a type other than the supported raw or object type.

Cause: An attempt was made to enqueue into a secure queue without specifying a sender name.

Cause: An invalid parameter has been specified for DEQUEUE_MODE.

Cause: The queue has not been enabled for dequeue.

Cause: The job doesn't exist in AQ$_SCHEDULES or cache.

Cause: User-specified dequeue wait time has passed or the end of the queue has been reached but no message has been retrieved.

Cause: There was an error when transforming a message at enqueue, dequeue or propagation time.

Cause: A negative value has been specified for WAIT.

Cause: A user tried to dequeue from a queue that has been created for multiple consumers but a CONSUMER_NAME was not been specified in the dequeue options.

Cause: An enqueue was performed with duplicate queue agents in the recipients parameter.

Cause: An invalid parameter has been specified for NAVIGATION.

Cause: The NEXT_TRANSACTION navigation option was used in a dequeue from a queue in a queue table that was not created for transactional grouping.

Cause: The NEXT_TRANSACTION navigation option was used in a dequeue when there were no more messages that belong to the same transaction.

Cause: The variable or buffer used for the out parameter payload is too small for the user data dequeued.

Cause: The NEXT_MESSAGE or NEXT_TRANSACTION option was specified after dequeuing all the messages.

Cause: An ENQUEUE was performed with more than 32 recipients for the given destination (address).

Cause: An attempt was made to dequeue from a release 8.0-compatible exception queue without including a message ID in the dequeue options.

Cause: An attempt was made to dequeue by including both a message ID and a dequeue condition/correlation ID in the dequeue options. In the dequeue options, you are permitted to specify either message ID or dequeue condition/correlation ID, or neither.

Cause: An attempt was made to change the correlation ID while using the NEXT_MESSAGE or NEXT_TRANSACTION option for dequeuing.

Cause: An attempt was made to change the subscriber name while using the NEXT_MESSAGE or NEXT_TRANSACTION option for dequeuing.

Cause: An attempt was made to dequeue from an exception queue by specifying the CONSUMER_NAME in the dequeue options. CONSUMER_NAME can only be specified when dequeuing from a normal queue created for multiple consumers.

Cause: An internal error was encountered. There may be an inconsistency in the queue table index.

Cause: The agent name for the agent in the LISTEN call was specified when the agent address was a single-consumer queue or an exception queue.

Cause: An 8.0 style exception queue was specified in the agent-list for the LISTEN call.

Cause: The consumer name specified in the dequeue options is not a recipient of the message specified by the message id.

Cause: An agent was specified more than once in the agent list of the LISTEN call.

Cause: An attempt was made to dequeue from a non-persistent queue.

Cause: A recipient for the message enqueued to a non-persistent queue had a non-local address.

Cause: An attempt was made to issue an ENQUEUE call that exceeded the the maximum number (1024) of recipients per message.

Cause: A non-persistent queue was specified as an address for an agent in the LISTEN call.

Cause: An attempt was made to specify a queue that is not enabled for dequeue in a LISTEN call.

Cause: The specified wait time has elapsed and there were no messages for any of the agents in the agent-list.

Cause: An incorrect subscription string was specified with OCIRegister.

Cause: An attempt was made to specify a consumer in the subscription string when registering for notification on a single-consumer queue or an exception queue.

Cause: An attempt was made to register on a multi-consumer queue without specifying a consumer in the subscription string.

Cause: An attempt was made to specify an 8.0 style exception queue in the subscription string of OCIRegister.

Cause: The user specified the protocol attribute for an agent in the agent list.

Cause: N/A.

Cause: AQ Propagator encountered a setting for JOB_QUEUE_PROCESSES that is insufficient for AQ propagation.

Cause: The name for the agent in the LISTEN call was not specified when the agent address was a multi-consumer queue.

Cause: An attempt was made to dequeue a message with a specific message ID, but no such message exists in the queue.

Cause: An attempt was made to dequeue the signature from this queue, which is not reciever non-repidiable.

Cause: An attempt was made to dequeue the message from a queue which does not support reciever non-repudiation, but the signature was specified for verification

Cause: The signature was specified for a queue, but the dequeue was not done by message id.

Cause: The signature was not specified for a reciever non-repudiable queue

Cause: The dequeue was not performed in browse mode with get signature option

Cause: The signature is not required for the dequeue with get signature option

Cause: The sender info. and the message id. do not match

Cause: The queue table does not exist for the given queue

Cause: Signature does not exist for the given reciever and message id.

Cause: N/A.

Cause: N/A.

Cause: An invalid queue table name is specified.

Cause: An attempt was made to grant or revoke object privilege on release 8.0 style queues.

Cause: An attempt was made to specify NULL for the grantee parameter.

Cause: Dequeue as select not supported before 8.2.

Cause: complete sender information not provided to non-repudiate sender

Cause: complete reciever information not provided to non-repudiate reciever

Cause: message id. was not provided

Cause: neither agent's name nor address provided for non-repudiation"

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

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

Cause: Number of elements in the message properties array do not match the number of elements in the payload array.

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

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

Cause: Buffer already exists for the specified queue.

Cause: Queue already has messages. Cannot complete operation

Cause: Buffer does not exist for the specified queue

Cause: Buffer operations are not supported on the specified queue type

Cause: Enqueue of a buffered message with a non-null lob attribute was attempted

Cause: Propagation of user buffered messages was attempted to a database with version lower than 10.2.

Cause: Subscriber is only allowed to dequeue persistent messages

Cause: Buffered message was enqueued by specifying delay or sequence deviation.

Cause: A visibility of dbms_aq.ON_COMMIT was supplied with the buffered message enqueue or dequeue

Cause: Invalid value was specified for delivery mode

Cause: Cannot drop buffer for queue with buffered subscribers

Cause: Enqueue or dequeue of user buffered messages was attempted to queues in a database with version lower than 10.2.

Cause: Last enqd/ackd message is only supported for buffered queues

Cause: Operation was not performed on the owner instance.

Cause: Capture LCRs can only use commit time or enqueue time ordered queues.

Cause: An attempt was made to enqueue to a buffered queue with expiration greater than zero seconds.

Cause: cannot connect to the owner instance of the buffered queue

Cause: Subscribers could not keep pace with the enqueue rate.

Cause: Notification only subscribers are not allowed to dequeue.

Cause: Specified QOS is not supported for non-persistent queues.

Cause: Sender protocol was specified during an enqueue operation.

Cause: The specified subscriber had a NULL name and an address equal to the queue name.

Cause: An attempt was made to migrate a commit-time queue table to an unsupported compatibility level.

Cause: An attempt was made to propagate buffered messages with the database link pointing to an instance in the destination database which is not the owner instance of the destination queue.

Cause: Check if the Enqueue/Dequeue operation is performed via triggers on Materialized Views which isn't supported.

Cause: A propagation job has stopped because the instance is shutting down.

Cause: A propagation job has stopped because its instance affinity has changed.

Cause: During instance restart in an Oracle RAC environment, queue table repartitioning aborted due to errors.

Cause: There is a pending enqueue or dequeue operation on this queue from the same session.

Cause: user properties can only be specified when enqueueing into 8.1 style queues.

Cause: The message priority range of 0 to 9 was exceeded.

Cause: Array operation fails for the message at specified index. Look at the remainder of the error stack to see what the problem was.

Cause: Array size must be a positive, non-zero integer.

Cause: The size of the argument is smaller than the given array size.

Cause: An array enqueue/dequeue was attempted on an 8.0 queue.

Cause: A PL/SQL associative array was provided for the payload parameter in an enqueue/dequeue array operation.

Cause: An attempt was made to downgrade a database that has commit-time queue tables.

Cause: The release level given for the queue table compatible parameter is invalid

Cause: Queue to Queue propagation for buffered messages didn't connect to the correct instance, most likely because service was not started for the destination queue.

Cause: Buffered propagation destination queue was recreated or its ownership was moved to another instance during propagation.

Cause: An array enqueue/dequeue was attempted for buffered messages

Cause: The specified instance was not responding to AQ requests.

Cause: Remote subscriber with queue_to_queue mode set to TRUE was added. The remote subscriber is on a database version lower than 10.2. Propagation was scheduled to a destination database with version lower than 10.2.

Cause: An attempt was made to execute the specified operation for a sync_capture process.

Cause: The specified capture STREAMS did not exist or was not a sync_capture process.

Cause: An attempt was made to create a sync_capture without using a commit-time queue.

Cause: sync_capture encountered a table with an unsupported property. The most common reason is an unsupported column data type.

Cause: An attempt was made to downgrade a database that has apply process for user-buffered messages.

Cause: An attempt was made to export a database that has apply errors.

Cause: Current API could not handle a statement with bind variables.

Cause: The minimum value requested for the Oracle Streams Advanced Queuing (AQ) pool size was greater than the Oracle Streams pool size.

Cause: The maximum value requested for the Oracle Streams Advanced Queuing (AQ) pool size was less than the minimum value of the Oracle Streams (AQ) pool size.

Cause: Dequeue of a buffered subscriber or JMS sharded queue failed with OCIAQDeq().

Cause: An Oracle Advanced Queuing (AQ) operation was attempted at a non-owner instance of the shard which could not establish an internal connection to it.

Cause: the limit on the number of concurrent transaction branches has been reached

Cause: The transaction is currently used by a different session.

Cause: The user session is not attached to any transaction.

Cause: The branch specified cannot be killed immediately because another session is using the branch, but it has been marked for kill. This means it will be deleted as soon as possible after the current uninterruptable operation is completed.

Cause: A failure occured since the last fetch on this statement. Failover was able to bring the statement to its original state to allow continued fetches.

Cause: A failure occured since the last fetch on this statement. Failover was unable to bring the statement to its original state to allow continued fetches.

Cause: A failure occured while a transaction was active on this connection.

Cause: The connection to the database has been lost, and attempts to reconnect have failed.

Cause: The primary instance has died.

Cause: A failure occured while a transaction was attempting to commit. Failover could not automatically determine instance status.

Cause: Failover was unable to generate an address for a backup instance.

Cause: The connection was lost while doing a fetch.

Cause: The connection was lost while doing this call. It may not be safe to replay it after failover.

Cause: The connection was lost when fetching a LOB column.

Cause: The application failover callback requested failover retry.

Cause: Replay was not able to restore the transaction state to match the pre-failover state.

Cause: The application called an Oracle Call Interface (OCI) function that is not supported with transactional failover.

Cause: The application explicitly disabled transaction replay by setting attribute OCI_ATTR_TRANSACTIONAL_TAF=FALSE.

Cause: The Transparent Application Failover (TAF) callback started a transaction and did not commit or rollback prior to exiting.

Cause: Application Continuity replay was attempted after REPLAY_INITIATION_TIMEOUT expired. The value for REPLAY_INITIATION_TIMEOUT is configured for the service to which the application is connected.

Cause: Failover sucessfully recovered an in-flight transaction

Cause: Oracle Call Interface (OCI) Application Continuity replay was attempted after a large call that could not be recorded due to excessive memory requirements.

Cause: The application used an Oracle Call Interface (OCI) object type that is not supported with transactional failover.

Cause: The application used an Oracle Call Interface (OCI) type that is not supported with transactional failover.

Cause: Application Continuity failover was attempted after executing a request with a large number of Oracle Call Interface (OCI) calls, so replay of the request was not possible.

Cause: The connection was lost while issuing a rollback and the application failed over.

Cause: A shared dblink is being used to connect to a remote instance that does not support this feature because it is an older version.

Cause: An attempt was made to downgrade after the upgrade of the database link data dictionary.

Cause: An attempt to connect using the database link failed.

Cause: No call in progress over shared database link.

Cause: A connected user database link is being used to connect to a remote database from a proxy user session.

Cause: An attempt to connect using the database link failed because the network protocol used for the database link is disallowed.

Cause: An attempt was made to use a connected user database link inside a definer's rights function, procedure or view, and the owner of the function, procedure or view lacked INHERIT REMOTE PRIVILEGES privilege on the connected user.

Cause: The COMMON_SCHEMA_ACCESS lockdown profile feature was disabled.

Cause: The use of database link was detected in the failed-over session while Transparent Application Continuity was in use.

Cause: An attempt to evaluate was made, which failed because one of the table values specified had an invalid alias.

Cause: An attempt to evaluate was made, which failed because some of the table values specified had the same table alias.

Cause: An attempt to evaluate was made, which failed because one of the variable values specified had an invalid name.

Cause: An attempt to evaluate was made, which failed because some of the variable values specified had the same variable name.

Cause: An attempt to evaluate was made, which failed because one of the column values specified had an invalid table alias.

Cause: An attempt to evaluate was made, which failed because one of the column values supplied a value for a table alias, which already had a table value supplied.

Cause: An attempt to evaluate was made, which failed because too many column values were supplied for the specified table alias.

Cause: An attempt to evaluate was made, which failed because duplicate column values were supplied for the specified table alias and column number.

Cause: An attempt to evaluate was made, which failed because an invalid ROWID was supplied for the specified table alias.

Cause: An attempt to evaluate was made, which failed because an invalid column number was supplied for the specified table alias as a part of a column value.

Cause: An attempt to evaluate was made, which failed because duplicate column values were supplied for the specified table alias and column name.

Cause: An attempt to evaluate was made, which failed during the evaluation of the specified rule.

Cause: An attempt to load the specified rule or expression failed due to errors in the rule or expression.

Cause: An attempt to evaluate was made, which failed because one of the attribute values specified had an invalid variable name.

Cause: The specified error occurred during evaluation of the rule set.

Cause: An attempt to evaluate was made, which failed because too many attribute values were supplied for the specified variable.

Cause: An attempt to evaluate was made, which failed because duplicate attribute values were supplied for the specified variable and attribute name.

Cause: An attempt to get rule hits or to close an iterator was made, which failed because an invalid iterator was passed in.

Cause: An attempt to get rule hits for an iterator was made, which failed because of an error in evaluation of the specified rule set.

Cause: An attempt to evaluate the specified rule set using the evaluation context specified failed due to some errors.

Cause: An attempt to get rule hits was made, which failed because the underlying rule set was modified after the iterator was returned.

Cause: The specified evaluation function returned a failure during evaluation, causing evaluation to terminate.

Cause: Variable or table column values were not supplied for evaluation.

Cause: The attempt to convert data to the data type of the variable or column failed.

Cause: An attempt to evaluate was made, which failed because the ruleset name specified was null.

Cause: An attempt to evaluate was made, which failed because the evaluation context specified was null.

Cause: An attempt to evaluate was made, which failed because one of the table values specified had a NULL alias name.

Cause: An attempt to evaluate was made, which failed because the table value for the specified table alias had a NULL ROWID.

Cause: An attempt to evaluate was made, which failed because one of the variable values specified had a NULL variable name.

Cause: An attempt to evaluate was made, which failed because the variable value for the specified variable name had NULL data.

Cause: An attempt to evaluate was made, which failed because one of the column values specified had a NULL alias name.

Cause: An attempt to evaluate was made, which failed because one of the column values for the specified alias name had a NULL column name.

Cause: An attempt to evaluate was made, which failed because the column value for the specified alias and column name had NULL data.

Cause: An attempt to evaluate was made, which failed because one of the attribute values supplied a value for a variable, which already had a variable value supplied.

Cause: An attempt to evaluate was made, which failed because one of the attribute values for the specified variable had a NULL attribute name.

Cause: The open rule hit iterators in the session exceeded 2 * OPEN_CURSORS.

Cause: The user attempted to put unsupported data types, such as LOBs and evolved ADTs, into the rule action context.

Cause: N/A

Cause: Database must be open to perform ALTER SYSTEM QUIESCE RESTRICTED command.

Cause: Database resource manager failed to change plan.

Cause: There is a concurrent ALTER SYSTEM QUIESCE RESTRICTED or ALTER SYSTEM UNQUIESCE command running in the system.

Cause: Database cannot be opened because the system is being or has been quiesced.

Cause: Cannot quiesce the system because the system is already quiesced.

Cause: Cannot unquiesce the system because the system is not in quiesced state.

Cause: Cannot quiesce the system because resource manager has not been continuously on since startup in this or some other instances.

Cause: Cannot quiesce the system because resource manager has not been continuously on since startup.

Cause: Database must be mounted to perform ALTER SYSTEM UNQUIESCE command.

Cause: A column has been added to a replicated table, but replication support processing has not completed.

Cause: Could not quiesce the root container.

Cause: Could not quiesce the pluggable database.

Cause: One value in _DB_MTTR_SIM_TARGET is not a valid MTTR.

Cause: One value in _DB_MTTR_SIM_TARGET is empty.

Cause: Too many candidate MTTRs are specified in _DB_MTTR_SIM_TARGET.

Cause: An attempt to start MTTR advisory was made, which failed because FAST_START_MTTR_TARGET was not specified.

Cause: The current FAST_START_MTTR_TARGET setting or a candidate MTTR setting is too small for MTTR advisory.

Cause: The current FAST_START_MTTR_TARGET setting or a candidate MTTR setting is too large for MTTR advisory.

Cause: An attempt to start MTTR advisory was made, which failed because either FAST_START_IO_TARGET or LOG_CHECKPOINT_INTERVAL was specified.

Cause: An attempt to create a join index was made, which failed because no valid where clause was found.

Cause: An attempt to create a join index was made, which failed because there was an OR branch in the where clause.

Cause: An attempt to create a join index was made, which failed because it included a predicate which wasn't an equi-inner join.

Cause: An attempt to create a join index was made, which failed because a functional index was requested or necessary (such as is the case for indexing columns using timezone).

Cause: An attempt to create a join index was made, which failed because one or more dimensions did not have an appropriate constraint matching the join conditions.

Cause: An attempt to create a join index was made, which failed because one of the tables in the from clause did not appear in the where clause.

Cause: An attempt to create a join index was made, which failed because one of the tables was owned by SYS.

Cause: An attempt to create a join index was made, which failed because the where clause contains a cycle.

Cause: An attempt to create a join index was made, which failed because a predicate in the where clause contained something other than a simple column.

Cause: An attempt to create a join index was made, which failed because no bitmap keyword was used.

Cause: An attempt to create a join index was made, which failed because one of the tables was temporary.

Cause: An attempt to execute dml resulted in the need to perform dml on another table because of a cascade constraint. The join index only allows one of its underlying tables to me modified at a time.

Cause: An attempt to execute an merge or multitable insert on a table that was used to create a bitmap join index was made. Merge and multitable inserts are not supported on tables that were used to create a bitmap join index.

Cause: An attempt to create a join index was made, which failed because the from clause contains non table object.

Cause: The datatype of the join column is incompatible with the datatype of the joined column.

Cause: An attempt to create a join index was made, which failed because the from clause does not contain the fact table.

Cause: An attempt to create a join index was made, which failed because one of the tables was an index organized table.

Cause: The Loader control file contains a PARTITION clause but the table being loaded is not partitioned.

Cause: A nonexistent index was specified in the SORTED INDEXES clause.

Cause: Parallel load was specified into a table which has index defined upon it.

Cause: Parallel load is not supported for index-organized tables.

Cause: User attempted to load a clustered table via the direct path.

Cause: In direct path load, the handle passed in does not match the type listed.

Cause: In direct path load, the bind variables listed in the sql expression do not match the input argument column names.

Cause: The value passed in a Direct Path API stream for a column containing a SETID or OID has an invalid value. SETIDs and Object IDs must be either 16 bytes of RAW data or 32 bytes of hexidecimal characters.

Cause: See following error message for more information. A SQL string cannot have quoted strings improperly terminated. A bind variable in a SQL string cannot have a length of 0, cannot exceed maximum length of 30 characters, and cannot be missing a double quote.

Cause: An error has occurred in a Data Pump stream verification operation.

Cause: A column which is NOT NULL in the database is not being loaded and will cause every row to be rejected.

Cause: A column can only store data of type declared for that column. And a substitutable column can only store data of valid subtypes of the supertype declared for that column.

Cause: A dump file was specified for a load operation whose version number is incompatible with the dump file version currently produced by the Oracle server on the system. Usually this message indicates that the dump file was produced by a newer version of the Oracle server.

Cause: There seems to be a discrepancy between the size for a list or buffer allocated by direct path api and the size needed.

Cause: The SQL error was returned from an OCIStmtExecute call.

Cause: User attempted to load an array column via the direct path.

Cause: You attempted to load an virtual column using the direct path.

Cause: Global indexes are defined on a table when direct path loading a single partition of the table.

Cause: Column specified in the loader control file does not exist.

Cause: The Specified column of SQL column type %s is not supported by the direct path loader.

Cause: Non-partitioned index information put to loader log file.

Cause: Partitioned index information put to loader log file.

Cause: A Non-partitioned index was made index unusable due to the error displayed below this error.

Cause: A partition of a partitioned index was made index unusable due to error displayed below this error.

Cause: User requested SKIP_UNUSABLE_INDEXES option, and the index segment * was in unusable state prior to the beginning of the load.

Cause: User requested that index maintenance be skipped on a direct path load.

Cause: A unique index is in IU state (a unique index cannot have * index maintenance skipped via SKIP_UNUSABLE_INDEXES).

Cause: A partition of a unique index is in IU state (a unique index * cannot have index maintenance skipped via SKIP_UNUSABLE_INDEXES).

Cause: An index is in IU state prior to the beginning of a direct * path load, it cannot be maintained by the loader.

Cause: A partition of an index is in IU state prior to the beginning * of a direct path load, it cannot be maintained by the loader.

Cause: A logical index error occurred on a partitioned index which * affected one or more index partitions, which are listed below * this message.

Cause: A index errror occurred during the index maintenance phase of * a direct path load. The load cannot continue. See error message * below this message.

Cause: An index error occurred during direct-load of an index-organized table. * Loading had to be aborted. No rows were loaded.

Cause: The source and destination columns did not have the same * encryption properties.

Cause: Column specified in the column list does not exist in the stream.

Cause: An error occurred while attemping to encrypt or decrypt * a database column.

Cause: The Loader control file contains a PARTITION clause but the table being loaded is not subpartitioned.

Cause: An attempt was made to load a system partitioned table with no partition name(s) specified.

Cause: An attempt to write an audit record during a SQL*Loader direct path load failed.

Cause: Trying to access data in block that was loaded without * redo generation using the NOLOGGING/UNRECOVERABLE option

Cause: The column could not be converted from DATETIME * datatype to internal DATETIME/CHARACTER datatype.

Cause: The number of arguments for the REF column is incorrect.

Cause: The scoped table name passed in by the user does not match the name in the schema.

Cause: The scoped table name passed in by the user does not match the name in the schema.

Cause: The table name passed in by the user does not exist in the schema.

Cause: Direct path can not load a domain index of that column type.

Cause: A packed decimal field with a non-zero scale factor is mapped to a character column. In order to perform the datatype conversion, a numeric format string must be created based on the input field's precision and scale specifications. Direct path loader encountered an error in creating this format string.

Cause: The direct path api does not support a SQL expression on a column of that type.

Cause: The current row was not loaded due to a conversion error.

Cause: The user prepared the direct path context for one operation (Load, Unload, Convert), but then tried to perform a different operation.

Cause: The user specified a zero length or null buffer to be used for the Direct Path Unload operation.

Cause: An attempt was made to load into a view using direct path that has user-defined types, XML data, object type table or SQL expressions.

Cause: User attempted to convert a direct path stream that does not require conversion.

Cause: The direct path API encountered an unexpected error while retrieving metadata for a column.

Cause: The direct path API encountered a column that can not be loaded because the input data is too large for a column.

Cause: The direct path API encountered a type identifier for a column that can not be loaded because a mapping can not be found for the input value.

Cause: User attempted a direct unload when another is still in progress.

Cause: User attempted to continue a direct path load after receiving an error which indicates the load can not continue.

Cause: User specified an SCN which occurs before the last time the table definition was modified.

Cause: User specified an invalid SCN.

Cause: An enabled check constraint was found on a column stored as a lob.

Cause: Client attempted to set or reset the number of rows in a direct path * structure after it has already been allocated and initialized. * Attributes used is one of the following: * - OCI_ATTR_NUM_ROWS: to set # of rows in a direct path column array * - OCI_ATTR_DIRPATH_DCACHE_SIZE: to set size of a date cache * (default is 0) * - OCI_ATTR_DIRPATH_DCACHE_DISABLE: to set whether date cache will be * disabled on overflow (default is FALSE)

Cause: Client attempted to allocate a column array for a direct path * function context before allocating a column array for the * table-level direct path context.

Cause: A parallel load file was specified which is not part * of the database.

Cause: A parallel load file was specified which is not in the * tablespace of the table being loaded.

Cause: A parallel load file was specified which is not in the * tablespace of the table (partition, subpartition) being loaded. * When a partitioned table is being loaded, the file must be * in the tablespace of every partition or subpartition * (i.e. each (sub)partition must be in the same tablespace).

Cause: Client application is attempting to do multiple direct path load * operations on the same table, but the segments overlap.

Cause: The stream version requested is not supported by the server.

Cause: An OCIDirPathLoadStream operation was attempted after * OCIDirPathFinish was called. Once a direct path operaton * has been finished, no more data can be loaded.

Cause: A direct path operation is being attempted within a transaction * that has already been started.

Cause: A direct path operation is being attempted on a table which * has enabled triggers.

Cause: All scalar columns (i.e. non-LOB and non-LONG columns) must be * specified by the client of the direct path API prior to * specifying any LOB columns.

Cause: A client of the direct path API specified a LONG column to be * loaded, but the LONG column was not the last column to be * specified.

Cause: A direct path operation is being finished or a data save request * has been made, but the table for which the request is being made * on has a row in partial state. The row must be completed before * the segment high water marks can be moved.

Cause: A direct path operation was requested that is not supported

Cause: A column which is not a LONG or LOB had the * OCI_DIRPATH_COL_PARTIAL flag associated with it. * Only LONG or LOB type columns can be loaded in pieces.

Cause: The user attempted to specify a column size (%d) that exceeded * the maximum allowable input size (%d)."

Cause: An input stream contained data for more input columns * than specified by the client of the direct path API.

Cause: Either a OCIDirPathLoadStream call was made which provided * more stream data prior to the server being able to fully * process the stream data that it already has, or a * OCIDirPathFinish call was made when the server had * unprocessed stream data.

Cause: Either the transfer buffer size specified, or the default * transfer buffer size (if you did not specify a size), is * too small to contain a single row of the converted row data.

Cause: The conversion required for the column was not supported. For * example, conversion from date to number was not supported.

Cause: A direct path api function was called with a direct path * context which has not been prepared.

Cause: OCIDirPathPrepare was called with a context that has already * been prepared.

Cause: The tablespace number in the file header is inconsistent with that in the control file.

Cause: The relative file number in the file header is inconsistent with that in the control file.

Cause: The file header of the referenced file is in V6 or V7 format.

Cause: Attempt to cache the replication information which is unavailable in the catalog for the object.

Cause: An external RepAPI operation failed.

Cause: An internal service failed and signalled an error"

Cause: An unexpected internal RepAPI failure was detected

Cause: The caller requested a RepAPI operation that was not implemented

Cause: An internal buffer control structure was NULL

Cause: An internal buffer control structure was NULL

Cause: The master connection handle was or became invalid.

Cause: The client connection handle was or became invalid.

Cause: An internal materialized view control structure could not be obtained.

Cause: The specified materialized view name was too long.

Cause: A RepAPI operation was attempted against a non-existent or invalid master table

Cause: An unexpected error occurred while sending an def$error rpc to the master site

Cause: A conflict/error occurred at the master site while executing a $RP.rep_insert(), rep_update(), or rep_delete() function which was not handled by conflict resolution logic at the master.

Cause: The specified object was expected but not found.

Cause: The specified master log was not found or available for the named table.

Cause: RepAPI was unable to confirm that the last pushed transaction was successfully commited by the master site.

Cause: The specified materialized view catalog control reocrd was not found.

Cause: Client tried to repush a transaction has already been committed at the master site. A common cause of this problem is an error at the local site in initializing or updating the local site transaction sequence mechanism.

Cause: There was no memory left for the RepAPI process. This error may occur when RepAPI is trying to allocate a new table buffer area.

Cause: An internal memory error was detected.

Cause: An error occurred during the initialization of a PL/SQL rpc.

Cause: An error occurred during the execution of a PL/SQL rpc.

Cause: An error occurred during the termination of a PL/SQL rpc. This is usually caused by master site being unable to close an opened cursor or if RepAPI cannot deallocate internal memory.

Cause: The NLS product/facility error message file could not be located or properly initialized.

Cause: A connection could not be established to the specified database using the provided connection string.

Cause: The client sql materialized view definition query could not be properly parsed by the master Oracle site.

Cause: The client callback failed during its INIT phase for the named object.

Cause: The client callback failed during its PROC phase for the named object.

Cause: The client callback failed during its TERM phase for the named object.

Cause: The materialized view control list could not be constructed. This is generally the result of an error while accessing the local materialized view catalog.

Cause: A parallel push executed with event 26531 enabled raises this error to simulation failure of network or destination site.

Cause: A transaction that was pushed had a transaction ID that collided with a transaction that was previously pushed and committed at the master site.

Cause: A transaction that was pushed had a transaction ID that collided with a transaction that was previously pushed and committed at the master site.

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

Cause: Attempt to rename a replicated table, an updatable materialized view table or the master table of a materialized view for which a materialized view log has beencreated.

Cause: User passed type of the given argument number doesn't match with the type of the argument in the stored arguments.

Cause: User invoked type_arg procedure before starting a deferred call

Cause: Failed to open connection using given dblink

Cause: number of arguments does not match replication catalog

Cause: the (rpc) call is corrupted

Cause: The remote database has a version lower than Oracle 8.0 and hence does not understand replication parallel propagation.

Cause: An attempt to acquire the SR enqueue in exclusive mode failed.

Cause: The materialized view consists of a view and a container table.

Cause: An outbound server's queue was not associated with a capture from the same multitenant container database (CDB) before adding or starting an outbound server.

Cause: An error occurred during creation of a capture or apply background process.

Cause: An attempt was made to start or stop a capture process while another capture process was concurrently starting or stopping.

Cause: An attempt to restart a capture process failed.

Cause: An attempt to restart an apply process failed.

Cause: An attempt was made by a GoldenGate, XStream or Streams Capture or XStream In to connect to an Apply that is already connected in the other mode.

Cause: An attempt was made to execute the specified procedure with an invalid SCN value.

Cause: The supplemental logging versions of capture side and apply side are incompatible.

Cause: The value specified in the action context is invalid for use in GoldenGate, XStream or Streams.

Cause: The database is unable to process GoldenGate, XStream or Streams Data Dictionary for this object.

Cause: The error queue for this apply process contains error entries.

Cause: An attempt was made to create a GoldenGate, XStream or Streams process when another was being created concurrently.

Cause: An attempt was made to create a GoldenGate, XStream or Streams process that already exists.

Cause: An attempt was made to alter a GoldenGate, XStream or Streams process that is currently running.

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

Cause: An attempt to remove the component failed because it is associated with the GoldenGate, XStream or Streams process.

Cause: An attempt was made to specify a subprogram parameter value that is inconsistent with another parameter value.

Cause: An attempt was made to add an XStream outbound server to a queue using uncommitted data mode when no co-located XStream capture was configured for that queue.

Cause: Cannot create additional GoldenGate, XStream or Streams processes since the maximum number of processes has been reached.

Cause: Timeout occurred while waiting for a GoldenGate, XStream or Streams process to shut down.

Cause: An attempt was made to specify a duplicate column name in an LCR.

Cause: The columns in the LCR were not the same or not found in the database table.

Cause: GoldenGate, XStream or Streams capture process could not be created because one or more parameters contain invalid value.

Cause: The number of columns in the LCR was not the same as the the replicated site.

Cause: Database global name has been set to a value which is same as the source database name of the downstream capture process.

Cause: A GoldenGate, XStream or Streams downstream capture process was nonexistent when this operation was attempted.

Cause: Certain operations on LOB/LONG columns of the LCR through rule-based transformations, DML handlers, or error handlers were not allowed.

Cause: The specified object type is not supported.

Cause: The specified command type is not supported.

Cause: The publication_on parameter should be either 'Y' or 'N'

Cause: The value_type parameter should be either 'OLD' or 'NEW'

Cause: The value_type parameter should be one of 'OLD', 'NEW' or '*'

Cause: Transactions from multiple sources were sent to the same apply process.

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

Cause: Object SCN was not set. If the object is a table, then both fields will be filled, for example "SCOTT"."EMP". If the object is a schema, only one field will be set, for example "SCOTT"."". And if the object is the entire database, no fields will be set, for example ""."".

Cause: Metadata mismatch, or not enough information in the user generated LCR.

Cause: The datatypes of columns in the LCR are not the same as the datatypes in the database object.

Cause: One of the columns of the LCR being applied was of a datatype not supported by either the target non-Oracle system or by the Oracle transparent gateway through which the apply is being done.

Cause: The apply process attempted an operation that is either not supported by the non-Oracle system or by the Oracle transparent gateway through which the apply is being done. Some kinds of DML (like procedure and function calls) and all DDL will cause this error to be raised.

Cause: The parameter specified was not in the correct format.

Cause: An attempt to drop an unused rule set failed after dropping the GoldenGate, XStream or Streams proccess successfully.

Cause: An error occurred while enqueueing a message.

Cause: A locking related call failed.

Cause: An attempt to access the database object failed because the data dictionary for the object was either never populated or it was purged.

Cause: The LCR contained more columns than the replicated table.

Cause: The GoldenGate, XStream or Streams client does not have a rule set of the indicated type.

Cause: An attempt was made to create a GoldenGate, XStream or Streams message consumer that already exists.

Cause: An attempt was made to access a GoldenGate, XStream or Streams process which does not exist.

Cause: An attempt was made to downgrade a capture process after it has upgraded the GoldenGate, XStream or Streams data dictionary.

Cause: An attempt was made to downgrade a capture process that has a higher version than the downgrade release version.

Cause: The apply process attempted to apply a DDL LCR via a dblink. This is not supported.

Cause: Remote file server (RFS) process was restarted to reflect a change in DOWNSTREAM_REAL_TIME_MINE option of the GoldenGate, XStream or Streams capture process.

Cause: Capture process cannot mine redo from a version higher than the current software release version.

Cause: The master table for remote apply does not constain a primary key constraint or the primary key constraint has been disabled.

Cause: See the preceding error message to identify the cause. This message names the remote object, usually a table or view, for which an error occurred when GoldenGate, XStream or Streams tried to access it for remote apply.

Cause: GoldenGate, XStream or Streams replication could not access the named table or view at a remote database to apply changes.

Cause: An error was encountered during an apply process.

Cause: The specified time limit was reached for the GoldenGate, XStream or Streams process.

Cause: The specified message limit was reached for the Capture process.

Cause: The specified SCN limit was reached for the GoldenGate, XStream or Streams process.

Cause: The specified transaction limit was reached for the Apply process.

Cause: An apply process attempted to enqueue an LCR with a LONG column. This is not supported.

Cause: The caller did not have the specified role or called the procedure from a definer's rights package or procedure.

Cause: The Capture or Apply user was specified as SYS by a user other than SYS.

Cause: An attempt was made to downgrade apply handlers that are not associated with a local database object, or the apply handlers are associated with a specific apply process.

Cause: An attempt was made to set the standby database and DOWNSTREAM_REAL_TIME_MINE option of the Oracle GoldenGate, XStream or Oracle Streams capture process on the same database.

Cause: The queue_to_queue property was specified for an existing propagation.

Cause: An attempt to use FILE GROUP, FILE GROUP VERSION, or FILE GROUP FILE failed because the item in question already exists.

Cause: A FILE GROUP, FILE GROUP VERSION, or FILE GROUP FILE was specified that does not exist.

Cause: The specified privilege number that was specified is invalid.

Cause: The procedure waited too long while getting a lock to perform a file group repository operation.

Cause: The attempted operation involved datafiles platform conversion which required the datafiles_directory_object parameter to be specified for placing the converted data files.

Cause: One or more datafiles or export dump file(s) were missing from the specified file group version.

Cause: A Data Pump error occurred when the procedure performed a File Group Repository operation.

Cause: A Data Pump dump file was added to a file group version that already has a dump file.

Cause: The FILE GROUP or FILE GROUP VERSION being dropped contained objects.

Cause: An attempt was made to downgrade a database that has file groups.

Cause: An attempt was made to assemble lobs, but the compatibility of the source database for the LOB information is lower than 10.2.0.

Cause: An attempt was made to add more than the allowed number of ignored transactions.

Cause: GoldenGate, XStream or Streams capture encountered a table with an unsupported property. The most common reason is an unsupported column data type.

Cause: The maximum number of open cursors was too small for GoldenGate, XStream or Streams Apply.

Cause: A DDL rule was specified for this operation.

Cause: The specified transformation function encountered an error.

Cause: The specified transformation function encountered an error.

Cause: GoldenGate, XStream or Streams capture process received an LCR with unsupported operation from LogMiner.

Cause: The columns in the LCR were not the same as the table in the database.

Cause: Both a one-to-one transformation function and a one-to-many transformation function were specified for a rule.

Cause: Error

Cause: Standby Redo Logs required for real time mining by downstream capture process were not available.

Cause: An error was encountered while attempting to generate a name for a parameter which was passed a NULL value.

Cause: An invalid file type was specified for the ASM file.

Cause: An invalid parameter was specified for the local capture process.

Cause: An invalid parameter was specified for the downstream capture process.

Cause: LogMiner encountered an unexpected redo pattern. This is usually caused by tables with unsupported data types or newer table features.

Cause: Direct-path SQL with NOLOGGING option or a SQL*Loader operation with UNRECOVERABLE clause was specified for the table.

Cause: An attempt was made to add more than the allowed number of unsupported tables.

Cause: A method was invoked on a NULL object.

Cause: The row to update or delete exists in the table but had conflicting value for some columns.

Cause: The row to update or delete does not exist in the table.

Cause: The column in the destination database is NOT encrypted while it is encrypted in the source database.

Cause: Only one propagation originated from the propagation source queue.

Cause: Could not get a lock on the object because another process was holding the lock.

Cause: A process tried to split or merge this propagation, but failed and left STREAMS in an inconsistent state.

Cause: The value for the source database global name was not valid.

Cause: Split-merge API requires only one capture process enqueued message to the queue where the propagation originated

Cause: Hierarchically enabled tables are not supported.

Cause: An attempt was made to modify an LCR generated by an XStream outbound server.

Cause: The apply slave could not fill update LOB because of missing LOB column.

Cause: The row to update or insert violated the unique constraint.

Cause: The combined capture and apply optimization could not be used since Apply was not the lone subscriber to the queue.

Cause: Multiple subscribers were found when the combined capture and apply optimization was configured to only work for one subscriber.

Cause: The combined capture and apply optimization could not be used since the queue had messages.

Cause: The combined capture and apply optimization could not be used since the subscribers had changed.

Cause: The apply process was disabled or aborted.

Cause: The combined capture and apply optimization could not be used since the queue had rule based subscribers.

Cause: The remote database has a version lower than Oracle 11.0 and hence does not understand combined capture and apply optimization.

Cause: The combined capture and apply optimization could not be used since apply_database_link was not NULL.

Cause: Apply process died unexpectedly.

Cause: The requirements for combined capture and apply mode were broken.

Cause: The combined capture and apply optimization could not be used because Apply was already in the mode of combined capture and apply.

Cause: The client has already attached to the specified apply process.

Cause: An attempt was made to attach to the specified XStream server while another session was attached to it.