Cause: An invalid or unknown NLS configuration parameter was specified.

Cause: The character set specified when creating the database is unknown.

Cause: An unknown parameter name or invalid value is specified in a NLS parameter string.

Cause: The requested conversion between two character sets in the CONVERT function is not implemented

Cause: One of the following: - The string operands(other than an nlsparams argument) to an operator or built-in function do not have the same character set. - An nlsparams operand is not in the database character set. - String data with character set other than the database character set is passed to a built-in function not expecting it. - The second argument to CHR() or CSCONVERT() is not CHAR_CS or NCHAR_CS. - A string expression in the VALUES clause of an INSERT statement, or the SET clause of an UPDATE statement, does not have the same character set as the column into which the value would be inserted. - A value provided in a DEFAULT clause when creating a table does not have the same character set as declared for the column. - An argument to a PL/SQL function does not conform to the character set requirements of the corresponding parameter.

Cause: Either an attempt was made to issue an ALTER SESSION command with an invalid NLS parameter or value; or the environment variable(s) NLS_LANG, ORA_NLSxx, or ORACLE_HOME was incorrectly specified, therefore the NLS data files cannot be located.

Cause: It is not allowed to create a database on a native ASCII-based machine using an EBCDIC-based character set, and vice versa.

Cause: Internal error

Cause: Internal error

Cause: Internal error

Cause: The character set specified when creating the control file is unknown.

Cause: It is not allowed to create a control file on a native ASCII-based machine using an EBCDIC-based character set, and vice versa.

Cause: When you ALTER DATABASE ... CHARACTER SET, the new character set must be a superset of the old character set. For example, WE8ISO8859P1 is not a superset of the WE8DEC.

Cause: When character set conversion happened between CHAR and NCHAR either implicitly or explicitly, some characters were lost due to no mapping characters in the destination character set.

Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set

Cause: The character set specified is not allowed for this operation or is invalid

Cause: CLOB data changes representation to Unicode when converting to a multibyte character set and must be migrated

Cause: NCLOB, NCHAR or NVARCHAR2 data changed the representation to Unicode when converting to a multibyte character set and must be migrated.

Cause: This command can only be run when connecting as SYS

Cause: This command can only be run when the database is in RESTRICTED mode

Cause: This command can only be run when the database is in EXCLUSIVE mode

Cause: This command can only be run when there are no other sessions active

Cause: A regular expression internal error occurred.

Cause: The regular expression was too complex and could not be parsed.

Cause: The regular expression contained an incorrect sequence of metacharacters.

Cause: The regular expression did not have balanced parentheses.

Cause: The regular expression did not have balanced brackets.

Cause: A back references was found before a sub-expression.

Cause: An invalid range was found in the regular expression.

Cause: An unknown character class was found in the regular expression.

Cause: An unknown equivalence class was found in the regular expression.

Cause: An unknown collation class was found in the regular expression.

Cause: An invalid interval value was found in the regular expression.

Cause: The operation failed because the regular expression it used exceeds the maximum supported size.

Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set. Instant Client Light has only minimal character sets.

Cause: The character set specified is not allowed for this operation or is invalid. Instant Client Light has only minimal character sets.

Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set. Instant Client Light has only minimal character sets.

Cause: The character set specified is not allowed for this operation or is invalid. Instant Client Light has only minimal character sets.

Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set. Instant Client has only minimal character sets.

Cause: The character set specified is not allowed for this operation or is invalid. Express Instant Client has only minimal character sets.

Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set. Instant Client has only minimal character sets.

Cause: The character set specified is not allowed for this operation or is invalid. Express Instant Client has only minimal character sets.

Cause: The character argument of a collation-sensitive operator was too long or it had too many decomposable characters to create a collation key for it in the available buffer space.

Cause: This is an internal error in a globalization support function.

Cause: An attempt was made to create or alter a database using a client-only or conversion-only character set.

Cause: The name of the collation that you specified was not recognized by the Oracle Database, because the name was misspelled, or the collation was user-defined but not installed in the Oracle Home of the database instance, or because the directory specified in the ORA_NLS10 environment setting, either explicitly or defaulting to $ORACLE_HOME/nls/data (%ORACLE_HOME%\nls\data on Microsoft Windows), did not contain valid NLS data files.

Cause: The ID of the collation that you specified was not recognized by the Oracle Database, because it was incorrect, or the collation was user-defined but not installed in the Oracle Home of the database instance, or because the directory specified in the ORA_NLS10 environment setting, either explicitly or defaulting to $ORACLE_HOME/nls/data(%ORACLE_HOME%\nls\data on Microsoft Windows), did not contain valid NLS data files.

Cause: An unexpected error was encountered by an instance-critical process.

Cause: The user ID that is the owner of the Oracle home directory was not the same as the effective user ID of the local client that connected to the Oracle instance.

Cause: The instance received a request to create a session. The request specified a service not currently associated with the instance. If an existing connection to the instance used this service, the service may have relocated to a different instance or may no longer exist.

Cause: An attempt to enter the sandbox for a multitenant container database (CDB) failed.

Cause: An attempt to enter the sandbox for a pluggable database (PDB) failed.

Cause: An attempt to exit the sandbox for a pluggable database (PDB) failed.

Cause: The error recorded before this error should not be cleared and should be re-signaled to the top-level error handler.

Cause: The path recorded in the SGA did not match the current value.

Cause: The Oracle Scheduler group private handle was not valid.

Cause: load on system is too high to perform parallel queries.

Cause: A parallel query server reached an exception condition.

Cause: A parallel query server lost contact with the foreground (coordinator) process/thread.

Cause: A parallel query server lost contact with another server.

Cause: Cannot find process information for a parallel query server thread.

Cause: A parallel query server died unexpectedly, PMON cleaning up the process.

Cause: Internal error.

Cause: Internal error.

Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER SYSTEM command to a value larger than the number of available instances.

Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER SYSTEM command while the database was mounted in exclusive mode.

Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter to a value higher than the maximum allowed by the system.

Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter to a value higher than PARALLEL_MAX_SERVERS.

Cause: PARALLEL was specified more than once, NOPARALLEL was specified more than once, or both PARALLEL and NOPARALLEL were specified in a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement, or in a RECOVER command.

Cause: PARALLEL 0 or DEGREE 0 was specified in a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement.

Cause: CACHE was specified more than once, NOCACHE was specified more than once, or both CACHE and NOCACHE were specified in a CREATE TABLE or CLUSTER, or in an ALTER TABLE or CLUSTER statement.

Cause: PARALLEL parameter specifying number of instances must be a positive integer or DEFAULT

Cause: A parallel query option feature has been invoked but this option has not been enabled.

Cause: an unrecognized option was used within a PARALLEL clause.

Cause: PARALLEL clause cannot be empty.

Cause: invalid value for DEGREE was specified within a PARALLEL clause.

Cause: invalid value for INSTANCES was specified within a PARALLEL clause.

Cause: DEGREE or INSTANCES was specified more than once within a PARALLEL clause.

Cause: the PARALLEL keyword was used alone or DEGREE DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE RECOVER command.

Cause: INSTANCES DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE RECOVER command

Cause: the DEGREE option was omitted from an ALTER DATABASE RECOVER command.

Cause: parallel query server was hung and subsequently killed.

Cause: PARALLEL_MIN_PERCENT parameter was specified and fewer than the minimum number of slaves were acquired

Cause: PDML transaction cannot be started because we are not in the coordinator site of the distributed transaction.

Cause: parallel statement failed because all itls in the current block are occupied by siblings of the same transaction.

Cause: After executing a parallel INSERT/UPDATE/DELETE statement, a command other than COMMIT or ROLLBACK was issued.

Cause: After executing an INSERT statement with an APPEND hint, a command other than COMMIT or ROLLBACK was issued.

Cause: After executing a query on a global v$ fixed view, one or more instances failed to allocate a slave to process query

Cause: The coordinator's instance must be a member of the parallel_instance_group in which this operation will be run.

Cause: The instance group name is too long.

Cause: There must be at least one instance in the GLOBAL_VIEW_ADMIN_GROUP in order to execute a query on global views

Cause: Within the same transaction, an attempt was made to add read or modification statements on a table after it had been modified in parallel or with direct load. This is not permitted.

Cause: Within the same transaction, an attempt was made to perform parallel modification operations on a table after it had been modified. This is not permitted.

Cause: Within a transaction, an attempt was made to perform distributed access after a PDML or insert direct statement had been issued.

Cause: Transaction in progress

Cause: The cursor was invalidated during the parse phase of deferred parallel processing, e.g. when set operands are parallelized.

Cause: The coodinator crashed or released the lock on the partition which the slave is trying to aquire currently.

Cause: OS or interconnect problem receiving interinstance message

Cause: When executing a query on a gv$ fixed view, one or more instances failed to allocate a slave to process query.

Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter to a value less than PARALLEL_MIN_SERVERS.

Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter to a value higher than PROCESSES minus the number of reserved processes.

Cause: Insufficient SGA memory for PX buffers

Cause: The parallel query statement produced a temporary LOB.

Cause: A loopback was created in the transaction before this operation.

Cause: A table or index in a parallel query is referenced via a loopback connection.

Cause: First hard parse on slave given QC-supplied environment and parameters gave different plan from QC. Try again with outline.

Cause: The parallel execution monitor process died.

Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter to 0 in the multitenant container database (CDB) system.

Cause: The 'setsparseparent' command specified a source file that was not sparse.

Cause: The 'setsparseparent' command specified a destination that was not backed by a sparse disk group.

Cause: The 'setsparseparent' command specified a child file that was not sparse.

Cause: The 'setsparseparent' command was not successful.

Cause: The parent information was not copied to the destination file.

Cause: An attempt was made to insert or update a column with a value which is too wide for the width of the destination column. The name of the column is given, along with the actual width of the value, and the maximum allowed width of the column. Note that widths are reported in characters if character length semantics are in effect for the column, otherwise widths are reported in bytes.

Cause: a locally managed database must have a temporary tablespace other than SYSTEM tablespace

Cause: in a locally managed database, default temporary tablespace must be TEMPORARY type

Cause: in a dictionary managed database, default temporary tablespace must be SYSTEM or TEMPORARY type

Cause: attempt to assign a temporary tablespace to be a user's default tablespace

Cause: attempt to assign a permanent tablespace to be a user's temporary tablespace

Cause: attempt to assign a dictionary managed tablespace to be a user's temporary tablespace

Cause: Attemp to create dictionary managed tablespace in database which has system tablespace as locally managed

Cause: Attemp to migrate locally managed tablespace to dictionary managed type when the database has locally managed system tablespace.

Cause: Attemp to alter dictionary managed tablespace to read write in database which has system tablespace as locally managed. This tablespace can only be dropped.

Cause: An attempt was made to shrink a permanent tablespace or a dictionary managed tablespace.

Cause: The tablespace is either dropped, temporary or undo

Cause: An attemp was made to drop the default permanent tablespace

Cause: ALTER DATABASE FORCE LOGGING command failed because the database is already in force logging mode.

Cause: ALTER DATABASE NO FORCE LOGGING command failed because the database is not in force logging mode.

Cause: There is a concurrent ALTER DATABASE FORCE LOGGING or ALTER DATABASE NO FORCE LOGGING command running in the system.

Cause: An attempt to alter the specified tablespace temporary failed because the tablespace is in force logging mode.

Cause: An attempt to alter the specified tablespace into force logging mode failed because it is already in force logging mode.

Cause: An attempt to alter the specified tablespace out of force logging mode failed because it is not in force logging mode.

Cause: In CREATE TABLESPACE, the FORCE LOGGING option was specified more than once.

Cause: In CREATE TABLESPACE, the RETENTION option was specified more than once.

Cause: In CREATE TABLESPACE, the ENCRYPTION option was specified more than once.

Cause: FORCE LOGGING or SET STANDBY NOLOGGING options were specified more than once.

Cause: A request from a remote database in the same Oracle Data Guard configuration to send data blocks to avoid or replace soft corrupt blocks due to nonlogged operations failed. This error is accompanied by additional errors that indicate the reason for the failure.

Cause: A request from a remote database in the same Oracle Data Guard configuration to send data blocks to avoid or replace soft corrupt blocks due to nonlogged operations could not connect to the requesting database. This error is accompanied by additional errors that indicate the reason for the failure.

Cause: The process performing replacement of nonlogged blocks failed to replace one or more blocks of the file indicated due to unexpected reasons such as a write failure reported by the operating system.

Cause: The process performing replacement of nonlogged blocks received an error when attempting to connect (CONNECT) or make a fetch request (REQUEST) against the database identified by the given service. The database was expected to act as a source of replacement blocks.

Cause: The process performing replacement of nonlogged blocks waited too long for a request sent to the remote database for a range of blocks to be completed.

Cause: A database received data blocks requested by a recovery session that has now terminated. This error signals to the sending database that no more transfer requests should be made for the same RCVID.

Cause: A request to use space in the data transfer cache was rejected because there was no free space left in the cache and space could not be freed up.

Cause: A request to perform Nonlogged Block Replacement (NBR) recovery could not identify any other database in the Data Guard environment from which to request replacement blocks.

Cause: DBVerify ran out of text buffer. The error was trapped internally by the system. DBVerify would return the result in text buffer and then resume checking.

Cause: DBVerify encountered run-time error. The error signal was trapped internally by the system.

Cause: A request to send data blocks to a recovery process failed because the source of the blocks is not on the same database incarnation as the site where the recovery is being performed.

Cause: SYSTEM tablespace was specified as the default permanent during database creation.

Cause: It is incorrect to alter the default permanent tablespace of a database to temporary type

Cause: The 12 GB space limit of Oracle Database Express Edition was reached.

Cause: An attempt was made to open the database on a read-only instance under the following two cases: 1) User explicitly specified read/write option in the SQL command. 2) User forgot to explicitly specify read-only in which case, read/write mode was assumed by default.

Cause: An attempt was made to create a database on a read-only instance.

Cause: A read-only instance was the first instance to try to open a database.

Cause: The last read/write instance holding the database open closed it.

Cause: An attempt was made to mount an enabled redo thread obtained as a user specified parameter.

Cause: There were no available disabled redo threads which could be used to mount on the current read-only instance.

Cause: An attempt was made to mount a standby database on a read-only instance.

Cause: The system parameter for ping with no log force feature was set to true.

Cause: An attempt was made to execute a disallowed ALTER DATABASE statement on a read-only instance.

Cause: An attempt was made to close a pluggable database (PDB) on the last read/write instance while a read-only instance was holding it open.

Cause: An attempt was made to recover an online pluggable database (PDB) on an Active Data Guard (ADG).

Cause: An attempt was made to recover a pluggable database (PDB) on an Active Data Guard (ADG) before the PDB creation was complete on the ADG, or while PDB side recovery was being canceled.

Cause: An attempt was made to recover a pluggable database (PDB) which is being recovered.

Cause: An attempt was made to cancel the recovery of a pluggable database (PDB) on an Active Data Guard (ADG) which did not have any recovery session in progress. There is nothing to cancel.

Cause: An attempt was made to start an Active Data Guard (ADG) recovery while PDB recovery session in progress.

Cause: A pluggable database name is incorrectly specified. There are two cases that this may occur: - Multiple pluggable database names were specified. - None or wrong pluggable database name was specified.

Cause: An attempt was made to specify checkpoint option with SET UNUSED.

Cause: An attempt was made to drop a column from an object type table.

Cause: An attempt was made to drop a column from a nested table.

Cause: An attempt was made to drop all columns in a table.

Cause: An attempt was made to drop a column used as the partitioning key.

Cause: An attempt was made to drop column from a partition/subpartition on a read only tablespace.

Cause: An attempt was made to access a table with columns in partially dropped state (i.e., drop column operation was interrupted).

Cause: An attempt was made to combine drop column with other ALTER TABLE operations.

Cause: An attempt was made to drop a column from a system table.

Cause: An invalid checkpoint interval specified in statement. Checkpoint interval must be between 0 and (2^31-1).

Cause: Duplicate option specified in statement.

Cause: An attempt was made to drop a column referenced by some constraints.

Cause: An attempt was made to drop a parent key column.

Cause: An attempt was made to drop a column from a partition/subpartition on an offline tablespace.

Cause: An attempt was made to repeat the drop column option in a single statement.

Cause: An attempt was made to submit DROP COLUMNS CONTINUE statement while there are no partially dropped columns.

Cause: An attempt was made to drop a virtual column generated by the system.

Cause: An attempt was made to drop a primary key column from an index- organized table.

Cause: An attempt was made to DROP or SET UNUSED a column that has already been 'set unused'.

Cause: The specified dimension was either smaller than 1 or greater than the number of dimensions encoded in the HHCODE.

Cause: The number of dimensions in two HHCODEs involved in a binary HHCODE operation did not match.

Cause: The specified level is either smaller than 1 or greater than the maximum level encoded in an HHCODE.

Cause: The specified range for a dimension was invalid.

Cause: The buffer size for a function is not valid.

Cause: An error occurred in a recursively called HHCODE function.

Cause: The cell identifier was either less than 0 or greater than (2^ndim - 1).

Cause: A character that is not in the range [0-9] or [A-F a-f] was detected.

Cause: Part of specified date format is invalid.

Cause: The specified date string had a bad component or did not match the specified format string.

Cause: An invalid number of arguments was specified for an SDO function.

Cause: A specified dimension value was outside the range defined for that dimension.

Cause: An invalid window type was specified.

Cause: A topology was specified that was not INTERIOR or BOUNDARY.

Cause: A topology identifier outside the range of 1 to 8 was specified.

Cause: The number of values used to define the window does not correspond to the window type.

Cause: The specified topology did not exist in the database, or some components of the topology were missing from the database.

Cause: The shape of a 2-D line partition could not be determined.

Cause: The specified distance type is invalid.

Cause: Vertex coordinates lie outside the valid range for specified dimension.

Cause: A vertex coordinate has a NULL value.

Cause: The coordinates defining a geometric element are not connected.

Cause: The coordinates defining a polygonal geometric element represent crossing segments.

Cause: An interior element of a geometric object interacts with the exterior element of that object.

Cause: The coordinates defining a polygonal geometric element represent less than three segments.

Cause: The coordinates defining a polygonal geometric element represent an open polygon.

Cause: The SDO_ETYPE column in the layer_SDOGEOM table contains an invalid geometric element type value.

Cause: There was a problem reading the dimension definition from the layer_SDODIM table.

Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object.

Cause: There is an invalid SDO_SRID in the SDO_GEOMETRY object. The specified SRID may be outside the valid SRID range.

Cause: There is a mismatch between the dimension in the SDO_GTYPE and dimension in the SDO_GEOM_METADATA for the SDO_GEOMETRY object.

Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object where the VARRAYs are NULL but the SDO_GTYPE is not of type POINT.

Cause: There are invalid SDO_POINT_TYPE or SDO_ELEM_INFO_ARRAY or SDO_ORDINATE_ARRAY fields in the SDO_GEOMETRY object.

Cause: There is invalid data in the SDO_ELEM_INFO_ARRAY field of the SDO_GEOMETRY object. The triplets in this field do not make up a valid geometry.

Cause: There is invalid data in the SDO_ORDINATE_ARRAY field of the SDO_GEOMETRY object. The coordinates in this field do not make up a valid geometry. There may be NULL values for X or Y or both.

Cause: There is invalid data in the SDO_ELEM_INFO_ARRAY field of the SDO_GEOMETRY object. There are arcs in a geometry that has geodetic coordinates.

Cause: The specified geometry function was not supported for point data.

Cause: A spatial operation was invoked with two geometries where one geometry had an SRID and the other geometry did not have an SRID.

Cause: Another error will accompany this message that will indicate the problem.

Cause: This is an internal error.

Cause: The spatial relationship between a generated tile and the specified element could not be determined.

Cause: An invalid combination of SDO_LEVEL and SDO_NUMTILES values was read from the layer_SDOLAYER table. The most likely cause is that the columns are NULL.

Cause: An error was encountered reading the layer metadata from the layer_SDOLAYER table.

Cause: The tile size specified for fixed size tessellation is smaller than the tolerance as specified in the layer metadata.

Cause: An invalid number of arguments were specified for an SDO_GEOM function.

Cause: An SDO_GEOM function was unable to determine the number of ordinates for the SDO layer layer.

Cause: This is an internal error.

Cause: An SDO_GEOM function was unable to determine the tolerance value for the SDO layer layer.

Cause: This is an internal error.

Cause: This is an internal error.

Cause: The geometry type for a specific instance in a layer_SDOGEOM table is not among the set of geometry types supported by Oracle Spatial.

Cause: The maximum number of geometric elements that can be specified in the argument list for an SDO_GEOM function was exceeded.

Cause: This is an internal error.

Cause: The requested object is not present in the specified table.

Cause: The operation required a valid SRID but none was specified.

Cause: The specified SRID is not known.

Cause: The SRID for the operation could not be determined.

Cause: An invalid "WRK_TBLSPC" parameter value was specified.

Cause: The specified topology name was not unique in the database.

Cause: The specified topology did not exist in the database.

Cause: The specified topology ID in the feature table did not match the topology ID stored in the topology metadata.

Cause: The topology relationship information table (xxx_RELATION$) did not have the matching partition corresponding to the feature table.

Cause: The topology_id and tg_layer_id values stored in the feature table did not match the values stored in the topology relationship information table (xxx_RELATION$).

Cause: A call was made to delete a feature layer which has a dependent layer defined on it.

Cause: The SDO_TOPO_GEOMETRY object had the wrong geometry and/or element type.

Cause: Both SDO_TOPO_GEOMETRY parameters did not come from the same topology.

Cause: An SDO_TOPO_GEOMETRY constructor was invoked with incorrect parameters for table name and/or column name.

Cause: An incorrect degree value <=1 was passed for a Non-Uniform Rational B-Spline curve.

Cause: An incorrect number of control points was passed for a Non-Uniform Rational B-Spline curve.

Cause: An incorrect number of control points and degree was passed for a Non-Uniform Rational B-Spline curve.

Cause: An incorrect number of knot values was passed for a Non-Uniform Rational B-Spline curve.

Cause: An incorrect value was passed for the weight of a control point of a Non-Uniform Rational B-Spline curve.

Cause: An incorrect knot value was passed for a Non-Uniform Rational B-Spline curve.

Cause: An incorrect knot value sequence was passed for a Non-Uniform Rational B-Spline curve.

Cause: An incorrect knot value sequence was passed for a Non-Uniform Rational B-Spline curve.

Cause: The end point of a subelement for a compound curve was not equal to the start point of the next subelement, or the start point of a subelement was not equal to the end point of the previous subelement and one of the subelements was a NURBS curve.

Cause: An attempt was made to commit changes to a spatial table in a distributed transaction, but spatial indexes are not supported in distributed transactions.

Cause: The specified schema name was invalid.

Cause: The specified spatial index name was invalid.

Cause: The specified index table name was invalid.

Cause: The specified index partition name was invalid.

Cause: The specified index parameter or parameter combination was invalid.

Cause: An attempt was made to create the spatial index on an index- organized table (IOT).

Cause: The specified column name was invalid.

Cause: An attempt was made to use optimized geodetic minimum bounding rectangles (MBR).

Cause: The number of table columns specified for the PointInPolygon() function was incorrect.

Cause: It has been detected that 1 or more rows have been pre-fetched from the specified query cursor.

Cause: The specified tolerance value was invalid.

Cause: The specified geometry is not two-dimensional.

Cause: The operation is not valid using geodetic MBRs.

Cause: The operation failed.

Cause: The polygon ring size exceeded half the area of the earth.

Cause: The specified query cursor was invalid.

Cause: The specified element number is incorrect.

Cause: The specified geometry type is incorrect.

Cause: The specified element type is incorrect.

Cause: There are more elements than were specified.

Cause: The geometry ring topology (inner or outer) is wrong.

Cause: The feature does not exist.

Cause: An incorrect ptn_type parameter was specified.

Cause: An incorrect ptn_capacity parameter was specified.

Cause: An incorrect numdim parameter was specified.

Cause: Null values cannot be specified in the supplied input data.

Cause: One or more parameters for the Partition_Table() function are invalid.

Cause: The specified MASK parameter was invalid.

Cause: This operation cannot be executed for Non-Uniform Rational B-Spline curves.

Cause: The specified spatial table did not exist.

Cause: The specified spatial table is registered in the Spatial data dictionary.

Cause: The drop_topology procedure was invoked for a topology that has assocated topo_geometry layers with it.

Cause: It was not possible to add the specified TOPO_GEOMETRY layer to the topology.

Cause: It was not possible to delete the specified topo_geometry layer from the topology.

Cause: An invalid layer_id was passed to the SDO_TOPO_GEOMETRY constructor.

Cause: The NODE$ table for the topology did not exist in the database.

Cause: The EDGE$ table for the topology did not exist in the database.

Cause: The FACE$ table for the topology did not exist in the database.

Cause: The RELATION$ table for the topology did not exist in the database.

Cause: A topology node operation was invoked with an invalid node_id.

Cause: A topology edge operation was invoked with an invalid edge_id.

Cause: A topology face operation was invoked with an invalid face_id.

Cause: The tg_type in SDO_TOPO_GEOMETRY constructor did not match the type specified for the layer.

Cause: The SDO_TOPO_GEOMETRY object passed into the function/operator was not valid.

Cause: The create_topo operation requires a unique TOPOLOGY name, that already does not exist in the database.

Cause: This is an internal error.

Cause: A partition key is already set for the spatial table.

Cause: This is an internal error.

Cause: This is an internal error.

Cause: This is an internal error.

Cause: The specified spatial column does not exist.

Cause: This is an internal error.

Cause: This is an internal error.

Cause: This is an internal error.

Cause: This is an internal error.

Cause: This is an internal error.

Cause: The specified target type is not valid.

Cause: The RANGE window specified is not correctly defined.

Cause: The PROXIMITY window specified is not correctly defined.

Cause: The POLYGON window specified is not correctly defined.

Cause: This is an internal error.

Cause: This is an internal error.

Cause: The partition name substitution variable %s was not found in the SQL filter.

Cause: This is an internal error.

Cause: This is an internal error.

Cause: This is an internal error.

Cause: Operation failed to insert a record into the exception table.

Cause: Operation failed to remove a record from the exception table.

Cause: Specified HHCODE type is not valid.

Cause: The high water mark was not greater than or equal to zero.

Cause: The precision specified is out of range.

Cause: The number of dimensions specified is out of range.

Cause: The specified table contained rows.

Cause: The specified Oracle error was encountered.

Cause: The specified object does not exist.

Cause: The specified table already exists.

Cause: The length of the SDO_CODE column in the layer_SDOINDEX table could not be determined.

Cause: The specified element could not be read from the layer_SDOGEOM table.

Cause: The geometry type in the layer_SDOGEOM table is unsupported.

Cause: Initialization of the tessellation package failed.

Cause: This is an internal error.

Cause: This is an internal error.

Cause: This is an internal error.

Cause: This is an internal error.

Cause: This is an internal error.

Cause: This is an internal error.

Cause: This is an internal error.

Cause: This is an internal error.

Cause: There was insufficient memory to read the geometry from the database.

Cause: This is an internal error.

Cause: This is an internal error.

Cause: The system was unable to compute the minimum bounding HHCODE or supercell for the geometry.

Cause: Tessellation did not generate any tiles for this element. This error could be caused if the geometry definition puts the geometry outside the domain defined in the layer_SDODIM table.

Cause: Internal error in some Oracle Spatial stored procedure.

Cause: This is an internal error.

Cause: This is an internal error.

Cause: An error was encountered while trying to parse the parameters clause for the spatial CREATE INDEX statement.

Cause: An error was encountered while trying to create the SDO_INDEX_METADATA table or insert data into it.

Cause: An error encountered while trying to read the USER_SDO_GEOM_METADATA view.

Cause: An error was encountered while trying to create the index table.

Cause: An internal error was encountered while parsing the spatial parameters.

Cause: An internal error was encountered while creating the spatial index.

Cause: An error was encountered while evaluating the specified operator.

Cause: An internal error was encountered.

Cause: An internal error was encountered while trying to read the SDO_INDEX_METADATA table.

Cause: An error was encountered while trying to insert data into the index table. Likely causes are: - Insufficient quota in the current tablespace - User does not appropriate privileges

Cause: An internal error was encountered while trying to tessellate the window object.

Cause: The spatial relationship between a generated tile and the specified window object could not be determined.

Cause: Another error, indicating the real cause of the problem, should accompany this error.

Cause: The system was unable to compute the minimum bounding tile or supercell for the geometry.

Cause: Tessellation did not generate any tiles for this geometry. This error could be caused if the geometry definition puts the geometry outside the domain defined in the USER_SDO_GEOM_METADATA view.

Cause: Another error will accompany this message that will indicate the problem.

Cause: An error was encountered while trying to parse the parameters clause for the spatial ALTER INDEX statement.

Cause: An add_index parameter was passed to ALTER INDEX when the number of existing index tables is already at maximum.

Cause: An error was encountered while trying to create the index table.

Cause: The spatial relationship between a generated tile and the specified geometry could not be determined.

Cause: The SDO_GTYPE attribute in the geometry object contains an invalid value

Cause: The system was unable to compute the minimum bounding tile or supercell for a geometry in the specified table.

Cause: There are duplicate entries for the given table and column value pair in the USER_SDO_GEOM_METADATA view.

Cause: A tolerance of zero or NULL was supplied for a layer in the USER_SDO_GEOM_METADATA view.

Cause: An index table name is specified which is longer than the supported length of the spatial index table name.

Cause: The geometry table does not have a spatial index.

Cause: The SDO_LEVEL values for the two index tables used in the spatial join operator do not match.

Cause: An attempt was made to create a spatial index on a column of type other than SDO_GEOMETRY.

Cause: The specified temporary table either already exists or there is not enough tablespace.

Cause: The specified index table either already exists or there is not enough tablespace.

Cause: This feature assumes a minimum of 64K memory for bulk creation.

Cause: The specified sequence number exists.

Cause: The index table is either deleted or corrupted.

Cause: An internal error occurred in R-tree processing.

Cause: An inconsistency is encountered during concurrent updates, possibly due to the use of serializable isolation level.

Cause: The spatial transaction journal cache was enabled. When enabled, spatial functions that require use of the spatial index could not be used when uncommitted transaction data existed.

Cause: An error occurred in reading the dimensionality parameter

Cause: An error occurred because of too few values in the query minimum bounding rectangle (MBR).

Cause: An error occurred because the dimensionality specified in the CREATE INDEX statement does not match that of the data.

Cause: Currently, an R-tree index with three or more index dimensions can be used only with the SDO_FILTER operator.

Cause: An internal error was encountered in the extensible spatial index component. The text of the message is obtained from some other server component.

Cause: The user requesting the operation does not have the appropriate privileges on the referenced tables.

Cause: The specified entry already exists in the metadata table.

Cause: Data migration source table layer_SDOGEOM does not exist.

Cause: The specified geometry table does not exist in the current schema.

Cause: The specified table does not have a column of type SDO_GEOMETRY.

Cause: The column intended for storing the geometry is not of type SDO_GEOMETRY.

Cause: The specified table does not contain a GID column.

Cause: GID column is not of type NUMBER.

Cause: An OCI error occurred, or the user has insufficient quota in the active tablespace, or the rollback segments are too small.

Cause: There was an error reading the geometry data from the layer_SDOGEOM table.

Cause: There is no entry in the USER_SDO_GEOM_METADATA view for the specified geometry table.

Cause: An internal error occurred.

Cause: An OCI error occurred while processing the layer or geometry tables.

Cause: Insufficient memory.

Cause: The specified object failed the geometric integrity checks performed by the validation function.

Cause: The layer_SDODIM table does not exist.

Cause: A spatial operator was invoked with a window geometry with an SRID but the layer has no SRID; or the window has no SRID but the layer has an SRID.

Cause: An attempt was made to create a spatial index on a column that was not of type SDO_GEOMETRY.

Cause: OCI internal error.

Cause: OCI internal error.

Cause: OCI internal error, or SRID does not match a table entry.

Cause: Parsing error on source or destination coordinate system WKT, or incompatible coordinate systems.

Cause: OCI internal error.

Cause: OCI internal error.

Cause: A coordinate pair was out of valid range for a conversion/projection.

Cause: A geometry with a gtype of <= 0 was specified for transformation. Only a gtype >= 1 is allowed.

Cause: An internal error occurred while transforming points.

Cause: An Oracle Spatial function was called with an unknown UNIT value.

Cause: Cannot convert the specified unit from/to standard unit for linear distance, angle, or area.

Cause: When a SDO_BUFFER or SDO_AGGR_BUFFER function is called on a geodetic geometry, or SDO_ARC_DENSIFY is called, ARC_TOLERANCE must be specified, and it should not be less than the tolerance specified for the geometry.

Cause: An Oracle Spatial function with a UNIT parameter was called on a geometry without a georeferenced SRID.

Cause: An attempt was made to transform a 3-point representation of a circular arc without distortion.

Cause: An Oracle Spatial function was called with two geometries that have different SRIDs.

Cause: Wrong numbers in WKT for Earth radius or flattening for the current SRID.

Cause: Low-level coordinate transformation error trap.

Cause: OCI internal error.

Cause: OCI internal error.

Cause: The MASK passed to the RELATE function is not valid.

Cause: The given LRS segment was not a valid line string.

Cause: The specified LRS point was not a point geometry with measure information.

Cause: The given measure for linear referencing was out of range.

Cause: The specified geometric segments are not connected.

Cause: The measure information of a geometric segment was not assigned (IS NULL).

Cause: There is no room for the measure dimension in the given diminfo, or the specified standard geometry is not a point a line string.

Cause: Referencing system (LRS) concatenation involving LRS polygons is not supported.

Cause: Reversing a referencing system (LRS) polygon or collection geometry produced an invalid geometry.

Cause: Clipping (dynseg) a polygon across multiple rings is not allowed.

Cause: A geometry, specified as being a point, has more than one coordinate in its definition.

Cause: A geometry, specified as being a line, has fewer than two coordinates in its definition.

Cause: A geometry, specified as being an arc, has fewer than three coordinates in its definition.

Cause: A geometry, specified as being a polygon, has fewer than four coordinates in its definition.

Cause: A geometry, specified as being an arcpolygon, has fewer than five coordinates in its definition.

Cause: A geometry, specified as being a compound polygon, has fewer than five coordinates in its definition.

Cause: Invalid definition of an arc. An arc is defined using three non-collinear coordinates.

Cause: Two or more of the three points defining an arc are the same.

Cause: The boundary of a polygon does not close.

Cause: The boundary of a polygon intersects itself.

Cause: The inner or outer rings of a complex polygon touch.

Cause: The inner or outer rings of a complex polygon overlap.

Cause: The set of coordinates used to describe a circle are incorrect.

Cause: The ELEM_INFO_ARRAY in an SDO_GEOMETRY definition has more or fewer elements than expected.

Cause: The offset field in ELEM_INFO_ARRAY of an SDO_GEOMETRY definition references an invalid array subscript in SDO_ORDINATE_ARRAY.

Cause: The number of elements in SDO_ORDINATE_ARRAY is not a multiple of the number of dimensions supplied by the user.

Cause: There are repeated points in the sequence of coordinates.

Cause: Extent type should be represented by two points: lower left and upper right.

Cause: Circle type should be represented by three distinct points on the circumference.

Cause: The two points representing the extent are identical.

Cause: This subtype is not allowed within the ETYPE specified.

Cause: The compound type declare more sub-elements than actually defined.

Cause: Compound polygon must describe an enclosed area.

Cause: None of the ETYPEs within the geometry is supported.

Cause: The spatial layer had a geometry with a different dimensions than the dimensions specified for the layer.

Cause: The spatial layer had a geometry with a different SRID than the SRID specified for the layer.

Cause: In an Oracle Spatial geometry, interior and exterior rings were not used consistently.

Cause: In an Oracle Spatial geometry, the exterior and/or interior rings are not oriented correctly.

Cause: In a polygon geometry there is more than one exterior ring.

Cause: A 4-digit etype for a non-polygon type element is used, or the orientation is not a valid orientation for interior/exterior rings of the polygon.

Cause: Only non-geodetic 3D line string geometries (made of line segments) are supported for 3D LRS functions.

Cause: LRS measure dimension has to be after spatial dimensions. The position has to be either 3rd or 4th in the dim_info_array.

Cause: Modifying the metadata after the index is created will cause an inconsistency between the geometry's gtype and diminfo.

Cause: A geodetic line segment was not less than half of a great circle.

Cause: The SDO_MBR functionality is not supported for geodetic data.

Cause: The layer has a type that is different or inconsistent with the type of the current geometry.

Cause: An invalid type name is specified for the layer_gtype constraint.

Cause: An element of the geometry had orientation specified while some other element had no orientation specified (4-digit etype).

Cause: An invalid (or out of bounds) index was specified for extracting an element from a geometry.

Cause: An invalid (or out of bounds) index was specified for extracting a sub-element from a geometry.

Cause: The specified network was not found in the network metadata.

Cause: The specified table was not found in the network metadata.

Cause: The specified geometry metadata was not found in the spatial network metadata.

Cause: There was an inconsistency between the network metadata and the node/link information.

Cause: The network table(s) did not have required column(s)

Cause: There was an internal error in network manager.

Cause: The index-level changes were not fully incorporated as part of the commit or rollback operation.

Cause: The specified value for sdo_batch_size was too high or too low.

Cause: The dst_spec parameter was specified in the wrong format.

Cause: There was an internal error in computing the buffers or intersections in the specified spatial analysis function.

Cause: There was an internal error in the specified analysis function.

Cause: An attempt was made to violate GeoRaster management restrictions.

Cause: There was an error on status report related operation.

Cause: The operation failed because the input parameter was null or invalid.

Cause: The two input GeoRaster objects had different dimension sizes.

Cause: The expression parameter was not a valid math expression.

Cause: The condition parameter was not a valid boolean expression.

Cause: The current operation caused a duplicate RASTER_DATA_TABLE and RASTER_ID combination to be inserted into the USER_SDO_GEOR_SYSDATA view.

Cause: The RASTER_DATA_TABLE and RASTER_ID columns contained the same information in two or more rows in the USER_SDO_GEOR_SYSDATA view.

Cause: The specified rasterType was null or not supported.

Cause: The raster data table name specified for a GeoRaster object was not unique among raster data table names in the database; or for a GeoRaster object, which was not empty and was not blank, or was used as an output GeoRaster object, one or more of the following requirements were not met. The raster data table must: - Exist. - Be visible in the current schema. - Be defined in the same schema as the GeoRaster data table. - Be an object table of SDO_RASTER type or a relational table with the same columns as the attributes of the SDO_RASTER type.

Cause: The ultCoordinate array parameter had the wrong length or contained an invalid value.

Cause: The dimensionSize array parameter was NULL, had the wrong length, or contained an invalid value.

Cause: The GeoRaster object for output was NULL or invalid.

Cause: The storage parameter contained an invalid specification.

Cause: The blockSize storage parameter had the wrong length or contained an invalid value.

Cause: The specified pyramidLevel parameter was NULL or invalid.

Cause: The layerNumbers or bandNumbers parameter was invalid.

Cause: The intersection of cropArea and source GeoRaster object was NULL.

Cause: The scale parameter contained an invalid specification.

Cause: The resampling parameter was NULL or invalid.

Cause: The pyramid parameter was invalid.

Cause: The point position specified by the <ptGeom, layerNumber> or <rowNumber, colNumber, bandNumber> parameter combination was invalid or out of scope.

Cause: The geometry parameter did not specify a valid single-point geometry.

Cause: The layerNumber parameter was null or out of scope.

Cause: A parameter for set metadata operations was null or invalid.

Cause: An attempt to perform a mosaic or append operation failed.

Cause: The input geometry was not in the GeoRaster cell space, which had a NULL SRID value.

Cause: The cell value was NULL or out-of-scope.

Cause: The model coordinate array parameter had the wrong length or had NULL ordinate element(s).

Cause: The cell coordinate array parameter had the wrong length or had NULL ordinate element(s).

Cause: The GeoRaster object was not spatially referenced.

Cause: The background filling value parameter was invalid either because the array had the wrong size or because some of the element values were invalid.

Cause: The specified window parameter was invalid.

Cause: The bitmap mask was not a valid 1-bit GeoRaster object, or it had the wrong dimension sizes.

Cause: The program [or user] specified a modelCoordinateLocation that is not supported, or the modelCoordinateLocation of the GeoRaster object was wrong.

Cause: An attempt to perform a georeference operation failed. Possible reasons include xCoefficients or yCoefficients having the wrong number of coefficients or invalid coefficients.

Cause: The metadata or rasterType of the GeoRaster object was null.

Cause: The rasterType in the metadata of the GeoRaster object was inconsistent with the GeoRaster rasterType attribute.

Cause: The blankCellValue element could not be found in the metadata of a blank GeoRaster object, or the specified blankCellValue element value was NULL or invalid.

Cause: At least one of the defaultRed, defaultGreen, and defaultBlue values (logical layer numbers) was zero, negative, or out of range.

Cause: The cellRepresentation type was not supported.

Cause: The specification of dimensions or totalDimensions was inconsistent with rasterType, or vice versa.

Cause: Either the dimensionSize for each dimension was not specified, or an extraneous dimensionSize was specified.

Cause: Either the wrong block number(s) or block size(s) along dimensions were specified, or the block numbers and sizes when taken together were not consistent.

Cause: The specified pyramid type was not supported.

Cause: The specified maxLevel exceeded the maximum level allowed by the specified pyramid type.

Cause: The specified compression type was not supported.

Cause: The specified error related to the polynomialModel element in the spatial reference system (SRS) metadata.

Cause: There was no SYSDATA entry for the specified GeoRaster object.

Cause: There were NULL or invalid component values in the specified metadata.

Cause: The two GeoRaster objects whose layers are to be combined together either had different row or column dimension sizes, or their georeferencing information did not match.

Cause: There was an invalid NODATA value or value range in the metadata, or the specified NODATA value or value range was invalid.

Cause: The GeoRaster Temporal Reference System was not supported.

Cause: The GeoRaster Band Reference System was not supported.

Cause: The GeoRaster spectral extent specification was incorrect.

Cause: The GeoRaster rasterInfo ULTCoordinate was not correct.

Cause: The GeoRaster had more than one layerInfo element, or the layerDimension value was not supported.

Cause: The scaling function had a zero denominator.

Cause: The bin function data did not match its type.

Cause: Too many subLayers were defined for the GeoRaster object, or layerNumber or layerDimensionOrdinate was not assigned correctly.

Cause: The GeoRaster metadata was invalid against its XML Schema.

Cause: The beginDateTime value was later than the endDateTime value.

Cause: There was an error in the original GeoRaster cell data or in the cell data of the pyramids.

Cause: There was an error in the cell data of an original bitmap mask or in the cell data of the pyramids of a bitmap mask.

Cause: The polynomial model did not match the requirements of a rectified GeoRaster object.

Cause: The polynomial model was not an six-parameter transformation, or the six-parameter transformation was not valid.

Cause: The referenced GeoRaster object had a zero model space SRID or the specified model space SRID was zero.

Cause: The interleaving type of the GeoRaster object was not supported.

Cause: The specified blocking configuration was invalid.

Cause: An internal error occurred while retrieving GeoRaster data from the database.

Cause: An internal error occurred while loading GeoRaster data into the database.

Cause: The specified table or column did not exist, or the column was not a GeoRaster column.

Cause: The operation failed because the GeoRaster object had an inappropriate type or format for the specified compression method. The GeoRaster type or format is not supported for the specified compression.

Cause: The GeoRaster metadata specification is not supported.

Cause: Invalid blockMBR geometries were stored in the raster data table.

Cause: The data of the source GeoRaster object could not be used to update that of the target GeoRaster object.

Cause: The number of specified target layers or bands and source layers or bands did not match.

Cause: The owner of the specified raster data table could not be determined.

Cause: The geometry parameter did not specify a valid geometry.

Cause: The rasterSpec parameter contained an invalid specification.

Cause: The rasterDataTable name was not a valid nonquoted identifier, it contained a period separator, or not all of the alphanumeric characters were uppercase.

Cause: The output GeoRaster object had the same RASTER_DATA_TABLE and RASTER_ID combination as that of an input GeoRaster object.

Cause: The point position specified by the point geometry parameter or the rowNumber/colNumber parameter combination was null or out of scope.

Cause: The specified functional fitting method was not supported, the number of GCPs was insufficient, some GCPs were invalid, or the distribution of the GCPs led to no solution or an unstable solution.

Cause: The target SRID was not different from the source GeoRaster object's SRID.

Cause: Reprojection from source to destination projection produced a large distortion.

Cause: The specified source type was not supported.

Cause: The specified destination type was not supported.

Cause: No GeoRaster object has been initialized for the specified image.

Cause: There was insufficient memory to hold the specified GeoRaster data for this operation.

Cause: The file format or compression type was not supported.

Cause: The operation could not be completed because an error occurred during compression or decompression. Check the error message for details.

Cause: The GeoTIFF metadata of the specified input image contained invalid or insufficient information to georeference the GeoRaster object.

Cause: No SRID was found in the Oracle Spatial CS_SRS table to match the source coordinate system metadata.

Cause: An attempt to perform a transformation operation failed.

Cause: There was an error in the GeoRaster operation, parameters, or compression types.

Cause: The specified option is not installed or enabled.

Cause: This is an internal GeoRaster error.

Cause: An error related to an external plugin was encountered in the GeoRaster component.

Cause: This is an internal Oracle Spatial error.

Cause: The CREATE DATABASE command contains more than one SYSAUX DATAFILE clause.

Cause: Tried to drop SYSAUX tablespace

Cause: An attempt to rename the SYSAUX tablespace failed.

Cause: An attempt to create the SYSAUX tablespace with invalid attributes.

Cause: If Create Database has the datafile clause, then SYSAUX datafile clause has to be specified, unless using OMF.

Cause: Attempting to set the SYSAUX tablespace to read only. The SYSAUX tablespace must remain read write for database operation.

Cause: An attempt was made to perform operation with an invalid Start/End Snapshot Pair.

Cause: An update error occurred during OCI operation due to an underlying error.

Cause: The user has specified a RETENTION setting that is not in the supported range of (MIN, MAX).

Cause: The user has specified a INTERVAL setting that is not in the supported range of (MIN, MAX).

Cause: The metric capture cannot be executed because it is too close to the last capture (within 1 centi-second).

Cause: Error occurred during OCI operation due to underlying error.

Cause: The operation failed because AWR is not available. The possible causes are: AWR schema not yet created; AWR not enabled; AWR schema not initialized; or database not open or is running in READONLY or STANDBY mode.

Cause: The operation failed because the specified baseline ID does not exist in the Workload Repository.

Cause: The operation failed because the specified database ID does not exist in the Workload Repository.

Cause: The operation failed because the specified database ID already exists in the Workload Repository.

Cause: The operation failed because the specified database ID was not registered in the Workload Repository properly.

Cause: The operation failed because the local database ID cannot be unregistered from the Workload Repository.

Cause: Out of memory to allocate the space for the return variable for an external procedure.

Cause: A read error occurred during the OCI operation to retrieve the baseline information

Cause: Error occurred during OCI operation due to underlying error.

Cause: The operation failed because the specified baseline name does not exist in the Workload Repository.

Cause: The operation failed because the specified baseline name is invalid.

Cause: The operation failed because the specified baseline name already exists in the Workload Repository.

Cause: An error occurred during the flushing of a table group. Because of the error in the group, we are unable to flush this table.

Cause: The user has specified a TOPNSQL setting that is not in the supported range of (MIN, MAX).

Cause: A SQL was purged from AWR before the operation completed.

Cause: The operation failed because the specified SQL ID already existed in the repository.

Cause: The operation failed because the specified SQL ID was invalid.

Cause: The operation failed because the maximum allowed colored SQL was exceeded.

Cause: The operation failed because the specified baseline template name already existed in the Workload Repository.

Cause: The operation failed because the specified baseline template name did not exist in the Workload Repository.

Cause: Invalid input was specified for the create baseline template routine.

Cause: An invalid value was specified for the expiration of a baseline. The expiration is specified in number of days, and the expiration must be at least one day.

Cause: Invalid input was specified for the modify baseline window size routine.

Cause: The requested operation was not allowed on the system moving window baseline.

Cause: The system moving window baseline size must be less than the retention setting. The specified window size or retention violate this.

Cause: The operation failed because the specified baseline ID did not exist in the Workload Repository.

Cause: A read error occurred during the OCI operation to retrieve the baseline template information.

Cause: An error occurred while automatically generating a baseline based on the template information.

Cause: The operation failed because the specified baseline template name was an invalid identifier.

Cause: Error occurred during OCI operation due to underlying error.

Cause: The system is not able to drop the baseline since the baseline is in use by a functionality that depends on its existence.

Cause: The system is not able to find valid snapshot IDs for the inputted time range while attempting to create a baseline.

Cause: Invalid time input was specified for the create baseline routine.

Cause: An invalid parameter was specified for the Automatic Workload Repository (AWR) registration routine.

Cause: An invalid parameter was specified for the Automatic Workload Repository (AWR) operation.

Cause: An invalid parameter was specified for the Automatic Workload Repository (AWR) operation.

Cause: The required parameter was missing for the Automatic Workload Repository (AWR) operation.

Cause: The operation failed because the specified baseline template name was a directory.

Cause: The purge operation failed due to the reason described in the error message.

Cause: The current database was not set up for snapshots on remote databases. See the description in the error message.

Cause: The Automatic Workload Repository (AWR) reset operation failed due to the reason described in the error message.

Cause: The remote Automatic Workload Repository (AWR) operation failed because the remote database did not match the local registration data. The operation was aborted because it was meant for another database ID. Either the database or the remote database ID changed and needs to be updated or registered in the repository.

Cause: The operation ran longer than the expected time.

Cause: An attempt was made to bring a SYSAUX tablespace offline.

Cause: An attempt was made to drop a SYSAUX tablespace.

Cause: The operation failed because the tablespace was invalid for the Automatic Workload Repository (AWR) or was not available.

Cause: The operation failed because the Automatic Workload Repository (AWR) warehouse feature was disabled.

Cause: The operation failed because the database was already registered as a warehouse server or a warehouse client.

Cause: The operation failed because the database was not registered as a warehouse server or a warehouse client.

Cause: The operation failed because the system could not create a subdirectory under the specified mailbox directory.

Cause: The operation failed because either the DBID of the specified client or the specified warehouse DBID was already registered in the warehouse.

Cause: The DBID of the client was not registered in the warehouse.

Cause: The registered directory object was invalid.

Cause: The operation failed because the database could not read the label file in the specified directory.

Cause: The Automatic Workload Repository (AWR) import or export operation failed due to some errors. The possible causes were: - The specified database directory object was invalid. - The specified dump file existed in the specified directory. - The specified dump file did not exist in the specified directory. - Data Pump job encountered some errors. - The operation exceeded the maximum number of retries.

Cause: The input parameters to the Automatic Workload Repository (AWR) warehouse were invalid.

Cause: The specified package was reported to the warehouse previously. It was already being processed by the warehouse.

Cause: The input parameters to the Automatic Workload Repository (AWR) operation were invalid.

Cause: The Automatic Workload Repository (AWR) version that exported the data was out of the range of the supported versions that could be imported in the local AWR.

Cause: An error occurred in the Advisor. This message will be followed by a second message giving more details about the nature of the error.

Cause: The user specified an advisor name that has not be defined in the advisor repository.

Cause: The user attempted to access a task parameter that does not exist for the specified advisor object. The parameter may be misspelled or the user has selected a parameter that is not supported by the particular advisor.

Cause: The user attempted to retrieve a string parameter as a numeric value.

Cause: The user attempted to retrieve a non-table parameter as a table name.

Cause: The user attempted to reference an advisor task or object using a name that does not exist in the Advisor repository.

Cause: The user attempted to reference an invalid parameter element.

Cause: The user attempted to create the specified task or object using a name that already exists in the Advisor repository. Task names must be unique to the database user.

Cause: An attempt was made to specify a name for a task, object, execution or directive instance, which contained invalid characters or an invalid wildcard specifier.

Cause: The user attempted to cancel or interrupt a task that is not currently executing.

Cause: The user attempted to access a task directive that does not exist.

Cause: The user attempted to specify a command that does not exist.

Cause: The user attempted to access a recommendation action that does not exist in the task.

Cause: The user attempted to perform an operation that is not supported for the particular advisor or task type.

Cause: The user attempted to create a new task or object using an existing task or object that was not created by the same advisor.

Cause: The user attempted to create a new task or object using a name that is too long.

Cause: The user attempted an advisor operation that requires privilege.

Cause: The user attempted to execute a task that is currently executing.

Cause: The user executed a procedure but failed to provide correct values for the argument.

Cause: The user attempted to pass a character argument that is too long.

Cause: The user attempted to perform an operation that will update or delete a read-only task or object.

Cause: The user attempted perform an unsupported operation on a task or object that is identified as a template.

Cause: The user attempted to mark a recommendation using an invalid annotation. Valid annotation actions are ACCEPT, REJECT and IGNORE.

Cause: The user attempted to access a recommendation that does not exist in the task.

Cause: The user attempted to access a task that currently executing.

Cause: The user has specified an invlaid object type.

Cause: The user specified an non-existent object for the task

Cause: The user attempted to set the value of a parameter before the task was reset. This parameter cannot be changed until the task is reset.

Cause: The user could not access dba_* views.

Cause: The user attempted to access a task or object that is locked by another session.

Cause: The user attempted to execute a task that already contains execution results.

Cause: The user attempted to create a report or script from a task that has not successfully completed an execution.

Cause: The user signaled a cancel during a task or object operation.

Cause: The user attempted to execute a task that was interrupted.

Cause: The task must be in an inital state to be executed.

Cause: A numeric parameter was incorrectly supplied in string form.

Cause: The user supplied an invalid parameter value.

Cause: The user attempted to execute or modify the task that is in not in its INITIAL state.

Cause: The user signaled an interrupt during a task or object operation.

Cause: The task or object operation timed out.

Cause: The task or object operation timed out.

Cause: The user attempted to interrupt a task that has not reached interruptible mode.

Cause: The user supplied a date value in an incorrect format.

Cause: Request to interrupt or cancel task execution can not be granted because the task has not reached the appropriate mode.

Cause: Invalid user name specified to advisor framework

Cause: You attempted to reference an advisor task execution using a name that did not exist.

Cause: You attempted to perform a new execution using a name that already exists for the specified task. Execution names must be unique within the same task.

Cause: You attempted to set the value of a parameter while the task was being executed. This parameter cannot be changed until the task finishes its execution.

Cause: You attempted to use an advisor task execution type using a name that did not exist.

Cause: You attempted to execute a task for a multi-execution task advisor without specifying the type of execution to perform.

Cause: You attempted to associate an object to a task execution that id not contain the object.

Cause: The list did not include pairs of (parameter_name, parameter_value) where every parameter is a valide task parameter. Duplicates are not allowed.

Cause: You attempted to set execution parameters for an advisor that did not support multiple executions of its tasks.

Cause: An invalid directive identifier was specified to advisor framework.

Cause: An invalid instance identifier was specified to advisor framework.

Cause: An attempt was made to load an XML-based directive that does not conform to the documented DTD.

Cause: The specified parameter name could not be located within the directive XML document.

Cause: The specified filter could not be compiled within the directive XML document.

Cause: An attempt was made to create multiple instances of a directive when not permitted

Cause: The specified directive is not unique among the directives.

Cause: The specified directive instance is not unique among instances for this directive.

Cause: An attempt was made to update or delete a non-existent directive instance.

Cause: The supplied parameter value was not valid for the current task configuration.

Cause: An attempt was made to create a report or script from an execution that had not been successfully completed.

Cause: An attempt was made to create a task-managed SQL Tuning Set for a task that already had one.

Cause: The supplied execution names were not properly ordered by execution start date.

Cause: The supplied task ID was invalid.

Cause: The supplied execution ID was invalid.

Cause: The task or object operation interrupted itself when it detected that it was blocking some other session.

Cause: An execution was provided whose type did not match the one expected by the API.

Cause: No execution of the required type existed for the given advisor task.

Cause: An attempt was made to execute an unsupported advisor operation.

Cause: The start snapshot id was greater than the end snapshot id.

Cause: The start snapshot id and end snapshot id were identical.

Cause: The snapshot ids or the database id or the instance id was invalid or the specified snapshots have already been purged.

Cause: The parameter was not set before executing the ADDM.

Cause: Instance was shut down and restarted between the two specified snapshots.

Cause: The parameter was not set to an acceptable value for this particular mode of analysis.

Cause: Either the start or the end snaphots was missing or purged or had encountered errors while creating them.

Cause: One or both of the snapshots have been purged from AWR.

Cause: The parameter needs to be set before running the ADDM

Cause: Invalid interaction between two parameter values.

Cause: Some AWR tables encountered errors while creating one or more snapshots in the given range. The data present in one or more of these missing tables is necessary to perform an ADDM analysis.

Cause: ADDM analysis can only be performed on AWR snapshots taken in the current release.

Cause: Attempt to refer to an advisor's finding name that does not exist.

Cause: The specified value of SQL_ID was not properly formatted.

Cause: The specified value for a system parameter was not recognized by ADDM.

Cause: The specified value for system parameter CONTROL_MANAGEMENT_PACK_ACCESS indicated that the Diagnostic Package was disabled.

Cause: The specified value for system parameter CONTROL_MANAGEMENT_PACK_ACCESS indicated that the Tuning Package was disabled.

Cause: The specified package license and option were not installed.

Cause: ADDM analysis was attempted on imported Automatic Workload Repository (AWR) snapshots with incompatible character set.

Cause: Active Session History (ASH) dimension name provided was longer than the limit of 30 characters.

Cause: Active Session History (ASH) dimension name provided was invalid.

Cause: An invalid value was passed an input for a procedure argument.

Cause: The string input value was too long for the specific procedure argument.

Cause: The user attempted an SQL Tuning Set operation that requires a specific privilege.

Cause: The user attempted to access a SQL Tuning Set that does not exist or the user does have permission to access the SQL Tuning Set

Cause: The attempted to create a SQL Tuning Set in another schema without having the right privilege.

Cause: The user attempted to create a "\SQL Tuning"\ Set using a name that already exists for that owner.

Cause: The user attempted to access a SQL Tuning Set that does not exist.

Cause: The user attempted to specify a SQL Tuning Set name that is invalid. A name must not contain wildcards and its length must be less than 30 characters.

Cause: The user attempted to update an attribute element that cannot be modified. The only string attributes that can be updated are MODULE, ACTION, PARSING_SCHEMA_NAME, PRIORITY, and OTHER.

Cause: The user attempted to update an active SQL Tuning Set.

Cause: The user attempted to modify a SQL Tuning Set or to add a reference to a SQL Tuning Set which is in use.

Cause: The user attempted to remove a SQL Tuning Set reference that does not exist. The user might not own the reference.

Cause: An attempt was made to execute an operation that is not supported from a physical standby database.

Cause: The user attempted to select data from a data source using an invalid filter. A filter is a WHERE clause on data source content.

Cause: The user attempted to select data from a data source using an invlaid ranking measure. A ranking measure must represent a valid numerical expression.

Cause: The user attempted to use an attribute element that is not allowed in a ranking measure.

Cause: The user attempted to select data from a SQL Tuning Set using an invalid result percentage. The result percentage must be between 0 and 1.

Cause: The user attempted to select data from a SQL Tuning Set using an invalid result limit. A result limit must be a positive interger.

Cause: The user attempted to select data from a SQL Tuning Set using a percentage argument without specifying a ranking measure.

Cause: The user attempted to select data from the workload repository using an invalid snaphot ID range.

Cause: The user attempted to select data from the workload repository using a snaphot ID which does not exist.

Cause: The user attempted to select data from the workload repository using snapshots that do not exist.

Cause: The user attempted to access a baseline that does not exsit.

Cause: Unexpected error from DBMS_LOCK.REQUEST.

Cause: Unexpected error from DBMS_LOCK.REQUEST

Cause: The user attempted to perform an operation without having the appropriate privileges on V$SQL and V$SQL_BIND_CAPTURE.

Cause: The user attempted to perform an operation without having the appropriate privileges on views DBA_HIST_BASELINE, DBA_HIST_SQLTEXT, DBA_HIST_SQLSTAT, DBA_HIST_SQLBIND, DBA_HIST_OPTIMIZER_ENV, and DBA_HIST_SNAPSHOT.

Cause: The user attempted to load a SQL Tuning Set using an invalid input cursor. All rows in the cursor must match type SQLSET_ROW.

Cause: The user attempted to read a SQL tuning set belonging to someone else without having SELECT privilege on the DBA views

Cause: The user specified an attribute element that is not valid. The only attributes that can be selected are NULL, BASIC, TYPICAL, ALL or a comma separated list of the names including EXECUTION_STATISTICS, OBJECT_LIST, BIND_LIST and SQL_PLAN.

Cause: The user attempted to call remap_stgtab_sqlset without specifying either a new SQL tuning set name or a new SQL tuning set owner

Cause: The user attempted to call load_sqlset with a load option that is different than INSERT, UPDATE and MERGE.

Cause: The user attempted to tune a SQL statement that does not exist.

Cause: The user attempted to test-execute or generate explain plans for a SQL workload using the automatic SQL tuning task.

Cause: "An attempt was made to pass an argument that is valid only for a physical standby database. "

Cause: The user attempted to specify a tuning task scope that is invalid. The possible values are LIMITED or COMPREHENSIVE.

Cause: An attempt was made to accept SQL profiles for all statements in the input workload.

Cause: The user attempted to perform an operation on a task without specifying a target object or by using an invalid object identifier.

Cause: The user attempted to accept SQL profile for an object that has not a SQL text associated to it.

Cause: The user attempted to accept a SQL profile for an object that has not a SQL profile associated to it.

Cause: The user passed an invalid recommendation type in the rec_type argument to script_tuning_task. Possible values are ALL or any subset of a comma-separated list of PROFILES, STATISTICS and INDEXES.

Cause: The user passed an invalid action to process a SQL statement. Possible value is any subset of a comma-seperated list of EXECUTE and EXPLAIN_PLAN.

Cause: The user passed an invalid value for the time limit argument.

Cause: An attempt was made to resume a task that was created for a single SQL statement. A task can be resumed only if it is used for a SQL Tuning Set.

Cause: An attempt was made to execute an operation from a physical standby database that requires a valid database link to access a primary database.

Cause: An invalid metric to compare SQL performance was specified.

Cause: An attempt was made to analyze the performance of a SQL workload using two executions that were generated using two different actions.

Cause: An insufficient number of valid task executions to analyze the performance of a SQL workload were specified.

Cause: An invalid problem type was specified to the SQL diagnosis advisor. Problem type should be one of the PROBLEM_TYPE_* defined in 'admin/dbmsdiag.sql'.

Cause: Invalid SQL Id specified for conversion.

Cause: A call to GET_THRESHOLD procedure was made without a required parameter.

Cause: No threshold was found with the specified threshold key.

Cause: A SQL repository object was the target of two concurrent DDL operations.

Cause: An invalid Oracle identifier was used as the value of the parameter.

Cause: An error occured while try to delete a SQL Tuning Base object.

Cause: An invalid value was passed for the parameter.

Cause: An invalid value was passed for the parameter.

Cause: An invalid value was passed for the parameter.

Cause: An attempt was made to start a database operation in a session that was already being monitored.

Cause: An attempt was made to end a database operation that did not exist.

Cause: The database operation name or execution ID did not match.

Cause: The database operation name provided was invalid.

Cause: The database operation execution ID provided was invalid.

Cause: No SQL text was provided to the create SQL profile or patch operation.

Cause: No attributes were specified to the create SQL profile or patch operation.

Cause: One of the attributes within the SQL profile or patch was not properly specified.

Cause: A SQL profile or patch already exists with the name generated by the system.

Cause: A SQL profile or patch already exists with the name specified.

Cause: A SQL profile or patch already exists for the given SQL statement and category.

Cause: An invalid SQL profile or patch name was specified.

Cause: An invalid category name was specified.

Cause: A SQL profile or patch name was specified that doesn't exist.

Cause: A SQL profile or patch name was not provided as the from target of a clone SQL profile or patch operation.

Cause: An invalid attribute name was specified for an alter SQL profile or patch operation.

Cause: An invalid attribute value was specified for an alter SQL profile or patch operation.

Cause: An invalid HASH_VALUE was passed to a create SQL profile operation

Cause: An invalid ADDRESS value was passed to a create SQL profile operation.

Cause: A HASH_VALUE and ADDRESS combination passed to the create SQL profile operation doesn't coorespond to an existing V$SQL entry.

Cause: A concurrent DDL operation was performed during a create or replace sql profile operation.

Cause: A SQL profile already exists with the name specified under a different signature/category pair so it cannot be replaced, even with FORCE specified.

Cause: A user has tried to perform an operation that requires SELECT privileges on the DBA_SQL_PROFILES view.

Cause: A user tried to perform an operation by specifying a profile name/ category filter that did not target any profiles

Cause: A user called remap_stgtab_sqlprof without specifying new values for the sql profile name or category. At least one is required.

Cause: The supplied XML specification for the SQL profile did not adhere to the proper schema.

Cause: There are either multiple plans exist for the given value or the plan is not reproducible.

Cause: The give plan does not exist.

Cause: All SQL tuning advisor APIs executed from a physical standby database are required to use the same database link.

Cause: Attempt to disable a client identifier tracing which was never enabled

Cause: Attempt to enable a client identifier tracing which has been already enabled

Cause: Attempt to disable a service-level tracing which was never enabled

Cause: Attempt to enable a service-level tracing which has been already enabled

Cause: Attempt to disable a service-level tracing which was never explicitly enabled on a specific instance

Cause: Attempt to enable a service-level tracing which has been already enabled on a specific instance

Cause: Omitting service name while enabling/disabling tracing or aggregation

Cause: Module name is too long (exceeding 48 characters)

Cause: Action name is too long (exceeding 32 characters)

Cause: Action name is specified, but the module name is not

Cause: Service name is too long (exceeding 64 characters)

Cause: Attempt to enable a client identifier aggregation which has been already enabled

Cause: Attempt to disable a client identifier statistics aggregation which was never enabled

Cause: Attempt to disable a service-level statistics aggregation which was never enabled

Cause: Attempt to enable a service-level statistics aggregation which has been already enabled

Cause: Attempt to enable/disable a service-level statistics aggregation without a module specification

Cause: Omitting client identifier while enabling/disabling tracing or aggregation

Cause: Attempt to enable a database-level tracing which has been already enabled

Cause: Attempt to disable a service-level tracing which was never explicitly enabled on a specific instance

Cause: Attempt to enable an instance-level tracing which has been already enabled on a specific instance

Cause: Attempt to disable a database-level tracing which was never enabled

Cause: Instance name is too long (exceeding 16 characters)

Cause: A call to SET_THRESHOLD procedure was either missing a parameter, or the parameter was invalid.

Cause: An object name was passed to SET_THRESHOLD procedure that did not map to a valid object.

Cause: The object name was passed to a SET_THRESHOLD procedure that did not map to a valid data file.

Cause: A non-positive number was used for "Blocked User Session Count" metrics while operator contains equal.

Cause: The file on which threshold is specified was dropped and recreated during the procedure call.

Cause: The tablespace threshold values can be in the range 0 to 100 only.

Cause: An attempt was made to set a threshold on dictionary-managed tablespaces.

Cause: An attempt was made to specify an invalid value for critical or warning thresholds.

Cause: An attempt was made to specify an invalid combination of metrics id // and object type parameters.

Cause: An attempt was made to specify an invalid combination of threshold value and operator.

Cause: An attempt was made to call GET_THRESHOLD procedure without a required parameter.

Cause: The threshold did not exist with the specified threshold key.

Cause: An attempt was made to call SET_THRESHOLD procedure with the critical threshold value less than the warning threshold value.

Cause: SET_THRESHOLD procedure was called when SYSAUX tablespace was offline.

Cause: An error occurred when sending notification for this threshold.

Cause: An attempt was made to call SET_THRESHOLD procedure with the bytes based critical threshold value greater than the warning threshold value.

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

Cause: Connection to the database is dead, or invalid parameter to alert routine.

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

Cause: Can only specify a value for one or the other.

Cause: SET_THRESHOLD procedure was called when database was open in read-only mode.

Cause: MMON sub-action did not complete within the system specified time frame.

Cause: Passed an invalid component, report, or transformation name to the framework. Names must be alphanumeric and can contain the underscore (_) character.

Cause: Passed an unknown component, report, or transformation to the framework.

Cause: An object with the first name is unknown within the naming scope of the second name

Cause: An object is unknown within the given naming scope

Cause: An object with the given name already exists

Cause: An object with the first name already exists within the naming scope of the second name

Cause: The top-level report tag was not built properly.

Cause: An invalid content type was passed to the register format API

Cause: An invalid parameter/value was passed to a dbms_report API

Cause: An invalid file name was passed to STORE_FILE

Cause: A URL with invalid syntax was provided, either directly to the function or via an XML IMPORT or INCLUDE.

Cause: Either a URL or path prefix with invalid syntax was provided.

Cause: The file requested could not be found in the given location.

Cause: An HTML document was passed to the function missing its body tag.

Cause: The given reference string could not be parsed.

Cause: An invalid URL was provided to the servlet.

Cause: An error was received from the xpath library during an xpath operation.

Cause: Invalid input was given when attempting to build a common tag.

Cause: An invalid parameter was provided to one of the report framework variable argument list functions.

Cause: An invalid parameter was provided to one of the report framework structured argument list functions.

Cause: An invalid tag name was provided to the report framework common tag callout function.

Cause: This is an internal Server Manageability Error

Cause: CREATE INDEX statement contained more than one LOCAL clause

Cause: CREATE INDEX statement contained a GLOBAL clause and a LOCAL clause

Cause: CREATE INDEX statement contained more than one GLOBAL clause

Cause: CREATE INDEX statement contained a LOCAL clause and a GLOBAL clause

Cause: keyword PARTITION missing

Cause: keyword RANGE missing

Cause: a partition name of the form identifier is expected but not present.

Cause: keyword LESS missing

Cause: keyword THAN missing

Cause: while parsing a CREATE INDEX statement to create a LOCAL partitioned index, partition-description of one of partitions was found to contain VALUES LESS THAN clause which is illegal since a LOCAL index inherits partition bounds from its base table

Cause: unexpected option was encountered while parsing physical attributes of an index partition; valid options for Range or Composite Range partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE; only TABLESPACE may be specified for Hash partitions

Cause: Names of partitions resulting from splitting of an existing table or index partition are not distinct

Cause: Name of a partition resulting from splitting of an existing table or index partition is identical to that of some other existing partition of that table or index

Cause: Name of a partition of a table or index being created is not unique

Cause: number of columns in a partitioning column list exceeded the legal limit of 16

Cause: CREATE TABLE or CREATE INDEX contained too many partition descriptions; maximum number of partitions is 1048575 (1024K-1).