ORA-14639: SUBPARTITIONS clause can be specfied only for Hash, Composite Range Hash table or partition

ORA-14639: SUBPARTITIONS clause can be specfied only for Hash, Composite Range Hash table or partition

Cause: Attempted to specify SUBPARTITIONS clause on table that is not partitioned by the Composite Range-Hash method

Action: Reissue the command after ensuring that the SUBPARTITIONS clause is not specified, to specify a template for a Composite Range List object use the SUBPARTITION TEMPLATE clause

ORA-14638: cannot MERGE subpartitions in different Range Composite partitions

ORA-14638: cannot MERGE subpartitions in different Range Composite partitions

Cause: Attempted to MERGE subpartitions in different Range Composite partitions

Action: Reissue the command after ensuring that the 2 subpartitions being merged lie in the same composite partition

ORA-14637: cannot merge a subpartition with itself

ORA-14637: cannot merge a subpartition with itself

Cause: The same subpartition name was specified twice for the merge operation

Action: Re-submit operation with 2 distinct subpartition names within the same composite partition

ORA-14636: only 2 resulting subpartition can be specified for SPLIT SUBPARTITION

ORA-14636: only 2 resulting subpartition can be specified for SPLIT SUBPARTITION

Cause: ALTER TABLE SPLIT SUBPARTITION contained more than 2 resulting subpartition for the SPLIT

Action: Ensure that the statement describes exactly 2 subpartitions as the target of the SPLIT operation

ORA-14635: only one resulting subpartition can be specified for MERGE SUBPARTITIONS

ORA-14635: only one resulting subpartition can be specified for MERGE SUBPARTITIONS

Cause: ALTER TABLE MERGE SUBPARTITIONS contained more than one resulting subpartition for the MERGE

Action: Ensure that the statement describes exactly one subpartition as the target that need to be MERGEd

ORA-14634: Subpartition descriptions cannot be specified during the SPLIT or MERGE of a partition of a Range-List partitioned table

ORA-14634: Subpartition descriptions cannot be specified during the SPLIT or MERGE of a partition of a Range-List partitioned table

Cause: During a split or a merge of a partition of a range list partitioned table you cannot specify any subpartitioning information for the resulting partition (s)

Action: Remove all subpartitioning information from the DDL.

ORA-14633: Index maintainence clause not allowed for ADD list subpartition to a Composite partitioned table

ORA-14633: Index maintainence clause not allowed for ADD list subpartition to a Composite partitioned table

Cause: The clause INVALIDATE or UPDATE GLOBAL INDEXES is allowed only for ADD hash subpartition to a composite partitioned table.

Action: Remove clause and reissue operation

ORA-14632: cannot specify PARALLEL clause when adding a List subpartition

ORA-14632: cannot specify PARALLEL clause when adding a List subpartition

Cause: User issued ALTER TABLE ADD SUBPARTITION statement with PARALLEL clause for a List subpartition of a Range or List partitioned object which is illegal

Action: Remove the PARALLEL clause.

ORA-14631: the partition bounds do not match the subpartition bounds of the partition

ORA-14631: the partition bounds do not match the subpartition bounds of the partition

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

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

ORA-14630: subpartition resides in offlined tablespace

ORA-14630: subpartition 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-14629: cannot drop the only subpartition of a partition

ORA-14629: cannot drop the only subpartition of a partition

Cause: A drop subpartition command is being executed when there is only one subpartition in the partition

Action: none

ORA-14628: specification of bounds is inconsistent with LIST method

ORA-14628: specification of bounds is inconsistent with LIST method

Cause: An operation such as ALTER TABLE SPLIT|ADD SUBPARTITION specified bounds that were inconsistent with List subpartitioning method

Action: Specify VALUES or subpartition descriptions correctly for SPLIT or ADD of List subpartitions

ORA-14627: Invalid operation was specified on a GLOBAL partitioned index

ORA-14627: Invalid operation was specified on a GLOBAL partitioned index

Cause: An invalid operation such as ALTER INDEX DROP|SPLIT SUBPARTITION was specified on the global index

Action: Ensure that subpartition level operations are not specified on a GLOBAL index, since these are only RANGE partitioned

ORA-14626: values being added already exist in DEFAULT subpartition

ORA-14626: values being added already exist in DEFAULT subpartition

Cause: An ADD VALUE operation cannot be executed because the values being added exist in the DEFAULT subpartition

Action: Issue a SPLIT of the DEFAULT subpartition and then MERGE the split subpartition into the subpartition to which values need to be added

ORA-14625: subpartition contains rows corresponding to values being dropped

ORA-14625: subpartition contains rows corresponding to values being dropped

Cause: table subpartition contains rows for the values being dropped.

Action: DELETE all rows for the values being dropped and reissue statement

ORA-14624: DEFAULT subpartition must be last subpartition specified

ORA-14624: DEFAULT subpartition must be last subpartition specified

Cause: A subpartition description follows the one describing the default subpartition

Action: Ensure that the DEFAULT subpartition is the last subpartition description

ORA-14623: Value string does not exist in subpartition string

ORA-14623: Value string does not exist in subpartition string

Cause: One of the list values in the SPLIT PARTITION or DROP VALUES statement does not exist in the subpartition

Action: Remove the value from the statement and try again

ORA-14622: Value string already exists in subpartition string

ORA-14622: Value string already exists in subpartition string

Cause: One of the list values in the ADD SUBPARTITION or ADD VALUES statement already exists in another subpartition

Action: Remove the duplicate value from the statement and try again

ORA-14621: cannot add subpartition when DEFAULT subpartition exists

ORA-14621: cannot add subpartition when DEFAULT subpartition exists

Cause: An ADD SUBPARTITION operation cannot be executed when a subpartition with DEFAULT values exists

Action: Issue a SPLIT of the DEFAULT subpartition instead

ORA-14620: DEFAULT subpartition already exists

ORA-14620: DEFAULT subpartition already exists

Cause: A subpartition already exists with DEFAULT value

Action: Remove the DEFAULT value from the list specified

ORA-14619: resulting List subpartition(s) must contain at least 1 value

ORA-14619: resulting List subpartition(s) must contain at least 1 value

Cause: After a SPLIT or DROP VALUE of a list subpartition, each resulting subpartition(as applicable) must contain at least 1 value

Action: Ensure that each of the resulting subpartitions contains atleast 1 value

ORA-14618: cannot drop the last value of subpartition

ORA-14618: cannot drop the last value of subpartition

Cause: ALTER TABLE DROP VALUES tried to drop the last value of the subpartition

Action: Cannot execute the command, unless two or more values exist for subpartition

ORA-14617: cannot add or drop values to DEFAULT subpartition

ORA-14617: cannot add or drop values to DEFAULT subpartition

Cause: A ADD or DROP VALUES operation is being done on the default subpartition

Action: Ensure that ADD or DROP VALUES is not done on the DEFAULT subpartition

ORA-14616: table is not subpartitioned by List method

ORA-14616: table is not subpartitioned by List method

Cause: A subpartition maintenance operation such as ALTER TABLE MODIFY SUBPARTITION ADD|DROP VALUES or ALTER TABLE DROP|SPLIT|MERGE SUBPARTITION can only be performed on List subpartitioned objects

Action: Re-issue the command against a List subpartitoned object.

ORA-14615: List value string specified twice in subpartitions string , string

ORA-14615: List value string specified twice in subpartitions string , string

Cause: A list value cannot be specified more that once

Action: Remove one of the specifications of the value

ORA-14614: List value string specified twice in subpartition string

ORA-14614: List value string specified twice in subpartition string

Cause: A list value cannot be specified more that once

Action: Remove one of the specifications of the value

ORA-14613: Attempt to generate name from parent name string and template name string failed as the combine named would have been longer than allowed

ORA-14613: Attempt to generate name from parent name string and template name string failed as the combine named would have been longer than allowed

Cause: Any name generated from a partition name and template name must be less than the maximum permissible name for an identifier

Action: Shorten either partition or template name.

ORA-14612: Duplicate lob segment name string for lob column string in template

ORA-14612: Duplicate lob segment name string for lob column string in template

Cause: Two lob segments of the same column were given the same name in the template

Action: Rename one of the lob segments

ORA-14611: Duplicate subpartition name string in template

ORA-14611: Duplicate subpartition name string in template

Cause: A subpartition name cannot be duplicated within the template

Action: Rename one of the subpartitions.

ORA-14610: Lob attributes not specified for lob column string for subpartition string

ORA-14610: Lob attributes not specified for lob column string for subpartition string

Cause: Lob attributes of a column must be specified for all subpartitions or must not be specified at all

Action: Ensure lob attributes of a column are specified for all subpartitions or not specified at all

ORA-14609: Tablespace was not specified for the previous lob segments of column string in template but is specified for string

ORA-14609: Tablespace was not specified for the previous lob segments of column string in template but is specified for string

Cause: Tablespaces may either be specified for all lob segments of a column or must not be specified for any lob segments of this column

Action: Either specify tablespaces for all or for none of the lob segments

ORA-14608: Tablespace was specified for the previous lob segments of column string in template but is not specified for string

ORA-14608: Tablespace was specified for the previous lob segments of column string in template but is not specified for string

Cause: Tablespaces may either be specified for all lob segments of a column or must not be specified for any lob segments of this column

Action: Either specify tablespaces for all or for none of the lob segments

ORA-14607: Tablespace was not specified for previous subpartitions in template but is specified for string

ORA-14607: Tablespace was not specified for previous subpartitions in template but is specified for string

Cause: Tablespaces may either be specified for all subpartitions or must not be specified for any subpartitions

Action: Either specify tablespaces for all or for none of the subpartitions

ORA-14606: Tablespace was specified for previous subpartitions in template but is not specified for string

ORA-14606: Tablespace was specified for previous subpartitions in template but is not specified for string

Cause: Tablespaces may either be specified for all subpartitions or must not be specified for any subpartitions

Action: Either specify tablespaces for all or for none of the subpartitions

ORA-14605: Name missing for subpartition or lob segment in template

ORA-14605: Name missing for subpartition or lob segment in template

Cause: A subpartition or lob segment was not specified a name in the template descriptions

Action: All subpartitions or lob segments must have names specified in the template

ORA-14604: During CREATE TABLE time it is illegal to specify SUBPARTITIONS or STORE IN once a SUBPARTITION TEMPLATE has been specified

ORA-14604: During CREATE TABLE time it is illegal to specify SUBPARTITIONS or STORE IN once a SUBPARTITION TEMPLATE has been specified

Cause: Once a subpartition template has been specified during a CREATE TABLE it is illegal to specify SUBPARTITIONS or STORE IN anywhere else

Action: Remove either the SUBPARTITIONS | STORE IN or remove the SUBPARTITION TEMPLATE clause

ORA-14603: (SUBPARTITIONS | SUBPARTITION TEMPLATE( subpartition_count syntax is valid only for range-hash tables

ORA-14603: (SUBPARTITIONS | SUBPARTITION TEMPLATE( subpartition_count syntax is valid only for range-hash tables

Cause: This syntax is valid only if subpartitioning dimension is hash

Action: none

ORA-14602: SUBPARTITION TEMPLATE is legal only for a composite partitioned table

ORA-14602: SUBPARTITION TEMPLATE is legal only for a composite partitioned table

Cause: SUBPARTITION TEMPLATE can be specified only for composite partitioned tables

Action: Do not use SUBPARTITION TEMPLATE on non-partitioned or non-composite partitioned tables.

ORA-14601: Illegal to specify SUBPARTITIONS or STORE-IN while specifying a subpartition template

ORA-14601: Illegal to specify SUBPARTITIONS or STORE-IN while specifying a subpartition template

Cause: Cannot specify these clauses while specifying a template

Action: Correct the subpartition template clause.

ORA-14553: cannot perform a lob write operation inside a query

ORA-14553: cannot perform a lob write operation inside a query

Cause: A lob write operation cannot be performed inside a query or a PDML slave.

Action: Ensure that the offending lob write operation is not performed or use an autonomous transaction to perform the operation within the query or PDML slave.

ORA-14552: cannot perform a DDL, commit or rollback inside a query or DML

ORA-14552: cannot perform a DDL, commit or rollback inside a query or DML

Cause: DDL operations like creation tables, views etc. and transaction control statements such as commit or rollback cannot be performed inside a query or a DML statement.

Action: Ensure that the offending operation is not performed or use autonomous transactions to perform the operation within the query or DML operation.

ORA-14551: cannot perform a DML operation inside a query

ORA-14551: cannot perform a DML operation inside a query

Cause: DML operation like insert, update, delete or select-for-update cannot be performed inside a query or under a PDML slave.

Action: Ensure that the offending DML operation is not performed or use an autonomous transaction to perform the DML operation within the query or PDML slave.

ORA-14523: Cannot co-locate (sub(partition of string string with table (sub(partition because string block size (string( does not match table block size (string(

ORA-14523: Cannot co-locate (sub(partition of string string with table (sub(partition because string block size (string( does not match table block size (string(

Cause: A DDL statement was issued that would require a partition or subpartition of a local index or LOB column to be co-located with the corresponding partition or subpartition of the base table. However, this is not possible because the block sizes of the table and the LOB column or local index are different.

Action: Either (1) Specify an object-level default tablespace (or partition-level default tablespace for the appropriate partition, if composite partitioning is used) for the partitioned local index or LOB column and then retry the DDL command, OR (2) Ensure that tablespaces of the correct block size are specified for all new partitions or subpartitions being created. Also ensure that neither of TABLESPACE DEFAULT and STORE IN (DEFAULT) is specified for a local index whose block size does not match that of the base table.

ORA-14522: Partition-level default tablespace string block size (string( for string string does not match existing string block size (string(

ORA-14522: Partition-level default tablespace string block size (string( for string string does not match existing string block size (string(

Cause: A DDL statement was issued that would require creation of a new subpartition in one of the partition-level default tablespaces of an existing composite partitioned object. However, the partition-level default tablespace block size does not match the block size of the partitioned object.

Action: Either (1) Modify the partition-level default tablespace of the appropriate partition of the partitioned object to a tablespace of the same block size as the object and then retry the DDL command, OR (2) Ensure that tablespaces of the correct block size are specified for all new subpartitions being created.

ORA-14521: Default tablespace string block size (string( for string string does not match existing string block size (string(

ORA-14521: Default tablespace string block size (string( for string string does not match existing string block size (string(

Cause: A DDL statement was issued that would require creation of a new partition or subpartition in the object-level default tablespace of an existing partitioned object. However, the object-level default tablespace block size does not match the block size of the partitioned object.

Action: Either (1) Modify the default tablespace of the partitioned object to a tablespace of the same block size as the object and then retry the DDL command, OR (2) Ensure that tablespaces of the correct block size are specified for all new partitions or subpartitions being created.

ORA-14520: Tablespace string block size (string( does not match existing object block size (string(

ORA-14520: Tablespace string block size (string( does not match existing object block size (string(

Cause: A DDL statement was issued that would require a tablespace of a block size different from the block size of the specified partitioned object to be assigned either: (1) As the object s default tablespace (or one of the object s partition-level default tablespaces, if composite partitioning is being used) OR (2) To one of the object s partitions or subpartitions.

Action: Specify a tablespace of the same block size as the partitioned object.

ORA-14519: Conflicting tablespace blocksizes for string string: Tablespace string block size string (string( conflicts with previously specified or implied tablespace string block size string (string(

ORA-14519: Conflicting tablespace blocksizes for string string: Tablespace string block size string (string( conflicts with previously specified or implied tablespace string block size string (string(

Cause: An attempt has been made to create a partitioned object in a manner that would require the partitioned object to span tablespaces of more than one block size.

Action: Ensure that all tablespaces specified in the DDL command for the given object as well as any tablespaces implicitly assigned to partitions or subpartitions of the object being created are all of the same block size.

ORA-14518: partition contains rows corresponding to values being dropped

ORA-14518: partition contains rows corresponding to values being dropped

Cause: table partition contains rows for the values being dropped.

Action: DELETE all rows for the values being dropped and reissue statement

ORA-14517: subpartition of index string.string is in unusable state

ORA-14517: subpartition of index string.string is in unusable state

Cause: An attempt has been made to access an index subpartition that has been marked unusable by a direct load or by a DDL operation

Action: REBUILD the unusable index subpartition

ORA-14516: subpartition corrupt. all rows do not fall within subpartition bounds

ORA-14516: subpartition corrupt. all rows do not fall within subpartition bounds

Cause: The subpartition contains rows which should really be in some other subpartition. Possibly due to an exchange subpartition without validation

Action: Delete rows in subpartition which do not qualify

ORA-14515: only one aubpartition name can be specified

ORA-14515: only one aubpartition name can be specified

Cause: More than one subpartition name has been specified for analyze

Action: Specify one subpartition name.

ORA-14514: LOCAL option not valid without subpartition name

ORA-14514: LOCAL option not valid without subpartition name

Cause: Incorrect syntax specified

Action: Retry the command

ORA-14513: partitioning column may not be of object datatype

ORA-14513: partitioning column may not be of object datatype

Cause: Partitioning column specified by the user was an object datatype (object, REF, nested table, array) which is illegal.

Action: Ensure that no partitioning column is an object datatype.

ORA-14512: cannot perform operation on a clustered object

ORA-14512: cannot perform operation on a clustered object

Cause: An attempt was made to perform an operation that is not allowed on clustered tables or indexes.

Action: Retry the command with correct syntax.

ORA-14511: cannot perform operation on a partitioned object

ORA-14511: cannot perform operation on a partitioned object

Cause: An attempt was made to perform an operation that is not allowed on partitioned tables or indexes.

Action: Retry the command with correct syntax.

ORA-14510: can specify VALIDATE INTO clause only for partitioned tables

ORA-14510: can specify VALIDATE INTO clause only for partitioned tables

Cause: The VALIDATE INTO has been specified for a non partitioned table or cluster or index.

Action: Use syntax correctly

ORA-14509: specified VALIDATE INTO table form incorrect

ORA-14509: specified VALIDATE INTO table form incorrect

Cause: The specified table does not have the proper field definitions.

Action: Specify the correct table to use. See utlvalid.sql for more information.

ORA-14508: specified VALIDATE INTO table not found

ORA-14508: specified VALIDATE INTO table not found

Cause: The specified table either does not exist or user does not have the proper privleges.

Action: Specify the correct table to use.

ORA-14507: partition corrupt. all rows do not fall within partition bounds

ORA-14507: partition corrupt. all rows do not fall within partition bounds

Cause: The partition contains rows which should really be in some other partition. Possibly due to an exchange partition without validation

Action: Delete rows in partition which do not qualify

ORA-14506: LOCAL option required for partitioned indexes

ORA-14506: LOCAL option required for partitioned indexes

Cause: Incorrect syntax specified

Action: Retry the command