OBE-00000 ~ OBE-00999

OBE-00000: PX DOP downgrade from %ld to %ld

• OceanBase error code: 5780

• SQLSTATE: HY000

• Cause: Normal exit.

OBE-00000: parallel_max_servers downgrade due to insufficent cpu resource from %ld to %ld. deprecated

• OceanBase error code: 5781

• SQLSTATE: HY000

• Cause: Normal exit.

  Note

  This error code is no longer used in the current version.

OBE-00001:unique constraint \'%s\' for key \'%.*s\' violated

• OceanBase error code: 5024

• SQLSTATE: 23000

• Cause: The UPDATE or INSERT statement attempts to insert a duplicate key.

• Solution: Remove the UNIQUE constraint or do not insert this key.

Related issue cases:

• Error OBE-00001 when inserting data with duplicate input

OBE-00001:unique constraint (%.*s) violated

• OceanBase error code: 5595

• SQLSTATE: 23000

• Cause: The UPDATE or INSERT statement attempts to insert a duplicate key.

• Solution: Remove the UNIQUE constraint or do not insert this key.

OBE-00001:unique constraint violated, column '%.*s' with value '%.*s' in %s

• OceanBase error code: 5334

• SQLSTATE: HY000

• Error cause: The UPDATE or INSERT statement attempts to insert a duplicate key.

• Solution: Remove the UNIQUE constraint or do not insert this key.

OBE-00001:unique constraint (%.*s) violated

• OceanBase error code: 5562

• SQLSTATE: HY000

• Error cause: The UPDATE or INSERT statement attempts to insert a duplicate key.

• Solution: Remove the UNIQUE constraint or do not insert this key.

OBE-00028:your session has been killed

• OceanBase error code: 5125

• SQLSTATE: HY000

• Error cause: The session using the database link (DBLINK) has been terminated.

• Solution: Check the network connection and the status of the remote database, then re-establish the database link session.

OBE-00036:maximum number of recursive SQL levels (%ld) exceeded

• OceanBase error code: 9697

• SQLSTATE: HY000

• Error cause: The specified maximum number of recursive SQL levels is exceeded.

• Solution: Delete the recursive SQL or recursive triggers.

OBE-00051:timeout occurred while waiting for a resource

• OceanBase error code: 5848

• SQLSTATE: HY000

• Error cause: Usually caused by a dead instance.

• Solution: Check for any dead or unrecovered instances. If so, recover them.

OBE-00054:resource busy and acquire with NOWAIT specified or timeout expired

• OceanBase error code: 6006

• SQLSTATE: HY000

• Error cause: The resource is busy.

• Solution: Retry or increase the timeout period.

OBE-00185:invalid argument for %s call

• OceanBase error code: 5488
• SQLSTATE: HY000
• Error cause: The parameter for the %s call is invalid.

OBE-00060:deadlock detected while waiting for resource

• OceanBase error code: 4101

• SQLSTATE: HY000

• Error cause: A deadlock was detected while waiting for a resource.

• Solution: Check the trace file and examine the involved transactions and resources. Retry if necessary.

OBE-00060:internal error code, arguments: -6005, Try lock row conflict

• OceanBase error code: 6005
• SQLSTATE: HY000
• Error cause: The lock acquisition failed during an update operation. This error code is returned to the upper layer, and the operation is retried.
• Solution: An internal error code. Contact technical support for assistance.

OBE-00060:internal error code, arguments: -4012, Timeout, query has reached the maximum query timeout: %ld(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again

• OceanBase error code: 4012
• SQLSTATE: HY000
• Error cause: Execution timed out.
• Solution:
  • Reduce execution time through performance tuning.
  • Set a larger timeout period.
  • Contact technical support for assistance.

OBE-00060:internal error code, arguments: -4013, No memory or reach tenant memory limit

• OceanBase error code: 4013
• SQLSTATE: HY000
• Cause: Memory allocation failed.
  • Physical memory exhausted.
  • Single memory allocation exceeds 4 GB.
  • CTX, Tenant, or Server memory usage reaches the limit.
• Solution: Contact Technical Support for assistance.

OBE-00060:internal error code, arguments: -4016, Internal error

• OceanBase error code: 4016
• SQLSTATE: HY000
• Cause: Internal error code.
• Solution: Internal error code. Contact Technical Support for assistance.

OBE-00060:internal error code, arguments: -4377, fatal internal error

• OceanBase error code: 4377
• SQLSTATE: HY000
• Cause: An unexpected internal error occurred in OceanBase Database, possibly due to abnormal program execution.
• Solution: Contact Technical Support for assistance.

OBE-00060: Migrate tx data not continues

• oceanbase error code: 4408

• SQLSTATE: HY000

• Error cause: The source transaction data table for migration was reclaimed. During copying to the destination, it was found that the transaction data table was discontinuous, causing a failure and an error message. A retry is performed.

• Solution: In most cases, a retry will succeed. If failures persist, contact OceanBase Technical Support for assistance in troubleshooting.

OBE-00060:internal error code, arguments: -5065, Query execution was interrupted

• OceanBase error code: 5065
• SQLSTATE: HY000
• Error cause: The query was terminated.
• Solution: Contact the system administrator or database administrator.

OBE-00060:internal error code, arguments: -6220, SQL sequence illegal

• OceanBase error code: 6220
• SQLSTATE: HY000
• Error cause: The SQL statement sequence is invalid.
• Solution: This is an internal error code. Please contact Technical Support for assistance in troubleshooting.

OBE-00224:object '%.*s' must be of type function or array to be used this way

• OceanBase error code: 9765

• SQLSTATE: HY000

• Error cause: The object '%.*s' must be of type function or array to be used in this way.

• Solution: Check the object's type and adjust it as necessary.

OBE-00324:cursor attribute may not be applied to non-cursor %.*s

• OceanBase error code: 9784

• SQLSTATE: HY000

• Cause: Cursor attributes were applied to a non-cursor object.

• Solution: Ensure that the object is a cursor object before applying cursor attributes. If it is not a cursor object, modify the code logic to ensure that cursor attributes are only applied to cursor objects.

OBE-00600: internal error code, arguments: -4410, ls not in learner list

• OceanBase error code: 4410

• SQLSTATE: HY000

• Cause: During migration replication or rebuild, when selecting the source, the destination log stream replica is not in the Learner List, possibly because the destination log stream replica has been deleted.

• Solution: Wait for the corresponding task to automatically retry.

OBE-00600:internal error code, arguments: -4673, Data source not valid

• OceanBase error code: 4673

• SQLSTATE: HY000

• Cause: The data source configuration is invalid or unavailable.

• Solution: Check the data source connection parameters and confirm that the external system is accessible.

OBE-00600:internal error code, arguments: -4678, conflicting %.*s specifications

• OceanBase error code: 4678

• SQLSTATE: HY000

• Cause: The option specifications in the SQL statement are conflicting or contradictory.

• Solution: Check the conflicting option definitions and modify the SQL syntax.

OBE-00600:internal error code, arguments: -4679, duplicate %.*s specifications

• OceanBase error code: 4679

• SQLSTATE: HY000

• Cause: The SQL statement contains duplicate or conflicting option specifications.

• Solution: Check for duplicate options in the SQL statement and remove redundant parameter definitions.

OBE-00600:internal error code, arguments: -4680, %s

• OceanBase error code: 4680

• SQLSTATE: HY000

• Error cause: The option specifications in the SQL statement are invalid or illegal.

• Solution: Check the SQL syntax and parameters to confirm the validity of the option combination.

OBE-00600:internal error code, arguments: -4689, web service content not valid

• OceanBase error code: 4689

• SQLSTATE: HY000

• Error cause: The web service request content is invalid or has a format error. Possible causes include:

  • The HTTP request body format does not meet expectations.
  • JSON/XML parsing failed.
  • Missing parameters or incorrect format.
  • Request content length or encoding issues.

• Solution: Check the request format (such as JSON/XML) to confirm the validity of the request content.

OBE-00600:internal error code, arguments: -4728, interval partition already exists

• OceanBase error code: 4728

• SQLSTATE: HY000

• Error cause: An INTERVAL partition already exists.

• Solution: Check the existing partitions, use a different partition name or range, and recreate a unique partition.

OBE-00600:internal error code, arguments: -4729, the property of interval partition is changed

• OceanBase error code: 4729

• SQLSTATE: HY000

• Error cause: The properties of an INTERVAL partition have been changed.

• Solution: Check the current partition definition and recreate the partitioned table.

OBE-00600:arbitration service does not exist

• OceanBase error code: 4747

• SQLSTATE: HY000

• Error cause: The arbitration service address has not been configured for the cluster.

• Solution: Arbitration-related operations are not supported when the arbitration service address is not configured. You can add an arbitration service address for the cluster by using OCP or executing the SQL command alter system add arbitration service‘$svr_ip:$svr_port’;.

OBE-00600:arbitration service already exist

• OceanBase error code: 4748

• SQLSTATE: HY000

• Error cause: The cluster already has a valid arbitration service address.

• Solution: A cluster does not support configuring multiple arbitration services at the same time.

EOBE-00600: wait degration finished timeout

• OceanBase error code: 4751

• SQLSTATE: HY000

• Error cause: Timeout occurred while waiting for tenant degradation during the Stop Server operation.

• Solution: Reissue the Stop Server command until it succeeds.

OBE-00600:unknown SET option '%s'

• OceanBase error code: 4764
• SQLSTATE: HY000
• Error cause: An unknown SET option was specified when setting parameters.
• Solution: Check whether the options specified in the SET command are correct, ensuring no spelling or syntax errors.

OBE-00600: internal error code, arguments: -4780, This service_name is not found in the tenant

• OceanBase error code: 4780

• SQLSTATE: HY000

• Error cause: The specified service_name does not exist.

• Solution: Check whether there is an issue with the service_name specified in the connection string, or check the connectivity between the proxy and OCP.

OBE-00600: internal error code, arguments: -4781, The service has not started on all servers

• OceanBase error code: 4781

• SQLSTATE: HY000

• Error cause: When performing service_name-related maintenance operations (for example, creating or deleting a service_name), some servers failed to take effect after notification to each OBServer node.

• Solution: Wait for a period of time. Normally, background threads refresh periodically, with a default refresh interval of about 10 seconds.

OBE-00600: internal error code, arguments: -4782, The tenant is not PRIMARY

• OceanBase error code: 4782

• SQLSTATE: HY000

• Cause: When specifying both service_name and failover_mode, the tenant must be the primary tenant. If the current tenant is no longer the primary tenant, it is a proxy routing error.

• Solution: The proxy cache or OCP cache is incorrect. If both the proxy and OCP caches are normal, the system will retry and refresh. You can then re-execute the SQL, which will route to the correct primary tenant.

OBE-00600: internal error code, arguments: -4783, The service has stopped

• OceanBase error code: 4783

• SQLSTATE: HY000

• Cause: The specified service_name has been stopped by the user.

• Solution: You need to use the O&M command to start the service_name: ALTER SYSTEM START SERVICE service_name TENANT = tenant_name;.

OBE-00600: internal error code, arguments: -5240, Column part of USING clause cannot have qualifier

• OceanBase error code: 5240

• SQLSTATE: HY000

• Cause: Columns in the USING clause cannot have qualifiers.

• Solution: When using the USING clause, write only the column name, without table aliases or table names. If you need to use qualifiers, use the ON clause instead.

OBE-00600: internal error code, arguments: -5313, Failed to sync ddl '%.*s'

• OceanBase error code: 5313

• SQLSTATE: HY000

• Cause: DDL synchronization failed.

• Solution: Check the cluster status, network connectivity, and resource usage. Retry the DDL operation, or execute complex DDL statements in steps.

OBE-00600: internal error code, arguments: -5321, CONNECT BY clause required in this query block

• OceanBase error code: 5321

• SQLSTATE: HY000

• Cause: The CONNECT BY clause is missing in the query block.

• Solution: When using CONNECT BY related pseudo-columns or functions, you must add a CONNECT BY clause to define the hierarchy.

OBE-00600:internal error code, arguments: -5322, Specified pseudocolumn, operator or function not allowed here

• OceanBase error code: 5322

• SQLSTATE: HY000

• Cause: The pseudocolumn, operator, or function is used in an invalid position. In an SQL statement, some pseudocolumns, operators, and functions can only be used in specific contexts and cannot be placed arbitrarily.

• Solution: Check whether the pseudocolumn is used in a valid position (for example, SELECT, ORDER BY, or HAVING). Avoid using it in invalid positions such as WHERE and GROUP BY. If necessary, rewrite the query by using a subquery.

OBE-00600:internal error code, arguments: -5323, NOCYCLE keyword is required with CONNECT_BY_ISCYCLE pseudocolum

• OceanBase error code: 5323

• SQLSTATE: HY000

• Cause: The NOCYCLE keyword is missing when using the CONNECT_BY_ISCYCLE pseudocolumn.

• Solution: Add the NOCYCLE keyword to the CONNECT BY clause.

OBE-00600:internal error code, arguments: -5324, CONNECT BY loop in user data

• OceanBase error code: 5324

• SQLSTATE: HY000

• Cause: There is a circular reference in the CONNECT BY query.

• Solution: Use the NOCYCLE option to detect and fix the circular data. Add constraints to prevent loops.

OBE-00600:Cannot create a JSON value from a string

• OceanBase error code: 5415

• SQLSTATE: 22032

• Cause: Internal error code.

• Solution: This is an internal error code. Contact technical support for assistance.

OBE-00600:Invalid JSON character data provided to function

• OceanBase error code: 5416

• SQLSTATE: 22032

• Cause: Internal error code.

• Solution: This is an internal error code. Contact technical support for assistance.

OBE-00600:Invalid data type for JSON data in argument %u to function %s; a JSON string or JSON type is required

• OceanBase error code: 5417

• SQLSTATE: 22032

• Cause: Internal error code.

• Solution: This is an internal error code. Contact technical support for assistance.

OBE-00600:Cannot CAST value to JSON

• OceanBase error code: 5418

• SQLSTATE: 22032

• Cause: Internal error code.

• Solution: This is an internal error code. Contact technical support for assistance.

OBE-00600:A path expression must be encoded in the utf8 character set

• OceanBase error code: 5419

• SQLSTATE: 22032

• Cause: Internal error code.

• Solution: This is an internal error code. Contact technical support for assistance.

OBE-00600:In this situation, path expressions may not contain the * and ** tokens

• OceanBase error code: 5420

• SQLSTATE: 22032

• Error cause: Internal error code.

• Solution: This is an internal error code. Contact technical support for assistance.

OBE-00600:The JSON value is too big to be stored in a JSON column

• OceanBase error code: 5421

• SQLSTATE: 22032

• Error cause: Internal error code.

• Solution: This is an internal error code. Contact technical support for assistance.

OBE-00600:JSON column '%.*s' cannot be used in key specification

• OceanBase error code: 5423

• SQLSTATE: 22032

• Error cause: Internal error code.

• Solution: This is an internal error code. Contact technical support for assistance.

OBE-00600:The path expression is not allowed in this context

• OceanBase error code: 5424

• SQLSTATE: 22032

• Error cause: Internal error code.

• Solution: This is an internal error code. Contact technical support for assistance.

OBE-00600:The oneOrAll argument may take these values: \'one\' or \'all\'

• OceanBase error code: 5425

• SQLSTATE: 22032

• Error cause: Internal error code.

• Solution: This is an internal error code. Contact technical support for assistance.

OBE-00600:Out of range JSON value for CAST

• OceanBase error code: 5426

• SQLSTATE: 22032

• Cause: Internal error code.

• Solution: This is an internal error code. Contact technical support for assistance.

OBE-00600:Invalid JSON value for CAST

• OceanBase error code: 5427

• SQLSTATE: 22032

• Cause: Internal error code.

• Solution: This is an internal error code. Contact technical support for assistance.

OBE-00600:The JSON document exceeds the maximum depth

• OceanBase error code: 5428

• SQLSTATE: 22032

• Cause: Internal error code.

• Solution: This is an internal error code. Contact technical support for assistance.

OBE-00600:Invalid default value for \'%.*s\'

• OceanBase error code: 5430

• SQLSTATE: 22032

• Cause: Internal error code.

• Solution: This is an internal error code. Contact technical support for assistance.

OBE-00600:A path expression is not a path to a cell in an array

• OceanBase error code: 5431

• SQLSTATE: 22032

• Cause: Internal error code.

• Solution: This is an internal error code. Contact technical support for assistance.

OBE-40600:JSON_EQUAL used outside predicate

• OceanBase error code: 5448
• SQLSTATE: 42000
• Cause: JSON_EQUAL is used outside a predicate.
• Solution: Use JSON_EQUAL inside a predicate, for example, by embedding it in a CASE expression.

OBE-00600:internal error code, arguments: -5524, not support semistruct encoding.

• OceanBase error code: 5524

• SQLSTATE: HY000

• Cause: Semi-structured encoding is not supported.

OBE-00600:internal error code, arguments: -5602, Should collect histogram after major freeze

• OceanBase error code: 5602

• SQLSTATE: HY000

• Cause: Attempt to collect histogram statistics before a major compaction.

• Solution: Perform the major compaction first, and then collect the statistics.

OBE-00600:internal error code, arguments: -5688, Empty block prohibited in Oracle

• OceanBase error code: 5688

• SQLSTATE: 42000

• Cause: Empty block error in a stored procedure. In Oracle-compatible mode, empty BEGIN...END blocks are not allowed.

• Solution: Add actual processing logic to the BEGIN...END block.

OBE-00600:internal error code, arguments: -5689, array binding need rollback

• OceanBase error code: 5689

• SQLSTATE: HY000

• Cause: Batch operations require a rollback.

• Solution: Check each row of data, execute in batches, or resolve constraint conflicts before executing.

OBE-00600:internal error code, arguments: -5703, Add index failed

• OceanBase error code: 5703

• SQLSTATE: HY000

• Error cause: Failed to add an index.

• Solution: Check whether the index is valid. You can delete and then recreate it.

OBE-00600:auto increment service busy

• OceanBase error code: 5794

• SQLSTATE: HY000

• Error cause: Internal error code.

• Solution: This is an internal error code. Contact technical support for assistance.

OBE-00600:internal error code, arguments: -5826, ROWID for tables without primary key is not implemented

• OceanBase error code: 5826

• SQLSTATE: HY000

• Error cause: Tables without a primary key do not support the ROWID type.

• Solution: Add a primary key to the table.

OBE-00600:rowid type mismatch, expect %.*s, got %.*s"

• OceanBase error code: 5870

• SQLSTATE: HY000

• Error cause: Internal error code.

• Solution: This is an internal error code. Contact technical support for assistance.

OBE-00600:rowid num mismatch, expect %ld, actual %ld

• OceanBase error code: 5871

• SQLSTATE: HY000

• Error cause: Internal error code.

• Solution: This is an internal error code. Contact technical support for assistance.

OBE-00600: internal error code, arguments: -6288, too many pending log in the trx

• OceanBase error code: 6288

• SQLSTATE: HY000

• Cause: A transaction has too many logs waiting to be committed.

• Solution: Split large transactions or reduce the number of rows modified at once.

OBE-00600: internal error code, arguments: -7109, transfer system error

• OceanBase error code: 7109

• SQLSTATE: HY000

• Cause: A transfer system error occurred.

• Solution: This is an internal error code. Contact technical support for assistance.

OBE-00600: internal error code, arguments: -7110, transfer src ls and dest ls member list not same

• OceanBase error code: 7110

• SQLSTATE: HY000

• Cause: The log stream member lists at the source and destination are inconsistent during a transfer operation.

• Solution: Check the member lists at the source and destination. Verify that the disaster recovery module is running normally, check for any ongoing log stream replication tasks, and wait for the tasks to complete.

OBE-00600: internal error code, arguments: -7111, lock owner id is not expected

• OceanBase error code: 7111

• SQLSTATE: HY000

• Cause: During a lock operation, the actual lock holder does not match the expected one.

• Solution: Contact technical support for assistance.

OBE-00600: internal error code, arguments: -7112, change member list compare ls transfer scn too small

• OceanBase error code: 7112

• SQLSTATE: HY000

• Cause: The transfer timestamp (SCN) is too small when changing the member list.

• Solution: Contact technical support for assistance.

OBE-00600: internal error code, arguments: -7124, partitions are already balanced, %s

• OceanBase error code: 7124

• SQLSTATE: HY000

• Cause: The partition is already balanced when you try to perform a partition balancing operation.

OBE-00600:Binary geometry function given two geometries of different srids.Binary geometry function %s given two geometries of different srids: %u and %u, which should have been identical

• OceanBase error code: 7201
• SQLSTATE: HY000
• Cause: The binary geometry functions returned two different SRIDs: %u and %u, which should be the same. The geometry values passed as parameters to spatial functions must have the same SRID value.

OBE-00600:Calling geometry function with unsupported types of arguments.Calling geometry function %s with unsupported types of arguments

• OceanBase error code: 7202
• SQLSTATE: HY000
• Cause: You called the geometry function %s with unsupported parameter types.

OBE-00600:Unknown GIS error occurred in function.Unknown GIS error occurred in function %s

• OceanBase error code: 7203
• SQLSTATE: HY000
• Cause: An unknown GIS error occurred in the function %s.

OBE-00600:Unknown exception caught in GIS function.Unknown exception caught in GIS function %s

• OceanBase error code: 7204
• SQLSTATE: HY000
• Error message: An unknown exception was caught in the spatial function %s.

OBE-00600:Invalid GIS data provided to function.Invalid GIS data provided to function %s

• OceanBase error code: 7205
• SQLSTATE: 22023
• Error message: Invalid spatial data was provided to the function %s. A spatial function was called with a parameter that was not recognized as a valid geometric value.

OBE-00600:The geometry has no data in function.The geometry has no data in function %s

• OceanBase error code: 7206
• SQLSTATE: HY000
• Error message: The geometry has no data in the function %s.

OBE-00600:Unable to calculate centroid because geometry is empty in function.Unable to calculate centroid because geometry is empty in function %s

• OceanBase error code: 7207
• SQLSTATE: HY000
• Error message: Unable to calculate the centroid because the geometry in the function %s is empty.

OBE-00600:Geometry overlay calculation error: geometry data is invalid in function.Geometry overlay calculation error: geometry data is invalid in function %s

• OceanBase error code: 7208
• SQLSTATE: HY000
• Error message: Geometry overlay calculation error: the geometry data in the function %s is invalid.

OBE-00600:Geometry turn info calculation error: geometry data is invalid in function.Geometry turn info calculation error: geometry data is invalid in function %s

• OceanBase error code: 7209
• SQLSTATE: HY000
• Cause: An error occurred during the calculation of geometry turn information. The geometry data is invalid in function %s.

OBE-00600:Analysis procedures of intersection points interrupted unexpectedly in function.Analysis procedures of intersection points interrupted unexpectedly in function %s

• OceanBase error code: 7210
• SQLSTATE: HY000
• Cause: The intersection point analysis process was unexpectedly interrupted in function %s.

OBE-00600:Unknown exception thrown in function.Unknown exception thrown in function %s

• OceanBase error code: 7211
• SQLSTATE: HY000
• Cause: An unknown exception was thrown in function %s.

OBE-00600:Geometry byte string must be little endian

• OceanBase error code: 7212
• SQLSTATE: HY000
• Cause: The geometry byte string must be in little-endian order.

OBE-00600:Do not support online operation on table with GIS index

• OceanBase error code: 7213
• SQLSTATE: HY000
• Error message: Online operations are not supported for tables with spatial indexes.

OBE-00600:Inconsistent intersection points.Inconsistent intersection points

• OceanBase error code: 7214
• SQLSTATE: HY000
• Error message: Inconsistent intersection points.

OBE-00600:Parameter exceeds the maximum number of points in a geometryin function.Parameter %s exceeds the maximum number of points in a geometry (%lu) in function %s

• OceanBase error code: 7215
• SQLSTATE: HY000
• Error message: Parameter %s exceeds the maximum number of points in the geometry (%lu) of function %s.

OBE-00600:value is a geometry of unexpected type.%.64s value is a geometry of unexpected type %.64s in %.64s

• OceanBase error code: 7216
• SQLSTATE: 22S01
• Error message: The value %s is a geometry of unexpected type %s in %s.

OBE-00600:Can't parse the spatial reference system definition of SRID.Can't parse the spatial reference system definition of SRID %u

• OceanBase error code: 7217
• SQLSTATE: SR002
• Error cause: The spatial reference system definition for SRID %u cannot be parsed.

OBE-00600:The spatial reference system definition for SRID does not specify the mandatory (EPSG) projection parameter.The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter

• OceanBase error code: 7218
• SQLSTATE: SR003
• Error cause: The spatial reference system definition for SRID %u does not specify the mandatory %s (EPSG %u) projection parameter.

OBE-00600:There's no spatial reference system with SRID.There's no spatial reference system with SRID %u

• OceanBase error code: 7219
• SQLSTATE: 01000
• Error cause: No spatial reference system exists for SRID %u.

OBE-00600:Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian

• OceanBase error code: 7220
• SQLSTATE: 22S00
• Error cause: The function %s is defined only for Cartesian spatial reference systems, but one of its parameters is in SRID %u, which is not a Cartesian spatial reference system.

OBE-00600:Function is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID, which has not been defined.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined

• OceanBase error code: 7221
• SQLSTATE: SR001
• Error cause: The function %s is defined only for Cartesian spatial reference systems, but one of its parameters is in the undefined SRID %u.

OBE-00600:There's no spatial reference system with SRID.There's no spatial reference system with SRID %u

• OceanBase error code: 7222
• SQLSTATE: SR001
• Error cause: No spatial reference system with SRID %u exists.

OBE-00600:There's no spatial reference system with SRID. The axis order is unknown.There's no spatial reference system with SRID %u. The axis order is unknown

• OceanBase error code: 7223
• SQLSTATE: 01000
• Error cause: No spatial reference system with SRID %u exists. The axis order is unknown.

OBE-00600:It has not been implemented for geographic spatial reference systems.%.192s(%.80s) has not been implemented for geographic spatial reference systems

• OceanBase error code: 7224
• SQLSTATE: 22S00
• Error cause: %s(%s) has not been implemented for geographic spatial reference systems.

OBE-00600:The SRID of the geometry does not match the SRID of the column. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID property of the column

• OceanBase error code: 7225
• SQLSTATE: HY000
• Error cause: The SRID of the geometry does not match the SRID of column '%s'. The SRID of the geometry is %lu, but the SRID of the column is %lu. Consider changing the SRID of the geometry or the SRID attribute of the column.

OBE-00600:The SRID specification on the column cannot be changed because there is a spatial index on the column.The SRID specification on the column '%.64s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification

• OceanBase error code: 7226
• SQLSTATE: HY000
• Error message: The SRID specification on column '%s' cannot be changed because the column has a spatial index. Delete the spatial index before changing the SRID specification.

OBE-00600:The spatial index on column will not be used by the query optimizer since the column does not have an SRID attribute.The spatial index on column '%.64s' will not be used by the query optimizer since the column does not have an SRID attribute. Consider adding an SRID attribute to the column

• OceanBase error code: 7227
• SQLSTATE: HY000
• Error message: The query optimizer does not use the spatial index on column "%s" because the column lacks an SRID attribute. Consider adding an SRID attribute to the column.

OBE-00600:Function is only defined for SRID 0 and SRID 4326.Function %.192s is only defined for SRID 0 and SRID 4326

• OceanBase error code: 7228
• SQLSTATE: 22S00
• Error message: Function %s is defined only for SRID 0 and SRID 4326.

OBE-00600:It has not been implemented for Cartesian spatial reference systems.%.192s(%.80s) has not been implemented for Cartesian spatial reference systems

• OceanBase error code: 7229
• SQLSTATE: 22S00
• Error message: %s(%s) has not been implemented for Cartesian spatial reference systems.

OBE-00600:It has not been implemented for projected spatial reference systems.%.192s(%.80s) has not been implemented for projected spatial reference systems

• OceanBase error code: 7230
• SQLSTATE: 22S00
• Error message: %s(%s) has not been implemented for projected spatial reference systems.

OBE-00600:Missing mandatory attribute.Missing mandatory attribute %s

• OceanBase error code: 7231
• SQLSTATE: SR006
• Error cause: The mandatory attribute %s is missing.

OBE-00600:Multiple definitions of attribute.Multiple definitions of attribute %s

• OceanBase error code: 7232
• SQLSTATE: SR006
• Error cause: Multiple definitions of the attribute %s.

OBE-00600:The spatial reference system name can't be an empty string or start or end with whitespace

• OceanBase error code: 7233
• SQLSTATE: SR006
• Error cause: The spatial reference system name cannot be an empty string, nor can it start or end with a space.

OBE-00600:The organization name can't be an empty string or start or end with whitespace

• OceanBase error code: 7234
• SQLSTATE: SR006
• Error cause: The organization name cannot be an empty string, nor can it start or end with a space.

OBE-00600:There is already a spatial reference system with SRID.There is already a spatial reference system with SRID %u

• OceanBase error code: 7235
• SQLSTATE: SR004
• Error cause: A spatial reference system with SRID %u already exists.

OBE-00600:There is already a spatial reference system with SRID.There is already a spatial reference system with SRID %u

• OceanBase error code: 7236
• SQLSTATE: 01S00
• Error cause: A spatial reference system with SRID %u already exists.

OBE-00600:SRID 0 is not modifiable

• OceanBase error code: 7237
• SQLSTATE: SR000
• Error cause: SRID 0 cannot be modified.

OBE-00600:The SRID range has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade.The SRID range [%u, %u] has been reserved for system use. SRSs in this range may be added, modified or removed without warning during upgrade

• OceanBase error code: 7238
• SQLSTATE: 01S01
• Error cause: The SRID range [%u, %u] is reserved for system use. During an upgrade, SRSs within this range may be added, modified, or deleted without warning.

OBE-00600:Can't modify SRID. There is at least one column depending on it.Can't modify SRID %u. There is at least one column depending on it

• OceanBase error code: 7239
• SQLSTATE: SR005
• Error cause: SRID %u cannot be modified. At least one column depends on it.

OBE-00600:Invalid character in attribute.Invalid character in attribute %s

• OceanBase error code: 7240
• SQLSTATE: SR006
• Error cause: The character in attribute %s is invalid.

OBE-00600:Attribute is too long.Attribute %s is too long. The maximum length is %u characters

• OceanBase error code: 7241
• SQLSTATE: SR006
• Error cause: Attribute %s is too long. The maximum length is %u characters.

OBE-00600:Function is only defined for geographic spatial reference systems, but one of its arguments is in SRID, which is not geographic.Function %s is only defined for geographic spatial reference systems, but one of its arguments is in SRID %u, which is not geographic

• OceanBase error code: 7242
• SQLSTATE: 22S00
• Error cause: Function %s is defined only for the geospatial reference system, but one of its parameters has SRID %u, which is not geographic.

OBE-00600:Function encountered a polygon that was too large. Polygons must cover less than half the planet.Function %s encountered a polygon that was too large. Polygons must cover less than half the planet

• OceanBase error code: 7243
• SQLSTATE: 22023
• Error cause: Function %s encountered a polygon that is too large.

OBE-00600:Spatial indexes can't be primary or unique indexes

• OceanBase error code: 7244
• SQLSTATE: HY000
• Error message: A spatial index cannot be a primary key or unique key.

OBE-00600:The index type is not supported for spatial indexes.The index type %.20s is not supported for spatial indexes

• OceanBase error code: 7245
• SQLSTATE: HY000
• Error message: The spatial index does not support the index type %s.

OBE-00600:A parameter of function contains a geometry with longitude, which is out of range.A parameter of function %.192s contains a geometry with longitude %f, which is out of range. It must be within (%f, %f]

• OceanBase error code: 7246
• SQLSTATE: 22S02
• Error message: The parameter of function %s contains a geometry with longitude %f, which is out of range. It must be within the range (%f, %f).

OBE-00600:A parameter of function contains a geometry with latitude, which is out of range.A parameter of function %.192s contains a geometry with latitude %f, which is out of range. It must be within [%f, %f]

• OceanBase error code: 7247
• SQLSTATE: 22S03
• Error message: The parameter of function %s contains a geometry with latitude %f, which is out of range. It must be within the range [%f, %f].

OBE-00600:The spatial reference system definition for SRID specifies invalid geographic axes. One axis must be NORTH or SOUTH and the other must be EAST or WEST.he spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST

• OceanBase error code: 7248
• SQLSTATE: SR002
• Error message: The spatial reference system definition for SRID %u specifies invalid geographic axes '%s' and '%s'. One axis must be NORTH or SOUTH, and the other must be EAST or WEST.

OBE-00600:The spatial reference system definition for SRID specifies invalid geographic axes. One axis must be NORTH or SOUTH and the other must be EAST or WEST.he spatial reference system definition for SRID %u specifies invalid geographic axes '%.20s' and '%.20s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.

• OceanBase error code: 7249
• SQLSTATE: SR002
• Error cause: The spatial reference system definition for SRID %u specifies invalid geographic axes "%s" and "%s". One axis must be NORTH or SOUTH, and the other must be EAST or WEST.

OBE-00600:The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere

• OceanBase error code: 7250
• SQLSTATE: SR002
• Error cause: The inverse flattening must be greater than 1.0, or 0.0 if the ellipsoid is a sphere.

OBE-00600:The angular unit conversion factor must be a positive number

• OceanBase error code: 7251
• SQLSTATE: SR002
• Error cause: The angular unit conversion factor must be a positive number.

OBE-00600:The prime meridian must be within (*180, 180] degrees, specified in the SRS angular unit

• OceanBase error code: 7252
• SQLSTATE: SR002
• Error cause: The prime meridian must be within (*180, 180] degrees, as specified by the SRS angular unit.

OBE-00600:Transformation from SRID is not supported.Transformation from SRID %u is not supported

• OceanBase error code: 7253
• SQLSTATE: 22S00
• Error cause: Conversions from SRID %u are not supported.

OBE-00600:Transformation to SRID is not supported.Transformation to SRID %u is not supported

• OceanBase error code: 7254
• SQLSTATE: 22S00
• Error message: Transformation to SRID %u is not supported.

OBE-00600:Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause

• OceanBase error code: 7255
• SQLSTATE: 22S00
• Error message: Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause.

OBE-00600:Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause

• OceanBase error code: 7256
• SQLSTATE: 22S00
• Error message: Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.

OBE-00600:Cannot create a functional index on a function that returns a JSON or GEOMETRY value

• OceanBase error code: 7257
• SQLSTATE: 42000
• Error message: Cannot create a functional index on a function that returns a JSON or GEOMETRY value.

OBE-00600:Spatial functional index is not supported

• OceanBase error code: 7258
• SQLSTATE: HY000
• Error message: Spatial functional indexes are not supported.

OBE-00600:The geometry passed to function is in SRID 0, which doesn't specify a length unit. Can't convert.The geometry passed to function %s is in SRID 0, which doesn't specify a length unit. Can't convert to '%s'

• OceanBase error code: 7259
• SQLSTATE: SU001
• Error cause: The geometry passed to the %s function has SRID 0 and no length unit specified, so it cannot be converted to "%s".

OBE-00600:Invalid cast.Invalid cast from %s to %s

• OceanBase error code: 7260
• SQLSTATE: 22S01
• Error cause: The conversion from %s to %s is invalid.

OBE-00600:Invalid cast. A polygon ring is in the wrong direction.Invalid cast from %s to %s. A polygon ring is in the wrong direction

• OceanBase error code: 7261
• SQLSTATE: 22S04
• Error cause: The conversion from %s to %s is invalid. The direction of the polygon ring is incorrect.

OBE-00600:Arguments to function contains geometries with different SRIDs. All geometries must have the same SRID.Arguments to function %s contains geometries with different SRIDs: %u and %u. All geometries must have the same SRID

• OceanBase error code: 7262
• SQLSTATE: 22S05
• Error cause: The parameters of the %s function contain geometries %u and %u with different SRIDs. All geometries must have the same SRID.

OBE-00600:Longitude is out of range in function.Longitude %f is out of range in function %.192s. It must be within (%f, %f]

• OceanBase error code: 7263
• SQLSTATE: 22S02
• Error message: Longitude %f is out of the range of function %s. It must be within the range (%f, %f).

OBE-00600:Latitude is out of range in function.Latitude %f is out of range in function %.192s. It must be within [%f, %f]

• OceanBase error code: 7264
• SQLSTATE: 22S03
• Error message: Latitude %f is out of the range of function %s. It must be within the range [%f, %f].

OBE-00600:Memory allocation error.Memory allocation error: %*.256s in function %s

• OceanBase error code: 7265
• SQLSTATE: HY000
• Error message: Memory allocation error: %s in function %s.

OBE-00600:Domain error.Domain error: %*.256s in function %s

• OceanBase error code: 7266
• SQLSTATE: HY000
• Error message: Domain error: %s in function %s.

OBE-00600:Length error.Length error: %*.256s in function %s

• OceanBase error code: 7267
• SQLSTATE: HY000
• Error message: Length error: %s in function %s.

OBE-00600:Invalid argument error.Invalid argument error: %*.256s in function %s

• OceanBase error code: 7268
• SQLSTATE: HY000
• Cause: An invalid argument error occurred for %s in function %s.

OBE-00600:Out of range error.Out of range error: %*.256s in function %s

• OceanBase error code: 7269
• SQLSTATE: HY000
• Cause: An out-of-range error occurred for %s in function %s.

OBE-00600:Overflow error.Overflow error: %*.256s in function %s

• OceanBase error code: 7270
• SQLSTATE: HY000
• Cause: An overflow error occurred for %s in function %s.

OBE-00600:Range error.Range error: %*.256s in function %s

• OceanBase error code: 7271
• SQLSTATE: HY000
• Cause: A range error occurred for %s in function %s.

OBE-00600:Underflow error.Underflow error: %*.256s in function %s

• OceanBase error code: 7272
• SQLSTATE: HY000
• Error cause: Underflow error, %s in function %s.

OBE-00600:Logic error.Logic error: %*.256s in function %s

• OceanBase error code: 7273
• SQLSTATE: HY000
• Error cause: Logic error, %s in function %s.

OBE-00600:Runtime error.Runtime error: %*.256s in function %s

• OceanBase error code: 7274
• SQLSTATE: HY000
• Error cause: A runtime error occurred at %s in function %s.

OBE-00600:Unknown exception: %*.384s in function %s

• OceanBase error code: 7275
• SQLSTATE: HY000
• Error cause: An unknown exception occurred at %s in function %s.

OBE-00600:Cannot get geometry object from data you send to the GEOMETRY field

• OceanBase error code: 7276
• SQLSTATE: 22003
• Error cause: A geometry object cannot be obtained from the data you sent to the GEOMETRY field.

OBE-00600:Incorrect usage of srid, srid column attribute only support in geometry

• OceanBase error code: 7277
• SQLSTATE: HY000
• Error cause: The Srid is used incorrectly. The Srid column attribute is supported only in geometry.

OBE-00600:Incorrect usage of spatial/fulltext/hash index and explicit index order

• OceanBase error code: 7278
• SQLSTATE: HY000
• Error cause: Spatial/full-text/hash indexes and explicit index orders are used incorrectly.

OBE-00600:All parts of a SPATIAL index must be NOT NULL

• OceanBase error code: 7280
• SQLSTATE: 42000
• Error cause: All parts of a SPATIAL index must be NOT NULL.

OBE-00600:The index type is not supported for spatial indexes.The index type %s is not supported for spatial indexes

• OceanBase error code: 7281
• SQLSTATE: HY000
• Error cause: The index type %s is not supported for spatial indexes.

OBE-00600:There's no unit of measure.There's no unit of measure named '%s'

• OceanBase error code: 7282
• SQLSTATE: SU001
• Error cause: There is no measurement unit named "%s".

OBE-00600:The string is not a valid key value pair in function.The string '%.192s' is not a valid key %c value pair in function %.192s

• OceanBase error code: 7283
• SQLSTATE: 22023
• Error cause: The string '%s' is not a valid key %c value pair in the function %s.

OBE-00600:Invalid radius provided to function: Radius must be greater than zero.Invalid radius provided to function %s: Radius(%lf) must be greater than zero

• OceanBase error code: 7284
• SQLSTATE: 22023
• Error message: The radius provided to the %s function is invalid. The radius must be greater than zero.

OBE-00600:Spatial reference system is empty

• OceanBase error code: 7285
• SQLSTATE: SR001
• Error message: No spatial reference system with SRID %u exists.

OBE-00600:Invalid option key in function.Invalid option key '%.192s' in function %.192s

• OceanBase error code: 7286
• SQLSTATE: 22023
• Error message: The option key "%s" is invalid in the %s function.

OBE-00600: Invalid value for option in function.Invalid value '%.192s' for option '%.192s' in function '%.192s'

• OceanBase error code: 7287
• SQLSTATE: 22023
• Error message: The value "%s" for the option "%s" is invalid in the "%s" function.

OBE-00600: Unknown WKB type.Unknown WKB type(%d)! Full WKB type number was (%d)

• OceanBase error code: 7288
• SQLSTATE: 22S01
• Error message: The %s value is a geometry of an unexpected type %s in %s.

OBE-00600: A FTS index may only contain a text type column.

• OceanBase error code: 7289

• SQLSTATE: 42000

• Cause: A full-text search (FTS) index can only contain columns of the TEXT type.

• Solution: Ensure that the data type of the column for which you are creating an FTS index is TEXT, such as VARCHAR, TEXT, or CHAR.

OBE-00600: internal error code, arguments: -9094, Restore log stream failed

• OceanBase error code: 9094

• SQLSTATE: HY000

• Cause: Log stream restore failed, possibly due to corrupted data in the log stream to be restored.

• Solution: Contact technical support for assistance.

OBE-00600: internal error code, arguments: -9095, No tablet need backup

• OceanBase error code: 9095

• SQLSTATE: HY000

• Cause: No tablets require backup.

• Solution: Contact technical support for assistance.

OBE-00600: internal error code, arguments: -9104, fail to commit direct load

• OceanBase error code: 9104

• SQLSTATE: HY000

• Cause: Direct load COMMIT failed, possibly due to a leader switchover.

• Solution: If direct load fails, you can try importing again.

OBE-00600: internal error code, arguments: -9119, %s

• OceanBase error code: 9119

• SQLSTATE: HY000

• Cause: Insufficient data (log archive or data backup) is available to restore to the specified point during data recovery. Possible causes:

  • The data backup set is incomplete, with missing or corrupted backup files.
  • Archival logs are missing, causing the required logs for restoring to the specified point to be discontinuous.
  • The restore point exceeds the range that can be recovered from the backup set and log archive, attempting to restore to a point without backups or logs.

• Solution:

  • Verify the restore point.
  • Check the integrity and time range of the backup set.
  • Confirm the continuity of the archived logs.

OBE-00600: internal error code, arguments: -9120, cannot find object on object storage

• OceanBase error code: 9120

• SQLSTATE: HY000

• Cause: The specified object (file) cannot be found in object storage. Possible causes:

  • The accessed object does not exist.
  • The specified path is incorrect.
  • Insufficient permissions to access object storage.

• Solution:

  • Check whether the accessed object or file exists.
  • Confirm whether the object storage path is correctly configured.
  • Confirm whether the current user has access permissions for object storage.

OBE-00600: internal error code, arguments: -9129, object storage io error

• OceanBase error code: 9129
• SQLSTATE: HY000
• Cause: An object storage error code. Common causes include connectivity and compatibility issues with object storage.
• Solution: Check the connectivity of object storage. If no connectivity issues are found, contact technical support for assistance in troubleshooting.

OBE-00600: internal error code, arguments: -9130, the pwrite offset of the object storage is inconsistent

• OceanBase error code: 9130

• SQLSTATE: HY000

• Cause: When performing an Append operation in object storage, the provided offset is inconsistent with the length of the current object.

• Solution: Contact technical support for assistance.

OBE-00600: internal error code, arguments: -9131, the contents of pwrite are inconsistent

• OceanBase error code: 9131

• SQLSTATE: HY000

• Cause: When performing an Append operation in object storage, if the provided offset is smaller than the length of the current object for some reason, a Get request is initiated to read the overlapping content. An error is reported if the content is inconsistent.

• Solution: Contact technical support for assistance.

OBE-00600: internal error code, arguments: -9132, object storage data checksum error

• OceanBase error code: 9132

• SQLSTATE: HY000

• Cause: An object storage data checksum error.

• Solution: This is an internal error code. Please contact technical support for assistance in troubleshooting.

OBE-00600: internal error code, arguments: -9134, tmp file has already sealed

• OceanBase error code: 9134

• Cause: The temporary file has been sealed.

• Solution: Retry the SQL statement. If the issue persists, contact technical support for assistance.

OBE-00600: tmp file exceeds disk quota

• OceanBase error code: 9135

• SQLSTATE: HY000

• Error cause: The amount of data with temporary files persisted on disk exceeds the set upper limit.

• Solution: Check whether the current erroneous SQL statement generates an amount of data exceeding the expected value (for example, the maximum expected amount of data with temporary files persisted on disk is 500 GB). If so, adjust the temporary_file_max_disk_size parameter to an appropriate value.

OBE-00600: internal error code, arguments: -9138, No suitable replica found to perform backup

• OceanBase error code: 9138

• SQLSTATE: HY000

• Error cause: No suitable replica was found to perform the backup operation.

• Solution: Check the status of the replicas. After confirming they are normal, re-initiate the backup.

OBE-00600: kms destination is not valid

• OceanBase error code: 9139

• SQLSTATE: HY000

• Error cause: When transparent encryption is enabled for the backup tenant, the key address was not specified or was specified incorrectly during tenant restore.

• Solution: Specify the correct key address in the restore command, or specify the correct key address by setting the Session variable SET @kms_encrypt_info before restore.

OBE-00600: the object is locked by worm

• OceanBase error code: 9140

• SQLSTATE: HY000

• Error cause: Attempt to delete or modify an object in object storage that is in the retention period.

• Solution: Check whether a retention policy is configured for the backup or archive path, and whether the enable_worm parameter was correctly configured when setting the backup or archive path. If the enable_worm parameter was correctly configured, contact OceanBase Technical Support for assistance.

OBE-00600: the resource has been released

• OceanBase error code: 9141

• SQLSTATE: HY000

• Cause: The macroblock of a temporary file was unexpectedly released during use.

• Solution: Contact OceanBase Technical Support for assistance.

OBE-00600: the object can not be overwritten with different content

• OceanBase error code: 9142

• SQLSTATE: HY000

• Cause: A non-idempotent file with the same name is written to an object store configured with a retention policy.

• Solution: Contact OceanBase Technical Support for assistance.

OBE-00600: internal error code, arguments: -9147, can not access backup set file

• OceanBase error code: 9147

• SQLSTATE: HY000

• Cause: During physical restore execution, the OBServer node cannot access the backup set file in the specified backup medium.

• Solution: Check the connectivity of the object store. If no connectivity issues are found, contact Technical Support for assistance.

OBE-00600:internal error code, arguments: -9148, disk quota is exceeded

• OceanBase error code: 9148

• SQLSTATE: HY000

• Cause: The disk quota has been exceeded.

• Solution: Clean up the files or adjust the disk quota.

OBE-00600:internal error code, arguments: -9149, backup dest is not allowed to set when log_only policy exists

• OceanBase error code: 9149

• SQLSTATE: HY000

• Cause: The log_only cleanup policy applies only to scenarios where only log archiving is enabled and no data backup is performed. When the log_only cleanup policy is in effect, configuring a data backup path is not allowed.

• Solution: First, remove the log_only cleanup policy, then configure the data backup path.

OBE-00600:internal error code, arguments: -9150, log_only policy is not allowed to set when backup dest exists

• OceanBase error code: 9150

• SQLSTATE: HY000

• Cause: The log_only cleanup policy applies only to scenarios where only log archiving is enabled and no data backup is performed. When a data backup path is already configured, the cleanup policy cannot be set to log_only.

• Solution: To use the log_only cleanup policy, you must first delete the configured data backup path.

OBE-00600:internal error code, arguments: -9151, backup clean can not start, because %s

• OceanBase error code: 9151

• SQLSTATE: HY000

• Cause: Data backup and archiving cleanup cannot proceed. Possible reasons include the tenant status being non-NORMAL (e.g., CREATING, RESTORE) or the tenant not having a cleanup policy configured (for expiration cleanup scenarios).

• Solution: Check whether the tenant status is normal. For expiration cleanup scenarios, confirm whether the relevant tenant has a cleanup policy correctly configured.

OBE-00600:internal error code, arguments: -9152, backup device may be not mounted, %s did not read any data written by %s

• OceanBase error code: 9152

• SQLSTATE: HY000

• Cause: The backup medium is not correctly mounted.

• Solution: Correctly mount the backup medium to ensure that all OBServer nodes of the tenant initiating the archiving/backup/restoration operation can access the same backup medium. For detailed operations on mounting NFS, see Deploy NFS.

OBE-00600:internal error code, arguments: -9153, backup device is not read and write strongly consistent. %s did not read the latest data written by %s.

• OceanBase error code: 9153

• SQLSTATE: HY000

• Cause: The read and write operations on the backup medium are not strongly consistent.

• Solution: If the backup medium is NFS, refer to Deploy NFS and mount it according to the specified method. If the backup medium is object storage, contact the corresponding service provider.

OBE-00600: internal error code, arguments: -9155, micro block is too large and rejected from micro cache

• OceanBase error code: 9155

• SQLSTATE: HY000

• Cause: The size of the microblock to be cached exceeds the upper limit allowed by the microcache (default is 128 KB), and the system refuses to write this microblock to the microcache.

• Solution: This error is a normal internal flow control behavior of the system and does not affect data correctness or business availability. Generally, no action is required. If it occurs frequently and significantly impacts read performance, contact technical support for assistance.

OBE-00600: internal error code, arguments: -9156, ss ls is in gc status

• OceanBase error code: 9156

• SQLSTATE: HY000

• Cause: The log stream is in GC status and no longer accepts new write or operation requests.

• Solution: Retry may succeed. If failures persist, contact OceanBase Technical Support for assistance.

OBE-00600:internal error code, arguments: -9158, the object type is invalid

• OceanBase error code: 9158

• SQLSTATE: HY000

• Cause: An unexpected object type was encountered when writing data to object storage. For example, a Put operation was performed on an Append-type object, or an Append operation was performed on a normal-type object.

• Solution: Contact Technical Support for assistance.

OBE-00600:internal error code, arguments: -9159, available data backup set is not found

• OceanBase error code: 9159

• SQLSTATE: HY000

• Error cause: Unable to restore to the specified time using any backup set.

• Solution: Select a different restore point or specify another backup set path.

OBE-00600:internal error code, arguments: -9574, document is not a stylesheet

• OceanBase error code: 9574

• SQLSTATE: HY000

• Error cause: Attempted to use a non-sheetstyle document as an XSL sheetstyle.

• Solution: Check the format and validity of the XSL sheetstyle to ensure no format errors or parameter errors exist.

OBE-00600:Incorrect usage of %s

• OceanBase error code: 9751
• SQLSTATE: HY000
• Error cause: Incorrect usage.
• Solution: Please check whether the usage is correct and use it in the correct way.

OBE-00600: internal error code, arguments: -9808, Table type is not valid, the definition of materialized view can only reference user tables or other materialized views

• OceanBase error code: 9808

• SQLSTATE: HY000

• Error cause: The table type referenced in the definition of the materialized view is invalid.

• Solution: Check the object types referenced in the definition of the materialized view (the definition of a materialized view can only reference user tables or other materialized views).

OBE-00600: internal error code, arguments: -9809, Base tables are altered during the creation or complete refresh of materialized views, please try again when base tables have no ongoing DDL operations

• OceanBase error code: 9809

• SQLSTATE: HY000

• Error cause: A DDL operation is being performed on the base table during the creation or complete refresh of the materialized view.

• Solution: Check whether a DDL operation is being performed on the base table of the materialized view.

OBE-00600: internal error code, arguments: -9810, Materialized view %s.%s has invalid dependency info, please perform a complete refresh to recover

• OceanBase error code: 9810

• SQLSTATE: HY000

• Cause: The dependency information for the materialized view %s is invalid.

• Solution: Perform a complete refresh on the materialized view.

OBE-00600: internal error code, arguments: -11015, Can't update table '%s' while '%s' is being created.

• OceanBase error code: 11015

• Cause: A table cannot be updated while it is being created.

• Solution: Wait for the table creation to complete and then try again.

OBE-00600: internal error code, arguments: -11018, Invalid external file: %s

• OceanBase error code: 11018

• SQLSTATE: HY000

• Cause: The specified external file cannot be read correctly.

• Solution:

  • Check whether the file exists, whether the file path is correct, and whether the current user has access permissions for the file.

  • Check whether the file format or encoding matches.

  • Check whether the file content is corrupted or has a format error.

OBE-00600: internal error code, arguments: -11020, HDFS: could not open file on hdfs

• OceanBase error code: 11020

• SQLSTATE: HY000

• Cause:

  • The file may not exist or you may not have permission.

  • The file opening mode does not match.

• Solution:

  • Check whether the file path is correct and ensure the file actually exists on HDFS.

  • Check the HDFS file permissions to ensure the current user has read or write access.

  • Confirm whether the HDFS namenode or datanode service is running normally.

OBE-00600: internal error code, arguments: -11021, HDFS: error reading the file on hdfs

• OceanBase error code: 11021

• SQLSTATE: HY000

• Error cause: Failed to read the HDFS file.

• Solution:

  • Confirm whether the HDFS datanode is running normally and the network connection is intact.

  • Check the HDFS logs (non-OceanBase Database-related HDFS logs) for any corrupt blocks or unavailable replicas.

OBE-00600: internal error code, arguments: -11042, HDFS: malformed uri

• OceanBase error code: 11042

• SQLSTATE: HY000

• Error cause:

  • The URI is missing the hdfs:// prefix.

  • The URI is missing the path part, i.e., there is no /path after hdfs://authority.

• Solution:

  • Ensure the URI format is hdfs://<namenode>:<port>/<path>, which must include the complete scheme, authority, and path.

  • Check whether the spelling of the LOCATION field in the external table or backup configuration is correct.

OBE-00600: internal error code, arguments: -11043, HDFS: invalid argument

• OceanBase error code: 11043

• SQLSTATE: HY000

• Error cause:

  • Incorrect HDFS URI format.
  • Incorrect Kerberos authentication configuration.
  • HDFS client environment not initialized or invalid.
  • Invalid HDFS connection parameters.
  • Failed to set HDFS parameters.

• Solution:

  • Check whether the HDFS URI format is correct and whether the HDFS-related configurations are complete.
  • Confirm that the files required for Kerberos authentication (keytab, krb5.conf, ticket cache) exist and have the correct paths.
  • Check the network connectivity of the HDFS cluster to ensure the namenode is accessible.
  • Check whether the key=value format of HDFS custom parameters is correct, and ensure there are no empty keys or values.

OBE-00600: internal error code, arguments: -11044, HDFS: not implementation

• OceanBase error code: 11044

• SQLSTATE: HY000

• Cause: An attempt was made to use a feature that is not yet implemented in HDFS. The current HDFS storage backend does not support pwrite and append write operations.

OBE-00600: internal error code, arguments: -11045, HDFS error

• OceanBase error code: 11045

• SQLSTATE: HY000

• Cause:

  • Duplicate access, possibly attempting to open a file that has already been opened.

  • Attempting to perform operations such as delete, mkdir, or list before a connection to HDFS is successfully established.

  • File deletion failed, possibly due to the file not existing or insufficient permissions.

  • Directory creation failed.

  • Write failed.

  • Flush failed.

• Solution:

  • Check the permissions of the HDFS file or directory to confirm whether the current user has read, write, and delete permissions.

  • Confirm whether the target path exists and has the correct format.

  • Ensure proper lifecycle management of HDFS components to avoid duplicate access or operations performed before a connection is successfully established.

  • Check whether the disk space of the HDFS cluster is sufficient.

OBE-00600: internal error code, arguments: -11046, Invalid path: %.*s

• OceanBase error code: 11046

• SQLSTATE: HY000

• Cause:

  • The column name or path specified in the DDL statement does not match the spelling or case of the column name in the file (files such as Parquet, ORC, and Arrow are typically case-sensitive).

  • An incorrect nested structure path was entered. For example, the target is addr.city, but it was written as addr_city or address.city in the DDL.

  • In the same external table, some files lack this column.

  • Format symbol issues. For example, extra spaces, quotes, or incorrect escape characters before or after the column name.

• Solution:

  • Verify whether the data_access_path or EXTERNAL_FILE_COLUMN_PATTERN on the external column in the DDL statement actually exists in the file's schema.

  • When specifying nested types, use the actual hierarchical path separator of the file for precise matching.

  • If the schemas of files from different partitions differ, create separate external tables for the files lacking the column, or set a default value for that column to avoid directly using path mapping to handle missing columns.

  • Modify the incorrect column definition and recreate the external table.

OBE-00600: internal error code, arguments: -11047, Column type mismatch between the file and the table: FileColumnType=%s TableColumnType=%s

• OceanBase error code: 11047

• SQLSTATE: HY000

• Cause: The column type in the file does not match the table definition.

• Solution: Compare the file content with the table definition to identify the mismatched column type, and modify the table definition or file content accordingly.

OBE-00600: internal error code, arguments: -11049, Exceed query memory limit (mem_limit=%ld, mem_hold=%ld), please check whether the query_memory_limit_percentage configuration item is reasonable.

• OceanBase error code: 11049
• SQLSTATE: HY000
• Cause: Query memory exceeds the limit.
• Solution: Check the value of the query_memory_limit_percentage parameter to ensure the setting is reasonable.

OBE-00600: internal error code, arguments: -11063, missing format for external table

• OceanBase error code: 11063

• SQLSTATE: HY000

• Cause: The file format was not specified when creating the external table, or no valid format configuration appeared in the DDL statement.

• Solution:

  • Add a FORMAT clause to the CREATE EXTERNAL TABLE statement and specify a TYPE consistent with the actual file.

  • Ensure the TYPE matches the actual file extension and content (for example, if the directory contains .parquet files, use PARQUET instead of CSV).

  • If using CSV, add parameters such as the delimiter and encoding as needed to avoid successful table creation but abnormal query parsing.

OBE-00600: internal error code, arguments: -11064, missing access path for external table

• OceanBase error code: 11064

• SQLSTATE: HY000

• Cause: The data access path was not specified when creating an external table. This is usually because the LOCATION parameter is not configured, is empty, or has not been correctly bound to a Location object.

• Solution:

  • Add a LOCATION clause to the DDL statement, pointing to the directory or URL where the external data is stored.

  • Ensure the path is accessible to the OceanBase cluster (network, authentication, mounting, object storage AK/SK, etc., configured according to the environment).

  • If using a Location object, first confirm that the object has been created and the current user has read permissions before referencing it in the external table.

  • It is recommended to use a protocol prefix agreed upon with relevant personnel for the path (such as file://, oss://, hdfs://, etc., subject to the version's support).

OBE-00600: internal error code, arguments: -11081, skip_header and parse_header cannot be used at the same time

• OceanBase error code: 11081

• SQLSTATE: HY000

• Cause: PARSE_HEADER and SKIP_HEADER cannot be used simultaneously due to semantic conflict.

• Solution: Do not use the PARSE_HEADER and SKIP_HEADER parameters together when specifying properties related to the external file format.

OBE-00600: internal error code, arguments: -11082, DDL operations on the internal catalog are not allowed

• OceanBase error code: 11082

• SQLSTATE: HY000

• Cause: DDL operations on the Internal Catalog are not allowed.

• Solution: Check the type of the Catalog to be operated on.

OBE-00600: internal error code, arguments: -11083, Command denied to user '%.*s'@'%.*s' for catalog '%.*s'

• OceanBase error code: 11083

• SQLSTATE: HY000

• Cause: The user does not have the privilege to operate on the catalog.

• Solution: Check whether the user has the privilege on the catalog and grant the corresponding privilege to the user.

OBE-00600: internal error code, arguments: -11084, Privilege not allowed for catalogs

• OceanBase error code: 11084

• SQLSTATE: HY000

• Cause: The catalog does not have the required privilege.

• Solution: Check the privileges of the catalog.

OBE-00600: internal error code, arguments: -11085, CCL rule '%.*s' already exists

• OceanBase error code: 11085

• SQLSTATE: HY000

• Cause: A CCL rule with the same name already exists when creating the new one.

• Solution: Use the IF NOT EXISTS keyword or delete the old rule before creating a new one.

OBE-00600: internal error code, arguments: -11086, CCL rule '%.*s' doesn't exist

• OceanBase error code: 11086

• SQLSTATE: HY000

• Cause: The rule does not exist when modifying or deleting it.

• Solution: Use the IF EXISTS keyword or confirm whether the rule name is correct.

OBE-00600: internal error code, arguments: -11087, SQL reach max ccl rule %s, concurrent num %ld

• OceanBase error code: 11087

• SQLSTATE: HY000

• Cause: The number of concurrent SQL statements has reached the upper limit specified by the CCL rule.

• Solution: Wait until the concurrency drops and then retry, or increase the value of MAX_CONCURRENCY.

OBE-00600: internal error code, arguments: -11088, reject limit %ld reached

• OceanBase error code: 11088

• SQLSTATE: HY000

• Error cause: Reached the denial limit %ld.

• Solution: Check the diagnostic error limit information.

OBE-00600: internal error code, arguments: -11089, Location is still in use

• OceanBase error code: 11089

• SQLSTATE: HY000

• Error cause: The accessed Location object is being used by an external table.

• Solution: Check all external tables that depend on this Location object to confirm if the dependency has been removed, and then re-execute the operation.

OBE-00600: internal error code, arguments: -11090, Location access denied

• OceanBase error code: 11090

• SQLSTATE: HY000

• Error cause: The specified Location object cannot be accessed.

• Solution: Check the user's access permissions for this Location object. Grant the READ privilege to the user using the command GRANT READ ON LOCATION location_name TO user_name WITH GRANT OPTION;.

OBE-00600: internal error code, arguments: -11091, Can't create location '%.*s'; location exists

• OceanBase error code: 11091

• SQLSTATE: HY000

• Error cause: The specified Location object already exists and cannot be created.

• Solution: Check if the specified Location object already exists. Replace the original Location object definition with a new one by adding the OR REPLACE keyword, or create a completely new Location object.

OBE-00600: internal error code, arguments: -11092, location '%.*s' doesn't exist

• OceanBase error code: 11092

• SQLSTATE: HY000

• Error cause: The specified Location object does not exist.

• Solution: Check if the specified Location object already exists and specify the correct Location object.

OBE-00600: internal error code, arguments: -11093, OBLogService rpc execute failed

• OceanBase error code: 11093

• SQLSTATE:HY000

• Cause: The log service RPC failed to execute due to insufficient target node resources or a network failure.

• Solution: First, locate the target node logs by trace_id, and resolve the issue by checking resource monitoring data and adjusting parameters.

OBE-00600: internal error code, arguments: -11094, Sensitive rule '%.*s' exists

• OceanBase error code: 11094

• SQLSTATE:HY000

• Cause: A sensitive rule with the same name already exists. This typically occurs when adding a new sensitive rule via a DDL statement if the new rule's name duplicates an existing one.

• Solution: Check whether the specified sensitive rule name already exists, and specify a different, non-existent sensitive rule name.

OBE-00600: internal error code, arguments: -11095, Sensitive rule '%.*s' does not exist

• OceanBase error code: 11095

• SQLSTATE: HY000

• Cause: The sensitive rule with the specified name does not exist. This usually occurs when deleting a sensitive rule using a DDL statement and specifying a non-existent rule name.

• Solution: Check whether the input sensitive rule name is correct and re-enter the correct sensitive rule name.

OBE-00600: internal error code, arguments: -11096, Sensitive column %.*s(%.*s) exists

• OceanBase error code: 11096

• SQLSTATE: HY000

• Cause: The specified column is already a sensitive column. This usually occurs when adding or modifying a sensitive rule using a DDL statement, and you attempt to apply a sensitive rule to a column that is already covered by another sensitive rule.

• Solution: Check whether the specified column is a sensitive column and select an appropriate column to add the sensitive rule.

OBE-00600: internal error code, arguments: -11097, Sensitive column %.*s(%.*s) does not exist

• OceanBase error code: 11097

• SQLSTATE: HY000

• Cause: The sensitive column with the specified name does not exist. This usually occurs when modifying a sensitive rule using a DDL statement, and you attempt to remove a column that is not a sensitive column.

• Solution: Check whether the specified sensitive column exists and re-enter the correct sensitive column name.

OBE-00600: internal error code, arguments: -11098, %.*s command denied to user '%.*s'@'%.*s' for sensitive rule '%.*s'

• OceanBase error code: 11098

• SQLSTATE: HY000

• Cause: The user does not have permission to execute the sensitive rule command '%.*s'. This usually occurs when a DML statement (such as INSERT, UPDATE, or REPLACE) accesses a column protected by a sensitive rule.

• Solution: Check the user's permissions and grant the user appropriate explicit access permissions using the GRANT PLAINACCESS ON SENSITIVE RULE '%.*s' TO '%.*s'@'%.*s' command.

OBE-00600: internal error code, arguments: -11099, Invalid sensitive rule name '%.*s'

• OceanBase error code: 11099

• SQLSTATE: HY000

• Cause: The sensitive rule name is invalid.

• Solution: Check whether the specified sensitive rule name is correct and re-enter the correct sensitive rule name.

OBE-00603: Prepare statement checksum error

• OceanBase error code: 5777

• SQLSTATE: HY000

• Cause: The server session is in a non-recoverable state.

• Solution: Log in to OceanBase Database again so that a new server session is automatically created. For more details, check the session trace file.

OBE-00715: attribute or method by name '%.*s' does not exist

• OceanBase error code: 9829
• SQLSTATE: HY000
• Cause: A property that is not defined on a database object was referenced.
• Solution: Ensure that every name of a database object referenced is accurate and exists.

OBE-00716: Attribute/method '%.*s' can occur only once in an ALTER TYPE statement

• OceanBase error code: 9831
• SQLSTATE: HY000
• Cause: In an ALTER TYPE statement, the same attribute or method name can only appear once.
• Solution: Carefully review and simplify your ALTER TYPE statement to ensure no duplicate names exist. For complex schema changes, consider splitting them into multiple simple, clear statements for sequential execution.

OBE-00718: type of attribute '%.*s' does not allow modifications to the attribute

• OceanBase error code: 9833
• SQLSTATE: HY000
• Cause: Modifications to this attribute are not allowed.
• Solution: The key to resolving this issue is to identify the source of the restriction and adopt a workaround strategy.

OBE-00719: only widening of attribute '%.*s' constraints is allowed

• OceanBase error code: 9830
• SQLSTATE: HY000
• Cause: OceanBase Database only allows increasing the length or constraints of a field, but not decreasing them.
• Solution: When this error occurs, you cannot perform the reduction operation forcibly. You need to reassess the necessity of reducing the length.

OBE-00739:FORALL INSERT/UPDATE/DELETE not support on remote tables

• OceanBase error code: 9752
• SQLSTATE: HY000
• Cause: FORALL INSERT/UPDATE/DELETE is not supported on remote tables.
• Solution: Do not use FORALL INSERT/UPDATE/DELETE on remote tables.

OBE-00900:invalid SQL statement

• OceanBase error code: 5001

• SQLSTATE: 42000

• Cause: The SQL statement contains errors.

• Solution: Refer to the "SQL Reference (Oracle-compatible mode)" for your corresponding OceanBase Database version to find the correct SQL statement.

• OceanBase error code: 5006

• SQLSTATE: 42000

• Cause: The SQL statement contains errors.

• Solution: Refer to the SQL Reference (Oracle-compatible mode) of your OceanBase database version to find the correct SQL statement.

Related issues:

• Error when creating a table group with RANGE or LIST partitions in an Oracle-compatible tenant, error code OBE-00900
• The PL module in OceanBase Database Oracle-compatible mode does not support the identifier NEW
• Stored procedure error caused by the $$PLSQL_UNIT variable in an Oracle-compatible tenant
• Differences between unique constraints and regular constraints in OceanBase Database

OBE-00902:invalid datatype

• OceanBase error code: 5874

• SQLSTATE: HY000

• Cause: The data type is invalid.

OBE-00903:invalid table name

• OceanBase error code: 5163

• SQLSTATE: 42000

• Cause: The table name is invalid.

OBE-00904:invalid identifier '%.*s'

• OceanBase error code: 5164

• SQLSTATE: 42000

• Cause: The string contains an invalid identifier.

OBE-00904:invalid identifier '%.*s'in '%.*s'

• OceanBase error code: 5217

• SQLSTATE: 42S22

• Cause: The string contains an invalid identifier.

Related issues:

• OBE-00904 error when operating on a table using the INSERT ALL statement in a trigger in Oracle-compatible mode

OBE-00904:'%.*s': invalid identifier

• OceanBase error code: 5211

• SQLSTATE: 42000

• Cause: The string contains an invalid identifier.

OBE-00905:missing keyword

• OceanBase error code: 5096

• SQLSTATE: HY000

• Error message: SQL statement is missing a keyword.

OBE-00909:invalid number of arguments in the call to native function '%.*s'

• OceanBase error code: 5054

• SQLSTATE: 42000

• Error message: The number of parameters is invalid.

OBE-00910:specified length too longfor column '%s' (max = %d byte)

• OceanBase error code: 5198

• SQLSTATE: 42000

• Error message: The specified string length is greater than the length supported by the data type. That is, for the CHAR and RAW data types, the specified string length is greater than 2000; for other data types, the specified string length is greater than 4000.

• Solution: Reduce the string length or switch to another data type that supports longer string lengths, such as VARCHAR2, LONG CHAR, or LONG RAW.

OBE-00911: invalid character

• OceanBase error code: 9782

• SQLSTATE: HY000

• Error message: Invalid character.

• Solution: Check and use a valid character set.

OBE-00913:too many values

• OceanBase error code: 5613

• SQLSTATE: HY000

• Error message: Too many values.

OBE-00917:missing comma

• OceanBase error code: 7403
• SQLSTATE: 42000
• Error message: A required comma is omitted in an INSERT statement or in a list of columns or values in the form ((C,D),(E,F), ...).
• Solution: Correct the syntax. Carefully check the SQL statement for missing commas or incorrect comma usage.

OBE-00918:column '%.*s' in %.*%s ambiguously defined

• OceanBase error code: 5207

• SQLSTATE: 23000

• Cause: The column definition is ambiguous.

OBE-00925:missing INTO keyword

• OceanBase error code: 9712

• SQLSTATE: HY000

• Cause: The INTO keyword is missing when executing the INSERT statement.

• Solution: Add the missing INTO keyword and re-execute the statement.

OBE-00926:missing VALUES keyword

• OceanBase error code: 5574

• SQLSTATE: HY000

• Cause: The VALUES keyword is missing.

OBE-00931:missing identifier

• OceanBase error code: 5963

• SQLSTATE: HY000

• Cause: An identifier is missing.

OBE-00932:inconsistent datatypes: left_type=%s right_type=%s

• OceanBase error code: 5083

• SQLSTATE: 22000

• Error cause: Inconsistent data types.

Related issues:

• Inconsistent data types reported during type operations in OceanBase Database Oracle-compatible mode
• Update a CLOB column in Oracle-compatible mode and get error ret_code=-5083
• Error 'inconsistent datatypes' when ordering by a CLOB column
• Insert data with inconsistent data types and get error code OBE-00932

OBE-00932:inconsistent datatypes,inconsistent datatypes: expected %s got %s

• OceanBase error code: 7402
• SQLSTATE: 22000
• Error cause: Incompatible data types are used in the SQL query.
• Solution: Check the SQL query statement to identify the inconsistent data types, and use the CAST or CONVERT function to convert the data types to the same type.

OBE-00932:inconsistent dimension: expected %u got %u

• OceanBase error code: 7600

• SQLSTATE: 22000

• Error cause: The vector dimensions are inconsistent. All vectors must have the same dimension.

• Solution: Check the vector dimension definition in the table definition and rebuild the vector index.

OBE-00932:array type mismatch found between definition(%.*s) and data(%.*s)

• OceanBase error code: 7602

• SQLSTATE: 22000

• Error cause: The array types do not match.

• Solution: Check the array definition in the table to ensure that the inserted data type matches the definition. Use type conversion functions if necessary.

OBE-00933:SQL command not properly ended

• OceanBase error code: 5607

• SQLSTATE: HY000

• Error cause: The SQL command is not properly terminated.

OBE-00934:group function is not allowed here

• OceanBase error code: 5694

• SQLSTATE: HY000

• Error message: The GROUP function is not supported here.

OBE-00937: not a single-group group function

• OceanBase error code: 5853

• SQLSTATE: HY000

• Error message: The function is not a single-group GROUP function.

OBE-00938: not enough arguments for function

• OceanBase error code: 5774

• SQLSTATE: HY000

• Error message: The function has insufficient arguments.

OBE-00939: too many arguments for function

• OceanBase error code: 5683

• SQLSTATE: HY000

• Error message: The function has too many arguments.

OBE-00942: table or view \'%s.%s\'does not exist

• OceanBase error code: 5019

• SQLSTATE: 42S02

• Error message: The table or view does not exist. For OceanBase Database V2.2.70 and later, role-based privileges are introduced. If the current role does not have the SELECT privilege on a table or view, this error will also be returned.

• Solution: Check your SQL statement spelling. Specifically, for OceanBase Database V2.2.70 and later, check the privileges of the current role.

Related issues:

• OBServer restart failed, error code 5019

OBE-00942: table or view '%.*s' does not exist

• OceanBase error code: 5201

• SQLSTATE: 42S02

• Cause: The table or view does not exist. For OceanBase Database V2.2.70 and later, role-based privileges have been introduced. If the current role does not have the SELECT privilege on a table or view, this error will also be returned.

• Solution: Check your SQL syntax. Specifically, for OceanBase Database V2.2.70 and later, verify the privileges of the current role.

Related issues:

• Insufficient PL privileges, error code OBE-00942
• Regular users cannot obtain object DDL via dbms_metadata.get_ddl() in Oracle-compatible mode, error code OBE-00942
• Error when calling a stored procedure across users
• Can execute a stored procedure without execution privileges
• Object privileges lost after re-creating an object in Oracle-compatible mode
• Object privileges lost after creating an object using CREATE OR REPLACE in Oracle-compatible mode

OBE-00947: not enough values

• OceanBase error code: 5614

• SQLSTATE: HY000

• Cause: Insufficient values.

OBE-00955: name is already used by an existing object

• OceanBase error codes: 5331, 5834

• SQLSTATE: HY000

• Cause: The name is already used by an existing object.

Related issues:

• Table already exists during creation, error code OBE-00955

OBE-00957: duplicate column name

• OceanBase error code: 4228

• SQLSTATE: 42000

• Cause: Column name duplicate.

OBE-00959: tablespace '%.*s' does not exist

• OceanBase error code: 4354

• SQLSTATE: HY000

• Cause: The tablespace does not exist.

OBE-00964: table name not in FROM list

• OceanBase error code: 5490
• SQLSTATE: 42000
• Cause: The table name is not in the FROM list.
• Solution: Ensure the input name is a valid table name and is included in the FROM list.

OBE-00969: missing ON keyword

• OceanBase error code: 5370

• SQLSTATE: HY000

• Cause: The ON keyword is missing.

OBE-00972: identifier \'%.*s\' is too

• OceanBase error code: 5179

• SQLSTATE: 42000

• Cause: The specified identifier exceeds the limit.

• Solution: Set the byte count of the specified identifier within the limit.

OBE-00976: Specified pseudo column or operator not allowed here

• OceanBase error code: 5763

• SQLSTATE: HY000

• Cause: The LEVEL, PRIOR, ROWNUM, CONNECT_BY_ROOT, CONNECT_BY_ISLEAF, or CONNECT_BY_ISCYCLE keywords are not allowed at this position.

• Solution: Remove the LEVEL, PRIOR, ROWNUM, CONNECT_BY_ROOT, CONNECT_BY_ISLEAF, or CONNECT_BY_ISCYCLE.

OBE-00979: not a GROUP BY expression

• OceanBase error code: 5218

• SQLSTATE: 42000

• Error cause: Not a GROUP BY expression.

OBE-00980: synonym translation is no longer valid

• OceanBase error code: 5330

• SQLSTATE: HY000

• Error cause: The synonym was not translated into a valid target object. This may be due to one of the following reasons:

  • The target schema does not exist.

  • The target object does not exist.

  • The synonym specifies an incorrect database link.

  • The synonym is not version-controlled, but a version-controlled target object is specified.

• Solution: Modify the synonym definition to point it to a valid target object.

OBE-00984: column not allowed here

• OceanBase error code: 5942

• SQLSTATE: HY000

• Error cause: This column is not allowed for insertion here.

OBE-00988: missing or invalid password(s)

• OceanBase error code: 5887

• SQLSTATE: HY000

• Error cause: Incorrect password.

OBE-00989: Cursor Variable in record, object, or collection is not supported by this release

• OceanBase error code: 9811
• SQLSTATE: HY000
• Error cause: The current version does not support nested cursor variables within records, objects, or collections.
• Solution: Avoid nesting cursor structures.

OBE-00990: missing or invalid privilege

• OceanBase error code: 5892

• SQLSTATE: HY000

• Error cause: The specified privilege name is incorrect or does not exist.

• Solution: Check the spelling and case of the privilege name. Separate multiple privileges with commas.

OBE-00998: must name this expression with a column alias

• OceanBase error code: 5872

• SQLSTATE: HY000

• Cause: This expression must be named with a column alias.