Applicability
This content applies only to the Oracle-compatible mode of OceanBase Database.
OBE-12000:a materialized view log already exists on table %s
OceanBase error code: 9756
SQLSTATE: HY000
Cause: You are trying to create a materialized view log on a table that already has one. Each primary table can have only one materialized view log.
Solution: All materialized views on a table can use the materialized view log of that table. To change the existing log, use the
DROP MATERIALIZED VIEW LOGcommand to drop the materialized view log and then recreate it.
Note
This error code is introduced in V4.2.2.
OBE-12003:materialized view %s.%s does not exist
OceanBase error code: 9757
SQLSTATE: HY000
Cause: The materialized view object with the given owner and name was not found.
Solution: Please try again.
Note
This error code is introduced in V4.2.2.
OBE-12006:materialized view %s.%s already exists
OceanBase error code: 9758
SQLSTATE: HY000
Cause: The materialized view already exists.
Solution: If you find that the materialized view already exists and needs to be rebuilt, delete it if necessary and rebuild it, or create a materialized view with a different name.
Note
This error code is introduced in V4.2.2.
OBE-12034:materialized view log on %s.%s younger than last refresh
OceanBase error code: 9759
SQLSTATE: HY000
Error cause: The materialized view log contains changes newer than those recorded during the last refresh of the materialized view.
Solution: Before performing the next fast refresh, you need to execute a complete refresh for the materialized view.
Note
This error code is introduced in V4.2.2.
OBE-12052:cannot fast refresh materialized view %s.%s
OceanBase error code: 9760
SQLSTATE: HY000
Error cause: The basic requirements for creating an incremental refresh materialized view are not met. For example:
- The base table in the definition of the incremental refresh materialized view does not have a materialized view log (mlog) table created.
- The definition of the incremental refresh materialized view does not support set operators.
- The columns used in the incremental refresh materialized view must be maintained in the base table's mlog.
Solution: Check whether the definition for creating the incremental refresh materialized view meets the basic requirements for incremental refresh. For more information about the basic requirements, see Refresh a materialized view.
Note
This error code is introduced in V4.3.0.
OBE-12401:invalid label string
OceanBase error code: 5696
SQLSTATE: HY000
Error cause: The policy cannot convert the label string into a valid internal label.
Solution: Correct the syntax of the label string.
OBE-12416:policy string not found
OceanBase error code: 5695
SQLSTATE: HY000
Error 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 error code: 5700
SQLSTATE: HY000
Error cause: An error occurred during Label-based access control (LBAC) enforcement.
Solution: Correct the issue identified in the error message.
OBE-12444: policy already applied to table
OceanBase error code: 5790
SQLSTATE: HY000
Error cause: You attempted to apply a policy to a table that is already protected by a policy.
Solution: To change 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 error code: 5701
SQLSTATE: HY000
Error cause: The policy name already exists.
Solution: Correct the policy name or delete the existing policy.
OBE-12461: undefined level string for policy string
OceanBase error code: 5698
SQLSTATE: HY000
Error cause: The specified level is not defined for the policy.
Solution: Specify a level identifier value for the policy.
OBE-12462: undefined compartment string for policy string
OceanBase error code: 5697
SQLSTATE: HY000
Error cause: The specified component is not defined for the policy.
Solution: Define a component identifier value for the policy.
OBE-12463: undefined group string for policy string
OceanBase error code: 5699
SQLSTATE: HY000
Cause: The specified group is not defined for the policy.
Solution: Define a group identifier value for the policy.
OBE-12470:NULL or invalid user label: %s
OceanBase error code: 5702
SQLSTATE: HY000
Cause: The input user label is
NULLor not within the authorized user range.Solution: Enter an authorized user label.
OBE-12702:invalid NLS parameter string used in SQL function
OceanBase 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: One of the following situations may be the case:
The string operands of the operator or built-in functions (except for the
nlsparamsparameter) use different character sets.The
nlsparamsoperand is not in the database character set.The string data passed to a built-in function uses a character set other than the database character set, but the built-in function does not accept that character set.
The second parameter of
CHR()orCSCONVERT()is notCHAR_CSorNCHAR_CS.The character set of the string expression in the
VALUESclause of anINSERTstatement or theSETclause of anUPDATEstatement is inconsistent with the character set used by the column to be inserted.The character set used by the value provided in the
DEFAULTclause when creating the table is inconsistent with the character set declared for the column.The parameters of a 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: One of the following situations may have occurred:
The string operands of operators or built-in functions (except for the
nlsparamsparameter) use different character sets.The
nlsparamsoperand is not in the database character set.The string data passed to a built-in function uses a character set other than the database character set, and the built-in function does not accept that character set.
The second parameter of
CHR()orCSCONVERT()is notCHAR_CSorNCHAR_CS.The character set of a string expression in the
VALUESclause of anINSERTstatement or in theSETclause of anUPDATEstatement is inconsistent with the character set used by the column to be inserted.The character set of the value provided in the
DEFAULTclause when creating a table is inconsistent with the character set declared for the column.The parameters of a 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:
An invalid
NLSparameter or value was specified for theALTER SESSIONstatement.The environment variables
NLS_LANG,ORA_NLSxx, orORACLE_HOMEare misspelled, preventing the NLS data files from being found.
Solution:
Check the syntax of the
ALTER SESSIONcommand andNLSparameters, correct the syntax, and retry the statement.Ensure the environment variable names are spelled correctly.
OBE-12725:unmatched parentheses in regular expression
OceanBase error code: 5813
SQLSTATE: HY000
Cause: The regular expression has unmatched parentheses.
Solution: Ensure the parentheses are correctly matched.
OBE-12726:unmatched bracket in regular expression
OceanBase error code: 5812
SQLSTATE: HY000
Error cause: The regular expression does not have symmetric brackets.
Solution: Ensure the brackets are correctly symmetrical.
OBE-12727:invalid back reference in regular expression
OceanBase error code: 5814
SQLSTATE: HY000
Error cause: There is a back reference in a subexpression.
Solution: Ensure the referenced subexpression is valid.
OBE-12728:invalid range in regular expression
OceanBase error code: 5815
SQLSTATE: HY000
Error cause: An invalid range was found in the regular expression.
Solution: Ensure a valid range is being used.
OBE-12729:invalid character class in regular expression
OceanBase error code: 5816
SQLSTATE: HY000
Error cause: An unknown character class was found in the regular expression.
Solution: Ensure 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 PX needs to terminate execution, it broadcasts this error code to all execution nodes to stop the current execution.
Solution: Check the execution logs for the cause of the interruption or contact technical support for assistance.
OBE-12827:insufficient parallel query worker available
OceanBase error code: 5345
SQLSTATE: HY000
Cause: The specified
parallel_servers_targetparameter results in fewer slaves than the minimum defined by the parameter or the number of slaves has reached 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 free up slaves.
OBE-12899:value too large for column '%.*s' at row %ld
OceanBase error code: 5167
SQLSTATE: 22001
Cause: The value attempted to be inserted or updated into the column is too wide.
Solution: Check the correctness of the SQL statement. Verify the data types of the source and target columns. Either widen the target column or use a subset of the source column (i.e., use a substring).
OBE-12984:cannot drop partitioning column '%.*s'
OceanBase error code: 5502
SQLSTATE: HY000
Cause: You tried to delete the partitioning key from a partitioned table.
Solution: This operation is not allowed.
Note
This error code is introduced in V4.2.2.
OBE-12991:column is referenced in a multi-column constraint
OceanBase error code: 5792
SQLSTATE: HY000
Cause: You tried to delete a column referenced by a constraint.
Solution: Delete all constraints that reference this column, or specify
CASCADE CONSTRAINTSin the statement.
OBE-12991:column \'%.*s\' is referenced in a multi-column constraint \'%.*s\'
OceanBase error code: 5859
SQLSTATE: HY000
Cause: You tried to delete a column referenced by a constraint.
Solution: Delete all constraints that reference this column, or specify
CASCADE CONSTRAINTSin the statement.
OBE-12992:cannot drop parent key column
OceanBase error code: 5793
SQLSTATE: HY000
Cause: You tried to drop a parent key column.
Solution: Delete all constraints that reference the parent key column, or specify
CASCADE CONSTRAINTSin the statement.
OBE-13000:dimension number is out of range
OceanBase error code: 7290
SQLSTATE: HY000
Cause: The specified dimension is less than 1 or greater than ($2^{64} - 1$).
Solution: Ensure the dimension is between 1 and ($2^{64} - 1$).
Note
This error code is introduced in V4.2.2.
OBE-13011:value is out of range
OceanBase error code: 7435
SQLSTATE: 42000
Cause: The specified value is out of the range allowed by the data type.
Solution: Verify the range allowed by the data type and adjust the table definition.
OBE-13028:Invalid Gtype in the SDO_GEOMETRY object
OceanBase error code: 7291
SQLSTATE: HY000
Cause: The
SDO_GEOMETRYobject contains an invalidSDO_GTYPE.Solution: Verify that the geometry has a valid Gtype.
Note
This error code is introduced in V4.2.2.
OBE-13029:Invalid SRID in the SDO_GEOMETRY object
OceanBase error code: 7292
SQLSTATE: HY000
Cause: The
SDO_GEOMETRYobject contains an invalidSDO_SRID. The specified SRID may be outside the valid SRID range.Solution: Verify that the geometry has a valid SRID.
Note
This error code is introduced in V4.2.2.
OBE-13031:Invalid Gtype in the SDO_GEOMETRY object for point object
OceanBase error code: 7293
SQLSTATE: HY000
Error cause: An invalid
SDO_GTYPEis present in theSDO_GEOMETRYobject, whereSDO Elem Info ArrayorSDO Ordinate Arrayis NULL, but theSDO_GTYPEis not of the POINT type.Solution: Verify that the geometry has a valid Gtype.
Note
This error code is introduced in V4.2.2.
OBE-13032:Invalid NULL SDO_GEOMETRY object
OceanBase error code: 7294
SQLSTATE: HY000
Error cause: The
SDO_POINT_TYPE,SDOElem Info Array, orSDO Ordinate Arrayfield is invalid in theSDO_GEOMETRYobject.Solution: Verify that the geometry has valid fields. To specify a NULL geometry, set the entire
SDO_GEOMETRYto NULL, rather than setting each field to NULL.
Note
This error code is introduced in V4.2.2.
OBE-13033:Invalid data in the SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY object
OceanBase error code: 7295
SQLSTATE: HY000
Error cause: The
SDO_elem_INFO_ARRAYfield in theSDO_GEOMETRYobject contains invalid data.Solution: Verify that the geometry contains valid data.
Note
This error code is introduced in V4.2.2.
OBE-13034:Invalid data in the SDO_ORDINATE_ARRAY in SDO_GEOMETRY object
OceanBase error code: 7296
SQLSTATE: HY000
Error cause: The
SDO_elem_INFO_ARRAYfield in theSDO_GEOMETRYobject contains invalid data.Solution: Verify that the geometry contains valid data.
Note
This error code is introduced in V4.2.2.
OBE-13205:internal error while parsing spatial parameters
OceanBase error code: 7302
SQLSTATE: 42000
Cause: An internal error occurred while parsing spatial parameters.
Solution: Check the settings of all spatial parameters to ensure their values are valid and as expected.
Note
- In V4.3.x, this error code is introduced in V4.3.2.
- In V4.2.x, this error code is introduced in V4.2.4.
OBE-13207:incorrect use of the ['%.*s'] operator
OceanBase error code: 5804
SQLSTATE: HY000
Cause: An error occurred when operating on the specified operator.
Solution: Check the parameters and return types of the specified operator.
OBE-13249:A SPATIAL index may only contain a geometrical type column
- OceanBase error code: 7279
- SQLSTATE: 42000
- Cause: A SPATIAL index can contain only columns of the geometry data type.
Note
- This error code is adjusted from 00600 to 13249 in V4.3.2.
- This error code is introduced in V4.1.0.
OBE-13291:conversion error between the specified unit and standard unit
OceanBase error code: 7434
SQLSTATE: 42000
Cause: An error occurred during unit conversion.
Solution: Check the data types and use valid unit formats.
OBE-13295:geometry objects are in different coordinate systems
OceanBase error code: 7300
SQLSTATE:42000
Error cause: Different coordinate systems were used for the two geometric objects during spatial data operations.
Solution: Ensure that you always use the same coordinate reference system when creating geometric objects.
Note
- In V4.3.x, this error code was introduced in V4.3.2.
- In V4.2.x, this error code was introduced in 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
Error cause: The partition boundary list contains elements of invalid types (that is, they are neither numbers nor empty strings, datetime or interval literals, or
MAXVALUE).Solution: Ensure that all elements in the partition boundary list are of a valid type.
OBE-14019:partition bound element must be one of: string, datetime or intervalliteral, number, or MAXVALUE
OceanBase error code: 5285
SQLSTATE:HY000
Error reason: The partition boundary list contains elements of invalid types (that is, they are neither numbers nor empty strings, datetime or interval literals, or
MAXVALUE).Solution: Ensure that all elements in the partition boundary list are of a valid type.
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 the partitioned table. For example, RANGE/LIST partitioning and HASH/KEY partitioning were used together in subpartitions.
- Solution:
- Modify the partitioning method: If you want to use both RANGE/LIST and HASH/KEY partitioning within a subpartition, consider modifying the partitioning method to use a compatible one. Note that modifying the partitioning method or splitting a partitioned table may affect existing data and applications; proceed with caution.
- Split partitions: If you need to use an incompatible partitioning method, you can consider splitting the partitioned table into multiple tables, each using a different partitioning method.
Note
This error code is introduced in V4.2.0.
OBE-14036:partition bound value too large for column
OceanBase error code: 5354
SQLSTATE: 22001
Error cause: The length of the partition boundary value is greater than the length of the corresponding partitioning column.
Solution: Ensure that the length of the partition's upper bound does not exceed the length of its corresponding partitioning column.
OBE-14037:partition bound of partition '%.*s' is too high
OceanBase error code: 5281
SQLSTATE: HY000
Error cause: The upper bound of a partition is greater than the upper bound of its next partition, which is illegal.
Solution: Ensure that the upper bound of each partition (except for the last one) is lower than the upper bound of its next partition.
OBE-14047:ALTER TABLE|INDEX RENAME may not be combined with other operations
OceanBase error code: 5863
SQLSTATE: HY000
Error cause: The
ALTER TABLEorALTER INDEXstatement attempts to combine theRENAMEoperation with other operations, which is illegal.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
Error cause: Attempting to use an
ALTER TABLEstatement to modify the data type or length of a table partitioning column named in the sameALTER TABLEstatement is illegal.Solution: Avoid modifying the data type or length of a table partitioning column.
OBE-14074:partition bound must collate higher than that of the last partition
OceanBase error code: 5353
SQLSTATE: HY000
Error cause: The partition boundary specified in the
ALTER TABLE ADD PARTITIONstatement is not higher than the boundary of the table's last partition, which is illegal.Solution: Ensure that the partition boundary of the new partition is higher than the boundary of the last partition in 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 you rename a partition of a table, the new partition name duplicates the name of an existing partition or subpartition of the table.
- Solution: Rename the partition or drop the duplicate partition.
Note
This error code is introduced in 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: The tables involved in the
ALTER TABLE EXCHANGE PARTITIONoperation 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 is introduced in V4.3.1.
OBE-14097:column type or size mismatch in ALTER TABLE EXCHANGE PARTITION
OceanBase error code: 4775
SQLSTATE: HY000
Cause: Column types or sizes do not match when executing the
ALTER TABLE EXCHANGE PARTITIONoperation.Solution: Check the columns involved in the exchange to ensure their types and sizes are consistent.
Note
This error code is introduced in V4.3.1.
OBE-14098:index mismatch for tables in ALTER TABLE EXCHANGE PARTITION
OceanBase error code: 4776
SQLSTATE: HY000
Cause: Indexes on the tables do not match when executing the
ALTER TABLE EXCHANGE PARTITIONoperation.Solution: Check and ensure that the indexes on the tables to be exchanged are matched.
Note
This error code is introduced in V4.3.1.
OBE-14100:partition extended table name cannot refer to a remote object
OceanBase error code: 5899
SQLSTATE: HY000
Cause: You tried to use extended partition table syntax to name a remote object, which is incorrect.
Solution: Correct the syntax and try again.
OBE-14109:partition-extended object names may only be used with tables and editioning views
OceanBase error code: 5977
SQLSTATE: HY000
Cause: A partition extended object name was used for an object that is not a table or an edited view.
Solution: Avoid using the partition extended name syntax for objects that are not tables or edited views.
Note
This error code is introduced in V4.0.0.
OBE-14118:CHECK constraint mismatch in ALTER TABLE EXCHANGE PARTITION
OceanBase error code: 4777
SQLSTATE: HY000
Cause: The CHECK constraints on the tables do not match when executing the
ALTER TABLE EXCHANGE PARTITIONoperation.Solution: Ensure that the CHECK constraints on the tables to be exchanged match.
Note
This error code is introduced in V4.3.1.
OBE-14128:FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE PARTITION
OceanBase error code: 4778
SQLSTATE: HY000
Cause: The foreign key constraints on the table do not match during the execution of the
ALTER TABLE EXCHANGE PARTITIONoperation.Solution: Check the involved tables and foreign key constraints to ensure they match.
Note
This error code is introduced in V4.3.1.
OBE-14159:duplicate subpartition name
OceanBase error code: 5867
SQLSTATE: HY000
Cause: The subpartition name is not unique in the table or index.
Solution: Rename the subpartition to ensure that the subpartition name is unique in the table or index.
OBE-14170:cannot specify <(sub)partition-description> clause in CREATE TABLE or CREATE INDEX
OceanBase error code: 5866
SQLSTATE: HY000
Cause: It is illegal to request a default partition description (which can be generated by
PARTITIONS number-of-partitions) while specifying the<(sub)partition-description>clause.Solution: Remove one of the offending clauses.
OBE-14214:VALUES (<value list>) cannot be used for Range subpartitioned tables
OceanBase 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 (<value list>) clause expected
OceanBase error code: 5877
SQLSTATE: HY000
Cause: The
VALUES (value list)clause was not specified for the LIST subpartition.Solution: Specify the
VALUES (``value list)clause.
OBE-14251:Specified subpartition does not exist
OceanBase error code: 5830
SQLSTATE: HY000
Cause: The specified subpartition was not found.
Solution: Use the correct subpartition name and try again.
OBE-14253:table is not partitioned by composite partition method
OceanBase error code: 5875
SQLSTATE: HY000
Cause: One of the following situations occurs:
The table in the subpartition maintenance operation (
ALTER TABLE [EXCHANGE | MODIFY | MOVE | TRUNCATE] SUBPARTITIONorALTER TABLE MODIFY PARTITION [ADD | COALESCE] SUBPARTITION) is not partitioned by the composite partition method.The table in the
MODIFY DEFAULT ATTRIBUTES FOR PARTITIONoperation is partitioned by a method other than the composite partition method.The table in the
ALTER TABLE MODIFY SUBPARTITION [UNUSABLE LOCAL INDEXES | REBUILD UNUSABLE LOCAL INDEXES]statement is not partitioned by the composite partition method.
Solution: Ensure the table is partitioned by the composite partition method.
OBE-14263:New subpartition name %.*s must differ from that of any other partition or subpartition of the object
- OceanBase error code: 5494
- SQLSTATE: HY000
- Error cause: When modifying the name of a subpartition of a table, the new name duplicates the name of an existing partition (either a partition or a subpartition) in the table.
- Solution: Modify the partition name or drop the duplicate partition.
Note
This error code is introduced in V4.2.0.
OBE-14265:data type or length of a
table subpartitioning column may not be changed
OceanBase error code: 5896
SQLSTATE: HY000
Error cause: Attempting to use the
ALTER TABLEstatement to modify the data type or length of a subtable partitioning column named in theALTER TABLEstatement is illegal.Solution: Avoid modifying the data type or length of a table subpartitioning column.
OBE-14291:cannot EXCHANGE a composite partition with a non-partitioned table
OceanBase error code: 4779
SQLSTATE: HY000
Error cause: A composite partition cannot be exchanged with a non-partitioned table.
Solution: Ensure the target table for the exchange has the corresponding partitioning attributes.
Note
This error code is introduced in V4.3.1.
OBE-14300:partitioning key maps to a partition outside maximum permitted number of partitions
OceanBase error code: 6274
SQLSTATE: HY000
Error cause: The number of partitions mapped by the partitioning key of the inserted row exceeds
1048575.Solution: Ensure the number of partitions or subpartitions mapped by the partitioning key is within
1048575.
Note
This error code is introduced in V4.0.0.
OBE-14308:partition bound element must be one of: string, datetime or interval literal, number, or NULL
OceanBase error code: 5355
SQLSTATE: HY000
Cause: The partition boundary list contains elements of invalid types (that is, they are neither numbers nor empty strings, date and time, or interval literals, or
NULL).Solution: Ensure all elements in the partition boundary list are of valid types.
OBE-14310:VALUES LESS THAN or AT clause cannot be used with List partitioned tables
OceanBase error code: 5878
SQLSTATE: HY000
Cause: The
VALUES LESS THANorVALUES LESS ATclause can only be used with RANGE-partitioned tables.Solution: Use the
VALUES (value list)clause with a LIST-partitioned table.
OBE-14311:Expecting VALUES LESS THAN or AT clause
OceanBase error code: 5879
SQLSTATE: HY000
Cause: The
VALUES (value list)clause can only be used with LIST-partitioned tables.Solution: Use the
VALUES LESS THANclause with a RANGE-partitioned table.
OBE-14312:invalid time limit specified
OceanBase error code: 5882
SQLSTATE: HY000
Cause: The input parameter
timeof 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 error code: 5491
- SQLSTATE: 42000
- Cause: The DEFAULT partition must be the last partition specified.
Note
This error code is introduced in V4.1.0.
OBE-14400:inserted partition key does not map to any partition
OceanBase error code: 5284
SQLSTATE: HY000
Cause:
You attempt to insert a record into a
RANGEorCOMPOSITE RANGEobject, but the multiple partition keys in theRANGEorCOMPOSITE RANGEobject exceed the multi-partition boundary list of the last partition.You attempt to insert a record into a
LISTobject, but the partition key in the object does not match any text value specified in a partition.
Solution: Do not insert this key, or add a partition that can accept 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 error code: 5350
SQLSTATE: HY000
Cause: The
UPDATEoperation causes the partition of the row to change.Solution: Enable the table's
enable row movementattribute.
OBE-14501:object is not partitioned
OceanBase error code: 5829
SQLSTATE: HY000
Cause: The table or index is not partitioned. Syntax is invalid.
Solution: Retry the command using the correct syntax.
OBE-14551:cannot perform a DML operation inside a query
OceanBase error code: 9709
SQLSTATE: HY000
Cause: DML operations such as insert, update, delete, or query updates cannot be performed inside a query or under a PDML secondary device.
Solution: Ensure that the problematic DML operation is not executed, or use autonomous transactions to perform DML operations within queries or on PDML secondary stations.
Note
This error code is introduced in V4.0.0.
OBE-14552:cannot perform a DDL commit or rollback inside a query or DML tips
OceanBase error code: 9710
SQLSTATE: HY000
Cause: DDL operations (such as creating tables or views) and transaction control statements (such as commit/rollback) cannot be executed within query or DML statements.
Solution: Ensure that invalid operations are not performed, or use autonomous transactions to execute operations within queries or DML operations.
Note
This error code is introduced in V4.0.0.
OBE-14750:Range partitioned table with INTERVAL clause has more than one column
OceanBase error code: 5997
SQLSTATE: HY000
Cause: An INTERVAL-partitioned table is created with multiple partitioning columns.
Solution: Use a single partitioning column.
Note
This error code is introduced in V4.0.0.
OBE-14751:Invalid data type for partitioning column of an interval partitioned table
OceanBase error code: 5998
SQLSTATE: HY000
Cause: An interval partition is used for a partitioned table whose data type is not number or date/time.
Solution: Use only columns of the number or date/time data type as the partitioning columns for an interval partitioned table.
Note
This error code is introduced in V4.0.0.
OBE-14752:Interval expression is not a constant of the correct type
OceanBase error code: 5999
SQLSTATE: HY000
Cause: A non-constant interval or an interval whose data type does not match that of the partitioning column is used.
Solution: Use only constant expressions for intervals. If the data type of the partitioning column is numeric, the interval must be a numeric constant. If the data type is date/time, the interval must be a constant of the interval type.
Note
This error code is introduced in V4.0.0.
OBE-14753:Interval cannot be zero
OceanBase 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 V4.0.0.
OBE-14757:Table is already a range partitioned table
OceanBase error code: 6000
SQLSTATE: HY000
Error cause: The
SET INTERVAL()clause is used to convert an interval-partitioned table into a range-partitioned table. Using it on a range-partitioned table is illegal.Solution: Use the
SET INTERVAL()clause only on interval-partitioned tables.
Note
This error code is introduced in V4.0.0.
OBE-14758:Last partition in the range section cannot be dropped
OceanBase error code: 4730
SQLSTATE: HY000
Error cause: Dropping the last RANGE partition from an interval-partitioned table.
Solution: Do not drop the last RANGE partition from an interval-partitioned table.
Note
This error code is introduced in V4.0.0.
OBE-14759:SET INTERVAL is not legal on this table
OceanBase error code: 4731
SQLSTATE: HY000
Error cause: The
SET INTERVALclause is specified. TheALTER TABLE SET INTERVALstatement applies only toRANGEpartitioned tables with a single partitioning key column. Furthermore, this partitioned table cannot have aMAXVALUEpartition.Solution: Use
SET INTERVALonly on valid tables.
Note
This error code is introduced in V4.0.0.
OBE-14760:ADD PARTITION is not permitted on Interval partitioned objects
OceanBase error code: 6269
SQLSTATE: HY000
Error cause: Adding a partition to an interval-partitioned object using the
ALTER TABLE ADD PARTITIONstatement.Solution: Do not perform this operation on interval-partitioned objects. Insert a row to create a new partition.
OBE-14761:MAXVALUE partition cannot be specified for Interval partitioned objects
OceanBase error code: 6270
SQLSTATE: HY000
Error cause: A partition or subpartition with a
MAXVALUEupper limit is created on an interval partition/subpartition object.Solution: Do not create a partition or subpartition with a
MAXVALUEupper limit.
OBE-14767: Cannot specify this interval with existing high bounds
OceanBase error code: 6271
SQLSTATE: HY000
Error cause: The specified interval conflicts with the existing upper bound of the last partition. This combination may render future upper bound dates invalid.
Solution: If performing a
CREATE TABLEoperation, try specifying a different upper bound value or a different interval for the last partition. If performing anALTER TABLE SET INTERVALoperation, choose a different interval, or modify the table to change the upper bound of the last partition.
OBE-16000: standby tenant is read only
OceanBase error code: 4688
SQLSTATE: HY000
Error cause: The standby cluster supports only read operations. Write statements such as DDL will trigger this error.
Solution: To modify the standby cluster, you need to perform a role switch to become the primary cluster.
## OBE-19010: Cannot insert XML fragments
- OceanBase error code: 7411
- SQLSTATE: 42000
- Error cause: Attempt to insert an invalid XML document.
- Solution:
- Check the XML data: You can check whether the XML data to be inserted is complete and ensure that the data complies with XML document specifications.
- Use the XMLType data type: You can use the XMLType data type to store XML data in a separate XMLType column.
Note
This error code is introduced in V4.2.0.
OBE-19012: Cannot convert XML fragment to the required datatype
- OceanBase error code: 7406
- SQLSTATE: 42000
- Error cause: Data type mismatch or invalidity when converting an XML fragment to the required data type.
- Solution: Check whether the data type or XML data is correct.
Note
This error code is introduced in V4.2.0.
OBE-19025: EXTRACTVALUE cannot extract values of multiple nodes
- OceanBase 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 V4.2.0.
OBE-19026: EXTRACTVALUE can only retrieve value of leaf nodetoo small
- OceanBase error code: 7410
- SQLSTATE: 42000
- Cause: When using the EXTRACTVALUE function, you attempt to extract a value from a non-leaf node.
- Solution: Check whether the XPath expression is correct and ensure it points to a leaf node.
Note
This error code is introduced in V4.2.0.
OBE-19044: character length specified for XMLSerialize is too small
- OceanBase error code: 7408
- SQLSTATE: 42000
- Cause: The specified character length is too small when using the XMLSerialize function.
- Solution: Check the character length or data size to ensure it is sufficient to accommodate all data.
Note
This error code is introduced in V4.2.0.
OBE-19102: XQuery string literal expected
OceanBase error code: 7423
SQLSTATE: 42000
Cause: A string literal containing an XQuery expression is missing.
Solution: Specify the XQuery expression as a string literal.
Note
This error code is introduced in V4.2.2.
OBE-19110:unsupported XQuery expression
OceanBase error code: 7428
SQLSTATE: 42000
Cause: The specified expression in the XQuery is not supported.
Solution: Rewrite the XQuery using a supported expression.
Note
This error code is introduced in V4.2.2.
OBE-19114:XPST0003 - error during parsing the XQuery expression : %.*s
OceanBase error code: 7422
SQLSTATE: 42000
Cause: An error occurred while parsing the XQuery expression.
Solution: Check the detailed error message for possible causes.
Note
This error code is introduced in V4.2.2.
OBE-19118:XQST0066 - duplicate default namespace definition - %s
OceanBase error code: 7420
SQLSTATE: 42000
Cause: Multiple default namespace declarations use the given namespace URI.
Solution: Remove duplicate default namespace definitions.
Note
This error code is introduced in V4.2.2.
OBE-19208:parameter %d of function XMLELEMENT must be aliased
- OceanBase error code: 7413
- SQLSTATE: 42000
- Cause: The nth attribute parameter of the XMLELEMENT() function has no alias.
- Solution:
- Check the syntax of the attributes in the XMLELEMENT() function to ensure it is correct and valid.
- Ensure that an alias is specified for the attribute parameter in the XMLELEMENT() function.
Note
This error code is introduced in V4.2.0.
OBE-19224:XPTY0004 - XQuery static type mismatch: expected - node()* got -
OceanBase error code: 7425
SQLSTATE: 42000
Cause: The expression cannot be used because its static type does not match the context in which it is used.
Solution: Fix the expression to have the desired type or add appropriate conversion functions to the expression.
Note
This error code is introduced in V4.2.2.
OBE-19253:XPST0033 - too many declarations for namespace prefix %.*s
OceanBase error code: 7424
SQLSTATE: 42000
Cause: The query preamble contains multiple declarations for the same namespace prefix.
Solution: Remove duplicate definitions of the namespace prefix.
Note
This error code is introduced in V4.2.2.
OBE-19279:XPTY0004 - XQuery dynamic type mismatch: expected singleton sequence - got multi-item sequence
OceanBase error code: 7421
SQLSTATE: 42000
Error cause: The input XQuery sequence contains more than one item.
Solution: Modify the XQuery expression to return a sequence of a single item.
Note
This error code is introduced in V4.2.2.
OBE-19276:XPST0005 - XPath step specifies an invalid element/attribute name: %.*s
OceanBase error code: 7426
SQLSTATE:42000
Error cause: The XPATH step specifies an invalid element or attribute name that 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 V4.2.2.
OBE-19277:XPST0005 - XPath step specifies an item type matching no node: %.*s
OceanBase error code: 7427
SQLSTATE:42000
Error cause: The item type specified in the XPath step does not match any node based on the input XML schema or structure.
Solution: Modify it to a type node that matches.
Note
This error code is introduced in V4.2.2.
