Oracle 11g Error Codes and Solution Suggestions from ORA-14700 to ORA-15000
- ORA-14700: Object(s) owned by SYS cannot be locked by non-SYS user
- Cause: Attempt to issue a LOCK TABLE statement on SYS owned object(s) by a non-SYS user, user should minimally have DML privileges
- Action: Re-issue LOCK TABLE statement for non-SYS user after granting DML privileges on object, or non-SYS user should connect as SYS
- ORA-14701: partition-extended name or bind variable must be used for DMLs on tables partitioned by the System method
- Cause: User attempted not to use partition-extended syntax for a table partitioned by the System method
- Action: Must use of partition-extended syntax in contexts mentioned above.
- ORA-14702: The partition number is invalid or out-of-range
- Cause: Attempted to use nonnumerical value or the number was out of range of the partitions.
- Action: Use a valid partition number.
- ORA-14703: The AFTER clause can be used to ADD PARTITION only to a System Partitioned table.
- Cause: The table is not partitioned by the System method
- Action: Skip the AFTER clause.
- ORA-14704: Create table as select disallowed for SYSTEM patitioned tables
- Cause: User attempted to create a SYSTEM partitioned table by doing a create table as select.
- Action: Do a create table followed by an insert as select into each partition.
- ORA-14750: Range partitioned table with INTERVAL clause has more than one column
- Cause: You attempted to create an interval partitioned table with more than one partitioning column.
- Action: Use a single partitioning column.
- ORA-14751: Invalid data type for partitioning column of an interval partitioned table
- Cause: You attempted to use interval partitioning on a table partitioned on a column of data type other than number or date/time.
- Action: Use only number or date/time columns as partitioning columns for interval partitioned tables.
- ORA-14752: Interval expression is not a constant of the correct type
- Cause: You attempted to use either a nonconstant interval or an interval whose data type does not correspond to the partitioning column
- Action: Use only constant expressions for the interval. If the data type of partitioning column is numeric, the interval must be a numeric constant. If the data type is of type date/time, the interval must be a constant of interval type
- ORA-14753: Interval cannot be zero
- Cause: The interval mapped to zero.
- Action: You must use a nonzero interval.
- ORA-14754: Interval string is too long
- Cause: The interval string was too long
- Action: Specify interval using a shorter string
- ORA-14755: Invalid partition specification for FOR VALUES clause.
- Cause: The [SUB]PARTITION FOR VALUES (…) clause can only take constants. In addition it takes as many arguments as there are partitioning columns and the values must be coercible to the partitioning columns.
- Action: Specify a valid FOR VALUES clause.
- ORA-14756: Table is not partitioned by Interval method.
- Cause: The table was not partitioned by Interval method.
- Action: ALTER TABLE SET STORE IN is only valid for Interval partitioned tables. Ensure that the table by Interval.
- ORA-14757: Table is already a range partitioned table
- Cause: SET INTERVAL () is used to convert an interval partitioned table to a range partitioned table. It is not legal on a range partitioned table
- Action: Use SET INTERVAL () only on an interval partitioned table.
- ORA-14758: Last partition in the range section cannot be dropped
- Cause: An attempt was made to drop the last range partition of an interval partitioned table.
- Action: Do not attempt to drop this partition.
- ORA-14759: SET INTERVAL is not legal on this table.
- Cause: SET INTERVAL clause was specified. ALTER TABLE SET INTERVAL is only legal on a range partitioned table with a single partitioning column. Additionally, this table cannot have a maxvalue partition and cannot be the parent table for any reference partitioned tables.
- Action: Use SET INTERVAL only on a valid table.
- ORA-14760: ADD PARTITION is not permitted on Interval partitioned objects
- Cause: ALTER TABLE ADD PARTITION was attempted on an Interval partitioned object.
- Action: Do not perform the operation on an Interval partitioned object. Insert a row to create the new partition.
- ORA-14761: MAXVALUE partition cannot be specified for Interval partitioned objects
- Cause: An attempt was made to create a partition with a MAXVALUE highbound on an Interval partitioned object.
- Action: Do not create a partition with a MAXVALUE highbound.
- ORA-14762: Domain index creation on interval partitioned tables is not permitted
- Cause: An attempt was made to create a domain index on an interval partitioned table.
- Action: Do not create a domain index on an interval partitioned table.
- ORA-14763: Unable to resolve FOR VALUES clause to a partition number
- Cause: Could not determine the partition corresponding to the FOR VALUES clause.
- Action: Remove bind variables and dependencies on session parameters from the values specified in the FOR VALUES clause.
- ORA-14764: FOR VALUES clause cannot be specified for only one partition
- Cause: An attempt was made to specify the FOR VALUES clause for only one of the two partitions being merged.
- Action: Specify a FOR VALUES clause for each of the two partitions being merged or do not specify the FOR VALUES clause for either.
- ORA-14765: Cannot create a partition while doing a create index
- Cause: An attempt was made to create a partition concurrently with index creation.
- Action: Retry the statement after the index build is finished.
- ORA-14766: Unable to obtain a stable metadata snapshot
- Cause: This operation was not able to obtain a stable snapshot of the interval partitioning metadata.
- Action: Retry the statement.
- ORA-14767: Cannot specify this interval with existing high bounds
- Cause: The interval specified conflicts with the existing high bound for the last partition. The combination might lead to invalid dates for high bounds in the future.
- Action: If this is a CREATE TABLE, try specifying a different high bound value for the last partition, or a different interval. If this is an ALTER TABLE SET INTERVAL, please choose either a different interval, or, modify the table to change the high bound for the last partition.
- ORA-14801: Hash composite partitioning is not supported
- Cause: An attempt was made to partition a table using a Hash composite method.
- Action: Do not partition the table by a Hash composite method.
- ORA-14802: Specified operation is not permitted on Hash composite partitioned objects
- Cause: An unsupported operation was attempted on a Hash composite partitioned object.
- Action: Do not perform the operation on a Hash composite partitioned object.
- ORA-14803: partition bound may not be specified for hash subpartitioned tables
- Cause: A VALUES LESS THAN or VALUES clause was specified with a subpartition description.
- Action: Remove the VALUES LESS THAN or VALUES clause from the subpartition description.
- ORA-15000: command disallowed by current instance type
- Cause: The user has issued a command to a conventional RDBMS instance that is only appropriate for an ASM instance. Alternatively, the user has issued a command to an ASM instance that is only appropriate for an RDBMS instance.
- Action: Connect to the correct instance type and re-issue the command.