Skip to content

Fatih Acar's blog

About of Database Systems and Information Technologies

Menu
  • Home
  • About Me
  • Contact Me
Menu

Oracle 11g Error Codes and Solution Suggestions from ORA-14200 to ORA-14300

Posted on 21/04/201626/10/2016 by Fatih Acar

Oracle 11g Error Codes and Solution Suggestions from ORA-14200 to ORA-14300

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-14218: Invalid operation for object without a segment
Cause: The object (table or index or lob) did not have a segment.
Action: Create segments for the object with the ALTER TABLE ALLOCATE EXTENT command.
ORA-14220: Invalid operation for object without a segment
Cause: Attempted to modify storage or allocate an extent for an object (table or LOB or index) without a segment.
Action: Create segments for the object with the ALTER TABLE ALLOCATE EXTENT command.
ORA-14221: Dictionary managed tablespace cannot be used for this operation
Cause: Attempted to create an index or add a LOB column in a dictionary managed tablespace to a table without a segment.
Action: Specify a locally managed tablespace OR create segments for the table with the ALTER TABLE ALLOCATE EXTENT command.
ORA-14223: Deferred segment creation is not supported for this table
Cause: The SEGMENT CREATION DEFERRED clause was specified in the CREATE TABLE statement.
Action: Remove the SEGMENT CREATION DEFERRED 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.
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-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-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-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-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-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-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-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-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-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-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-14295: column type or size mismatch between partitioning columns and subpartitioning columns
Cause: When exchanging a partitioned table with a composite partition the type and size of the partitioning columns of the table must match the type and size of the subpartitioning columns of the composite partition.
Action: Ensure that the type and size of the partitioning columns of the partitioned is the same as the type and size of the subpartitioning columns of the composite partition.
ORA-14296: Table block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
Cause: The block sizes of the two tables specified in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are different. For index organized tables, either the block sizes of the index or the overflow (or both) do not match.
Action: Ensure that the block sizes of the tables involved in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are the same. For index organized tables, ensure that the block sizes of both the index and the overflow of the two tables match.
ORA-14297: Index block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
Cause: The block sizes of a pair of indexes being exchanged in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are different.
Action: Ensure that the block sizes of the corresponding pairs of indexes that need to be exchanged in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are the same.
ORA-14298: LOB column block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
Cause: The block sizes of a pair of corresponding LOB columns of the two tables specified in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are different.
Action: Ensure that the block sizes of corresponding pairs of LOB columns of the tables involved in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are the same.
ORA-14299: total number of partitions/subpartitions exceeds the maximum limit
Cause: The total number of combined fragments specified in partitions /subpartitions exceeds 1048575.
Action: Reissue the statement with fewer number of fragments
ORA-14300: partitioning key maps to a partition outside maximum permitted number of partitions
Cause: The row inserted had a partitioning key that maps to a partition number greater than 1048575
Action: Ensure that the partitioning key falls within 1048575 partitions or subpartitions.

Share this:

  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to share on X (Opens in new window) X
  • Click to share on Facebook (Opens in new window) Facebook

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload CAPTCHA.



View Fatih ACAR's profile on LinkedIn

Categories

  • Databases (329)
    • MsSQL Server (18)
      • Administration (16)
      • Errors and Solutions (4)
      • SQL (2)
    • MySQL (5)
      • Administration (4)
      • Backup And Recovery (1)
      • Errors and Solutions (1)
    • Oracle (290)
      • Administration (79)
      • Backup And Recovery (29)
      • Errors and Solutions (195)
      • Procedure (10)
      • SQL (32)
    • PostgreSQL (16)
      • Administration (15)
      • Errors and Solutions (3)
      • SQL (2)
    • Redis (1)
  • Microsotf Dynamics CRM (1)
  • Operating Systems (47)
    • Linux & Unix (34)
    • Windows (13)
  • Programing (5)
    • Python (5)
  • SAP (15)
    • Errors and Solutions (4)
    • SAP Basis (12)
  • Security (8)
    • Database Security (6)
    • Information Security (1)
    • System Security (4)
  • VMware (4)

Recent Posts

  • Redis 7 Sentinel Infrastructure Installation
  • Oracle Database 19c Multi Data Guard and DML Redirect, Switchover-Failover Operations on Oracle Linux 8
  • Oracle Database 23ai Free Installation Steps on Oracle Linux 9
  • Oracle Database 19c Active Data Guard Installation and DML Redirect, Switchover-Failover Operations on Oracle Linux 8
  • Oracle Database 19c Installation and 19.22 RU Patch Apply on Oracle Linux 8

Resources

  • Oracle
  • PostgreSQL

Blogroll

  • Gökhan Atıl
  • H. Koray Gündüz
  • Hakan Talip Öztürk
  • Zekeriya Beşiroğlu

Web Pages

  • BT Çözümleri

Tag Cloud

Administration Backup and Recovery Cluster Systems Database Administration Database Security Linux Linux Administration MsSQL Server MsSQL Server Error and Solutions MySQL MySQL Administration ORA-00018 ORA-00020 Oracle Oracle 12c Oracle 19c Oracle Administration Oracle Backup and Restore Oracle Data Guard Oracle Data Guard Failover Oracle Data Guard Switchover Oracle Error Solutions Oracle Linux Oracle Rman Backup Oracle Security Oracle SQL Query PostgreSQL PostgreSQL Administration PostgreSQL High Availability PostgreSQL Hot Standby Python SAP Basis Sap Errors and Solutions Sap System Administration SQL SQL Server Administration SQL Server Availability Group Stored Procedure System Administration System Security VMware VMware Administration Windows Windows Batch Script Windows Server

Social

  • View facar1987’s profile on Twitter
  • View facar’s profile on LinkedIn

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 17 other subscribers
©2026 Fatih Acar's blog | Built using WordPress and Responsive Blogily theme by Superb