OBE-00000 to OBE-00999

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

• OceanBase error code: 5780

• SQLSTATE: HY000

• Error cause: Normal exit.

OBE-00000: parallel_max_servers downgraded from %ld to %ld due to insufficient CPU resources. deprecated

• OceanBase error code: 5781

• SQLSTATE: HY000

• Error 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

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

• SQLSTATE: 23000

• 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 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-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: Remove the recursive SQL statement or the recursive trigger.

OBE-00051: timeout occurred while waiting for a resource

• OceanBase error code: 5848

• SQLSTATE: HY000

• Error cause: Usually, this error occurs because of a dead instance.

• Solution: Check if there are 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 parameters for the %s call are invalid.

OBE-00060: deadlock detected while waiting for resource

• OceanBase error code: 4101

• SQLSTATE: HY000

• Error cause: A deadlock is 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 is failed to be added during the update operation. This error code is returned to the upper layer and the operation is retried.
• Solution: 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: The query times 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
• Error cause: The memory allocation fails.
  • The physical memory is exhausted.
  • The allocated memory exceeds 4 GB.
  • The memory usage of the CTX, tenant, or server reaches the upper limit.
• Solution: Contact technical support for assistance.

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

• OceanBase error code: 4016
• SQLSTATE: HY000
• Error cause: Internal error code.
• Solution: Internal error code. Contact technical support engineers for assistance.

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

• OceanBase error code: 4377
• SQLSTATE: HY000
• Error 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 is discontinuous, causing a failure and prompting a retry.

• Solution: In most cases, a retry will succeed. If failures persist, contact OceanBase technical support for assistance.

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

• OceanBase error code: 5065
• SQLSTATE: HY000
• 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
• Cause: The SQL statement sequence is invalid.
• Solution: This is an internal error code. Please contact technical support for assistance.

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

• OceanBase error code: 9765

• SQLSTATE: HY000

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

• Solution: Check the object type and adjust it as needed.

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

• OceanBase Database error code: 9784

• SQLSTATE: HY000

• Error reason: A cursor attribute is applied to a non-cursor object.

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

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

• OceanBase error code: 4410

• SQLSTATE: HY000

• Error reason: During the process of selecting the source for migration or rebuild, the log stream replica on the destination is not in the Learner List. This may be because the log stream replica on the destination has been deleted.

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

OBE-00600: arbitration service does not exist

• OceanBase error code: 4747

• SQLSTATE: HY000

• 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 reason: The cluster already has a valid arbitration service address.

• Solution: A cluster does not support configuring multiple arbitration services simultaneously.

EOBE-00600: wait degration finished timeout

• OceanBase error code: 4751

• SQLSTATE: HY000

• Error reason: The tenant degradation failed to complete within the specified time when stopping the server.

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

OBE-00600: unknown SET option '%s'

• OceanBase error code: 4764
• SQLSTATE: HY000
• Error reason: An unknown SET option was specified when setting parameters.
• Solution: Check whether the options specified in the SET statement are correct and ensure that there are 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

• 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

• Cause: When performing service_name-related O&M operations (for example, creating or deleting a service_name) to notify each OBServer node for effect, some servers fail.

• Solution: Wait for a while. 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, you must ensure the tenant is a primary tenant. If the current tenant is no longer the primary tenant, it is a proxy routing error.

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

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 this service_name: ALTER SYSTEM START SERVICE service_name TENANT = tenant_name;.

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

• OceanBase error code: 5415

• SQLSTATE: 22032

• Error cause: Internal error code.

• Solution: Internal error code. Please contact technical support engineers for assistance.

OBE-00600: Invalid JSON character data provided to function

• OceanBase error code: 5416

• SQLSTATE: 22032

• Error cause: Internal error code.

• Solution: Internal error code. Please contact technical support engineers 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

• Error cause: Internal error code.

• Solution: Internal error code. Please contact technical support engineers for assistance.

OBE-00600: Cannot CAST value to JSON

• OceanBase error code: 5418

• SQLSTATE: 22032

• Error cause: Internal error code.

• Solution: Internal error code. Please contact technical support engineers for assistance.

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

• OceanBase error code: 5419

• SQLSTATE:22032

• Error 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

• Error 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

• Error 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

• Error 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

• Error 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 was 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: -5703, Add index failed

• OceanBase error code: 5703

• SQLSTATE: HY000

• Error reason: Failed to add an index.

• Solution: Check whether the index is valid. You can try deleting it and then creating it again.

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: 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: -7109, transfer system error

• OceanBase error code: 7109

• SQLSTATE: HY000

• Error 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

• Error cause: The member list of the log streams at the source and destination does not match 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 these tasks to complete.

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

• OceanBase Database error code: 7111

• SQLSTATE: HY000

• Error reason: During a lock operation, the actual lock holder does not match the expected holder.

• Solution: Contact OceanBase Technical Support for assistance.

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

• OceanBase Database error code: 7112

• SQLSTATE: HY000

• Error reason: When the member list is changed, the transfer SCN is too small.

• Solution: Contact OceanBase 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
• Error reason: The binary geometry function is given two geometries of different SRIDs: %u and %u, which should have been identical. The geometries passed as parameters to spatial functions must have the same SRID.

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
• Error reason: The geometry function %s is called with unsupported argument types.

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

• OceanBase error code: 7203
• SQLSTATE: HY000
• Error reason: 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 cause: 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 cause: 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 cause: 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 cause: The centroid cannot be calculated because the geometry in 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 cause: A geometry overlay calculation error occurred because 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 in calculating the 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
• Error message: The geometry byte string must be little-endian.

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 %s value is a geometry of unexpected type %s in %s.

OBE-00600: Cannot parse the spatial reference system definition for SRID %u.

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

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

• 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: There is no spatial reference system with SRID %u.

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

• 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: The 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
• Cause: The function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which has not been defined.

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: There is no spatial reference system with SRID %u.

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: There is no spatial reference system with SRID %u. The axis order is unknown.

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

• OceanBase error code: 7224
• SQLSTATE: 22S00
• Cause: The function %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 message: 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 reason: The SRID specification on the column '%s' cannot be changed because there is a spatial index on the column. Please remove the spatial index before altering the SRID specification.

OBE-00600: The spatial index on the column will not be used by the query optimizer since the column does not have an SRID attribute. The spatial index on the 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 reason: The spatial index on the column '%s' 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.

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: The 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 message: The mandatory attribute %s is missing.

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

• OceanBase error code: 7232
• SQLSTATE: SR006
• Error message: 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, and cannot 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, and cannot 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 reason: There is already a spatial reference system with SRID %u.

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 reason: There is already a spatial reference system with SRID %u.

OBE-00600: SRID 0 is not modifiable

• OceanBase error code: 7237
• SQLSTATE: SR000
• Error reason: 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 the upgrade process, SRS 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 reason: 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 reason: 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 message: The function %s is defined only for geospatial reference systems, but one of its parameters has an SRID of %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 message: The 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: Spatial indexes cannot be primary or unique indexes.

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 reason: The index type %s is not supported for spatial indexes.

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
• Cause: The 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.

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.The 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
• Cause: The 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.

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 message: 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 when specified in SRS angular units.

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

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

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

• OceanBase error code: 7254
• SQLSTATE: 22S00
• Error cause: 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 cause: Conversions from SRID %u are not supported. The spatial reference system does not have a 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 cause: 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 reason: A functional index cannot be created 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 cause: 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 function %s has SRID 0 and does not specify a length unit, 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 reason: The conversion from %s to %s is invalid. The direction of a 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
• Cause: The function %s has parameters %u and %u that are geometric shapes with different SRIDs. All geometric shapes 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: The longitude %f is out of the range of the 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: The latitude %f is out of the range of the 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
• Error cause: Invalid argument error, %s in function %s.

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

• OceanBase error code: 7269
• SQLSTATE: HY000
• Error cause: Out-of-range error, %s in function %s.

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

• OceanBase error code: 7270
• SQLSTATE: HY000
• Error cause: Overflow error, %s in function %s.

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

• OceanBase error code: 7271
• SQLSTATE: HY000
• Error cause: Range error, %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: Runtime error, %s in function %s.

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

• OceanBase error code: 7275
• SQLSTATE: HY000
• Error cause: Unknown exception, %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: Unable to obtain a geometry object 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
• Cause: The Srid is used incorrectly. The Srid column attribute is only supported in geometry.

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

• OceanBase error code: 7278
• SQLSTATE: HY000
• Cause: The spatial/fulltext/hash index and explicit index order 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
• 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 reason: The provided radius is invalid for the function %s. The radius must be greater than zero.

OBE-00600: Spatial reference system is empty

• OceanBase error code: 7285
• SQLSTATE: SR001
• Error reason: The spatial reference system for SRID %u does not exist.

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

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

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

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

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

• Error reason: The full-text search (FTS) index can only contain columns of the text type.

• Solution: Make sure that the column data type of the FTS index you are trying to create is of the text type, such as VARCHAR, TEXT, or CHAR.

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

• OceanBase Database error code: 9094

• SQLSTATE: HY000

• Error reason: Log stream restore failed. The log stream data to be restored may be corrupted.

• Solution: Contact OceanBase Technical Support for assistance.

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

• OceanBase Database error code: 9095

• SQLSTATE: HY000

• Error reason: No tablet needs to be backed up.

• Solution: Contact OceanBase Technical Support for assistance.

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

• OceanBase Database error code: 9104

• SQLSTATE: HY000

• Error reason: The direct load COMMIT operation failed, possibly because a leader switch occurred.

• Solution: The direct load failed. You can re-import the data.

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

• OceanBase Database error code: 9119

• SQLSTATE: HY000

• Error reason: During a data restore operation, there is insufficient data (log archive or data backup) to restore to the specified point in time. Possible causes include:

  • The data backup set is incomplete, or backup files are missing or corrupted.
  • Log archive files are missing, and the logs required for point-in-time recovery are not continuous.
  • The restore point in time is beyond the range that can be recovered from the backup set and log archive. You may be attempting to restore to a point in time for which no backup or log exists.

• Solution:

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

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

• OceanBase Database error code: 9120

• SQLSTATE: HY000

• Error reason: The specified object (file) cannot be found in the object storage. Possible causes include:

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

• Solution:

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

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

• OceanBase error code: 9129
• SQLSTATE: HY000
• Error reason: The object storage error code. The common cause is the object storage connectivity and compatibility issues.
• Solution: Check the connectivity of the object storage. If the connectivity is normal, contact OceanBase Technical Support for further assistance.

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

• OceanBase Database error code: 9130

• SQLSTATE: HY000

• Error reason: When the object storage performs an Append operation, the provided offset is inconsistent with the current object length.

• Solution: Contact OceanBase Technical Support for assistance.

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

• OceanBase Database error code: 9131

• SQLSTATE: HY000

• Error reason: When the object storage performs an Append operation, if the provided offset is less than the current object length for some reason, a Get request is initiated to read the overlapping content. An error is returned if the content is inconsistent.

• Solution: Contact OceanBase Technical Support for assistance.

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

• OceanBase Database error code: 9132

• SQLSTATE: HY000

• Error reason: Object storage data checksum error.

• Solution: Internal error code. Contact OceanBase Technical Support for assistance.

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

• OceanBase Database error code: 9134

• Error reason: The temporary file has already been sealed.

• Solution: Retry the SQL statement. If the issue persists, contact OceanBase Technical Support for assistance.

OBE-00600: tmp file exceeds disk quota

• OceanBase error code: 9135

• SQLSTATE: HY000

• Error reason: The amount of data written to the disk by the temporary file exceeds the set limit.

• Solution: Check whether the amount of data generated by the SQL statement that triggered the error exceeds the expected value (for example, whether the maximum amount of data written to the disk by the temporary file is 500 GB). If the amount of data is within the expected value, 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 reason: No suitable replica can be found to perform the backup operation.

• Solution: Check the replica status. After confirming that the status is normal, initiate the backup again.

OBE-00600: kms destination is not valid

• OceanBase error code: 9139

• SQLSTATE: HY000

• Error reason: When the transparent encryption feature is enabled for the backup tenant, the key address is not specified or the specified key address is invalid during the restore of the tenant.

• Solution: Specify the correct key address in the restore command, or set the correct key address by using the SET @kms_encrypt_info session variable before restore.

OBE-00600: the object is locked by worm

• OceanBase error code: 9140

• SQLSTATE: HY000

• Error reason: You attempt to delete or modify an object in the object storage that is under retention.

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

OBE-00600: the resource has been released

• OceanBase error code: 9141

• SQLSTATE: HY000

• Cause: The temporary file macroblock 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

• Error reason: You attempt to write a non-idempotent file with the same name to an object storage that is 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 Database 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 storage. If no connectivity issues are found, contact technical support for assistance with troubleshooting.

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

• OceanBase error code: 9148

• SQLSTATE: HY000

• Error reason: The disk quota has exceeded the limit.

• Solution: Clean up 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 Database error code: 9149

• SQLSTATE: HY000

• Error reason: The log_only cleanup policy applies to scenarios where only log archiving is enabled and no data backup is performed. When the log_only cleanup policy exists, data backup paths cannot be configured.

• Solution: Delete the log_only cleanup policy first, and 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 strategy is applicable only to scenarios where log archiving is enabled but no data backup is performed. In scenarios where a data backup path is configured, the cleanup strategy cannot be set to log_only.

• Solution: If you want to use the log_only cleanup policy, you need to delete the configured data backup path first.

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 be performed. Possible reasons include the tenant's status being non-NORMAL (for example, CREATING, RESTORE, etc.) or the tenant not having a cleanup strategy 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 strategy 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 Database error code: 9152

• SQLSTATE: HY000

• Error reason: The backup media is not properly mounted.

• Solution: Mount the backup media correctly and ensure that all OBServer nodes of the tenant initiating the archive/backup/recovery operation can access the same backup media. For more information about how to mount an NFS file system, see Deploy an NFS file system.

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 Database error code: 9153

• SQLSTATE: HY000

• Error reason: The backup media does not support strong consistency for read and write operations.

• Solution: If the backup media is an NFS file system, mount it in the manner specified in Deploy an NFS file system. If the backup media is an object storage service, contact the corresponding service provider.

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

• OceanBase Database error code: 9155

• 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: This error is a normal flow control behavior of the system and does not affect data correctness or business availability. Generally, no action is required. If this error frequently occurs and significantly affects read performance, contact OceanBase Technical Support for assistance.

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

• OceanBase Database error code: 9156

• SQLSTATE: HY000

• Error reason: The log stream is in the garbage collection (GC) state and no longer accepts new write or operation requests.

• Solution: Retry the operation. If it still fails, contact OceanBase Technical Support for assistance.

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

• OceanBase Database error code: 9158

• SQLSTATE: HY000

• Error reason: An unexpected object type was encountered when writing data to the object storage. For example, you tried to perform a Put operation on an Append object or an Append operation on a normal object.

• Solution: Contact Technical Support for assistance.

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

• OceanBase Database error code: 9159

• SQLSTATE: HY000

• Error reason: No backup set is available for restore to the specified point in time.

• 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 Database error code: 9574

• SQLSTATE: HY000

• Error reason: A non-stylesheet document is used as an XSL stylesheet.

• Solution: Check the format and validity of the XSL stylesheet to ensure that there are no format errors, parameter errors, or similar issues.

OBE-00600: Incorrect usage of %s

• OceanBase Database error code: 9751
• SQLSTATE: HY000
• Error reason: The usage is incorrect.
• Solution: Check whether the usage is correct and use it correctly.

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

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

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

• Solution: Check if there is any DDL operation in progress 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 full refresh on the materialized view.

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

• OceanBase Database error code: 11015

• Error reason: The table cannot be updated while it is being created.

• Solution: Wait until table creation is complete, and then retry.

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

• OceanBase Database error code: 11018

• SQLSTATE: HY000

• Error reason: The specified external file cannot be read correctly.

• Solution:

• Verify that the file exists, the file path is correct, and 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 format errors.

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

  • OceanBase Database error code: 11020

  • SQLSTATE: HY000

• Error reason:

• The file may not exist, or you may not have permission to access it.

• The file open mode does not match.

• Solution:

  • Verify that the file path is correct and that the file actually exists on HDFS.

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

• Verify that the HDFS NameNode or DataNode services are running properly.

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

  • OceanBase Database error code: 11021

  • SQLSTATE: HY000

• Error reason: Failed to read the HDFS file.

• Solution:

• Verify that the HDFS DataNode is running properly and that the network connection is normal.

• Check the HDFS logs (HDFS-related logs outside OceanBase Database) to determine whether there are corrupt blocks or unavailable replicas.

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

• OceanBase Database error code: 11042

• SQLSTATE: HY000

• Error reason:

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

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

• Solution:

  • Ensure that the URI format is hdfs://<namenode>:<port>/<path>, including 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 Database error code: 11043

• SQLSTATE: HY000

• Error reason:

• The HDFS URI format is incorrect.

• The Kerberos authentication configuration is incorrect.

• The HDFS client environment is not initialized or is invalid.

  • The HDFS connection parameters are invalid.
  • Failed to set HDFS configuration items.
  • Solution:
  • Check whether the HDFS URI format is correct and whether the HDFS-related configuration is complete.
  • Verify that the files required for Kerberos authentication (keytab, krb5.conf, ticket cache) exist and that the paths are correct.

• Check the network connectivity of the HDFS cluster and ensure that the NameNode is accessible.

  • Check whether the key=value format of custom HDFS configuration items is correct, and ensure that there are no empty keys or values.

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

  • OceanBase Database error code: 11044
  • SQLSTATE: HY000

• Error reason: An attempt was made to use a feature that HDFS has not implemented. The current HDFS storage backend does not support pwrite and append write operations.

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

• OceanBase Database error code: 11045

• SQLSTATE: HY000

• Error reason:

• Duplicate access. For example, an already opened file is opened again.

• Operations such as delete, mkdir, or list are attempted before an HDFS connection is successfully established.

• File deletion failed, possibly because the file does not exist or permissions are insufficient.

  • Directory creation failed.

  • Write failed.

  • Flush failed.

  • Solution:

  • Check HDFS file or directory permissions and verify that the current user has read, write, and delete permissions.

  • Verify that the target path exists and is correctly formatted.

• Verify that the lifecycle management of HDFS components is correct to avoid duplicate access or operations before a connection is established.

  • Check whether the HDFS cluster has sufficient disk space.

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

  • OceanBase Database error code: 11046

  • SQLSTATE: HY000

• Error reason:

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

• The nested structure path is incorrect. For example, addr.city should be accessed, but the DDL specifies addr_city or address.city.

• Under the same external table, some files are missing the column.

  • Format symbol issue. For example, extra spaces, quotation marks, or escape errors before or after the column name.

  • Solution:

  • Verify that data_access_path on external columns or EXTERNAL_FILE_COLUMN_PATTERN in the DDL statement actually exists in the file schema.

  • For nested types, use the actual hierarchical path separator in the file for exact matching.

• If the schemas of files in different partitions differ, create separate external tables for the partitions with missing columns, or set a default value for the column to avoid directly mapping a missing column by path.

  • Correct the invalid 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 Database error code: 11047

  • SQLSTATE: HY000

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

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

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 Database error code: 11049

• SQLSTATE: HY000

• Error reason: The query memory exceeds the limit.

• Solution: Check the value of the query_memory_limit_percentage parameter and verify that the setting is reasonable.

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

• OceanBase Database error code: 11063

• SQLSTATE: HY000

• Error reason: When an external table is created, no file format is specified, or no valid format configuration appears in the DDL statement.

• Solution:

• Add a FORMAT clause to the CREATE EXTERNAL TABLE statement and specify a TYPE that matches the actual files.

• Verify that the TYPE matches the actual file extension and content. For example, if the directory contains .parquet files, use PARQUET instead of CSV.

• If you use CSV, add delimiter, encoding, and other parameters 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 Database error code: 11064

  • SQLSTATE: HY000

• Error reason: When an external table is created, no data access path is specified. This usually means that LOCATION is not configured, is empty, or is not correctly bound to a Location object.

• Solution:

• Add LOCATION to the DDL statement to point to the directory or URL where the external data is stored.

• Verify that the path is accessible to the OceanBase cluster (network, authentication, mount, object storage AK/SK, and other environment-specific settings).

• If a Location object is used, verify that the object has been created and that the current user has read permissions before referencing it in the external table.

  • Use a protocol prefix agreed upon with relevant personnel, such as file://, oss://, or hdfs://, depending on the version 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 because they conflict in meaning.

• 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 are not allowed on the Internal Catalog.

• 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 permission to operate on the catalog.

• Solution: Check whether the user has the permission on the catalog and grant the corresponding operation permission 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 a 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 CCL rule does not exist when you modify or delete it.

• Solution: Use the IF EXISTS keyword or verify that 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 SQL concurrency has reached the upper limit of the CCL rule.

• Solution: Retry after the concurrency decreases, or increase the value of MAX_CONCURRENCY.

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

• OceanBase error code: 11088

• SQLSTATE: HY000

• Cause: The rejection limit %ld has been reached.

• Solution: Check the diagnostic error limit information.

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

• OceanBase Database error code: 11089

• SQLSTATE: HY000

• Error reason: The Location object being accessed is still in use by external tables.

• Solution: Check all external tables that depend on the Location object, verify that the dependencies have been removed, and then retry the operation.

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

• OceanBase Database error code: 11090

• SQLSTATE: HY000

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

• Solution: Check the user's access permissions for the Location object, and grant the user READ permissions by using the GRANT READ ON LOCATION location_name TO user_name WITH GRANT OPTION; command.

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

• OceanBase Database error code: 11091

• SQLSTATE: HY000

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

• Solution: Check whether the specified Location object already exists. Add the OR REPLACE keyword to replace the existing Location object definition with a new one, or create a new Location object.

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

• OceanBase Database error code: 11092

• SQLSTATE: HY000

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

• Solution: Check whether the specified Location object 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 RPC execution of the log service failed due to insufficient resources or network failure at the target node.

• Solution: First, locate the target node logs by using the trace_id, and resolve the issue by combining resource monitoring and parameter adjustment.

• Error reason: A sensitive rule with the same name already exists. This usually occurs when a new sensitive rule added by a DDL statement has the same name as an existing rule.

• Solution: Check whether the specified sensitive rule name already exists, and specify a name that does not exist.

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

• OceanBase Database error code: 11095

• SQLSTATE: HY000

• Error reason: The sensitive rule with the specified name does not exist. This usually occurs when a DDL statement attempts to delete a sensitive rule with a name that does not exist.

• Solution: Check whether the entered sensitive rule name is correct, and enter the correct sensitive rule name.

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

• OceanBase Database error code: 11096

• SQLSTATE: HY000

• Error reason: The column with the specified name is already a sensitive column. This usually occurs when a DDL statement adds or modifies a sensitive rule and attempts to apply a sensitive rule to a column already covered by another sensitive rule.

• Solution: Check whether the specified column is a sensitive column, and choose 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

• Error cause: The sensitive column with the specified name does not exist. This usually occurs when a DDL statement modifies a sensitive rule and attempts to remove a column that is not a sensitive column.

• Solution: Check whether the specified sensitive column exists, and 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

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

• Solution: Check user permissions, and use the GRANT PLAINACCESS ON SENSITIVE RULE '%.*s' TO '%.*s'@'%.*s' command to grant the user the appropriate plain-text access permission.

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

• OceanBase error code: 11099

• SQLSTATE: HY000

• Error cause: Invalid sensitive rule name.

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

OBE-00603: Prepare statement checksum error

• OceanBase error code: 5777

• SQLSTATE: HY000

• Cause: The server session is in an unrecoverable state.

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

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

• OceanBase Database error code: 9829

• SQLSTATE: HY000

• Error reason: An attribute that is not defined on a database object is referenced.

• Solution: Ensure that every database object name referenced is accurate and exists.

• Error reason: In an ALTER TYPE statement, the same attribute name or method name can appear only once.

• Solution: Carefully review and simplify your ALTER TYPE statement to ensure that there are no duplicate names. For complex structure changes, consider splitting the operation into multiple simple, clear statements and executing them sequentially.

• Error reason: Modifications to this attribute are not allowed.

• Solution: The key to resolving this issue is to identify the source of the restriction and use a workaround.

• Error reason: OceanBase Database allows only widening field lengths or constraints, not narrowing them.

• Solution: When you encounter this error, do not force a narrowing operation. Re-evaluate whether narrowing the length is necessary.

• Cause: FORALL INSERT/UPDATE/DELETE is not supported on remote tables.

• Solution: Do not use FORALL INSERT/UPDATE/DELETE on remote tables.

• Cause: The SQL statement contains an error.

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

• OceanBase error code: 5006

• SQLSTATE: 42000

• Cause: The SQL statement contains errors.

• Solution: For the correct SQL statement, refer to the "SQL Reference (Oracle-compatible mode)" of the corresponding OceanBase Database version.

OBE-00902: invalid datatype

• OceanBase Database error code: 5874

• SQLSTATE: HY000

• Cause: The specified data type is invalid.

OBE-00903: invalid table name

• OceanBase Database error code: 5163

• SQLSTATE: 42000

• Cause: The specified table name is invalid.

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

• OceanBase Database error code: 5164

• SQLSTATE: 42000

• Cause: The string contains an invalid identifier.

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

• OceanBase Database error code: 5217

• SQLSTATE: 42S22

• Cause: The string contains an invalid identifier.

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

• OceanBase Database error code: 5211

• SQLSTATE: 42000

• Cause: The string contains an invalid identifier.

• Cause: The specified SQL statement is missing a keyword.

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

• OceanBase Database error code: 5054

• SQLSTATE: 42000

• Error message: The number of arguments is invalid.

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

• OceanBase Database error code: 5198

• SQLSTATE: 42000

• Error message: The specified string length exceeds the maximum supported by the data type. For CHAR and RAW data types, the specified length must be less than or equal to 2,000 bytes. For other data types, the specified length must be less than or equal to 4,000 bytes.

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

OBE-00911: invalid character

• OceanBase Database error code: 9782

• SQLSTATE: HY000

• Error reason: Invalid character.

• Solution: Check and use a valid character set.

OBE-00913: too many values

• OceanBase error code: 5613

• SQLSTATE: HY000

• Cause: Too many values.

OBE-00917: missing comma

• OceanBase Database error code: 7403

• SQLSTATE: 42000

• Error message: A required comma is missing in an INSERT statement or in a list of columns or values in the form ((C,D),(E,F), ...).

• Solution: Correct the syntax by carefully checking the SQL statement for missing or incorrectly used commas.

• Cause: The column definition is ambiguous.

OBE-00925: missing INTO keyword

• OceanBase Database 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.

• Cause: The VALUES keyword is missing.

OBE-00931: missing identifier

• OceanBase Database error code: 5963

• SQLSTATE: HY000

• Cause: The identifier is missing.

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

• OceanBase Database error code: 5083

• SQLSTATE: 22000

• Cause: The data types are inconsistent.

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

• OceanBase Database error code: 7402

• SQLSTATE: 22000

• Error cause: Incompatible data types are used in the SQL query.

• Solution: Check the SQL query statement, identify the inconsistent data types, and use the CAST or CONVERT function to convert the data types to the same type.

• Error reason: 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 Database error code: 7602

• SQLSTATE: 22000

• Error reason: Array types do not match.

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

OBE-00933: SQL command not properly ended

• OceanBase Database error code: 5607

• SQLSTATE: HY000

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

OBE-00934: group function is not allowed here

• OceanBase Database error code: 5694

• SQLSTATE: HY000

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

OBE-00937: not a single-group group function

• OceanBase Database error code: 5853

• SQLSTATE: HY000

• Cause: The specified group function is not a single-group function.

OBE-00938: not enough arguments for function

• OceanBase Database error code: 5774

• SQLSTATE: HY000

• Cause: The function has insufficient arguments.

OBE-00939: too many arguments for function

• OceanBase Database error code: 5683

• OceanBase error code: 5683

• SQLSTATE:HY000

• Cause: The function has too many arguments.

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

• OceanBase Database error code: 5019

• SQLSTATE:42S02

• Error cause: 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 specific 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 permissions of the current role.

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

• OceanBase Database error code: 5201

• SQLSTATE:42S02

• Error cause: 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 specific 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 permissions of the current role.

OBE-00947: not enough values

• OceanBase Database error code: 5614

• OceanBase error code: 5614

• SQLSTATE:HY000

• Error cause: Insufficient values.

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

• OceanBase Database error code: 5331, 5834

• OceanBase error codes: 5331, 5834

• SQLSTATE: HY000

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

OBE-00957: duplicate column name

• OceanBase Database error code: 4228

• SQLSTATE: 42000

• Cause: Column names are duplicate.

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

• OceanBase Database error code: 4354

• SQLSTATE: HY000

• Error cause: The tablespace does not exist.

OBE-00964: table name not in FROM list

• OceanBase Database error code: 5490
• SQLSTATE: 42000
• Error reason: The table name is not in the FROM list.
• Solution: Make sure that the name is a valid table name and is in the FROM list.

OBE-00969: missing ON keyword

• OceanBase Database error code: 5370

• SQLSTATE: HY000

• Error cause: The ON keyword is missing.

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

• OceanBase Database error code: 5179

• SQLSTATE: 42000

• Error cause: The specified identifier exceeds the limit.

• Solution: Set the number of bytes of the specified identifier to a value within the limit.

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

• OceanBase Database error code: 5763

• SQLSTATE: HY000

• Error reason: The LEVEL, PRIOR, ROWNUM, CONNECT_BY_ROOT, CONNECT_BY_ISLEAF, or CONNECT_BY_ISCYCLE keyword is specified in an invalid position.

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

OBE-00979: not a GROUP BY expression

• OceanBase Database error code: 5218

• SQLSTATE: 42000

• Error cause: The expression is not a GROUP BY expression.

OBE-00980: synonym translation is no longer valid

• OceanBase Database error code: 5330

• SQLSTATE: HY000

• 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 invalid database link.

  • The synonym does not specify version control, but specifies a target object that is subject to version control.

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

OBE-00984: column not allowed here

• OceanBase Database error code: 5942

• SQLSTATE: HY000

• Error reason: The column cannot be inserted at this location.

OBE-00988: missing or invalid password(s)

• OceanBase Database error code: 5887

• SQLSTATE: HY000

• Error cause: The password is incorrect.

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

• OceanBase Database error code: 9811
• SQLSTATE: HY000
• Error reason: The current version does not support nested cursor variables in records (record), objects (object), or collections (collection).
• Solution: Avoid using nested cursor structures.

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

• OceanBase Database error code: 5872

• SQLSTATE: HY000

• Error reason: You must use a column alias to name this expression.