Cause: invalid or illegal combination of options provided to COMMIT WRITE SQL statement.

Cause: invalid or illegal value provided for parameter.

Cause: An attempt was made to create an index that refers to the ORA_ROWSCN pseudo-column, either directly or in an expression.

Cause: An attempt was made to drop an index defined on a hash cluster. Hash cluster indexes cannot be dropped.

Cause: An Advanced Compression Option (ACO) feature was specified without enabling the ACO parameter.

Cause: SECUREFILE and BASICFILE were both specified.

Cause: A LOB that is not a SECUREFILE was used in a SQL statement or in a call where a SECUREFILE LOB was expected.

Cause: Attempt to modify a LOB with an invalid parameter.

Cause: Length of CONTENTTYPE string exceeded the defined maximum.

Cause: Length of CONTENTTYPE buffer less than defined constant.

Cause: An 11.2 LOB feature was specified when the database was operating at a compatible setting lower than "11.2.0".

Cause: Invalid delta update operation was issued on LOB. This includes operation beyond LOB length; move operation with destination offset inside move interval.

Cause: An attempt was made to provide an argument that was not a literal or bind variable.

Cause: An invalid output data type was provided. The valid output data types for VALIDATE_CONVERSION operator and the operators supporting DEFAULT ON CONVERSION ERROR syntax are: NUMBER, BINARY_FLOAT, BINARY_DOUBLE, DATE, TIMESTAMP, TIMESTAMP WITH TIME ZONE, INTERVAL DAY TO SECOND, INTERVAL YEAR TO MONTH.

Cause: An invalid input data type was provided for Validate_Conversion operator. For the NUMBER, BINARY_FLOAT and BINARY_DOUBLE output data types, the input data types can be: - NUMBER - BINARY_FLOAT - BINARY_DOUBLE - CHAR - VARCHAR2 - NCHAR - NVARCHAR2 For the DATE, TIMESTAMP, TIMESTAMP WITH TIME ZONE, INTERVAL DAY TO SECOND, and INTERVAL YEAR TO MONTH output data types, the input data types can be: - CHAR - VARCHAR2 - NCHAR - NVARCHAR2

Cause: Precision was provided for the following data types: NUMBER, TIMESTAMP, TIMESTAMP WITH TIME ZONE, INTERVAL YEAR TO MONTH, INTERVAL DAY TO SECOND.

Cause: COLLATE was specified for a non-character column.

Cause: A character LOB column or expression was declared as having a collation other than USING_NLS_COMP or the determined collation for a collation-sensitive operator or function operating on character LOB values was not USING_NLS_COMP. Character LOB values support only the USING_NLS_COMP collation.

Cause: Arguments to the operator or function (operation) that have the lowest coercibility level and are relevant for derivation of the collation for the result of this operation had conflicting collations.

Cause: Arguments to the operator, function, or condition (operation) that are relevant for determining the collation to be used by this operation had undefined collations.

Cause: Arguments to the operator, function, or condition (operation) that have the lowest coercibility level and are relevant for determining the collation to be used by this operation had different collations.

Cause: An attempt was made to create a virtual character column in a table, a character column in a table based on a query (CREATE TABLE AS SELECT), or a character column in the key of a functional index. The expression on which the column definition was based did not have a derived collation to be used for the column, because of a collation conflict in one of its operators. In case of a virtual column, no collation was provided for the column through the data type declaration, either.

Cause: An attempt was made to specify an invalid collation for the primary key column of an index-organized table.

Cause: An attempt was made to provide an argument that was not a literal.

Cause: Nested aggregates were specified in the pivot operator. This operation is not supported.

Cause: DEFAULT ON NULL was specified on a object type or REF column. These types are not supported.

Cause: An attempt was made to create an index cluster in which one of the key columns had an unsupported declared collation or an attempt was made to create a hash cluster in which a key column with SORT clause had an unsupported declared collation. Only the collations BINARY, USING_NLS_COMP, USING_NLS_SORT, USING_NLS_SORT_CS, USING_NLS_SORT_VAR1, and USING_NLS_SORT_VAR1_CS are supported for character columns in index clusters and for sorted character columns of hash clusters.

Cause: An attempt was made to modify the declared collation of a column that either: o belonged to a foreign key o belonged to a primary or unique key and that key was referenced by some foreign key o corresponded to a cluster key column o was referenced by a defining expression of a virtual column o was referenced by a defining expression of a functional index o corresponded to an attribute of a user-defined type or an object table o belonged to the container table of a materialized view o was referenced by a join condition of a bitmap join index The declared collation of such columns cannot be modified.

Cause: An attempt was made to modify the declared collation of a column that belonged to a primary or unique key, or a standard index key, or a partitioning key, and the new collation was from a different group than the old collation, where the groups are defined as follows: Group 1: BINARY, USING_NLS_COMP, USING_NLS_SORT, USING_NLS_SORT_CS, USING_NLS_SORT_VAR1, and USING_NLS_SORT_VAR1_CS Group 2: BINARY_CI, USING_NLS_SORT_CI, and USING_NLS_SORT_VAR1_CI Group 3: BINARY_AI, USING_NLS_SORT_AI, and USING_NLS_SORT_VAR1_AI

Cause: An attempt was made to modify the collation of an Oracle-maintained database object. Modifications of Oracle-maintained database objects are generally not permitted.

Cause: An attempt was made to create a bitmap join index or a domain index with a key or join condition that contained a character column with a declared collation other than BINARY, USING_NLS_COMP, USING_NLS_SORT, USING_NLS_SORT_CS, USING_NLS_SORT_VAR1, or USING_NLS_SORT_VAR1_CS. Only these listed collations are supported by this type of the index.

Cause: An attempt was made to change the collation of a character column to a collation that is not supported in a key of a bitmap join index, a domain index key to which the column belongs. Only the collations BINARY, USING_NLS_COMP, USING_NLS_SORT, USING_NLS_SORT_CS, USING_NLS_SORT_VAR1, and USING_NLS_SORT_VAR1_CS are supported in these keys.

Cause: An attempt was made to explicitly state the default collation setting for an object table. However, default collations do not apply to object tables because all columns of an object table inherit collations from the attributes of the base type of the table.

Cause: An attempt was made to use the default value, in case of a conversion failure, by specifying the DEFAULT argument ON CONVERSION ERROR statement to a conversion operator. This feature is not allowed for current operation.

Cause: The COLLATE or DEFAULT COLLATION clause was specified in a DDL statement or the DEFAULT_COLLATION parameter was specified in an ALTER SESSION statement, but the value of the initialization parameter MAX_STRING_SIZE was STANDARD. The data-bound collation feature is disabled if the value of this parameter is STANDARD.

Cause: A table or view column with a declared collation other than USING_NLS_COMP was referenced in a distributed query that originated in an Oracle Database with the release number lower than 12.2. Such references are not allowed.

Cause: An ALTER TABLE statement attempted to combine DEFAULT COLLATION with some other operation, which is not allowed.

Cause: An ALTER TABLE statement attempted to combine DROP IDENTITY with some other operation, which is not allowed.

Cause: Collation was not specified in a context where it was required.

Cause: The schema for the given schema name did not exist.

Cause: The input parameter string was not a qualified SQL identifier of an existing SQL object.

Cause: The input parameter string was not a valid simple SQL name.

Cause: The input parameter string was not a valid qualified SQL name.

Cause: Set schema failed because an attempt was made to change the pluggable database (PDB) before the set schema took effect.

Cause: The priority level given by the user was invalid.

Cause: An unknown or unsupported authentication or compression algorithm was encountered.

Cause: A timeout occured while waiting for a cursor to be compiled. This is usually caused by the SQL parse requiring access to system resources which are locked by concurrently executing sessions.

Cause: The pseudo-cursor depends on a table which was found to be obsolete due to metadata invalidation of the library cache object.

Cause: The service name argument was found to be NULL.

Cause: The network name argument was found to be NULL.

Cause: This service name was already in existence.

Cause: The specified service was not in existence.

Cause: The specified service was running.

Cause: The service name was too long.

Cause: The network name, excluding the domain, was too long.

Cause: The maximum number of services has been reached.

Cause: The specified service was not running.

Cause: The database was closed.

Cause: The instance name argument was not valid.

Cause: The network name was already in existence.

Cause: All attributes specified were null.

Cause: Invalid argument supplied.

Cause: The database is open read-only.

Cause: The total length of all running service network names exceeded the maximum allowable length.

Cause: Specified AQ service belonged to a queue.

Cause: Could not modify the global service because of insufficient privileges or you were trying to modify the global service attribute.

Cause: Trace file could not be read.

Cause: A NULL or zero length file name was specified.

Cause: The given count was a nonpositive number.

Cause: Count number was missing for the option.

Cause: The given trace symbol was not found.

Cause: symbol argument to -[un]trace option was missing.

Cause: filename argument to the option was missing.

Cause: Version of the trace file was not supported.

Cause: The full path name provided was too long.

Cause: Mutually exclusive values were specified for the flag parameter.

Cause: A 10.2 or higher client is being used with an older Oracle server.

Cause: The END_DATE was smaller than the START_DATE in one of the ACE's in this ACL.

Cause: A cycle was formed by ACL inheritance.

Cause: Security class of parent ACL was not an ancestor of security class of child ACL

Cause: The path to the parent ACL was not a valid resource.

Cause: An undefined privilege was found in an ACE in the ACL.

Cause: An unresolved principal is found in an ACE in the ACL.

Cause: The specified ACLID did not point to a valid ACL document.

Cause: The specified ACL did not meet the validation requirements of the constraining ACL.

Cause: If no SCHEMA clause (explicit schema or ANYSCHEMA) was specified, nonschema data cannot be disallowed.

Cause: An attempt was made to insert nonschema based XML documents in a binary XML column that disallows nonschema data.

Cause: An attempt was made to use a XML Schema registered for binary usage as part of a CLOB or OBJ-REL clause.

Cause: An attempt was made to specify BINARY XML storage using an XML schema not registered for BINARY.

Cause: An attempt was made to create an XMLType table or column with out XML DB installed.

Cause: Too much concurrency

Cause: Lock not found

Cause: Lock denied

Cause: The resource is locked by an implicit lock

Cause: Arguments to QMEL are not correct.

Cause: Archive logging was not enabled.

Cause: An attempt was made to modify supplemental logging settings using Oracle Database Express Edition.

Cause: An attempt was made to use DBMS_LOGMNR.START_LOGMNR with CONTINOUS_MINE as an option.

Cause: An attempt was made to use one of the DBMS_LOGSTDBY extended data type support procedures.

Cause: Invalid language.

Cause: The document had multiple translations and one of them did not have the xml:lang attribute.

Cause: The document had multiple translations for a language.

Cause: The document had multiple source language translations.

Cause: The given XPath pointed to multiple translated elements.

Cause: The value of xdb:maxOccurs was not '1' for a translated element.

Cause: The value of xsd:maxOccurs was not 'unbounded' for a translated element.

Cause: The document had no source language translation for a translated element.

Cause: The storage type of the schema was object relational.

Cause: The schema definition for a translated element was invalid.

Cause: The XLIFF document was malformed.

Cause: XPath pointed to an untranslatable element.

Cause: XPath within trans-unit/id attribute was invalid.

Cause: XPath did not select all translations for a particular element.

Cause: An attempt was made to add or add a resource to the XDB repository at a position reserved for fusion security.

Cause: A port number specified in the XDB Configuration file conflicts with a port number used in the XDB Configuration file of the same non-consolidated database or the same Pluggable Database or a different Pluggable Database of the same consolidated database or the root container of the same consolidated database.

Cause: The async XML Index could not be used since ORACLE is not open for query.

Cause: The repository XML Index indexed one of the parent folders of the resource identified by given path.

Cause: The repository XML Index did not index the resource identified by given path.

Cause: DROP INDEX could not be used on the repository XML Index.

Cause: There was at least one node in the document with multiple similar children which was used in Predicate Indexing.

Cause: Number of predicates were more than limit.

Cause: The group name specified already exists.

Cause: The parameter name specified did not exist.

Cause: The group name specified did not exist.

Cause: An attempt was made to drop the last group in the index.

Cause: The parameter name specified was already registered.

Cause: An attempt was made to drop a group whose tables are shared by other group(s).

Cause: An attempt was made to add columns to, modify columns of, or drop columns from a table shared by other group(s).

Cause: An attempt was made to add columns to, modify columns of, or drop columns from a dependent shared table. One can only add columns to, modify columns of, or drop columns from the original shared table.

Cause: An attempt was made to have more than one add, modify, or drop column or group operations in the ALTER INDEX statement.

Cause: An attempt was made to add or drop columns to or from multiple tables in a single ALTER INDEX statement.

Cause: An attempt was made to create or add a group without XMLTABLE.

Cause: An attempt was made to specify ASYNC parameter for an XMLIndex with a structured component.

Cause: An attempt was made to create a GROUP with invalid name.

Cause: An attempt was made to create a COLUMN without PATH.

Cause: An attempt was made to create a secondary index on the unstructured component of an XMLIndex when the XMLIndex does not have an unstructured component.

Cause: The enumeration item corresponding to the enumeration index could not be found in the XML schema.

Cause: The new element that was added to a complex type by in-place XML schema evolution had the same qualified name as another element in the same complex type or in one of its ancestor complex types.

Cause: The value of attribute minOccurs on an element could not be increased by in-place XML schema evolution.

Cause: The value of attribute maxOccurs on an element could not be decreased by in-place XML schema evolution.

Cause: The complexType property on an element could not be changed by in-place XML schema evolution.

Cause: The SQLType property on an element in a binary XML schema could not be changed by in-place XML schema evolution.

Cause: The service operation failed.

Cause: The CRS operation failed.

Cause: The consolidated database was not open. The operation was not performed.

Cause: The attempted operation was invalid for a consolidated database.

Cause: The attempted pluggable database operation failed.

Cause: The attempted pluggable database operation failed.

Cause: The attempted pluggable database operation failed.

Cause: The attempted operation failed.

Cause: The attempted operation failed.

Cause: The attempted operation failed.

Cause: The attempted operation failed.

Cause: The attempted CRS service operation failed.

Cause: The number of runtime load balancing services reached the maximum allowed.

Cause: The attempted service operation failed.

Cause: The attempted service operation failed.

Cause: The service was not imported successfully while plugging in the pluggable database or the service is defined in a different pluggable database.

Cause: The service did not exist in the new pluggable database or the service was not started in the pluggable database.

Cause: One of the verification checks failed.

Cause: The total length of a globally unique identifier (GUID) exceeded 16 characters.

Cause: Drain timeout and stop option could not be used for remote operations.

Cause: There was not enough memory available.

Cause: The user tried to stop an internal service.

Cause: The num_classifiers argument was found to be NULL.

Cause: The wlm_classifiers argument was found to be NULL.

Cause: No new plan was created before submission.

Cause: New plan was attempted to be created before activating the current plan.

Cause: A new plan was not created before submitting the Classifier and Performance Class lists.

Cause: The classifier list contained no classifiers.

Cause: More classifiers were present in the list than specified.

Cause: The Performance Class name was larger than 32 bytes.

Cause: The Work Request Class name was larger than 32 bytes.

Cause: This classifiers contained no expression. It should contain one more more expressions.

Cause: This expression contained no paramaters or attribute values. It should contain one or more attribute values. Attributes can be SERVICE_NAME, MODULE, ACTION, PROGRAM or USER.

Cause: The service name mentioned in the parameter list was too large.

Cause: The module name mentioned in the parameter list was too large.

Cause: The action name mentioned in the parameter list was too large.

Cause: The program name mentioned in the parameter list was too large.

Cause: The user name mentioned in the parameter list was too large.

Cause: The number of Performance Classes submitted were less than what was specified.

Cause: The length of the classifier list was greater than 4000 bytes.

Cause: There was an unknown failure.

Cause: Either a WLM plan was being loaded from another instance, or the strict order of the PL/SQL calls for loading WLM plan was not followed.

Cause: The number of Work Request Classes submitted were less than what was specified.

Cause: A very large number ( > 1024) of classifiers were requested.

Cause: QoS Resource Manager plan did not exist in this database.

Cause: The QoS Resource Manager plan was not in use.

Cause: Resource Manager was turned off.

Cause: Classifier plan was not the same across instances.

Cause: The number of Performance Classes submitted were more than what was specified.

Cause: A large number ( >= 50) of Performance Classes were requested.

Cause: There was an internal Global Service Manager (GSM) error.

Cause: The specified database name was not valid.

Cause: The maximum number of regions was exceeded.

Cause: The maximum number of nodes for valid node checking for registration (VNCR) was exceeded.

Cause: This database already contained the catalog.

Cause: The specified configuration name contained invalid characters or was too long.

Cause: There was an internal Global Service Manager (GSM) error.

Cause: A catalog did not exist in the database.

Cause: The catalog contained one or more database or Global Service Manager (GSM) objects.

Cause: The specified Global Service Manager (GSM) was already in existence in the catalog.

Cause: The specified region was not found in the catalog.

Cause: A valid node and group name were specified in the same command.

Cause: A region was specified as buddy for itself.

Cause: The last region could not be removed from the cloud catalog.

Cause: The region contained databases or Global Service Manager (GSM).

Cause: The Global Data Services (GDS) pool contained databases or services.

Cause: An attempt was made to add a database that does not belong to a Data Guard broker configuration to a Data Guard broker pool.

Cause: The database or service was already in the Global Data Services (GDS) pool.

Cause: An attempt was made to add a database to a pool that contains a Data Guard broker configuration.

Cause: The automatically created network service name was too long.

Cause: ROLE was specified for a pool that did not contain a Data Guard broker configuration.

Cause: The service was created with the PREFERRED_ALL option.

Cause: The source and target parameters of MOVE SERVICE were the same.

Cause: An attempt was made to add a service to a database that already offered the service.

Cause: An attempt was made to start or stop a service on a database that does not offer the service.

Cause: The specified database-related service parameters were not valid.

Cause: The specified service was running.

Cause: The service could not be started on the database because it was disabled.

Cause: The service could not be started on the standby database because the database current lag exceeds the service lag.

Cause: An attempt was made to add a new Global Service Manager (GSM) without providing a region. When there is more than one existing region, a region name must be provided.

Cause: An attempt was made to modify the catalog, but it does not yet exist.

Cause: An attempt was made to add broker configuration to a Global Data Services (GDS) pool that already contained a database. This is not allowed.

Cause: The name of the specified Global Data Services (GDS) pool was not valid.

Cause: The name of the specified region was not valid.

Cause: The name of the specified service was not valid.

Cause: The name specified for the valid node checking for registration (VNCR) was not valid.

Cause: The name specified for the valid node checking for registration (VNCR) group was not valid.

Cause: The name of the specified Global Service Manager (GSM) was not valid.

Cause: The name of the specified Global Service Manager (GSM) was not valid.

Cause: The specified region was already in existence in the catalog.

Cause: The specified Global Data Services (GDS) pool was already in existence in the catalog.

Cause: The specified region was not found in the catalog.

Cause: The specified Global Data Services (GDS) pool was not found in the catalog.

Cause: The specified database was not found in the pool.

Cause: The specified service was not found in the catalog.

Cause: The region contained databases.

Cause: The service was already in the Global Data Services (GDS) pool.

Cause: LAG was specified for a pool that did not contain a Data Guard broker configuration.

Cause: FAILOVER_PRIMARY was specified for a pool that did not contain a Data Guard broker configuration.

Cause: The specified valid node checking for registration (VNCR) name was already in existence in the catalog.

Cause: The specified identifier exceeded the maximum allowed length.

Cause: The system is unable to resolve the specified symbolic link.

Cause: This error is raised when the system is unable to fully resolve a path with symbolic links within a reasonable number of steps. It could be due to cycles in definitions of symbolic links or very long chains of symbolic links to symbolic links.

Cause: The system cannot create a hard link to the specified resource.

Cause: Target path length exceeds the maximum which can be stored to disk.

Cause: XLink type attribute is extended.

Cause: target path does not resolve to valid resource.

Cause: there is a hard document link with this resource as the target.

Cause: There is a loop in XInclude elements within the document.

Cause: The href attribute is missing within XInclude element.

Cause: The xpointer attribute is specified within XInclude element.

Cause: The depth of nested xinclude expansion has exceeded system limit.

Cause: The specified xpath is either invalid or unsupported in this context.

Cause: There was an error while processing the specified XInclude.

Cause: The XPointer was too long with the schema URL and element name.

Cause: Renaming virtual folders was not supported.

Cause: Recursive deletion of virtual folders was not supported.

Cause: A REF was being set to point to the resource table."

Cause: The destination of a copy was an ancestor of the source.

Cause: Overwriting an existing resource was prohibited.

Cause: A copy or move was attempted with the same source and destination.

Cause: The XPath did not map to a single node.

Cause: The XPath did not map to a scalar type.

Cause: A SecureFile was archived and implicit retrieval was not allowed.

Cause: The content ID was invalid or was already deleted.

Cause: Potential data corruption.

Cause: Error related to SBT Tape library.

Cause: Error related to DBFS HS Store.

Cause: An operation was not permitted to start because the database role is not supported.

Cause: An upgrade plan was already active.

Cause: The DG_CONFIG attribute was missing from the LOG_ARCHIVE_CONFIG parameter.

Cause: The specified database was not found in the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter.

Cause: The configured target software version was incompatible with a DBMS_ROLLING administered upgrade.

Cause: A DBMS_ROLLING operation was already in progress. Only one operation is permitted at a time.

Cause: An operation succeeded but warnings were generated.

Cause: An internal database query failed.

Cause: The specified parameter could not be modified because the parameter name was not recognized.

Cause: The specified parameter could not be modified because its value was invalid or out of bounds.

Cause: The specified parameter could not be modified.

Cause: An operation has failed because one or more arguments were not supplied.

Cause: An operation has failed because the database unique name provided in the scope argument was not known.

Cause: The specified parameter could not be reverted back to its default value because the default value did not exist.

Cause: Connections to one or more databases failed.

Cause: A rolling upgrade operation has halted due to the failure of one or more required upgrade instructions.

Cause: An operation was not permitted to start due to recent parameter modifications which required a rebuild of the upgrade plan.

Cause: An operation was not permitted to start because the upgrade was in a different phase.

Cause: A rolling upgrade instruction has failed because a database was not running the correct target RDBMS version.

Cause: The DB_UNIQUE_NAME parameter was not configured.

Cause: An instruction failed because a Transparent Network Substrate (TNS) service name for return communication was not found on a remote database.

Cause: One or more databases specified in the DG_CONFIG attribute was incompatible with a DBMS_ROLLING administered upgrade.

Cause: An operation was not permitted to start because it required an active plan.

Cause: A specified DB_UNIQUE_NAME attribute in a LOG_ARCHIVE_DEST_n parameter did not match the DB_UNIQUE_NAME at the target database.

Cause: An instruction failed due to an initialization parameter file at a remote database that was found to be invalid.

Cause: A rolling upgrade operation stopped because interaction is required.

Cause: An operation failed due to the inactive managed recovery process at a remote database.

Cause: An operation failed due to the inactive logical standby Redo Apply process at a remote database.

Cause: An instruction failed due to a database operating in a database role which was not expected.

Cause: An instruction failed due to a database operating at a data protection mode that was not expected.

Cause: An instruction failed due to a database that was found to not have Flashback Database enabled.

Cause: An instruction failed due to a database that was mounted or open in an invalid mode.

Cause: An operation was not permitted because the future primary database is not a physical standby database.

Cause: An operation was not permitted because a failover was detected on a database which does not permit continuation of the rolling upgrade.

Cause: An operation was not permitted because multiple failovers were detected on standby databases which protect a common target.

Cause: An operation failed due to an active managed recovery process at a remote database.

Cause: An operation failed due to an active Redo Apply process at a remote database.

Cause: An operation failed due to the discovery of the catalog upgrade progress on a database that was different from the progress value saved in the plan state.

Cause: An operation failed due to the discovery of a database which was not in mounted mode.

Cause: An operation failed due to the discovery of a database which was not in open read/write mode.

Cause: An operation failed due to the discovery of a database which was not configured with a server parameter file that could be modified.

Cause: A rollback operation could not start because the databases have not created the guaranteed restore point needed for rollback.

Cause: A rollback operation was not permitted due to a prior role change event such as a switchover or failover.

Cause: An operation failed because there were other processes executing long running replicated PL/SQL procedures.

Cause: An operation failed due to the discovery of the update progress on a database that was different from the progress value saved in the plan state.

Cause: An attempt was made to remove a database from a pool that contained a broker configuration.

Cause: A new Global Service Manager (GSM) was added to a region that already contained the maximum number of GSMs.

Cause: A Global Service Manager (GSM) command was executed by a non-privileged user.

Cause: An attempt was made to add a database to a cloud when it was already in another cloud.

Cause: The command 'relocate service' is not supported for preferred_all services.

Cause: The hard limit for the number of global services has been reached.

Cause: The hard limit for the number of Global Data Services (GDS) pools has been reached.

Cause: The specified region did not have a buddy.

Cause: The specified database did not have an assigned region.

Cause: The specified database had an invalid status.

Cause: A change request originating from a gdsctl command was not applied after several minutes.

Cause: The specified service did not have a preferred database. This can happen if the database was removed from the pool.

Cause: The specified service did not have a preferred database in a region in which it had an available database.

Cause: A database was added to the global data services framework, but no global services have been defined for it, or they have all been removed.

Cause: A region was added to the global data services framework, but no databases were added to this region, or they have all been removed.

Cause: A region was added to the global data services framework, but no global services manager servers were defined for this region, or they have all been removed.

Cause: The specified Global Data Services (GDS) pool did not contain any databases.

Cause: The specified Global Data Services (GDS) pool did not contain any global services.

Cause: The specified service will not be started on a logical/snapshot standby.

Cause: The database pool does not contain any databases. Therefore this operation will have no effect.

Cause: Service attributes ANYWHERE and REGION_FAILOVER are incompatible.

Cause: A service with a primary role cannot set FAILOVER_PRIMARY.

Cause: The specified service is LOCAL_ONLY and cannot be relocated to a database in a different region.

Cause: The service was stopped already.

Cause: An attempt to have a default Global Data Services pool when multiple pools already coexist in the domain failed.

Cause: The command specified a value of TRANSACTION for the service parameter '-failovertype', and either did not provide a value for the parameter '-retention', or provided a value that was less than or equal to the value provided for the parameter '-replay_init_time'.

Cause: The command specified a value of TRANSACTION for the service parameter '-failovertype', and either did not provide a value for the parameter '-replay_init_time', or provided a value that was less than or equal to the value provided for the parameter '-failoverdelay'.

Cause: The major database compatibility level is below 12. The Global Data Services (GDS) feature requires that the database compatibility level of all participating databases be at 12 or above.

Cause: An attempt was made to start the service in a specific database without first starting it globally.

Cause: The database was not configured to use an SPFILE. This is required before it can be used within a Global Data Services (GDS) framework.

Cause: An attempt was made to create a global service with the same name as an existing local service.

Cause: An attempt was made to create a Global Data Services (GDS) catalog on a database that was already in another GDS framework.

Cause: An attempt was made add a database to a Global Data Services (GDS) framework, but it was already a catalog database for another framework.

Cause: The specified service was already in the process of being modified.

Cause: This command could not be executed while there were running GSM (Global Service Manager) servers connected to the catalog.

Cause: The version of the GDS (Global Data Services) catalog could not be determined.

Cause: The version of GDSCTL being used was not compatible with the current GDS catalog.

Cause: The version of GSM being used was not compatible with the current GDS catalog.

Cause: The version of the database being added was not compatible with the GDS catalog.

Cause: An attempt was made to add a database to a pool, but this database has already been added to another pool.

Cause: An attempt to call the SRVCTL command line failed with the specified errors.

Cause: The service command stipulated -serverpool or -cardinality but this database was an administrator-managed Oracle RAC database, which does not recognize these parameters.

Cause: The service command stipulated -serverpool, -cardinality, or -instances but this database was a non-Oracle RAC database, which does not recognize these parameters.

Cause: The service command stipulated -instances, but this database was a policy-managed Oracle RAC database, which does not recognize this parameter.

Cause: The string provided by GDSCTL to override runtime load balancing with manual region weights was badly formed.

Cause: This command would delete all remaining instances from the service, leaving the service in an invalid state.

Cause: There was a problem creating a new process to run SRVCTL from the command line.

Cause: The command-line execution of SRVCTL failed because of bad parameters.

Cause: This is a warning message only. This command required catalog changes and the 'compatible' database parameter indicated that the database could be downgraded. Downgrading a catlog database after making catalog changes is not advised and may cause data loss in the catalog.

Cause: This command required catalog changes, which are not allowed unless there is at least one Global Service Manager (GSM) server running at the current version.

Cause: An attempt was made to start a service that did not exist on the target database.

Cause: An attempt was made to delete an instance from this database but the instance was not in the existing instance list.

Cause: The provided instance list did not contain any valid instances, or the existing instance list for the catalog was empty.

Cause: An attempt was made to start a service on an administrator-managed Oracle RAC database, but there were no instances defined for the service on that database.

Cause: An attempt was made to start all services for a given database but there were no services that could start.

Cause: The new database name provided was not in the list of preferred or available databases for the service.

Cause: A disable service request did not provide either a database name or a service name.

Cause: An attempt was made to remove a broker configuration from a database pool that does not contain one.

Cause: The catalog did not have any database pools defined.

Cause: The GSM did not provide a version when attempting to connect to the catalog.

Cause: The MODIFY command did not add any preferred instances or removed all existing preferred instances from this database.

Cause: A region name was not provided and was required because there were multiple regions in the catalog.

Cause: The CREATE CATALOG command could not be executed on a container other than the root container.

Cause: The ADD DATABASE command could not add a pluggable database.

Cause: An attempt was made to add non-uniform service to a pool that contains a sharded root.

Cause: An attempt was made to add a database to a pool that contains a sharded root.

Cause: An attempt was made to work with a generic pool that was not a sharded root.

Cause: An attempt was made to work with a generic pool that was not a shard.

Cause: An attempt to use a database link from a pool database to a catalog failed.

Cause: The shardspace or shardgroup was not empty and contained at least one shardgroup or shard.

Cause: The remote scheduler job to convert a shard from seed has failed.

Cause: The shard was opened in the incorrect mode for Oracle Data Guard broker setup.

Cause: The shard did not have the correct role for Oracle Data Guard broker setup.

Cause: Due to previous errors deployment could not continue.

Cause: The remote scheduler agent is required to convert the shard from a seed, but it has not been configured.

Cause: A primary shard was added to the catalog but the DBID was not discovered, and none of the standby shards could be converted.

Cause: Credential could not be created or retrieved.

Cause: The primary shard was still an unconverted seed, but it had converted standby shards. Standby shards cannot be converted before their primary shard.

Cause: The specified parameter was set to an invalid value.

Cause: At attempt was made to create a sharded and a non-sharded database pool in the same catalog.

Cause: The client application specified a chunk name associated with the current user call that was not found on the current shard.

Cause: The chunk, specified by the client application, was split or never contained the specified key.

Cause: The shardspace or shardgroup that you intended to remove did not exist in catalog.

Cause: The chunk move failed. The source shard could not connect to the target.

Cause: The chunk move failed. The target shard was improperly configured.

Cause: The chunk move failed. The source shard could not connect to the target standby shard.

Cause: Shard metadata inconsistency was detected.

Cause: Shard configuration inconsistency was detected.

Cause: Shard configuration inconsistency was detected.

Cause: There was a database management system (DBMS) file transfer error.

Cause: There was a database management system (DBMS) file transfer error.

Cause: The backup file could not be deleted from the file system.

Cause: There was an internal error which prevented a chunk state change.

Cause: There was an internal error which prevented the metadata export.

Cause: The region was not empty because it contained at least one shardgroup.

Cause: The shard was in an invalid or unsupported state for use with sharding.

Cause: The discovered database identifier (DBID) for the shard was invalid, but the shard was already converted from a shard seed.

Cause: There was an unexpected error during TSDP operation.

Cause: The names of invalid or nonexistent database objects were found in the XML input.

Cause: The schema specified did not exist.

Cause: The table specified did not exist in the schema.

Cause: The column specified did not exist.

Cause: A sensitive type that was associated with one or more sensitve columns did not exist.

Cause: There was no sensitive column matching the schema, table and column input.

Cause: The column was already identified as sensitive.

Cause: No sensitive columns were found for the given source.

Cause: The sensitive type already existed in the database.

Cause: The sensitive type did not exist in the database.

Cause: The sensitive type that is associated with one or more columns could not be dropped.

Cause: A TSDP policy with the same name was found.

Cause: The Oracle security feature specified was not supported by Transparent Sensitive Data Protection.

Cause: The TSDP policy specified did not exist.

Cause: Importing the list of sensitive columns succeeded. However, one or more sensitive column types already existed in the database and were not imported again. The corresponding column is associated with the existing type.

Cause: An attempt was made to alter a column that was not identified as sensitive.

Cause: The given policy was not associated with the sensitive column type.

Cause: Policy enforcement on one or more columns encountered errors.

Cause: The given policy was not enabled on the column.

Cause: The given policy was associated with the sensitive column type.

Cause: Errors were encountered while disabling one or more policies.

Cause: The cause of this error could be one or more of the following: - The policy that was associated with the sensitive column type of a column was not enabled on the column because no subpolicy matched the column properties. - There was no policy associated with the sensitive column type of a sensitive column. - A conflicting redaction policy was enabled on the table.

Cause: There was no policy associated with the sensitive column type of a column.

Cause: Importing the list of sensitive columns failed because there was a problem in disabling protection on the columns. A subsequent attempt to reenable protection on the columns also failed.

Cause: Importing the list of sensitive columns succeeded. A subsequent attempt to reenable protection on the columns failed.

Cause: Disabling protection on the column failed.

Cause: There was no column for the given sensitive column type.

Cause: There was no policy associated with the sensitive column type.

Cause: A Transparent Sensitive Data Protection policy that was enabled on a column could not be altered or dropped.

Cause: A Transparent Sensitive Data Protection policy that was associated with a sensitive column type could not be dropped.

Cause: The given condition was not found for the policy.

Cause: The default policy for Transparent Sensitive Data Protection could not be altered.

Cause: The default policy for Transparent Sensitive Data Protection could not be dropped.

Cause: An invalid parameter was found for the given security feature.

Cause: An invalid parameter was found for the given security feature.

Cause: Invalid input was given for the parameter.

Cause: The given condition was invalid.

Cause: A Transparent Sensitive Data Protection policy that was enabled on one or more columns of a particular sensitive type could not be disassociated from the sensitive type.

Cause: One or more columns from the XML input were already identified as sensitive by a different source.

Cause: A column in a SYS-owned table was being marked as sensitive.

Cause: The SEC_RELEVANT_COLS parameter was specified while configuring a Transparent Sensitive Data Protection (TSDP) policy. SEC_RELEVANT_COLS_OPT parameter can be specified to indicate that TSDP should input the sensitive column as input to SEC_RELEVANT_COLS parameter at the time of enabling protection.

Cause: An attempt was made to perform the TSDP operation from inside the application install or patch begin-end block.

Cause: An attempt was made to mark one of the virtual or hidden columns as sensitive.

Cause: RMAN attempted to use the specified data file number, but this data file number was already in use by a different container database.

Cause: During ALTER DATABASE RENAME or RMAN command SWITCH, the rename was specified for an instantly restored file.

Cause: This data file copy was instantly restored. Cataloging such file is not supported.

Cause: An attempt was made to restore a data file copy in instant restore mode. This is not supported.

Cause: This data file was instantly restored with the full option. A background process was repopulating the data file. An attempt to take the data file out of the process failed. Deleting or restoring such files is not supported.

Cause: This data file was instantly restored. Moving such file is not supported.

Cause: During an instant restore, it was not possible to initialize the destination data file. There might be other messages on the error stack or alert log or trace file that indicate the specific reason for the failure. One common reason for this message is that the instant restore feature is disabled in this database.

Cause: This data file was instantly restored. An attempt was made to create a record in the control file for the data file. Unless the database is mounted, this command cannot be completed.

Cause: A backup or copy was attempted while restore, recover or block media recovery was in progress. This error should be preceded by another error indicating file access enqueue problem for a file specified in a backup, copy or restore operation.

Cause: During transport, an encrypted tablespace could not find its rewrapped key as part of an RMAN cross-platform command.

Cause: Restore with encryption and decryption is only supported on 12.2 compatible databases and above.

Cause: An attempt was made to restore with encryption and decryption for backups with compatibility less or equal to Oracle Database 11g release 2 (11.2).

Cause: The indicated file was not included in the backup because it belongs to a dropped pluggable database (PDB).

Cause: An attempt was made to backup a control file when the mounted control file at that time was a backup control file. This is not allowed.

Cause: The physical block size and logical block size of the backup piece did not match.

Cause: Some restored files belonged to the dropped pluggable database (PDB) with respect to the current control file.

Cause: An attempt was made to access a backup piece or data file. This attempt failed because the specified file is not known to the current container.

Cause: The incremental-start system change number (SCN) which was specified when starting an incremental data file backup is greater than the data file checkpoint SCN, which could cause some blocks to be missed.