Cause: An invalid index was specified in a call to bind_array of dbms_sql. The index may have been null or of an improper value.

Cause: The value of index1 was greater than the value for index2 in the call to bind_array. This is illegal since the elements of the table that will be bound are those with indexes greater than or equal to index1 and less than or equal to index2.

Cause: The bound table does not contain elements at both index locations in call to bind_array of dbms_sql. This is illegal. Both index locations must contain elements. In other words tab.exists(index1) and tab.exists(index2) must both return true.

Cause: The count argument specified in the call to procedure define_array of package dbms_sql had an invalid value. Invalid values are negative numbers and nulls. The argument must be a positive integer.

Cause: The lower_bound argument specified in the call to procedure define_array had an invalid value. Legal values are all integers (both positive and negative) including zero. The null value is illegal.

Cause: Both define_array and bind_array have been called on this cursor. This is illegal. It is not possible for a cursor to both contain array binds and array defines. The semantics of this setting are nonsensical. Array defines are used to move data from select queries into PL/SQL tables and array binds to bind PL/SQL tables to non-select queries.

Cause: Both define_array and define_column have been called on this cursor. This is illegal. It is not possible for a cursor to both contain regular and array defines. The semantics of this setting are nonsensical. Array defines are used to move data from select queries into PL/SQL tables and regular defines to move data from select queries into PL/SQL variables.

Cause: The specified host was unknown.

Cause: The input or output buffer was too small for the operation.

Cause: The end of the input was reached.

Cause: A network error occurred.

Cause: A bad argument was passed to the PL/SQL API.

Cause: An improperly formed URL was passed to the PL/SQL API.

Cause: A HTTP protocol error occured during the HTTP operation.

Cause: The URL scheme was unknown or unsupported.

Cause: The requested HTTP header was not found.

Cause: The end of the HTTP response body was reached.

Cause: The call to the PL/SQL API was illegal at the current stage of the operation.

Cause: The HTTP response indicated that the HTTP client error occurred.

Cause: The HTTP response indicated that the HTTP server error occurred.

Cause: Too many HTTP requests were opened.

Cause: The network connection was not made while the network operation was attempted.

Cause: The UTL_HTTP package failed to initialize.

Cause: The UTL_HTTP package failed to execute the HTTP request.

Cause: The character set used as an encoding of the URL is a fixed-width multibyte character set and is not allowed for a URL.

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

Cause: Timeout occurred while reading from or writing to a network connection.

Cause: The SMTP operation was invalid at the current stage of the SMTP transaction.

Cause: A SMTP transient error occurred.

Cause: A SMTP permanent error occurred.

Cause: A corresponding directory object does not exist.

Cause: An invalid value was specified for file open mode.

Cause: A file ID handle was specified for which no corresponding open file exists.

Cause: An attempt was made to read from a file or directory that does not exist, or file or directory access was denied by the operating system.

Cause: An attempt to read from a file failed.

Cause: Failed to write to, flush, or close a file.

Cause: A fatal error occurred while allocating PL/SQL session memory.

Cause: An invalid maximum line size value was specified.

Cause: An invalid file name or a file name of an invalid length was specified.

Cause: A directory object was specified for which insufficient privilege was granted.

Cause: An attempt was made to seek past the end of the file, or both the absolute and relative offsets were NULL, or absolute offset was less than zero.

Cause: A file deletion attempt was refused by the operating system.

Cause: A file rename attempt was refused by the operating system either because the source or destination directory does not exist or is inaccessible, or the source file isn't accessible, or the destination file exists.

Cause: The stream state was discovered to be invalid during compression or uncompression, or an invalid compression quality was requested or a NULL or invalid compression parameter was detected.

Cause: An error occurred while compressing or uncompressing input source.

Cause: An error occurred while scanning string for mime header tag

Cause: An error occurred while decoding the input string

Cause: The compressed output is too big to return.

Cause: The character set mode in which the file was opened did not match the character set of the read or write operation.

Cause: The process program opened too many handles, and the specified handle was either uninitialized or outside a valid range.

Cause: Another ORACLE error occured in the DBMS_PITR package.

Cause: The DBMS_PITR package function/procedure was called in an incorrect order.

Cause: The database was not opened as a clone database.

Cause: The user did not log in as SYS to perform tablespace point-in-time recovery in a clone database.

Cause: The selected tablespace does not exist in the database.

Cause: An attempt was made to ALTER the tablespace to be read only.

Cause: The selected datafile was not online.

Cause: The datafile is not ready for tablespace point-in-time recovery.

Cause: Some objects which crossed the boundary of the recovery set were not allowed in the tabelspace point-in-time recovery.

Cause: The version of DBMS_PITR is different from the version of the cloned database.

Cause: Either the database was not open, or an attempt was made to open it as a cloned database.

Cause: The export dump files were imported to an incorrect database.

Cause: This is an internal error.

Cause: Tablespace clean SCN is either 0 or invalid.

Cause: An attempt was made to recover a tablespace to a point-in-time before it was recreated.

Cause: This is an internal error.

Cause: The specified datafile could not be found in the production database.

Cause: The datafile is online.

Cause: An incorrect datafile was copied to the production database. The datafile information in the export dump file differs with the information in the datafile in the production database.

Cause: An error occured during reading datafile header.

Cause: Too many datafiles were added to the recovery set since the point-in-time recovery.

Cause: Too many characters in specifying the SCN string

Cause: The ALTER DATABASE SET COMPATIBILITY command failed because one or more instances do not support dynamic compatible setting change.

Cause: It should be of the form x.x.x

Cause: The SET COMPATIBILITY release compatibility release number was lower than the current compatible setting.

Cause: The ALTER DATABASE SET COMPATIBILITY command failed because one or more instances had a lower release number.

Cause: The client compatibility mode is higher than the version of the server.

Cause: Too many datafiles in this bitmap tablespace. ORACLE does not support at this moment.

Cause: Table is not XMLType table

Cause: Source script length exceeded the maximum size of 4 Gigabytes.

Cause: The HTTP response indicated a redirection to another location.

Cause: The tablespace is not read only.

Cause: Internal error from package DBMS_PLUGTS.

Cause: The tablespace has a non-standard block size and making such a tablespace read-write is not permitted.

Cause: The referred datafile is not in a state ready for tablespace copy operation. For example, the datafile may be offline. The datafile needs to be ONLINE, and either READ ONLY or READ WRITE.

Cause: The block size of the tablespace to be plugged in or created does not match the block sizes configured in the database.

Cause: This is caused either by a corrupted export file or by an Oracle internal error.

Cause: The set of objects in the set of tablespaces selected are not self-contained.

Cause: The referred user is one of the owners of data in the pluggable set. This user does not exist in the database.

Cause: The referred user is one of the owners of data in the pluggable set. This user does not exist in the database.

Cause: The system failed to match the referred owner. There are two cases that this may occur. (1) This user owns data in the transportable set, but this user is not specified in the TTS_OWNERS list of the import command line option, assuming that TTS_OWNERS is specified. (2) This user is specified in the TTS_OWNER list, but this user does not own any data in the transportable set.

Cause: Oracle does not support plugging a tablespace into a database using an incompatible character set.

Cause: the tablespace list supplied to dbms_tts.transport_set_check PL/SQL routine is in an incorrect format.

Cause: The system failed to match the referred tablespace. There are 2 cases that this may happen. (1) This tablespace is in the transportable set, but it is not specified in the TABLESPACES list of the import command line option, assuming that TABLESPACES is specified. (2) This tablespace is in the TABLESPACES list, but it is not in the transportable set.

Cause: The datafiles to be plugged in are not specified.

Cause: Tried to plug-in a tablespace which already exists.

Cause: The referred tablespace is either the system tablespace, the sysaux tablespace, or a temporary tablespace.

Cause: The DBMS_SYSTEM.WAIT_FOR_EVENT procedure was called with an event name that is not an internal event.

Cause: The transportable list exceeds the buffer size of 32767.

Cause: An attempt to transport a tablespace, or unplug a pluggable database containing a tablespace in the middle of a tablespace encrypt, decrypt, or rekey failed.

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

Cause: A parameter was specified as an argument to procedure CREATE_PLAN_DIRECTIVE or UPDATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER that is not allowed when the GROUP_OR_SUBPLAN is a plan. Only the following parameters are allowed when GROUP_OR_SUBPLAN is a plan: - MGMT_P1, MGMT_P2, MGMT_P3, MGMT_P4 MGMT_P5, MGMT_P6, MGMT_P7, MGMT_P8 - UTILIZATION_LIMIT

Cause: The name specified as an argument to procedure CREATE_PLAN, CREATE_CDB_PLAN, CREATE_CONSUMER_GROUP, or CREATE_CATEGORY of package DBMS_RESOURCE_MANAGER was already in use.

Cause: An invalid plan name was specified as an argument to procedure UPDATE_PLAN or UPDATE_CDB_PLAN of package DBMS_RESOURCE_MANAGER.

Cause: An invalid method was specified as an argument to procedure CREATE_PLAN or UPDATE_PLAN of package DBMS_RESOURCE_MANAGER.

Cause: A resource plan and its subplans had more than one directive for a particular subplan.

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

Cause: A nonexistent plan directive was specified for procedure UPDATE_PLAN_DIRECTIVE or UPDATE_CDB_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER.

Cause: An attempt was made to modify a mandatory plan directive.

Cause: An attempt was made to create a plan directive that already exists.

Cause: An attempt was made to set both parameters.

Cause: An invalid consumer group name was specified.

Cause: A non-existent object name was specified as an argument to procedure CREATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER.

Cause: An non-existent consumer group was specified.

Cause: An invalid method name was specified as an argument to procedure CREATE_CONSUMER_GROUP or UPDATE_CONSUMER_GROUP of package DBMS_RESOURCE_MANAGER.

Cause: An attempt was made to activate a pending area that is already active.

Cause: An attempt was made to make changes without creating a pending area.

Cause: An attempt was made to specify a string that exceeded the maximum length for that parameter.

Cause: An attempt was made to execute an operation that cannot be executed with the resource manager being off

Cause: A plan was created in the pending area that is an orphan or stand-alone.

Cause: The sum of plan directive parameter values for the specified plan level exceeded the limit specified.

Cause: The number of consumer groups in the specified plan was more than the limit specified.

Cause: OTHER_GROUPS was not included as part of the specified top-plan. Each top plan must include the built-in consumer group OTHER_GROUPS.

Cause: The mapping priorities were not unique integers within the valid range.

Cause: A loop was discovered while validating a top-plan.

Cause: An attempt was made to delete an active plan in the pending area. No changes can be made to active plans.

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

Cause: Invalid changes were attempted in the pending area.

Cause: An attempt was made to create or modify the specified top-plan but it has some plans as leaves.

Cause: An attempt was made to create or modify the specified plan, but the plan has more than 28 consumer groups or subplans.

Cause: An attempt was made to create a plan directive from a plan to itself.

Cause: An attempt was made to delete or modify the specified mandatory plan or consumer group.

Cause: The VALIDATE_PENDING_AREA procedure found that either the intended top-plan(s) are involved in a loop or there are no top-plans.

Cause: An attempt was made to delete a subtree that includes a plan or consumer group that is part of more than one top-plan as part of procedure DELETE_PLAN_CASCADE or package DBMS_RESOURCE_MANAGER. Such a plan or consumer group cannot be deleted.

Cause: The number of errors detected during validation is too high.

Cause: An attempt was made to create or modify some plans in the pending area that are not part of any top-plan

Cause: An attempt was made to create a mandatory plan directive where either PLAN or GROUP_OR_SUBPLAN or both were not mandatory

Cause: The cpu parameters for the specified level had a non-zero value, which is not a valid value for the plan's current cpu policy.

Cause: An invalid user name was specified as argument to procedure SET_INITIAL_CONSUMER_GROUP of package DBMS_RESOURCE_MANAGER or SWITCH_CONSUMER_GROUP_FOR_USER of package DBMS_SYSTEM or the specified user was not logged on.

Cause: Invalid session id and serial# were specified as arguments to procedure SWITCH_CONSUMER_GROUP_FOR_SESS of package DBMS_SYSTEM.

Cause: An attempt was made to set the initial consumer group of a user to OTHER_GROUPS or an INTERNAL_USE group.

Cause: An attempt was made to switch the consumer group of a user or a session to OTHER_GROUPS or an INTERNAL_USE group.

Cause: An attempt was made to grant or revoke the privilege to switch to OTHER_GROUPS or an INTERNAL_USE group.

Cause: An invalid privilege name was specified as an argument to procedure GRANT_SYSTEM_PRIVILEGE or REVOKE_SYSTEM_PRIVILEGE of package DBMS_RESOURCE_MANAGER_PRIVS.

Cause: An attempt was made to set the initial consumer group of the specified user but the user does not have the privilege to switch to that group.

Cause: An error has occurred in a data cartridge external procedure. This message will be followed by a second message giving more details about the data cartridge error.

Cause: The data cartridge encountered an unexpected condition. The argument is a string that identifies the internal error to Oracle development. This argument and the database version number are critical in identifying the root cause.

Cause: Too many UTL_FILE files were opened.

Cause: The directory object mapped to an empty directory.

Cause: The file was opened in an unexpected mode.

Cause: The directory path contained a symlink.

Cause: The expected file or path did not exist.

Cause: There was an access error on the file.

Cause: The file was a link.

Cause: An internal error occurred in the UTL_FILE.

Cause: The effective userid or roles on this call to DBMS_SQL are not the same as those at the time the cursor was parsed.

Cause: DBMS_SQL access was denied due to security concerns.

Cause: An invalid security_level value was specified.

Cause: Invalid privilege checking level specified.

Cause: Security level of 0 is specified with DBMS_SQL.OPEN_CURSOR.

Cause: An unsupported combination of argument values was present in a call to DBMS_SYS_SQL.PARSE_AS_USER.

Cause: An attempt was made to close a DBMS_SQL cursor while it was executing under its own context.

Cause: The size of the SQL statement exceeded 4 gigabytes -1.

Cause: An attempt was made to return an implicit result through a statement type other than a PL/SQL or DML statement.

Cause: An attempt was made to return more than the maximum number of implicit results permitted.

Cause: An attempt was made to retrieve implicit results when none were available.

Cause: An attempt was made to return implicit results to an older version client that is not capable of receiving these implicit results.

Cause: An unsupported combination of argument values was present in a call to DBMS_SYS_SQL.PARSE_AS_USER.

Cause: An unsupported combination of argument values was present in a call to DBMS_SYS_SQL.PARSE_AS_USER.

Cause: An unsupported combination of argument values was present in a call to DBMS_SYS_SQL.PARSE_AS_USER.

Cause: A complex type bound or defined in one container, where cursor execution occurs in another container, was not an object or metadata linked type.

Cause: The ADM_PARALLEL_EXECUTE role needed to execute the subprogram was not granted.

Cause: An attempt was made to chunk a table by ROWID, but the table was not a physical table or the table was an IOT. physical table or the table is an IOT.

Cause: An attempt was made to create chunks on a task which was not in the CREATED state.

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

Cause: An attempt was made to execute the task which was not in the CHUNKED state.

Cause: An attempt was made to resume execution but the task was not the FINISHED_WITH_ERROR or CRASHED state.

Cause: The input argument was null, or it exceeded the maximum length limit.

Cause: A task with the same name was already in existence.

Cause: The task did not exist.

Cause: The specified chunk did not exist.

Cause: A NAMED keyword was specified in the CREATE JAVA CLASS statement. NAMED keywords are valid only in CREATE JAVA SOURCE or RESOURCE statements.

Cause: The required name for a Java source, class, or resource was invalid or missing.

Cause: The name for a Java resource was not specified. The name must be specified with the NAMED keyword.

Cause: SCHEMA and NAMED keywords were used together in the same CREATE JAVA command, but only one may be used in a CREATE JAVA command.

Cause: The required schema name was invalid or missing.

Cause: The AS keyword was used in CREATE JAVA CLASS or RESOURCE. The AS keyword is valid only in CREATE JAVA SOURCE.

Cause: The USING clause did not form a valid query.

Cause: The USING clause defined a query that either did not return any values, or returned more than one value.

Cause: The USING clause did not form a query that selects a value of the type specified by the term following the USING keyword.

Cause: An attempt was made to create a Java class using data expected to be in binary (Java .class) format. The data was found not to be in this format, or to be incorrectly formed.

Cause: A CREATE JAVA command attempted to create a source, class, or resource object with a name that is already in use.

Cause: A CREATE AND RESOLVE NOFORCE JAVA CLASS command specified definition data that could not be resolved, or resolution failed for some referenced class.

Cause: A name resolver was not specified in the required form: (( name pattern , schema name) ...)

Cause: An attempt was made to import a .class file containing a class name of length greater than %d. The .class file could not be imported because the referenced class name was too long.

Cause: An attempt was made to import a .class file containing a character that cannot be converted to the server character set. The .class file could not be imported because of the illegal character.

Cause: Java code included a call to java.lang.Runtime.exitInternal.

Cause: An internal error occurred in the Aurora module.

Cause: An attempt to resolve a referenced class failed.

Cause: A referenced name was resolved to an object that is not a Java class.

Cause: A referenced name was resolved to a synonym, which translated to a class whose name does not match the referenced name.

Cause: An attempt to access a referenced class failed.

Cause: Name resolution failed to find an object with the indicated name.

Cause: An attempt was made to resolve a class that is not authorized to use the indicated referenced class.

Cause: An attempt was made to resolve a class that is not authorized to use a referenced class. The name of the referenced class could not be determined.

Cause: A method was called with argument(s) of incompatible type(s).

Cause: An attempt was made to create a class that references a name longer than 4000 characters. The class could not be created because the name is too long.

Cause: An informational message, not an error.

Cause: An informational message, not an error.

Cause: The Java method specified in trigger does not exist or cannot be called as used.

Cause: The function or method specified in Java trigger call expression could not be resolved.

Cause: Insert into shortened name translation table failed.

Cause: An attempt was made to execute a non-existent method in a Java class.

Cause: A Java exception or error was signaled and could not be resolved by the Java code.

Cause: A class or resource defined by a SQLJ source conflicted with an existing object.

Cause: Name resolution determined that the indicated object is referenced but could not be resolved.

Cause: The reason the current class object was invalid is recorded with the source object from which it was compiled.

Cause: An attempt was made to create a Java source object with text that could not be parsed adequately to determine the class(es) defined by it.

Cause: An attempt was made to create or drop a Java class or resource that is known to result from compilation of an existing Java source object.

Cause: An attempt was made to use a Java command when Java is not installed.

Cause: An attempt was made to use the CREATE JAVA SYSTEM command in a database where the Java system classes already are installed.

Cause: Java method execution failed to find a class with the indicated name.

Cause: An attempt was made to execute a method in a Java class that had not been previously and cannot now be compiled or resolved successfully.

Cause: An attempt was made to create a Java source object that would define a class that is already defined by a different Java source object.

Cause: An attempt was made to use a Java command that is not yet implemented.

Cause: The type argument in a call to a Java export or import command did not have a recognized value.

Cause: An attempt was made to create a Java class object with bytecodes that were rejected by the Java verifier.

Cause: An attempt was made to create a Java resource object with data that was rejected by the Java verifier.

Cause: An attempt was made to use a command that requires a Java system class that was not yet present or was invalid.

Cause: A command that uses a Java system class was aborted due to an error reported by the Java system class.

Cause: A class in use by the current session was redefined or dropped, invalidating the current Java session state and requiring that it be cleared.

Cause: The Java state in the current session became inconsistent and was cleared.

Cause: A string in the database character set could not be converted to Unicode, as required for use by Java.

Cause: An attempt was made to create a Java class object with bytecodes that caused the Java verifier to issue a warning.

Cause: An attempt was made to modify a Java class that is in use in the current call.

Cause: The session encountered an out of memory condition in Java from which it could not recover. Java session state was cleared.

Cause: A Java source, class, or resource was specified in an inappropriate place in a statement.

Cause: A database object name that named a Java source, class, or resource now names an object of a different type.

Cause: A command was attempted that would have modified a Java system class.

Cause: JAccelerator (NCOMP) is not installed.

Cause: Java VM JIT is not supported on this platform.

Cause: The USING clause of a type has to be the same as its supertype or compatible with it.

Cause: The class has to implement the required interface for the value of the option for USING.

Cause: The supertype has an existing type that has the same value for the EXTERNAL NAME.

Cause: The EXTERNAL NAME clause of the type is not a subclass of the supertype EXTERNAL NAME.

Cause: Unable to connect using the JDBC default connection.

Cause: The class is not loaded in the database.

Cause: The class is not loaded in the database.

Cause: The EXTERNAL NAME option of one or more attributes do not match any fields in the defined class.

Cause: The EXTERNAL NAME option of one or more functions do not match any method in the defined class.

Cause: The helper class used for supporting SQLJ Object Type is not generated.

Cause: The Java VM has detected a thread deadlock.

Cause: Connect to CSS failed or timed out.

Cause: An unexpected error occurred while performing a CGS operation.

Cause: An unexpected error occurred while performing a global enqueue service operation.

Cause: The ACTIVE_INSTANCE_COUNT parameter was specified when one of the instances in the cluster was running Oracle 8.1.5 or an earlier release.

Cause: The value of the ACTIVE_INSTANCE_COUNT parameter must be the same in all Oracle cluster database instances.

Cause: The ACTIVE_INSTANCE_COUNT parameter must be set to 1 in a two node cluster database configuration or unspecified if a secondary instance is not needed.

Cause: The value of the initialization parameter in error must be identical on all Oracle cluster database instances and was not.

Cause: An unexpected error occurred while performing a CSS operation.

Cause: Could not communicate with CSS to complete the operation.

Cause: The operation could not be performed or CSS was shutting down.

Cause: An unexpected error occurred while performing a Cluster Synchronization Services (CSS) operation.

Cause: A client of the global enqueue service specified an instance that no longer existed.

Cause: The instances that were running were only read-mostly or read-only instances which causes the whole cluster to shut down.

Cause: The attempted feature was not allowed on read-mostly instances.

Cause: The Read-mostly and Read-only instances were part of the same cluster.

Cause: This instance was evicted from the group by another instance of the cluster database group for one of several reasons, which may include a communications error in the cluster and failure to issue a heartbeat to the control file.

Cause: The IMR feature is not active for this instance, but is active for another instance in the cluster database.

Cause: The selected Instance Membership Recovery protocol was not compatible with other running instances in the cluster database.

Cause: This instance did not participate in the instance membership recovery protocol because it was not in good health. Some or all of its receivers were not making progress. Therefore, this instance terminated itself.

Cause: The database was configured with Oracle Real Application Clusters (Oracle RAC) enabled in Oracle Database Standard Edition (SE).

Cause: The administrator has shut down the Cluster Synchronization Service daemon. This error message is intended to be informative to users on the status of the service.

Cause: The init.ora file did not contain a value for the instance_number which is required to identify this instance to other instances of the database running on the same cluster

Cause: The specified process mades no progress within the maximum allowed time.

Cause: The specified process blocked a global enqueue process for the maximum allowed time.

Cause: Attempt to connect to the GPnP deamon failed with the error reported.

Cause: An attempt to set the Grid Plug and Play (GPnP) attribute failed. See the brackets for the reason.

Cause: The update operation for attributes was not permitted because Cluster Synchronization Services (CSS) was not running on the host.

Cause: An attempt to get the Grid Plug and Play (GPnP) attribute failed. See the brackets for the reason.

Cause: An attempt to get the Oracle Restart attribute failed. See the brackets for the reason.

Cause: An attempt to set the Oracle Restart attribute failed. See the brackets for the reason.

Cause: Attempt to get the network information failed. See the brackets for the reason.

Cause: An attempt was made to change user session parameters for a non-user session.

Cause: The user attempted to replay a transaction.

Cause: The name specified for the operator is incorrect.

Cause: The RETURN keyword has not been specified.

Cause: The CONTEXT keyword has not been specified.

Cause: The ANCILLARY keyword has not been specified.

Cause: The DATA keyword has not been specified.

Cause: Keyword COLUMN is expected .

Cause: The operator binding which has been specified does not exist.

Cause: The operator which has been specified does not exist.

Cause: The specified binding for the primary operator does not exist.

Cause: The operator which is being dropped has some dependent objects.

Cause: The user does not have the appropriate privileges to perform the specified operation on the operator.

Cause: This is not a valid option with the ASSOCIATE command.

Cause: The specified name is not a valid name.

Cause: The type of object specified is not supported with the associate statistics statement.

Cause: Expecting the USING or DEFAULT keyword after the names of object(s).

Cause: The object for which the association is being defined is not present.

Cause: Object which is being disassociated is not present.

Cause: The type of object specified is not supported with the disassociate statistics statement.

Cause: Name of the column should contain the table and the column name.

Cause: User tried to associate DEFAULT values with columns which is not a valid option .

Cause: The statistics type which is being associated with object(s) is not present.

Cause: The specified primary operator does not exist.

Cause: User tried to associate selectivity with index or indextypes which is not allowed .

Cause: The object being analyzed is not a table and is not supported

Cause: The operator is invalid.

Cause: Indextype name or Indextype schema name has invalid characters.

Cause: FOR keyword must be provided with Create Indextype statement.

Cause: USING keyword and corresponding implementation details must be provided.

Cause: Implementation type or Implementation schema name is invalid.

Cause: The implementation type specified with USING clause could not be found.

Cause: The operator could not be found.

Cause: The specified binding for the operator is not available from the operator schema object.

Cause: One or more indexes are dependent upon the indextype.

Cause: There is no indextype by the specified name.

Cause: The user specified a REF datatype which is not supported in CREATE OPERATOR.

Cause: The ODCIObjectList returned by the ODCIGetInterfaces routine does not contain the interface(s) required by the current usage.

Cause: One of the operators referenced cannot be compiled.

Cause: User does not have privileges to execute the implementation type.

Cause: User does not have privileges to execute one of the operators.

Cause: Implementation type cannot be compiled.

Cause: Indextype and implementation type are in different schema.

Cause: The user specified an invalid option with the ALTER INDEXTYPE command

Cause: User specified an option which is not supported with the version of the indextype interface provided

Cause: User attempted to drop all the operators from the indextype

Cause: User attempted to add an operator name to an indextype which is already supported by the indextype

Cause: User specified a create local domain index statement using an indextype that does not support local domain indexes on tables partitioned with the given method

Cause: User specified a create local domain index statement on a table partitioned using a method not supported by domain indexes

Cause: User specified a create local domain index statement on a partitioned index-organized table

Cause: Failed to successfully execute the ODCIIndexMergePartition routine.

Cause: Failed to successfully execute the ODCIIndexSplitPartition routine.

Cause: The user specified an invalid option like ASC, DESC, SORT or a parallel clause, partitioning clause or physical attributes clause.

Cause: User attempted to build a domain index on more than one column.

Cause: IS keyword must be specified with Create Index statement for domain indexes.

Cause: An attempt was made to create a domain index with the UNIQUE attribute.

Cause: An attempt was made to create a domain index with the BITMAP attribute.

Cause: Failed to successfully execute the ODCIIndexCreate routine.

Cause: Failed to successfully execute the ODCIIndexDrop routine.

Cause: An attempt was made to drop a tablespace which contains secondary objects and/or domain indexes.

Cause: Failed to successfully execute the ODCIIndexAlter routine.

Cause: Failed to successfully execute the ODCIIndexTruncate routine.

Cause: The table has domain indexes defined on it that are marked LOADING.

Cause: An attempt has been made to access a domain index that is being built or is marked failed by an unsuccessful DDL or is marked unusable by a DDL operation.

Cause: A DROP INDEX FORCE was issued for a non-domain index.

Cause: A warning was returned from the ODCIIndexCreate routine.

Cause: Tried to analyze a domain index which was marked as LOADING or FAILED.

Cause: The indextype is invalid.

Cause: Tried to create a domain index on a column of an index-organized table.

Cause: The user attempted to create a domain index on a column of LONG datatype.

Cause: Tried to issue a DROP/ALTER/TRUNCATE on a domain index in a LOADING state.

Cause: Tried to issue a DROP/ALTER on a domain index in a FAILED state.

Cause: Specified the ONLINE or PARAMETERS clause with a non-domain index.

Cause: The user specified an invalid option for altering a domain index.

Cause: The user combined PARAMETERS clause with other alter index options.

Cause: A waring was returned from the ODCIIndexDrop routine.

Cause: A waring was returned from the ODCIIndexAlter routine.

Cause: Failed to successfully execute the ODCIIndexInsert routine.

Cause: Failed to successfully execute the ODCIIndexDelete routine.

Cause: Failed to successfully execute the ODCIIndexUpdate routine.

Cause: A warning was returned from the ODCIIndexTruncate routine.

Cause: An attempt was made to define multiple domain indexes on the same column list using identical indextypes.

Cause: An attempt was made to create multiple domain indexes on a column list using indextypes which do not have disjoint operators.

Cause: Indextype cannot be compiled.

Cause: User does not have privileges to execute the indextype.

Cause: User specified an expression in the column list.

Cause: An ALTER TABLE DROP COLUMN was issued on a column on which a domain index exists.

Cause: An ALTER TABLE MODIFY COLUMN was issued on a column on which a domain index exists.

Cause: Feature is not supported for domain indexes.

Cause: An ALTER TABLE ENABLE ROW MOVEMENT was issued on a table which has a domain index defined on it.

Cause: A create domain index statement was issued on a table that has row movement enabled.

Cause: The primary operator does not have an index and scan contexts.

Cause: The user specified a REF or a LONG datatype which is not supported in CREATE/ALTER INDEXTYPE WITH ARRAY DML (DATA_TYPE, VARRAY_TYPE).

Cause: WITH ARRAY DML (DATA_TYPE, VARRAY_TYPE) option and WITHOUT COLUMN DATA option conflicted in an alter indextype statement

Cause: One of the base and varray datatypes specified in WITH ARRAY DML (DATA_TYPE, VARRAY_TYPE) clause could not be found.

Cause: User attempted to add a base datatype to an indextype with ARRAY DML which is already supported by the indextype

Cause: An attempt was made to specify a parameter value that is longer than the allowed maximum.

Cause: An attempt was made to create a domain index on the same column where an invalid domain index exists.

Cause: There is no binding for the current usage of the operator.

Cause: The function underlying the operator binding does not exist.

Cause: The execution of ODCIIndexStart routine caused an error.

Cause: The execution of ODCIIndexFetch routine caused an error.

Cause: The execution of ODCIIndexClose routine caused an error.

Cause: A required method with the required signature does not exist in the specified type.

Cause: The indextype does not exist.

Cause: There are multiple primary invocations of operators with the same number as the label.

Cause: The primary invocation corresponding to an ancillary operator is missing.

Cause: The label used for invoking the ancillary operator is not a literal number.

Cause: Encountered an invalid callback operation.

Cause: The ODCIIndexStart() routine returned a null scan context

Cause: The execution of the specified callout caused an error.

Cause: The ODCIObjectList returned by the ODCIGetInterfaces routine does not contain the required stream version for external tables.

Cause: Collection operands cannot be updated

Cause: Tables which gets its rows from a collection operand cannot be locked

Cause: An attempt was made to create a domain index on a temporary table

Cause: Failed to successfully execute the ODCIINDEXUPDPARTMETADATA routine.

Cause: Failed to successfully execute the partition maintenance operation of a secondary table in system managed domain index.

Cause: Outer view query block contains ancillary operator and view query block contains union all.

Cause: An invalid row identifier was returned by the user-defined query methods.

Cause: The specified function does not exist or does not have an appropriate signature.

Cause: The object for which the association is being defined, already has a statistics type associated with it.

Cause: The ODCIStatsCollect / ODCIStatsDelete function is causing an error.

Cause: The keyword DEFAULT SELECTIVITY can only be specified once.

Cause: The scan context is not specified.

Cause: The COMPUTE ANCILLARY DATA option was specified without the WITH INDEX CONTEXT clause.

Cause: One or more of the object(s) that have been specified to be disassociated, do not have an association defined for them.

Cause: Some objects have defined their statistics methods in the type being dropped.

Cause: There are some user defined statistics collected for the object being disassociated.

Cause: The user issued an ASSOCIATE STATISTICS command with an index which is not a domain index.

Cause: The keyword FROM is missing.

Cause: User tried to use the ASSOCIATE command with a schema object other than a column or an index

Cause: An ASSOCIATE STATISTICS command was issued with a domain index which is system-managed.

Cause: Either an ASSOCIATE STATISTICS WITH SYSTEM MANAGED STORAGE TABLES command was issued with an indextype which is not system-managed, or an ASSOCIATE STATISTICS command was issued with an indextype which is system-managed.

Cause: Implicit validation of a user-managed domain index with a system-managed indextype failed.

Cause: An attempt was made to create a local user-managed domain index on an interval-partitioned table.

Cause: An attempt was made to convert a range-partitioned table with local user-managed domain indexes to interval partitioning.

Cause: A warning was returned from the ODCIIndexMergePartition routine.

Cause: A warning was returned from the ODCIIndexSplitPartition routine.

Cause: Tried to issue a DROP/ALTER/TRUNCATE on a domain index partition in a LOADING state.

Cause: Tried to issue a DROP/ALTER on a domain index partition in a FAILED state.

Cause: An attempt has been made to access a domain index that is being built or is marked failed by an unsuccessful DDL or is marked unusable by a DDL operation.

Cause: Failed to successfully execute the ODCIIndexExchangePartition routine.

Cause: A warning was returned from the ODCIIndexExchangePartition routine.

Cause: User specified an unsupported create function-based domain index statement.

Cause: Failed to successfully execute the ODCIIndexCreate routine.

Cause: An error occurred during execution of the routine for one or more of the index partitions

Cause: The ODCIIndex DDL routine has put a warning message into table SYS.ODCI_WARNINGS$

Cause: The number of warnings during the ODCIIndex DDL routine is too high.

Cause: Failed to successfully execute the ODCIIndexAlter routine.

Cause: Keyword BINDING is expected .

Cause: One of the keywords ADD or DROP is expected.

Cause: The binding specified in the DROP BINDING clause is not a valid binding for this operator.

Cause: This operator only has one binding. It cannot be dropped using Alter Operator Drop Binding.

Cause: The operator binding that is being dropped has dependent objects.

Cause: At least one ancillary binding of the specified operator could not be validated because all of its associated primary operator bindings have been dropped.

Cause: An incorrect regid value was passed to dbms_chnf procedure.

Cause: The database could not locate the passed in table name

Cause: User passed in an incorrect or someone else's regid/ handle.

Cause: The user attempted to register an unsupported query type or an unsupported operation like a DML/DDL for change notification.

Cause: None

Cause: User tried to register a query within an uncommitted transction.

Cause: An operator or expression in the query was incompatible with query registration in the guaranteed granularity mode.

Cause: An attempt was made to register a query with an unsupported column type or too many columns.

Cause: None

Cause: An attempt was made to register query result change notification (QRCN) on a table with more than 255 columns.

Cause: A query registration was attempted while there was a a concurrent DDL in progress.

Cause: The user attempted to register a query involving an unsupported table type.

Cause: The query cannot be registered for Continuous Query Notification.

Cause: None

Cause: User is using manual undo management

Cause: Since FROM is specified in TRIM function, either trim specification (TRAILING, HEADING, BOTH) or trim character or both must be specified.

Cause: Trim set contains more or less than 1 character. This is not allowed in TRIM function.

Cause: SYS_CONNECT_BY_PATH function was called at places other than the SELECT list and ORDER BY clause.

Cause: A column value contained the string that the SYS_CONNECT_BY_PATH function was to use to separate column values.

Cause: A non-zero integer must be specified for wait interval (in seconds) after the WAIT keyword.

Cause: The requested resource is busy.

Cause: An attempt was made to use CONNECT BY ROOT operator in the START WITH or in the CONNECT BY condition.

Cause: A CONNECT BY clause did not include a predicate referencing a PRIOR so there was no condition connecting a parent row to its child row.

Cause: The memory size was not sufficient to process all the levels of the hierarchy specified by the query.

Cause: The sort was unable to allocate enough I/O buffers.

Cause: error generated for testing purposes.

Cause: the specified undo tablespace does not exist or of the wrong type.

Cause: the specified undo tablespace is currently used by another instance.

Cause: the operation is only supported in automatic undo mode.

Cause: the current operation is not allowed because an undo tablespace containing active transactions is pending from a previous SWITCH UNDO operation. The operation will be allowed again after all transactions in the previous undo tablespace are committed.

Cause: the specified undo tablespace is currently used by this instance. The operation failed.

Cause: the type of the specified undo segment is incompatible with the current undo management mode of the instance.

Cause: the system runs out of undo segment number. Too many undo segments exist.

Cause: This operation only allowed in Manual Undo mode.

Cause: This operation is not allowed on undo tablespaces

Cause: Cannot create segments in undo tablespace

Cause: Cannot create more than one undo tablespace during database creation

Cause: You have specified an clause that should not used with CREATE UNDO TABLESPACE

Cause: Explicit DROP operation is not allowed on undo tablespace segments

Cause: Tried to drop a tablespace that contains unexpired undo information

Cause: the amount of undo assigned to the consumer group of this session has been exceeded.

Cause: the current instance does not have an active undo tablespace assigned to execute transactions.

Cause: none

Cause: DBA or the user aborted the execution of the suspended statement in the resumable session

Cause: A correctible error was signaled in the resumable session and the error was not cleared within the timeout interval.

Cause: It is incorrect to specify undo tablespace as default user tablespace

Cause: Undo tablespace cannot be specified as default temporary tablespace for the user

Cause: Undo tablespace cannot be specified as default temporary tablespace for the database

Cause: the specified undo tablespace has no more space available.

Cause: Attempt to perform parallel DML after another DML on the same object in the same transaction.

Cause: Attempt to perform parallel insert on a non-partitioned object after a previous DML on the object in the same transaction.

Cause: Cannot drop an undo tablespace that is in use

Cause: Cannot operate on an offlined undo tablespace

Cause: User tried to grant quota on an undo or temporary tablespace

Cause: Cannot offline an undo tablespace that is in use

Cause: the specified undo management mode is invalid

Cause: An attempt was made to specify retention for a non-undo tablespace.

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

Cause: The specified undo tablespace is not present in the control file.

Cause: A VERSIONS clause was specified when it was not allowed.

Cause: The lower limit snapshot expression was below the UNDO_RETENTION limit.

Cause: The upper limit snapshot expression is greater than the SQL statement read snapshot.

Cause: The upper limit snapshot expression is less than the lower limit snapshot expression.

Cause: The snapshot expression is NULL.

Cause: none

Cause: none

Cause: none

Cause: An error occurs during a conversion between datetime/interval and string data type due to one of the following reasons: - The buffer is too short to hold the result. - The format string is bad.

Cause: The value specified for the time zone string, which appears in ALTER SESSION statement, environment variable ORA_SDTZ, or a datetime factor, is not valid.

Cause: The value is none of the followings: 'ADJUST', 'NO_ADJUST', 'ANSI_DATE', 'ADJUST_WITH_ANSI_DATE'. 'NO_ADJUST' is the default value.

Cause: try to GLOBAL partitioned index on TIME/TIMESTAMP WITH TIME ZONE.

Cause: User is trying to create a constraint on a time or timestamp with or without time zone column without explicitly specifying the time zone.

Cause: The extract source does not contain the specified extract field.

Cause: Cannot cast between the specified datetime types.

Cause: An attempt was made to use a time/timestamp expression whose format does not explicitly have time zone on a TIME/TIMESTAMP or TIME/TIMESTAMP WITH TIME ZONE column.

Cause: An attempt was made to alter database timezone with TIMESTAMP WITH LOCAL TIME ZONE column in the database.

Cause: The data types of the operands are not valid for datetime/interval arithmetic.

Cause: datetime/interval column with existing data is being modified to decrease fractional second or leading field precisions.

Cause: A syntax error was found during parsing an interval value value expression.

Cause: When a time zone modifier is specified, the data type of datetime primary must be one of the following: TIME, TIME WITH TIME ZONE, TIMESTAMP, TIMESTAMP WITH TIME ZONE.

Cause: A syntax error was found during parsing an overlaps predicate.

Cause: An attempt was made to specify interval year to month as the result of datetime subtraction.

Cause: An attempt was made to add two datetime values.

Cause: The specified datetime/interval precision was not between 0 and 9.

Cause: A datetime field (YEAR, MONTH, DAY, HOUR, MINUTE, SECOND) is expected but not found, or a datetime field specified the end field in an interval qualifier is more significant than its start field.

Cause: The secondary translation table for DST patching on TSTZ data was not loaded.

Cause: Query included a function that is not allowed in the current state of DST upgrade process.

Cause: Query included a function that is not allowed until the database is restarted.

Cause: There was no corresponding time zone data file in $ORACLE_HOME/oracore/zoneinfo for the input time zone version.

Cause: An internal error has occurred.

Cause: You have misspelled the parameter name.

Cause: The value of the parameter is not within the legal range.

Cause: An illegal integer radix specification was found.

Cause: The value is not a valid integer.

Cause: The value is not a valid boolean.

Cause: None.

Cause: The abbreviation given was not unique.

Cause: An invalid positional parameter value has been entered.

Cause: The parameter file does not exist.

Cause: A syntax error was detected.

Cause: A quoted string was begun but not finished.

Cause: You attempted to specify multiple values for a parameter which can take only one value.

Cause: A problem occurred when processing this file.

Cause: A problem occurred when processing the command line.

Cause: A problem occurred when processing an environment variable.

Cause: A syntax error was detected.

Cause: A syntax error was detected.

Cause: A syntax error was detected.

Cause: No valid value was obtained for this parameter.

Cause: The value is not a valid oracle number.

Cause: The value is not a legal value for this parameter.

Cause: The value of the parameter is not within the legal range.

Cause: A function received an invalid argument

Cause: A function received an invalid parameter key type

Cause: Number of parameter keys being set exceeds allocation

Cause: The key index specified was not within bounds

Cause: None.

Cause: None.

Cause: An OCI Thread function call has failed.

Cause: The current application is statically linked with defopt.o from an older release, which is incompatible with the current client shared library.

Cause: An invalid argument is passed to the OCIFile function. The most common cause is that a NULL pointer is passed where a non-NULL pointer is expected.

Cause: Tried to open a file with OCI_FILE_EXCL flag and the file already exists.

Cause: The OCIFile function requires the file to exist, but it does not.

Cause: An invalid File Object is passed to the OCIFile function.

Cause: An invalid memory address is given as the buffer pointer for OCIFileRead/Write.

Cause: An I/O error occurred at the system level.

Cause: The disks associated with the underlying file system are full.

Cause: The OS call was called with an invalid argument.

Cause: There is no space to write to the file. Its size is at the maximum limit.

Cause: The create flag was specified in OCIFileOpen such that the file was to be created. But unable to do so. Or the file already exists and the permissions on it doesn't allow the file to be opened in in the requested open mode

Cause: The function was unable to access the existing the file.

Cause: A system error occured while executing the OCIFile function.

Cause: The function OCIFileInit need to be called before calling any other OCIFile function to initialize the OCIFile context.

Cause: The call to SlgInit failed in OCIFileInit.

Cause: There is an argument with an invalid type in the argument list.

Cause: There is an invalid format code in the format string.

Cause: There is an invalid flag in a format specification.

Cause: There is a duplicate flag in a format specification.

Cause: Zero or negative argument index or index not following (."

Cause: An argument index exceeds actual number of arguments supplied.

Cause: Missing closing parenthesis in argument index.

Cause: Period in format specification not followed by valid format.

Cause: Invalid field width supplied.

Cause: Bad argument type given for a format code.

Cause: The buffer is not large enough to hold the entire output string.

Cause: In the argument of SQL function UNISTR, a '' must be followed by four hexdecimal characters or another ''

Cause: The client was unauthorized to invoke the procedure DBMS_INTERNAL_CLKM.GET_KEY.

Cause: None.

Cause: None.

Cause: None.

Cause: No argument list supplied.

Cause: Oracle GoldenGate (OGG) AdminService or DistributionService operation failed.

Cause: Internal error. An Oracle GoldenGate (OGG) specific sharding functionality was called in a non-Oracle GoldenGate sharding deployment.

Cause: The values specified for Oracle GoldenGate (OGG) sharding deployment parameters (number of shards, number of chunks, replication factor and distribution factor) were not compatible with each other.

Cause: Internal error. The payload for Oracle GoldenGate (OGG) command sent from the Sharding Catalog to the shard database contained invalid operation code.

Cause: Internal error. A database initialization parameter required by the shard database was not set during deployment.

Cause: None.

Cause: None.

Cause: None.

Cause: The item is not supported NLS item

Cause: It may be caused by invalid NLS environment setting

Cause: The NULL pointer was passed.

Cause: The message may not exist in your system.

Cause: The destination buffer is not large enough for storing converted data.

Cause: The specified character set is invalid.

Cause: A non-existant summary name was specified.

Cause: Another summary is already using this table as a container table.

Cause: The dimension named in a dimension DDL statment does not exist.

Cause: A level name in a dimension ddl statement did not conform to SQL identifier rules.

Cause: The level name specified with the REFERENCES portion of a JOIN KEY clause in a dimension DDL statement does not reference a level in the hierarchy that contains the JOIN KEY clause. *Acction: Check the spelling of the level name.

Cause: The level specified in the REFERENCES portion of a JOIN KEY clause in a dimension DDL statement does not have a child level.

Cause: Multiple JOIN KEY clauses were specified for a given parent level in a dimension hierarchy.

Cause: An illegal dimension hierarchy name was specified in a dimension DDL statement.

Cause: An illegal dimension attribute name was specified in a dimension DDL statement.

Cause: An illegal dimension name was specified in a dimension DDL statement.

Cause: An attempt was made to drop a level using the default or RESTRICT option in a dimension while references to that level remain in the dimension. References can occur in hierarchies and attributes within the dimension.

Cause: A reference to a level not defined within the dimension was found.

Cause: Two or more levels were defined with the same name.

Cause: The number of child columns specified in a JOIN KEY clause is not the same as the number of columns in the specified parent level.

Cause: A circularity was found the dimension hierarchy.

Cause: The same name was used for more than one hierarchy in a dimension.

Cause: A table name was omitted in a column specification where where the column must be qualified by the table name.

Cause: One or more ADD clauses were found in the same ALTER DIMENSION statement with one or more DROP clauses.

Cause: A hierarchy name was encountered that is not defined within the dimension.

Cause: An attribute name was encountered that is not defined within the dimension.

Cause: A complex expression was specified that is is not currently supported by query rewrite.

Cause: The SELECT expression was of a different numeric precision or string length than the corresponding container column. Therefore, query rewrite cannot guarantee results that are identical to the results obtained with the un-rewritten query.

Cause: The SELECT clause referenced UID, USER, ROWNUM, SYSDATE, CURRENT_TIMESTAMP, MAXVALUE, a sequence number, a bind variable, correlation variable, a set result, a trigger return variable, a parallel table queue column, collection iterator, a non-deterministic date format token RR, etc.

Cause: A SYS relation was referenced in the select clause for a materialized view with query rewrite enabled.

Cause: A DROP TABLE command was issued directly against the materialized view container table.

Cause: The refresh method that was specified is not currently supported.

Cause: The statement referenced a PL/SQL function that is not marked DETERMINISTIC.

Cause: An internal Oracle error occured.

Cause: An attempt was made to enable the REWRITE option on a materialized view in the SYS schema.

Cause: The statement contained a REF operator. Repeatable behavior cannot be guaranteed with the REF operator. Therefore, query rewrite cannot support the REF operator.

Cause: An internal Oracle error occured.

Cause: The dimension statement referenced a column that is a sequence.

Cause: The dimension statement contained a column list where the columns are not all from the same relation.

Cause: The level definition contained the same set of columns as another level.

Cause: The relation of the child columns on the left side of the JOIN KEY clause was the same as that of the parent level on the right side.

Cause: The relation of the child columns on the left side of the JOIN KEY clause differed from that of that child level.

Cause: A JOIN KEY clause was omitted in a dimension statement. A JOIN KEY clause is required when the child level and the parent level are not in the same relation.

Cause: An ATTRIBUTE clause in a dimension statement specified a determined column on the right that is in a different relation than that of the level on the left.

Cause: A list of columns was specified using more than 32 columns.

Cause: A set operator such as UNION, UNION ALL, INTERSECT, or MINUS was encountered in an unsupported context, such as in a materialized view definition.

Cause: A column was used in the definition of a level after it had already been used to define a level in a different dimension.

Cause: A fine grain access control procedure has applied a non-null policy to the query for the materialized view.

Cause: An object data type was encountered in an unsupported context.

Cause: If the materialized view is fresh, ORACLE ignores the ALTER MATERIALIZED VIEW mv RELY FRESH command, and issues this error message.

Cause: If the materialized view is invalid or unusable, it cannot be considered fresh with the ALTER MATERIALIZED VIEW mv CONSIDER FRESH command.

Cause: Explain rewrite generates a shared cursor after parsing the user query. Raising this error will prevent the cursor from being shared.

Cause: You have used the DBMS_MVIEW.EXPLAIN_MVIEW() API before you have defined the MV_CAPABILITIES_TABLE.

Cause: One or more column definitions in the MV_CAPABILITIES_TABLE is either missing or incompatible with the current Oracle version.

Cause: You have attempted use DBMS_MVIEW.EXPLAIN_REWRITE() API using an empty query text argument

Cause: You have used the DBMS_MVIEW.EXPLAIN_REWRITE() API before you have created the REWRITE_TABLE.

Cause: One or more column definitions in the REWRITE_TABLE is either missing or incompatible with the current Oracle version.

Cause: The drop materialized view operation got an unexpected error while dropping summary object.

Cause: An attribute level was encountered that is not defined within the attribute.

Cause: A column was encountered that is not defined within the attribute.

Cause: The specified attribute relationship has already been declared in one of the attribute clauses

Cause: Either the source or destination statement is NULL

Cause: The specified rewrite mode is not supported by REWRITE_EQUIVALENCE API

Cause: The name of the rewrite equivalence is NULL

Cause: The SELECT clause of the source statement is not compatible with the SELECT clause of the destination statement

Cause: the set of rows returned by the source SQL text is not the same as the set of rows returned by the destination SQL text

Cause: the specified rewrite equivalence does not exist

Cause: the given checksum does not match with that generated from the source and destination statements.

Cause: A query block with a REWRITE_OR_ERROR hint did not rewrite

Cause: The source statement was identical to the destination statement

Cause: Multiple JOIN KEY clauses were specified for a given child level in a dimension hierarchy.

Cause: A JOIN KEY clause was specified that did not conform to certain requirements. A JOIN KEY clause connecting a child level with its non-immediate ancestor level is allowed only when that child level and its ancestor level satisfy the following conditions: 1. The immediate parent of the child level must be a skip level. 2. The child level cannot be a skip level. 3. The ancestor level must be a non-skip level. 4. The ancestor level must be the nearest non-skip level to the child level in the hierarchy.

Cause: A SKIP clause cannot be specified with a level when all of the columns that make up the level have NOT NULL constraints.

Cause: Two JOIN KEY clauses with identical child keys and parent levels were specified.

Cause: The dimension statement failed because the column(s) in the JOIN KEY clause permitted NULL values. The JOIN KEY columns are related to the columns of the dimension's skip levels in one or both of the following ways: 1. A skip level is defined over one or more of the JOIN KEY columns. 2. The attribute clauses of a skip level determine one or more of the JOIN KEY columns.

Cause: Daylight Saving Time upgrade was in progress on a table in the materialized view.

Cause: The Hive table name was missing.

Cause: The cluster ID or the hive URI (Uniform Resource Identifier) or both were missing.

Cause: The external table was not found.

Cause: There was an attempt to create hive catalog views or a DBMS_HADOOP package on a platform other than Linux x86-64.

Cause: There was an attempt to synchronize an external table with a hive table when external table partitions were identical to the hive table partitions.

Cause: There was an attempt to synchronize an external table with the source hive table with incompatible metadata.

Cause: There was an attempt to create an Oracle external table partition from a Hive table partition with a partition key value identical to that of an existing partition. The Hive table partition key was of type decimal, but the Oracle table partition key was of type NUMBER(10, 0).

Cause: An attempt was made to merge external Hive table partitions with a hybrid Oracle table, whose external partitions are not of the Hive type.

Cause: An attempt was made to merge external Hive table partitions with an already hybrid partitioned Oracle table.

Cause: An attempt was made to merge external Hive table partitions with an unpartitioned or a non-list partitioned Oracle table.

Cause: An attempt was made to merge external Hive table partitions with an Oracle external table.

Cause: An attempt was made to merge an external non-partitioned or empty partitioned Hive table with an Oracle table.

Cause: The EXTERNAL MODIFY clause was used to change the location for an ORACLE_BIGDATA external table.

Cause: A SELECT FOR UPDATE operation on an external partition from a hybrid partitioned table was attempted.

Cause: All identifiers used in the DBMS_OLAP package must have at most 30 characters, and must start with a letter that is followed by any combination of letters, numerals, and the signs '$', '_', and '#'. Other characters cannot be used in identifiers. The rules for DBMS_OLAP identifiers are the same as for PL/SQL identifiers.

Cause: List is empty or does not contain the names of existing summaries

Cause: An invalid refresh method was specified

Cause: The summary is in INVALID state and cannot be refreshed

Cause: There is no such summary, therefore it cannot be refreshed

Cause: An invalid refresh method was specified

Cause: The server must be started with parameter 'job_queue_processes' greater than zero

Cause: The refresh process was unable to open a named pipe to the job queue process usually because of insufficient system resources

Cause: All of the job queue processes used by refresh have stopped for some reason. At least one job queue process must be running in order to refresh summaries.

Cause: The refresh process was unable to access a named pipe to the job queue process after it successfully opened the pipe. This usually indicates an internal or operating system error condition.

Cause: The refresh job queue process encountered an error and is reporting it. The accompanying text of the message indicates cause of the error

Cause: Both DML and direct-load are performed against detail tables. Fast refresh can only process direct-load inserts.

Cause: For the specified filterid parameter, there is no corresponding filter definition found in the advisor repository

Cause: The specified filter is invalid. It contains at least one invalid filter item. If a filter item has a string list, it becomes illegal when the string list cannot be successfully parsed. If the filter item contains a range definition, and the lower bound of the range is greater than the higher bound, the item also becomes invalid.

Cause: The sql analyzer terminates the rewrite process

Cause: No workload queries in the advisor repository can satifiy the specified filter

Cause: None of the specified queries can be successfully parsed. The error may come from many sources: SQL syntax error, the owner specified by the load_workload subprograms do not match the real user who generates the SQL statement

Cause: Users should not explicitly modify summary advisor's internal tables. Such modifications may cause inconsistency in the internal tables and result in this error.

Cause: Users should not explicitly modify summary advisor's internal tables. Such modifications may cause inconsistency in the internal tables and result in this error.

Cause: The syntax for the specified parameter is incorrect

Cause: One or more errors occurred during a refresh of multiple summaries.

Cause: An internal error was detected by the summary refresh subsystem, and aborted the refresh operation

Cause: Incremental refresh of summaries requires a COUNT(X) column in order to incrementally refresh AVG(X). It requires both SUM(X) and COUNT(X) columns in order to in refresh STDDEV(X) or VARIANCE(X)

Cause: Incremental refresh of summaries with AVG(X) requires a COUNT(X) column to be included in the summary definition

Cause: Incremental refresh of summaries with STDDEV(X) requires COUNT(X) and SUM(X) columns to be included in the summary definition

Cause: Incremental refresh of summaries with VARIANCE(X) requires COUNT(X) and SUM(X) columns to be included in the summary definition

Cause: The user lacks one or more permissions that are required in order to refresh summaries.

Cause: The container object for the summary contains one or more unmanaged columns do not allow nulls, and which do not specify a default valur for those columns.

Cause: An attempt was made to incrementally refresh a summary that is not incrementally refreshable.

Cause: An attempt was made to refresh a summary whose refresh method is NONE

Cause: An attempt was made to refresh a summary which is UNUSABLE

Cause: An attempt was made to refresh a summary which is DISABLED

Cause: An attempt was made to refresh a summary containing an unsupported operator

Cause: The list of tables passed to refresh_dependent contains at least one invalid table name. That table is not a detail table of any summary and is therefore an invalid input to refresh_dependent

Cause: A call was made to refresh_all_mviews, but no summaries exist. At least one summary must exist before calling refresh_all_mviews

Cause: There are three possible causes: The specified run_id does not exist; the run_id was created by another user other than the current user; the run_id has already been used.

Cause: The specified workload_id is not valid

Cause: Users should not explicitly modify summary advisor's internal tables. Such modifications may cause inconsistency in the internal tables and result in this error.

Cause: The specified feature is not enabled.

Cause: Estimate_Summary_Size uses Oracle SQL "EXPLAIN PLAN" command to estimate cardinality of the specified select-clause. This requires a table called the PLAN_TABLE in the user's schema. For more information refer to the SQL Reference Manual.

Cause: The input select-clause parameter to Estimate_Summary_Size is incorrectly specified and cannot be compiled.

Cause: the specified dimension to be verified does not exist

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

Cause: Window functions are allowed only in the SELECT list of a query. And, window function cannot be an argument to another window or group function.

Cause: All window functions should be followed by window specification, like function(argument list) OVER (window specification)

Cause: Either the ORDER BY expression is mandatory for this function, or there is an aggregation group without any ORDER by expression.

Cause: If the window specification is specified using RANGE option and there are multiple ORDER BY expressions, then the aggregation group cannot contain any expression (It can only have CURRENT ROW, UNBOUNDED PRECEDING, or UNBOUNDED FOLLOWING). First end point (bound) cannot be UNBOUNDED FOLLOWING and second end point cannot be UNBOUNDED PRECEDING. If the first end point is CURRENT ROW, then second end point can only be CURRENT ROW or expr /UNBOUNDED FOLLOWING. If the first end point is expr FOLLOWING, then second end point can only be expr/UNBOUNDED FOLLOWING.

Cause: DISTINCT functions and RATIO_TO_REPORT cannot have an ORDER BY

Cause: The argument of the window function should be a constant for a partition.

Cause: GROUP BY clause has more than one rollup/cube expression list.

Cause: An expression in the GROUP BY ROLLUP or CUBE list matches an expression in the ordinary GROUP BY expression list

Cause: A percentile value for PERCENTILE_CONT or PERCENTILE_DISC function is specified out of range.

Cause: An attempt was made to create a trigger that fires before the database is open or before server errors, but these types of triggers are not supported.

Cause: An attempt was made to create a trigger that fires after an instance shutdown, but this type of trigger is not supported.

Cause: An attempt was made to create a system trigger with INSERT, UPDATE, or DELETE triggering events, but this type of trigger is not supported because a system trigger does not have a base table.

Cause: An attempt was made to use a REFERENCING clause with a system trigger, but this type of trigger is not supported because a system triggers does not have a base table.

Cause: An attempt was made to use a FOR EACH ROW clause with a system trigger, but this type of trigger is not supported because a system triggers does not have a base table.

Cause: An attempt was made to use a WHEN clause to reference a column with a system trigger, but this type of trigger is not supported because a system trigger does not have a base table.

Cause: An attempt was made to base a system trigger on a table or a view.

Cause: An attempt was made to base a normal trigger on a schema, a database, or a pluggable database, but normal triggers can be based only on tables or views.

Cause: An attempt was made to create a trigger that fires before logon. This type of trigger is not supported.

Cause: An attempt was made to create a trigger that fires after logoff. This type of trigger is not supported.

Cause: An attempt was made to define a system trigger on the schema of SYS user. This type of trigger is not supported currently.

Cause: An attempt was made to perform an invalid DDL operation in a system trigger. Most DDL operations currently are not supported in system triggers. The only currently supported DDL operations are table operations, pluggable database operations, ALTER COMPILE operations, and ALTER SESSION operations.

Cause: An attempt was made to modify an object more than once in a transaction. This error is usually caused by a DDL statement that fires a system trigger that tries to modify the same object. It can also happen when an attempt is made to perform more than one DDL operation on a queue table in the same transaction without issuing a commit between operations.

Cause: Only BEFORE or AFTER triggers can be created on system events.

Cause: A beofre trigger tries to modify a tablespace which is being made READ ONLY as the part of DDL oepration

Cause: An attempt was made to create a trigger that fires before execution suspended. This type of trigger is not supported.

Cause: An attempt was made to create a trigger that fires before the role change completed. This type of trigger is not supported.

Cause: the functional indexes depends on some invalid/non-existent package/function spec/body

Cause: the functional indexes depends on a package/type body which does not exist

Cause: The package/procedure/function is deterministic and some object depends on it

Cause: The function on which the index is defined is not deterministic

Cause: An attempt was made to access a function-based index that has been marked disabled because the function on which the index depends has been changed.

Cause: An attempt was made to use an expression as a partitioning key in an index.

Cause: An ALTER TABLE MODIFY COLUMN was issued on a column on which either a functional index or bitmap join index exists.

Cause: The user updated a column on which a function based index is present which was not successfully updated

Cause: This is an internal error.

Cause: An attempt was made to reference (+) in either the select-list, CONNECT BY clause, START WITH clause, or ORDER BY clause.

Cause: The clause INVALIDATE or UPDATE GLOBAL INDEXES is allowed only for ADD partition to a HASH partitioned table or ADD subpartition to a composite partitioned table.

Cause: The clause INVALIDATE or UPDATE GLOBAL INDEXES was specified more than once.

Cause: The clause INVALIDATE or UPDATE GLOBAL INDEXES is not allowed for this command

Cause: The specified log group name has to be unique.

Cause: The <log_group_name> specified in alter table drop log group is incorrect or nonexistent.

Cause: An attempt was made to include a column in a log group with one of these unsupported data types: LONG, VARRAY, nested table, object, or LOB.

Cause: In CREATE TABLESPACE, the SEGMENT SPACE MANAGEMENT option was specified more than once.

Cause: An invalid option appears for SEGMENT SPACE MANAGEMENT clause.

Cause: in CREATE TABLESPACE, the AUTO SEGMENT SPACE MANAGEMENT was used with a DICTIONARY extent management clause.

Cause: in CREATE TABLESPACE, the AUTO SEGMENT SPACE MANAGEMENT was used while creating an UNDO or TEMPORARY tablespace.

Cause: A rollback segment is being created in a tablespace that was created with AUTO segment space management.

Cause: Oracle executable doesn't have ConText Option linked in

Cause: ConText dictionary tables may be corrupted

Cause: A member method of a type is being invoked with a NULL SELF argument.

Cause: Reject limit specifies the number of records rejected before terminating a table scan. The range is a either a number between 1..100000 or UNLIMITED if no limit is intended.

Cause: A schema other then SYS was specified for the TYPE

Cause: An error occurred when fetching the access parameters for the specified external or hybrid-partitioned table.

Cause: DEFAULT DIRECTORY clause missing or incorrect.

Cause: the reject limit has been reached.

Cause: DEFAULT DIRECTORY clause not specified or incorrect.

Cause: A select for update on an external table was attempted.

Cause: An attempt was made to create an external-organized table or hybrid-partitioned table with a column of type LONG, LOB, BFILE, ADT, or VARRAY.

Cause: User attempted on operation on an external table which is not supported.

Cause: An attempt was made to create an External Organized Temporary table. This is not supported.

Cause: An attempt was made to create or query an external-organized or hybrid-partitioned table with more than the maximum allowed (32767) locations specified.

Cause: A NULL entry was detected in the column with a NOT NULL constraint during a fetch from an external or hybrid-partitioned table.

Cause: An EXTERNAL MODIFY clause was specified when querying a table that was not an external or hybrid-partitioned table.

Cause: A requested column was not found in the projected column list.

Cause: A NOT NULL constraint was not specified correctly on a DEFAULT ON NULL column.

Cause: The NOT NULL constraint on a DEFAULT ON NULL column could not be modified.

Cause: The NOT NULL constraint on a DEFAULT ON NULL column could not be dropped.

Cause: An attempt was made to follow the CROSS APPLY or OUTER APPLY keyword with the LATERAL keyword.

Cause: An attempt was made to specify more than one identity column on a table.

Cause: A NOT NULL constraint was not specified correctly on an identity column.

Cause: The NOT NULL constraint on an identity column could not be modified.

Cause: The NOT NULL constraint on an identity column could not be dropped.

Cause: An attempt was made to modify the identity properties of that is not an identity column.

Cause: An attempt was made to add a default value to an identity column.

Cause: An attempt was made to create or alter an identity column with a non-numeric data type.

Cause: A problem kept a socket from reading or writing the expected amount of data. More specific information is not available.

Cause: An attempt to connect a session to a debugger could not proceed because the session is already connected to some debugger.

Cause: An attempt to open a connection failed because too many are already open by this session. The number of allowed connections varies as some may be in use through other components which share the same pool of allowed connections.

Cause: An attempt to open a debugging connection failed because this server configuration cannot support the required asynchronous socket traffic detection.

Cause: A problem occurred when trying to establish a debugger connection. This might indicate that the port specified as the location of the debugger is actually being used by some other type of application.

Cause: An improper parameter value was provided in a call to DBMS_DEBUG_JDWP.CONNECT_TCP.

Cause: An improper parameter value was provided in a call to DBMS_DEBUG_JDWP.CONNECT_TCP.

Cause: An error was indicated when trying to establish a connection to a debugger. Usually a TNS error will display along with this message to further explain the problem, although this TNS error will likely be hidden if you choose to trap the error.

Cause: The request was not processed within the given time.

Cause: The installed version of the package from which this error is raised is not compatible with this release of Oracle.

Cause: A connection had to be routed through a local socket rather than a dispatcher. When this occurs, shared servers are less beneficial because the session that owns the socket cannot relinquish the process until the socket is closed. The most likely cause is that no dispatcher is configured for protocol=tcp.

Cause: The execution of the session was stopped by the debugger. This can occur because of an explicit request sent by the debugger, or because the debugger disconnected without requesting the ORACLE server to let the session continue to run after the disconnection. It can also occur if the ORACLE server needs to disconnect the debugger at a time when the person controlling the debugger might not expect, such as upon a reset of the related package state or a change of the login user. To prevent continuing the execution using debugger-introduced modifications that might have been intended to be temporary, the ORACLE server needs to fully terminate the session.

Cause: Your program contains a set of calls that are too deep to be handled. Only transitions between the different execution engines (SQL, PL/SQL, and Java) count in reaching this limit; calls within the same engine don't count.

Cause: An improper value was used for ORA_DEBUG_JDWP when trying to establish a connection to a debugger. The value either did not conform to the format of ORA_DEBUG_JDWP or was too long.

Cause: A timeout occurred while registering a TCP/IP connection for data traffic detection.

Cause: System resources ran out while registering a TCP/IP connection for data traffic detection.

Cause: A message passed from one software subcomponent to another using the JDWP protocol appears invalidly formatted.

Cause: The request was aborted by the target session. Possible causes include an unresolved error while the request was processed or the target session had aborted.

Cause: This feature is not yet available for use.

Cause: An attempt was made to specify a referenced column list for a referential constraint involving a REF column.

Cause: Multiple referential constraints were specified for a single REF column.

Cause: Adding referential constraint on a REF column requires the the creation of an additional column.

Cause: Adding scope or referential constraint on a REF column requires the creation of additional columns if the target table's object identifier is primary key based.

Cause: An attempt was made to define a referential constraint on a nested table column.

Cause: An attempt was made to define a scope constraint on a nested table column when the nested table is being created.

Cause: An attempt was made to query on a system table which has no user-visible columns.

Cause: An attempt was made to specify rowid constraint on a scoped REF column.

Cause: An attempt was made to specify scope constraint on a REF column with the rowid constraint.

Cause: An attempt was made to create under a supertable (superview), a subtable(subview) of the same type as another existing subtable (subview).

Cause: An attempt was made to create a subtable(subview) under a supertable(superview) located in another schema.

Cause: An attempt was made to create a subtable(subview) of a type which is not a subtype of the type of the super object.

Cause: The specified object does not exist.

Cause: The user tried to drop a table that has subtables defined under it.

Cause: The user tried to grant UNDER privilege on an object that is not one of the following : non final object type, object table of non final type, object view of non final type.

Cause: An attempt was made to specify WITH HIERARCHY OPTION for a privilege other than SELECT or READ.

Cause: An attempt was made to grant the SELECT or READ privilege when the WITH HIERARCHY OPTION was specified on an object that is not one of the following: - Object table of non-final type - Object view of non-final type

Cause: The specified object is not an object view.

Cause: The specified object is not an object table.

Cause: The user tried to add a subtype which tried to alter the tables dependent on the supertype.

Cause: The user tried to drop a subtype with VALIDATE option which tried to check for stored instances of the type in the stated table

Cause: The user tried to create substitutable table or column of a non final type. This operation is not currently supported.

Cause: The user is trying to enable a column to store instances of a type for which it is already enabled.

Cause: The user is trying to disable a column from storing instances of a type for which it is already enabled.

Cause: The user is trying to enable a column to store instances of a subtype. The error is raised due to one of the following :

Cause: The user is trying to drop a type from being stored in a substitutable column or table. This error is raised due to one of the following reasons : - the column is enabled to store instances of some subtype of the type being dropped. - the column is enabled to store instances of only one type

Cause: The user is performing an operation that is not allowed on non substitutable column or table.

Cause: The user is performing an operation that is not allowed on substitutable column or table.

Cause: The user is trying to perform an operation that is not allowed on object column or table that is enabled to store instances of a single type.

Cause: There was an error while trying to expand a view hierarchy. This could be due to invalid subviews (or subviews with errors)

Cause: The user tried to create a column or table of an object type that contains a supertype attribute. This is not supported because it leads to infinite recursion in our current storage model. Note that creating a column of a type implies that we create columns corresponding to all subtype attributes as well.

Cause: Either a subtype was created and operations performed with this new type while the session was in progress, or the type information was unpinned from the object cache.

Cause: The user specified local or global for a nested table storage parameter while the base table is non-partitioned.

Cause: The user specifed local or nested table parameters inside partition clause for a composite partitioned table.

Cause: An attempt was made to drop a system-generated hidden object column

Cause: An attempt was made to modify the scope for an unscoped REF column.

Cause: An attempt was made to modify the scope for a REF column with a REFERENCES constraint.

Cause: An attempt was made to modify the scope for a REF column to a table whose object identifier's type is different from that of the original scoped table.

Cause: Pipelined functions can only be used in a TABLE expression in the from clause.

Cause: Storage clause was specified during table creation for a fixed size opaque type.

Cause: Multiple referential constraints were specified for a single REF column.

Cause: Constructor invocation did not succeed, since no user-defined constructors were defined for the opaque type, and since opaque types do not have default constructors.

Cause: Constructor invocation did not succeed, since no user-defined constructors were defined for the opaque type, and since opaque types do not have default constructors.

Cause: User has defined some library as trusted library for opaque types.

Cause: A stable set of rows could not be got because of large dml activity or a non-deterministic where clause.

Cause: In memory temporary tables we create are aged out of shared pool before we are able to grab them again.

Cause: It is probably caused by the fact that there is a loop in the data.

Cause: ORDER SIBLINGS BY clause is specifed in a query which doesn't have CONNECT BY clause.

Cause: CONNECT_BY_ISCYCLE was specifed in a query which does not have the NOCYCLE keyword.

Cause: XML elements must be declared mixed to contain multiple text nodes

Cause: When using a reference node, it must have the specified parent node

Cause: The ordering specified by the content model of the parent does not allow for this element to occur at this position.

Cause: The schema does not allow a child node of this type to be inserted into a parent node of this type. For example, only element nodes may only be inserted into a document

Cause: An attempt was made to insert more than maxoccurs values into a schema-based XML document.

Cause: An attempt was made to insert more than the allowed number of elements (specified by the maxoccurs facet) into an XML document.

Cause: The schema definition for the parent node being processed does not allow for the specified child node in its content model. Note that any typecasting via xsi:type must occur before the schema definitions for the new type can be used.

Cause: An XML namespace mapping (xmlns:prefix=namespace URL) must be defined for each particle (element or attribute) stored in an schema-constrained XMLType document.

Cause: The XML schema specifies a content model that is sequential, where the order of nodes in the instance must follow the order specified by the schema, and this instance relies on the schema validity to avoid maintaining instance order information

Cause: An attempt was made to store a QName value without having a valid namespace in scope for that prefix.

Cause: An attempt was made to insert a namespace declaration for a non-default namespace using an empty URI string.

Cause: The given XMLType table/column which conforms to the given schema had errors during evolution. For more information, see the more specific error below this one

Cause: Not all dependent schemas were specified and/or the schemas were not specified in dependency order, i.e., if schema S1 is dependent on schema S, S must appear before S1.

Cause: The given XMLType table/column which conforms to the given schema had errors during a rollback of XML schema evolution. For more information, see the more specific error below this one

Cause: A mapping table could not be created during XML schema evolution. For more information, see the more specific error below this one

Cause: An error occurred after the schema was evolved while cleaning up temporary tables. The schema evolution was successful

Cause: An XMLType table that is dependent on an XML schema being evolved is version-enabled.

Cause: An attempt was made to make an XML schema change that is not permitted through in-place XML schema evolution.

Cause: An attempt was made to insert a node of length exceeding the maximum length (specified by the maxLength facet) into an XML document.

Cause: An attempt was made to update xdbconfig.xml when either 1) a value was specified for http2-port but not for http2-protocol (or vice versa), OR 2) http-port and http2-port were set to the same value.

Cause: An attempt was made to delete more than the required minimum number of elements (specified by the minoccurs facet) from an XML document.

Cause: An invalid XML character was found.

Cause: An attempt was made to synchronize a nonexistent XML Index or a synchronous XML Index.

Cause: Unexpected error.

Cause: An attempt was made to downgrade a database that has XML indexes.

Cause: An illegal operation was attempted on secondary objects of an XML Index.

Cause: An attempt was made to create an XML Index on an OR-XMLType column.

Cause: The given string had invalid syntax.

Cause: unexpected internal error

Cause: unexpected internal error

Cause: An attempt was made to create an XML Index on a non-XMLType column.

Cause: The domain index for XML was not created properly. The Path Table is missing.

Cause: The fragment size exceeded the max size.

Cause: Unexpected error.

Cause: illegal operation on secondary objects of a domain index

Cause: An attempt was made to use an unsupported option.

Cause: An attempt was made to specify an invalid option.

Cause: An attempt was made to specify an invalid option.

Cause: An attempt was made to use an unsupported option.

Cause: An attempt was made to use an unsupported option.

Cause: An attempt was made to use an unsupported option.

Cause: An attempt was made to use an unsupported option.

Cause: An attempt was made to use an unsupported option.

Cause: An attempt was made to use an unsupported option.

Cause: An attempt was made to use an unsupported option.

Cause: An attempt was made to create a global partitioned XML Index.

Cause: An attempt was made to create a partitioned XML Index.

Cause: The input to the function is not valid.

Cause: An invalid option was specified at the partition level.

Cause: The document could not be indexed because its nesting depth was more than that allowed by XML Index.

Cause: The XMLType column was not declared as virtual when creating a structured XMLIndex.

Cause: The virtual XMLType column for chaining was missing when creating a structured XML index.

Cause: An attempt was made to create an XML Index with more than one virtual column.

Cause: An attempt was made to operate on a non-existent XML Index on XML DB repository.

Cause: An attempt to locate the XML Index failed.

Cause: XML Index supported only on Heap Organized Table.

Cause: An attempt was made to change the Owner field of an XML DB resource without sufficient privileges to do so.

Cause: An attempt was made to add or remove an xsi:schemaLocation, xsi:noNamespaceSchemaLocation, xsi:type, or xsi:nil attribute to or from a schema-based XML node using DOM.

Cause: Either a null or a nonleaf node was passed.