OBE-00000 ~ OBE-00999

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

• OceanBase Database error code: 5780

• SQLSTATE: HY000

• Error reason: Normal exit.

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

• OceanBase Database error code: 5781

• SQLSTATE: HY000

• Error reason: Normal exit.

  Note

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

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

• OceanBase Database error code: 5024

• SQLSTATE: 23000

• Error reason: The UPDATE or INSERT statement attempts to insert duplicate keys.

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

Related case:

• The system returns an error when you insert duplicate data. Error code: OBE-00001

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

• OceanBase Database error code: 5595

• SQLSTATE: 23000

• Error reason: The UPDATE or INSERT statement attempts to insert duplicate keys.

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

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

• OceanBase Database error code: 5334

• SQLSTATE: HY000

• Error reason: The UPDATE or INSERT statement attempts to insert duplicate keys.

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

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

• OceanBase Database error code: 5562

• SQLSTATE: HY000

• Error reason: The UPDATE or INSERT statement attempts to insert duplicate keys.

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

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

• OceanBase Database error code: 9697

• SQLSTATE: HY000

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

• Solution: Remove the recursive SQL or the recursive trigger.

OBE-00051: timeout occurred while waiting for a resource

• OceanBase Database error code: 5848

• SQLSTATE: HY000

• Error reason: Usually, this error is caused by a dead instance.

• Solution: Check whether there are dead or unrecovered instances. If so, recover them.

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

• OceanBase Database error code: 6006

• SQLSTATE: HY000

• Error reason: The resource is busy.

• Solution: Retry or increase the timeout.

OBE-00060: invalid argument for %s call

• OceanBase Database error code: 5488
• SQLSTATE: HY000
• Error reason: The arguments for the %s call are invalid.

OBE-00060: deadlock detected while waiting for resource

• OceanBase Database error code: 4101

• SQLSTATE: HY000

• Error reason: A deadlock is detected while waiting for a resource.

• Solution: View the trace file and check the involved transactions and resources. If necessary, retry.

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

• OceanBase Database error code: 6005
• SQLSTATE: HY000
• Error reason: The lock for the update operation fails. Return this error code to the upper layer and retry.
• 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 Database error code: 4012
• SQLSTATE: HY000
• Error reason: The query times out.
• Solution:
  • Optimize the query to reduce the execution time.
  • Set a larger timeout.
  • Contact Technical Support for assistance.

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

• OceanBase Database error code: 4013
• SQLSTATE: HY000
• Error reason: The memory allocation fails.
  • The physical memory is exhausted.
  • The memory allocated in a single operation 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 Database error code: 4016
• SQLSTATE: HY000
• Error reason: 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
• Error reason: OceanBase Database encountered an unexpected internal error, which may be caused by an exception during program execution.
• Solution: Contact OceanBase Technical Support for assistance.

OBE-00060: Migrate tx data not continues

• OceanBase error code: 4408

• SQLSTATE: HY000

• Error reason: The source transaction data table was recycled, and the destination copy found that the transaction data table was discontinuous, resulting in a failure and a retry.

• Solution: Generally, after a retry, it can be successful. If it fails continuously, please contact OceanBase Technical Support for assistance.

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

• OceanBase error code: 5065
• SQLSTATE: HY000
• Error reason: 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 reason: The SQL statement sequence is invalid.
• Solution: Internal error code. Contact OceanBase 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

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

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

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

• OceanBase error code: 4410

• SQLSTATE: HY000

• Error reason: During the selection of the source for migration replication/Rebuild, the log stream replica at the destination is not in the Learner List, which may be because the log stream replica at the destination has been deleted.

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

OBE-00600: arbitration service does not exist

• OceanBase error code: 4747

• SQLSTATE: HY000

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

• Solution: You cannot perform arbitration-related operations without configuring the arbitration service address. You can add the arbitration service address to the cluster by using OCP or executing the alter system add arbitration service'$svr_ip:$svr_port'; statement.

OBE-00600: arbitration service already exist

• OceanBase error code: 4748

• SQLSTATE: HY000

• Error reason: The cluster already has an effective 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 reason: The timeout occurred while waiting for the tenant to be degraded during the Stop Server operation.

• Solution: Initiate the Stop Server command again 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 the parameter.
• Solution: Check whether the option specified in the SET statement is correct and ensure that there are no spelling or syntax errors.

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

• OceanBase error code: 5415

• SQLSTATE: 22032

• Error reason: Internal error code.

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

OBE-00600: Invalid JSON character data provided to function

• OceanBase error code: 5416

• SQLSTATE: 22032

• Error reason: Internal error code.

• Solution: Internal error code. Contact OceanBase 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

• Error reason: Internal error code.

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

OBE-00600: Cannot CAST value to JSON

• OceanBase error code: 5418

• SQLSTATE: 22032

• Error reason: Internal error code.

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

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

• OceanBase error code: 5419

• SQLSTATE: 22032

• Error reason: Internal error code.

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

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

• OceanBase error code: 5420

• SQLSTATE: 22032

• Error reason: Internal error code.

• Solution: Internal error code. Contact OceanBase 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 reason: Internal error code.

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

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

• OceanBase error code: 5423

• SQLSTATE: 22032

• Error reason: Internal error code.

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

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

• OceanBase error code: 5424

• SQLSTATE: 22032

• Error reason: Internal error code.

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

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

• OceanBase error code: 5425

• SQLSTATE: 22032

• Error reason: Internal error code.

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

OBE-00600: Out of range JSON value for CAST

• OceanBase error code: 5426

• SQLSTATE: 22032

• Error reason: Internal error code.

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

OBE-00600: Invalid JSON value for CAST

• OceanBase error code: 5427

• SQLSTATE: 22032

• Error reason: Internal error code.

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

OBE-00600: The JSON document exceeds the maximum depth

• OceanBase error code: 5428

• SQLSTATE: 22032

• Error reason: Internal error code.

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

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

• OceanBase error code: 5430

• SQLSTATE: 22032

• Error reason: Internal error code.

• Solution: Internal error code. Contact OceanBase 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

• Error reason: Internal error code.

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

OBE-40600: JSON_EQUAL used outside predicate

• OceanBase error code: 5448
• SQLSTATE: 42000
• Error reason: JSON_EQUAL is used outside a predicate.
• Solution: Use JSON_EQUAL in a predicate, such as in a CASE expression.

OBE-00600: auto increment service busy

• OceanBase error code: 5794

• SQLSTATE: HY000

• Error reason: Internal error code.

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

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

• OceanBase error code: 5870

• SQLSTATE: HY000

• Error reason: Internal error code.

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

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

• OceanBase error code: 5871

• SQLSTATE: HY000

• Error reason: Internal error code.

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

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

• OceanBase error code: 7124

• SQLSTATE: HY000

• Error reason: The partitions are already balanced when you attempt to execute 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 %s is given two geometries of different SRIDs: %u and %u, which should have been identical. The geometry values passed as arguments 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
• Error reason: The geometry function %s is called with arguments of unsupported 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 occurs 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 reason: An unknown exception is caught in the GIS function %s.

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

• OceanBase error code: 7205
• SQLSTATE: 22023
• Cause: Invalid spatial data provided to function %s. The function is called with a parameter that is not recognized as a valid geometry value.

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

• OceanBase error code: 7206
• SQLSTATE: HY000
• Cause: The geometry has no data in 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
• Cause: Unable to calculate the centroid because the geometry is empty in function %s.

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
• Cause: Geometry overlay calculation error: geometry data is invalid in function %s.

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: Geometry turn info calculation error: 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 analysis procedures of intersection points are interrupted unexpectedly 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 is 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 little endian.

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

• OceanBase error code: 7213
• SQLSTATE: HY000
• Cause: Online operations are not supported on a table with a spatial index.

OBE-00600: Inconsistent intersection points. Inconsistent intersection points

• OceanBase error code: 7214
• SQLSTATE: HY000
• Cause: 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
• Cause: The parameter %s exceeds the maximum number of points in a geometry (%lu) in 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
• Cause: The %s value is a geometry of unexpected type %s in %s.

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

• OceanBase Database Error Code: 7217
• SQLSTATE: SR002
• Cause: The spatial reference system definition for SRID %u cannot be parsed.

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

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

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

• OceanBase Database Error Code: 7219
• SQLSTATE: 01000
• Cause: There is no spatial reference system with 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.

• OceanBase Database Error Code: 7220
• SQLSTATE: 22S00
• Cause: Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian.

OBE-00600: 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 Database Error Code: 7221
• SQLSTATE: SR001
• Cause: 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 is no spatial reference system with SRID %u.

• OceanBase Database Error Code: 7222
• SQLSTATE: SR001
• Cause: There is no spatial reference system with SRID %u.

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

• OceanBase Database Error Code: 7223
• SQLSTATE: 01000
• Cause: There is no spatial reference system with SRID %u. The axis order is unknown.

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

• OceanBase Database Error Code: 7224
• SQLSTATE: 22S00
• 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 Database Error Code: 7225
• SQLSTATE: HY000
• Cause: 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.

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 Database error code: 7226
• SQLSTATE: HY000
• Error reason: The SRID specification on 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 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 Database error code: 7227
• SQLSTATE: HY000
• Error reason: The spatial index on 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: The function is only defined for SRID 0 and SRID 4326. Function %.192s is only defined for SRID 0 and SRID 4326.

• OceanBase Database error code: 7228
• SQLSTATE: 22S00
• Error reason: The function %s is only defined 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 Database error code: 7229
• SQLSTATE: 22S00
• Error reason: %.192s(%.80s) 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 Database error code: 7230
• SQLSTATE: 22S00
• Error reason: %.192s(%.80s) has not been implemented for projected spatial reference systems.

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

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

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

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

OBE-00600: The spatial reference system name cannot be an empty string or start or end with whitespace.

• OceanBase Database error code: 7233
• SQLSTATE: SR006
• Error reason: The spatial reference system name cannot be an empty string or start or end with whitespace.

OBE-00600: The organization name cannot be an empty string or start or end with whitespace.

• OceanBase Database error code: 7234
• SQLSTATE: SR006
• Error reason: The organization name cannot be an empty string or start or end with whitespace.

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

• OceanBase Database error code: 7235
• SQLSTATE: SR004
• Error reason: 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 Database error code: 7236
• SQLSTATE: 01S00
• Error reason: A spatial reference system with SRID %u already exists.

OBE-00600: SRID 0 is not modifiable

• OceanBase error code: 7237
• SQLSTATE: SR000
• 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
• Cause: The SRID range [%u, %u] has been reserved for system use. During upgrade, SRSs in this range may be added, modified, or removed 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
• Cause: Cannot modify SRID %u. At least one column depends on it.

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

• OceanBase error code: 7240
• SQLSTATE: SR006
• 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
• 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
• Cause: Function %s is defined only for geographic spatial reference systems, but one of its arguments is in 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
• Cause: Function %s encountered a polygon that was too large.

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

• OceanBase error code: 7244
• SQLSTATE: HY000
• Cause: 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
• Cause: 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
• Cause: A parameter of function %s contains a geometry with longitude %f, which is out of range. It must be within (%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
• Cause: The function %s contains a geometry with a latitude of %f, which is out of range. It must be within [%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.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
• 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
• Cause: The inverse flattening must be larger than 1.0. If the ellipsoid is a sphere, it must be 0.0.

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

• OceanBase error code: 7251
• SQLSTATE: SR002
• 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
• Cause: The prime meridian must be within (*180, 180] degrees, specified in 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
• 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
• 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
• Cause: 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
• 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: You 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 reason: 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 reason: The geometry passed to function %s is in SRID 0, which does not specify a length unit. The geometry cannot be converted to '%s'.

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

• OceanBase error code: 7260
• SQLSTATE: 22S01
• Error reason: 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 wrong.

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 reason: The function %s contains geometries with different SRIDs: %u and %u. 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 reason: The longitude %f is out of range in function %s. It must be within (%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 reason: The latitude %f is out of range in function %s. It must be within [%f, %f].

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

• OceanBase error code: 7265
• SQLSTATE: HY000
• Error reason: A memory allocation error occurs in function %s: %s.

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

• OceanBase error code: 7266
• SQLSTATE: HY000
• Error reason: A domain error occurs in function %s: %s.

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

• OceanBase error code: 7267
• SQLSTATE: HY000
• Error reason: A length error occurs in function %s: %s.

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

• OceanBase error code: 7268
• SQLSTATE: HY000
• Error reason: An invalid argument error occurs in function %s: %s.

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

• OceanBase error code: 7269
• SQLSTATE: HY000
• Cause: Out of range error in function %s.

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

• OceanBase error code: 7270
• SQLSTATE: HY000
• Cause: Overflow error in function %s.

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

• OceanBase error code: 7271
• SQLSTATE: HY000
• Cause: Range error in function %s.

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

• OceanBase error code: 7272
• SQLSTATE: HY000
• Cause: Underflow error in function %s.

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

• OceanBase error code: 7273
• SQLSTATE: HY000
• Cause: Logic error in function %s.

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

• OceanBase error code: 7274
• SQLSTATE: HY000
• Cause: Runtime error in function %s.

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

• OceanBase error code: 7275
• SQLSTATE: HY000
• Cause: Unknown exception in function %s.

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

• OceanBase error code: 7276
• SQLSTATE: 22003
• Cause: Cannot get a geometry object from the data you send to the GEOMETRY field.

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

• OceanBase error code: 7277
• SQLSTATE: HY000
• Cause: Incorrect usage of srid. The srid column attribute is supported only for geometry.

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

• OceanBase error code: 7278
• SQLSTATE: HY000
• Cause: Incorrect usage of spatial, full-text, and hash indexes and explicit index order.

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

• OceanBase error code: 7280
• SQLSTATE: 42000
• 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
• 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: No unit of measure named '%s' exists.

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
• Cause: The string '%s' is not a valid key %c value pair in 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 radius provided to the function %s is invalid. 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 with the specified 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 "%.192s" provided to the function %s is invalid.

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 "%.192s" provided to the option "%.192s" of the function "%.192s" is invalid.

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

• OceanBase error code: 7288
• SQLSTATE: 22S01
• Error reason: The value %s 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 FTS index can contain only columns of the TEXT type.

• Solution: Make sure that the column data type is TEXT, such as VARCHAR, TEXT, or CHAR.

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

• OceanBase error code: 9129
• SQLSTATE: HY000
• Error reason: The object storage error code. Common causes include object storage connectivity and compatibility issues.
• Solution: Check the connectivity of the object storage. If no connectivity issues are found, contact OceanBase Technical Support for further assistance.

OBE-00600: tmp file exceeds disk quota

• OceanBase error code: 9135

• SQLSTATE: HY000

• Error reason: The data volume of the temporary file exceeds the upper limit.

• Solution: Check whether the SQL statement that caused the current error generates more data than expected (for example, the maximum data volume of the temporary file is 500 GB). If the data volume is within the expected range, you can adjust the temporary_file_max_disk_size parameter to a suitable value.

OBE-00600: kms destination is not valid

• OceanBase error code: 9139

• SQLSTATE: HY000

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

• Solution: Specify the correct key address in the restore command or set the @kms_encrypt_info session variable to the correct key address before restore.

OBE-00600: the object is locked by worm

• OceanBase error code: 9140

• SQLSTATE: HY000

• Error reason: Attempt to delete or modify an object in the retention period on the object storage.

• Solution: Check whether the backup or archive path is configured with a retention strategy 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

• Error reason: The temporary file macroblock is unexpectedly released during use.

• Solution: Contact OceanBase Technical Support for further assistance.

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

• OceanBase error code: 9142

• SQLSTATE: HY000

• Error reason: The object storage is configured with a retention strategy. A non-idempotent file with the same name is written to the object storage.

• Solution: Contact OceanBase Technical Support for further assistance.

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

• OceanBase error code: 9147

• SQLSTATE:HY000

• Error: During physical recovery, the OBServer node cannot access backup set files in the specified backup media.

• Solution: Check the connectivity to the object storage service. If no connectivity issues are found, contact Huawei Cloud support for further assistance.

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

• OceanBase Database error code: 9148

• SQLSTATE:HY000

• The reason is a disk quota limit exceeded.

*Solve: Clear the file 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 strategy applies to scenarios where only log archiving is enabled and no data backup is configured. When the log_only cleanup strategy exists, configuring a data backup path is not allowed.

• Resolution: First, delete the log_only cleanup strategy, and then configure a data backup path.

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

• OceanBase Database error code: 9150

• SQLSTATE:HY000

• Error reason: The log_only cleanup policy applies only to scenarios with only archive logs enabled and without any data backups. If data backups are already configured, setting the cleanup policy to log_only is not allowed.

• Solution: If you want to use the log_only cleanup strategy, you must delete the data backup paths that have been configured.

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

• OceanBase Database error code: 9151

• SQLSTATE:HY000

• Error: Data backup and archive cleanup cannot be performed. Possible reasons include a tenant status other than NORMAL (such as CREATING or RESTORE) or no cleanup strategy is configured for the tenant (for scenarios involving expiration-based cleanup).

• Resolution: Check the status of the tenant. If it is an overdue clearance scenario, make sure that the clearance strategy is properly configured for the tenant.

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

• OceanBase error number: 9152

• SQLSTATE:HY000

• Error: The backup media is not correctly mounted.

• Solution: Correctly mount the backup media and ensure that all OBServer nodes of the tenant initiating the archive, backup, or restore operation can access the same backup media. For more information about how to mount an 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/write consistency of the backup medium is not strong.

• Solution: If the backup medium is an NFS, see Deploy NFS to mount it as instructed. If the backup medium is an object storage, contact the corresponding service provider.

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

• OceanBase error code: 9158

• SQLSTATE:HY000

• Error: When data is written to an object storage, unexpected object types are encountered, such as performing a Put operation on an Append type object or an Append operation 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

• Cause: No backup set is available for restore to the specified time.

• Solution: Specify a different restore point or a different backup set path.

OBE-00600:Incorrect usage of %s

• OceanBase error code: 9751
• SQLSTATE:HY000
• Cause: Use the statement incorrectly.
• Resolution: Check that you are using it properly, and make sure to use it as intended.

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

• OceanBase Error: 11093

• SQLSTATE:HY000

• Cause: The RPC call to Log Service failed. The target node is out of resources or a network fault occurred.

• Solution: Priority tracing through the trace_id to locate target node logs, combined with resource monitoring and parameter adjustments to solve the issue.

OBE-00603: Prepare statement checksum error

• OceanBase Database error code: 5777

• SQLSTATE: HY000

• Error reason: The server session is in an unrecoverable state.

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

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

• OceanBase Database error code: 9752
• SQLSTATE: HY000
• Error reason: 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 Database error code: 5001

• SQLSTATE: 42000

• Error reason: The SQL statement is invalid.

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

• OceanBase error code: 5006

• SQLSTATE: 42000

• Cause: The SQL statement is invalid.

• Solution: For more information, see the SQL reference manual for your OceanBase Database version.

See the following examples:

• Error OBE-00900 occurs when you create a table group with a RANGE or LIST partitioning scheme in an Oracle tenant.
• PL modules in Oracle mode of OceanBase Database do not support the NEW identifier.
• An error occurs when you use the $$PLSQL_UNIT variable in an Oracle tenant.
• Differences between unique constraints and regular constraints in OceanBase Database.

OBE-00902: invalid datatype

• OceanBase error code: 5874

• SQLSTATE: HY000

• Error reason: The data type is invalid.

OBE-00903: invalid table name

• OceanBase error code: 5163

• SQLSTATE: 42000

• Error reason: The table name is invalid.

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

• OceanBase error code: 5164

• SQLSTATE: 42000

• Error reason: The identifier is invalid.

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

• OceanBase error code: 5217

• SQLSTATE: 42S22

• Error reason: The identifier is invalid.

Related issues:

• An OBE-00904 error is returned when you perform operations on a table that contains an INSERT ALL statement in a trigger in Oracle mode.

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

• OceanBase error code: 5211

• SQLSTATE: 42000

• Error reason: The identifier is invalid.

OBE-00905: missing keyword

• OceanBase error code: 5096

• SQLSTATE: HY000

• Error reason: The keyword is missing.

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

• OceanBase error code: 5054

• SQLSTATE: 42000

• Error reason: The number of parameters is invalid.

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

• OceanBase error code: 5198

• SQLSTATE: 42000

• Error reason: The specified string length exceeds the maximum length supported by the data type. Specifically, the specified string length exceeds 2000 for the CHAR and RAW data types, and exceeds 4000 for other data types.

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

OBE-00913: too many values

• OceanBase error code: 5613

• SQLSTATE: HY000

• Error reason: Too many values.

OBE-00917: missing comma

• OceanBase error code: 7403
• SQLSTATE: 42000
• Error reason: A required comma is missing in the INSERT statement or in a column or value list of the form ((C,D),(E,F), ...).
• Solution: Correct the syntax and 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

• Error reason: The column definition is ambiguous.

OBE-00925: missing INTO keyword

• OceanBase error code: 9712

• SQLSTATE: HY000

• Error reason: The INTO keyword is missing when you execute an INSERT statement.

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

OBE-00926: missing VALUES keyword

• OceanBase error code: 5574

• SQLSTATE: HY000

• Error reason: The VALUES keyword is missing.

OBE-00931: missing identifier

• OceanBase error code: 5963

• SQLSTATE: HY000

• Error reason: The identifier is missing.

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

• OceanBase error code: 5083

• SQLSTATE: 22000

• Error reason: The data types are inconsistent.

Related issues:

• An inconsistent datatypes error is returned when you perform type operations in Oracle mode.
• An error with ret_code=-5083 is returned when you update a CLOB column in Oracle mode.
• An inconsistent datatypes error is returned when you sort by a CLOB column.
• An OBE-00932 error is returned when you insert data with inconsistent data types.

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

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

OBE-00933: SQL command not properly ended

• OceanBase error code: 5607

• SQLSTATE: HY000

• Error reason: The SQL command is not properly ended.

OBE-00934: group function is not allowed here

• OceanBase error code: 5694

• SQLSTATE: HY000

• Error reason: The group function is not supported here.

OBE-00937: not a single-group group function

• OceanBase error code: 5853

• SQLSTATE: HY000

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

OBE-00938: not enough arguments for function

• OceanBase error code: 5774

• SQLSTATE: HY000

• Error reason: The number of function parameters is insufficient.

OBE-00939: too many arguments for function

• OceanBase error code: 5683

• SQLSTATE: HY000

• Error reason: The number of function parameters exceeds the maximum.

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

• OceanBase error code: 5019

• SQLSTATE: 42S02

• Error reason: The table or view does not exist. For OceanBase Database V2.2.70 and later, if the current role does not have the SELECT privilege on certain tables or views, this error will also be returned.

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

Related issues:

• OBServer fails to restart, error code 5019

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

• OceanBase error code: 5201

• SQLSTATE: 42S02

• Error reason: The table or view does not exist. For OceanBase Database V2.2.70 and later, if the current role does not have the SELECT privilege on certain tables or views, this error will also be returned.

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

Related issues:

• PL privileges are insufficient, error code OBE-00942
• In Oracle mode, a common user cannot retrieve the DDL statements of an object by calling the dbms_metadata.get_ddl() function, error code OBE-00942
• An error is returned when a stored procedure is called across users.
• A stored procedure can be executed without the EXECUTE privilege.
• In Oracle mode, the privileges on an object are lost after the object is recreated.
• In Oracle mode, the privileges on an object are lost after the object is created by using the CREATE OR REPLACE statement.

OBE-00947: not enough values

• OceanBase error code: 5614

• SQLSTATE: HY000

• Error reason: The number of values is insufficient.

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

• OceanBase error code: 5331, 5834

• SQLSTATE: HY000

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

Related issues:

• The table already exists when you create it, error code OBE-00955.

OBE-00957: duplicate column name

• OceanBase error code: 4228

• SQLSTATE: 42000

• Error reason: The column name is duplicated.

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

• OceanBase error code: 4354

• SQLSTATE: HY000

• Error reason: The tablespace does not exist.

OBE-00964: table name not in FROM list

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

OBE-00969: missing ON keyword

• OceanBase error code: 5370

• SQLSTATE: HY000

• Error reason: The ON keyword is missing.

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

• OceanBase error code: 5179

• SQLSTATE: 42000

• Error reason: The specified identifier exceeds the limit.

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

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

• OceanBase error code: 5763

• SQLSTATE: HY000

• Error reason: The LEVEL, PRIOR, ROWNUM, CONNECT_BY_ROOT, CONNECT_BY_ISLEAF, or CONNECT_BY_ISCYCLE keyword is not allowed at this position.

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

OBE-00979: not a GROUP BY expression

• OceanBase error code: 5218

• SQLSTATE: 42000

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

OBE-00980: synonym translation is no longer valid

• OceanBase error code: 5330

• SQLSTATE: HY000

• Error reason: The synonym cannot be translated to a valid target object. This may be caused by the following reasons:

  • The target schema does not exist.

  • The target object does not exist.

  • The synonym specifies an incorrect database link.

  • The synonym does not support version control but specifies a target object that supports version control.

• Solution: Modify the synonym definition so that the synonym points to a valid target object.

OBE-00984: column not allowed here

• OceanBase error code: 5942

• SQLSTATE: HY000

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

OBE-00988: missing or invalid password(s)

• OceanBase error code: 5887

• SQLSTATE: HY000

• Error reason: The password is invalid.

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

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

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

• OceanBase error code: 5872

• SQLSTATE: HY000

• Error reason: You must specify a column alias for this expression.