Cause: The geometry did not start from the correct level in the hierarchy.

Cause: The geometry contained one or more unexpected holes.

Cause: The solid geometry was not closed i.e., faces of solid are not 2-manifold due to incorrectly defined, oriented, or traversed line segment because each edge of a solid must be traversed exactly twice, once in one direction and once in the reverse direction.

Cause: The orientation of the solid was not correct.

Cause: The geometry contained more than one outer geometry.

Cause: The ring was not flat.

Cause: The 3-D geometry contained one or more compound curves, which are not supported for 3-D geometries.

Cause: The multipoint geometry had two points that either had identical coordinates or were the same point considering the geometry tolerance.

Cause: The multisolid geometry contained one or more fully or partially overlapping surfaces.

Cause: To connect solids in a composite solid geometry, at least one of the faces of a solid must be shared (fully or partially) with only another solid. However, at least one of the faces in this composite solid was not shared by exactly two solids only.

Cause: An outer geometry was found when only inner geometries were expected.

Cause: An inner solid had a common edge with outer solid.

Cause: A solid geometry contained an inner solid with at least one vertex outside its corresponding outer solid.

Cause: One or more faces of an inner solid surface either fully or partially overlapped an outer solid surface.

Cause: A multipolygon geometry contained one or more common (shared, fully or partially overlapped) polygons.

Cause: Outer rings, either on the same plane or different planes, in a composite surface intersected.

Cause: The conditional flag was set, and a composite surface had at least two outer rings sharing a common edge on the same plane.

Cause: An outer ring in a composite surface shared a common area with another outer ring.

Cause: A shared edge (one shared by two polygons) in a composite surface was not correctly oriented. Each shared edge must be oriented in one direction with respect to its first polygon and then in the reverse direction with respect to its second polygon.

Cause: Not all polygons of a surface had a common (fully or partially shared) edge.

Cause: An inner ring was not on the same plane as its outer ring.

Cause: An inner ring either was not inside its outer ring or touched its outer ring more than once.

Cause: Two inner rings of the same outer ring intersected or shared a boundary.

Cause: Two inner rings of the same outer ring touched more than once.

Cause: An inner ring was inside another ring of the same outer ring.

Cause: The rectangular box in shortcut format did not have its first x,y,z coordinates either all greater or less than its second x,y,z coordinates.

Cause: The extraction could not be performed because the multi or composite geometry must first be decomposed into simple geometries (with or without inner geometries). The multi or composite geometry had a gtype of GTYPE_MULTISOLID, GTYPE_MULTISURFACE, GTYPE_MULTICURVE, GTYPE_MULTIPOINT, or GTYPE_COLLECTION, or the geometry was a line string.

Cause: A MULTICOMP_TOSIMPLE parameter to element extractor was attempted on a geometry that is already simple.

Cause: An INNER_OUTER parameter to element extractor was attempted on a surface that was not simple or composite.

Cause: The geometry did not have the multi-level hierarchy required for this operation. For example, if the parameter to element extractor (hierarchy level) is not LOWER_LEVEL, but the geometry etype is ETYPE_SOLID and gtype is GTYPE_SOLID, an extract operation is not allowed, because a simple solid can only be decomposed into lower level geometries, such as composite surfaces.

Cause: An invalid etype was encountered.

Cause: The orientation of the current geometry was not valid.

Cause: The end of composite surface was reached before all necessary surfaces were defined.

Cause: The etype of the composite surface of a solid was not valid.

Cause: The elemInfo definition was not correct for the surface of the axis aligned box.

Cause: The axis aligned box surface was not on the yz, xz, or xy plane.

Cause: The inner geometry etype did not start with 2, or the outer geometry etype did not start with 1, or both occurred.

Cause: The rectangular surface in shortcut format did not have its first x,y,z coordinates all greater than or equal to or all less than or equal to its second x,y,z coordinates.

Cause: The gtype of the geometry was not GTYPE_SOLID, GTYPE_SURFACE, GTYPE_CURVE or GTYPE_POINT.

Cause: The geometry had errors in it.

Cause: One of the geometries had holes, and the geometries were neither (A) simple, composite, or multisurfaces, or (B) simple, composite, or multisolids. (Surfaces and solids are the only geometries that can have holes. Points and curves cannot have holes.)

Cause: The holes were defined with incorrect etype.

Cause: The solid geometry having one outer and multiple inner geometries had a negative or zero volume.

Cause: The COUNT_SHARED_EDGES parameter value was not 1 or 2.

Cause: The input geometry gtype was not GTYPE_POLYGON.

Cause: The input 2-D polygon did not have only one outer ring.

Cause: The 2-D polygon violated the rules for polygons and rings.

Cause: The sizes of grdHeight and Height arrays were not equal to half the size of input 2-D polygon's ordinates array. As a result, each point in the 2-D polygon could not be extruded from the grdHeight entry to the Height entry.

Cause: In the definition of a solid, the height values were less than the ground height.

Cause: The geometry could not be appended to a homogeneous collection (for example, multi-geometry) or to a heterogeneous geometry (for example, collection). In other words, the gtype of the geometry to be appended was neither GYTPE_COLLECTION or GTYPE_MULTI-X (where X is point, curve, surface, or solid).

Cause: An arc was defined in a geometry type in which arcs are not supported. Arcs are supported for 2-D (circle) polygons, 2-D compound polygons, 2-D single arc, and 2-D compound (composite) curves only.

Cause: The geometry did not have three dimensions.

Cause: A 3-D geometry was passed into an operation that supports only 2-D geometries.

Cause: The end of composite solid was reached before all necessary solids were defined.

Cause: In extruding a 2D polygon into a 3D geometry, the SRID conversion function did not find an equivalent 3D SRID of the 2D SRID.

Cause: A query element geometry and a source geometry were the same, which prevented a label pointing query element in the source geometry from being output.

Cause: A query element was a collection geometry or a multitype geometry. Such geometries are not permitted in a query element because they are at the top of the geometry hierarchy. A query element must be part of the source geometry.

Cause: An invalid or unknown parameter was specified in the creation of Point Cloud.

Cause: The specified table for loading points into a Point Cloud did not exist.

Cause: The specified total dimensionality for the Point Cloud exceeded the maximum limit of 8.

Cause: The input points table had no data.

Cause: Transient tables/views from a previous CREATE_PC operation were still in existence.

Cause: An internal read error occurred during Point Cloud creation.

Cause: An internal LOB write error occurred during Point Cloud creation. The cause might be lack of table space.

Cause: The extent of the Point Cloud was null.

Cause: The extent of the Point Cloud was more than 2-D for geodetic data.

Cause: The base table or schema, or both, were invalid strings; or the base table and schema combination did not exist.

Cause: The necessary privileges to create the trigger were not granted.

Cause: The specified block table name was not unique. For example, it might have been used for another block table.

Cause: An internal error occurred.

Cause: The input Point Cloud for the CLIP_PC operation was invalid.

Cause: The Point Cloud and the query geometry had incompatible SRID values.

Cause: Both the query and BLKID parameters were null in the call to the CLIP_PC operation.

Cause: An internal error occurred.

Cause: The specified TOTAL_DIMENSIONALITY was invalid.

Cause: An internal error occurred.

Cause: An internal error occurred.

Cause: An internal error occurred.

Cause: Scratch tables/views could not be created because they already existed.

Cause: An invalid string was specified for the SORT_DIMENSION.

Cause: An invalid string was specified for the WORKTABLESPACE parameter.

Cause: The names for the input/output tables were invalid, or the tables did not exist or did not have the right structure.

Cause: An invalid or unknown parameter was specified in the creation of the TIN.

Cause: The specified table for loading points into a TIN did not exist.

Cause: The specified total dimensionality for the TIN exceeded the maximum limit of 8.

Cause: The input points table had no data.

Cause: Transient tables from previous CREATE_TIN operation still existed.

Cause: An internal read error occurred during TIN creation.

Cause: An internal LOB write error occurred during TIN creation. The cause might be lack of table space.

Cause: The extent of the TIN was null.

Cause: The extent of the TIN was more than 2-D for geodetic data.

Cause: The input TIN for the CLIP_TIN operation was invalid.

Cause: The TIN and the query geometry had incompatible SRID values.

Cause: Both the query and blkid parameters were null in the call to the CLIP_TIN operation.

Cause: An internal error occurred.

Cause: An internal error occurred.

Cause: An internal error occurred.

Cause: A query element geometry was at a higher level in the geometry hierarchy than the source geometry.

Cause: A query element geometry was not a part of the source geometry.

Cause: A 2D SRID was used with a 3D geometry.

Cause: There was an error in the Spatial Web Services operation or the parameters.

Cause: Web Coverage Service (WCS) metadata tables were not found.

Cause: The Web Coverage Service (WCS) operation required temporary tables, but these tables did not exist.

Cause: Web Coverage Service (WCS) parameter values were invalid, the user had insufficient privileges, or the coverage was already published.

Cause: Parameters were invalid or privileges were insufficient.

Cause: The XML schema could not be found.

Cause: Either the Catalog Services for the Web (CSW) user table, the SRID parameter, the metadata ID, or the XML schema definition (XSD) type was incorrect.

Cause: The XQuery Full Text (XQFT) index could not be dropped or created for the Catalog Services for the Web (CSW) user table.

Cause: A Catalog Services for the Web (CSW) server-side error occurred.

Cause: A Catalog Services for the Web (CSW) client-side error occurred.

Cause: Java exceptions.

Cause: No matching category ID could be found.

Cause: No matching scheme could be found for the input data format.

Cause: No matching level could be found for the input data format.

Cause: No matching option could be found for the input data format.

Cause: Invalid field value.

Cause: Invalid input field.

Cause: Error occurred when idcode translator tried to evaluate the rule specified in the tag data translation XML.

Cause: Necessary field values were missing.

Cause: The specified model could not be found.

Cause: The specified rulebase could not be found.

Cause: Sufficient privileges were not granted.

Cause: SDO_RDF_TRIPLE_S constructor failed.

Cause: The reuse-bNode model-id specified for the SDO_RDF_TRIPLE_S constructor was neither 0 nor the model-id of the target model.

Cause: Unsupported reification constructor functions were used.

Cause: The value type of this component of the RDF triple was invalid.

Cause: The value type of this lexical value was invalid.

Cause: The time zone of this lexical value was invalid.

Cause: Attempts to resolve hash collision exceeded the maximum retry count.

Cause: Attempts to insert the specified lexical value failed.

Cause: The value type of this long (length > 4000) lexical value was invalid.

Cause: Attempts to insert triple failed.

Cause: The SDO_RDF_TRIPLE_S constructor without bNode reuse option was invalid for triple containing bNode.

Cause: Specified temporary table name was not valid.

Cause: The batch load operation failed.

Cause: This column of the table was not associated with the specified model.

Cause: A model with the specified name was already present.

Cause: At model creation time, the table column contained data.

Cause: The attempt to create the specified model did not succeed.

Cause: The attempt to drop the specified model did not succeed.

Cause: Attempt to create the network failed because the network already existed.

Cause: An attempt was made to drop a network that contained one or more models.

Cause: An attempt was made to drop a network that contained one or more rulebases.

Cause: Rulebases for the operation were not specified.

Cause: A rulebase or rules index with the specified name already existed.

Cause: The attempt to create the specified rules index did not succeed.

Cause: The specified rule created an invalid triple containing a literal in the subject or predicate position.

Cause: The attempt to create the specified literal value failed.

Cause: The specified model occurred more than once in the list of models.

Cause: The specified rulebase or rules index was busy and could not be used.

Cause: The user could not be dropped because it owns RDF objects.

Cause: A virtual model was used as input instead of a model.

Cause: The specified virtual model could not be found.

Cause: The specified virtual model name was not valid.

Cause: An empty list of models was specified as the set of models for a virtual model.

Cause: An attempt was made to create a virtual model without the appropriate privileges.

Cause: A virtual model or rules index with the specified name was already present.

Cause: A model with the specified name was already present.

Cause: A virtual model with identical components was already present.

Cause: A rules index did not exist for the specified sets of models and rulebases.

Cause: An attempt was made to use an out-of-range index for retrieving the label.

Cause: An attempt was made to use an undefined label.

Cause: An attempt was made to specify an invalid dependent component for the label generator.

Cause: An attempt was made to use an invalid label generator to generate labels for inferred data.

Cause: An attempt was made to use a label generator when Oracle Label Security (OLS) was not enabled for Resource Definition Framework (RDF) data.

Cause: An attempt was made to specify an invalid label generation option for entailment involving user rules.

Cause: The chosen label generation option required proof, which was missing for the entailment.

Cause: An invalid label generator option was chosen for entailment.

Cause: Oracle Label Security (OLS) support for Resource Definition Framework (RDF) was not installed.

Cause: An attempt was made to use an unsupported Oracle Label Security (OLS) option for Resource Definition Framework (RDF) data.

Cause: An attempt was made to use an unsupported secure access option for Resource Definition Framework (RDF).

Cause: The necessary privileges needed to administer Oracle Label Security (OLS) or Oracle Virtual Private Database (VPD) policies for Resource Definition Framework (RDF) data were not specified.

Cause: An attempt was made to use an invalid column to maintain labels for Resource Definition Framework (RDF) data.

Cause: An attempt was made to use a nonexistent policy.

Cause: An attempt was made to perform an operation that required Resource Definition Framework (RDF) network to be present.

Cause: An attempt was made to perform an RDF-OLS-specific operation when Oracle Label Security (OLS) was not enabled for Resource Definition Framework (RDF) data.

Cause: An attempt was made to perform a Resource Definition Framework (RDF) secure access operation with restricted privileges.

Cause: An attempt was made to reset Oracle Label Security (OLS) labels for a model with some data.

Cause: An attempt was made to perform an unauthorized DML operation on OLS-enabled Resource Definition Framework (RDF) repository.

Cause: An invalid value was specified for the resource position while setting labels.

Cause: An attempt was made to use a namespace map that contained one or more duplicate specifications.

Cause: An attempt was made to create an Oracle Virtual Private Database (VPD) policy in the SYS schema.

Cause: An attempt was made to specify a nonexistent context for the Oracle Virtual Private Database (VPD) policy.

Cause: An attempt was made to specify an invalid operation for the application of Oracle Virtual Private Database (VPD) policy.

Cause: An attempt was made to define invalid metadata elements for the Oracle Virtual Private Database (VPD) policy.

Cause: An attempt was made to make use of an undefined namespace prefix in Oracle Virtual Private Database (VPD) metadata.

Cause: An attempt was made to perform an invalid maintenance operation on Oracle Virtual Private Database (VPD) metadata.

Cause: An attempt was made to specify an empty match or apply pattern for a Oracle Virtual Private Database (VPD) constraint.

Cause: An invalid SQL identifier was specified for the constraint group.

Cause: The input parameter was not zero or a positive integer.

Cause: A rules index with the specified name has already been built for a different model-rulebase combination.

Cause: The entailed graph (rules index) already exists.

Cause: An unexpected internal error condition occurred.

Cause: URIs or literals used in the query did not exist in the database.

Cause: A table containing RDF data could not be dropped without first dropping its RDF model.

Cause: A table column containing RDF data could not be altered or dropped without first dropping its RDF model.

Cause: An internal error occurred during validation. The number of triples was less than 1 or the error indication marker was null.

Cause: An invalid error code was passed in during validation.

Cause: An internal error occurred during validation. Too many triples were passed in.

Cause: The query pattern specified in the SEM_MATCH query was null.

Cause: An attempt was made to drop a virtual model without the appropriate privileges.

Cause: The set of models used as input to a SEM_MATCH query contained a virtual model.

Cause: A rulebase was specified in conjunction with a virtual model as input to a SEM_MATCH query.

Cause: An attempt was made to use continually refreshed workspaces with Resource Definition Framework (RDF) data.

Cause: An attempt was made to use multi-parent workspaces with Resource Definition Framework (RDF) data.

Cause: An attempt was made to batch load data into a version- enabled Resource Definition Framework (RDF) model. This is not supported.

Cause: An attempt was made to create entailment for OLS/VPD-enabled models using unsupported API.

Cause: An attempt was made to create entailment for version- enabled models using unsupported API.

Cause: The specified rules index status was not recognized.

Cause: A valid rules index did not exist for specified combination of models and rulebases.

Cause: The predicate value passed in as an argument to the semantic operator did not exist in the model.

Cause: The object value passed in as an argument to the semantic operator did not exist in the model.

Cause: The parameter string used in the creation of an index of type SEM_INDEXTYPE had invalid or malformed parameters.

Cause: There was a syntax error in the call to the SEM_RELATED operator

Cause: Distance information was not generated during rules index creation.

Cause: An internal error occurred during a semantic operator query or during the creation of an index of type SEM_INDEXTYPE.

Cause: An attempt was made to run entailment with insufficient privileges for MDSYS schema.

Cause: An attempt was made to use a nonexistent Resource Definition Framework (RDF) model.

Cause: An attempt was made to associate labels with resource positions that were not secured with Oracle Label Security (OLS).

Cause: An attempt was made to reset a label for a resource that participated in triples with incompatible label.

Cause: An attempt was made to set a global label for a resource when an incompatible model-specific label already existed.

Cause: An attempt was made to specify a rule base that did not exist.

Cause: An attempt was made to set a label for a rule that did not exist.

Cause: An attempt was made to OLS-enable Resource Definition Framework (RDF) repository when one or more models is VPD-enabled.

Cause: An attempt was made to OLS-enable Resource Definition Framework (RDF) repository when one or more models is version-enabled.

Cause: An attempt was made to assign an Oracle Label Security (OLS) policy to Resource Definition Framework (RDF) data when some other policy was already in effect.

Cause: An attempt was made to version-enable a Resource Definition Framework (RDF) model which participated in a virtual model.

Cause: There was an internal error with Resource Definition Framework (RDF) OLS/VPS support.

Cause: An attempt was made to specify a duplicate Oracle Virtual Private Database (VPD) policy name.

Cause: An attempt was made to use a nonexistent Oracle Virtual Private Database (VPD) policy.

Cause: An attempt was made to drop an Oracle Virtual Private Database (VPD) policy with dependent models.

Cause: An attempt was made to VPD-enable a model which shared the application table with another model.

Cause: An attempt was made to assign Oracle Virtual Private Database (VPD) policy to a model with a VPD policy already in effect.

Cause: An attempt was made to VPD-enable a model that participated in a virtual model.

Cause: An attempt was made to VPD-enable a model with an Oracle Label Security (OLS) policy already in effect.

Cause: An attempt was made to VPD-enable a version-enabled Resource Definition Framework (RDF) repository. This is not supported.

Cause: An attempt was made to remove an Oracle Virtual Private Database (VPD) policy that was never assigned to the model.

Cause: An attempt was made to define metadata elements that had a circular dependency for the Oracle Virtual Private Database (VPD) policy.

Cause: An attempt was made to assign metadata directly to a property that was declared to be an equivalent of another.

Cause: An attempt was made to make a property equivalent of another when some metadata already existed for this property.

Cause: An attempt was made to make a property equivalent of another when some Oracle Virtual Private Database (VPD) constraints already existed for this property.

Cause: An attempt was made to add a duplicate metadata definition for an Oracle Virtual Private Database (VPD) policy.

Cause: An attempt was made to define conflicting metadata definitions for an Oracle Virtual Private Database (VPD) policy.

Cause: An attempt was made to assign an Oracle Virtual Private Database (VPD) constraint to a property declared to be an equivalent of another.

Cause: An attempt was made to specify a duplicate name for the Oracle Virtual Private Database (VPD) policy.

Cause: The Oracle Virtual Private Database (VPD) constraint had errors.

Cause: An attempt was made to operate on an Oracle Virtual Private Database (VPD) constraint that did not exist.

Cause: An attempt was made to execute a multi-model query where the models, as a set, did not have a unique Oracle Virtual Private Database (VPD) policy.

Cause: An attempt was made to version-enable an application table associated with multiple Resource Definition Framework (RDF) models.

Cause: An attempt was made to use an unsupported configuration for Resource Definition Framework (RDF) versioning.

Cause: An attempt was made to version-enable a model with Oracle Label Security (OLS) policy.

Cause: An attempt was made to version-enable a model with an Oracle Virtual Private Database (VPD) policy in effect.

Cause: None.

Cause: Flashback Transaction Backout was requested on a transaction that has not committed yet.

Cause: The specified transaction names for Flashback Transaction Backout was missing an SCN hint.

Cause: The SCN hit passed was not good. The SCN hit may have come after the start of any of the input transactions.

Cause: Transactions other than the ones specified conflicts with the specified transactions.

Cause: The Flashback Transaction Backout process encountered an interesting object which had its last DDL operation done on it after the mining start time. An interesting object is one that has been modified by either the specified transactions or any of their dependents.

Cause: A transaction in the dependency DAG performed some action that cannot be backed out. You can back out a transaction, only if undo has been logged for all of its operations. Note some operations do not log undo, such as Insert Direct Load and LOB changes. If you encounter a transaction that has performed any of these operations, you cannot back it out.

Cause: Mining error.

Cause: Null varrays passed or invalid input specified

Cause: One or more input transaction or any of its dependents are not committed or have been aborted after more than 1 minute of calling the backout function.

Cause: Mining could not start for the following reasons. 1. A logminer session was processing 2. The database was not mounted or not opened for read and write 3. Minimum supplemental logging was not enabled 4. Archiving was not enabled

Cause: There was a constraint violation exception when executing in NOCASCADE_FORCE mode. Users could also get this error if appropriate supplemental logging is not enabled causing constraint dependencies to go unnoticed.

Cause: One of the transactions in the dependency graph was a PDML transaction or a local transaction which is a branch of a global XA transaction, spanning multiple RAC instances. Currently flashback transaction does not support this type of transaction.

Cause: One of the transactions in the dependency graph touched an AQ table. As AQ externalizes database information, these transactions are not backed out, as the entire effects of the transaction cannot be seen from inside the database.

Cause: One of the transactions in the dependency graph is a DDL transaction and could not be backed out.

Cause: The start SCN provided was higher than the transaction start but below the transaction commit. The result was only partial changes for the given transaction.

Cause: None.

Cause: None.

Cause: Flashback Transaction Backout cannot work with missing changes. This error is thrown if we walk across a reset-logs branch, where we might have missed changes.

Cause: Flashback Transaction cannot work if there are regions in the mining range where supplemental logging is not enabled.

Cause: The logical change record shows that the compatibility of the mined redo is lower than version 11.0. Flashback transaction works only on redo versions 11.0 and above.

Cause: A failure occurred when trying to extend the temporary undo segment.

Cause: An attempt was made to issue too many recursive autonomous transactions causing the temporary undo segment to be out of slots.

Cause: An attempt was made to generate temporary undo in a distributed transaction.

Cause: An attempt was made to generate temporary undo without adding temporary tablespace in the database.

Cause: To mitigate a potential denial-of-service (DoS) attack via the recoverer process (RECO), the creation of a new RECO session has been prevented, because the maximum number of RECO sessions has been reached.

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

Cause: None.

Cause: Above events used for testing corruption path

Cause: the given transaction is not in the corrupt list v$corrupt_xid_list

Cause: the given usn is not a valid one

Cause: the given txn is not a valid one

Cause: the given usn is not a valid one

Cause: Tried to access SMON time zone information when database was not open for queries.

Cause: The _highthreshold_undoretention value was not greater than or equal to the UNDO_RETENTION setting and the low threshold value used for tuning undo retention.

Cause: The maximum query length (mql in minutes) was not less than or equal to half the _highthreshold_undoretention parameter setting.

Cause: The UNDO_RETENTION parameter value was not less than or equal to the _highthreshold_undoretention parameter setting.

Cause: The consolidated database was in shared undo mode and Oracle Flashback Transaction Query could not mine undo records across pluggable databases.

Cause: The specified table is already enabled for Flashback Archive.

Cause: An attempt is made to enable Flashback Archive for a table which should never be enabled for Flashback Archive.

Cause: An attempt was made to perform Flashback Archive operation on a table on which Flashback Archive is not enabled.

Cause: An invalid flashback archive or valid time period command was specified.

Cause: An incorrect tablespace is specified for the Flashback Archive.

Cause: An attempt was made to operate on a Flashback Archive that does not exist, or to create a Flashback Archive that already exists.

Cause: 30 seconds is recommended as the archiver sleep time for tests.

Cause: The purpose of this event is for debugging.

Cause: The default Flashback Archive did not exist.

Cause: An attempt was made to create a default Flashback Archive while one already exists.

Cause: An attempt was made to perform certain DDL statement that is disallowed on tables that are enabled for Flashback Archive.

Cause: An attempt was made to create, alter, or drop the default Flashback Archive.

Cause: An attempt was made to create, alter, or drop a Flashback Archive.

Cause: An attempt was made to specify invalid Flashback Archive quota size.

Cause: An attempt was made to execute DML on a tracked table without enabling Auto Undo Management.

Cause: The purpose of this event is for testing.

Cause: Too many transaction table slots were being taken by transactions on tracked tables.

Cause: Flashback archive tablespace quota is running out.

Cause: An attempt was made to grant Flashback Archive privilege.

Cause: An attempt was made to grant invalid privilege on a Flashback Archive object.

Cause: An attempt was made to enable Flashback Archive on a table without such privileges.

Cause: An attempt was made to create or alter a Flashback Archive quota which is larger than the user's quota.

Cause: An attempt was made to write to or alter or create unique index on a Flashback Archive internal table.

Cause: Flashback archive tablespace has run out of space.

Cause: An attempt was made to enable Flashback Archive again on a table which was just disabled.

Cause: An attempt was made to grant or revoke Flashback Archive privilege to a role.

Cause: An attempt was made to remove the primary tablespace of the Flashback Archive.

Cause: An attempt was made to add a tablespace that was not an ASSM tablespace.

Cause: An attempt was made to created a Flashback Archive with incorrect compatible mode or without auto undo management.

Cause: The purpose of this event is for testing.

Cause: An attempt was made to enable flashback data archive on an object which is not supported by flashback data archive.

Cause: An attempt was made to add a column of data type that is not supported by Flashback Data Archive. Or, the table on which Flashback Data Archive is being enabled contains column(s) with data types not supported by Flashback Data Archive.

Cause: An attempt was made to remove a tablespace that has Flashback Archive tables.

Cause: An attempt was made to do DDL on tracked tables while one DDL is runnning.

Cause: Either an incorrect table name was used or an exclusive lock on the table could not be acquired.

Cause: An attempt was made to perform operation on a Flashback Data Archive enabled table that is currently disassociated for DDL.

Cause: The Flashback Data Archive enabled table has different table definition from its history table.

Cause: An attempt was made to perform disassociation operation on a Flashback Data Archive enabled table that is in compliance mode. Or, DDL are not supported on tables in noncompliance mode.

Cause: Flashback Data Archive could not acquire resources to complete the operation on Oracle RAC.

Cause: Flashback Data Archive encountered internal SQL error.

Cause: An attempt was made to disassociate tables enabled for Flashback Data Archive without the required privilege.

Cause: An attempt was made to drop a Flashback Data Archive tablespace.

Cause: The table on which Flashback Data Archive is being enabled contains column(s) with names that are reserved by Flashback Data Archive.

Cause: An attempt was made to combine the Flashback Data Archive operation with other ALTER TABLE operations.

Cause: The purpose of this event was for testing.

Cause: An attempt was made to enable a valid time period on an object which is not supported by valid time period.

Cause: An attempt was made to enable flashback archive on an application for a second time.

Cause: An attempt was made to disable flashback archive on an application that has not been enabled for flashback archive.

Cause: An attempt was made to add a table to an application for a second time.

Cause: An attempt was made to remove a table that has not been added to an application.

Cause: An attempt was made to access an application that has not been registered for flashback archive.

Cause: An attempt was made to register an application for flashback archive for a second time.

Cause: An attempt was made to lock down an application for a second time.

Cause: An attempt was made to unlock an application that was not previously locked down.

Cause: An attempt was made to enable flashback archive on a base table with so many columns that the history table has no room for metadata columns.

Cause: An attempt was made to drop the flashback archive, however, it was still being used by an application.

Cause: The system was in the process of adjusting the number of global transaction background processes.

Cause: Undo tablespace was not onlined for automatic undo management.

Cause: The initialization parameter GLOBAL_TXN_PROCESSES was set to 0.

Cause: An attempt was made to set initialization parameter GLOBAL_TXN_PROCESSES to 0 at runtime.

Cause: After the savepoints were established, interleaved changes were made across Oracle RAC instances within the clusterwide global transaction.

Cause: The current local transaction was already bound to an undo segment that was not compatible with clusterwide global transactions.

Cause: Error occurred when trying to convert Oracle number to an integer.

Cause: The bit values that we consider. 0x1: Remove fix for bug 3514835 which could potentially throw more 8177 errors We have conservatively blocked some serializability errors, where there could potentially be a dependency between a service transaction in an index and forward going transaction.

Cause: This feature has not been implemented yet.

Cause: The specified log name was bigger than the maximum identifier supported in Oracle.

Cause: Create operation was attempted on an existing secure file log.

Cause: An open operation for read or write was attempted on a nonexistent log.

Cause: The specified tablespace to keep the swap space for the secure file log does not exist.

Cause: Specified tablespace to keep secure file logs did not support secure files.

Cause: The mode to create the log was not supported, or there was a discrepancy between the in-memory log creation and the persistent definition already present.

Cause: The dictionary-provided swap name did not exist. This could be caused by an external dropping of the swap table without going through the secure file log API's. This means that all of the persistent part of the log was lost.

Cause: A write, read or open operation was being tried on a log that was in the process of being destroyed.

Cause: A valid thread Id was not provided in order to write to a threaded log. Thread Ids are used to partially order messages to the log from different writing processes.

Cause: A valid logical thread Id was provided for a nonthreaded log. A partial order will not be maintained in a nonthreaded log and messages could be output in random order.

Cause: An invalid or uninitialized descriptor was found while doing a secure file log read or write.

Cause: An invalid option was passed for a log operation.

Cause: The log is opened with split messages across buffers set to false. However, the message size is bigger than what can be fit in one buffer.

Cause: Table flush I/O failed. The most common cause for this could be out-of-space errors in the tablespace.

Cause: The buffer size was greater than 16K. Secure file logging supports buffer sizes of 4K, 8K and 16K. The only reason a large buffer size is required is if split message is set to false, and the potential message is large.

Cause: The method to destroy, purge or partition log was called and requested to wait for open descriptors. After waiting for 5 minutes, an error is returned if writers or readers still exist.

Cause: The buffer sequence was too low or rows were removed from the swap table.

Cause: The provided start point, from which to begin reading, was incorrect.

Cause: PL/SQL callbacks had a problem

Cause: Number of elements in an array write exceeded the maximum limit 100 message segments in one write.

Cause: A null element was encountered during an array write.

Cause: An attempt was made to end write without a corresponding start write.

Cause: An attempt was made to close the log descriptor before the corresponding write end.

Cause: No suitable tablespace was found for the log.

Cause: The tablespace being added for the named log already existed in the list of tablespaces available for this log.

Cause: An attempt was made to create a new partition for the named log when the current partition is empty.

Cause: Version of log, identified by (logname, instanceid), did not exist.

Cause: The highest partition of log, identified by (logname, instanceid), did not exist.

Cause: An attempt was made to create a secure file log with no available memory for buffers.

Cause: The user provided did not own the secure file log under consideration.

Cause: The specified user ID did not exist in the database.

Cause: The specified user name did not exist in the database.

Cause: The user ID provided did not own the secure file log under consideration.

Cause: An attempt was made to associate storage with a secure file log which already has storage.

Cause: Flush callback was not associated with the secure file log under consideration.

Cause: The attempted operation failed because the database is not yet open.

Cause: An error occurred during execution of ktliIngestExternData.

Cause: A DML or DDL operation was attempted on a Common Logging Infrastructure internal table.

Cause: An attempt was made to get a readsavepoint before ktliRead successfully returned a message, using the secure file log descriptor under consideration.

Cause: An attempt was made to open a secure file log with a readsavepoint which had unsupported version.

Cause: External flush I/O failed.

Cause: The tablespace needed to keep the swap space for the secure file log has not been provided by the user.

Cause: The operation failed due to a CrossInstanceCall failure. Check the trace files on remote instances for the underlying problem.

Cause: The message length was greater than what the Secure file log supports.

Cause: The flush threshold specified for the secure file log is invalid.

Cause: The swap table of secure file log did not exist. This could be caused by an external dropping of the swap table without going through the secure file log API's. This means that all of the persistent parts of the log were lost.

Cause: An attempt was made to import data from an external source into a secure file log which is not associated with tablespace storage.

Cause: The pool name passed was either null or an invalid pool name.

Cause: The connection pool failed to start up.

Cause: The operation is only supported on an active pool.

Cause: The operation is only supported on an inactive pool.

Cause: The configuration paramter name is null or invalid input.

Cause: The configuration paramter value is null or invalid input.

Cause: Connection pool failed to shutdown.

Cause: Connection pool failed to configure pool.

Cause: Connection Broker failed to startup the pool.

Cause: Connection Broker failed to shutdown the pool.

Cause: Connection Broker failed to configure the pool.

Cause: Publish message to all RAC instances failed.

Cause: Some of the RAC instances were not synchronized.

Cause: This operation was not supported using connections from a pool.

Cause: The value passed exceeded the maximum allowed.

Cause: The operation was not allowed in Database Resident Connection Pooling when connected to a Pluggable Database.

Cause: An illegal OCI function call was issued.

Cause: Wrong value for connection class was given.

Cause: Wrong value for purity was provided.

Cause: Malformed input values.

Cause: Length exceeded MAX for the value.

Cause: Application tried to switch or migrate session across connections.

Cause: The client version is lower than 11g.

Cause: Attempt to reauthenticate the connection which is authenticated.

Cause: Server Group attribute was set on the server handle, connected to a Database Resident connection pool.

Cause: This usage was not supported on a DRCP connection.

Cause: The multi-property fix up callback encountered an error or was not able to fix up all the properties.

Cause: The value of SERVER_WAIT_TIMEOUT was reached while waiting for a server.

Cause: PL/SQL fix up callback was specified without multi-property tagging.

Cause: An attempt was made to modify the SUB_PLAN attribute of the specified plan.

Cause: An attempt was made to modify the INTERNAL_USE attribute of the specified consumer group.

Cause: An attempt was made to specify an INTERNAL_USE consumer group as a switch target.

Cause: An explicit kill or internal error caused the death of VKTM background process.

Cause: An attempt was made to set the EXPLICIT mapping priority to a value other than 1.

Cause: An attempt was made to run a second instance of I/O Calibration

Cause: An attempt was made to set a subplan as a top-level plan.

Cause: An attempt was made to specify INTERNAL_QUIESCE as a top-level Resource Manager plan.

Cause: There are no datafiles which are asynchronous I/O capable.

Cause: timed_statistics parameter in database is set to FALSE. Needs to be enabled for calibration.

Cause: An explicit kill or internal error caused the death of the DBRM background process.

Cause: The named argument is invalid.

Cause: An attempt was made to execute administration procedures from the DBMS_RESOURCE_MANAGER package without the appropriate privilege. The procedure requires the Resource Manager system privilege.

Cause: Plan name is greater than 30 characters long.

Cause: The specified plan name is prefixed with a reserved prefix such as FORCE or SCHED.

Cause: A non-existent category was specified as an argument to a procedure in the package, DBMS_RESOURCE_MANAGER.

Cause: The plan directive contained a switch directive (SWITCH_TIME, SWITCH_IO_REQS, or SWITCH_IO_MEGABYTES) without a SWITCH_GROUP.

Cause: A timeout occurred while waiting for one or more RAC instances to set the resource plan.

Cause: An error occurred in calibration slave process - Calibration process aborted.

Cause: The Resource Manager SWITCH_IO_MEGABYTES limit was exceeded.

Cause: The Resource Manager SWITCH_IO_MEGABYTES limit was exceeded.

Cause: The Resource Manager SWITCH_IO_REQS limit was exceeded.

Cause: The Resource Manager SWITCH_IO_REQS limit was exceeded.

Cause: An error occurred when spawning calibration slave process - Calibration process aborted.

Cause: An attempt was made to delete a category that is referred to by a consumer group.

Cause: Orion is spawning a child process and cannot determine the location of the executable.

Cause: An attempt was made to start an SQL block using DBMS_RESOURCE_MANAGER.BEGIN_SQL_BLOCK() while already inside an SQL block.

Cause: Binding the database instance to the processor group specified by the PROCESSOR_GROUP_NAME parameter failed.

Cause: Resource plans inside a pluggable database attempted to use the following parameters: MGMT_P2, MGMT_P3, MGMT_P4, MGMT_P5, MGMT_P6, MGMT_P7, MGMT_P8

Cause: An attempt was made to set a resource plan that contains subplans. Subplans are not supported in pluggable databases (PDBs).

Cause: An invalid value was specified for a plan directive parameter.

Cause: The Resource Manager SWITCH_IO_LOGICAL limit was exceeded.

Cause: The Resource Manager SWITCH_IO_LOGICAL limit was exceeded.

Cause: The Resource Manager SWITCH_ELAPSED_TIME limit was exceeded.

Cause: The Resource Manager SWITCH_ELAPSED_TIME limit was exceeded.

Cause: The plan directive specified a value for SWITCH_GROUP without specifying one of the following switch directives: - SWITCH_TIME - SWITCH_IO_REQS - SWITCH_IO_MEGABYTES - SWITCH_ELAPSED_TIME - SWITCH_IO_LOGICAL

Cause: An attempt was made to create or update the specified multitenant container database (CDB) resource plan to use more than the supported number of profile directives.

Cause: An attempt was made to alter the Resource Manager max_iops or max_mbps parameter in a non-consolidated database.

Cause: An attempt was made to create or set a resource manager plan that does not contain a consumer group mandated by the administrator. The specified plan has too many plan directives for the system to automatically add the mandatory consumer group.

Cause: An attempt was made to set a resource plan that contains multilevel management directives: MGMT_P2, MGMT_P3, MGMT_P4, MGMT_5, MGMT_P6, MGMT_P7, or MGMT_P8. Multilevel management directives are not supported in pluggable databases (PDBs).

Cause: An attempt was made to alter the Resource Manager max_iops or max_mbps parameter on an Oracle Exadata system.

Cause: An attempt was made to create a multitenant container database (CDB) plan directive where memory_min was greater than memory_limit.

Cause: An attempt was made to create a multitenant container database (CDB) plan directive where memory_min was greater than memory_limit.

Cause: The value for this parameter was invalid.

Cause: The value for this parameter was invalid.

Cause: The value for this parameter was invalid.

Cause: The value for this parameter was invalid.

Cause: The value for this parameter was invalid.

Cause: The value for this parameter was invalid.

Cause: The plan directive specified a value for PQ_TIMEOUT_ACTION without specifying a PARALLEL_QUEUE_TIMEOUT directive.

Cause: An invalid parameter or a value more than the maximum memory allowed was specified

Cause: On Oracle Exadata, the calibration run was terminated because the data files did not have a sufficient percentage of populated blocks.

Cause: This parameter cannot be set to a value that is lower than the current resource usage.

Cause: An explicit kill or internal error caused the death of the DSKM background process.

Cause: A LIBCELL operation in Master Diskmon failed.

Cause: A LIBCELL operation from Master Diskmon failed to create a network connection to the target CELL.

Cause: A LIBCELL operation in Master Diskmon failed because of a network error.

Cause: A LIBCELL operation from Master Diskmon failed because of an SKGXP network layer error.

Cause: A LIBCELL operation between Master Diskmon and a CELL failed because of a network error.

Cause: One or more of the specified IP addresses in CELLINIT.ORA is not valid.

Cause: No IP address is set in CELLINIT.ORA.

Cause: Master Diskmon was not running or the listening pipe was deleted.

Cause: One or more of the specified IP addresses in CELLINIT.ORA was repeated.

Cause: An attempt was made by a process to register a cell that is known to be down.

Cause: Attempted to use bind variables inside pivot|unpivot operation.

Cause: Attempted to use non-constant expression for pivot|unpivot values.

Cause: Attempted to use non-aggregate expression inside pivot operation.

Cause: invalid use of sys_op_pivot function.

Cause: Datatype of pivot value is not convertible to the datatype of pivot column.

Cause: An attempt was made to do a pivot or unpivot operation on a lateral view.

Cause: Either the combined column size for multicolumn pivot was too large or a multicolumn pivot value was too large.

Cause: A prepare or upgrade window was started or an on-demand or datapump-job loading of a secondary time zone data file was done.

Cause: Invalid time zone version passed.

Cause: Error(s) occurred when starting a prepare window.

Cause: There were no database properties related to time zone version in dictionary table sys.props$.

Cause: There was no active prepare window.

Cause: Error(s) occurred when ending a prepare window.

Cause: Database was not in UPGRADE mode.

Cause: Error(s) occurred when starting an upgrade window.

Cause: There was no active upgrade window.

Cause: Ending an upgrade window failed or there were tables containing TSTZ data which have not been upgraded.

Cause: Database was not restarted after starting an upgrade window.

Cause: DST patching was in an inconsistent state.

Cause: Specified table name was invalid.

Cause: Error(s) occurred when creating the table.

Cause: Database property DST_UPRGRADE_STATE was not recorded correctly.

Cause: An attempt was made from a datapump job to request a different version of time zone data file from the one used by existing datapump jobs.

Cause: An on-demand loading of secondary time zone data file was requested when there was a secondary time zone data file already loaded in the database utilized by existing datapump jobs.

Cause: Attempt to load the secondary timezone data file failed.

Cause: There was no secondary timezone data file being loaded by on-demand or a datapump job.

Cause: Attempt to unload the secondary timezone data file failed.

Cause: Invalid incident identifier argument passed.

Cause: The attribute value was null.

Cause: The reference plan resolved to multiple plans.

Cause: Both statement_id and plan_id attributes were null in PLAN_TABLE_OBJECT.

Cause: A quarantined plan was used for this statement.

Cause: The options specified are inconsistent

Cause: One of the file specified in the test case package is mising

Cause: The import options specified do not match the export options

Cause: The import options specified are inconsistent

Cause: The SQL_ID specified was incorrect.

Cause: One or more export options were inconsistent.

Cause: One or more import options were inconsistent.

Cause: The root directory for Test Case Builder (TCB) does not exist.