Applicability
This topic applies only to OceanBase Database in Oracle mode.
OBE-12000: A materialized view log already exists on table %s
OceanBase Database error code: 9756
SQLSTATE: HY000
Cause: You tried to create a materialized view log on a table that already has a materialized view log. A table can have only one materialized view log.
Solution: All materialized views on the table can use the materialized view log on the table. To modify the existing log, use the
DROP MATERIALIZED VIEW LOGstatement to drop the materialized view log and then recreate it.
Note
This error code is introduced in OceanBase Database V4.2.2.
OBE-12003: Materialized view %s.%s does not exist
OceanBase Database error code: 9757
SQLSTATE: HY000
Cause: The specified materialized view does not exist.
Solution: Enter the correct materialized view name and retry.
Note
This error code is introduced in OceanBase Database V4.2.2.
OBE-12006: Materialized view %s.%s already exists
OceanBase Database error code: 9758
SQLSTATE: HY000
Cause: The specified materialized view already exists.
Solution: If the materialized view already exists and needs to be rebuilt, you can either drop and rebuild it or create a materialized view with a different name.
Note
This error code is introduced in OceanBase Database V4.2.2.
OBE-12034: Materialized view log on %s.%s is younger than last refresh
OceanBase Database error code: 9759
SQLSTATE: HY000
Cause: The materialized view log contains changes that were not recorded when the materialized view was last refreshed.
Solution: Before you perform the next fast refresh, you must perform a complete refresh on the materialized view.
Note
This error code is introduced in OceanBase Database V4.2.2.
OBE-12052: Cannot fast refresh materialized view %s.%s
OceanBase Database error code: 9760
SQLSTATE: HY000
Cause: The definition of the materialized view does not meet the basic requirements for incremental refresh. For example:
- The base table in the definition of the incremental refresh materialized view does not have a materialized view log (mlog) table.
- The definition of the incremental refresh materialized view does not support the use of set operators.
- The columns used in the incremental refresh materialized view must be maintained in the mlog table of the base table.
Solution: Check whether the definition of the incremental refresh materialized view meets the basic requirements for incremental refresh. For more information, see Refresh a materialized view.
Note
This error code is introduced in OceanBase Database V4.3.0.
OBE-12401: Invalid label string
OceanBase Database error code: 5696
SQLSTATE: HY000
Cause: The specified label string cannot be converted to a valid internal label by the policy.
Solution: Correct the syntax of the label string.
OBE-12416: Policy string not found
OceanBase Database error code: 5695
SQLSTATE: HY000
Cause: The specified policy does not exist in the database.
Solution: Enter the correct policy name or create a policy.
OBE-12432: LBAC error: %s
OceanBase Database error code: 5700
SQLSTATE: HY000
Cause: An error occurred during the implementation of label-based access control (LBAC).
Solution: Correct the issue identified in the error message.
OBE-12444: Policy already applied to table
OceanBase Database error code: 5790
SQLSTATE: HY000
Cause: You tried to apply a policy to a table that is already protected by a policy.
Solution: To modify the policy options, predicates, or label functions, remove the policy from the table and apply it again.
OBE-12447: Policy role already exists for policy string
OceanBase Database error code: 5701
SQLSTATE: HY000
Cause: The specified policy name already exists.
Solution: Correct the policy name or drop the existing policy.
OBE-12461: Undefined level string for policy string
OceanBase Database error code: 5698
SQLSTATE: HY000
Cause: The specified level is not defined for the policy.
Solution: Specify the identifier value for the level.
OBE-12462: Undefined compartment string for policy string
OceanBase Database error code: 5697
SQLSTATE: HY000
Cause: The specified compartment is not defined for the policy.
Solution: Specify the identifier value for the compartment.
OBE-12463: Undefined group string for policy string
OceanBase Database error code: 5699
SQLSTATE: HY000
Cause: The specified group is not defined for the policy.
Solution: Specify the identifier value for the group.
OBE-12470: NULL or invalid user label: %s
OceanBase Database error code: 5702
SQLSTATE: HY000
Cause: The specified user label is
NULLor is not authorized.Solution: Specify an authorized label for the user.
OBE-12702: Invalid NLS parameter string used in SQL function
OceanBase Database error code: 5604
SQLSTATE: HY000
Cause: The
NLSparameter string specifies an unknown parameter name or an invalid value.
OBE-12704: COLLATION '%.*s' is not valid for CHARACTER SET '%.*s'
OceanBase error code: 5144
SQLSTATE: 42000
Cause: The error may be caused by one of the following reasons:
The string operands of the operator or built-in function (except for the
nlsparamsparameter) use different character sets.The
nlsparamsoperand is not in the database character set.The string data passed to the built-in function uses a character set other than the database character set, but the built-in function does not accept this character set.
The second parameter of
CHR()orCSCONVERT()is notCHAR_CSorNCHAR_CS.The character set of the string expression in the
VALUESclause of theINSERTstatement or theSETclause of theUPDATEstatement does not match the character set of the column to be inserted.The character set of the value provided in the
DEFAULTclause when creating the table does not match the character set declared for the column.The parameters of the PL function do not meet the character set requirements of the corresponding parameters.
OBE-12704: character set mismatch
OceanBase error code: 5808
SQLSTATE: HY000
Cause: The error may be caused by one of the following reasons:
The string operands of the operator or built-in function (except for the
nlsparamsparameter) use different character sets.The
nlsparamsoperand is not in the database character set.The string data passed to the built-in function uses a character set other than the database character set, but the built-in function does not accept this character set.
The second parameter of
CHR()orCSCONVERT()is notCHAR_CSorNCHAR_CS.The character set of the string expression in the
VALUESclause of theINSERTstatement or theSETclause of theUPDATEstatement does not match the character set of the column to be inserted.The character set of the value provided in the
DEFAULTclause when creating the table does not match the character set declared for the column.The parameters of the PL function do not meet the character set requirements of the corresponding parameters.
OBE-12705 : Cannot access NLS data files or invalid environment specified
OceanBase error code: 5943
SQLSTATE: HY000
Cause:
The
ALTER SESSIONstatement specifies an invalidNLSparameter or value.The environment variables
NLS_LANG,ORA_NLSxx, orORACLE_HOMEare misspelled, making it impossible to find the NLS data files.
Solution:
Check the syntax of the
ALTER SESSIONcommand and theNLSparameter, correct the syntax, and retry the statement.Ensure that the environment variable names are spelled correctly.
OBE-12725: unmatched parentheses in regular expression
OceanBase error code: 5813
SQLSTATE: HY000
Cause: The regular expression does not have a matching pair of parentheses.
Solution: Ensure that the parentheses are correctly matched.
OBE-12726: unmatched bracket in regular expression
OceanBase error code: 5812
SQLSTATE: HY000
Cause: The regular expression does not have a matching pair of brackets.
Solution: Ensure that the brackets are correctly matched.
OBE-12727: invalid back reference in regular expression
OceanBase error code: 5814
SQLSTATE: HY000
Cause: The regular expression contains a backward reference in a subexpression.
Solution: Ensure that a valid subexpression is referenced.
OBE-12728: invalid range in regular expression
OceanBase error code: 5815
SQLSTATE: HY000
Cause: An invalid range is found in the regular expression.
Solution: Ensure that a valid range is used.
OBE-12729: invalid character class in regular expression
OceanBase error code: 5816
SQLSTATE: HY000
Cause: An unknown character class is found in the regular expression.
Solution: Ensure that a valid character class is used.
OBE-12731: invalid collation class in regular expression
OceanBase error code: 5817
SQLSTATE: HY000
Cause: The regular expression contains an unknown collation class.
Solution: Ensure that a valid collation class is used.
OBE-12801: error signaled in parallel query server
OceanBase error code: 5736
SQLSTATE: HY000
Cause: When the PX needs to terminate the execution, it broadcasts this error code to all execution nodes to terminate the current execution.
Solution: Check the execution log for the reason of the interruption or contact Technical Support for assistance.
OBE-12827: insufficient parallel query worker available
OceanBase error code: 5345
SQLSTATE: HY000
Cause: The number of slaves obtained is less than the minimum number defined by the
parallel_servers_targetparameter or the number of slaves reaches the upper limit.Solution: Increase the value of the
parallel_servers_targetparameter and re-execute the query, or wait for some running queries to complete to release the slaves.
OBE-12899: value too large for column '%.*s' at row %ld
OceanBase error code: 5167
SQLSTATE: 22001
Cause: The value of the column to be inserted or updated is too wide.
Solution: Check the correctness of the SQL statement. Check the data types of the source column and the target column. Either increase the width of the target column or use a subset of the source column (i.e., use a substring).
Related issues:
- ## OBE-12899: value too large for column when using virtual columns in an Oracle-compatible tenant
- Reason for the "cannot decrease column length because some value is too big" error
OBE-12984: cannot drop partitioning column '%.*s'
OceanBase error code: 5502
SQLSTATE: HY000
Cause: You are trying to drop a partitioning column from a partitioned table.
Solution: You cannot perform this operation.
Note
This error code was introduced in OceanBase Database V4.2.2.
OBE-12991: column is referenced in a multi-column constraint
OceanBase error code: 5792
SQLSTATE: HY000
Cause: You are trying to drop a column that is referenced by a multi-column constraint.
Solution: Drop all constraints that reference the column or specify
CASCADE CONSTRAINTSin the statement.
OBE-12991: column '%.*s' is referenced in a multi-column constraint '%.*s'
OceanBase Database error code: 5859
SQLSTATE: HY000
Cause: You tried to drop a column that is referenced by a multi-column constraint.
Solution: Drop all constraints that reference the column, or specify
CASCADE CONSTRAINTSin the statement.
OBE-12992: cannot drop parent key column
OceanBase Database error code: 5793
SQLSTATE: HY000
Cause: You tried to drop a parent key column.
Solution: Drop all constraints that reference the parent key column, or specify
CASCADE CONSTRAINTSin the statement.
OBE-13000: dimension number is out of range
OceanBase Database error code: 7290
SQLSTATE: HY000
Cause: The specified dimension is less than 1 or greater than ($2^{64} - 1$).
Solution: Make sure that the dimension number is between 1 and ($2^{64} - 1$).
Note
This error code is introduced in OceanBase Database V4.2.2.
OBE-13028: Invalid Gtype in the SDO_GEOMETRY object
OceanBase Database error code: 7291
SQLSTATE: HY000
Cause: The
SDO_GEOMETRYobject contains an invalidSDO_GTYPE.Solution: Verify whether the geometry has a valid Gtype.
Note
This error code is introduced in OceanBase Database V4.2.2.
OBE-13029: Invalid SRID in the SDO_GEOMETRY object
OceanBase Database error code: 7292
SQLSTATE: HY000
Cause: The
SDO_GEOMETRYobject contains an invalidSDO_SRID. The specified SRID may be out of the valid SRID range.Solution: Verify whether the geometry has a valid SRID.
Note
This error code is introduced in OceanBase Database V4.2.2.
OBE-13031: Invalid Gtype in the SDO_GEOMETRY object for point object
OceanBase Database error code: 7293
SQLSTATE: HY000
Cause: The
SDO_GEOMETRYobject contains an invalidSDO_GTYPE. TheSDO_ELEM_INFO_ARRAYorSDO_ORDINATE_ARRAYis NULL, but theSDO_GTYPEis not of the POINT type.Solution: Verify whether the geometry has a valid Gtype.
Note
This error code is introduced in OceanBase Database V4.2.2.
OBE-13032: Invalid NULL SDO_GEOMETRY object
OceanBase Database error code: 7294
SQLSTATE: HY000
Cause: The
SDO_GEOMETRYobject contains an invalidSDO_POINT_TYPE,SDO_ELEM_INFO_ARRAY, orSDO_ORDINATE_ARRAYfield.Solution: Verify whether the geometry has valid fields. To specify a NULL geometry, specify the entire
SDO_GEOMETRYas NULL, instead of setting each field to NULL.
Note
This error code is introduced in OceanBase Database V4.2.2.
OBE-13033: Invalid data in the SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY object
OceanBase Database error code: 7295
SQLSTATE: HY000
Cause: The
SDO_ELEM_INFO_ARRAYfield of theSDO_GEOMETRYobject contains invalid data.Solution: Verify whether the geometry has valid data.
Note
This error code is introduced in OceanBase Database V4.2.2.
OBE-13034: Invalid data in the SDO_ORDINATE_ARRAY in SDO_GEOMETRY object
OceanBase Database error code: 7296
SQLSTATE: HY000
Cause: The
SDO_ELEM_INFO_ARRAYfield of theSDO_GEOMETRYobject contains invalid data.Solution: Verify whether the geometry has valid data.
Note
This error code is introduced in OceanBase Database V4.2.2.
OBE-13205: internal error while parsing spatial parameters
OceanBase Database error code: 7302
SQLSTATE: 42000
Cause: An internal error occurred while parsing spatial parameters.
Solution: Check the settings of all spatial parameters and make sure that their values are valid and expected.
Note
- This error code is introduced in OceanBase Database V4.3.2.
- This error code is introduced in OceanBase Database V4.2.4.
OBE-13207: incorrect use of the ['%.*s'] operator
OceanBase Database error code: 5804
SQLSTATE: HY000
Cause: An error occurred while using the specified operator.
Solution: Check the parameters and return type of the specified operator.
OBE-13249: A SPATIAL index may only contain a geometrical type column
- OceanBase Database error code: 7279
- SQLSTATE: 42000
- Cause: A SPATIAL index may only contain a geometrical type column.
Note
- This error code was changed from 00600 to 13249 in OceanBase Database V4.3.2.
- This error code is introduced in OceanBase Database V4.1.0.
OBE-13295: geometry objects are in different coordinate systems
OceanBase Database error code: 7300
SQLSTATE: 42000
Cause: Two geometry objects use different coordinate systems during spatial data operations.
Solution: Make sure that the same coordinate reference system is used when creating geometry objects.
Note
- This error code is introduced in OceanBase Database V4.3.2.
- This error code is introduced in OceanBase Database V4.2.4.
OBE-14019: partition bound element must be one of: string, datetime or intervalliteral, number, or MAXVALUE
OceanBase error code: 5275
SQLSTATE: HY000
Cause: The partition bound list contains an element of an invalid type (i.e., not a number, not an empty string, not a datetime or interval literal, and not
MAXVALUE).Solution: Ensure that all elements in the partition bound list are of valid types.
OBE-14019: partition bound element must be one of: string, datetime or intervalliteral, number, or MAXVALUE
OceanBase error code: 5285
SQLSTATE: HY000
Cause: The partition bound list contains an element of an invalid type (i.e., not a number, not an empty string, not a datetime or interval literal, and not
MAXVALUE).Solution: Ensure that all elements in the partition bound list are of valid types.
OBE-14020: this physical attribute may not be specified for a table partition
- OceanBase error code: 4398
- SQLSTATE: HY000
- Cause: An incompatible partitioning method was used when creating a partitioned table, such as using both RANGE/LIST and HASH/KEY partitioning in subpartitions.
- Solution:
- Change the partitioning method: If you want to use both RANGE/LIST and HASH/KEY partitioning in subpartitions, consider changing to a compatible partitioning method. Note that changing the partitioning method or splitting a partitioned table may affect existing data and applications. Proceed with caution.
- Separate partitions: If you need to use an incompatible partitioning method, consider splitting the partitioned table into multiple tables, each using a different partitioning method.
Note
This error code was introduced in OceanBase Database V4.2.0.
OBE-14036: partition bound value too large for column
OceanBase error code: 5354
SQLSTATE: 22001
Cause: The length of the partition bound value exceeds the length of the corresponding partitioning column.
Solution: Ensure that the length of the partition bound value does not exceed the length of the corresponding partitioning column.
OBE-14037: partition bound of partition '%.*s' is too high
OceanBase error code: 5281
SQLSTATE: HY000
Cause: The upper bound of the partition is greater than the upper bound of the next partition, which is invalid.
Solution: Ensure that the upper bound of each partition (except the last one) is less than the upper bound of the next partition.
OBE-14047: ALTER TABLE|INDEX RENAME may not be combined with other operations
OceanBase error code: 5863
SQLSTATE: HY000
Cause: The
ALTER TABLEorALTER INDEXstatement attempts to combine theRENAMEoperation with other operations, which is invalid.Solution: Ensure that the
ALTER TABLEorALTER INDEXstatement contains only theRENAMEoperation.
OBE-14060: data type or length of a
table partitioning column may not be changed
OceanBase error code: 5895
SQLSTATE: HY000
Cause: The
ALTER TABLEstatement attempts to modify the data type or length of the partitioning column specified in the statement, which is invalid.Solution: Avoid modifying the data type or length of the partitioning column.
OBE-14074: partition bound must collate higher than that of the last partition
OceanBase error code: 5353
SQLSTATE: HY000
Cause: The partition bound specified in the
ALTER TABLE ADD PARTITIONstatement is not higher than the bound of the last partition of the table, which is invalid.Solution: Ensure that the partition bound of the partition to be added is higher than the bound of the last partition of the table.
OBE-14082: New partition name %.*s must differ from that of any other partition or subpartition of the object
- OceanBase error code: 5493
- SQLSTATE: HY000
- Cause: When renaming a partition of a table, the new partition name is the same as the name of an existing partition (either a primary or subpartition) of the table.
- Solution: Rename the partition or delete the duplicate partition.
Note
This error code was introduced in OceanBase Database V4.2.0.
OBE-14096: tables in ALTER TABLE EXCHANGE PARTITION must have the same number of columns
OceanBase error code: 4774
SQLSTATE: HY000
Cause: When executing the
ALTER TABLE EXCHANGE PARTITIONoperation, the tables to be exchanged must have the same number of columns.Solution: Ensure that the tables to be exchanged have the same number of columns.
Note
This error code was introduced in OceanBase Database V4.3.1.
OBE-14097: column type or size mismatch in ALTER TABLE EXCHANGE PARTITION
OceanBase error code: 4775
SQLSTATE: HY000
Cause: When executing the
ALTER TABLE EXCHANGE PARTITIONoperation, the column types or sizes do not match.Solution: Check the columns involved in the exchange and ensure their types and sizes are consistent.
Note
This error code was introduced in OceanBase Database V4.3.1.
OBE-14098: index mismatch for tables in ALTER TABLE EXCHANGE PARTITION
OceanBase error code: 4776
SQLSTATE: HY000
Cause: When executing the
ALTER TABLE EXCHANGE PARTITIONoperation, the table indexes do not match.Solution: Check and ensure that the indexes on the tables to be exchanged match.
Note
This error code was introduced in OceanBase Database V4.3.1.
OBE-14100: partition extended table name cannot refer to a remote object
OceanBase error code: 5899
SQLSTATE: HY000
Cause: An attempt was made to name a remote object using the extended partition table syntax, which is incorrect.
Solution: Correct the expression and retry.
OBE-14109: Partition-extended object names may only be used with tables and editioning views
OceanBase Database error code: 5977
SQLSTATE: HY000
Cause: A partition-extended object name is used for an object that is not a table or an editioning view.
Solution: Do not use the partition-extended object name syntax for objects that are not tables or editioning views.
Note
This error code is introduced in OceanBase Database V4.0.0.
OBE-14118: CHECK constraint mismatch in ALTER TABLE EXCHANGE PARTITION
OceanBase Database error code: 4777
SQLSTATE: HY000
Cause: The CHECK constraints of the tables involved in the
ALTER TABLE EXCHANGE PARTITIONstatement do not match.Solution: Make sure that the CHECK constraints of the tables involved in the
ALTER TABLE EXCHANGE PARTITIONstatement match.
Note
This error code is introduced in OceanBase Database V4.3.1.
OBE-14128: FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE PARTITION
OceanBase Database error code: 4778
SQLSTATE: HY000
Cause: The foreign key constraints of the tables involved in the
ALTER TABLE EXCHANGE PARTITIONstatement do not match.Solution: Check the tables and foreign key constraints involved in the
ALTER TABLE EXCHANGE PARTITIONstatement and make sure that they match.
Note
This error code is introduced in OceanBase Database V4.3.1.
OBE-14159: Duplicate subpartition name
OceanBase Database error code: 5867
SQLSTATE: HY000
Cause: The names of the subpartitions in the table or index are not unique.
Solution: Rename the subpartitions to ensure that the names of the subpartitions in the table or index are unique.
OBE-14170: Cannot specify <(sub)partition-description> clause in CREATE TABLE or CREATE INDEX
OceanBase Database error code: 5866
SQLSTATE: HY000
Cause: The
PARTITIONS number-of-partitionsclause is specified when the <(sub)partition-description> clause is also specified in aCREATE TABLEorCREATE INDEXstatement. This is invalid.Solution: Remove one of the invalid clauses.
OBE-14214: VALUES (
) cannot be used for Range subpartitioned tables
OceanBase Database error code: 5876
SQLSTATE: HY000
Cause: The
VALUES (value list)clause is used for a RANGE subpartitioned table.Solution: Use the
VALUES LESS THANorATclause with a RANGE subpartitioned table.
OBE-14217: VALUES (
) clause expected
OceanBase Database error code: 5877
SQLSTATE: HY000
Cause: The
VALUES (value list)clause is not specified for a LIST subpartitioned table.Solution: Specify the
VALUES (value list)clause.
OBE-14251: Specified subpartition does not exist
OceanBase Database error code: 5830
SQLSTATE: HY000
Cause: The specified subpartition does not exist.
Solution: Use the correct subpartition name and retry.
OBE-14253: Table is not partitioned by composite partition method
OceanBase Database error code: 5875
SQLSTATE: HY000
Cause: At least one of the following conditions is true:
The table involved in a subpartition maintenance operation (
ALTER TABLE [EXCHANGE | MODIFY | MOVE | TRUNCATE] SUBPARTITIONorALTER TABLE MODIFY PARTITION [ADD | COALESCE] SUBPARTITION) is not partitioned by using the composite partition method.The table involved in the
MODIFY DEFAULT ATTRIBUTES FOR PARTITIONoperation is partitioned by using a method other than the composite partition method.The table involved in the
ALTER TABLE MODIFY SUBPARTITION [UNUSABLE LOCAL INDEXES | REBUILD UNUSABLE LOCAL INDEXES]statement is not partitioned by using the composite partition method.
Solution: Make sure that the table is partitioned by using the composite partition method.
OBE-14263: New subpartition name %.*s must differ from that of any other partition or subpartition of the object
- OceanBase Database error code: 5494
- SQLSTATE: HY000
- Cause: The name of the subpartition that is being modified is the same as the name of another partition or subpartition of the table.
- Solution: Modify the name of the subpartition or drop the duplicate partition.
Note
This error code is introduced in OceanBase Database V4.2.0.
OBE-14265: Data type or length of a
table subpartitioning column may not be changed
OceanBase Database error code: 5896
SQLSTATE: HY000
Cause: The
ALTER TABLEstatement is used to modify the data type or length of a subpartitioning column specified in theALTER TABLEstatement. This is invalid.Solution: Do not modify the data type or length of a subpartitioning column of a table.
OBE-14291: Cannot EXCHANGE a composite partition with a non-partitioned table
OceanBase Database error code: 4779
SQLSTATE: HY000
Cause: A composite partition cannot be exchanged with a non-partitioned table.
Solution: Make sure that the target table for exchange has the corresponding partitioning attributes.
Note
This error code is introduced in OceanBase Database V4.3.1.
OBE-14300: Partitioning key maps to a partition outside maximum permitted number of partitions
OceanBase Database error code: 6274
SQLSTATE: HY000
Cause: The number of partitions mapped by the partitioning key of the inserted row exceeds 1048575.
Solution: Make sure that the number of partitions or subpartitions mapped by the partitioning key is within 1048575.
Note
This error code is introduced in OceanBase Database V4.0.0.
OBE-14308: The partition bound element must be one of: string, datetime, or interval literal, number, or NULL
OceanBase Database error code: 5355
SQLSTATE: HY000
Cause: The partition bound list contains an element of an invalid type (i.e., not a number, not an empty string, not a datetime or interval literal, and not
NULL).Solution: Ensure that all elements in the partition bound list are of valid types.
OBE-14310: The VALUES LESS THAN or AT clause cannot be used with list partitioned tables
OceanBase Database error code: 5878
SQLSTATE: HY000
Cause: The
VALUES LESS THANorVALUES LESS ATclause can be used only with RANGE partitioned tables.Solution: Use the
VALUES (value list)clause with list partitioned tables.
OBE-14311: Expecting VALUES LESS THAN or AT clause
OceanBase Database error code: 5879
SQLSTATE: HY000
Cause: The
VALUES (value list)clause can be used only with list partitioned tables.Solution: Use the
VALUES LESS THANclause with RANGE partitioned tables.
OBE-14312: Invalid time limit specified
OceanBase Database error code: 5882
SQLSTATE: HY000
Cause: The
timeparameter of thedbms_lock.sleep(time)package specifies a non-positive value.Solution: Specify a positive value.
OBE-14318: DEFAULT partition must be last partition specified
- OceanBase Database error code: 5491
- SQLSTATE: 42000
- Cause: The DEFAULT partition must be the last partition specified.
Note
This error code is introduced in OceanBase Database V4.1.0.
OBE-14400: Inserted partition key does not map to any partition
OceanBase Database error code: 5284
SQLSTATE: HY000
Cause:
You attempt to insert a record into a
RANGEorCOMPOSITE RANGEobject, but the partition keys of multiple rows in theRANGEorCOMPOSITE RANGEobject exceed the partition bound list of the last partition.You attempt to insert a record into a
LISTobject, but the partition key does not match any of the text values specified in the partitions.
Solution: Do not insert this key, or add a partition that can receive this key, or add a value that matches this key to the partition configuration.
OBE-14402: Updating partition key column would cause a partition change
OceanBase Database error code: 5350
SQLSTATE: HY000
Cause: The
UPDATEoperation causes the partition of the row to change.Solution: Enable the
enable row movementattribute of the table.
OBE-14450: Attempt to access a transactional temp table already in use
OceanBase Database error code: 6333
SQLSTATE: HY000
Cause: A session is using the global temporary table, blocking the current DDL request.
Solution: To resolve this, end the session using the temporary table. For transaction-level temporary tables, commit the transaction to release the table. For session-level temporary tables, either
truncatethe table or end the session holding it.
Note
This error code is introduced in OceanBase Database V4.4.2.
OBE-14501: Object is not partitioned
OceanBase Database error code: 5829
SQLSTATE: HY000
Cause: The table or index is not partitioned. The syntax is invalid.
Solution: Retry the command using the correct syntax.
OBE-14551: Cannot perform a DML operation inside a query
OceanBase Database error code: 9709
SQLSTATE: HY000
Cause: DML operations such as insert, update, delete, and query update cannot be performed inside a query or a PDML subordinate device.
Solution: Ensure that the problematic DML operation is not performed, or execute the DML operation in an autonomous transaction within a query or a PDML subordinate device.
Note
This error code is introduced in OceanBase Database V4.0.0.
OBE-14552: Cannot perform a DDL commit or rollback inside a query or DML tips
OceanBase Database error code: 9710
SQLSTATE: HY000
Cause: DDL operations such as creating tables and views and transaction control statements such as commit and rollback cannot be performed in a query or a DML statement.
Solution: Ensure that the violation operation is not performed, or execute the operation in an autonomous transaction within a query or a DML operation.
Note
This error code is introduced in OceanBase Database V4.0.0.
OBE-14750: Range partitioned table with INTERVAL clause has more than one column
OceanBase Database error code: 5997
SQLSTATE: HY000
Cause: You create an interval partitioned table with multiple partitioning columns.
Solution: Use a single partitioning column.
Note
This error code is introduced in OceanBase Database V4.0.0.
OBE-14751: Invalid data type for partitioning column of an interval partitioned table
OceanBase Database error code: 5998
SQLSTATE: HY000
Cause: You use interval partitioning for a table with a partitioning column of a data type other than number or date/time.
Solution: Use only number or date/time columns as the partitioning columns of interval partitioned tables.
Note
This error code is introduced in OceanBase Database V4.0.0.
OBE-14752: Interval expression is not a constant of the correct type
OceanBase Database error code: 5999
SQLSTATE: HY000
Cause: You use a non-constant interval or an interval of a data type that does not match the partitioning column.
Solution: Use only constant expressions for intervals. If the data type of the partitioning column is number, the interval must be a number constant. If the data type is date/time, the interval must be an interval constant.
Note
This error code is introduced in OceanBase Database V4.0.0.
OBE-14753: Interval cannot be zero
OceanBase Database error code: 6273
SQLSTATE: HY000
Cause: The interval is mapped to 0.
Solution: Use a non-zero interval.
Note
This error code is introduced in OceanBase Database V4.0.0.
OBE-14757: Table is already a range partitioned table
OceanBase Database error code: 6000
SQLSTATE: HY000
Cause: The
SET INTERVAL()clause is used to convert an interval-partitioned table to a range-partitioned table. It is not allowed to use this clause on a range-partitioned table.Solution: Use the
SET INTERVAL()clause only on an interval-partitioned table.
Note
This error code is introduced in OceanBase Database V4.0.0.
OBE-14758: Last partition in the range section cannot be dropped
OceanBase Database error code: 4730
SQLSTATE: HY000
Cause: The last RANGE partition of an interval-partitioned table is dropped.
Solution: Do not drop the last RANGE partition of an interval-partitioned table.
Note
This error code is introduced in OceanBase Database V4.0.0.
OBE-14759: SET INTERVAL is not legal on this table
OceanBase Database error code: 4731
SQLSTATE: HY000
Cause: The
SET INTERVALclause is specified. TheALTER TABLE SET INTERVALstatement is applicable only to aRANGEpartitioned table with a single partitioning column. In addition, theMAXVALUEpartition cannot be specified for this partitioned table.Solution: Use the
SET INTERVALclause only on valid tables.
Note
This error code is introduced in OceanBase Database V4.0.0.
OBE-14760: ADD PARTITION is not permitted on Interval partitioned objects
OceanBase Database error code: 6269
SQLSTATE: HY000
Cause: A partition is added to an interval-partitioned object by using the
ALTER TABLE ADD PARTITIONstatement.Solution: Do not perform this operation on interval-partitioned objects. Instead, insert a row to create a new partition.
OBE-14761: MAXVALUE partition cannot be specified for Interval partitioned objects
OceanBase Database error code: 6270
SQLSTATE: HY000
Cause: A partition or subpartition with the
MAXVALUEupper bound is created for an interval-partitioned or interval-subpartitioned object.Solution: Do not create a partition or subpartition with the
MAXVALUEupper bound.
OBE-14767: Cannot specify this interval with existing high bounds
OceanBase Database error code: 6271
SQLSTATE: HY000
Cause: The specified interval conflicts with the upper bound of the last partition. This combination may result in an invalid upper bound in the future.
Solution: If you are executing the
CREATE TABLEstatement, try to specify a different upper bound or a different interval for the last partition. If you are executing theALTER TABLE SET INTERVALstatement, select a different interval or modify the table to change the upper bound of the last partition.
OBE-16000: standby tenant is read only
OceanBase Database error code: 4688
SQLSTATE: HY000
Cause: The standby cluster only supports read operations. DDL statements that modify data will trigger this error.
Solution: If you want to modify the standby cluster, you need to switch its role to primary.
OBE-19010: Cannot insert XML fragments
- OceanBase Database error code: 7411
- SQLSTATE: 42000
- Cause: An invalid XML document is inserted.
- Solution:
- Check the XML data: Verify that the XML data to be inserted is complete and conforms to the XML document specification.
- Use the XMLType data type: Store XML data as a separate XMLType column by using the XMLType data type.
Note
This error code is introduced in OceanBase Database V4.2.0.
OBE-19012: Cannot convert XML fragment to the required datatype
- OceanBase Database error code: 7406
- SQLSTATE: 42000
- Cause: The data type does not match or is invalid when an XML fragment is converted to the required data type.
- Solution: Check the data type or XML data to ensure they are correct.
Note
This error code is introduced in OceanBase Database V4.2.0.
OBE-19025: EXTRACTVALUE cannot extract values of multiple nodes
- OceanBase Database error code: 7405
- SQLSTATE: 42000
- Cause: The EXTRACTVALUE function cannot extract values from multiple nodes.
- Solution: Use other functions or redesign the query statement.
Note
This error code is introduced in OceanBase Database V4.2.0.
OBE-19026: EXTRACTVALUE can only retrieve value of leaf nodetoo small
- OceanBase Database error code: 7410
- SQLSTATE: 42000
- Cause: The EXTRACTVALUE function is used to extract a value from a non-leaf node.
- Solution: Check the XPath expression to ensure that it points to a leaf node.
Note
This error code is introduced in OceanBase Database V4.2.0.
OBE-19044: character length specified for XMLSerialize is too small
- OceanBase Database error code: 7408
- SQLSTATE: 42000
- Cause: The specified character length is too small when the XMLSerialize function is used.
- Solution: Check the character length or data size to ensure that it is sufficient to accommodate all data.
Note
This error code is introduced in OceanBase Database V4.2.0.
OBE-19102: XQuery string literal expected
OceanBase Database error code: 7423
SQLSTATE: 42000
Cause: The XQuery expression is not enclosed in a string literal.
Solution: Specify the XQuery expression as a string literal.
Note
This error code is introduced in OceanBase Database V4.2.2.
OBE-19110: unsupported XQuery expression
OceanBase Database error code: 7428
SQLSTATE: 42000
Cause: The expression specified in the XQuery is not supported.
Solution: Rewrite the XQuery using a supported expression.
Note
This error code is introduced in OceanBase Database V4.2.2.
OBE-19114: XPST0003 - error during parsing the XQuery expression: %.*s
OceanBase Database error code: 7422
SQLSTATE: 42000
Cause: An error occurred while parsing the XQuery expression.
Solution: Check the detailed error message to identify the cause.
Note
This error code is introduced in OceanBase Database V4.2.2.
OBE-19118: XQST0066 - duplicate default namespace definition - %s
OceanBase Database error code: 7420
SQLSTATE: 42000
Cause: The given namespace URI is specified in multiple default namespace declarations.
Solution: Remove the duplicate default namespace declaration.
Note
This error code is introduced in OceanBase Database V4.2.2.
OBE-19208: parameter %d of function XMLELEMENT must be aliased
- OceanBase Database error code: 7413
- SQLSTATE: 42000
- Cause: The nth attribute parameter of the XMLELEMENT() function does not have an alias.
- Solution:
- Check the syntax of the XMLELEMENT() function attribute to ensure it is correct and valid.
- Confirm whether the attribute parameter of the XMLELEMENT() function specifies an alias.
Note
This error code is introduced in OceanBase Database V4.2.0.
OBE-19224: XPTY0004 - XQuery static type mismatch: expected - node()* got -
OceanBase Database error code: 7425
SQLSTATE: 42000
Cause: The static type of the expression is not compatible with the context in which it is used.
Solution: Fix the expression to the required type or add an appropriate conversion function to the expression.
Note
This error code is introduced in OceanBase Database V4.2.2.
OBE-19253: XPST0033 - too many declarations for namespace prefix %.*s
OceanBase Database error code: 7424
SQLSTATE: 42000
Cause: The query prolog contains multiple declarations for the same namespace prefix.
Solution: Remove the duplicate namespace prefix declaration.
Note
This error code is introduced in OceanBase Database V4.2.2.
OBE-19279: XPTY0004 - XQuery dynamic type mismatch: expected singleton sequence - got multi-item sequence
OceanBase Database error code: 7421
SQLSTATE: 42000
Cause: The XQuery sequence contains more than one item.
Solution: Modify the XQuery expression to return a single-item sequence.
Note
This error code is introduced in OceanBase Database V4.2.2.
OBE-19276: XPST0005 - XPath step specifies an invalid element/attribute name: %.*s
OceanBase Database error code: 7426
SQLSTATE: 42000
Cause: The XPath step specifies an invalid element or attribute name. The element or attribute name does not match any node based on the input XML schema or structure.
Solution: Modify the element or attribute name.
Note
This error code is introduced in OceanBase Database V4.2.2.
OBE-19277: XPST0005 - XPath step specifies an item type matching no node: %.*s
OceanBase Database error code: 7427
SQLSTATE: 42000
Cause: The item type specified by the XPath step does not match any node based on the input XML schema or structure.
Solution: Modify the item type to the correct node type.
Note
This error code is introduced in OceanBase Database V4.2.2.
