ORA-14294: Number of partitions does not match number of subpartitions

ORA-14294: Number of partitions does not match number of subpartitions

Cause: When exchanging a partitioned table with a composite partition the number of partitions of the table must match the number of subpartitions of the composite partition.

Action: Ensure that the number of partitions in the partitioned table is the same as the number of subpartitions in the the composite partition.

ORA-14293: Number of partitioning columns does not match number of subpartitioning columns

ORA-14293: Number of partitioning columns does not match number of subpartitioning columns

Cause: When exchanging a partitioned table with a composite partition the number of partitioning columns of the table must match the number of subpartitioning columns of the composite partition.

Action: Ensure that the number of partitioning columns in the partitioned table is the same as the number of subpartitioning columns in the the composite partition.

ORA-14292: Partitioning type of table must match subpartitioning type of composite partition

ORA-14292: Partitioning type of table must match subpartitioning type of composite partition

Cause: When exchanging a partitioned table with a composite partition the partitioning type of the table must match the subpartitioning type of the composite partition.

Action: Ensure that the partitioning type of partitioned table is the same as the subpartitioning type of the composite partition.

ORA-14291: cannot EXCHANGE a composite partition with a non-partitioned table

ORA-14291: cannot EXCHANGE a composite partition with a non-partitioned table

Cause: A composite partition can only be exchanged with a partitioned table.

Action: Ensure that the table being exchanged is partitioned or that that the partition being exchanged is non-composite.

ORA-14290: PRIMARY KEY constraint mismatch in ALTER TABLE EXCHANGE (SUB(PARTITION

ORA-14290: PRIMARY KEY constraint mismatch in ALTER TABLE EXCHANGE (SUB(PARTITION

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

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

ORA-14289: cannot make local index partition of Composite Range partitioned table unusable

ORA-14289: cannot make local index partition of Composite Range partitioned table unusable

Cause: User attempted to rebuild a partition of a Composite Range partitioned index which is illegal

Action: none

ORA-14288: index is not partitioned by Composite Range method

ORA-14288: index is not partitioned by Composite Range method

Cause: The index in a partition or subpartition maintenance operation (ALTER INDEX MODIFY (SUBPARTITION|DEFAULT ATTRIBUTES FOR PARTITION( or ALTER INDEX REBUILD SUBPARTITION command must be partitioned by Composite Range method

Action: none

ORA-14287: cannot REBUILD a partition of a Composite Range partitioned index

ORA-14287: cannot REBUILD a partition of a Composite Range partitioned index

Cause: User attempted to rebuild a partition of a Composite Range partitioned index which is illegal

Action: REBUILD the index partition, a subpartition at a time

ORA-14286: cannot COALESCE the only subpartition of this table partition

ORA-14286: cannot COALESCE the only subpartition of this table partition

Cause: A COALESCE SUBPARTITION command was issued when there is only one subpartition in the partition which is illegal

Action: Ensure that there is at least one subpartition. Drop partition to remove all subpartitions.

ORA-14285: cannot COALESCE the only partition of this hash partitioned table or index

ORA-14285: cannot COALESCE the only partition of this hash partitioned table or index

Cause: A COALESCE PARTITION command was issued when there is only one partition in the table or index, which is illegal

Action: Ensure that there is at least one partition. Drop the table or index to remove all partitions.

ORA-14284: one or more of table s subpartitions reside in a read-only tablespace

ORA-14284: one or more of table s subpartitions reside in a read-only tablespace

Cause: User issued ALTER TABLE statement attempting to 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 one or more subpartitions of which reside in read-only tablespaces, which is illegal

Action: Avoid performing aformentioned operations on a partitioned table one or more subpartitions of which reside in read-only tablespaces

ORA-14283: UNIQUE constraints mismatch in ALTER TABLE EXCHANGE SUBPARTITION

ORA-14283: UNIQUE constraints mismatch in ALTER TABLE EXCHANGE SUBPARTITION

Cause: One of the tables named in the ALTER TABLE EXCHANGE SUBPARTITION command has a UNIQUE constraint for which no matching (vis-a-vis key columns) constraint is defined on the other table or a matching constraint is defined on the other table, but it differs from that defined on the first table vis-a-vis being enabled and or or validated.

Action: Ensure that for every UNIQUE constraint defined on one of the tables named in the ALTER TABLE EXCHANGE SUBPARTITION statement there is a matching (vis-a-vis key columns and being enabled and or or validated) UNIQUE constraint defined on the other table. If UNIQUE constrains are enabled, UNIQUE constraints on the partitioned table should be enforced using local indexes.

ORA-14282: FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION

ORA-14282: FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION

Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE SUBPARTITION 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.

ORA-14281: CHECK constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION

ORA-14281: CHECK constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION

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

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

ORA-14280: all rows in table do not qualify for specified subpartition

ORA-14280: all rows in table do not qualify for specified subpartition

Cause: There is at least one row in the non partitioned table which does not qualify for the subpartition specified in the ALTER TABLE EXCHANGE SUBPARTITION

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

ORA-14279: index mismatch for tables in ALTER TABLE EXCHANGE SUBPARTITION

ORA-14279: index mismatch for tables in ALTER TABLE EXCHANGE SUBPARTITION

Cause: The two tables specified in the ALTER TABLE EXCHANGE SUBPARTITION 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-14278: column type or size mismatch in EXCHANGE SUBPARTITION

ORA-14278: column type or size mismatch in EXCHANGE SUBPARTITION

Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE SUBPARTITION 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-14277: tables in EXCHANGE SUBPARTITION must have the same number of columns

ORA-14277: tables in EXCHANGE SUBPARTITION must have the same number of columns

Cause: The two tables specified in the ALTER TABLE EXCHANGE SUBPARTITION have different number of columns

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

ORA-14276: EXCHANGE SUBPARTITION requires a non-partitioned, non-clustered table

ORA-14276: EXCHANGE SUBPARTITION requires a non-partitioned, non-clustered table

Cause: The table in the ALTER TABLE EXCHANGE SUBPARTITION operation is either clustered or partitioned

Action: Ensure that the table with which the subpartition is being exchanged for is not partitioned or clustered.

ORA-14275: cannot reuse lower-bound partition as resulting partition

ORA-14275: cannot reuse lower-bound partition as resulting partition

Cause: User attempt to reuse lower-bound partition of the partitions being merged which is illegal

Action: Specify new resulting partition name or reuse the higher-bound partition only

ORA-14274: partitions being merged are not adjacent

ORA-14274: partitions being merged are not adjacent

Cause: User attempt to merge two partitions that are not adjacent to each other which is illegal

Action: Specify two partitions that are adjacent

ORA-14273: lower-bound partition must be specified first

ORA-14273: lower-bound partition must be specified first

Cause: User specified higher-bound partition before lower-bound partition in ALTER TABLE MERGE PARTITIONS statement which is illegal

Action: Specify lower-bound partition then higher-bound partition

ORA-14272: only a partition with higher bound can be reused

ORA-14272: only a partition with higher bound can be reused

Cause: User attempt to reuse a lower-bound partition in ALTER TABLE MERGE PARTITIONS statement as the resulting partition which is illegal.

Action: Use the higher-bound partition to be the resulting partition or specify a new partition name

ORA-14271: table is not partitioned by Composite Range method

ORA-14271: table is not partitioned by Composite Range method

Cause: The table in ALTER TABLE MODIFY SUBPARTITION { UNUSABLE LOCAL INDEXES | REBUILD UNUSABLE LOCAL INDEXES } statement is not partitioned by Composite Range method which is illegal.

Action: Ensure that the table is partitioned by Composite Range method

ORA-14270: table is not partitioned by Range or Hash or List method

ORA-14270: table is not partitioned by Range or Hash or List method

Cause: The table in ALTER TABLE MODIFY PARTITION { UNUSABLE LOCAL INDEXES | REBUILD UNUSABLE LOCAL INDEXES } statement is not partitioned by Range or Hash method which is illegal.

Action: Ensure that the table is partitioned by Range or Hash method

ORA-14269: cannot exchange partition other than a Range or Hash partition

ORA-14269: cannot exchange partition other than a Range or Hash partition

Cause: User attempt to exchange a partition with a non-partitioned table but the specified partition is not a Range or Hash partition which is illegal

Action: Specify EXCHANGE PARTITION for a Range or Hash partition only

ORA-14268: subpartition string of the partition resides in offlined tablespace

ORA-14268: subpartition string of the partition resides in offlined tablespace

Cause: User attempted an operation requiring that we access data in a subpartition 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-14267: cannot specify PARALLEL clause when adding a (Composite) Range partition

ORA-14267: cannot specify PARALLEL clause when adding a (Composite) Range partition

Cause: User issued ALTER TABLE ADD PARTITION statement with PARALLEL clause for a Range or Composite Range partition which is illegal

Action: Remove the PARALLEL clause.

ORA-14266: data type or length of an index subpartitioning column may not be changed

ORA-14266: data type or length of an index subpartitioning column may not be changed

Cause: User issued ALTER TABLE statement attempting to modify data type and or or length of a column used to subpartition some index defined on the table named in ALTER TABLE statement, which is illegal

Action: Avoid modifying data type and or or length of index subpartitioning column(s)

ORA-14265: data type or length of a table subpartitioning column may not be changed

ORA-14265: data type or length of a table subpartitioning column may not be changed

Cause: User issued ALTER TABLE statement attempting to modify data type and or or length of a column used to subpartition the table named in ALTER TABLE statement, which is illegal

Action: Avoid modifying data type and or or length of table subpartitioning column(s)

ORA-14264: table is not partitioned by Composite Range method

ORA-14264: table is not partitioned by Composite Range method

Cause: The table in the MODIFY DEFAULT ATTRIBUTES FOR PARTITION operation is partitioned by method other than Composite method

Action: Ensure that the table is partitioned by Composite method

ORA-14263: new subpartition name must differ from that of any other subpartition of the object

ORA-14263: new subpartition name must differ from that of any other subpartition of the object

Cause: User entered ALTER TABLE or INDEX RENAME SUBPARTITION specifying lamp;lt;lamp;nbsp;new-subpartition-namelamp;gt; which is identical to the name of some existing subpartition of the object

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

ORA-14262: new subpartition name must differ from the old subpartition name

ORA-14262: new subpartition name must differ from the old subpartition name

Cause: User entered ALTER TABLE or INDEX RENAME SUBPARTITION specifying lamp;lt;lamp;nbsp;new-subpartition-namelamp;gt; which is identical to the name of the subpartition being renamed

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

ORA-14261: partition bound may not be specified when adding this Hash partition

ORA-14261: partition bound may not be specified when adding this Hash partition

Cause: User specified VALUES LESS THAN clause when adding a partition (via ALTER TABLE ADD PARTITION) to a Hash partitioned table which is illegal

Action: Remove VALUES LESS THAN clause from the description of partition being added

ORA-14260: incorrect physical attribute specified for this partition

ORA-14260: incorrect physical attribute specified for this partition

Cause: User specified INITRANS, MAXTRANS, STORAGE, PCTFREE, PCTUSED, and or or (NO(LOGGING option to a Hash partition via ALTER TABLE ADD or MOVE PARTITION command which is illegal. Only TABLESPACE may be specified.

Action: Remove invalid option(s)

ORA-14259: table is not partitioned by Hash method

ORA-14259: table is not partitioned by Hash method

Cause: ALTER TABLE COALESCE PARTITION is only valid for table partitioned by Hash method

Action: Specify valid ALTER TABLE option for the table, or ensure that the table is partitioned by Hash method

ORA-14258: invalid partition description

ORA-14258: invalid partition description

Cause: User specified STORE-IN clause, SUBPARTITIONS clause, and or or lamp;lt;lamp;nbsp;subpartition-descriptionlamp;gt; clause in ALTER TABLE ADD PARTITION statement but the table in the maintenance operation is not a Composite Range or Hash partitioned table which is illegal

Action: Remove invalid clause(s), or ensure that the table is partitioned by Composite Range or Hash method

ORA-14257: cannot move partition other than a Range or Hash partition

ORA-14257: cannot move partition other than a Range or Hash partition

Cause: User attempt to move a partition that is not a Range or Hash partition which is illegal

Action: Specify MOVE PARTITION for a Range or Hash partition only

ORA-14256: invalid resulting partition description(s)

ORA-14256: invalid resulting partition description(s)

Cause: User specified STORE-IN clause, SUBPARTITIONS clause, and or or lamp;lt;lamp;nbsp;subpartition-descriptionlamp;gt; clause in partition description(s) in ALTER TABLE SPLIT PARTITION or ALTER TABLE MERGE PARTITIONS statement but the table in the maintenance operation is not a Composite Range partitioned table which is illegal

Action: Remove invalid clause(s), or ensure that the table is partitioned by Composite Range method

ORA-14255: table is not partitioned by Range, Composite Range or List method

ORA-14255: table is not partitioned by Range, Composite Range or List method

Cause: ALTER TABLE SPLIT or DROP PARTITION or ALTER TABLE MERGE PARTITIONS command is only valid for table partitioned by Range, List or Composite Range method

Action: Ensure that the table is partitioned by Range, List or Composite Range method

ORA-14254: cannot specify ALLOCATE STORAGE for a (Composite) Range or List partitioned table

ORA-14254: cannot specify ALLOCATE STORAGE for a (Composite) Range or List partitioned table

Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE statement issued against a Range or Composite Range partitioned table which is illegal.

Action: Remove the illegal option. If it is desired to add storage to individual partitions or subpartitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE MODIFY PARTITION or SUBPARTITION statement. If it is desired to add storage to all subpartitions of a Composite partition, ALLOCATE STORAGE clause may be specified with ALTER TABLE MODIFY PARTITION.

ORA-14253: table is not partitioned by Composite Range method

ORA-14253: table is not partitioned by Composite Range method

Cause: The table in a subpartition maintenance operation (ALTER TABLE EXCHANGE or MODIFY or MOVE or TRUNCATE SUBPARTITION, or ALTER TABLE MODIFY PARTITION ADD or COALESCE SUBPARTITION command must be partitioned by Composite Range method

Action: Ensure that the table is partitioned by Composite Range method

ORA-14252: invalid ALTER TABLE MODIFY PARTITION option for a Hash partition

ORA-14252: invalid ALTER TABLE MODIFY PARTITION option for a Hash partition

Cause: Only ALLOCATE EXTENT and DEALLOCATE UNUSED may be specified in ALTER TABLE MODIFY PARTITION for a Hash partition.

Action: Specify only legal options.

ORA-14251: Specified subpartition does not exist

ORA-14251: Specified subpartition does not exist

Cause: Subpartition not found for the object.

Action: Retry with correct subpartition name.

ORA-14196: Specified index cannot be used to enforce the constraint.

ORA-14196: Specified index cannot be used to enforce the constraint.

Cause: The index specified to enforce the constraint is unsuitable for the purpose.

Action: Specify a suitable index or allow one to be built automatically.

ORA-14195: ALLOCATE STORAGE may not be specified for RANGE or LIST partitioned object

ORA-14195: ALLOCATE STORAGE may not be specified for RANGE or LIST partitioned object

Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE or ALTER INDEX statement issued against a range-partitioned index which is illegal.

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

ORA-14194: only one subpartition may be rebuilt

ORA-14194: only one subpartition may be rebuilt

Cause: ALTER INDEX REBUILD SUBPARTITION contained descriptions of more than one subpartition to be rebuilt

Action: Ensure that the statement describes exactly one subpartition to be rebuilt and that it does not contain any commas

ORA-14193: invalid ALTER INDEX MODIFY SUBPARTITION option

ORA-14193: invalid ALTER INDEX MODIFY SUBPARTITION option

Cause: An option other than UNUSABLE, ALLOCATE EXTENT, DEALLOCATE UNUSED was specified in an ALTER INDEX MODIFY SUBPARTITION statement.

Action: Specify only legal options.

ORA-14192: cannot modify physical index attributes of a Hash index partition

ORA-14192: cannot modify physical index attributes of a Hash index partition

Cause: User attempted to modify one of INITRANS or MAXTRANS or LOGGING or STORAGE clause for an index partition of a Hash partitioned index

Action: Remove the physical attributes one is trying to modify

ORA-14191: ALLOCATE STORAGE may not be specified for Composite Range partitioned object

ORA-14191: ALLOCATE STORAGE may not be specified for Composite Range partitioned object

Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE or ALTER INDEX statement issued against a range-partitioned index which is illegal.

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

ORA-14190: only one ENABLE or DISABLE ROW MOVEMENT clause can be specified

ORA-14190: only one ENABLE or DISABLE ROW MOVEMENT clause can be specified

Cause: One of three possible actions caused the error: 1) ENABLE ROW MOVEMENT was specified more than once. 2) DISABLE ROW MOVEMENT was specified more than once. 3) Both ENABLE ROW MOVEMENT and DISABLE ROW MOVEMENT were specified.

Action: Remove all but one of the ENABLE ROW MOVEMENT or DISABLE ROW MOVEMENT clauses; then, reissue the command.

ORA-14189: this physical attribute may not be specified for an index subpartition

ORA-14189: this physical attribute may not be specified for an index subpartition

Cause: unexpected option was encountered while parsing physical attributes of an index subpartition; TABLESPACE is the only valid option

Action: remove invalid option(s)

ORA-14188: sub-partitioning columns must form a subset of key columns of a UNIQUE index

ORA-14188: sub-partitioning columns must form a subset of key columns of a UNIQUE index

Cause: User attempted to create a UNIQUE partitioned index whose sub-partitioning columns do not form a subset of its key columns which is illegal

Action: If the user, indeed, desired to create an index whose subpartitioning columns do not form a subset of its key columns, it must be created as non-UNIQUE; otherwise, correct the list of key and or or subpartitioning columns to ensure that the index subpartitioning columns form a subset of its key columns

ORA-14187: partitioning method for LOCAL index is inconsistent with that of the underlying table

ORA-14187: partitioning method for LOCAL index is inconsistent with that of the underlying table

Cause: User attempted to create a LOCAL partitioned index that is not equi-partitioned with the underlying table. The partitioning types are mismatched.

Action: Correct the CREATE INDEX statement to ensure that the index partitionining method is consistent with that of the base table

ORA-14186: number of sub-partitions of LOCAL index must equal that of the underlying table

ORA-14186: number of sub-partitions of LOCAL index must equal that of the underlying table

Cause: User attempted to create a LOCAL partitioned index with a number of sub-partitions which is different from that of the underlying table.

Action: Correct the CREATE INDEX statement to specify a correct number of sub-partitions

ORA-14185: incorrect physical attribute specified for this index partition

ORA-14185: incorrect physical attribute specified for this index partition

Cause: unexpected option was encountered while parsing physical attributes of a local index partition; valid options for Range or Composite Range partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE, PCTUSED, LOGGING and TABLESPACE; but only TABLESPACE may be specified for Hash partitions STORE IN () is also disallowed for all but Composite Range partitions

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

ORA-14183: TABLESPACE DEFAULT can be specified only for Composite LOCAL index

ORA-14183: TABLESPACE DEFAULT can be specified only for Composite LOCAL index

Cause: User attempted to specify TABLESPACE DEFAULT for a partition of a Range or System or Hash partitioned LOCAL index object, which is illegal.

Action: Replace TABLESPACE DEFAULT with TABLESPACE lamp;lt;lamp;nbsp;ts_namelamp;gt; or remove it.

ORA-14178: STORE IN (DEFAULT) clause is not supported for hash partitioned global indexes

ORA-14178: STORE IN (DEFAULT) clause is not supported for hash partitioned global indexes

Cause: STORE IN (DEFAULT) is valid only for local indexes.

Action: a) Specify a tablespace list in place of DEFAULT, or b) Remove STORE IN clause and specify tablespaces individually for each index partition.

ORA-14177: STORE-IN (Tablespace list) can only be specified for a LOCAL index on a Hash or Composite Range Hash table

ORA-14177: STORE-IN (Tablespace list) can only be specified for a LOCAL index on a Hash or Composite Range Hash table

Cause: STORE-IN (Tablespace list) clause was used while creating a local index on a range or list or composite range list partitioned table

Action: Do not use the STORE_IN (Tablespace list) clause while creating a local index on range or list or composite range list partitioned table

ORA-14176: this attribute may not be specified for a hash partition

ORA-14176: this attribute may not be specified for a hash partition

Cause: An invalid option was encountered while parsing physical attributes of a partition of an object partitioned using the HASH method. The TABLESPACE option is the only valid option for such partitions.

Action: Remove the invalid option(s).