ORA-14153: only one of STORE IN or
<partition-description> clause may be specified
Cause:
both STORE IN and <partition-description> clauses were specified in a
CREATE TABLE|INDEX command
Action:
Remove one of offending clauses
ORA-14154: only one of STORE IN or
<subpartition-description> clause may be specified
Cause:
both STORE IN and <subpartition-description> clauses were specified in a
CREATE TABLE|INDEX, or ALTER TABLE ADD|SPLIT PARTITION or ALTER TABLE MERGE
PARTITIONS command for a Composite Range partitioned object
Action:
Remove one of offending clauses
ORA-14155: missing PARTITION or SUBPARTITION
keyword
Cause:
expect either PARTITION or SUBPARTITION keyword but none was supplied
Action:
supply missing keyword
ORA-14156: invalid number of subpartitions
specified in [SUBPARTITIONS | SUBPARTITION TEMPLATE] clause
Cause:
number-of-subpartitions clause contained in CREATE TABLE or CREATE INDEX
statement specified a number of subpartitions outside of legal range
(1-1048575)
Action:
Specify a number between 1 and 1024K-1 in the number-of-subpartitions clause
ORA-14157: invalid subpartition name
Cause:
a subpartition name of the form <identifier> is expected but not present.
Action:
enter an appropriate subpartition name.
ORA-14158: too many subpartition descriptions
Cause:
CREATE TABLE or CREATE INDEX contained too many subpartition descriptions;
maximum number of subpartitions is 1048575.
Action:
Reduce number of subpartitions to not exceed 1024K-1.
ORA-14159: duplicate subpartition name
Cause:
Name of a subpartition of a table or index being created is not unique
Action:
rename subpartition(s) to ensure that their names are unique among
subpartitions of the table or index being created
ORA-14160: this physical attribute may not be
specified for a table subpartition
Cause:
unexpected option was encountered while parsing physical attributes of a table
subpartition; TABLESPACE is the only valid option
Action:
remove invalid option(s)
ORA-14161: subpartition number string: sum
of PCTUSED and PCTFREE may not exceed 100
Cause:
the sum of PCTUSED and PCTFREE for a subpartition whose number (subpartitions
are numbered starting with 1) is displayed in this message exceeds 100. Note
that if PCTUSED and/or PCTFREE values for this subpartition were not specified
explicitly, default values at partition-level would be used. If, in turn,
default PCTUSED and/or PCTFREE values at partition-level were not specified,
default values for the partitioned table or index would be used. If those
values were also not specified explicitly, system defaults would be used.
Action:
ensure that a sum of PCTUSED and PCTFREE for the subpartition does not exceed
100
ORA-14162: subpartition "string":
sum of PCTUSED and PCTFREE may not exceed 100
Cause:
the sum of PCTUSED and PCTFREE for a subpartition whose name (explicitly
specified by the user) is displayed in this message exceeds 100. Note that if
PCTUSED and/or PCTFREE values for this subpartition were not specified
explicitly, default values at partition-level would be used. If, in turn,
default PCTUSED and/or PCTFREE values at partition-level were not specified,
default values for the partitioned table or index would be used. If those
values were also not specified explicitly, system defaults would be used.
Action:
ensure that a sum of PCTUSED and PCTFREE for the subpartition does not exceed
100
ORA-14163: subpartition number string:
INITRANS value must be less than MAXTRANS value
Cause:
Value of INITRANS was found to be greater than that of MAXTRANS for a
subpartition whose number (subpartitions are numbered starting with 1) is
displayed in this message. Note that if INITRANS and/or MAXTRANS values for
this subpartition were not specified explicitly, default values at
partition-level would be used. If, in turn, default INITRANS and/or MAXTRANS
values at partition-level were not specified, default values for the
partitioned table or index would be used. If those values were also not
specified explicitly, system defaults would be used.
Action:
ensure that value of INITRANS (whether specified explicitly or derived from the
default value at partition-level, table-level or index-level) is no greater
than that of MAXTRANS
ORA-14164: subpartition "string":
INITRANS value must be less than MAXTRANS value
Cause:
Value of INITRANS was found to be greater than that of MAXTRANS for a
subpartition whose name (explicitly specified by the user) is displayed in this
message. Note that if INITRANS and/or MAXTRANS values for this subpartition
were not specified explicitly, default values at partition-level would be used.
If, in turn, default INITRANS and/or MAXTRANS values at partition-level were
not specified, default values for the partitioned table or index would be used.
If those values were also not specified explicitly, system defaults would be
used.
Action:
ensure that value of INITRANS (whether specified explicitly or derived from the
default value at partition-level, table-level or index-level) is no greater
than that of MAXTRANS
ORA-14165: MODIFY DEFAULT ATTRIBUTES FOR PARTITION
may not be combined with other operations
Cause:
ALTER TABLE or ALTER INDEX statement attempted to combine MODIFY DEFAULT
ATTRIBUTES OF PARTITION with some other operation (e.g. 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 at will
ORA-14166: missing INTO keyword
Cause:
keyword INTO missing
Action:
supply missing keyword
ORA-14167: only one subpartition may be moved
Cause:
ALTER TABLE MOVE SUBPARTITION contained descriptions of more than one
subpartition to be moved
Action:
Ensure that the statement describes exactly one subpartition to be moved and
that it does not contain any commas
ORA-14168: only one subpartition may be modified
Cause:
ALTER TABLE|INDEX MODIFY SUBPARTITION contained descriptions of more than one
subpartition to be modified
Action:
Ensure that the statement describes exactly one subpartition to be modified and
that it does not contain any commas
ORA-14169: invalid ALTER TABLE MODIFY SUBPARTITION
option
Cause:
An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, was
specified in an ALTER TABLE MODIFY SUBPARTITION statement.
Action:
Specify only legal options.
ORA-14170: cannot specify
<partition-description> clause in CREATE TABLE|INDEX
Cause:
User requested to generate default partition description(s) (possibly via
PARTITIONS <number-of-partitions>) while at the same time specified
<partition-description> clause which is illegal
Action:
Remove one of offending clauses.
ORA-14171: cannot specify
<subpartition-description> clause in CREATE|ALTER TABLE
Cause:
User requested to generate default subpartition description(s) (possibly via
SUBPARTITIONS) while at the same time specified
<subpartition-description> clause which is illegal
Action:
Remove one of offending clauses.
ORA-14172: invalid ALTER TABLE EXCHANGE
SUBPARTITION option
Cause:
Name of the table to be EXCHANGED has to be followed by [{INCLUDING|EXCLUDING}
INDEX][{WITH|WITHOUT} VALIDATION]
Action:
Ensure that no options besides INCLDING INDEX or EXCLUDING INDEX are specified
with ALTER TABLE EXCHANGE SUBPARTITION
ORA-14173: illegal subpartition-extended table name
syntax
Cause:
Subpartition to be accessed may only be specified using its name. User
attempted to use a subpartition number or a bind variable.
Action:
Modify statement to refer to a subpartition using its name
ORA-14174: only a <parallel clause> may
follow COALESCE PARTITION|SUBPARTITION
Cause:
ALTER TABLE COALESCE PARTITION|SUBPARTITION may be followed by an optional
<parallel clause>. No partition/subpartition attributes may be specified
Action:
Ensure that no partition/subpartition attribute was specified.
ORA-14175: a subpartition maintenance operation may
not be combined with other operations
Cause:
ALTER TABLE or ALTER INDEX statement attempted to combine a subpartition
maintenance operation (e.g. MOVE SUBPARTITION) with some other operation (e.g.
MODIFY PARTITION ADD SUBPARTITION or PCTFREE) which is illegal
Action:
Ensure that a subpartition maintenance operation is the sole operation
specified in ALTER TABLE or ALTER INDEX statement; operations other than those
dealing with subpartitions, default attributes of partitioned tables/indices or
specifying that a table be renamed (ALTER TABLE RENAME) may be combined at will
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).
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/list/composite range list partitioned table
Action:
Do not use the STORE_IN (Tablespace list) clause while creating a local index
on range/list/composite range list partitioned table
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-14183: TABLESPACE DEFAULT can be specified only
for Composite LOCAL index
Cause:
User attempted to specify TABLESPACE DEFAULT for a partition of a
Range/System/Hash partitioned LOCAL index object, which is illegal.
Action:
Replace TABLESPACE DEFAULT with TABLESPACE <ts_name> or remove it.
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-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-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-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 subpartitioning columns to ensure
that the index' subpartitioning columns form a subset of its key columns
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-14190: only one ENABLE/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-14191: ALLOCATE STORAGE may not be specified
for Composite Range partitioned object
Cause:
User specified ALLOCATE STORAGE clause in ALTER TABLE/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/INDEX
MODIFY PARTITION statement.
ORA-14192: cannot modify physical index attributes
of a Hash index partition
Cause:
User attempted to modify one of INITRANS/MAXTRANS/LOGGING/STORAGE clause for an
index partition of a Hash partitioned index
Action:
Remove the physical attributes one is trying to modify
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-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-14195: ALLOCATE STORAGE may not be specified
for RANGE or LIST partitioned object
Cause:
User specified ALLOCATE STORAGE clause in ALTER TABLE/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/INDEX
MODIFY PARTITION statement.
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-14201: specified subpartition bound is too long
Cause:
Length of a linear key representation of a high bound of a table subpartition
being added or along which an existing table or index subpartition is being
split exceeded the legal limit (4K).
Action:
Change the representation of a subpartition high bound to bring its length
within legal limit.
ORA-14202: subpartition bound of subpartition
"string" is too high
Cause:
High bound of the specified subpartition displayed in this message did not
collate lower than that of the subsequent subpartition.
Action:
Ensure that high bound of every subpartition (except for the last one) collates
lower than that of a subsequent subpartition.
ORA-14203: subpartition bound of subpartition
"string" is too long
Cause:
Length of linear key representation of a high bound of the specified
subpartition displayed in this message exceeded the legal limit (4K).
Action:
Change the representation of a subpartition high bound to bring its length
within legal limit.
ORA-14204: subpartition bound of subpartition
number string is too high
Cause:
High bound of the specified subpartition displayed in this message did not
collate lower than that of the subsequent subpartition.
Action:
Ensure that high bound of every subpartition (except for the last one) collates
lower than that of a subsequent subpartition.
ORA-14205: subpartition bound of subpartition
number string is too long
Cause:
Length of linear key representation of a high bound of the specified
subpartition displayed in this message exceeded the legal limit (4K).
Action:
Change the representation of a subpartition high bound to bring its length
within legal limit.
ORA-14206: table is not subpartitioned by List or
Range methods
Cause:
A subpartition maintenance operation such as ALTER TABLE DROP|SPLIT|MERGE
SUBPARTITION can only be performed on List or Range subpartitioned objects
Action:
Issue the command only against a List or Range subpartitioned object.
ORA-14207: maximum number of subpartitioning
columns is 16
Cause:
number of columns in a subpartitioning column list exceeded the legal limit of
16
Action:
modify subpartitioning column list so that it consists of at most 16 columns
ORA-14208: lower-bound subpartition must be
specified first
Cause:
A higher-bound subpartition was specified before the lower-bound subpartition
in ALTER TABLE MERGE SUBPARTITIONS statement.
Action:
Specify lower-bound subpartition first and then higher-bound subpartition
ORA-14209: subpartitions being merged are not
adjacent
Cause:
Attempted to merge two subpartitions that are not adjacent to each other.
Action:
Specify two subpartitions that are adjacent
ORA-14210: cannot reuse lower-bound subpartition as
resulting subpartition
Cause:
Attempted to reuse the lower-bound subpartition of the subpartitions being
merged.
Action:
Specify new resulting subpartition name or reuse the higher-bound subpartition
only
ORA-14211: subpartition bound must collate higher
than that of the last subpartition
Cause:
Subpartition bound specified in ALTER TABLE MODIFY PARTITION ADD SUBPARTITION
statement did not collate higher than that of the partition's last
subpartition.
Action:
Ensure that the subpartition bound of the subpartition to be added collates
higher than that of the table partition's last subpartition.
ORA-14212: subpartition cannot be split along the
specified high bound
Cause:
Attempted to split a subpartition along a bound which either collates higher
than that of the subpartition to be split or lower than that of a subpartition
immediately preceding the one to be split
Action:
Ensure that the bound along which a subpartition is to be split collates lower
than that of the subpartition to be split and higher than that of a subpartition
immediately preceding the one to be split
ORA-14213: VALUES LESS THAN or AT clause cannot be
used for List subpartitioned tables
Cause:
VALUES LESS THAN or AT clause was used for List subpartitioned tables
Action:
Use VALUES (<value list>) clause for List subpartitioned tables
ORA-14214: VALUES (<value list>) cannot be
used for Range subpartitioned tables
Cause:
VALUES (<value list>) clause was used for Range subpartitioned tables
Action:
Use VALUES LESS THAN or AT clause with Range subpartitioned tables
ORA-14215: subpartition bound list contains too
many elements
Cause:
Subpartition bound list contained more elements than there are subpartitioning
columns
Action:
Ensure that the number of elements in subpartition bound list is equal to the
number of subpartitioning columns of the table or index
ORA-14216: subpartition bound list contains too few
elements
Cause:
Subpartition bound list contained fewer elements than there are subpartitioning
columns
Action:
Ensure that the number of elements in partition bound list is equal to the
number of partitioning columns of the table or index
ORA-14217: VALUES (<value list>) clause
expected
Cause:
VALUES (<value list>) clause was not specified for the list subpartition
being added
Action:
Specify a VALUES (<value list>) clause
ORA-14251: Specified subpartition does not exist
Cause:
Subpartition not found for the object.
Action:
Retry with correct subpartition name.
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-14253: table is not partitioned by Composite
Range method
Cause:
The table in a subpartition maintenance operation (ALTER TABLE
EXCHANGE/MODIFY/MOVE/TRUNCATE SUBPARTITION, or ALTER TABLE MODIFY PARTITION
ADD/COALESCE SUBPARTITION command must be partitioned by Composite Range method
Action:
Ensure that the table is partitioned by Composite Range method
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/subpartitions, ALLOCATE STORAGE clause may be specified with ALTER
TABLE MODIFY PARTITION/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-14255: table is not partitioned by Range, List,
Composite Range or Composite List method
Cause:
The table was not partitioned by Range, List, Composite Range or Composite List
method.
Action:
ALTER TABLE SPLIT/DROP PARTITION or ALTER TABLE MERGE PARTITIONS command is
only valid for table partitioned by Range, List, Composite Range or Composite
List methods. Ensure that the table is partitioned appropriately.
ORA-14256: invalid resulting partition
description(s)
Cause:
User specified STORE-IN clause, SUBPARTITIONS clause, and/or
<subpartition-description> 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-14257: cannot move partition other than a Range,
List, System, or Hash partition
Cause:
User attempt to move a partition that is not a Range,List,System, or Hash
partition which is illegal
Action:
Specify MOVE PARTITION for a Range,List,System, or Hash partition only
ORA-14258: invalid partition description
Cause:
User specified STORE-IN clause, SUBPARTITIONS clause, and/or
<subpartition-description> clause in ALTER TABLE ADD PARTITION statement
but the table in the maintenance operation is not a Composite Range/Hash
partitioned table which is illegal
Action:
Remove invalid clause(s), or ensure that the table is partitioned by Composite
Range/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-14260: incorrect physical attribute specified
for this partition
Cause:
User specified INITRANS, MAXTRANS, STORAGE, PCTFREE, PCTUSED, and/or [NO]LOGGING
option to a Hash partition via ALTER TABLE ADD/MOVE PARTITION command which is
illegal. Only TABLESPACE may be specified.
Action:
Remove invalid option(s)
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-14262: new subpartition name must differ from
the old subpartition name
Cause:
User entered ALTER TABLE/INDEX RENAME SUBPARTITION specifying
<new-subpartition-name> 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-14263: new subpartition name must differ from
that of any other subpartition of the object
Cause:
User entered ALTER TABLE/INDEX RENAME SUBPARTITION specifying
<new-subpartition-name> 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-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-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 length
of a column used to subpartition the table named in ALTER TABLE statement,
which is illegal
Action:
Avoid modifying data type and/or length of table subpartitioning column(s)
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 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 length of index subpartitioning column(s)
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-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-14269: cannot exchange partition other than a
Range,List,System, or Hash partition
Cause:
User attempt to exchange a partition with a non-partitioned table but the
specified partition is not a Range,List,System, or Hash partition which is
illegal
Action:
Specify EXCHANGE PARTITION for a Range,List,System, or Hash partition only
ORA-14270: table is not partitioned by Range,
System, 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,List,System, or
Hash method which is illegal.
Action:
Ensure that the table is partitioned by Range,List,System, or Hash 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-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-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-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-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-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-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-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-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-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-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-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-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 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 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.
No hay comentarios:
Publicar un comentario