Oracle8 Error Messages Release 8.0.4 A58312-01 |
Library | Product | Contents | Index

## 14000-14119: Partitioned Objects - Parsing Messages

##### ORA-14000: only one LOCAL clause may be specified

Cause: A CREATE INDEX statement was issued that contained more than one LOCAL clause.

Action: Specify the LOCAL option at most once. Then retry the operation.

##### ORA-14001: LOCAL clause contradicts previously specified GLOBAL clause

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

Action: Specify either a LOCAL or a GLOBAL clause, but not both. Then retry the operation.

##### ORA-14002: only one GLOBAL clause may be specified

Cause: A CREATE INDEX statement contained more than one GLOBAL clause.

Action: Specify the GLOBAL option at most once. Then retry the operation.

##### ORA-14003: GLOBAL clause contradicts previously specified LOCAL clause

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

Action: Specify a GLOBAL or a LOCAL clause, but not both. Then retry the operation.

##### ORA-14004: missing PARTITION keyword

Cause: A statement was issued which was missing the keyword PARTITION.

Action: Supply the missing keyword and retry the operation.

##### ORA-14005: missing RANGE keyword

Cause: A statement was issued which was missing the keyword RANGE.

Action: Supply the missing keyword and retry the operation.

##### ORA-14006: invalid partition name

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

Action: Enter an appropriate partition name. Then retry the operation.

##### ORA-14007: missing LESS keyword

Cause: A statement was issued which was missing the keyword LESS.

Action: Supply the missing keyword. Then retry the operation.

##### ORA-14008: missing THAN keyword

Cause: A statement was issued which was missing the keyword THAN.

Action: Supply the missing keyword. Then retry the operation.

##### ORA-14009: partition bound may not be specified for a LOCAL index partition

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

Action: Remove all VALUES LESS THAN clauses from descriptions of LOCAL index partitions.

##### ORA-14010: this physical attribute may not be specified for an index partition

Cause: An unexpected option was encountered while parsing physical attributes of an index partition; valid options are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE. This message could also have resulted from omission of a terminating (right) parenthesis following the list of partition descriptions.

Action: Remove invalid option(s) from the list of physical attributes of an index partition.

##### ORA-14011: names assigned to resulting partitions must be distinct

Cause: The names given to partitions resulting from the splitting of an existing table or index partition were not distinct.

Action: Rename resulting partition(s) to ensure that their names are distinct and different from those of any other partition of the table or index.

##### ORA-14012: resulting partition name conflicts with that of an existing partition

Cause: Name of a partition resulting from splitting of an existing table or index partition was given a name identical to that of some other existing partition of that table or index.

Action: Rename resulting partition(s) to ensure that their names are distinct and different from those of any other partition of the table or index.

##### ORA-14013: duplicate partition name

Cause: Name given to a partition of a table or index being created was not unique.

Action: Rename partition(s) to ensure that their names are unique among partitions of the table or index being created.

##### ORA-14014: maximum number of partitioning columns is 16

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

Action: Modify the partitioning column list so that it consists of at most 16 columns.

##### ORA-14015: too many partition descriptions

Cause: CREATE TABLE or CREATE INDEX contained too many partition descriptions; maximum number of partitions is 2**32-1 (65535).

Action: Reduce the number of partitions so that they do not exceed 2**32-1 (65535).

##### ORA-14016: underlying table of a LOCAL partitioned index must be partitioned

Cause: An attempt was made to create a LOCAL partitioned index on a non-partitioned table. Only GLOBAL indices (partitioned or otherwise) can be created on a non-partitioned table.

Action: Correct the statement and retry the operation.

##### ORA-14017: partition bound list contains too many elements

Cause: A partition bound list contained more elements than there are partitioning columns.

Action: Ensure that the number of elements in the partition bound list is equal to the number of partitioning columns of the table or index. Then retry the operation.

##### ORA-14018: partition bound list contains too few elements

Cause: Partition bound list contained fewer elements than there are partitioning columns.

Action: Ensure that the number of elements in the partition bound list is equal to the number of partitioning columns of the table or index.

##### ORA-14019: partition bound element must be one of: string literal, number, or MAXVALUE

Cause: Partition bound list contained an element of invalid type (that is, not a number, non-empty string literal, or MAXVALUE).

Action: Ensure that all elements of partition bound list are of valid type.

##### ORA-14020: this physical attribute may not be specified for a table partition

Cause: An unexpected option was encountered while parsing physical attributes of a table partition; valid options are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE, and PCTUSED. This error also could have resulted from the omission of a terminating (right) parenthesis following the list of partition descriptions.

Action: Remove invalid option(s) from the list of physical attributes of a table partition.

##### ORA-14021: MAXVALUE must be specified for all columns

Cause: In the VALUES LESS THAN clause for the highest (last) partition of a GLOBAL index, MAXVALUE was not specified for all columns.

Action: Ensure that the VALUES LESS THAN clause for the last partition of a GLOBAL index has MAXVALUE specified for all columns.

##### ORA-14022: creation of LOCAL partitioned cluster indices is not supported

Cause: An attempt was made to create a LOCAL partitioned cluster index, which is currently illegal.

Action: Remove LOCAL along with partition descriptions, if any, from the CREATE INDEX statement.

##### ORA-14023: creation of GLOBAL partitioned cluster indices is not supported

Cause: An attempt was made to create a GLOBAL partitioned cluster index, which is currently illegal.

Action: Remove PARTITION BY RANGE clause along with partition descriptions from the CREATE INDEX statement.

##### ORA-14024: number of partitions of LOCAL index must equal that of the underlying table

Cause: An attempt was made to create a LOCAL partitioned index with a number of partitions which is different from that of the underlying table.

Action: Correct the CREATE INDEX statement to specify a correct number of partitions and retry the operation.

##### ORA-14025: PARTITION may not be specified for a snapshot or a snapshot log

Cause: PARTITION option was encountered while parsing a definition of a snapshot or a snapshot log.

Action: Ensure that the definition of a SNAPSHOT does not include invalid options and retry the operation.

##### ORA-14026: PARTITION and CLUSTER clauses are mutually exclusive

Cause: The definition of a table contained both PARTITION and CLUSTER clauses which is illegal.

Action: Remove one of the conflicting clauses and retry the operation.

##### ORA-14027: only one PARTITION clause may be specified

Cause: A CREATE TABLE statement contained more than one PARTITION clause.

Action: Specify the PARTITION option at most once and retry the operation.

##### ORA-14028: missing AT keyword

Cause: A statement was issued that was missing the keyword AT.

Action: Supply the missing keyword and retry the operation.

##### ORA-14029: GLOBAL partitioned index must be prefixed

Cause: The partitioning columns of a global partitioned index did not contain a prefix of the index's key columns.

Action: Ensure that the GLOBAL partitioned index being created is prefixed and retry the operation.

##### ORA-14030: non-existent partitioning column in CREATE TABLE statement

Cause: The partitioning column specified in the CREATE TABLE statement is not one of columns of the table being created.

Action: Ensure that all columns in the partitioning column list are columns of the table being created. Then retry the operation.

##### ORA-14031: partitioning column may not be of type LONG or LONG RAW

Cause: The partitioning column specified was of type LONG or LONG RAW, which is illegal.

Action: Ensure that no partitioning column is of type LONG or LONG RAW. Then retry the operation.

##### ORA-14032: partition bounds of partition number num are too high

Cause: High bound of the partition whose number (partitions are numbered starting with 1) is displayed in this message did not collate lower than that of the following partition, which is illegal.

Action: Ensure that high bound of every partition (except for the last one) collates lower than that of a following partition. Then retry the operation.

##### ORA-14036: partition bound value too large for column

Cause: Length of partition bound value is longer than that of the corresponding partitioning column.

Action: Ensure that lengths of the high bound values do not exceed those of corresponding partitioning columns. Then retry the operation.

##### ORA-14037: partition bounds of partition name are too high

Cause: High bound of the partition whose name (explicitly specified by the user) is displayed in this message did not collate lower than that of the following partition, which is illegal.

Action: Ensure that the high bound of every partition (except for the last one) collates lower than that of a following partition.

##### ORA-14038: GLOBAL partitioned index must be prefixed

Cause: An attempt was made to create a GLOBAL non-prefixed partitioned index which is illegal.

Action: If a non-prefixed index is desired, it must be created as LOCAL; otherwise, correct the list of key and/or partitioning columns to ensure that the index is prefixed. Then retry the operation.

##### ORA-14039: partitioning columns must form a subset of key columns of a UNIQUE index

Cause: An attempt was made to create a UNIQUE partitioned index whose partitioning columns do not form a subset of its key columns.

Action: If an index whose partitioning columns do not form a subset of its key columns is indeed desired, it must be created as non-UNIQUE; otherwise, correct the list of key and/or partitioning columns to ensure that the index's partitioning columns form a subset of its key columns. Then retry the operation.

##### ORA-14041: partition bound may not be specified for resulting partitions

Cause: While parsing an ALTER {TABLE|INDEX} SPLIT PARTITION statement, a resulting partition was found to contain a VALUES LESS THAN clause which is illegal.

Action: Remove the VALUES LESS THAN clause from the description(s) of partitions which result from splitting an existing table or index partition. Then retry the operation.

##### ORA-14042: partition bound may not be specified for a partition being moved, modified or rebuilt

Cause: While parsing an ALTER {TABLE|INDEX} MODIFY PARTITION, ALTER TABLE MOVE PARTITION, or ALTER INDEX REBUILD PARTITION statement, the description of new physical attributes of the partition being moved, modified, or rebuilt was found to contain VALUES LESS THAN clause which is illegal.

Action: Remove the VALUES LESS THAN clause from the description of new attributes of the partition being moved, modified, or rebuilt. Then retry the operation.

##### ORA-14043: only one partition may be added

Cause: The ALTER TABLE ADD PARTITION statement contained descriptions of more than one partition to be added.

Action: Ensure that the statement contains exactly one partition definition and that it does not contain any commas. Then retry the operation.

##### ORA-14044: only one partition may be moved

Cause: The ALTER TABLE MOVE PARTITION statement contained descriptions of more than one partition to be moved.

Action: Ensure that the statement describes exactly one partition to be moved and that it does not contain any commas. Then retry the operation.

##### ORA-14045: only one partition may be modified

Cause: The ALTER TABLE|INDEX MODIFY PARTITION statement contained descriptions of more than one partition to be modified.

Action: Ensure that the statement describes exactly one partition to be modified and that it does not contain any commas.

##### ORA-14046: a partition may be split into exactly two new partitions

Cause: The ALTER TABLE|INDEX SPLIT PARTITION did not contain descriptions of exactly two new partitions into which an existing table or index partition was to be split.

Action: Ensure that the statement describes exactly two partition into which an existing partition is to be split. Then retry the operation.

##### ORA-14047: ALTER TABLE|INDEX RENAME may not be combined with other operations

Cause: The ALTER TABLE or ALTER INDEX statement attempted to combine a RENAME operation with some other operation, which is illegal.

Action: Ensure that RENAME operation is the sole operation specified in ALTER TABLE or ALTER INDEX statement. Then retry the operation.

##### ORA-14048: a partition maintenance operation may not be combined with other operations

Cause: The ALTER TABLE or ALTER INDEX statement attempted to combine a partition maintenance operation (for example, MOVE PARTITION) with some other operation (for example, ADD PARTITION or PCTFREE) which is illegal.

Action: Ensure that a partition maintenance operation is the sole operation specified in an ALTER TABLE or ALTER INDEX statement; operations other than those dealing with partitions, default attributes of partitioned tables/indices, or specifying that a table be renamed (ALTER TABLE RENAME) can be combined.

##### ORA-14049: invalid ALTER TABLE MODIFY PARTITION option

Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, BACKUP, ALLOCATE EXTENT, or DEALLOCATE UNUSED was specified in an ALTER TABLE MODIFY PARTITION statement.

Action: Specify only legal options, then retry the operation.

##### ORA-14050: invalid ALTER INDEX MODIFY PARTITION option

Cause: An option other than INITRANS, MAXTRANS, STORAGE, or DEALLOCATE UNUSED was specified in an ALTER INDEX MODIFY PARTITION statement.

Action: Specify only legal options, then retry the operation.

##### ORA-14051: invalid ALTER SNAPSHOT option

Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, or BACKUP was specified in an ALTER SNAPSHOT statement.

Action: Specify only legal options, then retry the operation.

##### ORA-14052: partition-extended table name syntax is disallowed in this context

Cause: An attempt was made to use partition-extended table name syntax in illegal context (that is, not in a FROM-clause or INSERT, DELETE, or UPDATE statement).

Action: Avoid use of partition-extended table name in contexts other than those mentioned above.

##### ORA-14053: illegal attempt to modify name in name statement

Cause: An attempt was made to modify an attribute (for example, a table) with the ALTER statement at creation time.

Action: Ensure that ALTER statement specifies new values only for attributes which can be changed after an object has been created.

##### ORA-14054: invalid ALTER TABLE TRUNCATE PARTITION option

Cause: An attempt was made to specify an invalid option following the partition name in the ALTER TABLE TRUNCATE PARTITION statement. The name of the partition to be truncated can be followed only by DROP STORAGE or REUSE STORAGE.

Action: Ensure that no options besides DROP STORAGE or REUSE STORAGE are specified with ALTER TABLE TRUNCATE PARTITION.

##### ORA-14055: keyword REBUILD in ALTER INDEX REBUILD must immediately follow name

Cause: The ALTER INDEX statement contained the REBUILD keyword following an index attribute (for example, INITRANS).

Action: Ensure that the keyword REBUILD immediately follows the name of the index being altered.

##### ORA-14056: partition number num: sum of PCTUSED and PCTFREE may not exceed 100

Cause: The sum of PCTUSED and PCTFREE for a partition whose number (partitions are numbered starting with 1) is displayed in this message exceeds 100. Note that if PCTUSED and/or PCTFREE values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default PCTUSED and/or PCTFREE values for the partitioned table or index were not specified, system defaults would be used.

Action: Ensure that a sum of PCTUSED and PCTFREE for the partition does not exceed 100. Then retry the operation.

##### ORA-14057: partition name: sum of PCTUSED and PCTFREE may not exceed 100

Cause: The sum of PCTUSED and PCTFREE for a partition whose name is displayed in this message exceeds 100. Note that if PCTUSED and/or PCTFREE values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default PCTUSED and/or PCTFREE values for the partitioned table or index were not specified, system defaults would be used.

Action: Ensure that a sum of PCTUSED and PCTFREE for the partition does not exceed 100. Then retry the operation.

##### ORA-14058: partition number num: INITRANS value must be less than MAXTRANS value

Cause: The value of INITRANS was found to be greater than that of MAXTRANS for a partition whose number (partitions are numbered starting with 1) is displayed in this message. Note that if INITRANS and/or MAXTRANS values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default INITRANS and/or MAXTRANS values for the partitioned table or index were not specified, system defaults would be used.

Action: Ensure that value of INITRANS (whether specified explicitly or derived from the default value for the partitioned table or index) is no greater than that of MAXTRANS. Then retry the operation.

##### ORA-14059: partition name: INITRANS value must be less than MAXTRANS value

Cause: The value of INITRANS was found to be greater than that of MAXTRANS for a partition whose name is displayed in this message. Note that if INITRANS and/or MAXTRANS values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default INITRANS and/or MAXTRANS values for the partitioned table or index were not specified, system defaults would be used.

Action: Ensure that value of INITRANS (whether specified explicitly or derived from the default value for the partitioned table or index) is no greater than that of MAXTRANS.

##### ORA-14060: data type or length of a table partitioning column may not be changed

Cause: An attempt was made to use the ALTER TABLE statement to modify data type and/or length of a column used to partition the table named in the ALTER TABLE statement.

Action: Avoid modifying data type and/or length of table partitioning column(s).

##### ORA-14061: data type or length of an index partitioning column may not be changed

Cause: An attempt was made to use the ALTER TABLE statement to modify data type and/or length of a column used to partition some index defined on the table named in the ALTER TABLE statement.

Action: Avoid modifying the data type and/or length of index partitioning column(s).

##### ORA-14062: one or more of table's partitions reside in a read-only tablespace

Cause: An attempt was made to use the ALTER TABLE statement modify an existing VARCHAR2 (or VARCHAR) column to be of type CHAR (or CHARACTER), increase length of an existing CHAR (or CHARACTER) column, or add a column with user-specified default for a table that has one or more partitions residing in read-only tablespaces.

Action: Avoid performing these operations on a partitioned table that has one or more partitions residing in read-only tablespaces.

##### ORA-14063: unusable index exists on unique/primary constraint key

Cause: An attempt was made to add or enable a primary key/unique constraint on column(s) of a table that has an index marked Index Unusable.

Action: Drop the existing index or rebuild it using ALTER INDEX REBUILD.

##### ORA-14064: index with Unusable partition exists on unique/primary constraint key

Cause: An attempt was made to add or enable a primary key/unique constraint on column(s) of a table on which there exists an index that has one or more partitions marked Index Unusable.

Action: Drop the existing index or rebuild unusable partitions it using ALTER INDEX REBUILD PARTITION.

##### ORA-14065: ALLOCATE STORAGE may not be specified for a partitioned table

Cause: An attempt was made to specify an ALLOCATE STORAGE clause in an ALTER TABLE statement issued against a partitioned table.

Action: Remove the ALLOCATE STORAGE option. If it is desired to add storage to individual partitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE MODIFY PARTITION statement.

##### ORA-14066: Illegal option for a non-partitioned table

Cause: An attempt was made to issue an ALTER TABLE statement containing an option (such as TABLESPACE and INITIAL, FREELISTS, and FREELIST GROUPS inside STORAGE clauses) for a non-partitioned table. These options are permitted only for partitioned tables.

Action: Remove the illegal option(s) and retry the operation.

##### ORA-14067: duplicate TABLESPACE_NUMBER specification

Cause: A TABLESPACE_NUMBER clause was specified more than once for an index or an index partition.

Action: Correct the code generating text of the CREATE INDEX statement sent to the slaves, then retry the operation.

##### ORA-14068: TABLESPACE and TABLESPACE_NUMBER may not be both specified

Cause: An attempt was made to specify both TABLESPACE and TABLESPACE_NUMBER clauses for an index or an index partition.

Action: Correct the code generating text of the CREATE INDEX statement sent to the slaves, then retry the operation.

##### ORA-14069: invalid TABLESPACE_NUMBER value

Cause: An attempt was made to specify a TABLESPACE_NUMBER value which is not an integer between 0 and 0x7FFFFFFF.

Action: Correct the code generating text of the CREATE INDEX statement sent to the slaves, then retry the operation.

##### ORA-14070: option may be specified only for partitioned indices or with REBUILD

Cause: An attempt was made to issue an ALTER INDEX statement containing an option (such as PCTFREE, TABLESPACE, [NO]PARALLEL and INITIAL, FREELISTS, and FREELIST GROUPS inside STORAGE clause) which are permitted only for partitioned indices or in conjunction with REBUILD.

Action: Remove illegal option(s) and retry the operation.

##### ORA-14071: invalid option for an index used to enforce a constraint

Cause: An option other than COMPRESS, NOCOMPRESS, PCTFREE, INITRANS, MAXTRANS, STORAGE, TABLESPACE, PARALLEL, NOPARALLEL, RECOVERABLE, UNRECOVERABLE, LOGGING, NOLOGGING, LOCAL, or GLOBAL was specified for an index used to enforce a constraint.

Action: Choose one of the valid index options and retry the operation.

##### ORA-14072: fixed table may not be truncated

Cause: An attempt was made to truncate a fixed table. Fixed tables cannot be truncated.

Action: Ensure that the table being truncated is not a fixed table.

##### ORA-14073: bootstrap table or cluster may not be truncated

Cause: An attempt was made to truncate a bootstrap table or cluster. Bootstrap tables or clusters cannot be truncated.

Action: Ensure that the table (or cluster) being truncated is not a bootstrap table (or cluster).

##### ORA-14074: partition bound for partition maintenance operation are too low

Cause: Partition bound for SPLIT or ADD partition operation did not collate higher than the partition bound of previous partition.

Action: Ensure that the partition bound of every partition (except the first one) collates higher than that of the previous partition.

##### ORA-14075: partition maintenance operations may only be performed on partitioned indices

Cause: The index named in the ALTER INDEX partition maintenance operation is not partitioned, making a partition maintenance operation meaningless.

Action: Ensure that the index named in the ALTER INDEX statement specifying a partition maintenance operation is partitioned.

##### ORA-14076: DROP/SPLIT PARTITION may not be applied to a LOCAL index partition

Cause: An attempt was made to drop or split a partition of a LOCAL index.

Action: Ensure that the index named in the DROP/SPLIT PARTITION statement is a GLOBAL partitioned index.

##### ORA-14077: specified partition does not exist

Cause: An attempt was made to perform a partition maintenance operation involving a non-existent partition.

Action: Ensure that the partitioned object (table or index) named in the ALTER TABLE/INDEX statement contains a specified partition.

##### ORA-14078: you may not drop the highest partition of a GLOBAL index

Cause: An attempt was made to drop highest partition of a GLOBAL index.

Action: Ensure that the partition specified in ALTER INDEX DROP PARTITION statement is not the highest partition of the index.

##### ORA-14079: illegal option for a partition marked Index Unusable

Cause: The ALTER INDEX MODIFY PARTITION statement issued against an index partition marked Index Unusable contained STORAGE and/or DEALLOCATE SPACE clauses.

Action: Ensure that only valid options are specified, then retry the operation.

##### ORA-14080: partition cannot be split along the specified high bound

Cause: An attempt was made to split a partition along a bound which either collates higher than that of the partition to be split, or lower than that of a partition immediately preceding the one to be split.

Action: Ensure that the bound along which a partition is to be split collates lower than that of the partition to be split and higher than that of a partition immediately preceding the one to be split.

##### ORA-14081: new partition name must differ from the old partition name

Cause: An attempt was made to enter a ALTER TABLE/INDEX RENAME PARTITION statement specifying a partition name identical to the name of the partition being renamed.

Action: Ensure that the new partition name is different from the name of any (including the one being renamed) existing partition of a given table or index.

##### ORA-14082: new partition name must differ from that of any other partition of the object

Cause: An attempt was made to enter a ALTER TABLE/INDEX RENAME PARTITION statement specifying a partition name identical to the name of some existing partition of the object.

Action: Ensure that the new partition name is different from the name of any (including the one being renamed) existing partition of a given table or index.

##### ORA-14083: cannot drop the only partition of a partitioned table

Cause: A drop partition command was executed when there is only one partition in the table.

Action: Ensure that there is more than one partition. Drop the table to remove all partitions.

##### ORA-14084: you may specify TABLESPACE DEFAULT only for a LOCAL index

Cause: An attempt was made to specify TABLESPACE DEFAULT for an object other than a LOCAL index.

Action: Reenter the statement without the TABLESPACE DEFAULT clause.

##### ORA-14085: partitioned table cannot have column with LONG datatype

Cause: An attempt was made either to create a partitioned table with a LONG datatype or to add a LONG datatype column to a partitioned table.

Action: LONG data types are not supported with partitioned tables. Create a table without the LONG column or change the table to not-partitioned. If adding a column, do not use the LONG datatype. If modifying attributes of a column to change data type to LONG, it has to be a non-partitioned table.

##### ORA-14086: a partitioned index may not be rebuilt as a whole

Cause: An attempt was made to rebuild a partitioned index using the ALTER INDEX REBUILD statement.

Action: Rebuild the index one partition at a time (using ALTER INDEX REBUILD PARTITION) or drop and recreate the entire index.

##### ORA-14094: invalid ALTER TABLE EXCHANGE PARTITION option

Cause: Name of the table to be EXCHANGED was not followed by the [{INCLUDING|EXCLUDING} INDEX][{WITH|WITHOUT} VALIDATION] statement.

Action: Ensure that no options besides INCLDING INDEX or EXCLUDING INDEX are specified with ALTER TABLE EXCHANGE PARTITION.

##### ORA-14095: ALTER TABLE EXCHANGE requires a non-partitioned, non-clustered table

Cause: An attempt was made to perform the EXCHANGE operation on a clustered or partitioned table.

Action: Ensure that the table being exchanged with the partition is not partitioned or clustered.

##### ORA-14096: tables in ALTER TABLE EXCHANGE PARTITION must have the same number of columns

Cause: The two tables specified in the EXCHANGE statement have a different number of columns.

Action: Ensure that the two tables have the same number of columns with the same type and size.

##### ORA-14097: column type or size mismatch in ALTER TABLE EXCHANGE PARTITION

Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION are of different type or size.

Action: Ensure that the two tables have the same number of columns with the same type and size.

##### ORA-14098: index mismatch for tables in ALTER TABLE EXCHANGE PARTITION

Cause: The two tables specified in the EXCHANGE statement have indexes which are not equivalent.

Action: Ensure that the indexes for the two tables have indexes which follow this rule: for every non-partitioned index for the non-partitioned table, there has to be an identical LOCAL index on the partitioned table and vice versa. By identical, the column position, type and size have to be the same.

##### ORA-14099: all rows in table do not qualify for specified partition

Cause: It was detected that at least one row in the non-partitioned table does not qualify for the partition specified in the ALTER TABLE EXCHANGE PARTITION.

Action: Ensure that all the rows in the segment qualify for the partition. Perform the ALTER TABLE operation with the NO CHECKING option. Run ANALYZE table VALIDATE on that partition to find out the invalid rows and delete them.

##### ORA-14100: partition extended table name cannot refer to a remote object

Cause: An attempt was made to use partition-extended table name syntax in conjunction with a remote object name.

Action: Correct the statement and retry the operation.

##### ORA-14101: partition extended table name cannot refer to a synonym

Cause: An attempt was made to use partition-extended table name syntax in conjunction with a synonym name.

Action: Correct the statement and retry the operation.

##### ORA-14102: only one LOGGING or NOLOGGING clause may be specified

Cause: LOGGING was specified more than once, NOLOGGING was specified more than once, or both LOGGING and NOLOGGING were specified.

Action: Remove all but one of the LOGGING or NOLOGGING clauses and reissue the statement.

##### ORA-14103: LOGGING/NOLOGGING may not be combined with RECOVERABLE/UNRECOVERABLE

Cause: A statement contained both [NO]LOGGING and [UN]RECOVERABLE clauses which is not allowed.

Action: Remove one of the offending clauses. [UN]RECOVERABLE is being deprecated in V8. To duplicate the semantics of the UNRECOVERABLE clause, create an object with the NOLOGGING option and then ALTER it specifying LOGGING. To duplicate semantics of RECOVERABLE clause, create an object with the LOGGING option.

##### ORA-14104: RECOVERABLE/UNRECOVERABLE may not be specified for partitioned tables/indices

Cause: The CREATE TABLE/INDEX statement used to create a partitioned table/index contained a RECOVERABLE or UNRECOVERABLE clause.

Action: Remove the offending clause. [UN]RECOVERABLE is being deprecated in V8. To duplicate the semantics of the UNRECOVERABLE clause, create an object with the NOLOGGING option and then ALTER it specifying LOGGING. To duplicate the semantics of the RECOVERABLE clause, create an object with the LOGGING option.

##### ORA-14105: RECOVERABLE/UNRECOVERABLE may not be specified in this context

Cause: RECOVERABLE/UNRECOVERABLE clause is not allowed in this context.

Action: Remove the offending clause. RECOVERABLE/UNRECOVERABLE may only be specified in CREATE TABLE/INDEX statement describing a non-partitioned table or index and ALTER INDEX REBUILD statement. [UN]RECOVERABLE is being deprecated in V8. To duplicate the semantics of the UNRECOVERABLE clause, create an object with the NOLOGGING option and then ALTER it specifying LOGGING. To duplicate the semantics of the RECOVERABLE clause, create an object with the LOGGING option.

##### ORA-14106: LOGGING/NOLOGGING may not be specified for a clustered table

Cause: An attempt was made to specify a LOGGING or NOLOGGING clause in a CREATE TABLE or ALTER TABLE statement involving a clustered table.

Action: Remove offending clause and retry the operation.

##### ORA-14107: partition specification is required for a partitioned object

Cause: A parameter which supplies the partition name was not entered. This parameter is optional for non-partitioned objects, but is required for partitioned objects.

Action: Supply the missing parameter and retry the operation.

##### ORA-14108: illegal partition-extended table name syntax

Cause: An attempt was made to use a partition number or a bind variable. A partition to be accessed can only be specified using its name.

Action: Modify the statement so that the partition is referred to by its name.

##### ORA-14109: partition-extended object names may only be used with tables

Cause: An attempt was made to use a partition-extended object name with an object which is not a table.

Action: Avoid using partition-extended name syntax with objects which are not tables.

##### ORA-14110: partitioning column may not be of type ROWID

Cause: The specified partitioning column was of type ROWID.

Action: Ensure that no partitioning column is of type ROWID, then retry the operation.

##### ORA-14111: creation of GLOBAL partitioned indices on clustered tables is not supported

Cause: An attempt was made to create a GLOBAL partitioned index on a clustered table which is currently illegal.

Action: Remove PARTITION BY RANGE() clause along with the partition-list to create a GLOBAL non-partitioned index on a clustered table.

##### ORA-14112: RECOVERABLE/UNRECOVERABLE may not be specified for a partition

Cause: Description of a partition found in CREATE TABLE/INDEX statement contained a RECOVERABLE or UNRECOVERABLE clause.

Action: Remove the offending clause. Use LOGGING or NOLOGGING instead and retry the operation.

##### ORA-14113: partitioned table cannot have column with LOB datatype

Cause: An attempt was made either to create a partitioned table with a LOB datatype or to add a LOB datatype column to a partitioned table.

Action: LOB data types are not supported with partitioned tables. Create table without the LOB column or change the table to non-partitioned. If adding a column, do not use LOB datatype. If modifying attributes of a column to change data type to LOB, it has to be a non-partitioned table.

##### ORA-14114: partitioned table cannot have column with ADT, REF, nested table, array datatype

Cause: An attempt was made either to create a partitioned table with an OBJECT datatype (ADT, REF, nested table, array) or to add an OBJECT datatype column to a partitioned table.

Action: Object data types are not supported with partitioned tables. Create the table without the Object column or change the table to non-partitioned. If adding a column, do not use OBJECT datatypes. If modifying attributes of a column to change data type to OBJECT, it has to be a non-partitioned table.

##### ORA-14115: partition bound of partition number num is too long

Cause: Length of linear key representation of a high bound of the partition whose number (partitions are numbered starting with 1) is displayed in this message exceeded the legal limit (4K).

Action: Change representation of a partition high bound to bring its length within legal limit.

##### ORA-14116: partition bound of partition num is too long

Cause: Length of linear key representation of a high bound of the partition whose name (explicitly specified by the user) is displayed in this message exceeded the legal limit (4K).

Action: Change representation of a partition high bound to bring its length within legal limit.

##### ORA-14117: partition resides in offlined tablespace

Cause: User attempted an operation requiring that we access data in a partition which resides in a tablespace which was taken offline. Such operations include trying to drop a tablespace of a table which has indices defined on it or is referenced by a constraint.

Action: Bring tablespace online before attempting the operation.

##### ORA-14118: CHECK constraint mismatch in ALTER TABLE EXCHANGE PARTITION

Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION statement have a CHECK constraint defined on them.

Action: Ensure that the two tables do not have a CHECK constraint defined on any column.

##### ORA-14119: specified partition bound is too long

Cause: Length of a linear key representation of a high bound of a table partition being added or along which an existing table or index partition is being split exceeded the legal limit (4K).

Action: Change representation of a partition high bound to bring its length within legal limit.

##### ORA-14120: incompletely specified partition bound for a DATE column

Cause: An attempt was made to use a date expression whose format does not fully (i.e. day, month, and year (including century)) specify a date as a partition bound for a DATE column. The format may have been specified explicitly (using TO_DATE() function) or implicitly (NLS_DATE_FORMAT).

Action: Ensure that date format used in a partition bound for a DATE column supports complete specification of a date (i.e. day, month, and year (including century)). If NLS_DATE_FORMAT does not support complete (i.e. including the century) specification of the year, use TO_DATE() (e.g. TO_DATE('01-01-1999', 'MM-DD-YYYY') to fully express the desired date.

##### ORA-14121: MODIFY DEFAULT ATTRIBUTES may not be combined with other operations

Cause: ALTER TABLE or ALTER INDEX statement attempted to combine MODIFY DEFAULT ATTRIBUTES with some other operation (for example, ADD PARTITION or PCTFREE) which is illegal.

Action: Ensure that MODIFY DEFAULT ATTRIBUTES is the sole operation specified in ALTER TABLE or ALTER INDEX statement; operations other than those dealing with partitions, default attributes of partitioned tables/indices, or specifying that a table be renamed (ALTER TABLE RENAME) may be combined.

##### ORA-14122: only one REVERSE or NOREVERSE clause may be specified

Cause: Both REVERSE and NOREVERSE were specified in CREATE INDEX statement..

Action: Remove all but one of the REVERSE or NOREVERSE clauses and reissue the statement.

##### ORA-14123: duplicate NOREVERSE clause

Cause: NOREVERSE was specified more than once in ALTER INDEX statement.

Action: Remove all but one of the NOREVERSE clauses and reissue the statement.

##### ORA-14124: duplicate REVERSE clause

Cause: REVERSE was specified more than once in ALTER INDEX or CREATE INDEX statements.

Action: Remove all but one of the REVERSE clauses and reissue the statement.

##### ORA-14125: REVERSE/NOREVERSE may not be specified in this context

Cause: REVERSE/NOREVERSE clause is not allowed in this context.

Action: Remove offending clause. REVERSE may be specified as an attribute of an index (not of an individual partition, if creating a partitioned index) in CREATE INDEX statement and ALTER INDEX REBUILD statement. NOREVERSE may be specified only in ALTER INDEX REBUILD statement.

##### ORA-14126: only a <parallel clause> may follow description(s) of resulting partitions

Cause: Descriptions of partition(s) resulting from splitting of a table or index partition may be followed by an optional <parallel clause> which applies to the entire statement and which, in turn, may not be followed by any other clause.

Action: Ensure that all partition attributes appear within the parenthesized list of descriptions of resulting partitions in ALTER TABLE/INDEX SPLIT PARTITION statement.

##### ORA-14128: FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE PARTITION

Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION statement have different FOREIGN KEY constraints.

Action: Ensure that the two tables do not have FOREIGN KEY constraints defined on any column or disable all FOREIGN KEY constraints on both tables. Then retry the operation.

Prev | Top | Next
| Copyright © 1997 Oracle Corporation. All Rights Reserved. |
Library | Product | Contents | Index