Oracle 12c R2 Error Codes and Solution Suggestions from ORA-14500 to ORA-14600
- ORA-14500: LOCAL option not valid without partition name
Cause: Incorrect syntax specified
Action: Retry the command
Cause: Table or index is not partitioned. Invalid syntax.
Action: Retry the command with correct syntax.
Cause: More than one partition name has been specified for analyze
Action: Specify one partition name.
Cause: A partition/subpartition number or bind variable has been used
Action: Specify a valid partition/subpartition name.
Cause: Incorrect syntax specified
Action: Retry the command
Cause: Incorrect syntax specified
Action: Retry the command
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
Cause: The specified table either does not exist or user does not have the proper privleges.
Action: Specify the correct table to use.
Cause: The specified table does not have the proper field definitions.
Action: Specify the correct table to use. See utlvalid.sql for more information.
Cause: The VALIDATE INTO has been specified for a non partitioned table or cluster or index.
Action: Use syntax correctly
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.
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.
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.
Cause: Incorrect syntax specified
Action: Retry the command
Cause: More than one subpartition name has been specified for analyze
Action: Specify one subpartition name.
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
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
Cause: table partition contains rows for the values being dropped.
Action: DELETE all rows for the values being dropped and reissue statement
- ORA-14519: Conflicting tablespace blocksizes for string string: Tablespace string block size string [string] conflicts with previously specified/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.
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/subpartitions.
Action: Specify a tablespace of the same block size as the partitioned object.
- 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/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/subpartitions being created.
- 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-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/subpartition of a local index/LOB column to be co-located with the corresponding partition/subpartition of the base table. However, this is not possible because the block sizes of the table and the LOB column/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/LOB column and then retry the DDL command, OR (2) Ensure that tablespaces of the correct block size are specified for all new partitions/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.
Cause: rows in table and index inconsistent
Action: run complete analyze to determine corrupt rows
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.
Cause: DDL operations like creation tables, views etc. and transaction control statements such as commit/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/DML operation.
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.
Cause: Requested operation requires the Cost Based Optimizer(CBO) which is not available during database startup. Features like partitioning, IOTs, grouping sets, and flashback cursor require the CBO.
Action: Retry the query after the database is open.
Cause: Cannot specify these clauses while specifying a template
Action: Correct the subpartition template clause.