7000 - 7999

2024-03-05 01:54:26  Updated

These error codes indicate election module errors.

ERROR 7000 (HY000): The log buffer is full

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Note

This error code is introduced since OceanBase Database V4.2.0.

ERROR 7114 (HY000): transfer detect active trans

  • OceanBase error code: 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. You can check whether active transaction killing is enabled by viewing the _enable_balance_kill_transaction and _balance_kill_transaction_threshold parameters. If the error persists, contact OceanBase Technical Support for troubleshooting.

Note

This error code is introduced since OceanBase Database V4.2.0.

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

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

Note

This error code is introduced since OceanBase Database V4.2.0.

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

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

Note

This error code is introduced since OceanBase Database V4.2.0.

ERROR 7117 (HY000): ls need rebuild

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

Note

This error code is introduced since OceanBase Database V4.2.0.

ERROR 7118 (HY000): obsolete clog need skip

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

Note

This error code is introduced since OceanBase Database V4.2.0.

ERROR 7119 (HY000): transfer wait transactions end timeout

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

Note

This error code is introduced since OceanBase Database V4.2.0.

ERROR 7120 (HY000): tablet GC lock conflict

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

Note

This error code is introduced since OceanBase Database V4.2.0.

ERROR 7121 (HY000): compare sequence not match

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

Note

This error code is introduced since OceanBase Database V4.2.1.

ERROR 7122 (HY000): compare sequence too small

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

Note

This error code is introduced since OceanBase Database V4.2.1.

ERROR 7123 (HY000): transfer cannot start

  • OceanBase error code: 7123

  • Cause: The load balancing task cannot be started.

  • Solution: The RootService automatically retries by rescheduling the transfer task. If the system keeps reporting the error, Contact OceanBase Technical Support for troubleshooting.

Note

This error code is introduced since OceanBase Database V4.2.2.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

ERROR 7237(SR000): SRID 0 is not modifiable

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

Note

This error code is introduced since OceanBase Database V4.1.0.

ERROR 7285(SR001): Spatial reference system is empty

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.1.0.

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

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

Note

This error code is introduced since OceanBase Database V4.2.0.

ERROR 7403 (42000): missing comma

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

Note

This error code is introduced since OceanBase Database V4.2.0.

ERROR 7404 (42000): invalid xpath expression

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

Note

This error code is introduced since OceanBase Database V4.2.0.

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 other functions or redesign the XPath expression for the query.

Note

This error code is introduced since OceanBase Database V4.2.0.

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

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

Note

This error code is introduced since OceanBase Database V4.2.0.

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

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

Note

This error code is introduced since OceanBase Database V4.2.0.

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

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

Note

This error code is introduced since OceanBase Database V4.2.0.

ERROR 7409 (42000): Given XPATH expression not supported

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

Note

This error code is introduced since OceanBase Database V4.2.0.

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

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

Note

This error code is introduced since OceanBase Database V4.2.0.

ERROR 7411 (42000): Cannot insert XML fragments

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

Note

This error code is introduced since OceanBase Database V4.2.0.

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

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

Note

This error code is introduced since OceanBase Database V4.2.0.

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

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

Note

This error code is introduced since OceanBase Database V4.2.0.

ERROR 7414 (42000): invalid alteration of datatype

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

Note

This error code is introduced since OceanBase Database V4.2.0.

ERROR 7415 (42000): invalid modification of columns

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

Note

This error code is introduced since OceanBase Database V4.2.0.

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

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

Note

This error code is introduced since OceanBase Database V4.2.0.

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

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

Note

This error code is introduced since OceanBase Database V4.2.0.

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

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

Note

This error code is introduced since OceanBase Database V4.2.0.

ERROR 7419 (HY000): LOB value does not exist

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

Note

This error code is introduced since OceanBase Database V4.2.0.

Contact Us