Oracle 12c R2 Error Codes and Solution Suggestions from ORA-14800 to ORA-15000
- 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.
Cause: An unsupported operation was attempted on a Hash composite partitioned object.
Action: Do not perform the operation on a Hash composite partitioned object.
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.
Cause: An ALTER TABLE SPLIT PARTITION contained a description for only one resulting partition.
Action: Specify at least 2 resulting partitions.
Cause: An ALTER TABLE SPLIT PARTITION contained a description for the last partition which included the bounds.
Action: Do not specify bounds for the last resulting partition.
Cause: An ALTER TABLE MERGE PARTITIONS or MERGE SUBPARTITIONS with more than two source partitions or subpartitions was issued. Merging more than two partitions or subpartitions is only supported for heap tables.
Action: Specify exactly two partitions or subpartitions to merge.
- ORA-14807: merging partitions or subpartitions using name TO name syntax is only supported for range partitioned tables
Cause: An ALTER TABLE MERGE PARTITIONS pname TO pname or an ALTER TABLE MERGE SUBPARTITIONS subpname TO subpname was issued. This is only supported for range partitions or subpartitions.
Action: Specify all the partitions or subpartitions to be merged.
Cause: An ALTER TABLE MOVE PARTITION ONLINE or ALTER TABLE MODIFY PARTITION INDEXING or ALTER TABLE SPLIT PARTITION ONLINE statement was issued on a table that was either not a heap-organized table or had an object type, domain index or bitmap join index defined on it. Or, the source table of the split online has reference partitioned child tables. This operation is only supported for heap-organized tables.
Action: Do not use the ONLINE keyword or the INDEXING clause.
Cause: An ALTER TABLE MOVE PARTITION ONLINE or an ALTER TABLE MODIFY PARTITION INDEXING statement was issued on a table owned by SYS, SYSTEM, PUBLIC, OUTLN, or XDB.
Action: Do not use the ONLINE keyword or the INDEXING clause.
Cause: An ALTER TABLE MOVE PARTITION ONLINE statement was issued on a table while the database was not open or was in migrate mode.
Action: Do not use the ONLINE keyword.
Cause: An online DDL with an INCLUDING ROWS clause was issued on a table while supplemental logging was enabled.
Action: Do not use the ONLINE keyword.
Cause: A DBMS_LOB operation was issued on a LOB while an ALTER TABLE MOVE PARTITION ONLINE was concurrently executing on the partition containing the LOB.
Action: Reissue DBMS_LOB operation after MOVE PARTITION ONLINE has completed.
- ORA-14813: ONLINE MOVE OR SPLIT PARTITION not supported while there are too many table segments and index segments
Cause: An ALTER TABLE MOVE or SPLIT PARTITION ONLINE command was issued on a table while the number of table segments multiplied by the number of index segments exceeded the maximum allowed.
Action: Do not use the ONLINE keyword.
- ORA-14850: Adding a partition with DEFAULT high value is not permitted on Autolist partitioned objects.
Cause: An attempt was made to add a DEFAULT partition to an Autolist partitioned object.
Action: Do not perform the operation on an Autolist partitioned object. Insert a row to create the new partition.
Cause: An attempt was made to create a [sub]partition with a DEFAULT high value on an AUTOLIST [sub]partitioned object.
Action: Do not create a [sub]partition with a DEFAULT high value.
Cause: SET [SUB]PARTITIONING AUTOMATIC clause was specified. ALTER TABLE SET [SUB]PARTITIONING AUTOMATIC is only legal on a list partitioned table. Additionally, this table cannot have a DEFAULT partition.
Action: Use SET [SUB]PARTITIONING AUTOMATIC only on a valid table.
Cause: SET [SUB]PARTITIONING clause was used with an invalid option. The only valid options are AUTOMATIC and MANUAL.
Action: Use valid options.
Cause: SET [SUB]PARTITIONING MANUAL clause was specified. ALTER TABLE SET [SUB]PARTITIONING MANUAL is only legal on a list partitioned table. Additionally, this table cannot have a DEFAULT partition.
Action: Use SET [SUB]PARTITIONING MANUAL only on a valid table.
Cause: An attempt to specify SET [SUB]PARTITIONING MANUAL on a list (sub)partitioned table failed. SET [SUB]PARTITIONING MANUAL is used to convert an autolist (sub)partitioned table to a list (sub)partitioned table.
Action: Use SET [SUB]PARTITIONING MANUAL on an autolist (sub)partitioned table.
Cause: An attempt to specify SET [SUB]PARTITIONING AUTOLIST on an autolist (sub)partitioned table failed. SET [SUB]PARTITIONING AUTOLIST is used to convert a list (sub)partitioned table to an autolist (sub)partitioned table.
Action: Use SET [SUB]PARTITIONING AUTOLIST on an autolist (sub)partitioned table.
Cause: An attempt was made to create an autolist subpartitioned table without a subpartition template.
Action: Use a subpartition template when creating an autolist subpartitioned table.
Cause: An attempt was made to set an empty subpartition template for an autolist subpartitioned table.
Action: Convert this table to a list subpartitioned table before set empty template.
Cause: An attempt was made to create an interval subpartitioned table with more than one subpartitioning column.
Action: Use a single subpartitioning column.
Cause: An attempt was made to create an interval subpartitioned table without a subpartition template.
Action: Use a subpartition template when creating an interval subpartitioned table.
Cause: ALTER TABLE ADD SUBPARTITION was attempted on an interval subpartitioned object.
Action: Do not add a subpartition on an interval subpartitioned object. Insert a row to create the new subpartition.
Cause: An attempt was made to set an empty subpartition template for an interval subpartitioned table.
Action: Convert this table to a range subpartitioned table before set empty template.
Cause: The logical transaction ID has been purged and the commit failed.
Action: Reconnect and re-run the transaction.
Cause: The transaction tried to commit during replay.
Action: Contact Oracle Support Services.
Cause: The partition of the transaction history table had not been created.
Action: Contact Oracle Support Services.
Cause: The logical transaction was corrupt. The size was incorrect.
Action: Verify your network configuration.
Cause: The logical transaction was corrupt. The database ID was incorrect.
Action: Verify your network configuration.
Cause: The transaction tried to replay a serializable transaction.
Action: This is not supported.
Cause: The transaction tried to execute get LTXID outcome on the current session.
Action: Check the parameters used to invoke get LTXID outcome.
Cause: The transaction tried to execute get LTXID outcome for a different user session.
Action: Check the parameters used to invoke get LTXID outcome.
Cause: Get LTXID outcome could not be executed because a transaction was open.
Action: Invoke get LTXID outcome after the transaction has been completed.
- ORA-14909: Current session has been blocked by another user with the same user name using GET_LTXID_OUTCOME.
Cause: Could not commit after GET_LTXID_OUTCOME was invoked.
Action: Contact Oracle Support Services.
- ORA-14910: Sessions with SYSDBA privilege are not allowed to connect to a service that has commit outcome enabled.
Cause: A session with SYSDBA privilege tried to connect to a service that has commit outcome enabled.
Action: Connect without the SYSDBA privilege.
Cause: The logical transaction was marked invalid.
Action: Verify your configuration. Transaction Guard does not support XA transactions that use the two-phase commit protocol.
Cause: An invalid parameter was specified.
Action: Specify a valid parameter.
Cause: An invalid database session was specified.
Action: Specify a valid database session.
Cause: The Database Resident Connection Pooling (DRCP) client tried to switch services while Transaction Guard was enabled.
Action: None
Cause: The client transaction had been commited or forced earlier.
Action: None
Cause: The client transaction had not been seen by the server and could not be forced. This can happen if the server is restored or a flashback operation has been executed.
Action: None
Cause: The force outcome operation failed. See previous error for the reason.
Action: None
Cause: The partition IDs of the transaction history table were not consecutive.
Action: Specify the next higer partition ID.
Cause: The tablespace did not exist.
Action: Specify an existing tablespace.
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.