Cause: An attempt to migrate was made, which failed because the session id list specified was null.

Cause: An attempt to migrate was made, which failed because the destination instance specified was null.

Cause: An attempt to migrate was made, which failed because the client id specified was null.

Cause: An attempt to migrate was made, which failed because the percentage specified was null.

Cause: An attempt to cancel migration was made, which failed because the session id list specified was null.

Cause: An attempt to get migration status was made, which failed because the session id specified was null.

Cause: A session id instance passed into a dbms_tsm procedure or function had a null sid field.

Cause: A session id instance passed into a dbms_tsm procedure or function had a null serial# field.

Cause: An attempt to migrate was made, which failed because of invalid session number and/or serial number.

Cause: An attempt to reference more connections than configured

Cause: An migration related operation failed because of contention between sessions.

Cause: An attempt to migrate was made, which failed because the session specified cannot be migrated.

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

Cause: An attempt to migrate was made, which failed because the session specified is currently being migrated.

Cause: A migration attempt was made, which failed because the connect string specified was null.

Cause: Session recreation failed at the destination instance.

Cause: A migration attempt was made, which failed because session prepare failed.

Cause: Session begin failed at the destination instance because the shadow connection could not be established.

Cause: An invalid value was specified for the the given parameter.

Cause: An OCI operation failed during transparent session migration.

Cause: An attempt to recover after instance death was made, which failed because the instance name specified was null.

Cause: An attempt to recover after instance death was made, which failed because the death time specified was null.

Cause: An SQL operation failed because the cursor state was lost.

Cause: A session id instance passed into a dbms_tsm procedure or function had an invalid sid field.

Cause: A session id instance passed into a dbms_tsm procedure or function had an invalid serial# field.

Cause: An OCI operation failed during transparent session migration.

Cause: An attempt to migrate was made, which failed during migration because the session id specified by the client was null.

Cause: An attempt to migrate was made, which failed during migration because the destination session id specified by the client was null.

Cause: An attempt to migrate was made, which failed during migration because the session id specified by the client was null.

Cause: An attempt to migrate was made, which failed during migration because the destination session key specified by the client was null.

Cause: The Portable Clusterware/Oracle Cluster Registry stack returned an error.

Cause: An attempt was made to designate multiple databases as the Cluster Director.

Cause: An attempt was made to query/undesignate a Cluster Director when no database has been designated as Cluster Director.

Cause: An attempt was made to undesignate the current Cluster Director by a database that is not the Cluster Director.

Cause: An attempt was made to control the Cluster Director on a database that is not the Cluster Director.

Cause: An attempt was made to control the Cluster Director before the Cluster Director was stopped.

Cause: An attempt to read the scan hostname or port failed

Cause: The program attempted to access a nonexistent or deleted service.

Cause: Internal Error: An attempt to post a system alert failed.

Cause: System Error: An attempt to update a system alert failed. The alert was improperly cleared from WRI$_ALERT_OUTSTANDING.

Cause: An attempt to start services on an instance that will be shutdown

Cause: Session state capture was initiated when session state could not be captured.

Cause: Capture or restore operation failed.

Cause: Invalid session state operation was issued.

Cause: Session state capture was initiated and could not perform the requested operation.

Cause: Invalid parameter was passed to session state capture or restore interface.

Cause: Internal operation error was encountered.

Cause: Session state restore was initiated when session was not ready for state restore.

Cause: An OCI operation failed during an internal operation of session state capture and restore.

Cause: An OCI operation failed during an internal operation of session state capture and restore.

Cause: Session state directory object passed to capture or restore was incorrect.

Cause: An error occurred while capture or restore record was being stored into the database.

Cause: Session state file may be corrupted.

Cause: This is the generic internal error number for the SSCR exceptions. This indicates that the SSCR has encountered an exceptional condition.

Cause: An error was encountered while reading from or writing to session state capture file.

Cause: An invalid session state file was used in session state restore operation.

Cause: The specified package is not supported.

Cause: An attempt was made to operate on the uninitialized file driver.

Cause: You may not have sufficient privileges or quotas for this action.

Cause: The file may not exist or you do not have privileges for this action.

Cause: This is the generic internal error number for file driver exceptions. This indicated that file driver encountered an exception condition.

Cause: The connect string may be incorrect.

Cause: You may not have sufficient privileges for this action.

Cause: In this recursive OCI call, the bind character set was different from the current database character set. This is usually caused by database character set change.

Cause: In this recursive OCI call, the define character set was different from the current database character set. This is usually caused by database character set change.

Cause: The Oracle server process failed and replay was initiated.

Cause: Failover replay was enabled for a service in which some standby databases were older than the original server and could not replay work from the original server.

Cause: Application continuity protocol was violated.

Cause: Failover replay was enabled for a service in which some standby databases were older than the original server and could not replay work from the original server.

Cause: Application replay encountered a command that was not supported for replay, and so replay was disabled.

Cause: The Oracle server process failed after committing a transaction but COMMIT was embedded in a stored procedure and it cannot be guaranteed that the stored procedure finished. Failover cannot continue.

Cause: The Oracle server process failed after committing a transaction in the current request. The transaction cannot be replayed, so the current request cannot be replayed and session state cannot be restored. Failover cannot continue.

Cause: The Oracle server process failed after committing a transaction in the current request. One call that committed a transaction, and thus cannot be replayed, also started a new transaction. Since that call cannot be replayed, the new transaction cannot be restored. Failover cannot continue.

Cause: The Oracle server process failed after executing a request with more than 65535 round trips, so replay of the request is not possible.

Cause: The Oracle server process failed and replay was initiated. However, results of the replay differed from the original execution. Failover cannot continue.

Cause: The Oracle server process failed after executing a request with a complicated call whose capture had too much data, therefore, replaying of the request was not possible.

Cause: The Oracle server process failed after executing a request with a memory allocation failure during capture, therefore, replaying of the request was not possible.

Cause: Duplicate KEEP or NOKEEP was specified, or both KEEP and NOKEEP were specified.

Cause: Application continuity protocol was violated.

Cause: The replay context was not valid.

Cause: The block size sent by remote server was zero.

Cause: The application ended its database request or released the connection to the connection pool, thereby disabling replay mode.

Cause: A background, JOBQ slave or PQ slave attempted to use an incoming database link connection and such usage is not supported.

Cause: The initial session state at replay did not match the state at the beginning of the request.

Cause: The request was unable to replay because it was part of a Two-Phase Commit (2PC) transaction managed by the Transaction Processing Monitor (TPM).

Cause: Unable to obtain session state classification information.

Cause: The client session environment could not be restored to the original values.

Cause: The client session environment could not be verified for a failover of the first statement in a series.

Cause: The application executed an operation with side effects, which disabled Application Continuity for this request.

Cause: An attempt was made to enable or disable a connection test that did not exist or to delete a predefined connection test.

Cause: Application Continuity did not support ISOLATION_LEVEL=SERIALIZABLE.

Cause: It is illegal to have an open transaction when starting a new request or at the end of a request.

Cause: The application passed to an Oracle Call Interface (OCI) function an argument value that was not supported with transactional failover.

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

Cause: The provided session template did not exist or was corrupt.

Cause: An invalid property was specified for the rule class.

Cause: The user does not have required privileges on the object.

Cause: An attempt was made to grant an invalid privilege on a rule class.

Cause: An attempt was made to revoke a privilege that was never granted.

Cause: An attempt was made to specify a schema extended name for an event structure, a rule class, or an action call-back procedure.

Cause: An attempt was made to create a rule class with a name that is already used by an existing object.

Cause: rule class creation failed with a recursive error.

Cause: An attempt was made to access a rule class that does not exist or is not accessible.

Cause: An invalid name was specified for the rule class.

Cause: An attempt was made to create a callback procedure with a name that is already used for an existing object.

Cause: An attempt was made to use a duplicate rule identifier.

Cause: Incorrect values were specified for the action preferences.

Cause: An attempt was made to use an invalid action preference.

Cause: Values for one or more action preferences were not specified.

Cause: Too many entries were specified in the action preference values list. The action preference values list should not have more entries than the action preference names list.

Cause: The operation failed because the action callback procedure associated with the rule class has compilation errors.

Cause: An attempt was made to create an action preference with the same name as an attribute in the event structure.

Cause: Invalid rule identifier was used to operate on a rule definition.

Cause: An attempt was made to use a rule manager feature that is currently not supported.

Cause: An attempt was made to specify an invalid ordering property for the rule class.

Cause: An attempt was made to specify an invalid ordering property for the rule class.

Cause: In the rule class properties, the name used for one or the primitive event objects was not found in the corresponding composite event structure.

Cause: An attempt was made to create a rule class with autocommit enabled when the duration of events is set to TRANSACTION.

Cause: An attempt was made to specify a SESSION or TRANSACTION duration policy for the primitive objects.

Cause: The object type that represents the event structure was not created in the user's schema.

Cause: An invalid XML element was used in the properties specification for the rule class.

Cause: The object type specified for the event structure was in an inconsistent state.

Cause: An invalid or unsupported XML attribute was used in the rule class properties.

Cause: An attempt was made to reuse an object type (event structure) for composite events when it is already configured for simple events.

Cause: An invalid value was specified for an attribute in the rule class properties.

Cause: An attempt was made to specify a child element or a text node in invalid position in the rule class properties specification.

Cause: An attempt was made to assign an invalid value for an attribute in the rule class properties.

Cause: An attempt was made to use an unsupported configuration for the rule class.

Cause: Invalid value was specified for the duration attribute in the rule class properties.

Cause: An attempt was made to use an invalid unit of time for the rule class's duration specification. Valid units are : minutes, hours, and days.

Cause: An attempt was made to specify a duration policy for the primitive events when the composite event was configured with TRANSACTION or SESSION duration policy.

Cause: The name attribute of the object element in the rule class properties was not specified. This is a required value.

Cause: An attempt was made to specify an invalid attribute for an XML element in the rule condition.

Cause: An attempt was made to specify an invalid child element or text node for an XML element in the rule condition.

Cause: An attempt was made to use an invalid element or a valid element in invalid position in the rule condition.

Cause: An attempt was made to specify an invalid or empty rule condition.

Cause: The rule condition was specified without a required element.

Cause: An attempt was made to specify an invalid attribute for an element in the rule condition.

Cause: An attempt was made to specify an invalid attribute for an element in the rule condition.

Cause: An attempt was made to specify the same XML tag in more than one positions within a single rule condition.

Cause: One of the required attributes was not specified in the rule condition.

Cause: An attempt was made to specify a "not" element within an "any" element in the rule condition.

Cause: An attempt was made to specify an invalid sequence of elements within a parent element.

Cause: An attempt was made to add an invalid rule condition to a rule set defined for composite events.

Cause: A composite event structure may only have attributes that are either table aliases or of an object type that is defined in the owner's schema.

Cause: An attempt was made to configure an object type that has one or more dependents as a event structure. The object type cannot be modified due to the dependent objects.

Cause: An invalid value is assigned to the equal attribute in the rule condition.

Cause: The value specified for the "count" attribute of the "any" element is greater than or equal to the the number of primitive events appearing in the rule condition.

Cause: An attempt was made to use "sequence" attribute when there is an insufficient number of primitive events in the rule conditions.

Cause: An attempt was made to use a rule condition construct that is not supported in the current release.

Cause: An attempt was made to use fewer than two elements within an "and" or "notany" element.

Cause: An attempt was made to drop an internal object that is required for a rule class.

Cause: An invalid value is assigned to the count attribute in the rule condition. The values should be a positive integer that is smaller than the number of object elements within the "any" element.

Cause: An attempt was made to use an invalid primitive event in a rule condition.

Cause: An attempt was made to configure the rule class with an ordering property that is longer than 240 characters.

Cause: An attempt was made to use a rule class configuration that was not supported.

Cause: An attempt was made to create a composite event structure with more than 32 primitive events.

Cause: An attempt was made to use "equal" or "sequence" attribute when the "count". attribute in a rule condition with "any" semantics is set to 1.

Cause: An attempt was made to use EXCLUSIVE consumption policy for a primitive event when the composite event is configured for RULE consumption policy.

Cause: An attempt was made to use an EXCLUSIVE consumption policy with no autocommit and a duration other than TRANSACTION or SESSION.

Cause: The user input has undefined element or attribute according to the provided XML schema definition.

Cause: An attempt was made to use a duplicate name for the rule class results view.

Cause: An attempt was made to use an invalid operation for the rule class.

Cause: An attempt was made to pass an empty list of primitive event identifiers to the CONSUME_PRIM_EVENTS API.

Cause: An attempt was made to specify a duplicate or invalid primitive event for the rule class's equal property.

Cause: The table used for an event structure has the same name as another table or a primitive event type in the event structure.

Cause: An attempt was made to pass a NULL or invalid rowid for a table in the event structure.

Cause: An attempt was made to use sequence attribute in a rule condition that is defined using table aliases. Sequence usage is not permitted for the lack of timestamp attribute.

Cause: An attempt was made to use the dmlevents policy for an event structure with no table alias constructs.

Cause: An attempt was made to use the dmlevents policy for a rule class that refers to table residing in different schema. To use the dmlevents policy, the table associated with table aliases in the event structure and the rule class should exist in the same schema.

Cause: An attempt was made to use the dmlevents policy for a primitive event defined with more than one table alias attribute.

Cause: Triggers could not be created on the data table to track DML events.

Cause: An attempt was made to use dmlevents policy in combination with autocommit set to YES. This combination is not allowed.

Cause: An attempt was made to use the dmlevents policy for an event structure not containing any table alias attributes.

Cause: An attempt was made to use a Scheduler process that does not exist.

Cause: The background process that cleans up the expired events failed for a rule class.

Cause: An attempt was made to use a rule class package with invalid signature or permissions.

Cause: A rule matching the current event is locked by another session.

Cause: An attempt was made to insert or update a value other than 'Y' or 'N' into the RLM$ENABLED column of a rule class table.

Cause: An invalid attribute value was specified for the "windowlen" or the "windowsize" attribute. The value specified for the "windowlen" attribute should be a number indicating the number of days or a fraction of a day. The value specified for the "windowsize" attribute should be an integer which indicates number of items in the collection. The maximum value allowed for the window specification is 64000.

Cause: An attempt was made to define a rule condition with "collection" element when the corresponding event was not configured for collections of events.

Cause: The attributes listed in the "groupby" specification in a rule condition were not a subset of the attributes specified in the rule class properties.

Cause: An invalid value was specified for the "groupby" attribute.

Cause: An attempt was made to insert a rule condition with invalid collection element specification.

Cause: An attempt was made to specify more than 32 expressions for the "groupby" clause in rule class properties.

Cause: The aggregate operation specified in the rule condition was invalid.

Cause: An attempt was made to use an unsupported aggregate operator in the having or the compute clause in the rule condition.

Cause: An attempt was made to apply an aggregate operator on an invalid attribute or an attribute with invalid or unsupported data type in the aggregate operator. Only NUMBER and DATE attributes are allowed in the aggregate operators.

Cause: An attempt was made to specify an invalid equal clause for a rule condition or the rule class properties.

Cause: An attempt was made to specify fewer than two elements in the equal clause for a rule condition or the rule class properties.

Cause: An attempt was made to use an invalid relational operator in the having clause of the rule condition.

Cause: An attempt was made to specify an aggregate predicate across multiple primitive event types with no attribute prefix.

Cause: An attempt was made to use an attribute where a literal is expected in the aggregate predicate in the rule condition.

Cause: An attempt was made to specify more than 5 aggregate operations in a rule condition.

Cause: A table storing the primitive rule conditions was already assigned to the event structure.

Cause: An attempt was made to truncate or drop a conditions table when one or more rule classes are associated to it through the event structure.

Cause: An attempt was made to use an invalid conditions table.

Cause: An attempt was made to use both a condition and a "ref" attribute in the "object" element.

Cause: An attempt was made to use a reference to a nonexistent conditions table or a condition.

Cause: An attempt was made to drop a conditions table with a DROP TABLE command.

Cause: An attempt was made to delete a condition when one or more rule conditions refer to it.

Cause: An attempt was made to define a collection rule condition with unsupported constructs.

Cause: An attempt was made to update the identifier of a row stored in the conditions table.

Cause: An attempt was made to specify an aggregate operator on an event that is not identified as collection.

Cause: An invalid attribute is used in the specification for the having clause of the rule condition.

Cause: An attempt was made to use a collection element with no groupby specification in the rule condition.

Cause: An attempt was made to use the windowlen and windowsize attributes within the same collection element.

Cause: An attempt was made to use the windowlen or windowsize attributes when the events are configured for SESSION or TRANSACTION duration.

Cause: An attempt was made to specify both the DMLEVENTS and CNFEVENTS for the same rule class.

Cause: An attempt was made to use CNFEVENTS property with insufficient privileges.

Cause: An attempt was made to change the logical structure of a materialized view log, queue table, or a partition by specifying a non-NULL column mapping during online redefinition.

Cause: An attempt was made to redefine a partition which is not involved in this redefinition.

Cause: A partition was involved in this redefinition but was not specified.

Cause: An attempt was made to complete an instantiation-deferred redefinition without invoking dbms_redefinition.sync_interim_table.

Cause: An unknown redefinition method was used.

Cause: An attempt was made to register dependent objects when redefining a partition.

Cause: An attempt was made to unregister dependent objects when redefining a partition.

Cause: An error occurred while instantiating the online redefinition which requires aborting the redefinition.

Cause: An error occurred while synchronizing the online redefinition.

Cause: An error occurred while synchronizing the online redefinition which requires aborting the redefinition.

Cause: An error occurred while completing the online redefinition.

Cause: An error occurred while completing the online redefinition which requires aborting the redefinition.

Cause: An attempt was made to create a table that is not an index-organized table (IOT) as the interim table of an AQ IOT table (history, time management, or dequeue).

Cause: An online redefinition of an AQ table was unable to lock all related AQ objects.

Cause: An online redefinition of an AQ table was unable to log changes made to AQ tables during the redefinition.

Cause: The number of columns, or the type or the length semantics of a column, in the interim table did not match the specified column mapping.

Cause: An attempt was made to create an AQ table as an interim table of an online redefined AQ table.

Cause: interim table is incompatible with partition being redefined because one or more of the following apply: - one is index-organized and the other is not - one has IOT overflow segment and the other does not - one has IOT mapping table and the other does not

Cause: both original and interim tables are partitioned, or original table is composite-partitioned but interim table is non-partitioned.

Cause: An unsupported type of interim table was provided during the partition redefinition. Currently the following types of interim tables are not supported: - a nested table or has nested-table columns - an external table - part of cluster - contains LOB shared segments

Cause: original/interim table was created with row dependency and interim/original table was not.

Cause: An attempt was made to online redefine a partition with nested table columns.

Cause: An attempt was made to perform online redefinition on an AQ table that was created with compatibility prior to release 8.1.x.

Cause: An attempt was made to use a partitioned table as an interim table.

Cause: An attempt was made to use method of DBMS_REDEFINITION.CONS_USE_ROWID to redefine an AQ IOT table.

Cause: Duplicated rows are detected during instantiation of the redefinition.

Cause: An attempt was made to redefine an object online that is not a table.

Cause: An attempt was made to register a nonexistent materialized view log as a dependent object.

Cause: An attempt was made to redefine a table which is incompatible with another ongoing redefinition.

Cause: An attempt was made to redefine a table which had a commit SCN-based materialzed view log defined on it.

Cause: An attempt was made to use an interim table which had a commit SCN-based materialzed view log defined on it.

Cause: An attempt was made to redefine a table which had Flashback Data Archive enabled.

Cause: An attempt was made to redefine a table with an interim table which had Flashback Data Archive enabled.

Cause: An attempt was made to redefine a table which is a CDC table.

Cause: An attempt was made to redefine an IOT table with CONS_USE_ROWID.

Cause: An attempt was made to redefine a temporary table.

Cause: An attempt was made to redefine a table with IOT overflow segment.

Cause: An attempt was made to redefine a table with a CDC log defined on it.

Cause: An attempt was made to redefine a table with Fine Grained Auditing (FGA) or Row Level Security (RLS) enabled.

Cause: An attempt was made to redefine a table with a column of binary XML type.

Cause: An attempt was made to redefine a table with nested table columns.

Cause: During FINISH_REDEF_TABLE procedure, the elapsed time waiting to acquire a table or partition DML lock on the original table exceeds the timeout the user specified.

Cause: An attempt was made to specify CONS_VPD_AUTO for non-null column mapping other than null column mapping. CONS_VPD_AUTO can only be specified for null column mapping.

Cause: Virtual Private Database (VPD) policies with non-null predicate against the table owner or redefinition invoker existed on the original table.

Cause: An attempt was made to set the COPY_VPD_OPT value to CONS_VPD_NONE. COPY_VPD_OPT cannot be set to CONS_VPD_NONE with Virtual Private Database (VPD) policies on the original table.

Cause: An attempt was made to set the COPY_VPD_OPT value to either CONS_VPD_NONE or CONS_VPD_AUTO. Cannot set the COPY_VPD_OPT value to CONS_VPD_NONE or CONS_VPD_AUTO with Virtual Private Database (VPD) policies on the interim table.

Cause: An unknown COPY_VPD_OPT value was used.

Cause: An attempt was made to set the COPY_VPD_OPT value to CONS_VPD_AUTO for Virtual Private Database (VPD) policies with application context. Automatic copying of VPD policies with application context is not supported in online redefinition.

Cause: An online redefinition procedure was passed multiple original tables and multiple partitions to redefine.

Cause: An attempt was made to set the COPY_VPD_OPT value to CONS_VPD_MANUAL. COPY_VPD_OPT cannot be set to CONS_VPD_MANUAL when redefining a partition.

Cause: An online redefinition procedure was passed a partition name list containing duplicates.

Cause: An attempt was made to redefine a table with an interim table on which a materialized view or zonemap was defined.

Cause: An attempt was made to redefine a table with Oracle Label Security (OLS) or Extensible Data Security (XDS) enabled.

Cause: An attempt was made to redefine a table with XML indexes having an Unstructured XMLIndex (UXI) component.

Cause: An attempt was made to redefine a table with an interim table that was a system-partitioned table.

Cause: An attempt was made to enable lock free finish redef for current redefinition, but lock free was not feasible.

Cause: The UPDATE statement passed to DBMS_REDEFINITION.EXECUTE_UPDATE was not supported.

Cause: An UPDATE statement passed to the DBMS_REDEFINITION.EXECUTE_UPDATE method attempted to update a table with a trigger on UPDATE, which is not supported.

Cause: An UPDATE statement passed to the DBMS_REDEFINITION.EXECUTE_UPDATE method attempted to update a table with a nested table column, which is not supported.

Cause: An UPDATE statement passed to the DBMS_REDEFINITION.EXECUTE_UPDATE method attempted to update a typed table or a table with an ADT column, which is not supported.

Cause: An attempt was made to pass an UPDATE statement with a partition extended name to the DBMS_REDEFINITION.EXECUTE_UPDATE method, which is not supported.

Cause: An attempt was made to pass an invalid UPDATE statement to the DBMS_REDEFINITION.EXECUTE_UPDATE method.

Cause: An attempt was made to redefine an Advanced Queueing (AQ) table with the REDEF_TABLE() procedure.

Cause: An attempt was made to redefine a clustered table to modify the tablespace or compression type with the REDEF_TABLE() procedure.

Cause: There was an invalid column mapping with invisible columns on the original or interim table.

Cause: ENABLE_ROLLBACK and COPY_VPD_OPT were both set to TRUE.

Cause: Tables in the redefinition are either an object, advanced queue or index-organized table.

Cause: ENABLE_ROLLBACK was not set to TRUE during START_REDEF_TABLE.

Cause: ENABLE_ROLLBACK was set to TRUE along with DML_LOCK_TIMEOUT set to -1.

Cause: An attempt was made to redefine a table that has a LONG column with the REDEF_TABLE() procedure.

Cause: An attempt was made to redefine an external table or a fixed table.

Cause: An UPDATE statement passed to the DBMS_REDEFINITION.EXECUTE_UPDATE method attempted to update a table with Virtual Private Database (VPD) policy.

Cause: ENABLE_ROLLBACK was not set to TRUE during START_REDEF_TABLE.

Cause: An attempt was made to use DBMS_REDEFINITION on a table on single table hash clusters.

Cause: An attempt was made with Oracle Virtual Private Database (VPD) policy to enforce column security on a column with unsupported operator type.

Cause: An attempt was made to use the DBMS_REDEFINITION package on a clustered table without a cluster index or with a virtual cluster index.

Cause: Rollback was initiated as part of the previous call to FINISH_REDEF_TABLE.

Cause: ABORT_ROLLBACK was called without starting the rollback operation.

Cause: ABORT_REDEF_TABLE was called when ROLLBACK was active.

Cause: An UPDATE statement passed to the DBMS_REDEFINITION.EXECUTE_UPDATE method attempted to update a table with a hidden column, which is not supported.

Cause: An attempt was made to redefine a table that had a staging log.

Cause: An attempt was made to redefine a table that had inconsistent sharing with an interim table.

Cause: An attempt was made to enable ROLLBACK on a table with row movement enabled in the redefinition.

Cause: An attempt was made to enable ROLLBACK on a nested table.

Cause: An attempt was made to enable ROLLBACK on a clustered table.

Cause: The specified column mapping string included an identity column.

Cause: An attempt was made to use EXECUTE_UPDATE when the update statement contained ROWID.

Cause: An attempt was made to online redef a table when either the original table or the interim table did not have ROW ARCHIVAL.

Cause: An attempt was made to redefine a table with automatic Oracle GoldenGate conflict detection and resolution (CDR) enabled.

Cause: An attempt was made to redefine a delete tombstone table.

Cause: An attempt was made to rename a user whose schema contained a type on which some table depends. The operation may not proceed as it would render the table invalid causing loss of data.

Cause: An attempt was made to create a schema synonym for one of the reserved schemas (such as SYS or SYSTEM.)

Cause: An attempt was made to rename one of the following: - reserved user (such as SYS or SYSTEM) - an administrative user - a common user - a locked user account

Cause: An attempt was made to create a schema synonym for a schema which did not exist.

Cause: The named schema synonym did not exist.

Cause: The RENAME TO clause was specified twice.

Cause: There was already a user, role or schema synonym with that name.

Cause: There was already a user, role or schema synonym with that name.

Cause: There was already a user, role or schema synonym with that name.

Cause: There was no user, role, or schema synonym by that name.

Cause: An attempt was made to drop a schema synonym for a schema of a user who was logged on.

Cause: An attempt was made to rename a user that was logged on.

Cause: An attempt was made to create an Editioning view on a table on which another Editioning view is already defined in the same Edition. This violates a restriction that at most one Editioning view may be associated with any base table in a given Edition.

Cause: An attempt was made to create an Editioning view referring to a synonym, which is not supported.

Cause: An attempt was made to create an Editioning view referring to remote tables, which is not supported.

Cause: An attempt was made create an Editioning view referencing the same column of a base table more than once, which is not supported.

Cause: An attempt was made to create an Editioning view in a schema different from that of the base table.

Cause: An attempt was made to replace an Editioning view with a view which is not an Editioning view or vice versa.

Cause: An attempt was made to create a CrossEdition trigger on an Editioning view, which is not supported.

Cause: An attempt was made to define an Editioning view containing a column referring to an entity other than a base table column (for example, a PL/SQL function without a parameter), which is not supported.

Cause: An attempt was made to set a read-only table in read-only mode.

Cause: An attempt was made to set a read/write view in read/write mode.

Cause: The view being altered was not an Editioning view. In this release, an ALTER VIEW READ ONLY, or ALTER VIEW READ WRITE operation is only permitted on Editioning views.

Cause: ALTER VIEW READ ONLY and ALTER VIEW READ WRITE are not permitted on Editioning views which have compilation errors.

Cause: ALTER VIEW READ ONLY and ALTER VIEW READ WRITE are not permitted on Editioning views which are marked invalid.

Cause: An attempt was made to create an editioning view in a schema where views were not editionable.

Cause: An attempt was made to insert, delete, or update row(s) of a view created with read-only option. DML operations on such views are explicitly prohibited.

Cause: An attempt was made to add an attribute association which was already attached to shared context-sensitive policies with the specified policy function. All shared context-sensitive policies with a common policy function need to have the same set of attribute associations. Attribute associations of an existing shared context-sensitive policy which is using the specified policy function will be automatically added to the new policy.

Cause: The value was not set for every attribute association of the shared context-sensitive policy. The value must be set for every attribute association of the shared context-sensitive policy.

Cause: An existing shared context-sensitive policy using the specified policy function was dropped from another session.

Cause: The object being accessed had a Row-Level Security (RLS) policy defined on it and the VERSIONS clause contained a bind variable.

Cause: The object being accessed had a Virtual Private Database (VPD) policy defined on it and the DML which is executed could disclose rows protected by the VPD policy.

Cause: A maximum of 255 Virtual Private Database (VPD) policies that can be enforced on an object was exceeded.

Cause: Oracle Label Security (OLS) policy creation was attempted in application root.

Cause: An attempt was made to enforce Oracle Label Security (OLS) policy on common or application objects.

Cause: An attempt was made to use the virtual column as an Oracle Label Security (OLS) policy column.

Cause: An attempt was made to assign Oracle Label Security (OLS) authorizations to common or application users.

Cause: The user did not have permission to bypass reads for Oracle Label Security policies.

Cause: An attempt was made to enforce Oracle Label Security (OLS) policy to external tables.

Cause: An attempt was made to assign a non-existing Oracle Label Security (OLS) data label as a row label in an OLS-OID configuration.

Cause: An attempt was made to enforce Oracle Label Security (OLS) policy with labeling function when Oracle Database Vault operations control was enabled.