ORA-10000 to ORA-19999

ORA-12000: a materialized view log already exists on table %s

• Error code in OceanBase Database: 9756

• SQLSTATE: HY000

• Cause: You are attempting to create a materialized view log on a table that already has a materialized view log. Each primary table can have only one materialized view log.

• Solution: All materialized views on a table can use the materialized view log of the table. To modify the existing materialized view log, execute the DROP MATERIALIZED VIEW LOG statement to drop the log and create a new one.

ORA-12003: materialized view %s.%s does not exist

• Error code in OceanBase Database: 9757

• SQLSTATE: HY000

• Cause: No materialized view object with the specified owner and name is found.

• Solution: Try again.

ORA-12006: materialized view %s.%s already exists

• Error code in OceanBase Database: 9758

• SQLSTATE: HY000

• Cause: The materialized view already exists.

• Solution: Drop the existing materialized view or create a materialized view with another name.

ORA-12034: materialized view log on %s.%s younger than last refresh

• Error code in OceanBase Database: 9759

• SQLSTATE: HY000

• Cause: The materialized view log is later than the change recorded when the materialized view is last refreshed.

• Solution: Perform a complete refresh before performing a fast refresh.

ORA-12052: cannot fast refresh materialized view %s.%s

• Error code in OceanBase Database: 9760

• SQLSTATE: HY000

• Cause:

  • The ROWIDs of some tables are absent in the definition, or no UNIQUE constraint is defined on the to-be-joined columns in the right-side table of an outer join.
  • The table object on which the materialized view depends changes.
  • The materialized view log does not exist.

• Solution:

  • Specify the FORCE or COMPLETE option.
  • Check and repair the schema of the base table to make sure that the definition of the materialized view is still valid, and perform a complete refresh for the materialized view.
  • Re-create the materialized view log and perform a complete refresh for the materialized view so that the view contains the complete latest data.

ORA-12401: invalid label string

• Error code in OceanBase Database: 5696

• SQLSTATE: HY000

• Cause: The strategy cannot convert the label string into a valid internal label.

• Solution: Correct the syntax of the label string.

ORA-12416: policy string not found

• Error code in OceanBase Database: 5695

• SQLSTATE: HY000

• Cause: The specified strategy does not exist in the database.

• Solution: Enter a correct strategy name or create a strategy.

ORA-12432: LBAC error: %s

• Error code in OceanBase Database: 5700

• SQLSTATE: HY000

• Cause: Label-based access control (LBAC) is performed.

• Solution: Correct the problem identified in the error message.

ORA-12444: policy already applied to table

• Error code in OceanBase Database: 5790

• SQLSTATE: HY000

• Cause: You are applying a strategy to a table that is already under strategy protection.

• Solution: If you need to modify the table options, predicate, or label function, you must first remove the strategy from the table and then reapply it.

ORA-12447: policy role already exists for policy string

• Error code in OceanBase Database: 5701

• SQLSTATE: HY000

• Cause: A strategy with the specified name already exists.

• Solution: Change the strategy name or delete the existing strategy.

ORA-12461: undefined level string for policy string

• Error code in OceanBase Database: 5698

• SQLSTATE: HY000

• Cause: The specified level is not defined for the strategy.

• Solution: Specify a level identifier value for the strategy.

ORA-12462: undefined compartment string for policy string

• Error code in OceanBase Database: 5697

• SQLSTATE: HY000

• Cause: The specified component is not defined for the strategy.

• Solution: Specify a component identifier value for the strategy.

ORA-12463: undefined group string for policy string

• Error code in OceanBase Database: 5699

• SQLSTATE: HY000

• Cause: The specified group is not defined for the strategy.

• Solution: Specify a group identifier value for the strategy.

ORA-12470: NULL or invalid user label: %s

• Error code in OceanBase Database: 5702

• SQLSTATE: HY000

• Cause: The entered user label is NULL or is beyond the authorization for the user.

• Solution: Enter an authorized label for the user.

ORA-12702: invalid NLS parameter string used in SQL function

• Error code in OceanBase Database: 5604

• SQLSTATE: HY000

• Cause: An unknown argument name or an invalid value is specified in the NLS argument string.

ORA-12704: COLLATION '%.*s' is not valid for CHARACTER SET '%.*s'

• Error code in OceanBase Database: 5144

• SQLSTATE: 42000

• Cause:

  • Different character sets are used for the string operands (excluding nlsparams) of the operator or built-in function.

  • The nlsparams operand is not contained in the character set of the database.

  • A character set other than the character set of the database is used for the string data passed to the built-in function, but the built-in function does not support the character set in use.

  • The second argument of CHR() or CSCONVERT() is not CHAR_CS or NCHAR_CS.

  • The character set of the string expression in the VALUES clause of the INSERT statement or the SET clause of the UPDATE statement is different from the character set used by the column to be inserted.

  • In the table creation statement, the character set used for the values in the DEFAULT clause is different from the character set declared for the column.

  • An argument of the PL function does not meet the character set requirements of the argument.

ORA-12704: character set mismatch

• Error code in OceanBase Database: 5808

• SQLSTATE: HY000

• Cause:

  • Different character sets are used for the string operands (excluding nlsparams) of the operator or built-in function.

  • The nlsparams operand is not contained in the character set of the database.

  • A character set other than the character set of the database is used for the string data passed to the built-in function, but the built-in function does not support the character set in use.

  • The second argument of CHR() or CSCONVERT() is not CHAR_CS or NCHAR_CS.

  • The character set of the string expression in the VALUES clause of the INSERT statement or the SET clause of the UPDATE statement is different from the character set used by the column to be inserted.

  • In the table creation statement, the character set used for the values in the DEFAULT clause is different from the character set declared for the column.

  • An argument of the PL function does not meet the character set requirements of the argument.

ORA-12705: Cannot access NLS data files or invalid environment specified

• Error code in OceanBase Database: 5943

• SQLSTATE: HY000

• Cause:

  • An invalid NLS parameter or value is specified in the ALTER SESSION statement.

  • The name of environment variable NLS_LANG, ORA_NLSxx, or ORACLE_HOME is incorrectly spelled, and therefore the NLS data file cannot be found.

• Solution:

  • Check the syntax of the ALTER SESSION statement and the NLS parameter, correct the syntax errors, and try this statement again.

  • Make sure that the name of the environment variable is correctly spelled.

ORA-12725: unmatched parentheses in regular expression

• Error code in OceanBase Database: 5813

• SQLSTATE: HY000

• Cause: Parentheses (()) in the regular expression do not appear in pairs.

• Solution: Make sure that the parentheses are symmetric.

ORA-12726: unmatched bracket in regular expression

• Error code in OceanBase Database: 5812

• SQLSTATE: HY000

• Cause: Square brackets ([]) in the regular expression do not appear in pairs.

• Solution: Make sure that the parentheses are symmetric.

ORA-12727: invalid back reference in regular expression

• Error code in OceanBase Database: 5814

• SQLSTATE: HY000

• Cause: The subexpression contains a back reference.

• Solution: Make sure that the referenced subexpression is valid.

ORA-12728: invalid range in regular expression

• Error code in OceanBase Database: 5815

• SQLSTATE: HY000

• Cause: An invalid range is found in the regular expression.

• Solution: Make sure that a valid range is used.

ORA-12729: invalid character class in regular expression

• Error code in OceanBase Database: 5816

• SQLSTATE: HY000

• Cause: An unknown character class is found in the regular expression.

• Solution: Use a valid character class.

ORA-12731: invalid collation class in regular expression

• Error code in OceanBase Database: 5817

• SQLSTATE: HY000

• Cause: An unknown collation class is found in the regular expression.

• Solution: Use a valid collation class.

ORA-12801: error signaled in parallel query server

• Error code in OceanBase Database: 5736

• SQLSTATE: HY000

• Cause: When Parallel eXecution (PX) needs to be terminated, this error code is broadcasted to all execution nodes to terminate the current execution.

• Solution: Find the cause of interruption in the execution log or contact OceanBase Technical Support for troubleshooting.

ORA-12827: insufficient parallel query worker available

• Error code in OceanBase Database: 5345

• SQLSTATE: HY000

• Cause: The parallel_servers_target parameter is specified, but the number of obtained slaves is less than the specified lower limit or reaches the upper limit.

• Solution: Increase the value of parallel_servers_target and execute the query again, or wait for slaves to be released after some ongoing queries are completed.

ORA-12899: value too large for column '%.*s' at row %ld

• Error code in OceanBase Database: 5167

• SQLSTATE: 22001

• Cause: The column value to be inserted or updated exceeds the width limit.

• Solution: Check the correctness of the SQL statement. Check the data types of the source and destination columns. Increase the width of the destination column or use a subset, namely, a substring, of the source column.

ORA-12984: cannot drop partitioning column '%.*s'

• Error code in OceanBase Database: 5502

• SQLSTATE: HY000

• Cause: You are attempting to drop the partitioning key from a partitioned table.

• Solution: Do not perform this operation.

ORA-12991: column is referenced in a multi-column constraint

• Error code in OceanBase Database: 5792

• SQLSTATE: HY000

• Cause: You are attempting to delete a column referenced by some constraints.

• Solution: Delete all constraints that reference the column or specify CASCADE CONSTRAINTS in the statement.

ORA-12991: column \'%.*s\' is referenced in a multi-column constraint \'%.*s\'

• Error code in OceanBase Database: 5859

• SQLSTATE: HY000

• Cause: You are attempting to delete a column referenced by some constraints.

• Solution: Delete all constraints that reference the column or specify CASCADE CONSTRAINTS in the statement.

ORA-12992: cannot drop parent key column

• Error code in OceanBase Database: 5793

• SQLSTATE: HY000

• Cause: You are attempting to drop a parent key column.

• Solution: Delete all constraints that reference this parent key column, or specify CASCADE CONSTRAINTS in the statement.

ORA-13000: dimension number is out of range

• Error code in OceanBase Database: 7290

• SQLSTATE: HY000

• Cause: The specified dimension is less than 1 or greater than ($2^{64} - 1$).

• Solution: Make sure that the dimension value ranges from 1 to ($2^{64} - 1$).

ORA-13028: Invalid Gtype in the SDO_GEOMETRY object

• Error code in OceanBase Database: 7291

• SQLSTATE: HY000

• Cause: The SDO_GTYPE value of the SDO_GEOMETRY object is invalid.

• Solution: Make sure that the Gtype of the geometry is valid.

ORA-13029: Invalid SRID in the SDO_GEOMETRY object

• Error code in OceanBase Database: 7292

• SQLSTATE: HY000

• Cause: The SDO_SRID value of the SDO_GEOMETRY object is invalid. The specified SRID may be beyond the valid SRID range.

• Solution: Make sure that the SRID of the geometry is valid.

ORA-13031: Invalid Gtype in the SDO_GEOMETRY object for point object

• Error code in OceanBase Database: 7293

• SQLSTATE: HY000

• Cause: The SDO_GTYPE value of the SDO_GEOMETRY object is invalid. The value of SDO_ELEM_INFO_ARRAY or SDO_ORDINATE_ARRAY is NULL but the type specified by SDO_GTYPE is not a POINT type.

• Solution: Make sure that the Gtype of the geometry is valid.

ORA-13032: Invalid NULL SDO_GEOMETRY object

• Error code in OceanBase Database: 7294

• SQLSTATE: HY000

• Cause: The SDO_POINT_TYPE, SDO_ELEM_INFO_ARRAY, or SDO_ORDINATE_ARRAY value of the SDO_GEOMETRY object is invalid.

• Solution: Make sure that the field values of the geometry are valid. To specify a NULL geometry, set SDO_GEOMETRY to NULL instead of setting each field to NULL.

ORA-13033: Invalid data in the SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY object

• Error code in OceanBase Database: 7295

• SQLSTATE: HY000

• Cause: Invalid data exists in the SDO_ELEM_INFO_ARRAY field of the SDO_GEOMETRY object.

• Solution: Make sure that the data of the geometry is valid.

ORA-13034: Invalid data in the SDO_ORDINATE_ARRAY in SDO_GEOMETRY object

• Error code in OceanBase Database: 7296

• SQLSTATE: HY000

• Cause: Invalid data exists in the SDO_ELEM_INFO_ARRAY field of the SDO_GEOMETRY object.

• Solution: Make sure that the data of the geometry is valid.

ORA-13207: incorrect use of the ['%.*s'] operator

• Error code in OceanBase Database: 5804

• SQLSTATE: HY000

• Cause: An error occurred while using the specified operator.

• Solution: Check the parameters and return type of the operator.

ORA-14019: partition bound element must be one of: string, datetime or interval literal, number, or MAXVALUE

• Error code in OceanBase Database: 5275

• SQLSTATE: HY000

• Cause: The partition bound list contains elements of invalid types. To be specific, the elements are not digits, null strings, datetime, interval literals, or MAXVALUE.

• Solution: Make sure that all elements in the partition bound list are of valid types.

ORA-14019: partition bound element must be one of: string, datetime or interval literal, number, or MAXVALUE

• Error code in OceanBase Database: 5285

• SQLSTATE: HY000

• Cause: The partition bound list contains elements of invalid types. To be specific, the elements are not digits, null strings, datetime, interval literals, or MAXVALUE.

• Solution: Make sure that all elements in the partition bound list are of valid types.

ORA-14020: this physical attribute may not be specified for a table partition

• Error code in OceanBase Database: 4398
• SQLSTATE: HY000
• Cause: You have specified an incompatible partitioning method when you create the partitioned table. For example, you may have specified RANGE-LIST partitioning and HASH-KEY partitioning.
• Solution:
  • Change the partitioning method. If you want to use both RANGE-LIST partitioning and HASH-KEY partitioning, you can use a compatible partitioning method. Note that changing the partitioning method or partitioning a partitioned table may affect the existing data and applications. Proceed with caution.
  • Separate the partitions: If you need to use incompatible partitioning methods, you can split the partitioned table into multiple tables and use different partitioning methods for the tables.

ORA-14036: partition bound value too large for column

• Error code in OceanBase Database: 5354

• SQLSTATE: 22001

• Cause: The length of a partition bound value exceeds that of the corresponding partitioning column.

• Solution: Make sure that the upper bounds of partitions do not exceed the lengths of the corresponding partitioning columns.

ORA-14037: partition bound of partition '%.*s' is too high

• Error code in OceanBase Database: 5281

• SQLSTATE: HY000

• Cause: The upper bound of a partition is greater than that of the next partition.

• Solution: Make sure that the upper bound of each partition, except for the last partition, is less than that of the next partition.

ORA-14047: ALTER TABLE|INDEX RENAME may not be combined with other operations

• Error code in OceanBase Database: 5863

• SQLSTATE: HY000

• Cause: The ALTER TABLE or ALTER INDEX statement attempted to combine the RENAME operation with other operations, which is not allowed.

• Solution: Make sure that the ALTER TABLE or ALTER INDEX statement contains only the RENAME operation.

ORA-14060: data type or length of a table partitioning column may not be changed

• Error code in OceanBase Database: 5895

• SQLSTATE: HY000

• Cause: The ALTER TABLE statement is used to modify the data type or length of a partitioning column in a table named by using the ALTER TABLE statement.

• Solution: Do not modify the data type or length of partitioning columns in a table.

ORA-14074: partition bound must collate higher than that of the last partition

• Error code in OceanBase Database: 5353

• SQLSTATE: HY000

• Cause: The partition bound specified in the ALTER TABLE ADD PARTITION statement is not higher than the bound of the last partition in the table.

• Solution: Make sure that the bound of the partition to be added is higher than that of the last partition in the table.

ORA-14082: New partition name %.*s must differ from that of any other partition or subpartition of the object.

• Error code in OceanBase Database: 5493
• SQLSTATE: HY000
• Cause: When you modify the name of a partition of a table, the new name is already taken by an existing partition or subpartition.
• Solution: Use another name or delete the existing partition or subpartition with the name.

ORA-14100: partition extended table name cannot refer to a remote object

• Error code in OceanBase Database: 5899

• SQLSTATE: HY000

• Cause: You are attempting to rename a remote object by using a partition-extended table name syntax.

• Solution: Correct the expression and retry.

ORA-14109: partition-extended object names may only be used with tables and editioning views

• Error code in OceanBase Database: 5977

• SQLSTATE: HY000

• Cause: You are attempting to use a partition-extended object name for an object which was not a table or an editioning view.

• Solution: Do not use the partition-extended name syntax for objects other than tables or editioning views.

ORA-14159: duplicate subpartition name

• Error code in OceanBase Database: 5867

• SQLSTATE: HY000

• Cause: The name of a subpartition of the table or index is not unique.

• Solution: Rename the subpartition to make sure that its name is unique among subpartitions of the table or index.

ORA-14170: cannot specify <(sub)partition-description> clause in CREATE TABLE or CREATE INDEX

• Error code in OceanBase Database: 5866

• SQLSTATE: HY000

• Cause: The request generates a default partition description (possibly through PARTITIONS number-of-partitions) and specifies the <(sub)partition-description> clause, which is not allowed.

• Solution: Delete one of the clauses.

ORA-14214: VALUES (<value list>) cannot be used for Range subpartitioned tables

• Error code in OceanBase Database: 5876

• SQLSTATE: HY000

• Cause: The VALUES (value list) clause is used for RANGE-subpartitioned tables.

• Solution: Use the VALUES LESS THAN or AT clause for RANGE-subpartitioned tables.

ORA-14217: VALUES (<value list>) clause expected

• Error code in OceanBase Database: 5877

• SQLSTATE: HY000

• Cause: The VALUES (value list) clause is not specified for a LIST-subpartitioned table.

• Solution: Specify the VALUES (value list) clause.

ORA-14251: Specified subpartition does not exist

• Error code in OceanBase Database: 5830

• SQLSTATE: HY000

• Cause: No subpartition is found for the object.

• Solution: Use the valid subpartition name and try again.

ORA-14253: table is not partitioned by composite partition method

• Error code in OceanBase Database: 5875

• SQLSTATE: HY000

• Cause: The possible causes are as follows:

  • The table in a subpartition maintenance operation, such as ALTER TABLE [EXCHANGE | MODIFY | MOVE | TRUNCATE] SUBPARTITION or ALTER TABLE MODIFY PARTITION [ADD | COALESCE] SUBPARTITION, is not partitioned by using the composite partitioning method.

  • The table in the MODIFY DEFAULT ATTRIBUTES FOR PARTITION operation is partitioned by using a method other than composite partitioning.

  • The table in the ALTER TABLE MODIFY SUBPARTITION [UNUSABLE LOCAL INDEXES | REBUILD UNUSABLE LOCAL INDEXES] statement is not partitioned by using the composite partitioning method.

• Solution: Make sure that the table is partitioned by using the composite partitioning method.

ORA-14263: New subpartition name %.*s must differ from that of any other partition or subpartition of the object.

• Error code in OceanBase Database: 5494
• SQLSTATE: HY000
• Cause: When you modify the name of a subpartition of a table, the new name is already taken by an existing partition or subpartition.
• Solution: Use another name or delete the existing partition or subpartition with the name.

ORA-14265: data type or length of a table subpartitioning column may not be changed

• Error code in OceanBase Database: 5896

• SQLSTATE: HY000

• Cause: The ALTER TABLE statement is used to modify the data type or length of a column used to partition a table named by using the ALTER TABLE statement.

• Solution: Do not modify the data type or length of table subpartitioning columns.

ORA-14300: partitioning key maps to a partition outside maximum permitted number of partitions

• Error code in OceanBase Database: 6274

• SQLSTATE: HY000

• Cause: The inserted row had a partitioning key that maps to a partition number greater than 1,048,575.

• Solution: Make sure that the partitioning key maps to no more than 1,048,575 partitions or subpartitions.

ORA-14308: partition bound element must be one of: string, datetime or interval literal, number, or NULL

• Error code in OceanBase Database: 5355

• SQLSTATE: HY000

• Cause: The partition bound list contains elements of invalid types, which are not digits, null strings, datetime, interval literals, or NULL.

• Solution: Make sure that all elements in the partition bound list are of valid types.

ORA-14310: VALUES LESS THAN or AT clause cannot be used with List partitioned tables

• Error code in OceanBase Database: 5878

• SQLSTATE: HY000

• Cause: The VALUES LESS THAN or VALUES LESS AT clause can be used only for RANGE-partitioned tables.

• Solution: Use the VALUES (value list) clause for LIST-partitioned tables.

ORA-14311: Expecting VALUES LESS THAN or AT clause

• Error code in OceanBase Database: 5879

• SQLSTATE: HY000

• Cause: The VALUES (value list) clause can be used only for LIST-partitioned tables.

• Solution: Use the VALUES LESS THAN clause for RANGE-partitioned tables.

ORA-14312: invalid time limit specified

• Error code in OceanBase Database: 5882

• SQLSTATE: HY000

• Cause: A non-positive value is specified for the time parameter of the dbms_lock.sleep(time) package.

• Solution: Specify a positive value.

ORA-14318: DEFAULT partition must be last partition specified

• Error code in OceanBase Database: 5491
• SQLSTATE: 42000
• Cause: The DEFAULT partition must be the last specified partition.

ORA-14400: inserted partition key does not map to any partition

• Error code in OceanBase Database: 5284

• SQLSTATE: HY000

• Cause:

  • You are attempting to insert a record to a RANGE or COMPOSITE RANGE object, but the concatenated partitioning key included in the RANGE or COMPOSITE RANGE object is beyond the concatenated partition bound list of the last partition.

  • You are attempting to insert a record to a LIST object, but the partitioning key included in this object does not match the specified literal value of any partition.

• Solution: Do not insert this key, add a partition that accepts this key, or add a value matching this key to the partition configuration.

ORA-14402: updating partition key column would cause a partition change

• Error code in OceanBase Database: 5350

• SQLSTATE: HY000

• Cause: The UPDATE operation caused a change of the partition to which the row belongs.

• Solution: Enable the enable row movement attribute for the table.

ORA-14501: object is not partitioned

• Error code in OceanBase Database: 5829

• SQLSTATE: HY000

• Cause: The table or index is not partitioned. The syntax is invalid.

• Solution: Retry the command with the valid syntax.

ORA-14551: cannot perform a DML operation inside a query

• Error code in OceanBase Database: 9709

• SQLSTATE: HY000

• Cause: A DML operation like INSERT, UPDATE, DELETE, or SELECT-for-UPDATE cannot be performed inside a query or under a PDML slave.

• Solution: Make sure that the offending DML operation is not performed, or use an autonomous transaction to perform the DML operation within the query or PDML slave.

ORA-14552: cannot perform a DDL commit or rollback inside a query or DML tips

• Error code in OceanBase Database: 9710

• SQLSTATE: HY000

• Cause: DDL operations (such as creating tables or views) and transaction control statements (such as commit and rollback) cannot be performed inside a query or a DML statement.

• Solution: Make sure that the offending operation is not performed, or use autonomous transactions to perform the operation within the query or DML statement.

ORA-14750: Range partitioned table with INTERVAL clause has more than one column

• Error code in OceanBase Database: 5997

• SQLSTATE: HY000

• Cause: You are attempting to create an interval-partitioned table with more than one partitioning columns.

• Solution: Use a single partitioning column.

ORA-14751: Invalid data type for partitioning column of an interval partitioned table

• Error code in OceanBase Database: 5998

• SQLSTATE: HY000

• Cause: You are attempting to use interval partitioning on a table partitioned on a column whose data type is not number or date/time.

• Solution: 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

• Error code in OceanBase Database: 5999

• SQLSTATE: HY000

• Cause: You are attempting to use either a nonconstant interval or an interval whose data type does not correspond to the partitioning column.

• Solution: Use only constant expressions for the interval. 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.

ORA-14753: Interval cannot be zero

• Error code in OceanBase Database: 6273

• SQLSTATE: HY000

• Cause: The interval mapped to zero.

• Solution: Use a non-zero interval.

ORA-14757: Table is already a range partitioned table

• Error code in OceanBase Database: 6000

• SQLSTATE: HY000

• Cause: SET INTERVAL() is used to convert an interval-partitioned table to a RANGE-partitioned table. You are not allowed to use SET INTERVAL() on a RANGE-partitioned table.

• Solution: Use SET INTERVAL() only on an interval-partitioned table.

ORA-14758: Last partition in the range section cannot be dropped

• Error code in OceanBase Database: 4730

• SQLSTATE: HY000

• Cause: You are attempting to drop the last RANGE partition of an interval-partitioned table.

• Solution: Do not drop the last RANGE partition of an interval-partitioned table.

ORA-14759: SET INTERVAL is not legal on this table

• Error code in OceanBase Database: 4731

• SQLSTATE: HY000

• Cause: The SET INTERVAL clause was specified. ALTER TABLE SET INTERVAL is allowed only on a RANGE-partitioned table with a single partitioning column. Additionally, this table cannot have a MAXVALUE partition.

• Solution: Use SET INTERVAL only on a valid table.

ORA-14760: ADD PARTITION is not permitted on Interval partitioned objects

• Error code in OceanBase Database: 6269

• SQLSTATE: HY000

• Cause: You are attempting to execute the ALTER TABLE ADD PARTITION statement on an interval-partitioned object to add a partition.

• Solution: Do not perform the operation on an interval-partitioned object. To add a partition, insert a row into the object.

ORA-14761: MAXVALUE partition cannot be specified for Interval partitioned objects

• Error code in OceanBase Database: 6270

• SQLSTATE: HY000

• Cause: You are attempting to create a partition or subpartition with a MAXVALUE high bound on an interval-partitioned or interval-subpartitioned object.

• Solution: Do not create a partition or subpartition with a MAXVALUE high bound.

ORA-14767: Cannot specify this interval with existing high bounds

• Error code in OceanBase Database: 6271

• SQLSTATE: HY000

• 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

• Solution: If you are executing CREATE TABLE, try to specify a different high bound value for the last partition or specify a different interval. If you are executing ALTER TABLE SET INTERVAL, choose either a different interval, or modify the table to change the high bound for the last partition.

ORA-16000: standby tenant is read only

• Error code in OceanBase Database: 4688

• SQLSTATE: HY000

• Cause: The standby cluster supports only read operations. This error is returned when you execute write statements, such as DDL statements.

• Solution: Switch the standby cluster to be the primary cluster.

ORA-19010: Cannot insert XML fragments

• Error code in OceanBase Database: 7411
• SQLSTATE: 42000
• Cause: The XML file to be inserted is invalid.
• Solution:
  1. Make sure that the XML data to be inserted is complete and conforms to the XML specifications.
  2. Use the XMLType data type, so that you can store the XML data in a separate XMLType column.

ORA-19012: Cannot convert XML fragment to the required datatype

• Error code in OceanBase Database: 7406
• SQLSTATE: 42000
• Cause: The XML fragment cannot be converted to the required data type.
• Solution: Make sure that the data type and XML data are correct.

ORA-19025: EXTRACTVALUE cannot extract values of multiple nodes

• Error code in OceanBase Database: 7405
• SQLSTATE: 42000
• Cause: The EXTRACTVALUE function cannot extract values from multiple nodes.
• Solution: Use other functions or redesign the XPath expression for the query.

ORA-19026: EXTRACTVALUE can only retrieve value of leaf nodetoo small.

• Error code in OceanBase Database: 7410
• SQLSTATE: 42000
• Cause: The EXTRACTVALUE function tried to extract a value from a non-leaf node.
• Solution: Make sure that the specified XPath expression is correct and points to a leaf node.

ORA-19044: character length specified for XMLSerialize is too small.

• Error code in OceanBase Database: 7408
• SQLSTATE: 42000
• Cause: The character length specified for the XMLSerialize function is too short.
• Solution: Check the specified character length and data size, and make sure that all data can be accommodated.

ORA-19102: XQuery string literal expected

• Error code in OceanBase Database: 7423

• SQLSTATE: 42000

• Cause: A string literal that contains the XQuery expression is missing.

• Solution: Specify the XQuery expression as a string literal.

ORA-19110: unsupported XQuery expression

• Error code in OceanBase Database: 7428

• SQLSTATE: 42000

• Cause: The expression specified in the XQuery is not supported.

• Solution: Rewrite the XQuery by using a supported expression.

ORA-19114: XPST0003 - error during parsing the XQuery expression : %.*s

• Error code in OceanBase Database: 7422

• SQLSTATE: 42000

• Cause: An error occurs while parsing the XQuery expression.

• Solution: Check the error message for the possible causes.

ORA-19118: XQST0066 - duplicate default namespace definition - %s.

• Error code in OceanBase Database: 7420

• SQLSTATE: 42000

• Cause: The given namespace URI is used in multiple default namespace declarations.

• Solution: Delete the duplicate default namespace definitions.

ORA-19208: parameter %d of function XMLELEMENT must be aliased

• Error code in OceanBase Database: 7413
• SQLSTATE: 42000
• Cause: The Nth parameter of the XMLELEMENT () function does not have an alias.
• Solution:
  1. Make sure that the attribute syntax of the XMLELEMENT() function is correct and valid.
  2. Make sure that aliases are specified for attribute parameters of the XMLELEMENT () function.

ORA-19224: XPTY0004 - XQuery static type mismatch: expected - node()* got -

• Error code in OceanBase Database: 7425

• SQLSTATE: 42000

• Cause: This expression cannot be used because its static type is unsuitable for the context where it is used.

• Solution: Change the type or add an appropriate conversion function in the expression.

ORA-19253: XPST0033 - too many declarations for namespace prefix %.*s

• Error code in OceanBase Database: 7424

• SQLSTATE: 42000

• Cause: The query prelog contains multiple declarations for the same namespace prefix.

• Solution: Delete the duplicate namespace prefix definitions.

ORA-19279: XPTY0004 - XQuery dynamic type mismatch: expected singleton sequence - got multi-item sequence

• Error code in OceanBase Database: 7421

• SQLSTATE: 42000

• Cause: The XQuery sequence passed in contains multiple items.

• Solution: Modify the XQuery expression so that only one item sequence is returned.

ORA-19276: XPST0005 - XPath step specifies an invalid element/attribute name: %.*s

• Error code in OceanBase Database: 7426

• SQLSTATE: 42000

• Cause: An invalid element or attribute name is specified in the XPath step. The element or attribute name does not match any node according to the input XML schema or structure.

• Solution: Correct the element or attribute name.

ORA-19277: XPST0005 - XPath step specifies an item type matching no node: %.*s

• Error code in OceanBase Database: 7427

• SQLSTATE: 42000

• Cause: The item type specified in the XPath step does not match any node according to the input XML schema or structure.

• Solution: Correct the item type definition.