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: Clear free space operation was used on the temporary, undo, or SYSTEM tablespace, which is not supported.

Cause: Clear free space operation requires database compatibility with release 12.2.0.2 or later.

Cause: inmemory_xmem_size was less than the minimum expected by the system.

Cause: The temporary tablespace had sort segments in use.

Cause: An attempt was made to refresh the pluggable database to a system change number (SCN) that was less than or equal to the last refresh SCN.

Cause: There was insufficient disk space at the specified location.

Cause: A list of pluggable databases was given to a command but the named one is not of the same type as the earlier ones in the list. The different types are Data Guard pluggable databases and non Data Guard pluggable databases.

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: Parallel query failed to duplicate KEY VECTOR across Oracle RAC instances.

Cause: A query undergoing vector transform ran out of memory in an unrecoverable way. This may indicate that poor statistics caused vector transform to be used for an unsuitable query.

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

Cause: VECTOR ENCODE was specified on a column that is not an Oracle number.

Cause: The system hidden virtual columns could not be dropped or modified directly.

Cause: The value being deserialized was invalid.

Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on index-organized tables (IOT).

Cause: An attempt was made to CREATE TEMPORARY TABLE with MEMOPTIMIZE FOR WRITE feature.

Cause: An attempt was made to populate data into hash index when in Active Data Guard mode.

Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on a table with row movement enabled.

Cause: An attempt was made to use the DBMS_MEMOPTIMIZE.POPULATE procedure with an invalid schema name.

Cause: An attempt was made to use the DBMS_MEMOPTIMIZE.POPULATE procedure with an invalid table name.

Cause: An attempt was made to use the DBMS_MEMOPTIMIZE.POPULATE procedure with invalid information. Either the specified schema and table names are non-existent or MEMOPTIMIZE FOR READ feature is not enabled on the table.

Cause: An attempt was made to use the DBMS_MEMOPTIMIZE package without creating the MEMOPTIMIZE memory area.

Cause: MEMOPTIMIZE_WRITE hint was specified for the operation.

Cause: An attempt was made to use the COMPRESS option with MEMOPTIMIZE FOR READ feature.

Cause: An attempt was made to use MEMOPTIMIZE FOR READ on a table that did not have the PRIMARY KEY constraint or the PRIMARY KEY constraint is DEFERRABLE.

Cause: An attempt was made to set the MEMOPTIMIZE FOR WRITE attribute on a table with trigger.

Cause: An attempt was made to set the MEMOPTIMIZE FOR WRITE attribute on a table with foreign key constraint.

Cause: An attempt was made to set the MEMOPTIMIZE FOR WRITE attribute on a table with deferred storage.

Cause: An attempt was made to use the COMPRESS option with MEMOPTIMIZE FOR WRITE feature.

Cause: An attempt was made to use MEMOPTIMIZE FOR READ option on a PARTITION table or SUBPARTITION table level.

Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on index-organized tables (IOT).

Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on a table with VIRTUAL COLUMNS.

Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on a table with INVISIBLE COLUMNS.

Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on a table with an unsupported partitioning type.

Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a table with LOB columns.

Cause: An attempt was made to use the DBMS_MEMOPTIMIZE.POPULATE procedure on a tablespace whose BLOCK SIZE was not equal to DB_BLOCK_SIZE.

Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a table with VIRTUAL COLUMNS.

Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on a table with LOB columns.

Cause: An attempt was made to set the MEMOPTIMIZE FOR READ attribute on a table with deferred storage.

Cause: An attempt was made to use MEMOPTIMIZE FOR READ clause more than once.

Cause: An attempt was made to use MEMOPTIMIZE FOR WRITE clause more than once.

Cause: An attempt was made to CREATE PARTITIONED table with MEMOPTIMIZE FOR READ enabled.

Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a table with INVISIBLE COLUMNS.

Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a table with COLUMNS with default values.

Cause: An attempt was made to use MEMOPTIMIZE FOR WRITE option on a PARTITION table or SUBPARTITION table level.

Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a table with ENCRYPTED COLUMNS.

Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a table with an unsupported partitioning type.

Cause: An attempt was made to CREATE PARTITIONED table with MEMOPTIMIZE FOR WRITE enabled.

Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a table with COLLATED COLUMNS.

Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a table with UNUSED COLUMNS.

Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a table with OID COLUMNS.

Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a table with unsupported COLUMN type.

Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a table with XML COLUMNS.

Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a table in encrypted tablespace.

Cause: An attempt was made to use the MEMOPTIMIZE FOR WRITE attribute on a materialized view log.

Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on a table with encrypted columns.

Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on a table with XML COLUMNS.

Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on a table with UNUSED COLUMNS.

Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on a table with unsupported COLUMN type.

Cause: An attempt was made to use the MEMOPTIMIZE FOR READ attribute on a table with COLLATED COLUMNS.

Cause: An attempt was made to CREATE TEMPORARY TABLE with MEMOPTIMIZE FOR READ feature.

Cause: Unsupported DDL on MEMOPTIMIZE FOR WRITE table.

Cause: An attempt was made to enable the MEMOPTIMIZE FOR READ feature on an unsupported table.

Cause: An attempt was made to use external partition with a MEMOPTIMIZE FOR WRITE table.

Cause: MEMOPTIMIZE memory area was full and did not have any free buffers.

Cause: An attempt was made to use a bitmap index with a MEMOPTIMIZE FOR WRITE table.

Cause: An attempt was made to create a materialized view log on a MEMOPTIMIZE FOR WRITE table.

Cause: An attempt was made to build an index online with a MEMOPTIMIZE FOR WRITE table.

Cause: While waiting to lock a memoptimize flush object, a timeout occurred .

Cause: The DESC keyword was not specified in the ORDER BY clause within the APPROX_RANK function.

Cause: An invalid expression was used in the ORDER BY clause within the APPROX_RANK function.

Cause: Multiple expressions are used in ORDER BY clause within APPROX_RANK.

Cause: APPROX_RANK functions use different PARTITION BY keys.

Cause: The PARTITION BY key in the APPROX_RANK function was not a subset of the key in the GROUP BY clause.

Cause: The GROUP BY clause was missing when the approximate top functions were used.

Cause: The HAVING clause was missing when the approximate top functions were used.

Cause: An attempt was made to use window functions or aggregates that were not approximate top functions along with approximate top functions.

Cause: An attempt was made to involve more than one columns as the top N key.

Cause: One or more corresponding APPROX_RANK clauses were missing when approximate top functions were used.

Cause: the HAVING clause contained predicates other than AND when approximate top functions were used.

Cause: Illegal predicates were used in the HAVING clause when approximate top functions were used.

Cause: An attempt was made to use GROUPING SETS, CUBE or ROLLUP over the approximate functions.

Cause: An attempt was made to pass a negative value to the APPROX_SUM function.

Cause: An attempt was made to execute subqueries that contain approximate top functions without unnesting.

Cause: The Nest handle was not valid.

Cause: The Nest open failed.

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

Cause: The Nest lookup for a given pluggable database (PDB) failed.

Cause: An attempt to delete a Nest that had a dependent child Nest failed.

Cause: An attempt to delete a Nest that was not created failed.

Cause: An attempt was made to create a Nest that was already created.

Cause: The Nest creation failed with an operating system operation.

Cause: An attempt to open the Nest before it was created failed.

Cause: The Nest open failed with an operating system operation.

Cause: An attempt to update a Nest that was not opened failed.

Cause: The Nest update failed with an operating system operation.

Cause: An attempt to close a Nest that was not open failed.

Cause: The Nest close failed with an operating system operation.

Cause: The Nest delete failed with an operating system operation.

Cause: Nest connections require an enabled dedicated broker. The dedicated broker was not enabled in the current instance.

Cause: An invalid value or length for the Nest parameter was specified.

Cause: The child Nest could not be created due to reaching the maximum depth.

Cause: A pluggable database (PDB) nest was not found for the specified PDB.

Cause: The current pluggable database (PDB) connection was outside of the PDB nest.

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: Either the PARTITION BY or ORDER BY was specified on more than one argument of a POLYMORPHIC TABLE FUNCTION.

Cause: COLUMNS function was used outside a POLYMORPHIC TABLE FUNCTION.

Cause: POLYMORPHIC TABLE FUNCTION was specified inside RECURSIVE WITH clause.

Cause: Non-scalar data types were used in polymorphic table function. Only scalar data types are supported.

Cause: Data types for the source and target did not match for polymorphic table function. In Get_Col and Put_Col APIs, both the type of the collection element and the type of the polymorphic table function column must match.

Cause: The new column name already existed as a passthrough column in the polymorphic table function.

Cause: The column number specified in the Get_Col or Put_Col API for polymorphic table functions was incorrect.

Cause: This API was called in a context other than the execution time context of a polymorphic table function. This API is not supported in this context.

Cause: The type of this new column was not set.

Cause: This new column name was already created during the describe phase and therefore it is a duplicate column name.

Cause: This method of polymorphic table function had error(s) during SQL compilation.

Cause: A zero-length identifier was used as a new column name that was created during the describe phase.

Cause: An identifier with more than 128 bytes was used for one of the new column names that was created during the describe phase.

Cause: Either the PARTITION BY or the ORDER BY clause was specified on an argument of a non-table semantic POLYMORPHIC TABLE FUNCTION.

Cause: A polymorphic table function was specified as an argument of a table function.

Cause: The new column name was invalid. It should be valid Oracle identifier and should not be an Oracle reserved word.

Cause: The length specified for a new column for the polymorphic table function was greater than the maximum allowed length.

Cause: An object view was being created with polymorphic table function in the select query.

Cause: The new column name was created in describe only polymorphic table function.

Cause: A row replication API was called, but the Describe method set ROW_REPLICATION to FALSE (default).

Cause: An attempt was made to use more than one argument with TABLE or DBMS_TF.TABLE_T as the type specification.

Cause: When reading a column from database or writing a column to the database, destination buffer should not be smaller than the source.

Cause: When reading a column from the database or writing a column to the database, character set did not match.

Cause: A cursor expression was used as an argument to polymorphic table function.

Cause: An attempt was made to pass an invalid value to a bitmap operator.

Cause: An attempt was made to pass an invalid size value for a BITMAP_BUCKET_NUMBER or BITMAP_BIT_POSITION operator.

Cause: An attempt was made to construct a bitmap larger than its maximum SQL type size.

Cause: An attempt was made to pass a bitmap that was not produced by one of the BITMAP COUNT DISTINCT operators.

Cause: Cluster feature is not supported in Oracle Autonomous Database Cloud.

Cause: An attempt was made to create a table with ROWID column type. By default, Oracle Autonomous Database Cloud runs with ROW MOVEMENT enabled. Hence, ROWIDs stored in ROWID column may not be valid if rows are moved by automated maintenance operations, such as table shrink.

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: Oracle server failed to read or write to the specified file because the file has an SCN value which is too high for this release.

Cause: A fractured block or checksum error was detected on reading the control file under no-enqueue control file transaction. The reason could be a stalled concurrent block update.

Cause: An operating system error or network error occurred when making a remote call to another instance during a local temporary space DDL operation.

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: An attempt was made to create an XMLIndex on an XML CLOB column stored with object-relational storage.

Cause: An attempt was made to create an XMLIndex on a table that had an autolist partition.

Cause: There was an attempt to create an Unstructured XMLIndex (UXI) component on a table with interval partitioning.

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 LOB locator sent from client to server was invalid.

Cause: LOB signature cannot always be supported for clients earlier than Oracle Database 19c release. For example, this could happen when the buffer size allocated for the locator at client side is not big enough to hold the locator with signature.

Cause: The CLOB/BLOB/JSON type LOB locator was marked as value-based but was sent to the server for a write operation.

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: An operation could not obtain the compression analysis lock in a reasonable amount of time.

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: DISTRIBUTE BY PARTITION was specified for a table that is not partitioned.

Cause: DISTRIBUTE BY SUBPARTITION was specified for a table that is not composite.

Cause: DISTRIBUTE BY SUBPARTITION was specified for a table that is not partitioned.

Cause: An attempt was made to do FastStart administrative tasks while FastStart is in use.

Cause: An attempt was made to execute a FastStart related action when FastStart was not enabled.

Cause: FastStart is already enabled.

Cause: This tablespace is already assigned to FastStart or some FastStart internal objects already exists on this tablespace.

Cause: An attempt make changes to FastStart objects on a read-only database.

Cause: An attempt to make FastStart tablespace offline when the feature is enabled.

Cause: An attempt drop FastStart tablespace when the feature is enabled.

Cause: An attempt was made to enable or migrate FastStart to a non-automatic segment space management (ASSM) tablespace.

Cause: The given tablespace was locked by another operation.

Cause: An attempt was made to initiate a checkpoint when one was already started.

Cause: The previous FastStart administrative procedure was incomplete.

Cause: The version number of the FastStart catalog was invalid or too old.

Cause: An attempt was made to use FastStart in the case of a proxy pluggable database (PDB).

Cause: An attempt was made to modify inmemory_size parameter when database was not opened, was read-only, or was being migrated.

Cause: inmemory_size was less than the minimum expected by the system.

Cause: An attempt was made to migrate FastStart to a tablespace which did not have sufficient space.

Cause: An attempt was made to use FastStart along with the feature that is not supported.

Cause: An attempt was made to open an In-Memory Expressions capture window with another capture window already in the OPEN state.

Cause: An attempt was made to CLOSE an In-Memory Expressions capture window before opening it first.

Cause: An internal error was encountered in the In-Memory Expressions procedure.

Cause: Resize of In-Memory Xmem area was not supported on non multitenant container database (CDB) and root pluggable database (PDB).

Cause: The specified In-Memory area size was larger than the configured In-Memory XMem area size.

Cause: A nonzero value was specified for the INMEMORY_SIZE initialization parameter for a non-Oracle cloud.

Cause: Either the segment requested for In-Memeory did not exist, or a population or repopulation task was already in progress for this segment, or this segment was not In-Memory enabled.

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 the maximum size allowed. This size is 30 bytes for clients prior to Oracle Database 12c Release 2 (12.2) and 128 bytes otherwise.

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: A common user tried to register a schema with missing type name annotations. All type names from the schema and its dependencies should be annotated.

Cause: A common user tried to register a schema with missing default table name annotations. All table names from the schema and its dependencies should be annotated.

Cause: The tablespace name did not have a closing double quotation mark.

Cause: An attempt was made to move XDB to a system tablespace.

Cause: The new tablespace was smaller than the current tablespace.

Cause: The new tablespace was not Automatic Segment Space Management (ASSM).

Cause: An invalid resource handle or path name was passed.

Cause: The internal input table containing the schemas was empty.

Cause: The XML schema existed for the user.

Cause: The inherited type could not be migrated.

Cause: The XML schema could not be migrated.

Cause: The owner could not be migrated for the XML schema.

Cause: The XML schema could not be granted to public.

Cause: The level up the hierarchy was less than 1.

Cause: The resource type was not recognized.

Cause: maintainDOM was not set to TRUE.

Cause: XQuery data model is not allowed.

Cause: An attempt was made to use position predicate on an out-of-line table when maintainDOM was set to FALSE.

Cause: For security reasons, ftp and http access over XDB repository is not allowed on server side.

Cause: For security reasons, ftp and http access over XDB repository is not allowed on server side.

Cause: ORADB client access was a security issue.

Cause: The PL/SQL XML parser handle was invalid.

Cause: The PL/SQL XSL processor handle was invalid.

Cause: The PL/SQL XSL stylesheet handle was invalid.

Cause: The PL/SQL DOM handle was invalid.

Cause: The named PL/SQL DOM handle was invalid.

Cause: The named argument was either invalid or was specified as a NULL.

Cause: The PL/SQL procedure or function was not supported.

Cause: ACL path was not valid.

Cause: XSLT parameter was not valid.

Cause: The attributes referenced in schema definition differ from the attributes referenced by SQLType.

Cause: At least one attribute, from an existing type, was not referenced in the schema definition.

Cause: The specified type was not defined for the given schema component.

Cause: The storage type was not supported for the packed XML memory object. The expected type is either RAW or VARCHAR2.

Cause: There was an invalid use of the VIRTUAL COLUMNS. VIRTUAL COLUMNS clause is only available during XMLType table creation.

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

Cause: The specified RESTART was a duplicate.

Cause: The RESTART clause was specified in the CREATE SEQUENCE statement.

Cause: The NOEXTEND constraint was specified for the scalable sequence and the generated value was wider than the sequence maximum value.

Cause: There were Sharded Sequence objects in the database that were created in a release later than the selected release for downgrade.

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 string returned from SQL macro contained bind variables.

Cause: The string returned from the SQL macro was invalid.

Cause: A SQL macro expansion had a reference to an earlier SQL macro.

Cause: The scalar SQL macro was called in the FROM clause of a SQL query.

Cause: The table SQL macro was called from outside of a FROM clause of a SQL query.

Cause: An attempt to create a persistent memory region failed.

Cause: An attempt to delete a persistent memory region failed.

Cause: A process failed to attach to a persistent memory region.

Cause: A process failed to detach from a persistent memory region.

Cause: System did not have %llu bytes of available persistent memory.

Cause: The system-wide limit on number of open files has been reached.

Cause: An internal error occurred while doing an operation on persistent memory.

Cause: An attempt to query system state failed.

Cause: Tracing was enabled while doing an operation on XGA memory.

Cause: The Recovery Appliance was in the process of shutting down. This message is recorded in the incident log for the Recovery 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 128 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 Recovery 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 Recovery Appliance.

Cause: While creating a full database backup to tape or to a replicated recovery appliance, level 0 backups of one or more data files were missing.

Cause: One of the following operations was performed resulting in the database using more than its allotted disk space: - UPDATE_DB lowering the DISK_SPACE_RESERVE value. - UPDATE_PROTECTION_POLICY setting the guaranteed_copy parameter to YES - DELETE_SBT_LIBRARY where backup data for the given database existed. New backup requests may be stalled until the system can recompute the safety of allowing additional backup data or backup data may be lost.

Cause: The recovery window golad was not available for the current set of backups. The recovery window goal in the protection policy indicates a desire to be able to restore and recover to any point in time within that range. This is not possible given the current set of backups. Possible reasons are missing archive log backups, missing data file backups or lack of reserved disk space.

Cause: An UNPROTECTED_WINDOW parameter in protection policy has been specified and the Recovery Appliance has not received sufficient archive log backups or data file backups from the given target database for at least that period.

Cause: The specified Recovery Appliance scheduler process could not be stopped.

Cause: The current command failed because the database was in the process of being deleted.

Cause: The argument was expecting a non-null, valid value but the argument value passed in was null, invalid, or out of range.

Cause: The length of the name exceeded the limit.

Cause: The name incorrectly started with "_", "-", ":", "#" or digits or contained non-alphanumeric characters. Verify that all other double quotation marks, if any, in the string are adjacent pairs of double quotation marks. Double quotation marks must not be used in the middle of the name.

Cause: The name incorrectly started with "_", "-", ":", "#" or digits or contained non-alphanumeric characters. Verify that all other double quotation marks, if any, in the string are adjacent pairs of double quotation marks. Double quotation marks must not be used in the middle of the name.

Cause: The configuration of the Recovery Appliance was modified to enable the production of trace files. Trace files have the capacity to exhaust disk space on the Recovery Appliance.

Cause: The Recovery Appliance was unable to find a file that is required for its operation.

Cause: The Recovery Appliance was unable to complete the configuration and setup of replication for the database specified.

Cause: There was a failure while backing up redo or copying backups from a polling location. This condition may be due to one of the following reasons: * An individual backup piece exceeded the database protection policy DISK_RESERVE_SPACE value. * Guaranteed_copy is enabled but not enough data has been spooled to tape. * Misconfiguration of the storage location size.

Cause: An incorrect object type was given to an API command.

Cause: An attempt to execute 'update_db' or 'update_protection_policy' and change storage locations with a replication server or tape job associated with the protection policy failed.

Cause: An attempt was made to delete a database, but the Recovery Appliance has been deactivated by the administrator.

Cause: An attempt was made to restore the specified backup piece which resulted in an error. An explanation of the error appears in the following messages.

Cause: Additional extents could not be allocated for the tables used to to implement the delta store.

Cause: The Recovery Appliance ended its restrictions on task execution. The restricted resources state was entered when tasks could not run due to insufficient temporary table space or insufficient undo space. At that time, resource intensive tasks were put into RESOURCE_WAIT state.

Cause: The specified database had an INDEX_BACKUP task that could not be run because the task did not tile against the delta store. An incremental backup piece will not tile into the delta store when the full backup that it was built upon is not found in the delta store.

Cause: A disk group was supplied to either the create_storage_location or update_storage_location APIs that was not previously prepared by the installation software for the Recovery Appliance.

Cause: An attempt was made to create a snapshot while 'max_pdb_snapshots' was set to 0.

Cause: The polling feature did not work on multiple tenants.

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: The number of pluggable databases exceeded either the MAX_PDBS property value or the maximum 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 data file.

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

Cause: A GRANT statement was issued specifying CONTAINER=ALL and naming a local user or role as a grantee, which is illegal.

Cause: A REVOKE statement was issued specifying CONTAINER=ALL and naming a local user or role as a revokee, which is illegal.

Cause: A GRANT or REVOKE statement was issued specifying CONTAINER=ALL and listing a local role among the 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: An attempt was made to clone a pluggable database that did not have local undo enabled.

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 or application 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 a CDB$ROOT or an application 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 or an application 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 (PDB) in a mode incompatible with the multitenant container database (CDB) or, if the PDB belonged to an application container, in a mode incompatible with the application root.

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 or remove containers to or 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: The pluggable database has been dropped.

Cause: An attempt was made to plug in a database that had a SYSTEM tablespace whose relative file number was not one. The most common cause of this error is when the database has been created using Oracle Database release 7 or earlier and then upgraded using the migrate utility.

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 either been created and not opened or has not been opened in read/write mode after the undo mode has been changed for the multitenant container database (CDB).

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 was made to revoke a system privilege that was granted with a different scope.

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 consist only of ASCII characters, and must contain the prefix specified in common_user_prefix parameter.

Cause: DML into a data link table was attempted outside an application action.

Cause: DML into an extended data link table was attempted in an application root outside an application action.

Cause: An operation was attemped inside a pluggable database that required the container database (CDB) to be open.

Cause: The path prefix was missing or invalid. This can also happen if any of the following are true: - The directory path specified by PATH_PREFIX clause contains the string '..' or an invalid path separator like // or exceeds the maximum length supported on host operating system. - The target path already exists as a file in operating system. - The ROOT container (CDB$ROOT, when connected to a pluggable database or application root, when connected to an application container) has a PATH_PREFIX set and either NONE or a directory location outside ROOT containers' PATH_PREFIX was specified.

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 INSTANCES clause.

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 or a PDB 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 invoke DBMS_PDB.RECOVER() by either not specifying a data file or directory location, or by specifying a nonexistent data file or directory 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 consist only of ASCII characters, and must contain the prefix specified in common_user_prefix parameter.

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 or an application root. Except for DEFAULT and ORA_STIG_PROFILE, which are out-of-the-box Oracle supplied local profiles, no customer created local profiles are allowed in this container.

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 multiple pluggable databases at the same time.

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 or the application root.

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 password of the common user account has expired and needs to be changed. Connect to the CDB$ROOT or Application Root of the multitenant container database to change the password of the common user.

Cause: The system could not access a required archived redo log file.

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: 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, role or profile with the same name as an existing local user, role or profile.

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 files belonging to SYSTEM and SYSAUX tablespace were found. SYSTEM and SYSAUX tablespaces are critical to recover a pluggable database (PDB).

Cause: There were pending SQL statements involving this user, role or profile which need to be resolved in order for the pluggable database (PDB) to be synced with ROOT.

Cause: An attempt was made to invoke DBMS_PDB.RECOVER() by specifying data files or a directory name containing data files which are duplicate copies of the same file.

Cause: An attempt was made to relocate a pluggable database (PDB) which was opened with warnings or there were warnings encountered after relocating the PDB.

Cause: An attempt was made to clone a pluggable database (PDB) from PDB$SEED as the source PDB.

Cause: An operation (such as creation of an application seed) that can only be performed in an application root was attempted by a user not connected to an application root.

Cause: An operation (such as creation of an application root) that can only be performed in a multitenant container database (CDB) root container was attempted by a user not connected to the CDB root.

Cause: An attempt is made to issue ALTER DATABASE LOCAL UNDO [ON | OFF] when the database is not open in UPGRADE mode.

Cause: The user connected to an application root attempted to specify a pluggable database (PDB) that does not belong to the application container in a statement which can only affect PDBs belonging to the application container.

Cause: An operation (such as ALTER PLUGGABLE DATABASE VIEW LOCAL) that can only be performed in a View Pluggable Database was attempted by a user not connected to a View Pluggable Database.

Cause: An attempt to clone from a pluggable database (PDB) which had one one or more data files that are currently part of an online move or a hot backup operation.

Cause: An attempt was made to perform an operation which is not allowed when the pluggable database (PDB) is being cloned concurrently.

Cause: An attempt was made to perform an operation while a conflicting database wide operation or a read write pluggable database (PDB) clone is in progress.

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

Cause: A DML on CONTAINERS() included the CON_ID column but did not include a non-CON_ID column. A DML on CONTAINERS() including the CON_ID column can be performed only if a column other than the CON_ID column is also specified.

Cause: A DML on CONTAINERS() specified an invalid value for the CON_ID column.

Cause: An attempt was made to assign an invalid pluggable database pattern for this initialization parameter.

Cause: The specified STANDBYS clause was too long in CREATE PLUGGABLE DATABASE statement.

Cause: A valid lockdown profile name was not present where required.

Cause: An attempt was made to use an invalid value in the VALUE clause.

Cause: An attempt was made to use an invalid statement or option or feature in ENABLE or DISABLE clause.

Cause: An attempt was made to specify a lockdown profile that did not exist.

Cause: An attempt was make to create a lockdown profile with a name that already existed.

Cause: The specified value for UPGRADE PRIORITY was outside of the legal range.

Cause: An attempt was made to specify UPGRADE PRIORITY for CDB$ROOT or PDB$SEED, which is illegal.

Cause: An operation was attempted that can only be performed in an application root.

Cause: An attempt was made to 'purge' or 'begin' an application action (install, uninstall, upgrade, or patch) while another action was already in progress.

Cause: An attempt was made to end an application action (install, uninstall, upgrade, or patch) without a prior 'begin' call.

Cause: The starting version of the application upgrade did not match the current version of the application.

Cause: The minimum version for the application patch did not exist.

Cause: An action was attempted on an application that did not exist.

Cause: An attempt was made to start an application patch that was already installed.

Cause: An attempt was made to end an application patch that was not in progress.

Cause: An attempt was made to change the sharing status of an object that either did not exist, or was of a type that could not be made common.

Cause: An action was attempted on an application that already exists.

Cause: An attempt was made to enable a parameter only supported in a multitenant container database (CDB), and the current database is not a CDB.

Cause: The default tablespace specified in the CREATE PLUGGABLE DATABASE statement either did not exist in the source pluggable database (PDB) or is not included in the USER_TABLESPACES clause.

Cause: An attempt was made to execute a SQL statement, in a pluggable database (PDB), which was disabled according to the corresponding lock down profile.

Cause: An attempt was made to run 'apex_to_common.sql' or 'pdb_to_apppdb.sql' on a pluggable database (PDB) that is an unconverted non-multitenant container database.

Cause: An attempt was made to use an incompatible client version. Clients prior to Oracle Database 12c Release 2 (12.2) do not support long identifiers.

Cause: An attempt was made to provide an invalid file name which could not be opened for generating the unplug archive.

Cause: An attempt was made to use an invalid host name in the HOST clause.

Cause: An attempt was made to use an invalid application version.

Cause: An attempt was made to directly alter or drop an internal database link. An internal database link can be altered or dropped only through an ALTER or DROP PLUGGABLE DATABASE statement.

Cause: An attempt was made to create or access a proxy pluggable database that referenced a non-existent or closed pluggable database.

Cause: An attempt to support pluggable database (PDB) isolation mode in a database without per-PDB recovery domains failed. PDB isolation mode is supported only on a per-PDB domain enabled instance.

Cause: An attempt to support pluggable database (PDB) isolation mode in a global undo enabled pluggable database failed. PDB isolation mode is supported only on a local undo enabled CDB instance.

Cause: An attempt was made to enable DATA_LINK_DML on a non-data link table.

Cause: An attempt was made to create a common user, role or profile with the same name as an existing common user, role or profile.

Cause: An attempt was made to drop or rename a CON_ID column of a CONTAINER_DATA table which is illegal.

Cause: An attempt was made to change the data type of a CON_ID column of a CONTAINER_DATA table to a non-numeric data type, which is illegal.

Cause: An operation was attempted inside an application root that requires the application root to be open.

Cause: A valid service name was not present where required by the syntax of ALTER SESSION SET CONTAINER= SERVICE=.

Cause: An attempt was made to create a pluggable database (PDB) by cloning or plugging in an application PDB while connected to the root of a multitenant container database (CDB).

Cause: An attempt was made to issue a statement affecting a user, role, or object used by an application installed in an application container while not installing, upgrading, patching, or uninstalling such application.

Cause: An attempt was made to disable a CONTAINER_DATA attribute of a table for which it was not enabled.

Cause: An attempt was made to enable a CONTAINER_DATA attribute of a table for which it is already enabled.

Cause: An attempt was made to execute an unsupported statement after an application action (install, uninstall, upgrade, or patch) was started.

Cause: An attempt was made to operate on an application after it was uninstalled.

Cause: An attempt was made to use an invalid user name in the USER clause.

Cause: One or more tablespaces listed in the USER_TABLESPACES clause were not self-contained.

Cause: An attempt was made to alter a lockdown profile with an invalid clause.

Cause: An attempt was made to alter a lockdown profile with an invalid option.

Cause: An attempt was made to use a file name that does not start with CREATE_FILE_DEST for the pluggable database.

Cause: The ending version of the application upgrade matched a previous version of the application.

Cause: An attempt was made to connect or ALTER SESSION SET CONTAINER to an application root clone.

Cause: An attempt was made to access a proxy pluggable database as SYSDBA or SYSOPER.

Cause: An absolute path was used in the CREATE DIRECTORY statement. Since the PDB has set the PATH_PREFIX property, only relative path is allowed for directories.

Cause: An attempt was made to create a pluggable database where one or more tablespaces has an invalid tablespace number.

Cause: An attempt was made to create an application root clone for an application container that has already reached the maximum permitted number of application root clones.

Cause: An attempt was made to create a proxy pluggable database to a non-multitenant container database (non-CDB) instance.

Cause: An attempt was made to create a proxy pluggable database that references an application root clone.

Cause: An attempt was made to synchronize an application that has not ended its install, patch, upgrade, or uninstall.

Cause: An attempt was made to either create a refreshable clone of a proxy pluggable database or to create a proxy pluggable database which is also enabled for refresh.

Cause: An attempt was made to refresh a pluggable database (PDB) which was either not created as a refreshable PDB or the final refresh was already complete.

Cause: An attempt was made to dismount a pluggable database with parameter enable_pdb_isolation set to FALSE.

Cause: This is an internally stimulated error.

Cause: An attempt was made to dismount a pluggable database on a standby instance.

Cause: An attempt was made to drop or unplug the root of an application container to which one or more application pluggable databases (PDBs) belong.

Cause: An attempt was made to drop, unplug, or alter an application root clone pluggable database which is not allowed.

Cause: An attempt was made to reopen an application root in a mode incompatible with that of an application PDB belonging to the same application container.

Cause: An attempt was made to either relocate a pluggable database (PDB) which was created as a refreshable PDB or to create a refreshable PDB from a PDB that was already created as refreshable PDB or was marked for relocation.

Cause: An attempt was made to refresh a pluggable database (PDB) with no refresh mode.

Cause: An attempt was made to perform an operation that is not allowed in an application patch.

Cause: An attempt was made to alter an application that was created internally.

Cause: An operation was attempted that can only be performed in an application PDB.

Cause: An attempt was made to apply the specified changes to all containers.

Cause: An operation was attempted that can only be performed in an application action (install, uninstall, upgrade, or patch).

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

Cause: An attempt was made to add a rule that already exists in the lockdown profile.

Cause: An attempt was made to support pluggable database (PDB) isolation mode with the MEMORY_TARGET or MEMORY_MAX_TARGET configuration parameters. PDB isolation mode is not supported with the MEMORY_TARGET or MEMORY_MAX_TARGET configuration parameters.

Cause: An attempt was made to start a pluggable database (PDB) with a system global area (SGA) size larger than or equal to the multitenant container.

Cause: An attempt was made to start a pluggable database (PDB) with SGA_MAX_SIZE configuration parameter size larger than or equal to the multitenant container database (CDB).

Cause: An attempt was made to create a proxy pluggable database that referenced a proxy pluggable database.

Cause: An attempt was made to create a pluggable database (PDB) by cloning or plugging in an application PDB or application root having an application that does not exist in the application root where the statement was issued.

Cause: The instance recovery could not proceed as the pluggable database (PDB) was in the middle of the SHUTDOWN ABORT operation.

Cause: An attempt was made to perform an operation on a pluggable database that did not belong to the current multitenant container database (CDB) in the CDB fleet.

Cause: An attempt was made to create a pluggable database (PDB) by cloning or plugging in an application PDB or application root having an application that has a higher version than the application root where the statement was issued.

Cause: An attempt was made to create a pluggable database (PDB) by cloning or plugging in an application PDB or application root having an application that has a mismatch status between application PDB and the application root where the statement was issued.

Cause: An attempt was made to change the sharing status of an object to extended data link when the object was of a type for which extended data links are not supported.

Cause: An attempt was made to set a common application context using a local package.

Cause: An attempt to create a pluggable database (PDB) archive file failed because a file with that name already exists.

Cause: An attempt was made to relocate the root of an application container.

Cause: An attempt was made to alter an application when the application pluggable database was not open.

Cause: An attempt was made to assign an invalid container map object to container_map property of the database.

Cause: An attempt was made to assign an invalid common data map object to common_data_map property of the database.

Cause: An attempt was made to create a common object to be owned by an implicit user.

Cause: An attempt was made to plug in or clone from a pluggable database with a higher compatible parameter value than the compatible parameter value of the multitenant container database (CDB).

Cause: An attempt was made to end an application action using a service name or module name that does not match the service name or module name that was in use when the application action was started.

Cause: An attempt was made to create a proxy pluggable database with relocate clause specified.

Cause: An operation was attempted that can only be performed outside an application action (install, uninstall, upgrade, or patch).

Cause: An attempt was made to create an application pluggable database (PDB) in an application root which was created by plugging in a non-multitenant container database (non-CDB) without first running noncdb_to_pdb.sql script.

Cause: A GRANT or REVOKE statement was issued specifying more than one grantee on an application pluggable database (PDB).

Cause: An attempt was made to set the 'common_user_prefix' parameter in a pluggable database (PDB) that conflicts with the value of the same parameter in the multitenant container database (CDB.)

Cause: An attempt was made to run an AUTHID CURRENT_USER function or procedure, or to reference a BEQUEATH CURRENT_USER view, that is not safe under the COMMON_SCHEMA_ACCESS lockdown.

Cause: An attempt was made to modify a common object that was created by another application.

Cause: The password of the application common user had expired and needed to be changed in order to successfully log in to application containers. But the application ROOT container's application status did not allow this operation to succeed either because: - An implicit application common user was attempting to change the password from within an explicit application action. - A non-implicit application common user was attempting to change the password from within an implicit application action.

Cause: An attempt was made to synchronize an application containing statements executed from a privileged session.

Cause: An attempt was made to create a pluggable database (PDB) using an archive file using the NOCOPY clause.

Cause: An attempt was made to use a file name that did not start with PATH_PREFIX for the pluggable database.

Cause: An attempt was made to use an invalid file name as an argument.

Cause: An attempt was made to modify a user or a role that was created by another application. This can also happen when connected to an Application container and DBMS_PDB.SET_USER_EXPLICIT or DBMS_PDB.SET_ROLE_EXPLICIT procedure was invoked with the following type of users and roles: - Pluggable Database (PDB) Administrative user, that is, a user who has been granted PDB_DBA role inside the PDB. - The out-of-box Oracle supplied common users or roles. - Container Database (CDB) Common Users and roles, that is, users and roles created at CDB$ROOT container.

Cause: An attempt was made to query the cross-container fixed tables.

Cause: A DML on CONTAINERS() included the CON_ID predicate in an OR chain or in an in-list.

Cause: A DML on CONTAINERS() included multiple CON_ID predicates, or the single CON_ID predicate specified a value that is not a constant or a bind.

Cause: A DML on CONTAINERS() attempted to set a value for the CON_ID column.

Cause: An attempt was made to use an invalid application patch.

Cause: An attempt was made to create or set an object table or an object view as a data link or an extended data link.

Cause: An invalid value is specified in an ALTER PLUGGABLE DATABASE CONTAINERS DEFAULT TARGET or ALTER DATABASE CONTAINERS DEFAULT TARGET statement.

Cause: An attempt was made to perform DML on CONTAINERS() outside the multitenant container database (CDB) root or an application root.

Cause: An attempt was made to query an object table or object view using CONTAINERS().

Cause: An attempt was made to modify the sharing property of an object outside an application action.

Cause: An attempt was made to end an application action in a manner that is inconsistent with the order in which sessions will be replayed during application SYNC.

Cause: An attempt was made to run 'pdb_to_apppdb.sql' on a pluggable database (PDB) that was not an unconverted application PDB.

Cause: An attempt was made to synchronize an application in an unconverted application PDB before running 'pdb_to_apppdb.sql'.

Cause: DDL on a data link table was attempted outside an application action.

Cause: DDL on an extended data link table was attempted in an application root outside an application action.

Cause: An attempt was made to purge an application that was installed in one or more application pluggable databases (PDBs).

Cause: An attempt was made to either set the MAX_PDBS database property to an invalid number or the number of current pluggable databases (PDBs) exceeds the number specified.

Cause: An attempt was made to end an application action using an incorrect application name.

Cause: An attempt was made to end an application action using an incorrect application patch number.

Cause: An attempt was made to modify a profile that was created by another application. This can also happen when connected to an Application container and DBMS_PDB.SET_PROFILE_EXPLICIT procedure was invoked and input profile type was either of the following: - The out-of-the-box Oracle supplied local profiles (DEFAULT and ORA_STIG_PROFILE). - Container Database (CDB) Common Profiles, that is, profiles created at CDB$ROOT Container.

Cause: An attempt was made to relocate a pluggable database using a database link to the source pluggable database.

Cause: An unsupported operation was performed on the source pluggable database, which rendered the target PDB invalid.

Cause: An attempt was made to set the compatibility version of an application to a version higher than that of one of the PDBs.

Cause: An attempt was made to open a refreshable pluggable database in read/write mode.

Cause: The source pluggable database had an active transaction when it was closed.

Cause: An attempt was made to unplug a pluggable database that was previously unplugged.

Cause: An attempt was made to uninstall or purge an application that had objects, users, roles, and profiles.

Cause: The foreign archive log required for refreshing the pluggable database was not found.

Cause: An attempt was made to plug in a pluggable database (PDB) that has a lower version and has more components than the multitenant container database (CDB) or the application root.

Cause: There were proxy pluggable databases or application containers in the database.

Cause: An attempt was made to relocate a pluggable database with availability max clause using a target pluggable database name which is different from source pluggable database name.

Cause: An attempt was made to relocate a pluggable database with availability max and service_name_convert clauses together.

Cause: An attempt was made to run 'approot_to_pdb.sql' on a pluggable database (PDB) that was already converted to a regular PDB.

Cause: An attempt was made to access an invalid partition using the CONTAINERS() clause.

Cause: An ancillary operator was used with a data link, extended data link, or CONTAINERS() clause.

Cause: An attempt was made to plug in a pluggable database (PDB) using an XML file that does not contain the SYSTEM, SYSAUX or undo tablespace specifications.

Cause: The multitenant container database (CDB) did not have sufficient system global area (SGA) memory available to open the pluggable database (PDB). *Result: Increase the CDB SGA size or dismount a PDB to free CDB SGA memory.

Cause: An attempt was made to specify an incorrect value for lead_cdb_uri. The lead_cdb_uri value can either specify the host name, port number and service name for the lead multitenant container database (CDB), or the value can specify a database link object name in the current CDB which connects to the lead CDB in the fleet.

Cause: An attempt was made to specify the lead_cdb_uri property in the multitenant container database (CDB) where the lead_cdb property is set to TRUE or vice versa.

Cause: The PDB specified was not a template pluggable database (PDB) and thus pdb_template cannot be set to this PDB.

Cause: An attempt was made to clone a pluggable database that was opened in read/write mode.

Cause: An attempt was made to switchover a pluggable database (PDB) using a database link that pointed to the source pluggable database.

Cause: An attempt was made to switchover to a pluggable database (PDB) which was not marked as a refresh copy.

Cause: An attempt was made to switchover to a pluggable database (PDB) which was not marked as a refresh copy of the source pluggable database (PDB).

Cause: An attempt was made to snapshot a pluggable database (PDB) which was created with snapshots disabled.

Cause: An attempt was made to create a pluggable database (PDB) using a snapshot or to drop a snapshot that could not be found.

Cause: An attempt was made to create a pluggable database (PDB) using a snapshot when Oracle Managed Files (OMF) was not enabled or if the CREATE_FILE_DEST clause was not specified.

Cause: An attempt was made to create a snapshot of a pluggable database (PDB) using a name that already existed.

Cause: An attempt was made to switch over a pluggable database (PDB) that was not a normal pluggable database that could be opened in read/write mode.

Cause: Recovery was required prior to opening the pluggable database, but an error during recovery was determined to be fatal enough to end both the recovery and the open operation.

Cause: An attempt was made to generate logical partitioning key values using a container map object that had multiple values for each partition.

Cause: An attempt was made to specify an illegal initialization parameter in a lockdown profile.

Cause: An attempt was made to modify an illegal initialization parameter inside a template pluggable database (PDB).

Cause: An attempt was made to set the PDB_LOCKDOWN initialization parameter along with the PDB_TEMPLATE initialization parameter.

Cause: The specified operation was not allowed in a template pluggable database (PDB).

Cause: An attempt was made to set the PDB_LOCKDOWN initialization parameter to an application lockdown profile when the PDB_LOCKDOWN initialization parameter was already set to a container database (CDB) lockdown profile.

Cause: An attempt was made to set the PDB_TEMPLATE initialization parameter to an application template when the PDB_TEMPLATE initialization parameter was already set to a multitenant container database (CDB) template.

Cause: A conflicting operation was in progress in the source pluggable database (PDB) for the refresh clone.

Cause: An attempt was made to modify an in-memory value for the SGA_TARGET parameter with pluggable database isolation mode enabled.

Cause: An invalid clause was used in an ALTER SYSTEM operation.

Cause: An attempt was made to unplug an application pluggable database (PDB), which had unfinished application action.

Cause: An attempt was made to materialize a pluggable database (PDB) that was not created as a snapshot copy.

Cause: An attempt was made to rename an application root that has one or more open application PDBs.

Cause: The template pluggable database (PDB) to which the current PDB was subscribed was not open.

Cause: An attempt was made to set the MAX_PDB_SNAPSHOTS property to a higher value than the allowed maximum.

Cause: The issued operation had a missing property name or the property specified was invalid or not found in the database.

Cause: The issued operation had a missing property value or the property value specified was invalid.

Cause: An attempt was made to specify a property that could not be altered using ALTER DATABASE PROPERTY or ALTER PLUGGABLE DATABASE PROPERTY statement.

Cause: An attempt was made to create a pluggable database using an XML file that was generate with DBMS_PDB.RECOVER and all tablespaces were not included.

Cause: An attempt was made to use PARTITION_CONTAINED clause outside subset cloning.

Cause: An attempt was made to create a refreshable clone of a pluggable database (PDB) or relocate a PDB from a standby database.

Cause: An attempt was made to use SET_SHARING_NONE, SET_METADATA_LINKED, SET_DATA_LINKED, or SET_EXT_DATA_LINKED on an object of an incompatible sharing mode.

Cause: An attempt was made to insert or update a row in a container map enabled table that violated the partitions of the container map.

Cause: An attempt was made to access an object column in a fleet proxy Pluggable Database (PDB).

Cause: One or more pluggable databases could not be recovered by the RESETLOGS operation because the Oracle Active Data Guard standby database was still open.

Cause: The LIBRARY objects did not use a DIRECTORY object for the pluggable database (PDB) with a defined PATH_PREFIX.

Cause: An attempt was made to add a referential integrity constraint from a table to a data-linked or an extended data-linked table.

Cause: An attempt was made to alter a linked tablespace to READ WRITE status.

Cause: An attempt was made to open a pluggable database with files in object store in read/write mode.

Cause: An attempt was made to change passward in an upgrade or uninstall block.

Cause: An attempt was made to create or alter an object table, an external table, a hybrid partitioned table, or an object view with a CONTAINER_DATA clause.

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 | ALTER] [TABLE | SNAPSHOT | MATERIALIZED VIEW]

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

Cause: The CLUSTERING clause conflicted with other clauses on the table. The CUSTERING clause cannot be used with IOT, CLUSTERED, GLOBAL TEMPORARY TABLE, or the EXTERNAL TABLE clause.

Cause: The CLUSTERING clause was not followed by the BY [LINEAR | INTERLEAVED] ORDER option.

Cause: The 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 or more than 4 groups were specified in the BY INTERLEAVED ORDER subclause. You can have at most 40 columns and at most 4 groups in the INTERLEAVED ORDER subclause.

Cause: A non-scalar column was specified in the BY [LINEAR | INTERLEAVED] 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 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 clause 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 join column(s).

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 a system-generated or unused column in a join condition in the CLUSTERING clause.

Cause: An attempt was made to create a pluggable database with temporary tablespace files in the object store.

Cause: An attempt was made to clone a source pluggable database (PDB) stored in an object store using a database link.

Cause: An attempt was made to unplug a pluggable database (PDB) stored in an object store using an invalid credential.

Cause: An attempt was made to unplug a pluggable database (PDB) to object store without a credential.

Cause: An internal error occurred when reading or writing to XML file in object store.

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 or non-inheritable PDB parameter.

Cause: An internal error was encountered while trying to update dependent parameter value.

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: Lost write was already in the requested state. If enable or disable lost write was specified, then lost write was already in the enabled or disabled state.

Cause: LOST WRITE PROTECTION could not be enabled for lost write tablespaces or temporary tablespaces.

Cause: An invalid option was specified while altering a LOST WRITE PROTECTION tablespace.

Cause: An invalid option was specified while creating or altering a flashback tablespace.

Cause: Enabling lost write protection could not succeed because the lost write tablespaces did not exist or had insufficient space. It is possible that shadow lost write was not enabled for the database.

Cause: There was an internal error code.

Cause: The object that was manipulated could not be set to the requested state.

Cause: A lost write was found in a data block protected by lost write.

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

Cause: An invalid option was specified while creating LOST WRITE PROTECTION tablespace.

Cause: In CREATE TABLESPACE, the LOST WRITE PROTECTION option was specified more than once.

Cause: An invalid option was specified while creating a tablespace.

Cause: The BIGFILE keyword was not specified while creating a LOST WRITE PROTECTION tablespace.

Cause: An attempt was made to assign a LOST WRITE PROTECTION tablespace to be a user's default tablespace.

Cause: An attempt was made to create user objects in a LOST WRITE PROTECTION tablespace. Other system objects such as rollback segments are also illegal.

Cause: An attempt was made to assign a LOST WRITE PROTECTION tablespace to be a default tablespace.

Cause: A different block size was specified when a SHADOW LOST WRITE tablespace was created.

Cause: An attempt was made to enable SHADOW LOST WRITE on a standby database.

Cause: An attempt was made to enable lost write when the database was not open or an access error occurred when attempting to access the new_lost_write_shadows$ dictionary table

Cause: Invalid parameters were specified for a LOST WRITE PROTECTION tablespace. Only BIGFILE TABLESPACE, SIZE and BLOCKSIZE for a LOST WRITE PROTECTION tablespace can be specified upon creation. ALTER cannot be used to make a LOST WRITE PROTECTION tablespace read-only.

Cause: The lost write tablespace does not exist.

Cause: An internal error occurred.

Cause: An attempt was made to shrink a lost write tablespace.

Cause: There was an internal error in lost write subsystem. The SYSAUX tablespace may be inaccessible or full.

Cause: There was an internal error in lost write subsystem.

Cause: One of the lost write tracking tables was inconsistent. A parallel operation may have caused this problem.

Cause: An internal error occurred when performing drop side effects

Cause: The attempted lost write operation is prohibited on a read-only database.

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: An attempt was made to send or receive a temporary LOB locator over a database link.

Cause: An attempt was made to send or receive a temporary LOB locator from an index-organized table over a database link.

Cause: An attempt was made to pass a remote LOB locator as a parameter to a LOB operation which does not accept a remote LOB locator.

Cause: An attempt was made to pass LOB locators belonging to different databases as parameters to the same LOB operation.

Cause: An attempt was made to select from a remote database, a LOB locator which was obtained by the remote from another remote database.

Cause: An attempt was made to send or receive an invalid LOB locator over a database link.

Cause: An attempt was made to perform an operation INSERT AS SELECT on a view with INSTEAD OF trigger on it and a remote LOB column in the select list.

Cause: An attempt was made to send or receive a LOB locator over a database link to a pre-12.2 database.

Cause: This is likely the result of passing a local LOB locator as a bind value to a SQL statement that is executed on a remote database over a database link. For example, running the statement "INSERT INTO tabl1@@dblink VALUES (:1)" where the bind value is a local persistent LOB locator and parallel execution is enabled on the remote side.

Cause: When the pluggable database was closed, any temporary LOBs in it were freed. An attempt was made to access a freed LOB.

Cause: The LOB locator operands that were passed to the SQL operator did not have the value-based property set uniformly.

Cause: An invalid value was specified for LOB ENABLE STORAGE IN ROW. The specified value for LOB ENABLE STORAGE IN ROW should be null, 4000, 8000, 16000 or 32000 for SECUREFILE LOBS in heap tables, and null in all other cases.

Cause: The attempted operation resulted in the number of index levels exceeding the maximum allowed.

Cause: An attempt was made to alter or drop an automatically created index.

Cause: Oracle Database clients earlier than release 12.1 could not handle error codes larger than 65535.