7000 to 7999

This range indicates error codes for the election module.

ERROR 7000 (HY000): The log buffer is full

• OceanBase error code: 7000

• Cause: The buffer of the election log module is full. The election module consumes more log bandwidth than expected, there is excessive internal logging, or the log buffer buffer is set too small.

• Solution: An internal error code. Contact technical support for assistance.

ERROR 7001(HY000): The log buffer is empty

• OceanBase error code: 7001

• Cause: This error code is currently unused.

• Solution: An internal error code. Contact technical support for assistance.

ERROR 7002 (HY000): The object is not running

• OceanBase error code: 7002

• Cause: The scheduled task for the election object has not started.

• Solution: An internal error code. Contact technical support for assistance.

ERROR 7003 (HY000): The object is running

• OceanBase error code: 7003

• Cause: The startup process for the election object is called repeatedly.

• Solution: An internal error code. Contact technical support for assistance.

ERROR 7004 (HY000): Election does not reach majority

• OceanBase error code: 7004

• Cause: The number of votes received during the election process does not reach a majority. Election fails without a leader or with an existing leader for re-election. This may be caused by various reasons such as server downtime, network latency, clock skew, high CPU load, etc.

• Solution: An internal error code. Contact technical support for assistance.

ERROR 7005 (HY000): The server is not valid

• OceanBase error code: 7005

• Cause: The network address of the target machine is invalid during leader switchover.

• Solution: An internal error code. Contact technical support for assistance.

ERROR 7006 (HY000): The leader is not valid

• OceanBase error code: 7006

• Cause: The network address of the leader recorded on the OBServer node is invalid.

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

ERROR 7007 (HY000): The leader lease is expired

• OceanBase error code: 7007

• Cause: The election lease has expired. This can occur in either a Follower or Leader, and may be caused by various reasons such as downtime, network latency, clock skew, or high CPU load.

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

ERROR 7010 (HY000): The message is not valid

• OceanBase error code: 7010

• Cause: An invalid election message was received.

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

ERROR 7011 (HY000): The message is not intime

• OceanBase error code: 7011

• Cause: The election message is not within the reception window specified by the protocol. This may be caused by various reasons such as network latency, clock skew, or high CPU load.

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

ERROR 7012 (HY000): The server is not candidate

• OceanBase error code: 7012

• Cause: The switchover target is not in the locally recorded member list, or the sender of the election message determines that it is not in its own member list.

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

ERROR 7013 (HY000): The server is not candidate or voter

• OceanBase error code: 7013

• Cause: The sender of the received vote message is not in the locally recorded member list.

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

ERROR 7014 (HY000): Election protocol error

• OceanBase error code: 7014

• Cause: Protocol error. Network latency and clock skew exceed the assumed upper limits, resulting in dual leaders.

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

ERROR 7015 (HY000): The task run time out of range

• OceanBase error code: 7015

• Cause: The execution time of the election scheduled task deviates significantly from expectations, typically caused by high CPU load.

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

ERROR 7021 (HY000): Last operation has not done

• OceanBase error code: 7021

• Cause: Another leader switchover task is triggered before the previous one is completed.

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

ERROR 7022 (HY000): Current server is not leader

• OceanBase error code: 7022

• Cause: The object being operated on by the leader switchover task is no longer the leader.

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

ERROR 7024 (HY000): There is not prepare message

• OceanBase error code: 7024

• Cause: No valid vote solicitation message was found locally during the vote counting phase of the election.

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

ERROR 7025 (HY000): There is more than one prepare message

• OceanBase error code: 7025

• Cause: The election virtual group receives more than one vote solicitation request from the leader within a single re-election cycle, resulting in an internal encoding error.

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

ERROR 7027 (HY000): Election manager is running

• OceanBase error code: 7027

• Cause: ElectionMgr has been started multiple times.

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

ERROR 7030 (HY000): Election async log init error

• OceanBase error code: 7030

• Cause: Election log initialization failed.

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

ERROR 7031 (HY000): Election waiting leader message

• OceanBase error code: 7031

• Cause: During leader switchover, the old leader did not receive a vote response from the new leader.

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

ERROR 7032 (HY000): Election group not exist

• OceanBase error code: 7032

• Cause: A message about a virtual group was received, but the corresponding virtual group does not exist locally.

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

ERROR 7033 (HY000): unexpected eg_version

• OceanBase error code: 7033

• Cause: A message from a virtual group of an older version was received, possibly due to unstable network latency.

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

ERROR 7034 (HY000): election_group_mgr is running

• OceanBase error code: 7034

• Cause: ObElectionGroupMgr has been started multiple times.

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

ERROR 7035 (HY000): Election manager is not running

• OceanBase error code: 7035

• Cause: ObElectionGroupMgr was used without going through the startup process.

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

ERROR 7036 (HY000): Receive change leader msg and vote msg with same T1 timestamp

• OceanBase error code: 7036

• Cause: The OBServer node receives both re-election and leader-switching messages within the same election cycle.

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

ERROR 7037 (HY000): Receive duplicated prepare/vote msg with same T1 timestamp

• OceanBase error code: 7037

• Cause: The OBServer node receives duplicate re-election/polling requests within the same election cycle.

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

ERROR 7038 (HY000): T1 timestamp is not match

• OceanBase error code: 7038

• Cause: The election message cached in the cache pool has a period that does not match the required one.

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

ERROR 7039 (HY000): not reach majority

• OceanBase error code: 7039

• Cause: The responses received by the replicas do not constitute a majority.

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

ERROR 7040 (HY000): over majority

• OceanBase error code: 7040

• Cause: The responses received by the replicas exceed a majority.

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

ERROR 7041 (HY000): election priority mechanism changed, maybe during upgrading

• OceanBase error code: 7041

• Cause: The election priority mechanism changes during a cross-version upgrade when priorities of different versions are compared.

• Solution: This is an internal error code. It is expected to be reported only during upgrades. Contact technical support for assistance.

ERROR 7109 (HY000): transfer system error

• OceanBase error code: 7109

• Cause: A system error occurred during the transfer.

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

ERROR 7110 (HY000): transfer src ls and dest ls member list not same

• OceanBase error code: 7110

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

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

ERROR 7111 (HY000): lock owner id is not expected

• OceanBase error code: 7111

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

• Solution: Contact technical support for assistance.

ERROR 7112 (HY000): change member list compare ls transfer scn too small

• OceanBase error code: 7112

• Cause: The transport timestamp (SCN) is too small during a member list change operation.

• Solution: Contact technical support for assistance.

ERROR 7113 (HY000): compare tablet transfer seq not match

• OceanBase error code: 7113

• Cause: A sequence mismatch was detected during the underlying TABLET transfer.

• Solution: Contact technical support for assistance.

• Cause: A system error occurred during the transfer operation.

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

ERROR 7114 (HY000): transfer detect active trans

• OceanBase error code: 7114
• Cause: An active transaction was detected during the underlying TABLET transfer in a load balancing task.
• Solution: Enable proactive transaction killing during load balancing. You can view the configuration parameters for transaction killing via _enable_balance_kill_transaction and _balance_kill_transaction_threshold. If the issue persists, contact technical support for assistance.

ERROR 7115 (HY000): transfer src ls does not exist

• OceanBase error code: 7115
• Cause: The specified source file or directory does not exist.
• Solution: Contact technical support engineers for assistance.

ERROR 7116 (HY000): transfer src tablet does not exist

• OceanBase error code: 7116
• Cause: The specified source data table does not exist.
• Solution: Contact technical support engineers for assistance.

ERROR 7117 (HY000): ls need rebuild

• OceanBase error code: 7117
• Cause: During data transmission, it is detected that indexes or metadata need to be rebuilt.
• Solution: Rebuild the indexes or metadata.

ERROR 7118 (HY000): obsolete clog need skip

• OceanBase error code: 7118
• Cause: During garbage collection, outdated clogs are found and need to be skipped.
• Solution: No action required.

ERROR 7119 (HY000): transfer wait transactions end timeout

• OceanBase error code: 7119
• Cause: A timeout occurred while waiting for waiting-to-be-transferred transactions to end.
• Solution: Adjust the timeout period for waiting-to-be-transferred transactions to ensure sufficient waiting time for all transactions to complete.

ERROR 7120 (HY000): tablet GC lock conflict

• OceanBase error code: 7120
• Cause: Tablet garbage collection lock conflict.
• Solution: No action required.

ERROR 7121 (HY000): compare sequence not match

• OceanBase error code: 7121

• Cause: The monotonicly increasing sequence numbers do not match.

• Solution: When the background thread detects that the monotonicly increasing sequence numbers do not match, it will attempt a retry with a new sequence number.

ERROR 7122 (HY000): compare sequence too small

• OceanBase error code: 7122

• Cause: The monotonicly increasing sequence number is smaller than an existing sequence number.

• Solution: If the sequence number of the background thread is smaller than an existing one, it means the sequence number has been preempted by another thread. The background thread will then retry.

ERROR 7123 (HY000): transfer cannot start

• OceanBase error code: 7123

• Cause: Load balancing cannot be started.

• Solution: RS will reschedule the transfer for retry. If the error persists, contact technical support for troubleshooting.

ERROR 7124 (HY000): partitions are already balanced, %s

• OceanBase error code: 7124

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

ERROR 7126(HY000): compare tablet reorganization scn not match

• OceanBase error code: 7126

• Cause: The reorganization SCN of tablets does not match. This may occur when tablets change after a transfer or split.

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

ERROR 7201 (HY000): 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
• Compatible MySQL error code: 3033

ERROR 7202(HY000): Calling geometry function with unsupported types of arguments.Calling geometry function %s with unsupported types of arguments

• OceanBase error code: 7202
• Compatible MySQL error code: 3034

ERROR 7203(HY000): Unknown GIS error occurred in function.Unknown GIS error occurred in function %s

• OceanBase error code: 7203
• Compatible MySQL error code: 3035

ERROR 7204(HY000): Unknown exception caught in GIS function.Unknown exception caught in GIS function %s

• OceanBase error code: 7204
• Compatible MySQL error code: 3036

ERROR 7205(22023): Invalid GIS data provided to function.Invalid GIS data provided to function %s

• OceanBase error code: 7205
• Compatible MySQL error code: 3037

ERROR 7206(HY000): The geometry has no data in function.The geometry has no data in function %s

• OceanBase error code: 7206
• Compatible MySQL error code: 3038

ERROR 7207(HY000): 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
• Compatible MySQL error code: 3039

ERROR 7208(HY000): 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
• Compatible MySQL error code: 3040

ERROR 7209(HY000): 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
• Compatible MySQL error code: 3041

ERROR 7210(HY000): Analysis procedures of intersection points interrupted unexpectedly in function.Analysis procedures of intersection points interrupted unexpectedly in function %s

• OceanBase error code: 7210
• Compatible MySQL error code: 3042

ERROR 7211(HY000): Unknown exception thrown in function.Unknown exception thrown in function %s

• OceanBase error code: 7211
• Compatible MySQL error code: 3043

ERROR 7212(HY000): Geometry byte string must be little endian

• OceanBase error code: 7212
• Compatible MySQL error code: 3055

ERROR 7213(HY000): Do not support online operation on table with GIS index

• OceanBase error code: 7213
• Compatible MySQL error code: 3060

ERROR 7214(HY000): Inconsistent intersection points.Inconsistent intersection points

• OceanBase error code: 7214
• Compatible MySQL error code: 3122

ERROR 7215(HY000): 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
• Compatible MySQL error code: 3134

ERROR 7216(22S01): value is a geometry of unexpected type.%.64s value is a geometry of unexpected type %.64s in %.64s

• OceanBase error code: 7216
• Compatible MySQL error code: 3516

ERROR 7217(SR002): 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
• Compatible MySQL error code: 3517

ERROR 7218(SR003): 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
• Compatible MySQL error code: 3518

ERROR 7219(01000): There's no spatial reference system with SRID.There's no spatial reference system with SRID %u

• OceanBase error code: 7219
• Compatible MySQL error code: 3519

ERROR 7220(22S00): 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
• Compatible MySQL error code: 3520

ERROR 7221(SR001): 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
• Compatible MySQL error code: 3521

ERROR 7222(SR001): There's no spatial reference system with SRID.There's no spatial reference system with SRID %u

• OceanBase error code: 7222
• Compatible MySQL error code: 3548

ERROR 7223(01000): 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
• Compatible MySQL error code: 3565

ERROR 7224(22S00): 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
• Compatible MySQL error code: 3618

ERROR 7225(HY000): 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
• Compatible MySQL error code: 3643

ERROR 7226(HY000): 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
• Compatible MySQL error code: 3644

ERROR 7227(HY000): 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
• Compatible MySQL error code: 3674

ERROR 7228(22S00): 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
• Compatible MySQL error code: 3682

ERROR 7229(22S00): 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
• Compatible MySQL error code: 3704

ERROR 7230(22S00): 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
• Compatible MySQL error code: 3705

ERROR 7231(SR006): Missing mandatory attribute.Missing mandatory attribute %s

• OceanBase error code: 7231
• Compatible MySQL error code: 3708

ERROR 7232(SR006): Multiple definitions of attribute.Multiple definitions of attribute %s

• OceanBase error code: 7232
• Compatible MySQL error code: 3709

ERROR 7233(SR006): The spatial reference system name can't be an empty string or start or end with whitespace

• OceanBase error code: 7233
• Compatible MySQL error code: 3710

ERROR 7234(SR006): The organization name can't be an empty string or start or end with whitespace

• OceanBase error code: 7234
• Compatible MySQL error code: 3711

ERROR 7235(SR004): There is already a spatial reference system with SRID.There is already a spatial reference system with SRID %u

• OceanBase error code: 7235
• Compatible MySQL error code: 3712

ERROR 7236(01S00): There is already a spatial reference system with SRID.There is already a spatial reference system with SRID %u

• OceanBase error code: 7236
• Compatible MySQL error code: 3713

ERROR 7237(SR000): SRID 0 is not modifiable

• OceanBase error code: 7237
• Compatible MySQL error code: 3713

ERROR 7238(01S01): 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
• Compatible MySQL error code: 3715

ERROR 7239(SR005): 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
• Compatible MySQL error code: 3716

ERROR 7240(SR006): Invalid character in attribute.Invalid character in attribute %s

• OceanBase error code: 7240
• Compatible MySQL error code: 3717

ERROR 7241(SR006): Attribute is too long.Attribute %s is too long. The maximum length is %u characters

• OceanBase error code: 7241
• Compatible MySQL error code: 3717

ERROR 7242(22S00): 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
• Compatible MySQL error code: 3726

ERROR 7243(22023): 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
• Compatible MySQL error code: 3727

ERROR 7244(HY000): Spatial indexes can't be primary or unique indexes

• OceanBase error code: 7244
• Compatible MySQL error code: 3728

ERROR 7245(HY000): The index type is not supported for spatial indexes.The index type %.20s is not supported for spatial indexes

• OceanBase error code: 7245
• Compatible MySQL error code: 3729

ERROR 7246(22S02): 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
• Compatible MySQL error code: 3731

ERROR 7247(22S03): 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
• Compatible MySQL error code: 3732

ERROR 7248(SR002): 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
• Compatible MySQL error code: 3736

ERROR 7249(SR002): 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
• Compatible MySQL error code: 3737

ERROR 7250(SR002): The inverse flattening must be larger than 1.0, or 0.0 if the ellipsoid is a sphere

• OceanBase error code: 7250
• Compatible MySQL error code: 3738

ERROR 7251(SR002): The angular unit conversion factor must be a positive number

• OceanBase error code: 7251
• Compatible MySQL error code: 3739

ERROR 7252(SR002): The prime meridian must be within (*180, 180] degrees, specified in the SRS angular unit

• OceanBase error code: 7252
• Compatible MySQL error code: 3740

ERROR 7253(22S00): Transformation from SRID is not supported.Transformation from SRID %u is not supported

• OceanBase error code: 7253
• Compatible MySQL error code: 3741

ERROR 7254(22S00): Transformation to SRID is not supported.Transformation to SRID %u is not supported

• OceanBase error code: 7254
• Compatible MySQL error code: 3742

ERROR 7255(22S00): Transformation from SRID %u is not supported. The spatial reference system has no TOWGS84 clause

• OceanBase error code: 7255
• Compatible MySQL error code: 3743

ERROR 7256(22S00): Transformation to SRID %u is not supported. The spatial reference system has no TOWGS84 clause

• OceanBase error code: 7256
• Compatible MySQL error code: 3744

ERROR 7257(42000): Cannot create a functional index on a function that returns a JSON or GEOMETRY value

• OceanBase error code: 7257
• Compatible MySQL error code: 3753

ERROR 7258(HY000): Spatial functional index is not supported

• OceanBase error code: 7258
• Compatible MySQL error code: 3760

ERROR 7259(SU001): 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
• Compatible MySQL error code: 3882

ERROR 7260(22S01): Invalid cast.Invalid cast from %s to %s

• OceanBase error code: 7260
• Compatible MySQL error code: 4032

ERROR 7261(22S04): 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
• Compatible MySQL error code: 4033

ERROR 7262(22S05): 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
• Compatible MySQL error code: 4034

ERROR 7263(22S02): 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
• Compatible MySQL error code: 3616

ERROR 7264(22S03): 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
• Compatible MySQL error code: 3617

ERROR 7265(HY000): Memory allocation error.Memory allocation error: %*.256s in function %s

• OceanBase error code: 7265
• Compatible MySQL error code: 3044

ERROR 7266(HY000): Domain error.Domain error: %*.256s in function %s

• OceanBase error code: 7266
• Compatible MySQL error code: 3045

ERROR 7267(HY000): Length error.Length error: %*.256s in function %s

• OceanBase error code: 7267
• Compatible MySQL error code: 3046

ERROR 7268(HY000): Invalid argument error.Invalid argument error: %*.256s in function %s

• OceanBase error code: 7268
• Compatible MySQL error code: 3047

ERROR 7269(HY000): Out of range error.Out of range error: %*.256s in function %s

• OceanBase error code: 7269
• Compatible MySQL error code: 3048

ERROR 7270(HY000): Overflow error.Overflow error: %*.256s in function %s

• OceanBase error code: 7270
• Compatible MySQL error code: 3049

ERROR 7271(HY000): Range error.Range error: %*.256s in function %s

• OceanBase error code: 7271
• Compatible MySQL error code: 3050

ERROR 7272(HY000): Underflow error.Underflow error: %*.256s in function %s

• OceanBase error code: 7272
• Compatible MySQL error code: 3051

ERROR 7273(HY000): Logic error.Logic error: %*.256s in function %s

• OceanBase error code: 7273
• Compatible MySQL error code: 3052

ERROR 7274(HY000): Runtime error.Runtime error: %*.256s in function %s

• OceanBase error code: 7274
• Compatible MySQL error code: 3053

ERROR 7275(HY000): Unknown exception: %*.384s in function %s

• OceanBase error code: 7275
• Compatible MySQL error code: 3054

ERROR 7276(22003): Cannot get geometry object from data you send to the GEOMETRY field

• OceanBase error code: 7276
• Compatible MySQL error code: 1416

ERROR 7277(HY000): Incorrect usage of srid, srid column attribute only support in geometry

• OceanBase error code: 7277
• Compatible MySQL error code: 1221

ERROR 7278(HY000): Incorrect usage of spatial/fulltext/hash index and explicit index order

• OceanBase error code: 7278
• Compatible MySQL error code: 1221

ERROR 7279(42000): A SPATIAL index may only contain a geometrical type column

• OceanBase error code: 7279
• Compatible MySQL error code: 1687

ERROR 7280(42000): All parts of a SPATIAL index must be NOT NULL

• OceanBase error code: 7280
• Compatible MySQL error code: 1252

ERROR 7281(HY000): The index type is not supported for spatial indexes.The index type %s is not supported for spatial indexes

• OceanBase error code: 7281
• Compatible MySQL error code: 3729

ERROR 7282(SU001): There's no unit of measure.There's no unit of measure named '%s'

• OceanBase error code: 7282
• Compatible MySQL error code: 3902

ERROR 7283(22023): 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
• Compatible MySQL error code: 3560

ERROR 7284(22023): 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
• Compatible MySQL error code: 3706

ERROR 7285(SR001): Spatial reference system is empty

• OceanBase error code: 7285
• Compatible MySQL error code: 3548

ERROR 7286(22023): Invalid option key in function.Invalid option key '%.192s' in function %.192s

• OceanBase error code: 7286
• Compatible MySQL error code: 3558

ERROR 7287(22023): Invalid value for option in function.Invalid value '%.192s' for option '%.192s' in function '%.192s'

• OceanBase error code: 7287
• Compatible MySQL error code: 3559

ERROR 7288(22S01): Unknown WKB type.Unknown WKB type(%d)! Full WKB type number was (%d)

• OceanBase error code: 7288
• Compatible MySQL error code: 3516

ERROR 7402 (22000): Invalid data type for the operation,inconsistent datatypes: expected %s got %s

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

ERROR 7403 (42000): missing comma

• OceanBase error code: 7403
• Cause: A comma is missing or used incorrectly in the SQL statement.
• Solution: Carefully check the SQL statement to locate where the comma is missing or used incorrectly.

ERROR 7404 (42000): invalid xpath expression

• OceanBase error code: 7404
• Cause: The XPath expression is incorrectly formatted or invalid.
• Solution: Check the XPath expression and verify that the XML data is correct.

ERROR 7405 (42000): EXTRACTVALUE cannot extract values of multiple nodes

• OceanBase error code: 7405
• Cause: The EXTRACTVALUE function cannot extract values from multiple nodes.
• Solution: Use another function or redesign the XPATH query statement.

ERROR 7406 (42000): Cannot convert XML fragment to the required datatype

• OceanBase error code: 7406
• Cause: The data type does not match or is invalid when converting an XML fragment to the required data type.
• Solution: Check whether the data type or the XML data is correct.

ERROR 7407 (42000): The specified printing option is invalid

• OceanBase error code: 7407
• Cause: The specified printing option is invalid.
• Solution: Check whether the printing option is correct.

ERROR 7408 (42000): character length specified for XMLSerialize is too small.

• OceanBase error code: 7408
• Cause: The character length of the return type specified when using the XMLSerialize function is too small.
• Solution: Check the character length or data size to ensure that it is large enough to hold all the data.

ERROR 7409 (42000): Given XPATH expression not supported

• OceanBase error code: 7409
• Cause: The XPath expression is not supported.
• Solution: Check whether the XPath expression used is correct and whether the database version supports the use of this XPath expression.

ERROR 7410 (42000): EXTRACTVALUE can only retrieve value of leaf node

• OceanBase error code: 7410
• Cause: When using the EXTRACTVALUE function, you try to extract a value from a non-leaf node.
• Solution: Check whether the XPath expression is correct and ensure that the expression points to a leaf node.

ERROR 7411 (42000): Cannot insert XML fragments

• OceanBase error code: 7411
• Cause: An invalid XML document is being inserted.
• Solution:
  1. Check the XML data: Verify that the XML data to be inserted is complete and complies with XML document specifications.
  2. Use the XMLType data type: You can use the XMLType data type to store XML data in a separate XMLType column.

ERROR 7412 (42000): cannot ORDER objects without MAP or ORDER method

• OceanBase error code: 7412
• Cause: An object does not have a defined MAP or ORDER method when being compared.
• Solution:
  1. Define a MAP or ORDER method: You can define a MAP or ORDER method in the object's definition for use during sorting. The MAP method maps an object to a scalar value, and the ORDER method compares the size of two objects.
  2. Modify the sorting method: If you cannot define a MAP or ORDER method, consider modifying the sorting method to use other sorting approaches, such as sorting by another column.

ERROR 7413 (42000): parameter %d of function XMLELEMENT must be aliased

• OceanBase error code: 7413
• Cause: The nth attribute parameter of the XMLELEMENT() function has no alias.
• Solution:
  1. Check the syntax of the XMLELEMENT() function attributes to ensure it is correct and valid.
  2. Ensure an alias is specified for the attribute parameter of the XMLELEMENT() function.

ERROR 7414 (42000): invalid alteration of datatype

• OceanBase error code: 7414
• Cause: When you attempt to change a data type, the data type is not allowed to be changed or the new data type is invalid.
• Solution:
  1. Check the data type: Verify that the data type to be changed is allowed and that the new data type is valid.
  2. Check the data size: Verify that the data size after the change can be accommodated by the new data type.

ERROR 7415 (42000): invalid modification of columns

• OceanBase error code: 7415
• Cause: You attempt to modify a column or table structure that is not allowed to be modified.
• Solution:
  1. Check the table structure: Verify that the table structure allows the modification.
  2. Check the column attributes: Verify that the column attributes allow the modification.

ERROR 7416 (42000): Expected XML tag , got no content

• OceanBase error code: 7416
• Cause: The XML data is missing tag content.
• Solution:
  1. Check the XML data: Verify that the XML data is correct and all tags have content.
  2. Check the XML format: Verify that the XML format is correct and all tags are correctly nested and closed.

ERROR 7417 (42000): cannot create index on expression with datatype ADT '%.*s'

• OceanBase error code: 7417
• Cause: You attempt to create an index on an expression with an abstract data type (ADT).
• Solution: Check the table structure for the index creation and ensure the table structure does not contain columns of the ADT type.

ERROR 7418 (42000): XML nodes must be updated with valid nodes and of the same type

• OceanBase error code: 7418
• Cause: An invalid node or node type was used as the update value when updating an XML node.
• Solution: Check whether the node type to be updated is correct and ensure that the node types match.

ERROR 7419 (HY000): LOB value does not exist

• OceanBase error code: 7419
• Cause: The LOB value does not exist when you try to access it.
• Solution: Check whether the table or index where the LOB value is located exists or has been deleted, and determine whether the table or index can be restored.

ERROR 7434 (42000): conversion error between the specified unit and standard unit

• OceanBase error code: 7434

• Cause: Unit conversion error.

• Solution: Check the data type and use a valid unit format.

ERROR 7435 (42000): value is out of range

• OceanBase error code: 7435

• Cause: The specified value is out of the range allowed by the data type.

• Solution: Determine the range allowed by the data type and adjust the table definition.

ERROR 7600 (22000): inconsistent dimension: expected %u got %u

• OceanBase error code: 7600

• Cause: The vector dimensions are inconsistent. All vectors must have the same dimensions.

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

ERROR 7601 (HY000): Column '%.*s' cannot be part of VECTOR index

• OceanBase error code: 7601

• Cause: The specified column %.*s does not support creating a vector index.

• Solution: Create a vector index on a column of the Vector type.

ERROR 7602 (22000): array type mismatch found between definition(%.*s) and data(%.*s)

• OceanBase error code: 7602

• Cause: The array types do not match.

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

ERROR 7603 (22000): Vector index memory usage exceeds user defined limit '%d'M

• OceanBase error code: 7603

• Cause: The memory allocated for the vector index is insufficient.

• Solution: If further configuration is required, modify the memstore_limit_percentage parameter. Contact technical support for assistance.

ERROR 7604 (22000): Using the vsag interface returns an error

• OceanBase error code: 7604

• Cause: An error occurred when using the VSAG interface.

• Solution: Contact technical support for assistance.