Cause: Save undo for the offline tablespace at segment MAXSIZE.

Cause: Extending a temporary segment violated MAXSIZE limit.

Cause: Extending a table partition violated MAXSIZE limit.

Cause: Extending a table violated MAXSIZE limit.

Cause: Extending a cluster violated MAXSIZE limit.

Cause: Extending an index partition violated MAXSIZE limit.

Cause: Extending an index subpartition violated MAXSIZE limit.

Cause: Extending an index violated MAXSIZE limit.

Cause: Extending a LOB segment violated MAXSIZE limit.

Cause: Extending a LOB segment violated MAXSIZE limit.

Cause: Extending a LOB segment violated MAXSIZE limit.

Cause: Extending a table subpartition violated MAXSIZE limit.

Cause: Invalid value was specified for MAXSIZE storage clause.

Cause: Minimum of 1M should have been specified against the MAXSIZE storage clause.

Cause: Value of MIN retention should have been nonzero.

Cause: The operation to ALTER FREELIST/RETENTION was not supported on SECUREFILE segment.

Cause: Extending a rollback segment violated MAXSIZE limit.

Cause: Creation of SECUREFILE segment failed due to small tablespace extent size.

Cause: Temp LOB segments used for temporary LOBs are deleted only on session exit which may lead to large amounts of memory being held across multiple sessions.

Cause: Extending the heat map segment violated the MAXSIZE limit.

Cause: SYSAUX tablespace has uniform extent allocation and the extent size is not a multiple of megabyte.

Cause: Parameter value contained a comma.

Cause: Encountered a value of unsupported type in a SQL/XML DML operator. SQL/XML operators, such as UPDATEXML, expect value operands of type VARCHAR2 and XMLTYPE. XML DML replication is not supported for SQL/XML DML operators with values of unsupported types or very large values of supported types.

Cause: Encountered a newer version of XML redo diff that is not supported.

Cause: An attribute was being populated or updated with characters which are not valid for XML and therefore could not be supplementally logged.

Cause: The function was specified outside of the MATCH_RECOGNIZE clause. This function is only allowed in the MATCH_RECOGNIZE clause.

Cause: The specified lower bound or upper bound value was greater than UB4MAXVAL. The lower bound value must be non-negative. The upper bound value must be strictly positive. The upper bound value must be greater than or equal to the lower bound value.

Cause: The specified variable name was invalid. Variable names are not allowed to be "^", "$", or "*".

Cause: The specified variable definition was invalid. Variables defined in the DEFINE clause must be in the PATTERN clause. Variables defined in the SUBSET clause cannot be in the PATTERN clause. Variables cannot be defined twice either in the SUBSET clause or the DEFINE clause.

Cause: The referenced variable was invalid. Variables referenced in the SUBSET clause must be in the PATTERN clause. Variables referenced in the DEFINE clause, the MEASURES clause, and the AFTER MATCH SKIP TO must be in the PATTERN clause or defined in the SUBSET clause.

Cause: The expression was not aliased. MEASURES clause items have to be aliased.

Cause: An attempt was made to nest aggregates/FIRST/LAST/PREV/NEXT. Aggregates/FIRST/LAST/PREV/NEXT cannot be nested. The only exception allowed is PREV/NEXT(FIRST/LAST()).

Cause: An attempt was made to use MATCH_NUMBER or CLASSIFIER in the MATCH_RECOGNIZE clause. CLASSIFIER and MATCH_NUMBER can only be used in the MEASURES clause. CLASSIFIER can only be used if the query is ALL ROWS PER MATCH. CLASSIFIER and MATCH_NUMBER cannot be used inside aggregates/FIRST/LAST/PREV/NEXT.

Cause: An attempt was made to define aggregates/FIRST/LAST/PREV/NEXT over multiple variables. Aggregates/FIRST/LAST/PREV/NEXT cannot be defined over multiple variables.

Cause: An attempt was made to use RUNNING or FINAL in MATCH_RECOGNIZE. RUNNING or FINAL can only be used on aggregate/FIRST/LAST. FINAL aggregate/FIRST/LAST is not allowed in the DEFINE clause.

Cause: An attempt was made to use correlated subqueries in the MATCH_RECOGNIZE clause. Correlated subqueries are currently not allowed in the MATCH_RECOGNIZE clause.

Cause: An attempt was made to use correlation variables in the MATCH_RECOGNIZE clause. Correlation variables are currently not allowed in the MATCH_RECOGNIZE clause.

Cause: An unsupported aggregate was specified in the MATCH_RECOGNIZE clause. Only COUNT, SUM, AVG, MIN, and MAX are currently supported in the MATCH_RECOGNIZE clause. Distinct aggregates are currently not supported in the MATCH_RECOGNIZE clause.

Cause: There were empty matches for the quantified subpattern in the PATTERN clause. Quantified subpatterns are currently required to match one or more rows.

Cause: AFTER MATCH SKIP TO variable was not bound in the match found due to pattern operators such as |, *, ?, and so on.

Cause: An attempt was made to use exclusion syntax with WITH UNMATCHED ROWS. Exclusion syntax {- -} cannot be used with WITH UNMATCHED ROWS.

Cause: The number of items in PARTITION BY, ORDER BY, or MEASURES clause exceeded the maximum allowed. There cannot be more than UB2MAXVAL elements in PARTITION BY, ORDER BY, or MEASURES clause.

Cause: AFTER MATCH SKIP TO option repositioned the next match at the start of the previous one resulting in an infinite loop.

Cause: MATCH_RECOGNIZE pattern was too large. More than UB2MAXVAL elements in alternation, concatenation, or permute, or more than UB4MAXVAL states in the state machine are currently not supported. Permute with more than 7 elements or bounded quantifier bound greater than 200 are also currently not supported.

Cause: An attempt was made to use a subquery containing a MATCH_RECOGNIZE clause inside a MATCH_RECOGNIZE clause. Subqueries containing MATCH_RECOGNIZE clauses are currently not allowed in the MATCH_RECOGNIZE clause.

Cause: An attempt was made to use something other than a constant or a bind variable as the offset for MATCH_RECOGNIZE navigation operators FIRST, LAST, PREV, or NEXT. Offset for MATCH_RECOGNIZE navigation operators have to be constants or bind variables.

Cause: An attempt was made to use MATCH_RECOGNIZE on a lateral view, which is not supported.

Cause: The SQL ROW LIMITING expression contained components other than literals, binds, correlation variables, or subqueries.

Cause: The specified data file was being moved.

Cause: The move operation encountered an error for the moved data file. The error might be caused by file going offline or by an I/O error. See alert or trace files in all instances for further information.

Cause: An obsolete copy of a data file left from a data file move operation was used for the CREATE CONTROLFILE command or file header read.

Cause: A half-done copy of a data file created from a previous data file move operation was used for the CREATE CONTROLFILE command or file header read.

Cause: Differring database names were found in database file headers.

Cause: An operating system error or device error occurred when retrieving the file's size.

Cause: An undo tablespace file was detected as inaccessible due to media failure.

Cause: A data file was detected as inaccessible due to media failure.

Cause: The pathname of a new item specified in a DBFS API operation already exists.

Cause: The pathname of an item specified in a DBFS API operation has one or more invalid parent components.

Cause: The pathname of an item specified in a DBFS API operation is invalid.

Cause: The current DBFS API operation is unsupported by a provider.

Cause: The current DBFS API operation specifies an invalid combination of arguments for the specified pathname(s) and operation.

Cause: The current DBFS API operation failed access control checks for the pathname(s) being accessed.

Cause: A DBFS API locking operation could not be completed due to conflicts in the locking protocol.

Cause: The current operation specifies an invalid store name.

Cause: The current operation specifies an invalid mount-point.

Cause: The current operation refers to an invalid or incomplete or non-conformant store provider package.

Cause: The current operation attempts to modify a store via a read-only mount (or specifies a read-only store).

Cause: The current operation attempts to span 2 or more different stores and cannot be implemented entirely by the DBFS API.

Cause: The current operation specifies a path that is a directory element, when a non-directory element is expected.

Cause: The current operation specifies a path that is not a directory element, when a directory element is expected.

Cause: The current operation specifies a directory element that is not empty as required.

Cause: An attempt was made to alter the unstructured component and structured component of an XMLIndex at the same time.

Cause: An attempt was made to create an XMLIndex with a structured component on a CLOB column within the object-relational storage model.

Cause: An attempt was made to create an XMLIndex on an XML type table or column that uses the object-relational storage model.

Cause: An attempt was made to use a column name already in use by an internal column of the structured component of the XMLIndex.

Cause: An attempt was made to create a domain index on an internal table of an XMLIndex.

Cause: An attempt was made to define COLUMNS with incorrect use of comma punctuation.

Cause: An internal error occured when updating the index metadata. The dbms_metadata.get_ddl function may return improper metadata.

Cause: An attempt was made to truncate a table that has an XMLIndex whose internal table has been indexed using Oracle Text.

Cause: See associated error message.

Cause: See associated error message.

Cause: See associated error message.

Cause: See associated error message.

Cause: See associated error message.

Cause: The non-partitioned table had no XMLIndex.

Cause: The XMLIndexes on the two tables had different path subsets.

Cause: The XMLIndexes on the two tables had different deferred DML modes.

Cause: One of the XMLIndexes had no unstructured component.

Cause: One of the XMLIndexes had no structured component.

Cause: The XMLIndexes had different structured components.

Cause: See associated error message.

Cause: See associated error message.

Cause: See associated error message.

Cause: See associated error message.

Cause: See associated error message.

Cause: See associated error message.

Cause: See associated error message.

Cause: See associated error message.

Cause: See associated error message.

Cause: Namespace mapping was invalid. The syntax is XMLNS="string".

Cause: See associated error message.

Cause: See associated error message.

Cause: See associated error message.

Cause: See associated error message.

Cause: See associated error message.

Cause: See associated error message.

Cause: An attempt was made to drop an XMLIndex whose internal table has been indexed using Oracle Text.

Cause: An attempt was made to drop groups from an XMLIndex whose internal table has been indexed using Oracle Text.

Cause: An attempt was made to create an XML index with VIRTUAL column not of XMLTYPE.

Cause: An attempt was made to create an XML index with VIRTUAL column but without required chaining XMLTABLE.

Cause: An attempt was made to create a shared table with more than one columns.

Cause: An attempt was made to create shared tables with inconsistent semantics for truncation. Either all shared tables should have or should not have (TRUNCATE) keyword.

Cause: An attempt was made to share a table without an XMLTYPE column.

Cause: An attempt was made to share a table with different paths.

Cause: One of the rewrites being tried by XMLIndex engine failed.

Cause: Internal error.

Cause: NONBLOCKING COMPLETE or ABORT is only allowed for XMLIndex that is being modified using NONBLOCKING ADD_GROUP or ADD_COLUMN.

Cause: NONBLOCKING COMPLETE is only allowed for XMLIndex that is being modified using NONBLOCKING ADD_GROUP or ADD_COLUMN and there are no pending rows left.

Cause: An attemp was made to alter an XMLIndex that is already being modified using NONBLOCKING ADD_GROUP or ADD_COLUMN. Only NONBLOCKING COMPLETE or ABORT alter index operations are allowed. Also, NONBLOCKING operation is not allowed with alter index rebuild.

Cause: DBMS_XMLINDEX.PROCESS_PENDING was called on an index that was not modified using NONBLOCKING ADD_GROUP or ADD_COLUMN.

Cause: DBMS_XMLINDEX.PROCESS_PENDING was called on an index that does not have any pending rows to process.

Cause: N/A

Cause: The LOB value associated with the input locator did not exist in client-side reference tables.

Cause: Local database encountered a temporary or abstract LOB created on a remote database. Remote access to temporary or abstract LOB is not supported.

Cause: An attempt was made to convert CLOB to CHAR, where the LOB size was bigger than the buffer limit for CHAR types or the CHAR buffer was not big enough to hold all data after character set conversion.

Cause: The requested operation could not complete because a partial multibyte character was found at the end of the input.

Cause: An attempt was made to use other triggering events (such as INSERT, DELETE and UPDATE) with the LOGICAL LOB UPDATE event.

Cause: INSTEAD OF LOGICAL LOB UPDATE trigger was not allowed.

Cause: The LOGICAL LOB UPDATE trigger could not be created on a non-LOB column of a table. The column name has to be specified while creating the trigger. Only one column name can be specified while creating the trigger.

Cause: An attempt was made to create a before or after LOGICAL LOB UPDATE trigger without a FOR EACH ROW clause.

Cause: WHEN clause was specified for a LOGICAL LOB UPDATE trigger.

Cause: The LOGICAL LOB UPDATE trigger did not follow other LOGICAL LOB UPDATE triggers. Non-LOGICAL LOB UPDATE triggers cannot follow LOGICAL LOB UPDATE triggers.

Cause: An attempt was made to access an invalid column. A LOGICAL LOB UPDATE trigger can only access ROWID column and the column for which it was specified. Access to other columns is not allowed.

Cause: A LOGICAL LOB UPDATE trigger could not be created on view.

Cause: A compound LOGICAL LOB UPDATE trigger could not contain statement level actions.

Cause: Crossedition LOGICAL LOB UPDATE triggers were not supported.

Cause: An attempt was made to use a subprogram that is for internal Oracle development use only.

Cause: The specified archive compression level value was invalid. Valid values are LOW or HIGH.

Cause: An attempt was made to use Exadata Hybrid Columnar Compression on unsupported storage.

Cause: One of the following was attempted: - Create a hybrid columnar compressed table with a LONG data type. - Alter an existing table with a LONG data type to be hybrid columnar compressed. - Add a LONG data type column to a hybrid columnar compressed table.

Cause: An attempt was made to use Hybrid Columnar Compression with row-level locking on an unsupported storage type.

Cause: INMEMORY was specified more than once.

Cause: An attempt was made to use the in-memory column store feature with Oracle RAC on an unsupported system.

Cause: The FastStart feature was enabled but its tablespace was offline.

Cause: An attempt was made to use the in-memory column store FastStart feature on an unsupported system.

Cause: An OCI error occurred when enabling or disabling FastStart.

Cause: Package installation invoked on database version that was not 10.2, 11.1 or 11.2..

Cause: XMLSchema was not provided to the procedure or function call..

Cause: An input parameter was null.

Cause: An input string was provided whose length exceeded 30 character.

Cause: The parameters provided to annotate the XMLSchema did not match any entities in the XMLSchema.

Cause: The parameters provided to annotate the XMLSchema did not match any entities in the XMLSchema.

Cause: The parameters provided to annotate the XMLSchema matched to multiple entities in the XMLSchema.

Cause: The name for the collection table exceeded 25 characters.

Cause: XPath could not be mapped to existing table.

Cause: The XPath string provided to the procedure was not valid.

Cause: An invalid collection table was specified by the XPath string.

Cause: The procedure renameCollectionTable did not work on binary storage model.

Cause: An attempt was made to disable constraints or indexes for non-global schemas owned by other users or a non schema based table/column.

Cause: An attempt was made to enable constraints or indexes for schemas owned by other users or for a non schema based table/column.

Cause: The namespace declaration was invalid.

Cause: The tab_name parameter provided the name of a table that did not exist..

Cause: The col_name parameter provided the name of a column that did not exist in the given table.

Cause: The col_name parameter provided the name of a column that was not an XMLType column.

Cause: The name for the collection table could not be used because it already exists.

Cause: The table_name parameter provided the name of a table that was not an XMLType table.

Cause: An attempt was made to create a new token table. If encountered during an import, a critical patch was possibly missing on the export database.

Cause: The specifications were either a duplicate of each other or were conflicting.

Cause: The specified RESTART was a duplicate.

Cause: An attempt was made to create more than one user tablespace during database creation.

Cause: An attempt was made to issue a SQL statement that exceeded the maximum allowed length of a statement.

Cause: The Backup Appliance was in the process of shutting down. This message is recorded in the incident log for the Backup Appliance. When the shutdown completes, the incident is marked as FIXED.

Cause: The specified storage location did not contain enough space to fulfill the reservations of all of the databases assigned to it. This error will be seen if a storage location lost part of its disk space and was in the process of being repaired.

Cause: An error was returned while trying to rebuild or repair the container files used to store data from protected databases.

Cause: A task needed to be interrupted because it detected a resource limitation such as insufficient temporary table space or a snapshot being too old. It will be retried once the contention for the resource decreases. The secondary messages will identify the resource that has been exhausted.

Cause: The storage destination contained a syntax error.

Cause: More than one polling_location was specified. Only one polling_location is allowed.

Cause: The polling_location specified an ASM-based location. Only non-ASM-based polling_locations are supported.

Cause: The storage destination referenced a non-ASM storage location. Only ASM-based storage destinations are allowed. The operation has been rolled back.

Cause: The size requested for the storage destination was smaller than its current size.

Cause: The size requested for the storage destination was larger than its current used space plus its currect free space.

Cause: The redundancy type for the specified diskgroup was not one of {NORMAL | HIGH | EXTERN}.

Cause: The minimum allocation size of the specified storage location was not the same as the specified diskgroup allocation unit size.

Cause: The configured network chunk size was not a multiple of the specified diskgroup allocation unit size.

Cause: The diskgroup allocation unit size was not a power of two.

Cause: The diskgroup allocation unit size was less than two megabytes.

Cause: No storage was allocated and initialized for the specified storage location.

Cause: No storage was allocated and initialized for the specified storage location.

Cause: The specified number of tape drives was NULL or was less than or equal to zero.

Cause: The number of tape drives reserved for restore operations was NULL or was less than zero.

Cause: The number of tape drives reserved for restore operations was at least as large as the total number of drives available. The number of tape drives reserved for restore operations must be at least one less than the total number of drives available.

Cause: The number of streams was less than or equal to zero.

Cause: The number of streams was larger than the total number of drives available. The number of streams must be no larger than the total number of drives available.

Cause: The number of copies was either NULL or not in the range 1 through 4 inclusive.

Cause: The replication server name was longer than 32 characters.

Cause: The replication server proxy port number was less than or equal to zero.

Cause: A replication server proxy URL was provided but a proxy port number was not. If either a proxy URL or a proxy port are specified, both must be specified.

Cause: A replication server proxy port number was provided but a proxy URL was not. If either a proxy URL or a proxy port are specified, both must be specified.

Cause: The HTTP server at the replication host site has not been configured.

Cause: An attempt was made to move an individual backup piece, but the backup set of which this backup piece was a member was not a KEEP backup.

Cause: A new archived log or backup set belonging to the new incarnation was received at Backup Appliance.

Cause: The specified task was restarted an unexpected number of times. Tasks get interrupted when there is competition for resources. This is only a warning. It does not necessarily indicate a problem with the Backup Appliance.

Cause: A valid pluggable database name was not present where required.

Cause: A valid administrative user name was not present where required by the syntax of CREATE PLUGGABLE DATABASE statement.

Cause: A valid administrative user password was not present where required by the syntax of CREATE PLUGGABLE DATABASE statement.

Cause: A valid XML file name was not present where required by the syntax of CREATE PLUGGABLE DATABASE statement.

Cause: A valid database link name was not present where required by the syntax of CREATE PLUGGABLE DATABASE statement.

Cause: Either source or replacement file name pattern was missing or invalid in a SOURCE_FILE_NAME_CONVERT or FILE_NAME_CONVERT clause.

Cause: An ENABLE PLUGGABLE DATABASE clause was not present where required by the syntax of CREATE DATABASE statement.

Cause: A duplicate ENABLE PLUGGABLE DATABASE clause was specified in a CREATE DATABASE statement.

Cause: A SEED clause was not present where required by the syntax of CREATE DATABASE statement.

Cause: User attempted to create more than supported number of pluggable databases.

Cause: User attempted to specify a pluggable database that does not exist.

Cause: User attempted to create a pluggable database with a name that already exists.

Cause: An invalid CONTAINER clause was encountered.

Cause: An invalid SHARING clause was encountered.

Cause: A valid container name was not present where required by the syntax of ALTER SESSION SET CONTAINER or ALTER USER ... SET|ADD|REMOVE CONTAINER_DATA statement.

Cause: Data files, and possibly other files, needed to be copied as a part of creating a pluggable database. However, Oracle Managed Files (OMF) was not enabled, PDB_FILE_NAME_CONVERT was not defined, and there was a failure to specify the FILE_NAME_CONVERT clause.

Cause: User attempted to drop or alter the Seed pluggable database which is not allowed.

Cause: Oracle Managed Files (OMF) was not enabled and PDB_FILE_NAME_CONVERT was not defined. The FILE_NAME_CONVERT or the NOCOPY clause was not specified as a part of creating a pluggable database using data files.

Cause: An attempt was made to open a pluggable database that was already opened.

Cause: An attempt was made to close a pluggable database that was already closed.

Cause: A SHARING clause was encountered in unexpected context.

Cause: A statement contained multiple CONTAINER clauses.

Cause: A statement attempted to create a new transaction in the current container while there was an active transaction in another container.

Cause: An operation was attempted on a pluggable database that was not open.

Cause: An operation was attempted on a pluggable database that was not closed on all Oracle RAC instances.

Cause: An error occurred while trying to parse or write to the XML metadata file.

Cause: An error occurred while trying to parse the XML metadata file.

Cause: Error occurred while trying to open the datafile.

Cause: A Local User issued a GRANT or REVOKE statement specifying CONTAINER=ALL, which is illegal.

Cause: A Common User issued a GRANT statement specifying CONTAINER=ALL and naming a Local User or Role as a grantee, which is illegal.

Cause: A Common User issued a REVOKE statement specifying CONTAINER=ALL and naming a Local User or Role as a grantee, which is illegal.

Cause: A user issued a GRANT or REVOKE statement specifying CONTAINER=ALL and listing a Local Role among roles to be granted or revoked, which is illegal.

Cause: A GRANT or REVOKE statement was issued specifying CONTAINER=ALL and naming a local object on which privileges are to be granted or revoked, which is illegal.

Cause: User attempted to describe a pluggable database without specifying an output XML file location.

Cause: The pluggable database had ongoing or active transactions that need to be recovered.

Cause: Attempted to perform an operation on a pluggable database in incorrect open mode.

Cause: A GRANT or REVOKE statement was issued specifying CONTAINER=ALL and naming a local user on which privileges are to be granted or revoked, which is illegal.

Cause: Table or view whose definition contained a CONTAINER_DATA clause lacked a column used to identify a container to which data belongs or the column was of unexpected type.

Cause: An operation was attempted that can only be performed in the root container.

Cause: An attempt was made to modify CONTAINER_DATA attribute for user SYS or SYSBACKUP which is disallowed.

Cause: The name was already used by another container.

Cause: TABLESPACE keyword was missing.

Cause: An option other than MAXSIZE or MAX_SHARED_TEMP_SIZE was specified.

Cause: An operation was attempted on a pluggable database that was not in restricted mode.

Cause: An operation was attempted that can only be performed from within a pluggable database.

Cause: An attempt was made to issue a metadata link ddl for an object that was invalid or compiled with errors in CDB$ROOT.

Cause: An error was encountered when executing a statement in one of the pluggable databases.

Cause: An attempt was made to create a local user or role in CDB$ROOT.

Cause: An attempt was made to issue a Common DDL in a pluggable database.

Cause: A valid container identifer was not specified.

Cause: An attempt was made to combine one operation that applies to all containers with another that only applies to the local container into one statement.

Cause: An attempt was made by a global user to change the container using the ALTER SESSION SET CONTAINER statement.

Cause: An attempt was made to open a pluggable database in a mode incompatible with that of the CDB.

Cause: User connected to a pluggable database attempted to modify a CONTAINER_DATA attribute which is illegal.

Cause: User issuing ALTER USER ... SET|REMOVE CONTAINER_DATA = ... statement attempted to exclude the current container from a CONTAINER_DATA attribute.

Cause: Object referenced in an ALTER USER statement modifying an object-specific CONTAINER_DATA attribute is not a CONTAINER_DATA table or view.

Cause: Duplicate references to a name of some container was encountered in a CONTAINER_DATA clause.

Cause: User attempted to add container(s) to an object-specific CONTAINER_DATA attribute which has not been explicitly set or has been set to DEFAULT or remove containers from a CONTAINER_DATA attribute which has not been explicitly set or has been set to DEFAULT.

Cause: User attempted to remove from a CONTAINER_DATA attribute container(s) which do not belong to it.

Cause: User attempted to add/remove container(s) to/from a CONTAINER_DATA attribute whose current value is ALL, which is not supported.

Cause: The CONTAINER_DATA clause was specified twice.

Cause: The contents of the XML metadata file were different from the actual file properties.

Cause: The ALTER USER or ALTER ROLE statement was issued specifying CONTAINER=ALL and listing a local user or role among the users or roles to be altered, which is illegal.

Cause: An attempt was made to apply the specified changes to the current container.

Cause: An attempt was made to reference a local role across all containers using the DEFAULT ROLE clause.

Cause: An attempt was made to create a trigger that fires after a pluggable database has been unplugged. This type of trigger is not supported.

Cause: An attempt was made to create a pluggable database trigger that fires after a role change occurs from a standby database to primary or vice versa. This type of trigger is not supported.

Cause: An attempt was made to create an AFTER CLONE trigger on a schema or a database. This type of trigger is not supported.

Cause: An attempt was made to create a BEFORE UNPLUG trigger on a schema or a database. This type of triggers is not supported.

Cause: An attempt was made to create a database event trigger on a pluggable database while not connected to a pluggable database. This is not supported.

Cause: An attempt was made to create a trigger that fires before a pluggable database has been cloned. This type of trigger is not supported.

Cause: An attempt was made to support editions for common users.

Cause: An attempt was made to map the database ID to the pluggable database name.

Cause: An operation was attempted on a database or pluggable database that is not open in read only mode

Cause: There was no more room in the control file for adding pluggable databases.

Cause: The pluggable database is in the middle of shutdown abort

Cause: An attempt was made to create a common object that does not exist in root.

Cause: The pluggable database has been created and not opened.

Cause: The pluggable database has been unplugged.

Cause: An operation in an Oracle-supplied script was attempted that can only be performed in the root container.

Cause: An inconsistency between the control file and the data dictionary was found and fixed during the database open. The database open needs to be executed again.

Cause: The pluggable database was not open anywhere but was not marked as clean yet.

Cause: User attempted an operation that is only allowed in a CDB

Cause: An undo tablespace or rollback segment operation was attempted that can only be performed in the root container.

Cause: An attempt to revoke a system privilege that was granted with a different scope has been made. The user tried to either revoke a common privilege in the current container or to revoke a local privilege in a container database (CDB).

Cause: An attempt was made to open a multitenant container database without the correct parameter set for a multitenant container database in the initialization parameter file.

Cause: An attempt was made to create a local user or role with a name that was not valid for local users or roles. In addition to the usual rules for user and role names, local user and role names cannot start with C## or c##.

Cause: An attempt was made to create a common object with a name that was not valid for common objects. In addition to the usual rules for object names, common object names must consist only of ASCII characters.

Cause: An attempt was made to create a common user or role with a name that was not valid for common users or roles. In addition to the usual rules for user and role names, common user and role names must start with C## or c## and consist only of ASCII characters.

Cause: CDB$VIEW may be applied to a valid table name of the form <varname>owner</varname>.<varname>tablename</varname>

Cause: Column with unsupported datatype was selected from a CDB View.

Cause: An operation was attemped inside a pluggable database that requires the container database (CDB) to be open. *Aciton: Open the CDB and then reissue the operation.

Cause: Path prefix was missing or invalid.

Cause: An attempt was made to use a non container database control file to startup a container database (CDB).

Cause: A valid instance name was not present where required by the syntax of a ALTER PLUGGABLE DATABASE statement.

Cause: ALTER PLUGGABLE DATABASE ... OPEN UPGRADE was specified, but the root is open READ ONLY, so the specified PDBs will also be opened READ ONLY, and UPGRADE cannot be specified for PDBs being opened READ ONLY.

Cause: The pluggable database status was INACTIVE. It was still being created or there was an error during the create operation.

Cause: Data files were not specified in a CREATE CONTROLFILE statement in the SYSTEM tablespace of a pluggable database.

Cause: Data files were not specified in a CREATE CONTROLFILE statement of a pluggable database.

Cause: An error was encountered when executing a pluggable database task on one of the Oracle RAC instances.

Cause: An attempt was made to use a cursor that was parsed or executed in a different container.

Cause: An operation was attempted that is not supported in the Container Database root.

Cause: An attempt was made to use an invalid or inactive instance name in the instance clause to alter the state of a pluggable database.

Cause: An attempt was made to relocate a pluggable database to the current instance.

Cause: Media recovery stopped because the pluggable database was either unplugged, dropped or renamed on the primary database.

Cause: The value of MAX_PDB_STORAGE specified in the ALTER or CREATE PLUGGABLE DATABASE statement is less than the current space usage of data files and temporary files of the container.

Cause: Space usage in the current container exceeded the value of MAX_PDB_STORAGE for the container.

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 directives.

Cause: The database character set of the container database was not a superset of the database character set of the pluggable database being plugged in.

Cause: The CONTAINER clause was specified when not connected to a container database (CDB).

Cause: An attempt was made to perform an operation affecting a pluggable database while connected to a different pluggable database.

Cause: The national character set of the container database was not the same as the national character set of the pluggable database being plugged in.

Cause: The XML metadata file for the pluggable database being plugged in contained a database or national character set ID that was not valid for the container database. This can happen if the XML file is manually modified, if it is corrupted on disk, or if the set of supported character sets differs between the container database and the source database of the pluggable database because a user-defined character set has not been installed in the Oracle Home directory of the container database.

Cause: Clients earlier than Oracle Database 12c Release 1 do not support this feature.

Cause: While creating a pluggable database, the GUID conflicted with the GUID of an existing container in the container database.

Cause: An attempt was made to set the container inside a context where such an operation is prohibited.

Cause: An attempt was made to provide a file name that did not have an XML extension.

Cause: The pluggable database was not closed cleanly and there are active transactions that need to be recovered.

Cause: An attempt was made torecover a pluggable database (PDB) without specifying an output XML file location.

Cause: An attempt was made to recover a pluggable database (PDB) without specifying a data file location.

Cause: The pluggable database was already opened on all instances.

Cause: An attempt was made to relocate more than one pluggable database.

Cause: An attempt was made to use a feature that is not supported in a pluggable database.

Cause: The endian of the container database was not the same as the endian of the pluggable database being plugged in.

Cause: An ALTER SESSION SET CONTAINER operation was attempted in a context where such an operation is prohibited.

Cause: An attempt was made to specify an SPFILE name for a pluggable database.

Cause: The pluggable database is in the middle of a Pluggable Database (PDB) RESETLOGS operation.

Cause: Either the specified data file was restored from a backup that was taken during a period of time that was discarded by a RESETLOGS operation, or Oracle could not identify which pluggable database incarnation the file belongs to. The alert log contains more information.

Cause: Either the XML metadata file or the data file was corrupt.

Cause: An attempt was made to create a common profile with a name that is not valid for common profiles. Common profile names must start with C## or c## and consist only of ASCII characters.

Cause: An attempt was made to create a local profile with a name that is not valid for local profiles. Local profile names cannot start with C## or c##.

Cause: An attempt was made to alter a local profile using an ALTER PROFILE statement with the CONTAINER=ALL clause.

Cause: An attempt was made to create a local profile in CDB$ROOT.

Cause: An attempt was made to disable a restricted session while an unresolved error existed in PDB_PLUG_IN_VIOLATIONS.

Cause: An attempt was made to FORCE open a pluggable database on more than one instance.

Cause: An attempt was made to unlock a common user account in a pluggable database (PDB) which was locked in the root of the container database.

Cause: An attempt was made to specify a DB_UNIQUE_NAME in an ALTER SYSTEM statement without SCOPE=SPFILE.

Cause: An attempt was made to FORCE open a pluggable database to or from upgrade mode.

Cause: An attempt was made to create a pluggable database (PDB) whose name conflicts with the existing service name in the container database (CDB) or the PDB.

Cause: An attempt was made to start an instance as a container or a non-container database when atleast one of the other instances was started in a different mode.

Cause: An attempt was made to use an invalid tablespace name or a mandatory tablespace name (SYSTEM or SYSAUX) in the USER_TABLESPACES clause when creating a pluggable database.

Cause: An attempt was made to bring online one or more datafiles belonging to a pluggable database that is disabled for recovery.

Cause: An attempt was made to bring online a tablespace that was either missing in the plug XML file or excluded when the pluggable database was created.

Cause: An attempt was made to change the default logging attribute to be the same as the current attribute value for the pluggable database.

Cause: Source file directory was missing or invalid.

Cause: An attempt was made to plug in a pluggable database with an incompatible version of the multitenant container database.

Cause: SOURCE_FILE_NAME_CONVERT and SOURCE_FILE_DIRECTORY clauses were both specified.

Cause: A matching file was not found in the directory specified with the SOURCE_FILE_DIRECTORY clause.

Cause: An attempt was made to use an invalid service name in the services clause.

Cause: An attempt was made to pass an invalid cleanup task ID to the DBMS_PDB.CLEANUP_TASK function.

Cause: An attempt was made to clone a pluggable database which contains some clustered tables or index organized tables or advanced queue tables.

Cause: The user's account expired and the password needs to be changed by connecting to the root of the multitenant container database

Cause: The database was in NOARCHIVELOG mode when pluggable database (PDB) shutdown abort was attempted.

Cause: The path specified in CREATE_FILE_DEST clause was missing or invalid.

Cause: An attempt was made to run noncdb_to_pdb.sql when the version of the pluggable database (PDB) was different from the version of the multitenant container database (CDB).

Cause: An attempt was made to run noncdb_to_pdb.sql when the multitenant container database (CDB) was in upgrade mode.

Cause: An operation involving PFILE was issued in a pluggable database without specifying the PFILE name

Cause: An error was encountered while attempting to copy the file while creating a pluggable database.

Cause: An attempt to create an XML file failed because a file with that name already exists.

Cause: An attempt was made to specify a value of FALSE or OFF for the DB_BLOCK_CHECKING parameter in a pluggable database (PDB), when the value of DB_BLOCK_CHECKING parameter in the multitenant container database (CDB) is neither FALSE nor OFF. If the CDB has enabled the DB_BLOCK_CHECKING parameter, then the PDB cannot disable the DB_BLOCK_CHECKING parameter.

Cause: An attempt was made to run 'noncdb_to_pdb.sql' on a pluggable database (PDB) that was not an unconverted non-container database.

Cause: An attempt to revoke a privilege that was granted with a different scope has failed. The user tried to either revoke a common privilege in the current container or to revoke a local privilege in a multitenant container database (CDB).

Cause: The service name or network name in the specified service is invalid or it conflicts with an existing service name or network name in the container database.

Cause: An attempt was made to grant SYSDBA privilege locally in the root of a multitenant container database (CDB).

Cause: The block size of the system tablespace of the pluggable database to be plugged in did not match the block sizes configured in the container database.

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

Cause: An attempt was made to either enable a conflicting logging mode or to disable a logging mode when it was not enabled.

Cause: An attempt was made to drop a pluggable database without specifying the INCLUDING DATAFILES clause, and the pluggable database has not been unplugged.

Cause: An attempt was made to issue a CREATE PLUGGABLE DATABASE statement with a duplicate source or target file name for the source file name mentioned in the message. This could be caused by incorrect SOURCE_FILE_NAME_CONVERT or FILE_NAME_CONVERT clause.

Cause: An attempt was made to create a multitenant container database (CDB) view with an invalid table or view name.

Cause: An attempt was made to modify the state of a pluggable database which is currently in the middle of a state transition.

Cause: An attempt was made to FORCE open a pluggable database on only a few Oracle RAC instances where it is currently open.

Cause: An attempt was made to invoke DBMS_PDB.RECOVER() by specifying data files or a directory name containing data files belonging to different PDBs.

Cause: An attempt was made to invoke DBMS_PDB.RECOVER() by specifying data files or a directory name containing data files where no data file belonging to SYSTEM tablespace was found. SYSTEM tablespace is critical to recover a PDB.

Cause: User attempts to modify clustering clasue on a table that that does not have one.

Cause: Invalid option on CLUSTERING clause. Only [YES | NO ] ON LOAD or [YES | NO ] ON DATA MOVEMENT are valid.

Cause: Invalid usage of CLUSTERING clause. The clause can be specified only for CREATE/ATLER TABLE/SNAPSHOT/MATERIALIZED VIEW

Cause: A table can have only one clustering clause. The clasue was specified multiple times.

Cause: CLUSTERING clause conflicts with other clasues on the table. Custering cannot be used on IOT, CLUSTERED, GLOBAL TEMPORARY TABLE, EXTERNAL TABLE.

Cause: CLUSTERING was not followed by BY [LINEAR | MULTIDIMENSIONAL] ORDER.

Cause: Add CLUSTERING clause was specified on a table with an existing clustering clause.

Cause: More than 10 columns were specified in the BY ORDER subclause. You can have at most 10 columns in the BY ORDER subclause.

Cause: More than 40 columns were specified in the MULTIDIMENSIONAL ORDER subclause.You can have at most 40 columns in the MULTIDIMENSIONAL ORDER subclause.

Cause: A non-scalar column was specified in the BY LINEAR or MULTIDIMENSIONAL ORDER subclause. Also, virtual or hidden columns are not allowed.

Cause: An attempt was made to modify or drop a CLUSTERING clause in a table that had no CLUSTERING clause associated with it.

Cause: You have specified an invalid option on ALTER TABLE...CLUSTERING. For example, you specified DROP and ADD CLUSTERING in one statement.

Cause: An object was referenced in the CLUSTERING clause that could not be resolved to a base table reference.

Cause: A column resolved to multiple tables in the CLUSTERING clause.

Cause: The CLUSTERING clause had an OR condition and the individual join condition on the base table columns was not an equijoin.

Cause: Joins in the CLUSTERING referenced a dimension table more than once.

Cause: The dimension table in the CLUSTERING clause was illegal. Dimension table cannot be GLOBAL TEMPORARY TABLE or EXTERNAL TABLE.

Cause: The join between the fact and dimension tables in the CLUSTERING clause did not have a primary or unique key constraint on the dimension table.

Cause: Columns in the clustering group did not come from the same table. For example: .. CLUSTERING BY ..( (t1.c1, t2.c2), (t2.c1, t2.c2) ). Clustering group (t1.c1, t2.c2) must contain references to only one table.

Cause: The data type of columns in the join condition of CLUSTERING clause were not compatible. They must be of the same type.

Cause: An ALTER TABLE MODIFY COLUMN command was issued on a column on which a CLUSTERING clause exists.

Cause: An ALTER TABLE MODIFY CLUSTERING command was issued with the WITH MATERIALIZED ZONEMAP option but the table already had zonemap define on it.

Cause: An ALTER TABLE MODIFY CLUSTERING command was issued with the WITHOUT MATERIALIZED ZONEMAP option but the table did not have zonemap associated with the CLUSTERING clause.

Cause: More than 4 joins were specified in the CLUSTERING clause. You can have at most 4 joins to the dimension tables.

Cause: An attempt was made to define clustering on a table stored in non-Oracle Exadata storage.

Cause: Oracle cannot perform data clustering because an attempt was made to populate a clustering column with non-scalar data values, or a clustering column defaulted to non-scalar values was omitted.

Cause: An attempt was made to use advanced index compression on an unsupported storage type.

Cause: An invalid family was used to specify a parameter value.

Cause: The specified family could not be used in the current instance type.

Cause: The specified family could ot be used in the current instance type.

Cause: Too many characters were specified in the parameter qualifier in the initialization parameter file.

Cause: A SID was used with FAMILY.

Cause: An invalid family was specified for this instance in ORACLE_FAMILY.

Cause: The CONTAINER clause was set to ALL in the ALTER SYSTEM SET statement for a non-PDB modifiable parameter.

Cause: The specified family contained an illegal character or the family specified was too long, which cannot occur in an SPFILE setting. Illegal characters include *,#"'=() and whitespace.

Cause: DB_UNIQUE_NAME could not be modified, because a database resource identified by DB_UNIQUE_NAME existed in the cluster. To modify DB_UNIQUE_NAME, any resource it identifies must first be removed.

Cause: In a pluggable database environment, an attempt was made to modify a LOB using a locator which belongs to a different container.

Cause: The database did not open.

Cause: Oracle server encountered an error whose error code exceeded 65535. Older Oracle clients (prior to version 12) cannot handle error codes larger than 65535.