OBE-00000 ~ OBE-00999

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

• OceanBase error code: 5780

• SQLSTATE: HY000

• Cause: Normal exit.

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

• OceanBase error code: 5781

• SQLSTATE: HY000

• Cause: Normal exit.

  Note

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

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

• OceanBase error code: 5024

• SQLSTATE: 23000

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

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

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

• OceanBase error code: 5595

• SQLSTATE: 23000

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

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

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

• OceanBase error code: 5334

• SQLSTATE: HY000

• 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

• 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

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

• Solution: Delete the recursive SQL or recursive triggers.

OBE-00051:timeout occurred while waiting for a resource

• OceanBase error code: 5848

• SQLSTATE: HY000

• Cause: Usually caused by 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

• 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
• Cause: The parameters passed to %s are invalid.

OBE-00060:deadlock detected while waiting for resource

• OceanBase error code: 4101

• SQLSTATE: HY000

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

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

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

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

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

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

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

• OceanBase error code: 4013
• SQLSTATE: HY000
• Cause: Memory allocation failed.
  • Physical memory is exhausted.
  • A single memory allocation 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
• Cause: An internal error code.
• Solution: This is an 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
• 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

• Cause: The source transaction data table for migration was reclaimed. During copying to the destination, it was found that the transaction data table was discontinuous, causing a failure and prompting a retry.

• Solution: Retry usually succeeds. 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 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 error code: 9784

• SQLSTATE: HY000

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

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

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

• OceanBase error code: 4410

• SQLSTATE: HY000

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

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

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

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

• Cause: Timeout occurred while waiting for tenant degradation during Stop Server.

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

OBE-00600:unknown SET option '%s'

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

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

• OceanBase error code: 5415

• SQLSTATE: 22032

• Cause: Internal error code.

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

OBE-00600:Invalid JSON character data provided to function

• OceanBase error code: 5416

• SQLSTATE: 22032

• Cause: Internal error code.

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

• Cause: Internal error code.

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

OBE-00600:Cannot CAST value to JSON

• OceanBase error code: 5418

• SQLSTATE: 22032

• Cause: Internal error code.

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

• 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

• 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

• 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

• 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

• 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

• Cause: Internal error code.

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

OBE-00600:Out of range JSON value for CAST

• OceanBase error code: 5426

• SQLSTATE: 22032

• Cause: Internal error code.

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

OBE-00600:Invalid JSON value for CAST

• OceanBase error code: 5427

• SQLSTATE: 22032

• Cause: Internal error code.

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

OBE-00600:The JSON document exceeds the maximum depth

• OceanBase error code: 5428

• SQLSTATE: 22032

• Cause: Internal error code.

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

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

• OceanBase error code: 5430

• SQLSTATE: 22032

• Cause: Internal error code.

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

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

• OceanBase error code: 5431

• SQLSTATE: 22032

• Cause: Internal error code.

• Solution: This is an internal error code. Contact Technical Support for assistance.

OBE-40600:JSON_EQUAL used outside predicate

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

OBE-00600:auto increment service busy

• OceanBase error code: 5794

• SQLSTATE: HY000

• 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

• 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

• Cause: Internal error code.

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

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

• OceanBase error code: 7124

• SQLSTATE: HY000

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

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

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

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

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

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

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

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

• OceanBase error code: 7204
• SQLSTATE: HY000
• 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
• Cause: Invalid spatial data was provided to 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
• 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: 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
• Cause: A geometry overlay calculation error occurred because the 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: A geometry turn information calculation error occurred because the geometry data is invalid in function %s.

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

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

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

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

OBE-00600:Geometry byte string must be little endian

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

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

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

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

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

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

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

• OceanBase error code: 7218
• SQLSTATE: SR003
• 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
• 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.Function %s is only defined for Cartesian spatial reference systems, but one of its arguments is in SRID %u, which is not Cartesian

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

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

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

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

• OceanBase error code: 7222
• SQLSTATE: SR001
• 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
• Cause: There is no spatial reference system with SRID %u. The axis order is unknown.

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

• OceanBase error code: 7224
• SQLSTATE: 22S00
• Error message: %s(%s) is not 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 message: The SRID specification on column '%s' cannot be changed because the column has a spatial index. Delete the spatial index before changing the SRID specification.

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

• OceanBase error code: 7227
• SQLSTATE: HY000
• Error message: The query optimizer will not use the spatial index on column "%s" because 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) is not 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) is not 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
• Cause: The spatial reference system name cannot be an empty string, nor can it start or end with a space.

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

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

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

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

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

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

OBE-00600:SRID 0 is not modifiable

• OceanBase error code: 7237
• SQLSTATE: SR000
• Error message: 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 message: The SRID range [%u, %u] is reserved for system use. During the upgrade, 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 message: 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 message: 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 message: 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: The function %s is defined only for the geospatial reference system, 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
• Cause: 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
• 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 spatial index does not support index type %s.

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

• OceanBase error code: 7246
• SQLSTATE: 22S02
• Error message: The geometry with longitude %f is out of range for the parameter of function %s. 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 geometry with latitude %f is out of range for the parameter of function %s. It must be within the range [%f, %f].

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

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

OBE-00600:The spatial reference system definition for SRID specifies invalid geographic axes. One axis must be NORTH or SOUTH and the other must be EAST or WEST. 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
• Error message: The spatial reference system definition for SRID %u specifies invalid geographic axes '%s' and '%s'. One axis must be NORTH or SOUTH and the other must be EAST or WEST.

OBE-00600:The 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
• 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 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
• 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: 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 message: Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause.

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

• OceanBase error code: 7257
• SQLSTATE: 42000
• Error message: 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 message: Spatial functional indexes are not supported.

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

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

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

• OceanBase error code: 7260
• SQLSTATE: 22S01
• Error message: 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
• Cause: The conversion from %s to %s is invalid. The direction of the polygon ring is incorrect.

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

• OceanBase error code: 7262
• SQLSTATE: 22S05
• Cause: Function %s has parameters %u and %u that are geometries with different SRIDs. All geometries must have the same SRID.

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

• OceanBase error code: 7263
• SQLSTATE: 22S02
• Cause: Longitude %f is out of the range for 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
• Cause: Latitude %f is out of the range for 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
• Cause: Memory allocation error: %s in function %s.

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

• OceanBase error code: 7266
• SQLSTATE: HY000
• Cause: Domain error, %s in function %s.

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

• OceanBase error code: 7267
• SQLSTATE: HY000
• Cause: Length error, %s in function %s.

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

• OceanBase error code: 7268
• SQLSTATE: HY000
• Cause: 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
• 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
• Cause: An overflow error occurred at %s in function %s.

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

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

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

• OceanBase error code: 7272
• SQLSTATE: HY000
• Cause: An underflow error occurred at %s in function %s.

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

• OceanBase error code: 7273
• SQLSTATE: HY000
• Cause: A logic error occurred at %s in function %s.

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

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

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

• OceanBase error code: 7275
• SQLSTATE: HY000
• 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
• 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
• 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: 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
• 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
• Cause: 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
• Cause: No spatial reference system with SRID %u exists.

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

• OceanBase error code: 7286
• SQLSTATE: 22023
• Cause: The option key "%s" in 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 Cause: The value "%s" for the option "%s" in the function "%s" is invalid.

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

• OceanBase error code: 7288
• SQLSTATE: 22S01
• Error Cause: 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 Cause: A full-text search (FTS) index can only contain columns of the TEXT type.

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

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

• OceanBase error code: 9104

• SQLSTATE: HY000

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

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

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

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

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

• OceanBase error code: 9130

• SQLSTATE: HY000

• Cause: The provided offset during an append operation in object storage is inconsistent with the length of the current object.

• Solution: Contact technical support for assistance.

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

• OceanBase error code: 9131

• SQLSTATE: HY000

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

• Solution: Contact technical support for assistance.

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

• OceanBase error code: 9132

• SQLSTATE: HY000

• Cause: Object storage data checksum error.

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

OBE-00600: tmp file exceeds disk quota

• OceanBase error code: 9135

• SQLSTATE: HY000

• Cause: The amount of data from temporary files that has been persisted to disk exceeds the set limit.

• Solution: Check whether the SQL statement causing the error generates more data than expected (for example, the maximum expected data volume for persistent temporary files is 500 GB). If it does, adjust the temporary_file_max_disk_size parameter to an appropriate value.

OBE-00600: kms destination is not valid

• OceanBase error code: 9139

• SQLSTATE: HY000

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

• 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

• Cause: You attempted to delete or modify an object in object storage that is in the retention period.

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

OBE-00600: the resource has been released

• OceanBase error code: 9141

• SQLSTATE: HY000

• Cause: A 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

• Cause: You attempted to write a non-idempotent file with the same name to object storage configured with a retention policy.

• Solution: Contact OceanBase Technical Support for assistance.

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

• OceanBase error code: 9147

• SQLSTATE: HY000

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

• 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

• Cause: The disk quota has been exceeded.

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

• SQLSTATE: HY000

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

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

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

• OceanBase error code: 9150

• SQLSTATE: HY000

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

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

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

• OceanBase error code: 9151

• SQLSTATE: HY000

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

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

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

• OceanBase error code: 9152

• SQLSTATE: HY000

• Cause: The backup medium is not correctly mounted.

• Solution: Mount the backup medium correctly to ensure all OBServer nodes of the tenant initiating the archiving/backup/restoration operation can access the same backup medium. For detailed NFS mounting operations, refer to Deploy NFS.

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

• OceanBase error code: 9153

• SQLSTATE: HY000

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

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

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

• OceanBase error code: 9155

• SQLSTATE: HY000

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

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

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

• OceanBase error code: 9156

• SQLSTATE: HY000

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

• Solution: Retry may succeed. If failures persist, contact OceanBase technical support for assistance.

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

• OceanBase error code: 9158

• SQLSTATE: HY000

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

• Solution: Contact technical support for assistance.

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

• OceanBase error code: 9159

• SQLSTATE: HY000

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

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

OBE-00600:Incorrect usage of %s

• OceanBase error code: 9751
• SQLSTATE: HY000
• Cause: Incorrect usage.
• Solution: Check whether the usage is correct and use it in the correct way.

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

• OceanBase error code: 9808

• SQLSTATE: HY000

• Cause: The table type referenced in the materialized view definition is invalid.

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

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

• OceanBase error code: 9809

• SQLSTATE: HY000

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

• Solution: Check whether any DDL operations are being performed on the base table of the materialized view.

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

• OceanBase error code: 9810

• SQLSTATE: HY000

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

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

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

• OceanBase error code: 11049
• SQLSTATE: HY000
• Cause: The query memory exceeds the limit.
• Solution: Check the value of the query_memory_limit_percentage parameter and confirm whether the setting is reasonable.

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

• OceanBase error code: 11063

• SQLSTATE: HY000

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

• Solution:

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

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

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

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

• OceanBase error code: 11064

• SQLSTATE: HY000

• Cause: The data access path was not specified when creating the external table. This is usually due to the LOCATION parameter being unconfigured, empty, or not correctly bound to a Location object.

• Solution:

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

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

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

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

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

• OceanBase error code: 11081

• SQLSTATE: HY000

• Cause: PARSE_HEADER and SKIP_HEADER cannot be used simultaneously, as they conflict in semantics.

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

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

• OceanBase error code: 11082

• SQLSTATE: HY000

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

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

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

• OceanBase error code: 11083

• SQLSTATE: HY000

• Cause: The user does not have the operation permission for the Catalog.

• Solution: Check whether the user has the Catalog permission and grant the corresponding Catalog 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 user does not have the required privilege on the catalog.

• Solution: Check the privileges on 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 you try to create it.

• Solution: Use the IF NOT EXISTS keyword, or delete the old rule and then recreate it.

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

• OceanBase error code: 11086

• SQLSTATE: HY000

• Cause: The rule does not exist when you try to modify or delete it.

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

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

• OceanBase error code: 11087

• SQLSTATE: HY000

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

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

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

• OceanBase error code: 11088

• SQLSTATE: HY000

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

• Solution: Check the diagnostic error limit information.

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

• OceanBase error code: 11089

• SQLSTATE: HY000

• Cause: The accessed location object is being used by an external table.

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

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

• OceanBase error code: 11090

• SQLSTATE: HY000

• Cause: The specified location object cannot be accessed.

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

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

• OceanBase error code: 11091

• SQLSTATE: HY000

• Cause: The specified location object already exists and cannot be created.

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

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

• OceanBase error code: 11092

• SQLSTATE: HY000

• Cause: The specified location object does not exist.

• Solution: Check if the specified location object exists and specify the correct one.

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

• OceanBase error code: 11093

• SQLSTATE: HY000

• Cause: The log service RPC execution failed due to insufficient resources or network issues at the target node.

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

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

• OceanBase error code: 11094

• SQLSTATE: HY000

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

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

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

• OceanBase error code: 11095

• SQLSTATE: HY000

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

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

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

• OceanBase error code: 11096

• SQLSTATE: HY000

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

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

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

• OceanBase error code: 11097

• SQLSTATE: HY000

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

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

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

• OceanBase error code: 11098

• SQLSTATE: HY000

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

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

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

• OceanBase error code: 11099

• SQLSTATE: HY000

• Cause: The sensitive rule name is invalid.

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

OBE-00603: Prepare statement checksum error

• OceanBase error code: 5777

• SQLSTATE: HY000

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

• Solution: Log in to OceanBase Database again 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 error code: 9829
• SQLSTATE: HY000
• Cause: A property that is not defined on a database object was referenced.
• Solution: Ensure that every name of the referenced database objects is accurate and exists.

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

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

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

• OceanBase error code: 9833
• SQLSTATE: HY000
• Cause: The attribute cannot be modified.
• Solution: The core to resolving this issue is to identify the source of the restriction and adopt a workaround strategy.

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

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

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

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

OBE-00900:invalid SQL statement

• OceanBase error code: 5001

• SQLSTATE: 42000

• Cause: The SQL statement contains errors.

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

• OceanBase error code: 5006

• SQLSTATE: 42000

• Cause: The SQL statement contains errors.

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

OBE-00902:invalid datatype

• OceanBase error code: 5874

• SQLSTATE: HY000

• Cause: The data type is invalid.

OBE-00903:invalid table name

• OceanBase error code: 5163

• SQLSTATE: 42000

• Cause: The table name is invalid.

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

• OceanBase error code: 5164

• SQLSTATE: 42000

• Cause: The string contains an invalid identifier.

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

• OceanBase error code: 5217

• SQLSTATE: 42S22

• Cause: The string contains an invalid identifier.

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

• OceanBase error code: 5211

• SQLSTATE: 42000

• Cause: The string contains an invalid identifier.

OBE-00905:missing keyword

• OceanBase error code: 5096

• SQLSTATE: HY000

• Error message: SQL statement is missing a keyword.

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

• OceanBase error code: 5054

• SQLSTATE: 42000

• Error message: The number of arguments is invalid.

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

• OceanBase error code: 5198

• SQLSTATE: 42000

• Error message: The specified string length exceeds the maximum supported by the data type. Specifically, for the CHAR and RAW data types, the specified length must not exceed 2,000; for other data types, it must not exceed 4,000.

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

• SQLSTATE: HY000

• Error message: Invalid character.

• Solution: Check and use a valid character set.

OBE-00913:too many values

• OceanBase error code: 5613

• SQLSTATE: HY000

• Error message: Too many values.

OBE-00917:missing comma

• OceanBase error code: 7403
• SQLSTATE: 42000
• Error message: A required comma is 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.

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

• OceanBase error code: 5207

• SQLSTATE: 23000

• Cause: The column definition is ambiguous.

OBE-00925:missing INTO keyword

• OceanBase error code: 9712

• SQLSTATE: HY000

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

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

OBE-00926:missing VALUES keyword

• OceanBase error code: 5574

• SQLSTATE: HY000

• Cause: The VALUES keyword is missing.

OBE-00931:missing identifier

• OceanBase error code: 5963

• SQLSTATE: HY000

• Cause: An identifier is missing.

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

• OceanBase error code: 5083

• SQLSTATE: 22000

• Cause: Inconsistent data types.

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

• OceanBase error code: 7402
• SQLSTATE: 22000
• Cause: Incompatible data types were 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.

OBE-00933:SQL command not properly ended

• OceanBase error code: 5607

• SQLSTATE: HY000

• Cause: The SQL command was not terminated correctly.

OBE-00934:group function is not allowed here

• OceanBase error code: 5694

• SQLSTATE: HY000

• Cause: The GROUP function is not supported here.

OBE-00937:not a single-group group function

• OceanBase error code: 5853

• SQLSTATE: HY000

• Cause: It is not a single-group GROUP function.

OBE-00938:not enough arguments for function

• OceanBase error code: 5774

• SQLSTATE: HY000

• Cause: Insufficient function parameters.

OBE-00939: too many arguments for function

• OceanBase error code: 5683

• SQLSTATE: HY000

• Cause: Too many function parameters.

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

• OceanBase error code: 5019

• SQLSTATE: 42S02

• Cause: The table or view does not exist. For OceanBase Database V2.2.70 and later, role-based privileges have been introduced. If the current role does not have the SELECT privilege on a 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 error code: 5201

• SQLSTATE: 42S02

• Cause: The table or view does not exist. For OceanBase Database V2.2.70 and later, role-based privileges have been introduced. If the current role does not have the SELECT privilege on a 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 error code: 5614

• SQLSTATE: HY000

• Cause: Insufficient values.

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

• OceanBase error codes: 5331, 5834

• SQLSTATE: HY000

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

OBE-00957:duplicate column name

• OceanBase error code: 4228

• SQLSTATE: 42000

• Cause: Column names are duplicate.

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

• OceanBase error code: 4354

• SQLSTATE: HY000

• Cause: The tablespace does not exist.

OBE-00964:table name not in FROM list

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

OBE-00969:missing ON keyword

• OceanBase error code: 5370

• SQLSTATE: HY000

• Cause: The ON keyword is missing.

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

• OceanBase error code: 5179

• SQLSTATE: 42000

• Cause: The specified identifier exceeds the limit.

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

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

• OceanBase error code: 5763

• SQLSTATE: HY000

• Cause: The LEVEL, PRIOR, ROWNUM, CONNECT_BY_ROOT, CONNECT_BY_ISLEAF, or CONNECT_BY_ISCYCLE 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

• Cause: It is not a GROUP BY expression.

OBE-00980: synonym translation is no longer valid

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

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

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

OBE-00984: column not allowed here

• OceanBase error code: 5942

• SQLSTATE: HY000

• Cause: This column cannot be inserted here.

OBE-00988: missing or invalid password(s)

• OceanBase error code: 5887

• SQLSTATE: HY000

• Cause: The password is incorrect.

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

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

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

• OceanBase error code: 5872

• SQLSTATE: HY000

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