7000 to 7999

These error codes indicate election module errors.

ERROR 7000 (HY000): The log buffer is full

• Error code in OceanBase Database: 7000

• Cause: The log buffer of the election module is full, the bandwidth usage of the election module exceeds the expectation, too many logs are generated, or the size of the log buffer is too small.

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

ERROR 7001(HY000): The log buffer is empty

• Error code in OceanBase Database: 7001

• Cause: This error code is not in use.

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

ERROR 7002 (HY000): The object is not running

• Error code in OceanBase Database: 7002

• Cause: No scheduled task of the election object is started.

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

ERROR 7003 (HY000): The object is running

• Error code in OceanBase Database: 7003

• Cause: The election object repeatedly calls the startup process.

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

ERROR 7004 (HY000): Election does not reach majority

• Error code in OceanBase Database: 7004

• Cause: The number of votes received during the election does not reach the majority threshold. Election without the leader or re-election with the leader failed due to downtime, network latency, clock offset, or high CPU load.

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

ERROR 7005 (HY000): The server is not valid

• Error code in OceanBase Database: 7005

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

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

ERROR 7006 (HY000): The leader is not valid

• Error code in OceanBase Database: 7006

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

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

ERROR 7007 (HY000): The leader lease is expired

• Error code in OceanBase Database: 7007

• Cause: The election lease of the leader or followers has expired due to downtime, network latency, clock offset, or high CPU load.

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

ERROR 7010 (HY000): The message is not valid

• Error code in OceanBase Database: 7010

• Cause: The received election message is invalid.

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

ERROR 7011 (HY000): The message is not intime

• Error code in OceanBase Database: 7011

• Cause: The election message is not received within the window period specified in the protocol due to network latency, clock offset, or high CPU load.

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

ERROR 7012 (HY000): The server is not candidate

• Error code in OceanBase Database: 7012

• Cause: The object for leader switchover is not in the local member list, or the election message sender determines that the object is not in its member list.

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

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

• Error code in OceanBase Database: 7013

• Cause: The sender of the received voting message is not in the local member list.

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

ERROR 7014 (HY000): Election protocol error

• Error code in OceanBase Database: 7014

• Cause: A protocol error occurred. The network latency or clock offset exceeds the expectation, resulting in two leaders.

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

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

• Error code in OceanBase Database: 7015

• Cause: The scheduled election task is not executed as scheduled due to a high CPU load.

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

ERROR 7021 (HY000): Last operation has not done

• Error code in OceanBase Database: 7021

• Cause: A leader switchover task was triggered before the previous task was completed.

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

ERROR 7022 (HY000): Current server is not leader

• Error code in OceanBase Database: 7022

• Cause: The object of the leader switchover task is no longer the leader.

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

ERROR 7024 (HY000): There is not prepare message

• Error code in OceanBase Database: 7024

• Cause: No valid local canvassing message is found during vote statistics.

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

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

• Error code in OceanBase Database: 7025

• Cause: The virtual group for election received more than one canvassing request from the leader in a re-election cycle, and an internal code error occurred.

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

ERROR 7027 (HY000): Election manager is running

• Error code in OceanBase Database: 7027

• Cause: ElectionMgr is started multiple times.

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

ERROR 7030 (HY000): Election async log init error

• Error code in OceanBase Database: 7030

• Cause: Election log initialization failed.

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

ERROR 7031 (HY000): Election waiting leader message

• Error code in OceanBase Database: 7031

• Cause: During leader switchover, the original leader receives no voting response from the new leader.

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

ERROR 7032 (HY000): Election group not exist

• Error code in OceanBase Database: 7032

• Cause: A message was received from a virtual group that is not in the local list.

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

ERROR 7033 (HY000): unexpected eg_version

• Error code in OceanBase Database: 7033

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

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

ERROR 7034 (HY000): election_group_mgr is running

• Error code in OceanBase Database: 7034

• Cause: ObElectionGroupMgr is started multiple times.

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

ERROR 7035 (HY000): Election manager is not running

• Error code in OceanBase Database: 7035

• Cause: ObElectionGroupMgr is not started.

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

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

• Error code in OceanBase Database: 7036

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

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

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

• Error code in OceanBase Database: 7037

• Cause: The OBServer node receives duplicate re-election or leader switchover messages in the same election cycle.

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

ERROR 7038 (HY000): T1 timestamp is not match

• Error code in OceanBase Database: 7038

• Cause: The cycle of election messages cached in the election message buffer does not meet the expectation.

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

ERROR 7039 (HY000): not reach majority

• Error code in OceanBase Database: 7039

• Cause: The number of responded replicas is insufficient to meet the majority requirement.

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

ERROR 7040 (HY000): over majority

• Error code in OceanBase Database: 7040

• Cause: The number of responded replicas meets the majority requirement.

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

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

• Error code in OceanBase Database: 7041

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

• Solution: This is an internal error code. It is expected that this error is reported only during the upgrade. Contact OceanBase Technical Support for troubleshooting.

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

• Error code in OceanBase Database: 7113
• Cause: When a tablet is transferred, the sequence does not match.
• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 7114 (HY000): transfer detect active trans

• Error code in OceanBase Database: 7114
• Cause: An active transaction is detected when a tablet is transferred during the execution of a load balancing task.
• Solution: Enable active transaction killing during load balancing. Check the settings of the _enable_balance_kill_transaction and _balance_kill_transaction_threshold parameters to determine whether active transaction killing is enabled. If the error persists, contact OceanBase Technical Support for troubleshooting.

Cases:

• Error code 7119 or 7114 is returned during a load balancing task in OceanBase Database V4.2

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

• Error code in OceanBase Database: 7114
• Cause: The specified source file or directory does not exist.
• Solution: Contact OceanBase Technical Support for troubleshooting.

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

• Error code in OceanBase Database: 7116
• Cause: The specified source data table does not exist.
• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 7117 (HY000): ls need rebuild

• Error code in OceanBase Database: 7117
• Cause: The index or metadata needs to be rebuilt during the data transmission.
• Solution: Rebuild the index or metadata.

ERROR 7118 (HY000): obsolete clog need skip

• Error code in OceanBase Database: 7118
• Cause: An outdated clog is found during garbage collection and needs to be skipped.
• Solution: Troubleshooting is not required.

ERROR 7119 (HY000): transfer wait transactions end timeout

• Error code in OceanBase Database: 7119
• Cause: The execution of the transfer timed out due to the wait for transactions to complete.
• Solution: Set a sufficient timeout period for the execution of transfers to make sure that all transactions can be completed before the timeout period elapses.

ERROR 7120 (HY000): tablet GC lock conflict

• Error code in OceanBase Database: 7120
• Cause: Lock contention occurred during tablet garbage collection.
• Solution: Troubleshooting is not required.

ERROR 7121 (HY000): compare sequence not match

• Error code in OceanBase Database: 7121

• Cause: The monotonically increasing sequence number does not match.

• Solution: The background thread identifies the mismatch of the monotonically increasing sequence number and tries a new sequence number.

ERROR 7122 (HY000): compare sequence too small

• Error code in OceanBase Database: 7122

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

• Solution: If the sequence number of the background thread is smaller than an existing sequence number, the sequence number has been preempted by another thread, and the background thread tries a new sequence number.

ERROR 7123 (HY000): transfer cannot start

• Error code in OceanBase Database: 7123

• Cause: The transfer feature cannot be started.

• Solution: RootService will reschedule the transfer feature. If an error repeatedly occurs, contact OceanBase Technical Support for troubleshooting.

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

• Error code in OceanBase Database: 7201
• Error code in MySQL: 3033

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

• Error code in OceanBase Database: 7202
• Error code in MySQL: 3034

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

• Error code in OceanBase Database: 7203
• Error code in MySQL: 3035

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

• Error code in OceanBase Database: 7204
• Error code in MySQL: 3036

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

• Error code in OceanBase Database: 7205
• Error code in MySQL: 3037

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

• Error code in OceanBase Database: 7206
• Error code in MySQL: 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

• Error code in OceanBase Database: 7207
• Error code in MySQL: 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

• Error code in OceanBase Database: 7208
• Error code in MySQL: 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

• Error code in OceanBase Database: 7209
• Error code in MySQL: 3041

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

• Error code in OceanBase Database: 7210
• Error code in MySQL: 3042

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

• Error code in OceanBase Database: 7211
• Error code in MySQL: 3043

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

• Error code in OceanBase Database: 7212
• Error code in MySQL: 3055

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

• Error code in OceanBase Database: 7213
• Error code in MySQL: 3060

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

• Error code in OceanBase Database: 7214
• Error code in MySQL: 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

• Error code in OceanBase Database: 7215
• Error code in MySQL: 3134

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

• Error code in OceanBase Database: 7216
• Error code in MySQL: 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

• Error code in OceanBase Database: 7217
• Error code in MySQL: 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

• Error code in OceanBase Database: 7218
• Error code in MySQL: 3518

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

• Error code in OceanBase Database: 7219
• Error code in MySQL: 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

• Error code in OceanBase Database: 7220
• Error code in MySQL: 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

• Error code in OceanBase Database: 7221
• Error code in MySQL: 3521

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

• Error code in OceanBase Database: 7222
• Error code in MySQL: 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

• Error code in OceanBase Database: 7223
• Error code in MySQL: 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

• Error code in OceanBase Database: 7224
• Error code in MySQL: 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

• Error code in OceanBase Database: 7225
• Error code in MySQL: 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

• Error code in OceanBase Database: 7226
• Error code in MySQL: 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

• Error code in OceanBase Database: 7227
• Error code in MySQL: 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

• Error code in OceanBase Database: 7228
• Error code in MySQL: 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

• Error code in OceanBase Database: 7229
• Error code in MySQL: 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

• Error code in OceanBase Database: 7230
• Error code in MySQL: 3705

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

• Error code in OceanBase Database: 7231
• Error code in MySQL: 3708

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

• Error code in OceanBase Database: 7232
• Error code in MySQL: 3709

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

• Error code in OceanBase Database: 7233
• Error code in MySQL: 3710

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

• Error code in OceanBase Database: 7234
• Error code in MySQL: 3711

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

• Error code in OceanBase Database: 7235
• Error code in MySQL: 3712

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

• Error code in OceanBase Database: 7236
• Error code in MySQL: 3713

ERROR 7237(SR000): SRID 0 is not modifiable

• Error code in OceanBase Database: 7237
• Error code in MySQL: 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

• Error code in OceanBase Database: 7238
• Error code in MySQL: 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

• Error code in OceanBase Database: 7239
• Error code in MySQL: 3716

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

• Error code in OceanBase Database: 7240
• Error code in MySQL: 3717

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

• Error code in OceanBase Database: 7241
• Error code in MySQL: 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

• Error code in OceanBase Database: 7242
• Error code in MySQL: 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

• Error code in OceanBase Database: 7243
• Error code in MySQL: 3727

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

• Error code in OceanBase Database: 7244
• Error code in MySQL: 3728

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

• Error code in OceanBase Database: 7245
• Error code in MySQL: 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]

• Error code in OceanBase Database: 7246
• Error code in MySQL: 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]

• Error code in OceanBase Database: 7247
• Error code in MySQL: 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

• Error code in OceanBase Database: 7248
• Error code in MySQL: 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

• Error code in OceanBase Database: 7249
• Error code in MySQL: 3737

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

• Error code in OceanBase Database: 7250
• Error code in MySQL: 3738

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

• Error code in OceanBase Database: 7251
• Error code in MySQL: 3739

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

• Error code in OceanBase Database: 7252
• Error code in MySQL: 3740

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

• Error code in OceanBase Database: 7253
• Error code in MySQL: 3741

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

• Error code in OceanBase Database: 7254
• Error code in MySQL: 3742

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

• Error code in OceanBase Database: 7255
• Error code in MySQL: 3743

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

• Error code in OceanBase Database: 7256
• Error code in MySQL: 3744

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

• Error code in OceanBase Database: 7257
• Error code in MySQL: 3753

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

• Error code in OceanBase Database: 7258
• Error code in MySQL: 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'

• Error code in OceanBase Database: 7259
• Error code in MySQL: 3882

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

• Error code in OceanBase Database: 7260
• Error code in MySQL: 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

• Error code in OceanBase Database: 7261
• Error code in MySQL: 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

• Error code in OceanBase Database: 7262
• Error code in MySQL: 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]

• Error code in OceanBase Database: 7263
• Error code in MySQL: 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]

• Error code in OceanBase Database: 7264
• Error code in MySQL: 3617

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

• Error code in OceanBase Database: 7265
• Error code in MySQL: 3044

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

• Error code in OceanBase Database: 7266
• Error code in MySQL: 3045

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

• Error code in OceanBase Database: 7267
• Error code in MySQL: 3046

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

• Error code in OceanBase Database: 7268
• Error code in MySQL: 3047

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

• Error code in OceanBase Database: 7269
• Error code in MySQL: 3048

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

• Error code in OceanBase Database: 7270
• Error code in MySQL: 3049

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

• Error code in OceanBase Database: 7271
• Error code in MySQL: 3050

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

• Error code in OceanBase Database: 7272
• Error code in MySQL: 3051

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

• Error code in OceanBase Database: 7273
• Error code in MySQL: 3052

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

• Error code in OceanBase Database: 7274
• Error code in MySQL: 3053

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

• Error code in OceanBase Database: 7275
• Error code in MySQL: 3054

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

• Error code in OceanBase Database: 7276
• Error code in MySQL: 1416

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

• Error code in OceanBase Database: 7277
• Error code in MySQL: 1221

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

• Error code in OceanBase Database: 7278
• Error code in MySQL: 1221

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

• Error code in OceanBase Database: 7279
• Error code in MySQL: 1687

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

• Error code in OceanBase Database: 7280
• Error code in MySQL: 1252

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

• Error code in OceanBase Database: 7281
• Error code in MySQL: 3729

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

• Error code in OceanBase Database: 7282
• Error code in MySQL: 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

• Error code in OceanBase Database: 7283
• Error code in MySQL: 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

• Error code in OceanBase Database: 7284
• Error code in MySQL: 3706

ERROR 7285(SR001): Spatial reference system is empty

• Error code in OceanBase Database: 7285
• Error code in MySQL: 3548

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

• Error code in OceanBase Database: 7286
• Error code in MySQL: 3558

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

• Error code in OceanBase Database: 7287
• Error code in MySQL: 3559

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

• Error code in OceanBase Database: 7288
• Error code in MySQL: 3516

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

• Error code in OceanBase Database: 7402
• Cause: An incompatible data type is used in the SQL query.
• Solution: Check the SQL query to find the incompatible data type and use the CAST or CONVERT function to convert the incompatible data type to a compatible one.

ERROR 7403 (42000): missing comma

• Error code in OceanBase Database: 7403
• Cause: Commas (,) are missing or incorrectly used in the SQL statements.
• Solution: Check the SQL statements to make sure that no commas (,) are missing or incorrectly used.

ERROR 7404 (42000): invalid xpath expression

• Error code in OceanBase Database: 7404
• Cause: The format of the XPath expression is incorrect or invalid.
• Solution: Make sure that the XPath expression and XML data are correct.

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

• Error code in OceanBase Database: 7405
• Cause: The EXTRACTVALUE function cannot extract values from multiple nodes.
• Solution: Use other functions or redesign the XPath expression for the query.

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

• Error code in OceanBase Database: 7406
• Cause: The XML fragment cannot be converted to the required data type.
• Solution: Make sure that the data type and XML data are correct.

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

• Error code in OceanBase Database: 7407
• Cause: The specified printing option is invalid.
• Solution: Make sure that the specified printing option is valid.

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

• Error code in OceanBase Database: 7408
• Cause: The length specified for the characters returned by the XMLSerialize function is too short.
• Solution: Check the specified character length and data size, and make sure that all data can be accommodated.

ERROR 7409 (42000): Given XPATH expression not supported

• Error code in OceanBase Database: 7409
• Cause: The specified XPath expression is not supported.
• Solution: Make sure that the specified XPath expression is valid and is supported by the current database version.

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

• Error code in OceanBase Database: 7410
• Cause: The EXTRACTVALUE function tried to extract a value from a non-leaf node.
• Solution: Make sure that the specified XPath expression is correct and points to a leaf node.

ERROR 7411 (42000): Cannot insert XML fragments

• Error code in OceanBase Database: 7411
• Cause: The XML file to be inserted is invalid.
• Solution:
  1. Make sure that the XML data to be inserted is complete and conforms to the XML specifications.
  2. Use the XMLType data type, so that you can store the XML data in a separate XMLType column.

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

• Error code in OceanBase Database: 7412
• Cause: The MAP or ORDER method is not specified for the comparison of objects.
• Solution:
  1. Specify the MAP or ORDER method in the definition of an object for sorting. You can use the MAP method to map an object to a scalar value, and use the ORDER method to compare the values of two objects.
  2. If you cannot specify the MAP or ORDER method, you can modify the sorting method. For example, you can use other columns for sorting.

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

• Error code in OceanBase Database: 7413
• Cause: The Nth parameter of the XMLELEMENT () function does not have an alias.
• Solution:
  1. Make sure that the attribute syntax of the XMLELEMENT() function is correct and valid.
  2. Make sure that aliases are specified for attribute parameters of the XMLELEMENT () function.

ERROR 7414 (42000): invalid alteration of datatype

• Error code in OceanBase Database: 7414
• Cause: The data type cannot be changed or the specified new data type is invalid.
• Solution:
  1. Check whether the data type can be changed and make sure that the specified new data type is valid.
  2. Check the size of the data to be changed and make sure that all data can be accommodated in the new data type.

ERROR 7415 (42000): invalid modification of columns

• Error code in OceanBase Database: 7415
• Cause: The column or table schema cannot be modified.
• Solution:
  1. Confirm whether the table schema can be modified before you perform modifications.
  2. Confirm whether the column attributes can be modified before you perform modifications.

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

• Error code in OceanBase Database: 7416
• Cause: The XML data lacks tag content.
• Solution:
  1. Make sure that the XML data is valid and all tags have content.
  2. Make sure that the XML format is valid and all tags are correctly nested and closed.

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

• Error code in OceanBase Database: 7417
• Cause: You tried to create an index on an expression of an abstract data type (ADT).
• Solution: Make sure that the table schema for which you want to create an index does not contain an ADT column.

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

• Error code in OceanBase Database: 7418
• Cause: An invalid XML node or node type is used in the update.
• Solution: Make sure that the new node type matches the node type before the update.

ERROR 7419 (HY000): LOB value does not exist

• Error code in OceanBase Database: 7419
• Cause: The LOB value that you tried to access does not exist.
• Solution: Make sure that the table or index that contains the LOB value exists or can be restored.