68 ORA-02100 to ORA-04099

Cause: An identifier does not follow ALTER TABLESPACE.

Cause: An option other than NORMAL or IMMEDIATE follows OFFLINE.

Cause: A valid option was not present.

Cause: An option other than INITIAL, NEXT, MINEXTENTS, MAXEXTENTS, or PCTINCREASE was specified in the STORAGE clause.

Cause: No ALTER CLUSTER options are specified.

Cause: No STORAGE options were specified following STORAGE (

Cause: The SHARED option was specified in a CREATE DATABASE statement multiple times.

Cause: Both the SHARED and EXCLUSIVE options were specified in a CREATE DATABASE statement.

Cause: The EXCLUSIVE option was specified in a CREATE DATABASE statement multiple times.

Cause: Partition not found for the object.

Cause: The new tablespace name specified in ALTER TABLESPACE RENAME TO statement was invalid.

Cause: Oracle cannot create a tablespace whose name starts with '_$deleted$'.

Cause: An option other than DATAFILE or TO follows by ALTER TABLESPACE ... RENAME.

Cause: An encoded password string does not follow the VALUES clause.

Cause: An attempt to rename a tablespace to a new name failed because the new name is already used by some other tablespace.

Cause: An identifier does not follow DEFAULT TABLESPACE.

Cause: An identifier does not follow TEMPORARY TABLESPACE.

Cause: No options were specified.

Cause: An option other than COMPRESS, NOCOMPRESS, PCTFREE, INITRANS, MAXTRANS, STORAGE, TABLESPACE, PARALLEL, NOPARALLEL, RECOVERABLE, UNRECOVERABLE, LOGGING, NOLOGGING, LOCAL, or GLOBAL was specified.

Cause: The parameter file specified gc_* parameters that allow locks to be release by the LCK process when not in use. This mode requires additional support from the DLM that is not available.

Cause: A column of type LONG defined for index-organized table.

Cause: A number does not follow MAXLOGFILES.

Cause: A number does not follow MAXDATAFILES.

Cause: A number does not follow FREELIST GROUPS.

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

Cause: An invalid CREATE DATABASE option is present.

Cause: Both ARCHIVELOG and NOARCHIVELOG are specified in a CREATE DATABASE statement.

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

Cause: A number does not follow FREELISTS

Cause: The user attempted to specify the FREELISTS storage option. This option may only be specified during create table or create index.

Cause: The user attempted to specify the FREELIST GROUPS storage option. This option may only be specified during create table and when allow_freelist_groups INIT.ORA is specified.

Cause: A number does not follow MAXLOGHISTORY

Cause: The PUBLIC keyword was specified for a disable.

Cause: Either a token other than INCLUDING was found following the tablespace name or some text was found following INCLUDING CONTENTS.

Cause: Must specify thread number after THREAD keyword

Cause: In the CREATE or DROP ROLLBACK SEGMENT statements, an identifier was not found following ROLLBACK SEGMENT.

Cause: An invalid option was specified in a CREATE ROLLBACK SEGMENT statement.

Cause: Must specify group number after GROUP keyword

Cause: There is a syntax error in the user's statement.

Cause: There is a syntax error in the user's statement.

Cause: An invalid option appeared.

Cause: A token other than TO follows ROLLBACK [WORK].

Cause: An identifier does not follow ROLLBACK [WORK] TO [SAVEPOINT].

Cause: There is a syntax error in the user's statement.

Cause: In a revoke statement, a resource quota was specified.

Cause: A token other than WORK follows COMMIT.

Cause: An attempt was made to grant or revoke a resource quota in the same statement in which other privileges are granted or revoked.

Cause: The user attempted to grant a tablespace quota above the upper limit.

Cause: An attempt was made to publicly enable a thread associated with an instance.

Cause: In a grant or revoke statement, the user specified a tablespace quota but did not follow it with the ON tablespace clause.

Cause: The keyword TABLES is expected following DROP CLUSTER name INCLUDING.

Cause: There is a syntax error in the user's statement.

Cause: pctincrease was specified in a create or alter rollback segment

Cause: There is a syntax error in an event specification.

Cause: The object type is inconsistent with a tablespace contents.

Cause: In CREATE TABLESPACE, the PERMANENT and/or TEMPORARY options were specified more than once.

Cause: In CREATE TABLESPACE, more than one DATAFILE/TEMPFILE clause was specified.

Cause: In CREATE TABLESPACE, the ONLINE and/or OFFLINE options were specified more than once.

Cause: A CREATE TABLESPACE statement has no DATAFILE/TEMPFILE clause.

Cause: An attempt was made to GRANT to PUBLIC WITH GRANT OPTION.

Cause: An attempt was made to reference a sequence in a from-list.

Cause: An attempt was made to create a table in a cluster which already contains 32 tables.

Cause: The user attempted to alter the INITIAL storage option of a table, cluster, index, or rollback segment. These options may only be specified when the object is created.

Cause: An attempt was made to grant or revoke an invalid privilege on a view.

Cause: An attempt was made to grant or revoke an invalid privilege on a sequence.

Cause: INITRANS is specified more than once.

Cause: The INITRANS value is not an integer between 1 and 255 and less than or equal to the MAXTRANS value.

Cause: MAXTRANS is specified more than once.

Cause: The MAXTRANS value is not an integer between 1 and 255 and greater than or equal to the INITRANS value.

Cause: No ALTER TABLE option was specified.

Cause: The specified value for PCTFREE or PCTUSED is not an integer between 0 and 100.

Cause: PCTFREE option specified more than once.

Cause: PCTUSED option specified more than once.

Cause: The BACKUP option to ALTER TABLE is specified more than once.

Cause: There is more than one TABLESPACE clause in the CREATE TABLE, CREATE INDEX, or CREATE ROLLBACK SEGMENT statement.

Cause: A tablespace name was not present where required by the syntax for the failing statement.

Cause: A storage option (INIITAL, NEXT, MINEXTENTS, MAXEXTENTS, PCTINCREASE) is specified more than once.

Cause: The specified value must be an integer.

Cause: The specified value must be an integer.

Cause: The specified value must be a positive integer less than or equal to MAXEXTENTS.

Cause: The specified value must be a positive integer greater than or equal to MINEXTENTS.

Cause: The specified value must be a positive integer.

Cause: The specified value must be an integer.

Cause: An attempt was made to grant or revoke an invalid privilege on a table.

Cause: An attempt was made to grant or revoke an invalid privilege on a procedure, function or package.

Cause: The MAXEXTENTS specified is too large for the database block size. This applies only to SYSTEM rollback segment.

Cause: A cluster name of the form [ identifier . ] identifier is expected but not present.

Cause: The SIZE option is specified more than once.

Cause: The specified value must be an integer number of bytes.

Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, or SIZE is specified in an ALTER CLUSTER statement.

Cause: An option other than ADD, DROP, RENAME, ARCHIVELOG, NOARCHIVELOG, MOUNT, DISMOUNT, OPEN, or CLOSE is specified in the statement.

Cause: A mode other than SHARED or EXCLUSIVE follows the MOUNT keyword in an ALTER DATABASE statement.

Cause: A mode other than NORMAL or IMMEDIATE follows the CLOSE keyword in an ALTER DATABASE statement.

Cause: the log table to be added is a duplicate of another

Cause: the table to be altered is already a change log for another table

Cause: A character string literal was not used in the filename list of a LOGFILE, DATAFILE, or RENAME clause.

Cause: A non-integer value was specified in the SIZE or RESIZE clause.

Cause: In a RENAME clause in ALTER DATABASE or TABLESPACE, the the number of existing filenames does not equal the number of new filenames.

Cause: the sequence to be dropped is still referenced

Cause: A number does not follow either OBJNO or TABNO.

Cause: bad extent storage clause

Cause: No options specified.

Cause: An option other than INITRANS, MAXTRANS,or STORAGE is specified in an ALTER INDEX statement or in the USING INDEX clause of an ALTER MATERIALIZED VIEW statement.

Cause: The STORAGE option is expected but not found.

Cause: An identifier was expected, but not found, following ALTER [PUBLIC] ROLLBACK SEGMENT.

Cause: A character string literal was expected, but not found, following ALTER SESSION SET EVENTS.

Cause: The option SET EVENTS was expected, but not found, following ALTER SESSION.

Cause: Obvious.

Cause: A valid number does not follow MAXLOGMEMBERS. The value specified must be between 1 and the port-specific maximum number of log file members.

Cause: The constraint name is missing or invalid.

Cause: Subquery is not allowed here in the statement.

Cause: The specified search condition for the check constraint is not properly ended.

Cause: Constraint specification is not allowed here in the statement.

Cause: Default value expression is not allowed for the column here in the statement.

Cause: Was that defaults must not conflict with not null constraints

Cause: The number of columns in the foreign-key referencing list is not equal to the number of columns in the referenced list.

Cause: The number of columns in the key list exceeds the maximum number.

Cause: Self-evident.

Cause: Self-evident.

Cause: Self-evident.

Cause: Self-evident.

Cause: New column datatype causes type-checking error for existing column default value expression.

Cause: The required datatype for the column is missing.

Cause: The specified constraint name has to be unique.

Cause: The datatype of the referenced column is not defined as yet.

Cause: An attempt was made to truncate a table with unique or primary keys referenced by foreign keys enabled in another table. Other operations not allowed are dropping/truncating a partition of a partitioned table or an ALTER TABLE EXCHANGE PARTITION.

Cause: The data type or collation of the referencing column was incompatible with the data type or collation of the referenced column.

Cause: The referenced table does not have a primary key.

Cause: Self-evident.

Cause: A REFERENCES clause in a CREATE/ALTER TABLE statement gives a column-list for which there is no matching unique or primary key constraint in the referenced table.

Cause: Self-evident.

Cause: Self-evident.

Cause: Self-evident.

Cause: Self-evident.

Cause: Self-evident.

Cause: The type of the evaluated default expression is incompatible with the datatype of the column.

Cause: The specified sequence name is not a valid identifier name.

Cause: Self-evident.

Cause: Self-evident.

Cause: Self-evident.

Cause: Self-evident.

Cause: Self-evident.

Cause: Self-evident.

Cause: Self-evident.

Cause: Self-evident.

Cause: Self-evident.

Cause: The specified sequence number (CURRVAL or NEXTVAL) is inappropriate here in the statement.

Cause: A token other than RESETLOGS appears following ALTER DATABASE name OPEN.

Cause: The specified sequence does not exist, or the user does not have the required privilege to perform this operation.

Cause: The values being inserted do not satisfy the named check constraint.

Cause: A foreign key value has no matching primary key value.

Cause: attempted to delete a parent key value that had a foreign key dependency.

Cause: an alter table operation tried to validate a check constraint to a populated table that had nocomplying values.

Cause: While one DDL statement was attempting to enable this constraint, another DDL changed this same constraint.

Cause: a create or alter table specified more than one enable and/or disable clause for a given constraint.

Cause: an alter table enable constraint failed because the table contains values that do not satisfy the constraint.

Cause: an alter table disable constraint failed becuase the table has foriegn keys that are dpendent on this constraint.

Cause: an alter table validating constraint failed because the table has orphaned child records.

Cause: an alter table validating constraint failed because the table has duplicate key values.

Cause: A number was not specified for the value of OIDGENERATORS.

Cause: A number greater than 255 was specified for the value of OIDGENERATORS.

Cause: An invalid or missing type name was entered in a statement.

Cause: An attempt was made to drop or replace a type that has type or table dependents.

Cause: An attempt was made to enter an object identifier literal for CREATE TYPE that is either: - not a string of 32 hexadecimal characters - an object identifier that already identifies an existing object - an object identifier different from the original object identifier already assigned to the type

Cause: An attempt was made to GRANT or REVOKE an invalid privilege (not EXECUTE, DEBUG, or UNDER) on a type.

Cause: An attempt was made to create a type that already has some valid dependent(s) (these dependents depend on the fact that the type does not exist).

Cause: An attempt was made to ALTER with REPLACE option a type that is not valid.

Cause: An attempt was made to specify an invalid option, such as PACKED or UNPACKED, for the object type column.

Cause: An attempt was made to acess the attributes of a NULL object instance.

Cause: The attributes in the object type column exceeded the maximum number of columns allowed in a table.

Cause: An attempt was made to ALTER with COMPILE option a type that is valid and has type or table dependents.

Cause: The specified object type contains a nested attribute whose type is non-queryable.

Cause: The statement contains an illegal use of a type constructor.

Cause: The number of arguments specified for the default constructor doesn't match the number of attributes of the object type.

Cause: An error occurred while creating the storage table for the specified nested table column.

Cause: An error occured while performing DML on the storage table of the nested table column.

Cause: More than one column was selected in the THE subquery.

Cause: An attempt was made to create an index on a non-indexable expression.

Cause: An attempt was made to place a UNIQUE or a PRIMARY KEY constraint on a column of datatype VARRAY, nested table, object, LOB, FILE or REF.

Cause: An attempt was made to specify the data type in the column constraint specification of an object table.

Cause: An attempt was made to create a constraint on a column posessing a non-constrainable datatype -- VARRAY, nested table, object, LOB, FILE, or REF.

Cause: An attempt was made to create an index on an attributes of an object type column.

Cause: An attempt was made to create a constraint on an attribute of an object type column.

Cause: A datatype was not declared for this column (in the CREATE TABLE) and an attempt was made to create a constraint on an attribute of this column.

Cause: An attempt was made to declare a CLUSTER column of datatype object, REF, nested table, VARRAY, LOB, or FILE.

Cause: An attempt was made to extract an attribute of an object type column.

Cause: An attempt was made to use dotted notation on a non-ADT column; that is, "a.b.c" where "a" is not an object type.

Cause: A column constraint was not specified.

Cause: An attempt was made to specify the PACKED or UNPACKED keyword for a non-object type column.

Cause: An attempt was made to specify an UNPACKED column within a packed table.

Cause: The use of the ALTER...REPLACE statement on a valid type caused a compilation error.

Cause: An attempt was made to revoke execute on a type that has dependents.

Cause: A CURSOR operator was used as one of the SELECT elements in the subquery of a CREATE VIEW or CREATE TABLE ... AS SELECT statement.

Cause: An attempt was made to grant privileges on the columns of an object table.

Cause: An attempt was made to create a column of a VARRAY type which has an embedded LOB attribute. The LOB could be an attribute of a subtype of the declared type of VARRAY's element.

Cause: An attempt was made to use an incomplete type definition as a column or table datatype.

Cause: An unexpected error condition was detected.

Cause: An OCI error has occurred.

Cause: An OCI error has occurred.

Cause: An error has occurred in a stream export or import operation. This message will be followed by another message giving more details about this error.

Cause: An attempt to open the specified file for data export/import failed.

Cause: The load was discontinued due to space exhaustion in the database.

Cause: The header may be corrupted.

Cause: An error has occurred in a stream export or import operation.

Cause: The specified file could not be used for this load because its database version was not compatible with the database version in the other files in the DUMPFILE clause.

Cause: An unexpected error occurred during initialization for data export/import.

Cause: An error occurred while trying to allocate memory. This is likely caused by insufficient memory.

Cause: An attempt to close the specified file for data export/import failed.

Cause: An attempt to read from the specified file for data export/import failed.

Cause: An attempt to write to the specified file for data export or import failed.

Cause: An attempt to seek to the specified position in file failed.

Cause: The table had some indexes which were loaded if there were no errors.

Cause: A truncated or incomplete file was used for the load operation.

Cause: A file could not be used for this load. See the following message for more information.

Cause: The specified file could not be used for this load because the internal number in the header was not valid.

Cause: The specified file could not be used for this load because the internal metadata stored in this file does not match the metadata stored in the first file piece set.

Cause: The loader being used is incompatible with this version of the kernel.

Cause: A conversion error occurred while loading data into a table. The message shows values for the field in the row that had the conversion error.

Cause: self-evident.

Cause: A row could not be loaded into the table because there was a conversion error for one or more columns in a row.

Cause: A row could not be loaded into the table because there was a conversion error for one or more columns in a row.

Cause: a create, or alter profile command which names a resource not yet defined, or try to specify same resource twice.

Cause: A value of 0 or lower was specified for the limit.

Cause: Try to create a profile which already exist

Cause: Try to assign a user to a non-existant profile

Cause: Try to drop PUBLIC_DEFAULT profile

Cause: Negative or UNLIMITED cost for this resourc

Cause: An attempt was made to exceed the maximum number of concurrent sessions allowed by the SESSION_PER_USER clause of the user profile.

Cause: as stated

Cause: Only when using TP monitor

Cause: Stored procedured used up too much space in SYSTEM Tablespace

Cause: As stated

Cause: The view specified in the SQL statement belongs to another user and cannot be explained.

Cause: The table used by EXPLAIN to store row source information does not exist in the current schema.

Cause: The explicit plan table does not have the appropriate field definitions.

Cause: The specified plan table does cannot be found.

Cause: The user provided a NULL, empty, or malformed object of type SQL_PLAN_TABLE_TYPE

Cause: the AUTHORIZATION clause is missing from a create schema statement.

Cause: the schema name is missing or is incorrect in an authorization clause of a create schema statement.

Cause: A statement other than a create table, create view, or grant privilege appears in a create schema statement.

Cause: a table definition with a schema name prepended to the table name does not match the schema name provided in the authorization clause of a create schema statement.

Cause: the create schema statement contains views that depend on other views in the containing create schema statement or they contain references to unknown tables.

Cause: a create table statement failed in the create schema statement.

Cause: a grant privilege statement failed inthe create schema statement.

Cause: a create view statement failed in the create schema statement.

Cause: could not add a foreign key reference because of error in declaration. Either referenced table does not exist or table does not have an unique key.

Cause: user attempted to drop an index that is being used as the enforcement mechanism for unique or primary key.

Cause: the named constraint does not exist for this table.

Cause: the named constraint does not exist for this table.

Cause: Attempted to enable a primary key that is not defined for the table.

Cause: Attempted to disable a primary key tht is not defined for the table.

Cause: attempted to enable a unique key that is not defined for the table.

Cause: attempted to disable a unique key that is not deined for the table.

Cause: An attempt was made to use a date constant or system variable, such as USER, in a check constraint that was not completely specified in a CREATE TABLE or ALTER TABLE statement. For example, a date was specified without the century.

Cause: attempted to validate a primary key with duplicate values or null values.

Cause: attempted to define a column check constraint that references another column.

Cause: attempted to enable a deferrable primary key/unique constraint that has an existing unique index on the constraint columns.

Cause: create table foo (... ref. con. ...) as select ...;

Cause: alter table drop primary key - primary key does not exist.

Cause: alter table drop unique (col list) - unique specification does not exist.

Cause: alter table drop constraint <constraint_name>

Cause: attempted to define foreign key referencing an object which cannot be resolved to a base table reference

Cause: the explicity or implicity declared exceptions table does not exist.

Cause: An attempt was made to use a CREATE TABLE ... AS SELECT statement when some rows violated one or more CHECK constraints.

Cause: An attempt was made to defer a nondeferrable constraint

Cause: The named constraint does not exist

Cause: An attempt was made to drop a table with unique or primary keys referenced by foreign keys in another table.

Cause: Missing IS keyword.

Cause: The HASHKEYS option is specified more than once.

Cause: The specified HASHKEYS option must be an integer value.

Cause: The HASH IS option is specified more than once.

Cause: The SIZE argument is too small.

Cause: When specifing the HASH IS option, the number of key columns must be 1.

Cause: The column specification must specify an integer.

Cause: The HASH IS column name is not specified in the cluster definition.

Cause: The HASHKEYS option must be specified when creating a HASH CLUSTER.

Cause: The value of the hash key was not a positive number.

Cause: An attempt to create a cluster index was issued on a hash cluster.

Cause: This option is only valid for non hash clusters.

Cause: The INDEX option is specified more than once.

Cause: The HASH IS option is specified more than once.

Cause: The cluster can either be a hash or indexed cluster - not both.

Cause: This option is only valid for clusters

Cause: An attempt was made to change the SIZE and INITRANS options after the hash cluster was created.

Cause: A column in the hash is expression was not present in cluster definition.

Cause: A constant or system variable was specified in the hash expression.

Cause: Result of evaluating hash expression is not an Oracle Number.

Cause: An attempt was made to specify SYSDATE, UID, USER, ROWNUM, or LEVEL in hash expression.

Cause: SYSDATE, UID, USER, ROWNUM, or LEVEL are not allowed in hash expressions.

Cause: A PL/SQL function was used in the hash expression.

Cause: An error occurred while evaluating the clusters hash expression.

Cause: The number of extents required for creating the fixed hash area exceeds the maximum number allowed.

Cause: The number of blocks in a cluster chain exceeds the maximum number allowed.

Cause: A parallel direct load is occurring to the specified table.

Cause: A parallel direct load is not possible because an index is is being created on the table.

Cause: Merge of temporary segment into base segment failed because MAXEXTENTS was larger than the total in the temp and base segments

Cause: An invalid file name was specified to load data into.

Cause: Too many processes specified than allowed per event.

Cause: Illegal event string

Cause: Illegal process string

Cause: Bad process or size in _trace_buffers INIT.ORA parameter.

Cause: Bad syntax for _trace_options INIT.ORA parameter.

Cause: Error occurred in creating/writing the file.

Cause: Incompatible binary trace data was specified.

Cause: An attempt was made to open or access the trace file during a trace conversion.

Cause: No value was specified for the RESIZE clause.

Cause: The keyword ON or OFF was not specified for the AUTOEXTEND clause.

Cause: No value was specified for the NEXT clause.

Cause: A non-integer value was used for the NEXT clause of the DATAFILE list.

Cause: UNLIMITED was not specified, or an invalid integer value was specified, for the MAXSIZE clause in the DATAFILE file list. The MAXSIZE value cannot be smaller than the SIZE value.

Cause: An attempt was made to resize a data file in a tablespace that is read only.

Cause: An attempt was made to alter or drop an individual chunk tablespace which is part of a tablespace set.

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

Cause: An invalid option IN SHARD was specified for the CREATE TABLESPACE SET statement.

Cause: An attempt to specify the TEMPLATE option without the CREATE TABLESPACE SET statement failed.

Cause: In the CREATE TABLESPACE SET, the USING TEMPLATE option was specified more than once.

Cause: A nonexistent SHARDSPACE was specified in the CREATE TABLESPACE or CREATE TABLESPACE SET statement.

Cause: In the CREATE TABLESPACE SET, the IN SHARDSPACE option was specified more than once.

Cause: The SHARDSPACE option was not specified in the CREATE TABLESPACE SET statement.

Cause: The SHARDSPACE keyword was omitted in the IN SHARDSPACE option.

Cause: An attempt was made to create a shard tablespace in a non-shard database.

Cause: An attempt was made to define multiple PARTITIONSETS in the SHARDSPACE.

Cause: An attempt was made to reference a tablespace set at the table level.

Cause: An attempt was made to run a shard DDL on a nondeployed shard or with the shard DDL option disabled.

Cause: The CREATE TABLE statement contained more than one PARTITIONSET option.

Cause: An invalid PARTITIONSET method was specified in the CREATE TABLE statement. A table may be partitioned by RANGE or LIST.

Cause: The number of columns in a PARTITIONSET column list exceeded the legal limit of one for list partitioned tables.

Cause: Interval PARTITIONSET was not supported for a sharded table.

Cause: Only tables can have the SHARDED type.

Cause: definition of a table with both PARTITIONSET and CLUSTER clauses which is illegal.

Cause: definition of a non sharded table with PARTITIONSET clause is illegal.

Cause: All shards where this chunk is stored were unavailable.

Cause: All shards where this chunk is stored were unavailable.

Cause: An attempt was made to enable shard DDL in a non-shard database.

Cause: An attempt was made to get a new range of data object numbers which resulted in a failure.

Cause: PARENT clause was specified on a non-sharded table.

Cause: The parent table specified was not a valid identifier.

Cause: The child and parent tables did not have the same owner.

Cause: The child and parent tables did not have the same sharding method.

Cause: The child and parent tables did not have the same shard key columns.

Cause: The child and parent tables did not have the same partition set key columns.

Cause: The table name specified was not the one of the root table.

Cause: An attempt was made to create a child table without specifying the PARENT clause.

Cause: An attempt was made to create a sharded table on a non-sharded database.

Cause: An attempt was made to create a primary key constaint on non-sharding columns.

Cause: The PARTITION clause was expected but was not supplied.

Cause: The PARTITION clause was supplied with CONSISTENT HASH sharding.

Cause: The TABLESPACE SET clause was expected but was not supplied.

Cause: The TABLESPACE SET supplied did not exist.

Cause: Data file explicit name was specified as part of the tablespace set template. Only Oracle Managed Files are supported by a tablespace set.

Cause: The TABLESPACE SET clause was not expected.

Cause: An attempt was made to perform an operation with shard DDL enabled, which is not supported for propagation from catalog to shards.

Cause: An attempt was made to create a global index on a sharded table, which is not supported.

Cause: The TABLESPACE SET clause was not supplied when creating an index on a system-managed sharded table.

Cause: The partitioning method specified was not compatible with user-defined sharding.

Cause: The partitioning method specified was not compatible with system-managed or composite sharding.

Cause: Supported data types were not used for the sharding or partition set columns.

Cause: Virtual column was used in the sharding or partition set key, which is not supported.

Cause: An invalid option was specified while creating duplicated tables.

Cause: An invalid option was specified while creating duplicated tables.

Cause: An invalid option was specified while altering duplicated tables.

Cause: An attempt was made to create an index-organized sharded table. This is not supported.

Cause: Duplicated tables were created when shard DDL was disabled.

Cause: Invalid operation was specified on a duplicated table.

Cause: The shard name specified was not valid.

Cause: The TABLESPACE clause was not supplied when specifying a partition of a user-defined sharded table.

Cause: The DROP TABLESPACE SET command was not compatible with user-defined sharding.

Cause: An attempt was made to perform online redefinition on a sharded table or a duplicated table for sharding, which is not supported.

Cause: An attempt was made to create a non-sharded, non-duplicated table across shards, which is not supported.

Cause: An attempt was made to operate on a sharded or a duplicated object across shards when the shard DDL was not enabled.

Cause: An attempt was made to ALTER or DROP a non-sharded object when the shard DDL was enabled.

Cause: The TABLESPACE SET supplied existed in a different shardspace from the one to which the table belonged.

Cause: An attempt was made to modify partitions on system-managed or composite sharded tables.

Cause: An attempt was made to create a duplicated table with 1000 columns when there was no primary key defined. Note that unused columns in the table are counted toward the 1000 column limit.

Cause: An attempt was made to create a duplicated table in a non-shard schema.

Cause: XMLType column in a duplicated table required an automatic segment space management (ASSM) tablespace.

Cause: An attempt was made to rebuild an outline with shard DDL enabled, which is not supported.

Cause: An individual chunk tablespace which was part of a tablespace set was used.

Cause: An attempt was made to create a duplicated table when the user did not have sufficient privileges.

Cause: An attempt was made to create a sharded table without any columns.

Cause: An attempt was made to create a sharded table with an identity column.

Cause: An attempt was made to drop a system tablespace part of the sharding environment when the sharding environment was deployed.

Cause: An attempt was made to alter the password for a user who created duplicated tables but did not have the privilege to execute the ALTER DATABASE LINK statement.

Cause: An invalid operation was specified on a duplicated table.

Cause: An attempt was made to operate on a sharded or duplicated schema object by a non all-shard user.

Cause: Shard DDL is not supported after a session's current schema has been altered.

Cause: An attempt was made to create a nested sharded table, which is not supported.

Cause: An invalid sharding method was set for a sharded database.

Cause: Fewer number of partition set specifications were specified than the number of shardspaces in the composite sharding environment.

Cause: PARTITIONSETS were specified while creating a sharded table in non-composite sharding environment.

Cause: PARTITIONSET specifications were missing.

Cause: An attempt was made to create a tablespace set with the SMALLFILE option.

Cause: An attempt was made to add or drop a data file from a tablespace set.

Cause: An attempt was made to create a foreign key constraint in a sharded table on a column referencing a duplicated table.

Cause: The tablespace set name specified for the paritition set was either invalid or belonged to a different shardspace.

Cause: An attempt was made to create a duplicated table as select from another table in parallel mode.

Cause: An attempt was made to create or alter a duplicated table by enabling INMEMORY options.

Cause: One of the tablespaces in the tablespace set was not created.

Cause: An attempt was made to change the dupl_table_refresh_rate in the non-catalog database.

Cause: An attempt was made to create a duplicated table of object type.

Cause: An attempt was made to change the dupl_table_refresh_rate to less than 20 seconds.

Cause: An invalid partition set name was specified.

Cause: The sequence used to specify partition sets was invalid.

Cause: An attempt was made to specify a tablespace set for indexes on a sharded table in a composite sharding environment which is not supported.

Cause: An attempt was made to drop a user who owns a duplicated table when the shard database was down or the gsm_requests were pending execution.

Cause: An attempt was made to drop a duplicated table when the shard database was down or the gsm_requests were pending execution.

Cause: An attempt was made to alter shard user password when the shard database was down or the gsm_requests were pending execution.

Cause: An invalid option was specified while creating duplicated tables.

Cause: An attempt was made to truncate a duplicated table on a shard database.

Cause: An invalid option was specified while creating a sharded table.

Cause: A DROP or ALTER TABLESPACE operation was attempted on a shard where the tablespace does not exist.

Cause: An attempt was made to drop a column used as the super-partitioning key for a sharded table.

Cause: An invalid credential name was specified.

Cause: Credential name specified already used by an existing object.

Cause: The specified credential does not exist.

Cause: An invalid file name was specified.

Cause: File name specified already used by an existing object.

Cause: The specified file does not exist.

Cause: An invalid destination name was specified.

Cause: A destination must be specified in the command.

Cause: The specified destination does not exist.

Cause: The specified remote scheduler agent cannot be contacted.

Cause: Unable to successfully run specified job.

Cause: An invalid shardgroup name was specified.

Cause: The specified shardgroup did not exist.

Cause: An invalid shardspace name was specified.

Cause: The specified shardspace did not exist.

Cause: A shardgroup or shardspace name was not specified.

Cause: A shardgroup and a shardspace name were both specified. For this command, either a shardgroup or shardspace name may be specified, but not both.

Cause: Either a credential or login information must be specified.

Cause: For this command, either a credential or login information may be specified, not both.

Cause: A file name and file contents were both specified.

Cause: The value specified for db_domain exceeded the 128 character limit.

Cause: The specified file was in use by an undeployed shard.

Cause: The shard was not opened in the correct mode.

Cause: A request to create the broker configuration failed.

Cause: A request to enable the broker configuration failed.

Cause: A request to add the shard to the broker configuration failed.

Cause: A request to enable the shard for the broker configuration failed.

Cause: The requested shardspace did not exist.

Cause: The shardgroup name was invalid.

Cause: The shardgroup was already deployed and could no longer be modified.

Cause: The shardgroup already contained a shard and could not be converted from a primary shard to a standby shard or from a standby shard to a primary shard.

Cause: An invalid shardspace name was provided.

Cause: The shardspace was already deployed and could no longer be modified.

Cause: An invalid shardpsace name was provided.

Cause: Oracle XML DB was required for remote scheduler agent configuration but was not installed.

Cause: An invalid value of chunks was passed.

Cause: The shard was already in a shardspace.

Cause: The source and target shards for a chunk move operation were in different shardgroups.

Cause: The containing shardgroup for the source and target shards was not yet deployed.

Cause: The source and target shards for a chunk move were the same.

Cause: An attempt was made to add a primary shardgroup to a shardspace that already had a primary shardgroup. When Oracle Data Guard replication is used, only one primary shardgroup is allowed in each shardspace.

Cause: The shard did not have a corresponding shard in all shardgroups in an Oracle Data Guard configuration, therefore it was not deployed.

Cause: The 'deploy' command was issued, but there were no new shards to deploy.

Cause: A request to enable fast-start failover failed.

Cause: The specified rack already contained another shard in the same Oracle Data Guard configuration.

Cause: The specified shardspace already contained a primary shard.

Cause: The Oracle GoldenGate configurations contained standby shards.

Cause: An invalid rack name was provided.

Cause: A SYS password was not specified when creating a new shard using Oracle Database Configuration Assistant (DBCA).

Cause: An attempt was made to change the region value for a system-managed or composite shard.

Cause: An operation failed when performed using the remote scheduler agent.

Cause: The specified pool was not sharded.

Cause: The maximum number of Global Data Services (GDS) sharded pools had been reached.

Cause: The specified shardgroup was already in existence.

Cause: The specified database pool already contained either a conflicting shard or shardgroup.

Cause: The catalog was not enabled for sharding and a sharding command was executed.

Cause: The specified shardspace was already in existence.

Cause: The number of chunks in the specified shardspace was less than twice the number of shards in one of its shardgroups.

Cause: The specified shardspace was already in existence.

Cause: An attempt was made to remove a shard which currently contains chunks.

Cause: When a shard was removed, all other shards in the same Oracle Data Guard configuration were also removed.

Cause: A command was issued that included both the shardspace and and shardgroup parameters.

Cause: An invalid chunk number or source database was provided.

Cause: The '-agent_port' parameter specified a new agent port value. The already registered scheduler agents must re-register with the catalog database to use this new value.

Cause: The '-agent_port' parameter specified a new agent port value. The port specified may already have been in use by another process in the system.

Cause: A command was issued that did not include shardspace".

Cause: An attempt was made to split a chunk before creating a tablespace set.

Cause: An attempt was made to split a chunk before creating a sharded table.

Cause: One or more conditions required by Data Guard observer were not met.

Cause: An attempt was made to issue an ALTER TABLE statement to modify the data type or length of a column used to super-partition the specified sharded table.

Cause: The query had a construct that was not supported for inter shard query.

Cause: The DML was applied to more than one shard.

Cause: An attempt was made to update the sharding key value using the UPDATE command.

Cause: The aggregate, group by, semi-join, or anti-join subquery was mapped to multiple shards.

Cause: The query had illegal or no join predicate on the sharding key.

Cause: The query had a sharded table outer joined to the replicated table.

Cause: The query had a non-equality join on the sharding key.

Cause: The query had an object defined by user-specified sharding.

Cause: The query had an object defined under composite sharding.

Cause: The query referenced a private and a sharded table.

Cause: The query referenced unsupported constructs which could not be fetched from the shard.

Cause: The statement attempts an array DML operation on a sharded table.

Cause: The INSERT statement was used to insert a row in the sharded table without inserting a value for the shard column.

Cause: The schema definition on the shard and the coordinator did not match.

Cause: A valid partition was not found for the chunk number passed to the shard database.

Cause: Two-task driver could not find the value of ORACLE_SID in the environment.

Cause: ORACLE_HOME environment variable not set.

Cause: ORACLE_HOME environment variable not set.

Cause: The pipe driver failed to create pipes for communications with the orapop process.

Cause: The two-task driver could not fork orapop.

Cause: The pipe driver failed while polling the communications channel.

Cause: The length of your host-string specified by the TWO_TASK environment variable exceeds the ORACLE system-imposed limit.

Cause: The invoked Unix two-task driver could not allocate heap space for the context area.

Cause: The invoked Unix two-task driver failed to find an entry in oratab for the sid you supplied.

Cause: The pipe driver failed to create pipes for two-task communications with the oracle shadow process.

Cause: The pipe driver could not fork the oracle shadow process.

Cause: The pipe driver failed to write to the orapop process.

Cause: The pipe driver failed to allocate enough heap space for its context area buffers.

Cause: The pipe driver failed to read a message from the communications channel.

Cause: The pipe driver failed to write a message to the communications channel.

Cause: The pipe driver received a message having an unrecognizable message type.

Cause: The Pipe driver received a message having an unrecognizable message type.

Cause: The Pipe driver sent a message that was apparently successful, but the number of bytes transmitted did not match the number of bytes furnished to the driver.

Cause: The two-task driver could not reset the connection.

Cause: The fast driver could not fork the oracle shadow process.

Cause: When the fast driver was invoked, processes failed to attach to the shared memory buffer. You probably supplied an illegal shared memory attach address, or the system ran out of data space to accomodate the buffer.

Cause: The Fast driver failed to get a semaphore set.

Cause: The Pipe driver could not send a break message to orapop.

Cause: The Pipe driver could not send a break message to the ORACLE shadow process.

Cause: The Pipe driver could not send a break message to orapop.

Cause: The Pipe driver could not send a break message to the ORACLE shadow process.

Cause: The Pipe driver could not access the oracle executable.

Cause: The Pipe driver could not access the orapop executable.

Cause: The Fast driver could not access the oracle executable.

Cause: The driver you have specified is not supported.

Cause: The driver you have specified could not find your logon directory while searching for your local .sqlnet file.

Cause: The specified driver could not find enough heap space to malloc a buffer.

Cause: Database alias specified was not identified in either $HOME/.sqlnet or /etc/sqlnet.

Cause: While converting a database alias to a database ID, the resulting database ID string exceeded the ORACLE system-imposed limit.

Cause: The Fast driver was unable to reset shared memory permissions.

Cause: The Fast driver failed to create a shared memory segment for two-task communication.

Cause: The Fast driver failed to establish a default shared memory address.

Cause: The Pipe driver failed to send orapop the command to exit.

Cause: The pipe driver apparently sent an imcomplete break message.

Cause: The alias used for a sqlnet host is longer than 161 characters.

Cause: The Fast driver failed to create a shared memory file for two-task communication.

Cause: The Fast driver failed to map a shared memory file for two-task communication.

Cause: The Fast driver failed to attach shared memory at the expected location.

Cause: The Fast driver cannot close the shared memory file.

Cause: The Fast driver could not alter the inheritence attributes of the shared memory.

Cause: The Fast driver failed to create a file for shared memory.

Cause: The Fast driver encountered an error translating the shared memory filename ?/dbs/ftt_pid.dbf.

Cause: The Fast driver failed to fork a process onto the desired cluster and node number.

Cause: The package was unable to allocate memory for an array because the system ran out of memory.

Cause: All of the package's request descriptors are in use performing other requests.

Cause: The client was unable to close a file after forking the servers.

Cause: The file number contained with the sfiov structure is less than zero.

Cause: The file number contained with the sfiov structure is greater than the maximum.

Cause: No requests were found that could be cancelled.

Cause: The mode of the package can only be parallel or duplex.

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

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

Cause: The package requires that the number of request descriptors be greater than or equal to the number of servers used.

Cause: The maximum number of files to be used by the package was less than or equal to zero.

Cause: The package was unable to set up handling by the server for the termination signal. This is an internal error.

Cause: The total number of blocks to be allocated for use by the package was not greater than zero.

Cause: The number was not a positive number.

Cause: The time given was not a positive number.

Cause: The time given was not a positive number.

Cause: The time given was not a positive number.

Cause: The signal number was not a positive number.

Cause: The value sent to the package for use as the "request done" signal exceeds the maximum allowed by the operating system.

Cause: The package was unable to get information about the directory in which the log files are to reside.

Cause: The name given for the directory in which the logs are to be kept does not correspond to a directory.

Cause: The package was unable to get information about the directory into which the servers are to dump core in the event of an exception.

Cause: The name given for the directory in which the server processes are to dump core in the event of an exception does not correspond to a directory.

Cause: The value given was not TRUE or FALSE.

Cause: To ensure that the functions act symmetrically, pointers to both the read and write functions must be given.

Cause: To ensure that the functions act symmetrically, pointers to both the posting and waiting functions must be given.

Cause: The ID of the segment specified for use as the shared buffer region was invalid.

Cause: The size given for the shared memory segment to be used as the shared buffer region was less than or equal to zero.

Cause: The size of the shared segment that was specified for the shared buffer region is less than the number of bytes required. The first field of the "additional information" field is the size needed. The second is the size of the segment.

Cause: The package cannot allocate memory for an internal segment list because the system has run out of memory. The "additional information" field is the amount of memory that the package attempted to allocate.

Cause: Internal error - Contact ORACLE support.

Cause: The maximum number of files that can be used for asynchronous I/O has been reached.

Cause: The length of the name of a file that is being opened for asynchronous I/O is longer than the maximum. The "additional information" field is the maximum length.

Cause: The package could not open file for some reason.

Cause: The fstat(2) call on a file being used for asynchronous I/O failed.

Cause: The client was unable to close a file being used for asynchronous I/O.

Cause: The client was unable to get a key so that it obtain shared memory for use with shared memory.

Cause: The client was signalled by a server that it was done with a request but the "done" list was empty.

Cause: A request is not in the right state.

Cause: No free request descriptors are available.

Cause: The number of operations sent to either sfard() or sfawrite() is less than zero.

Cause: The arming of a signal handler for the "done" signal failed.

Cause: Some of the requests for asynchronous input or output were not serviced in the required amount of time.

Cause: Some asynchronous operations timed out in kernel mode.

Cause: Internal error.

Cause: Internal error.

Cause: The client was unable to allocated a buffer for the name of the log file.

Cause: Internal error.

Cause: Internal error.

Cause: The client was unable to allocate memory for the array of I/O vectors that the servers are to use.

Cause: The client was unable to allocate memory for an array of flags that the servers are to use.

Cause: Internal error.

Cause: Internal error.

Cause: Shmget(2) failed.

Cause: Shmat(2) failed.

Cause: A server did not die after being sent a kill signal.

Cause: A server could not read a requested amount of data.

Cause: A server could not read in the request amount of data. The first number in the "additional information" field is the block number being read in. The second is the actual number of bytes that was read in.

Cause: A server was unable to perform a write. The number in the "additional information" field is the starting block number of the data segment being written out. The first number in the "additional information" field is the block number being written out. The second is the actual number of bytes that was written out. The disk may have filled up.

Cause: A server could not write the requested amount of data out to disk. The disk may have run out of space.

Cause: A server could not read the number of blocks that was requested. The end of the file may have been read.

Cause: A server was unable to seek to the designated block.

Cause: The buffer on which an I/O is being done is not on the correct boundary.

Cause: The list from which the package allocates request descriptors is empty because all of the descriptors is in use.

Cause: Internal error.

Cause: A negative number was given for the I/O block size to be used by the asynchronous I/O package.

Cause: The file number upon which an operation is to done is either less than zero or greater than the maximum number of files than can be open.

Cause: No segments are available to allocated.

Cause: No segment of the proper size is ready for use by the caller.

Cause: A segment that is larger than that desired could not be split because no free segment was available.

Cause: The caller attempted to deallocate a segment but the "in use" list was empty. This is a programming error.

Cause: The caller attempted to deallocate a segment that was not on the "in use" list. This is a programming error.

Cause: A server was unable to close a file being used for asynchronous I/O.

Cause: The server was unable to open a file for use with asynchronous I/O.

Cause: Internal error.

Cause: Internal error.

Cause: Internal error.

Cause: The arming of a signal handler for the alarmsignal failed.

Cause: The server was unable to flush its writes out to disk.

Cause: The client process was unable to open its log file.

Cause: A server exited during its initialization process.

Cause: The client could not spawn a server. A possible reason is that the operating system has reached its limit on the number of processes that it can spawn.

Cause: An illegal value was given for the kernel flag in the information structure. Only TRUE and FALSE are permitted.

Cause: A value was given for the flag that determines whether a file is to be left open after the client checks it to see if the servers can use it. Only TRUE and FALSE are supported.

Cause: A value was given for the flag that indicates that operations are to be timed out. Only TRUE and FALSE are supported.

Cause: A server would not respond to the termination signal. The first number is the number of the server. The second is its UNIX process number. This is an internal problem.

Cause: A server did not respond to a posted request to shutdown. The first number is the number of the server. The second is its UNIX process number. This is an internal problem.

Cause: An operation using the asynchronous I/O package was attempted without first initializing the package using sfainit().

Cause: A server could not read the requested amount of data from disk.

Cause: A file upon which an asynchronous I/O operation is to be performed has already been closed by the package.

Cause: This is an internal problem.

Cause: The time given was not a positive number.

Cause: The time given was not a positive number.

Cause: The value given for "db_slave_buffers" in your INIT.ORA file is less than 0.

Cause: The value given for 'db_slave_buffers' in the initialization parameter file was less than the number specified for the number of slaves, 'db_slaves.'

Cause: Stated in errno.

Cause: Stated in errno.

Cause: The adspcinit program has not been executed.

Cause: The variable smpdidini was overwritten, probably by client code.

Cause: This is an internal error, note error code in errno.

Cause: This is an internal error, note error code in errno.

Cause: This is an internal error, note error code in errno.

Cause: This is an internal error, note error code in errno.

Cause: The environment variable EXTSHM was set before starting oracle.

Cause: This feature is not implemented.

Cause: This is an internal error.

Cause: User attempted to use a feature which is no longer supported.

Cause: An incompatible OCI function call was issued for new functionality.

Cause: Invalid input data was detected for the specified data type.

Cause: A malformed TTC (Two-Task Common) packet was received.

Cause: A statement containing a SQL*Net connect string was issued to the single-task server. For example, a database link was used in a SQL statement.

Cause: The connection between Client and Server process was broken.

Cause: There was both a datatype, and an anonymous datatype declaration found.

Cause: This is an internal error.

Cause: This is a status code that indicates that the operation cannot complete now.

Cause: Internal error.

Cause: The application received a bad escape sequence from the server and may indicate a problem with the client application user code.

Cause: A non-blocking operation was attempted and the network driver does not support non-blocking operations.

Cause: An attempt was made to execute a new operation before the active non-blocking operation completed or a new operation was attempted before all the pieces of a column were inserted or fetched.

Cause: The OCI test for non-blocking mode on a connection indicates that the connection is in blocking mode.

Cause: The application performed a piecewise bind on a column.

Cause: The application performed a piecewise define on the column.

Cause: The application either provided the length of the buffer for the next piece to be zero or provided a null pointer.

Cause: The default value specified for a record field was too large.

Cause: An attempt was made to connect to an Oracle server of older version.

Cause: 1) Server unexpectedly terminated or was forced to terminate. 2) Server timed out the connection.

Cause: Inbound connection was timed out by the server because user authentication was not completed within the given time specified by SQLNET.INBOUND_CONNECT_TIMEOUT or its default value

Cause: A malformed TTC (Two-Task Common) packet was received from the client.

Cause: Connection was terminated due to a security policy violation.

Cause: The SEC_DISABLE_OLDER_ORACLE_RPCS initialization parameter was enabled.

Cause: The current I/O operation was not complete. The error is typically returned from vectored and/or asynchronous I/O calls.

Cause: The I/O request queue was full and no more requests could be queued.

Cause: Connection was lost for the specified session and serial number. This is either due to session being killed or network problems.

Cause: Connection was lost for the specified process ID and thread ID. This is either due to session being killed or network problems.

Cause: Connection was lost for the specified process ID. This is either due to session being killed or network problems.

Cause: Attempted to PUT data when GET streaming was in progress or attempted to GET data when PUT streaming was in progress.

Cause: A malformed TTC (Two-Task Common) packet was received.

Cause: A malformed TTC (Two-Task Common) packet was received.

Cause: The row count was larger than UB4MAXVAL. OCI clients using OCI_ATTR_ROW_COUNT cannot see row counts larger than UB4MAXVAL.

Cause: An invalid Oracle error code was received by the server.

Cause: The connection between the client and the remote server process was broken.

Cause: The schema name length was larger than UB1MAXVAL, and clients older than Release 12.2 were unable to process longer names.

Cause: The object name length was larger than UB1MAXVAL, and clients older than Release 12.2 wree unable to process longer names.

Cause: The column name length was larger than UB1MAXVAL, and clients older than Release 12.2 were unable to process longer names.

Cause: A Deprecated Two-Task Common (TTC) remote procedural call (RPC) was invoked.

Cause: Statement execution could not proceed because the rewritten statement that was issued to the remote had a different ordering (or number) of bind variables as compared to the original statement issued locally.

Cause: You are using an Oracle client application linked with libraries with lower version than the current server version.

Cause: A new undo segment was added. A query can occasionally deadlock when issued around the time an undo segment is added and used immediately on the primary.

Cause: Recovery was terminated. A query can ocassionally deadlock when recovery is terminated because it needs a block with changes that are made after the point at which recovery was terminated.

Cause: Standby recovery fell behind the STANDBY_MAX_DATA_DELAY requirement.

Cause: ALTER SESSION SYNC WITH PRIMARY did not work because either the standby was not synchronous or in a data-loss mode with regard to the primary, or the standby recovery was terminated.

Cause: ALTER SESSION SET STANDBY_MAX_DATA_DELAY did not work for SYS users.

Cause: The value of the %s parameter was not the same in all instances.

Cause: The database was not an open physical standby database.

Cause: Duplicate SESSION or GLOBAL specifications were specified.

Cause: NOCACHE or ORDER sequences were not supported for Active Data Guard standby.

Cause: Connection to the corresponding primary database failed. The primary database might be down.

Cause: The sequence object might have been dropped by the primary database.

Cause: The sequence object might have been altered by the primary database.

Cause: The parameter could not be changed during Oracle Active Data Guard (Oracle ADG) recovery.

Cause: An attempt was made to enable the parameter on a non-Engineered system or it was not on a Platform as a Service.

Cause: segment type is not TABLE, INDEX, or CLUSTER

Cause: the freelist group number was either negative or larger than the the number of freelist groups in the segment

Cause: the scan limit did not have a positive integer value the number of freelist groups in the segment

Cause: high volume of user updates interfere with the space analysis

Cause: partition name is specified for the space analysis, but the object type does not indicate parttitioning

Cause: partition name is not specified for the space analysis, but the object type indicates parttitioning

Cause: The maximum file size for an autoextendable file has exceeded the maximum number of blocks allowed.

Cause: partition type is specified for the space analysis, but the object type indicates composite partitioning

Cause: subpartition type is specified for the space analysis, but the object type indicates non-composite partitioning

Cause: The value of file number or block number is outside of limits or inconsistent

Cause: The value of one of the option parameters is incorrect

Cause: The segment specified in the DBMS_SPACE_ADMIN or DBMS_SPACE operation does not exist or is not in a state appropriate for this operation

Cause: Attempt to create a temporary segment for sort/hash/lobs in in permanent tablespace of kind locally-managed

Cause: The Lob Segment specified in the DBMS_SPACE operation does not exist.

Cause: File Size specified for add/resize datafile/tempfile does not allow for the minimum required of one allocation unit.

Cause: File Size specified for resize datafile/tempfile causes bitmap control structures to overlap

Cause: Corruptions detected during verification whch cannot be dealt with

Cause: invalid option for alter of temporary tablespace was specified

Cause: invalid option for create/alter tablespace of type locally-managed

Cause: Operation which is only applicable to permanent, online, locally-managed tablespaces is specified for a tablespace which is either dictionary-managed, offline or temporary

Cause: Some of the procedures was called with missing or NULL parameters

Cause: An attempt was made to do one of the following : (1) create a temporary tablespace with a non-standard block size or, (2) alter an existing permanent tablespace of non-standard block size to a temporary tablespace or, (3) issue a DDL statement that would result in the creation of a temporary segment in a tablespace of non-standard block size.

Cause: Either a bad value passed to dbms_space.create_table_cost() or explain plan did not pass through size information.

Cause: The limitation of addressability of BMIB (Bitmap Index Block) was reached for the current blocksize.

Cause: Attempt to preserve too many blocks.

Cause: Attempt to deallocate space from the segment which was truncated prior to the 7.3 release.

Cause: Failed to allocate an extent for table subpartition segment in tablespace.

Cause: Failed to allocate an extent for index subpartition segment in tablespace.

Cause: A table subpartition tried to extend past maxextents

Cause: An index subpartition tried to extend past maxextents

Cause: Too large a size for an initial extent due to freelist group specification

Cause: An attempt was made to allocate an extent for LOB subpartition segment in tablespace, but the extent could not be allocated because there is not enough space in the tablespace indicated.

Cause: A LOB subpartition segment tried to extend past maxextents.

Cause: Users default temporary tablespace must be different from the tablespace being migrated.

Cause: User specified an invalid unit size for the tablespace

Cause: For migration to complete, temporary segments should not be present in the tablespace at the time of migration.

Cause: Cannot overlap control information during relocation

Cause: During migration of tablespace found no place to put the control information. If during bitmaps relocation, found no space at the specified destination.

Cause: Tablespace was not dictionary managed or online or permanent.

Cause: Control information cannot be placed at the specified dba either because the block number specified is beyond the file end or the file is not large enough to accomodate the control information at that location

Cause: Relocation of bitmaps to the said destination will make the tablespace self descriptive

Cause: Temporary segments were attempted to be created during migration

Cause: For the given blocksize, uniform size specified is insufficient

Cause: This segment cannot be marked corrupt because it contains data dictionary objects

Cause: It is not permitted to migrate SYSTEM tablespace from locally managed format to dictionary managed format or relocate bitmaps.

Cause: Fatblock size of LOB segment is too big to fit into the initial extent.

Cause: Unable to create a consistent snapshot of the object in a read only database. Transaction recovery must be performed before opening the database read only.

Cause: Dropping file from ts which has a single file extent.

Cause: Trying to drop a non-empty datafile

Cause: Trying to drop the first datafile with which ts is created

Cause: Trying to drop offline datafile in lmts

Cause: The DEALLOCATE option and the ALLOCATE option are specified in the same command.

Cause: The DEALLOCATE UNUSED option to ALTER TABLE or ALTER INDEX is specified more than once.

Cause: The ALLOCATE EXTENT option to ALTER TABLE or ALTER INDEX is specified more than once.

Cause: The specified value must be an integer.

Cause: An option (DATAFILE, SIZE or INSTANCE) was specified more than once.

Cause: The specified value is not recognized as a valid instance name.

Cause: A character string literal is expected, but not found.

Cause: An option other than DATAFILE, SIZE or INSTANCE was specified.

Cause: No ALLOCATE EXTENT options were specified.

Cause: The datafile does not exist

Cause: The specified datafile or tempfile did not belong to the tablespace that the object resides in.

Cause: The cluster is a hash cluster, and can not use the allcoate extent option.

Cause: The specified FREELIST GROUP number is invalid

Cause: Both FREELIST GROUP and INSTANCE were specified in clause

Cause: Partition name and segment type specified for space analysis do not match

Cause: Invalid object specification given.

Cause: Expected STORAGE keyword

Cause: The table being truncated is a member of a cluster.

Cause: Only INDEX CLUSTERS can be truncated.

Cause: The specified datafile is not available for resizing.

Cause: Some portion of the file in the region to be trimmed is currently in use by a database object

Cause: Attempt to shrink a datafile while it is under hot backup. This is not allowed.

Cause: A dictionary table is created upon the first execution of the command 'alter database datafile autoextend on' for a database. This operation did not succeed. The most probable cause for this is insufficient space in the system tablespace.

Cause: An attempt to add a shardspace to the catalog was attempted when a shardspace already existed.

Cause: Mutually exclusive parameters were specified in a command.

Cause: A reserved word was used as the name of an object.

Cause: A command was issued which required a sharded database pool, but none existed.

Cause: A command was issued which required a sharded database pool, but more than one existed.

Cause: A command was issued without specifying a shardgroup and a default shardgroup could not be determined.

Cause: A command was issued without specifying a shardspace and a default shardspace could not be determined.

Cause: An environment variable required for the operation was not set at the specified destination.

Cause: The requested shard did not exist.

Cause: The input file contained a parameter that was too long.

Cause: A directory required for successful operation did not exist or was not writeable at the destination.

Cause: A shard with the same database identifier was a member of a shardgroup in another shardspace.

Cause: A shard with the same database identifier was a member of the specified shardgroup.

Cause: A shard that contained chunks was removed from the catalog. Those chunks are no longer available.

Cause: The chunk recovery procedure was not able to automatically recover corrupted chunks.

Cause: The specified user did not exist on this shard.

Cause: The statement was too long.

Cause: A nonexistent shard was provided for execution.

Cause: The primary database was not registered. Service management requires registration of all primary databases.

Cause: The specified shard character set did not match the catalog character set.

Cause: The specified shard national character set did not match the catalog national character set.

Cause: The specified database was not in the sharded schema.

Cause: The specified chunk move could not be suspended.

Cause: The specified chunk could not be removed from the queue.

Cause: The specified database was not configured to be a catalog.

Cause: Unable to successfully complete shard deployment.

Cause: Unable to retrieve default Oracle Database Configuration Assistant (DBCA) template from shard.

Cause: Chunk migration pre-check failed because one of the transporting tablespaces was either read-only or in hot backup mode.

Cause: An attempt was made to create a service in a sharded pool that specified preferred and available databases.

Cause: The requested operation required one or more involved shards to be up-to-date with the DDL state of the sharded system.

Cause: The master global service manager was no longer connected to the catalog.

Cause: The GSMUSER account was not granted SYSDG and SYSBACKUP privileges.

Cause: New shardspaces could not be added because a root table already existed in the sharded database.

Cause: A previous request for deploy operation was still in progress.

Cause: A database condition that prevents chunk move was detected.

Cause: The flashback database was not enabled on the database being configured.

Cause: User-defined sharding was not supported on the database being configured.

Cause: The specified valid node check for registration (VNCR) was in use by at least one database or shard.

Cause: SYS.EXEC_SHARD_PLSQL can only execute a limited set of PL/SQL procedures.

Cause: An attempt was made to create a shardgroup with user-defined sharding.

Cause: An attempt was made to create a primary shard from a standby database or a standby shard from a primary database.

Cause: There was an incomplete split operation on the same chunk ID.

Cause: An attempt was made to skip a system DDL request such as SPLITCHUNK.

Cause: There was an incomplete move operation.

Cause: An attempt was made to set a database parameter that cannot be set using this procedure.

Cause: An attempt to enable affinity on non-Oracle RAC database was made

Cause: The table specification was not correct.

Cause: The specified table was not partitioned.

Cause: The specified table was not partitioned by either RANGE, LIST or HASH.

Cause: A table affinity was already specified. Multiple table affinities are currently not supported.

Cause: An attempt was made to delete a service that was already deleted.

Cause: An attempt was made to modify a service that was already deleted.

Cause: The job_queue_processes initialization parameter was set to zero or one.

Cause: The parameter values passed to SET DATAGUARD_PROPERTY were invalid.

Cause: The values passed to SET DATAGUARD_PROPERTY were invalid.

Cause: An attempt was made to directly alter or drop an internal database link for sharding, which is not allowed.

Cause: An attempt was made to rename a shard key column or a partition set key column of a sharded table, which is not allowed.

Cause: An attempt was made to shrink a system-managed or composite sharded table with primary key or a sharded table with functional index, which is not allowed.

Cause: An attempt was made to perform the Flashback Table operation on a sharded or duplicated table, which is not allowed.

Cause: An attempt was made to modify the sharding virtual column, SYS_HASHVAL, which is not allowed.

Cause: An attempt was made to use a tablespace for multiple partitions of a user-defined sharded table.

Cause: An attempt was made to specify a tablespace for LOBs that belonged to a different shardspace.

Cause: An attempt was made to purge an individual chunk tablespace which is a part of a tablespace set.

Cause: An operation failed when performed using Oracle GoldenGate.

Cause: One or more components of the Oracle GoldenGate (OGG) service descriptor could not be verified.

Cause: Oracle GoldenGate (OGG) AdminService or DistributionService could not be reached.

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

Cause: Internal error. An Oracle GoldenGate (OGG) sharding functionality was called in an invalid context, for example, catalog function in shard or vice versa.

Cause: The values specified for Oracle GoldenGate (OGG) deployment parameters (number of shards - S, number of chunks - C and replication factor - R) for the shardgroup 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 an invalid entry.

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

Cause: A request to remove a shard database failed.

Cause: Internal error. Chunk allocation algorithm for Oracle GoldenGate (OGG) detected inconsistencies in the sharding configuration.

Cause: An invalid chunk number or target shard name was provided.

Cause: An invalid chunk number or source shard name was provided.

Cause: the sum of PCTUSED and PCTFREE for a cluster or table exceeds 100

Cause: %s (a sequence parameter) specified was not an integer

Cause: a sequence increment was specified to be zero

Cause: %s (a sequencer parameter) had too many digits

Cause: MINVALUE was specified to be greater than or equal to MAXVALUE

Cause: the INCREMENT specified is >= MAXVALUE-MINVALUE

Cause: the given starting value is less than MINVALUE

Cause: the given MINVALUE would be greater than the current value

Cause: the starting value would be larger than MAXVALUE

Cause: the current value exceeds the given MAXVALUE

Cause: the value in the CACHE clause was one

Cause: the value specified for one of the sequence parameters exceeds limits

Cause: the object specified cannot have sequence ddl's performed on it

Cause: number to CACHE given is larger than values in a cycle

Cause: sequences that cycle must have their wrap-wrap specified

Cause: sequences that cycle must have their wrap-wrap specified

Cause: sequence was dropped while processing its next value.

Cause: The string supplied for the parameter MAX_DUMP_FILE_SIZE was not an integer, an integer followed by 'K', 'M', or 'G', nor the special value UNLIMITED.

Cause: An attempt was made to alter the specified parameter in the Standard Edition or Express Edition.

Cause: While trying to lock a library object, a deadlock is detected.

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

Cause: Had to wait to lock a library object during a nowait request.

Cause: A number of attempts were made to validate or authorize an object but failed.

Cause: While trying to mutex pin a cursor, a self-deadlock is detected.

Cause: Too many active locks for the object has been allocated. This error can be a result of too many cursors kept open per session.

Cause: An attempt was made to validate an invalidated object but it failed because of a self-deadlock.

Cause: Cannot generate diana for an object because of lock conflict.

Cause: The table or view being queried might be missing. The error number indicates the error.

Cause: Operating system process private memory was exhausted.

Cause: More shared memory is needed than was allocated in the shared pool or Streams pool.

Cause: attempt to set workarea_size_policy to AUTO while pga_aggregate_target is not specified

Cause: The system had insufficient memory to grow the pool to the specified size.

Cause: The pool could not shrink to the specified size as it could not free memory.

Cause: More shared memory is needed than was allocated in the shared object cache.

Cause: Private memory across the instance exceeded the limit specified in the PGA_AGGREGATE_LIMIT initialization parameter. The largest sessions using Program Global Area (PGA) memory were interrupted to get under the limit.

Cause: Attempt to create a package body before creating its package specification.

Cause: Attempt to access a procedure, function, package, or package body that does not exist.

Cause: An object name was specified that was not recognized by the system. There are several possible causes: - An invalid name for a table, view, sequence, procedure, function, package, or package body was entered. Since the system could not recognize the invalid name, it responded with the message that the named object does not exist. - An attempt was made to rename an index or a cluster, or some other object that cannot be renamed.

Cause: A procedure, function, or package was specified in an inappropriate place in a statement.

Cause: This message indicates the object to which the following errors apply. The errors occurred during implicit recompilation/revalidation of the object.

Cause: Attempt to compile and store a large stored procedure that results in compilation data that is too large for the system to support or store.

Cause: The object type implied by the flag does not match the type of object specified.

Cause: The required procedure, function, or package name is invalid or missing.

Cause: During forwarding of a remote object access, an attempt was made to use a non-existent database link or one owned by a user other than the logon user or PUBLIC.

Cause: An error occurred when trying to look up a remote object.

Cause: An error occurred when trying to validate a remote object.

Cause: During compilation of a PL/SQL block, an attempt was made to use a non-existent database link.

Cause: This compilation was aborted because the library unit that was compiled would have formed a non-REF mutually-dependent cycle with some other library units. This happens when an attempt is made to compile types that have attributes of other types that may participate in a cycle with this type. Example: create type t1; create type t2 (a t1); create type t1 (a t2);

Cause: Attempt to execute a stored procedure without sufficient privileges.

Cause: Attempt to resume the execution of a stored procedure using the existing state which has become invalid or inconsistent with the stored procedure because the procedure has been altered or dropped.

Cause: Attempt to execute a stored procedure to serve an RPC stub which specifies a timestamp or signature that is different from the current timestamp/signature of the procedure.

Cause: Attempt to execute a stored procedure or use a view that has errors. For stored procedures, the problem could be syntax errors or references to other, non-existent procedures. For views, the problem could be a reference in the view's defining query to a non-existent table. Can also be a table which has references to non-existent or inaccessible types.

Cause: Attempt to execute a stored procedure that has been invalidated.

Cause: Attempt to execute a stored procedure that has been altered or dropped thus making it not callable from the calling procedure.

Cause: Attempt to execute a non-procedure.

Cause: Attempt to execute a non-existent stored procedure.

Cause: One of errors 4060 - 4067 when attempt to execute a stored procedure.

Cause: An attempt was made to drop or replace a library that has dependents. There could be a table which depends on type which depends on the library being dropped.

Cause: An invalid trigger name was specified.

Cause: The trigger statement is missing the BEFORE/AFTER/INSTEAD OF clause.

Cause: An invalid trigger type was given.

Cause: A column list was specified for a non-update trigger type.

Cause: An invalid name was given in the referencing clause.

Cause: An statement was given for the trigger action.

Cause: An invalid NEW or OLD specification was given for a column.

Cause: The when clause can only be specified for row level triggers.

Cause: The referencing clause specifies identical values for NEW and OLD.

Cause: The create TRIGGER statement is invalid.

Cause: The TRIGGER name is invalid.

Cause: The TRIGGER name or type already exists.

Cause: The trigger is accessing "new" or "old" values in a table trigger.

Cause: The variable referenced in the trigger body is invalid.

Cause: New trigger variables can only be changed in before row insert or update triggers.

Cause: Old values can only be read and not changed.

Cause: The trigger description is limited to 2000 characters (for dictionary storage reasons). The description does not include the text of the "when" clause or the text of the pl/sql code executed for the trigger.

Cause: Rowid's can only be read and not changed.

Cause: A runtime error occurred during execution of a trigger.

Cause: An attempt was made to create a trigger on an object owned by SYS.

Cause: Trigger is of duplicate event and trigger time.

Cause: A trigger (or a user defined plsql function that is referenced in this statement) attempted to look at (or modify) a table that was in the middle of being modified by the statement which fired it.

Cause: A trigger attempted to commit or rollback.

Cause: A trigger attempted to reference a long column in the triggering table.

Cause: A trigger attempted to modify a table that was constraining for some referential constraint of a parent SQL statement.

Cause: Cannot replace a trigger which already exists on a different table than the one being replaced.

Cause: A trigger's 'when' clause is limited to 2K for dictionary storage reasons. The trigger being created exceeded that size.

Cause: An attempt was made to concurrently perform two DDL operations on a trigger or trigger table.

Cause: A trigger was attempted to be retrieved for execution and was found to be invalid. This also means that compilation/authorization failed for the trigger.

Cause: A trigger was attempted to be retrieved for execution and was found to be valid, but not stored. This may mean the an upgrade was done improperly from a non-stored trigger release.