4000 to 4499

These error codes indicate common errors.

ERROR 4000 (HY000): Common error

• OceanBase error code: 4000

• Cause: A common error occurred.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4001 (HY004): Object type error

• OceanBase error code: 4001

• Cause: The specified object type is invalid.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4003 (42000): Array index out of range

• OceanBase error code: 4003

• Cause: The array index is out of range.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4004 (08S01): Failed to listen to the port

• OceanBase error code: 4004

• Cause: The listener failed to start due to network disconnection.

• Solution: Switch to an idle port and then restart the observer process.

ERROR 4005 (HY000): The object is initialized twice

• OceanBase error code: 4005

• Cause: The object is repeatedly initialized.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4005 (HY000): User '%.*s'@'%.*s' is referenced as a definer account in a stored routine.

• OceanBase error code: 5388

• MySQL error code: 4005

• Cause: An orphan object is generated or inherited during the operation on a user.

• Solution: Verify whether you have required privileges, or drop the corresponding object.

ERROR 4006 (HY000): The object is not initialized

• OceanBase error code: 4006

• Cause: The object is not initialized.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4006 (HY000): Operation %.*s failed for '%.*s'@'%.*s' as it is referenced as a definer account in a stored routine.

• OceanBase error code: 5389

• MySQL error code: 4006

• Cause: An orphan object is generated or inherited during the operation on a user.

• Solution: Drop the corresponding object.

ERROR 4008 (HY000): End of iteration

• OceanBase error code: 4008

• Cause: The iteration has ended.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4009 (58030): IO error

• OceanBase error code: 4009

• Cause: An I/O-related system call, such as a read request or a write request, failed.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4010 (HY000): Wrong RPC command version

• OceanBase error code: 4010

• Cause: The version of the remote procedure call (RPC) command is invalid.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4012 (HY000): Timeout, query has reached the maximum query timeout: %ld(us), maybe you can adjust the session variable ob_query_timeout or query_timeout hint, and try again

• OceanBase error code: 4012

• Cause: The execution timed out.

• Solution:

  • Reduce the amount of time required through performance tuning.

  • Extend the timeout period.

  • Contact OceanBase Technical Support for troubleshooting.

ERROR 4012 (HY000): Task timeout and not executed

• OceanBase error code: 4049

• MySQL error code: 4012

ERROR 4012 (HY000): RPC session not found

• OceanBase error code: 4067

• MySQL error code: 4012

ERROR 4012 (HY000): RPC send error

• OceanBase error code: 4121

• MySQL error code: 4012

ERROR 4012 (HY000): RPC post error

• OceanBase error code: 4122

• MySQL error code: 4012

ERROR 4012 (HY000): IO timeout

• OceanBase error code: 4404

• MySQL error code: 4012

  Note

  • For V4.3.x, this field was introduced in V4.3.3.
  • For V4.2.x, this field was introduced in V4.2.5.

ERROR 4012 (HY000): Timeout

• OceanBase error code: 4664

• MySQL error code: 4012

ERROR 4012 (HY000): Statement is timeout

• OceanBase error code: 6004

• MySQL error code: 4012

ERROR 4012 (25000): Transaction timeout occurred, please rollback the transaction, set the variable ob_trx_timeout to a larger value and then restart the transaction

• OceanBase error code: 6210

• MySQL error code: 4012

ERROR 4012 (25000): Statement timeout occurred, please set the variable ob_query_timeout to a larger value an then restart the statement

• OceanBase error code: 6212

• MySQL error code: 4012

ERROR 4012 (25000): Transaction result isunknown

• OceanBase error code: 6225

• MySQL error code: 4012

ERROR 4012 (25000): transaction rpc timeout

• OceanBase error code: 6230

• MySQL error code: 4012

ERROR 4013 (HY001): No memory or reach tenant memory limit

• OceanBase error code: 4013

• Cause: Memory allocation failed.

  • The physical memory is exhausted.
  • The memory allocated at a time is greater than 4 GB.
  • The memory usage of the context, tenant, and OBServer node reaches the upper limit.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4014 (HY000): Inner state error

• OceanBase error code: 4014

• Cause: An internal status error occurred.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4015 (HY000): System error

• OceanBase error code: 4015

• Cause: An internal error occurred.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4016 (HY000): Internal error

• OceanBase error code: 4016

• Cause: An internal error occurred.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4017 (HY000): Entry already exist

• OceanBase error code: 4017

• Cause:

  The possible causes are described as follows:

  • The current log stream involves an ongoing disaster recovery task and therefore does not support parallel execution.
  • The log stream already has a replica on the server.
  • The replica of the log stream on the server is the same as the target type.
  • A replica already exists on the destination server.

• Solution: Resolve the issue based on the actual business scenario or contact OceanBase Technical Support for troubleshooting.

ERROR 4018 (HY000): Entry not exist

• OceanBase error code: 4018

• Cause: The specified data does not exist.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4019 (HY000): Size overflow

• OceanBase error code: 4019

• Cause: A space overflow occurred.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4020 (HY000): Reference count is not zero

• OceanBase error code: 4020

• Cause: The reference count is not 0.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4021 (HY000): Conflict value

• OceanBase error code: 4021

• Cause: The base library encountered a logic error, generally, a code error.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4022 (HY000): Item not set

• OceanBase error code: 4022

• Cause: No value is specified.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4023 (HY000): Try again

• OceanBase error code: 4023

• Cause: The operation needs to be retried.

• Solution: Retry the operation, or contact OceanBase Technical Support for troubleshooting.

ERROR 4024 (HY000): Buffer not enough

• OceanBase error code: 4024

• Cause: The storage space is insufficient.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4025 (HY000): Partial failed

• OceanBase error code: 4025

• Cause: Partial tasks that were initiated at a time failed.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4026 (02000): Nothing to read

• OceanBase error code: 4026

• Cause: No available data can be read.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4028 (HY000): Log entry not continuous

• OceanBase error code: 4028

• Cause: File IDs are inconsecutive.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4029 (HY000): Schema error

• OceanBase error code: 4029

• Cause: The schema failed to be obtained.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4030 (HY000): Over tenant memory limits

• OceanBase error code: 4030

• Cause: The tenant has insufficient memory.

• Solution: Increase the memory size of the tenant.

ERROR 4031 (HY004): Unknown object

• OceanBase error code: 4031

• Cause: The object is unknown.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4033 (HY000): Serialize error

• OceanBase error code: 4033

• Cause: Serialization failed.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4034 (HY000): Deserialize error

• OceanBase error code: 4034

• Cause: Deserialization failed.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4035 (HY000): Asynchronous IO error

• OceanBase error code: 4035

• Cause: Asynchronous I/O-related system calls failed.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4036 (HY000): Need retry

• OceanBase error code: 4036

• Cause: The operation needs to be retried.

• Solution: Retry the operation, or contact OceanBase Technical Support for troubleshooting.

ERROR 4037 (HY000): Too many sstable

• OceanBase error code: 4037

• Cause: Excessive SSTables are generated, generally due to frequent minor compactions.

• Solution: Scale out the cluster to reduce the load on a single server, or contact OceanBase Technical Support for troubleshooting.

ERROR 4038 (HY000): The observer or zone is not the master

• OceanBase error code: 4038

• Cause: The current partition does not serve as the leader to provide services.

• Solution: Execute the current statement or transaction again.

ERROR 4039 (HY000): Request has killed by sql throttle

• OceanBase error code: 4039

• Cause: Throttling is enabled on SQL execution.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4041 (HY000): Decrypt error

• OceanBase error code: 4041

• Cause: Decryption failed.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4045 (HY000): pushdown status changed

• OceanBase error code: 4045

• Cause: An internal error occurred.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4046 (HY000): Storage schema is not valid

• OceanBase error code: 4046

• Cause: The schema of the storage layer is invalid.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4047 (HY000): Medium compaction info is not valid

• OceanBase error code: 4047

• Cause: The Medium Info is invalid.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4048 (HY000): Not registered

• OceanBase error code: 4048

• Cause: An internal error occurred.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4050 (HY000): Not the object

• OceanBase error code: 4050

• Cause: An object mismatch occurred.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4052 (HY000): Corrupted log entry

• OceanBase error code: 4052

• Cause: The log data retrieved by the read request is invalid due to a hardware or disk error.

• Solution: Contact the database administrator for hardware troubleshooting, or contact OceanBase Technical Support for troubleshooting.

ERROR 4055 (HY000): Invalid entry

• OceanBase error code: 4055

• Cause: An internal status error occurred.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4057 (HY000): Decimal overflow warning

• OceanBase error code: 4057

• Cause: The precision of the input data is out of range.

• Solution: Reduce the precision of the input data.

ERROR 4058 (HY000): Decimal overflow error

• OceanBase error code: 4058

• Cause: The precision of the input data is out of range.

• Solution: Reduce the precision of the input data.

ERROR 4060 (HY000): Divide error

• OceanBase error code: 4060

• Cause: A division error occurred.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4061 (HY000): Not a decimal

• OceanBase error code: 4061

• Cause: The specified object type is invalid.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4062 (HY104): Decimal precision error

• OceanBase error code: 4062

• Cause: A numeric precision error occurred.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4063 (HY000): Empty range

• OceanBase error code: 4063

• Cause: The query range of the LIKE condition failed to be obtained.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4064 (HY000): Session killed

• OceanBase error code: 4064

• Cause: The current session is terminated.

• Solution: Contact the system administrator or database administrator for troubleshooting.

ERROR 4065 (HY000): Log not sync

• OceanBase error code: 4065

• Cause: Replica logs are not synchronized.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4068 (HY000): Invalid log

• OceanBase error code: 4068

• Cause: Logs are invalid.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4070 (HY000): Invalid data

• OceanBase error code: 4070

• Cause: Data is invalid.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4071 (HY000): Already done

• OceanBase error code: 4071

• Cause: The operation has been completed.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4072 (HY000): Operation canceled

• OceanBase error code: 4072

• Cause: The operation has been canceled.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4074 (HY000): Log not aligned

• OceanBase error code: 4074

• Cause: Logs are not aligned.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4075 (HY000): Log entry missed

• OceanBase error code: 4075

• Cause: Logs are not found.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4076 (HY000): Need wait

• OceanBase error code: 4076

• Cause: Waiting is required.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4077 (0A000): Not implemented feature

• OceanBase error code: 4077

• Cause: The feature is not supported.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4080 (HY013): exceed memory limit

• OceanBase error code: 4080

• Cause: An internal error occurred. The size of used memory exceeds the upper limit.

• Solution: Locate the cause of the issue.

ERROR 4084 (02000): No result

• OceanBase error code: 4084

• Cause: The value of the parameter is not found.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4085 (HY000): Queue overflow

• OceanBase error code: 4085

• Cause: A queue overflow occurred.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4090 (HY000): Table log_id range no continuous

• OceanBase error code: 4090

• Cause: Log IDs of SSTables in a partition are inconsecutive.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4098 (HY000): Term not match

• OceanBase error code: 4098

• Cause: A replica proposal_id mismatch occurred.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4103 (42000): Data checksum error

• OceanBase error code: 4103

• Cause: A data checksum error occurred.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4104 (HY000): Initialize error

• OceanBase error code: 4104

• Cause: Initialization failed.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4105 (HY000): Rowkey order error

• OceanBase error code: 4105

• Cause: The sequence of primary keys is not as expected.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4107 (HY000): block switched when fill commitlog

• OceanBase error code: 4107

• Cause: The buffer used for group commit must be switched.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4108 (HY000): Physic data checksum error

• OceanBase error code: 4108

• Cause: A physical data checksum error occurred due to a disk failure or a program bug.

• Solution: Check the hardware, or contact OceanBase Technical Support for troubleshooting.

ERROR 4109 (HY000): Server state or role not the same as expected

• OceanBase error code: 4109

• Cause: A status mismatch occurred.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4111 (HY000): block need freeze

• OceanBase error code: 4111

• Cause: The block needs to be frozen.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4112 (HY000): block frozen

• OceanBase error code: 4112

• Cause: The block has been frozen.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4113 (HY000): In FATAL state

• OceanBase error code: 4113

• Cause: The status is invalid.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4114 (08S01): In STOP state

• OceanBase error code: 4114

• Cause: The OBServer node is being stopped.

• Solution: If the error persists, contact OceanBase Technical Support for troubleshooting.

ERROR 4119 (08000): RPC packet to send too long

• OceanBase error code: 4119

• Cause: The length of the RPC packet exceeds the upper limit.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4120 (HY000): Log too large

• OceanBase error code: 4120

• Cause: The log size exceeds the upper limit.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4123 (08000): Libeasy error

• OceanBase error code: 4123

• Cause: Network initialization failed.

• Solution: Contact the system administrator or database administrator for troubleshooting.

ERROR 4124 (HY000): Connect error

• OceanBase error code: 4124

• Cause: A connection to the server failed to be established.

• Solution: Contact the system administrator or database administrator for troubleshooting.

ERROR 4128 (HY000): RPC packet is invalid

• OceanBase error code: 4128

• Cause: The format of the RPC packet is invalid.

• Solution: Contact the system administrator or database administrator for troubleshooting.

ERROR 4138 (HY000): Request to read too old versioned data

• OceanBase error code: 4138

• Cause: The version of the accessed data is outdated.

• Solution: Execute the statement again, or increase the value of the undo_retention parameter.

ERROR 4143 (42000): Version not match

• OceanBase error code: 4143

• Cause: A version mismatch occurred.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4147 (HY000): Invalid config

• OceanBase error code: 4147

• Cause: The current configuration is invalid.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4150 (42000): Min value

• OceanBase error code: 4150

• Cause: You are attempting to access the invalid minimum special value in the internal table.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4151 (42000): Max value

• OceanBase error code: 4151

• Cause: You are attempting to access the invalid maximum special value in the internal table.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4152 (42000): Null value

• OceanBase error code: 4152

• Cause: You are attempting to access an invalid null value in the internal table.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4154 (HY000): Internal SQL client error

• OceanBase error code: 4154

• Cause: An internal SQL client error occurred.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4161 (42000): Invalid argument num

• OceanBase error code: 4161

• Cause: The number of specified parameters is invalid.

• Solution: Check the parameter list, or contact OceanBase Technical Support for troubleshooting.

ERROR 4162 (HY000): reserved lease not enough

• OceanBase error code: 4162

• Cause: The validity period of the lease is insufficient.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4165 (HY000): Empty result

• OceanBase error code: 4165

• Cause: The result set is empty.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4168 (HY000): Invalid log module id

• OceanBase error code: 4168

• Cause: The log module ID is invalid.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4169 (HY000): Unknown module name. Invalid Setting:'%.*s'. Syntax:parMod.subMod:level, parMod.subMod:level

• OceanBase error code: 4169

• Cause: The log module name that you specified when you set the log generation level on the client is invalid.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4170 (HY000): Invalid level. Invalid setting:'%.*s'. Syntax:parMod.subMod:level, parMod.subMod:level

• OceanBase error code: 4170

• Cause: The log generation level that you set on the client is invalid.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4171 (HY000): Syntax to set log_level error. Invalid setting:'%.*s'. Syntax:parMod.subMod:level, parMod.subMod:level

• OceanBase error code: 4171

• Cause: The syntax that you used to set the log generation level on the client is invalid.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4172 (HY000): Index out of range

• OceanBase error code: 4172

• Cause: The index is out of range.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4175 (42000): Out of range

• OceanBase error code: 4175

• Cause: The value is out of range.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4177 (42000): Schema version too old

• OceanBase error code: 4177

• Cause: The local schema version is outdated.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4179 (HY000): %s not allowed

• OceanBase error code: 4179

• Cause:

  The possible causes are described as follows:

  • The log stream in the current state does not support the operation.
  • The server that executes the task is in an abnormal state.
  • The number of replica members on the list has reached the upper limit.
  • This log stream replica does not exist in the provided data source.
  • The data source server is not in the alive state.
  • The data source server is in the stopped state.
  • A read-only replica is used as the data source of a full-featured replica, which is not allowed.
  • The replica restore in the data source failed.
  • After this replica is removed, no leader is available.
  • The source and destination are not in the same zone.

• Solution: Resolve the issue based on the actual business scenario or contact OceanBase Technical Support for troubleshooting.

ERROR 4180 (HY000): No empty entry

• OceanBase error code: 4180

• Cause: The data entry is not empty.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4181 (42S01): Already exist

• OceanBase error code: 4181

• Cause: The entry already exists in the location cache.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4182 (HY000): Value not found

• OceanBase error code: 4182

• Cause: The value is not found.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4183 (HY000): Key out of range

• OceanBase error code: 4183

• Cause: The key is out of range.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4184 (53100): ChunkServer out of disk space

• OceanBase error code: 4184

• Cause: The disk space is fully occupied.

• Solution: Add servers for scale-out, or contact OceanBase Technical Support for troubleshooting.

ERROR 4186 (HY000): ChunkServer failed to get compress library

• OceanBase error code: 4186

• Cause: No compression library is found.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4187 (HY000): Item not match

• OceanBase error code: 4187

• Cause: A value mismatch occurred.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4189 (HY000): the macro block type does not exist

• OceanBase error code: 4189

• Cause: The specified macroblock type does not exist.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4191 (HY000): partition group is removed

• OceanBase error code: 4191

• Cause: The partition has been deleted.

• Solution: Troubleshooting is not required.

ERROR 4192 (42000): ddl task executes too much time

• OceanBase error code: 4192
• Cause: The execution time of DDL tasks is too long.
• Solution: Check whether the execution time of DDL tasks is as expected. If the execution time is too long, contact OceanBase Technical Support for troubleshooting.

ERROR 4200 (HY000): hash map/set entry exist

• OceanBase error code: 4200

• Cause: The HASH value already exists.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4201 (HY000): hash map/set entry not exist

• OceanBase error code: 4201

• Cause: The HASH value does not exist.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4204 (HY000): hash map/set get timeout

• OceanBase error code: 4204

• Cause: The HASH operation timed out.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4205 (HY000): hash map/set retry

• OceanBase error code: 4205

• Cause: The HASH operation needs to be retried.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4206 (HY000): hash map/set full

• OceanBase error code: 4206

• Cause: The HashMap instance is full.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4208 (HY000): wait next packet timeout

• OceanBase error code: 4208

• Cause: No subsequent packets are received within the timeout period.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4209 (HY000): partition has not leader

• OceanBase error code: 4209

• Cause: The partition or log stream has no leader.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4210 (HY000): prepare major freeze failed

• OceanBase error code: 4210

• Cause: The preparation for a major compaction failed.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4211 (HY000): commit major freeze failed

• OceanBase error code: 4211

• Cause: The commit of a major freeze failed.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4212 (HY000): abort major freeze failed

• OceanBase error code: 4212

• Cause: The rollback of a major freeze failed.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4213 (HY000): last major freeze not finish", "%s

• OceanBase error code: 4213

• Cause: The last major compaction has not been completed.

• Solution: Wait until the last major compaction is completed, and then initiate a new major compaction.

ERROR 4215 (HY000): wait major freeze response timeout

• OceanBase error code: 4215

• Cause: No major freeze response is returned within the timeout period.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4216 (HY000): curl error

• OceanBase error code: 4216

• Cause: A libcurl access error occurred.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4217 (HY000): Major freeze not allowed now

• OceanBase error code: 4217

• Cause: Major freezes are not allowed when the system is in the current state.

• Solution: Check whether the system is being upgraded or in the process of another operation.

ERROR 4218 (HY000): prepare freeze failed

• OceanBase error code: 4218

• Cause: The preparation for a freeze failed.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4220 (HY000): Inactive sql client, only read allowed

• OceanBase error code: 4220

• Cause: The SQL client is inactive.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4221 (HY000): Inactive rpc proxy, can not send RPC request

• OceanBase error code: 4221

• Cause: The RPC client is not initialized.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4222 (42000): Interval with year or month can not be converted to microseconds

• OceanBase error code: 4222

• Cause: The system encountered an error when converting the time data type.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4223 (42000): Interval has too many datetime parts

• OceanBase error code: 4223

• Cause: The system encountered an error when converting the time data type.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4225 (HY000): Partition entry not exists

• OceanBase error code: 4225

• Cause: The specified partition does not exist.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4232 (HY000): The observer or zone is not a follower

• OceanBase error code: 4232

• Cause: The OBServer node or zone that is accessed is not a follower.

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

ERROR 4233 (HY000): smaller than container lower bound

• OceanBase error code: 4233

• Cause: The value is below the lower limit of the container.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4234 (HY000): bigger than container upper bound

• OceanBase error code: 4234

• Cause: The value is above the upper limit of the container.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4236 (HY000): ObConfig return error code

• OceanBase error code: 4236

• Cause: OceanBase Database encountered an error when accessing Config Server.

• Solution: Check the obconfig_url parameter to determine whether Config Server is running properly, and contact OceanBase Technical Support for troubleshooting.

ERROR 4237 (HY000): Appname mismatch with obconfig result

• OceanBase error code: 4237

• Cause: The cluster name specified for Config Server is inconsistent with the actual cluster name.

• Solution: Check the obconfig_url parameter and contact OceanBase Technical Support for troubleshooting.

ERROR 4239 (HY000): Can not use merge join to join the tables without join conditions

• OceanBase error code: 4239

• Cause: A kernel error occurred.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4240 (HY000): No join order generated

• OceanBase error code: 4240

• Cause: A kernel error occurred.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4241 (HY000): No join path generated

• OceanBase error code: 4241

• Cause: A kernel error occurred.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4242 (HY000): Schema error

• OceanBase error code: 4242

• Cause: The execution server failed to obtain the schema.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4243 (HY000): file not opened

• OceanBase error code: 4243

• Cause: The file is not opened.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4244 (HY000): Timer task has been scheduled

• OceanBase error code: 4244

• Cause: A timer task has been scheduled.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4245 (HY000): Timer task has not been scheduled

• OceanBase error code: 4245

• Cause: No timer task is scheduled.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4246 (HY000): parse debug sync string error

• OceanBase error code: 4246

• Cause: The string of debug_sync does not conform to the syntax.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4247 (HY000): unknown debug sync point

• OceanBase error code: 4247

• Cause: The debug sync point does not exist.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4248 (HY000): task is interrupted while running

• OceanBase error code: 4248

• Cause: The distributed task execution scheduler was interrupted and stopped in advance.

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

ERROR 4250 (HY000): module is not running

• OceanBase error code: 4250

• Cause: The module has not been started.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4251 (HY000): partition not valid

• OceanBase error code: 4251

• Cause: The partition is invalid.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4253 (HY000): Comment for tenant is too long (max = %ld)

• OceanBase error code: 4253

• Cause: The length of the COMMENT for a tenant in a DDL statement exceeds the upper limit.

• Solution: Shorten the COMMENT in the DDL statement.

ERROR 4257 (HY000): compress data or decompress data failed

• OceanBase error code: 4257

• Cause: Data compression or decompression failed because the data was corrupted.

• Solution: Contact the database administrator to check the hardware and replace the faulty server or recover the data.

ERROR 4263 (HY000): Minor freeze not allowed now

• OceanBase error code: 4263

• Cause: Minor freezes are not allowed when the system is in the current state.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4264 (HY000): Log out of disk space

• OceanBase error code: 4264

• Cause: The log disk is fully occupied.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4265 (HY000): Rpc connect error

• OceanBase error code: 4265

• Cause: An RPC connection failed to be established.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4266 (HY000): minor merge not allow

• OceanBase error code: 4266

• Cause: Minor compactions are not allowed when the system is in the current state.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4270 (HY000): Working partition entry does not exists

• OceanBase error code: 4270

• Cause: The partition status is abnormal.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4271 (HY000): LIBEASY reach memory limit

• OceanBase error code: 4271

• Cause: The memory size occupied by unsent libeasy packets has exceeded the upper limit.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4273 (HY000): free memblock in cache is not enough

• OceanBase error code: 4273

• Cause: Available memory blocks in the cache are insufficient.

• Solution: Increase the memory size, reduce the load, or contact OceanBase Technical Support for troubleshooting.

ERROR 4274 (HY000): sync wash memblock timeout

• OceanBase error code: 4274

• Cause: Memory blocks were not released within the timeout period.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4278 (HY000): last log is not complete

• OceanBase error code: 4278

• Cause: The last log is incomplete due to a power failure or an emergency.

• Solution: Restart the OBServer node or contact OceanBase Technical Support for troubleshooting.

ERROR 4279 (HY000): table is deleted

• OceanBase error code: 4279

• Cause: The table has been deleted.

• Solution: Check whether the SQL statement attempts to access the deleted table.

ERROR 4280 (HY000): version range not continues

• OceanBase error code: 4280

• Cause: The version range is inconsecutive.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4281 (HY000): io buffer is invalid

• OceanBase error code: 4281

• Cause: The I/O buffer is invalid.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4282 (HY000): partition is removed

• OceanBase error code: 4282

• Cause: The partition has been dropped.

• Solution: Check whether the operation is initiated on the dropped partition, or contact OceanBase Technical Support for troubleshooting.

ERROR 4283 (HY000): gts is not ready

• OceanBase error code: 4283

• Cause: Global Timestamp Service (GTS) is not available.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4286 (HY000): major sstable may has been merged

• OceanBase error code: 4286

• Cause: Baseline data has been compacted.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4287 (HY000): minor sstable version range cross

• OceanBase error code: 4287

• Cause: Version ranges of SSTables have an intersection.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4288 (HY000): memtable cannot minor merge

• OceanBase error code: 4288

• Cause: A minor compaction of the MemTable failed.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4289 (HY000): task exist

• OceanBase error code: 4289

• Cause: Duplicate tasks exist.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4290 (HY000): cannot allocate disk space

• OceanBase error code: 4290

• Cause: The available disk space is insufficient.

• Solution: Increase the disk space, or contact OceanBase Technical Support for troubleshooting.

ERROR 4297 (HY000): name is already used by an existing object

• OceanBase error code: 4297

• Cause: The specified object name is already used in the same namespace.

• Solution: Specify an object name that is not used in the namespace.

ERROR 4298 (HY000): %s does not exist

• OceanBase error code: 4298

• MySQL error code: 4298

• Cause: The specified sequence does not exist.

• Solution: Make sure that the specified sequence name is valid and that you have the required privilege to perform the operation on the sequence.

ERROR 4300 (HY000): invalid sequence name

• OceanBase error code: 4300

• Cause: The specified sequence name is invalid.

• Solution: Modify the sequence name.

ERROR 4301 (HY000): duplicate MAXVALUE/NOMAXVALUE specifications

• OceanBase error code: 4301

• Cause: Duplicate MAXVALUE or NOMAXVALUE settings exist.

• Solution: Deduplicate MAXVALUE or NOMAXVALUE settings.

ERROR 4302 (HY000): duplicate MINVALUE/NOMINVALUE specifications

• OceanBase error code: 4302

• Cause: Duplicate MINVALUE or NOMINVALUE settings exist.

• Solution: Deduplicate MINVALUE or NOMINVALUE settings.

ERROR 4303 (HY000): duplicate CYCLE/NOCYCLE specifications

• OceanBase error code: 4303

• Cause: Duplicate CYCLE or NOCYCLE settings exist.

• Solution: Deduplicate CYCLE or NOCYCLE settings.

ERROR 4304 (HY000): duplicate CACHE/NOCACHE specifications

• OceanBase error code: 4304

• Cause: Duplicate CACHE or NOCACHE settings exist.

• Solution: Deduplicate CACHE or NOCACHE settings.

ERROR 4305 (HY000): duplicate ORDER/NOORDER specifications

• OceanBase error code: 4305

• Cause: Duplicate ORDER or NOORDER settings exist.

• Solution: Deduplicate ORDER or NOORDER settings.

ERROR 4306 (HY000): conflicting MAXVALUE/NOMAXVALUE specifications

• OceanBase error code: 4306

• Cause: Conflicting MAXVALUE or NOMAXVALUE settings exist.

• Solution: Delete conflicting MAXVALUE or NOMAXVALUE settings.

ERROR 4307 (HY000): conflicting MINVALUE/NOMINVALUE specifications

• OceanBase error code: 4307

• Cause: Conflicting MINVALUE or NOMINVALUE settings exist.

• Solution: Delete conflicting MINVALUE or NOMINVALUE settings.

ERROR 4308 (HY000): conflicting CYCLE/NOCYCLE specifications

• OceanBase error code: 4308

• Cause: Conflicting CYCLE or NOCYCLE settings exist.

• Solution: Delete conflicting CYCLE or NOCYCLE settings.

ERROR 4309 (HY000): conflicting CACHE/NOCACHE specifications

• OceanBase error code: 4309

• Cause: Conflicting CACHE or NOCACHE settings exist.

• Solution: Delete conflicting CACHE or NOCACHE settings.

ERROR 4310 (HY000): conflicting ORDER/NOORDER specifications

• OceanBase error code: 4310

• Cause: Conflicting ORDER or NOORDER settings exist.

• Solution: Delete conflicting ORDER or NOORDER settings.

ERROR 4311 (HY000): cannot alter starting sequence number

• OceanBase error code: 4311

• Cause: The START WITH value of an auto-increment column cannot be modified.

• Solution: Do not modify the START WITH value.

ERROR 4312 (HY000): duplicate INCREMENT BY specifications

• OceanBase error code: 4312

• Cause: INCREMENT BY is repeatedly defined.

• Solution: Delete the duplicate INCREMENT BY specifications.

ERROR 4313 (HY000): duplicate START WITH specifications

• OceanBase error code: 4313

• Cause: START WITH is repeatedly defined.

• Solution: Delete the duplicate START WITH specifications.

ERROR 4314 (HY000): no options specified for ALTER SEQUENCE

• OceanBase error code: 4314

• Cause: No option is specified in the ALTER SEQUENCE statement.

• Solution: Options in statements are meaningful. Make sure that all the required options are specified in the statement.

ERROR 4315 (HY000): sequence number not allowed here

• OceanBase error code: 4315

• Cause: Auto-increment columns are not allowed for this operation.

• Solution: Delete the specified auto-increment column.

ERROR 4316 (HY000): sequence does not exist

• OceanBase error code: 4316

• Cause: The specified auto-increment column does not exist, or you do not have the required privilege.

• Solution: Make sure that the specified auto-increment column name is valid and that you have the required privilege on the column.

ERROR 4317 (HY000): sequence parameter %s must be an integer

• OceanBase error code: 4317

• Cause: A parameter value in the CREATE SEQUENCE or ALTER SEQUENCE statement is not an integer.

• Solution: When you create or modify an auto-increment column, specify integer values for parameters in the statement.

ERROR 4318 (HY000): INCREMENT must be a non-zero integer

• OceanBase error code: 4318

• Cause: The value of INCREMENT is not a non-zero integer.

• Solution: Set INCREMENT to a non-zero integer.

ERROR 4319 (HY000): sequence parameter exceeds maximum size allowed

• OceanBase error code: 4319

• Cause: A parameter value specified for the auto-increment column exceeds the maximum value allowed.

• Solution: Specify parameter values within the range allowed.

ERROR 4320 (HY000): MINVALUE must be less than MAXVALUE

• OceanBase error code: 4320

• Cause: In the CREATE SEQUENCE or ALTER SEQUENCE statement, the value of MINVALUE is not less than that of MAXVALUE.

• Solution: Make sure that the value of MINVALUE is less than that of MAXVALUE.

ERROR 4321 (HY000): INCREMENT must be less than MAXVALUE minus MINVALUE

• OceanBase error code: 4321

• Cause: In the CREATE SEQUENCE or ALTER SEQUENCE statement, the value of INCREMENT is not less than the difference between the values of MAXVALUE and MINVALUE.

• Solution: Make sure that the value of INCREMENT is less than the difference between the MAXVALUE and MINVALUE values.

ERROR 4322 (HY000): START WITH cannot be less than MINVALUE

• OceanBase error code: 4322

• Cause: In the CREATE SEQUENCE or ALTER SEQUENCE statement, the value of START WITH is less than that of MINVALUE.

• Solution: Make sure that the value of START WITH is greater than or equal to that of MINVALUE.

ERROR 4323 (HY000): MINVALUE cannot be made to exceed the current value

• OceanBase error code: 4323

• Cause: The new value of MINVALUE is greater than the current value.

• Solution: Make sure that the value of MINVALUE is less than the current value.

ERROR 4324 (HY000): START WITH cannot be more than MAXVALUE

• OceanBase error code: 4324

• Cause: The value of START WITH is greater than that of MAXVALUE.

• Solution: Make sure that the value of START WITH is less than that of MAXVALUE.

ERROR 4325 (HY000): MAXVALUE cannot be made to be less than the current value

• OceanBase error code: 4325

• Cause: The value of MAXVALUE is less than the current value.

• Solution: Make sure that the value of MAXVALUE is greater than the current value.

ERROR 4326 (HY000): the number of values to CACHE must be greater than 1

• OceanBase error code: 4326

• Cause: A parameter value in the CACHE clause is not greater than 1.

• Solution: Make sure that the parameter values in the CACHE clause are greater than 1.

ERROR 4327 (HY000): sequence option value out of range

• OceanBase error code: 4327

• Cause: A parameter value in the CREATE SEQUENCE or ALTER SEQUENCE statement is out of range.

• Solution: Specify parameter values within the range allowed.

ERROR 4328 (HY000): number to CACHE must be less than one cycle

• OceanBase error code: 4328

• Cause: The parameter values to be cached are not within one cycle.

• Solution: Increase the cycle or cache fewer values.

ERROR 4329 (HY000): descending sequences that CYCLE must specify MINVALUE

• OceanBase error code: 4329

• Cause: MINVALUE is not specified for the descending auto-increment column.

• Solution: Create a sequence and specify MINVALUE.

ERROR 4330 (HY000): ascending sequences that CYCLE must specify MAXVALUE

• OceanBase error code: 4330

• Cause: MAXVALUE is not specified for the ascending auto-increment column.

• Solution: Create a sequence and specify MAXVALUE.

ERROR 4331 (HY000): sequence %s no longer exists

• OceanBase error code: 4331

• Cause: The specified auto-increment column does not exist.

• Solution: Create an auto-increment column.

ERROR 4332 (HY000): sequence exceeds %s and cannot be instantiated

• OceanBase error code: 4332

• Cause: The number of values in the auto-increment column has reached the upper limit, and no more values can be generated.

• Solution: Modify the auto-increment column to generate new values.

ERROR 4333 (HY000): divisor is equal to zero

• OceanBase error code: 4333

• Cause: The divisor is 0.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4334 (HY000): fail to decrypt data

• OceanBase error code: 4334

• Cause: Decryption failed.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4335 (HY000): fail to encrypt data

• OceanBase error code: 4335

• Cause: Encryption failed.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4337 (HY000): store directory structure error

• OceanBase error code: 4337

• Cause: A storage directory structure error occurred.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4338 (HY000): open twice

• OceanBase error code: 4338

• Cause: The file was repeatedly opened.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4339 (HY000): raid super block not match

• OceanBase error code: 4339

• Cause: The super block encountered an error.

• Solution: Check the disk or contact OceanBase Technical Support for troubleshooting.

ERROR 4340 (HY000): not opened

• OceanBase error code: 4340

• Cause: The item is not opened.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4341 (HY000): target module is not in service

• OceanBase error code: 4341

• Cause: Weak-consistency reads are disabled.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4342 (HY000): raid disk not in normal status

• OceanBase error code: 4342

• Cause: The disk status is abnormal.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4343 (HY000): tenant schema is not full

• OceanBase error code: 4343

• Cause: The local tenant schema version is outdated.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4344 (HY000): invalid timestamp

• OceanBase error code: 4344

• Cause: The specified timestamp is invalid.

• Solution: Specify a valid timestamp.

ERROR 4345 (HY000): dir not empty

• OceanBase error code: 4345

• Cause: The specified directory is not empty.

• Solution: Make sure that the installation directory of OceanBase Database is valid.

ERROR 4346 (HY000): schema is not up to date for read

• OceanBase error code: 4346

• Cause: The local schema version is outdated.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4347 (HY000): role (string) does not exist

• OceanBase error code: 4347

• Cause: The role identified by ROLE does not exist.

• Solution: Specify a valid value for ROLE.

ERROR 4348 (HY000): role '%.*s' does not exist

• OceanBase error code: 4348

• Cause: A user or role with the specified name already exists.

• Solution: Specify another name.

ERROR 4349 (HY000): duplicate privilege listed

• OceanBase error code: 4349

• Cause: Duplicate privileges or roles are specified in the GRANT or REVOKE statement.

• Solution: Deduplicate the privileges or roles specified in the statement.

ERROR 4350 (HY000): the keystore already exists and each tenant can only have at most one

• OceanBase error code: 4350

• Cause: A Keystore already exists within the current tenant. You can create only one Keystore for a tenant.

• Solution: Check whether a Keystore has been created for the tenant.

ERROR 4351 (HY000): the keystore is not exist

• OceanBase error code: 4351

• Cause: No Keystore exists within the current tenant.

• Solution: Check whether a Keystore has been created for the tenant.

ERROR 4352 (HY000): the password is wrong for keystore

• OceanBase error code: 4352

• Cause: The specified Keystore password is invalid.

• Solution: Specify a valid password.

ERROR 4353 (HY000): tablespace '%.*s' already exists

• OceanBase error code: 4353

• Cause: A tablespace with the specified name already exists.

• Solution: Specify another name for the tablespace to be created.

ERROR 4354 (HY000): tablespace '%.*s' does not exist

• OceanBase error code: 4354

• Cause: The tablespace does not exist.

• Solution: Make sure that the tablespace to be accessed exists.

ERROR 4355 (HY000): cannot delete a tablespace which is not empty

• OceanBase error code: 4355

• Cause: The tablespace to be deleted is not empty.

• Solution: Make sure that the tablespace is empty and then delete it.

ERROR 4356 (HY000): floating point precision is out of range(1 to 126)

• OceanBase error code: 4356

• Cause: The precision of BINARY_DOUBLE data is out of range.

• Solution: Reduce the precision of the data.

ERROR 4357 (HY000): numeric precision specifier is out of range (1 to 38)

• OceanBase error code: 4357

• Cause: The precision of NUMBER data is out of range.

• Solution: Reduce the precision of the data.

ERROR 4358 (HY000): numeric scale specifier is out of range (-84 to 127)

• OceanBase error code: 4358

• Cause: The precision of NUMBER data is out of range.

• Solution: Reduce the precision of the data.

ERROR 4359 (HY000): the keystore is not open

• OceanBase error code: 4359

• Cause: The Keystore is not open.

• Solution: Open the Keystore.

ERROR 4360 (HY000): the keystore opened with dont have a master key

• OceanBase error code: 4360

• Cause: No master key is available.

• Solution: Create a master key.

ERROR 4361 (HY000): slog active transaction entries reach maximum

• OceanBase error code: 4361

• Cause: The number of concurrent slog transactions exceeds the upper limit.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4362 (HY000): BY ACCESS | SESSION clause not allowed for NOAUDIT

• OceanBase error code: 4362

• Cause: The BY ACCESS or BY SESSION clause is specified in the NOAUDIT statement.

• Solution: Delete the BY ACCESS or BY SESSION clause.

ERROR 4363 (HY000): auditing the object is not supported

• OceanBase error code: 4363

• Cause: This type of object cannot be audited.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4364 (HY000): DDL statement cannot be audited with BY SESSION specified

• OceanBase error code: 4364

• Cause: The BY SESSION clause is used to audit the DDL statement.

• Solution: Delete the BY SESSION clause.

ERROR 4367 (HY000): The data more than 64M(rpc limit), split into smaller task and retry

• OceanBase error code: 4367

• Cause: When the data volume exceeds 64 MB, the execution task must be split into smaller tasks. This error code is used to instruct the execution scheduler to split the task and try again.

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

ERROR 4368 (HY000): cluster %s not exist

• OceanBase error code: 4368

• Cause: When you access Config Server to obtain cluster information, Config Server returns this error code to indicate that the cluster does not exist.

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

ERROR 4369 (HY000): fail to get master key

• OceanBase error code: 4369

• Cause: The master key failed to be obtained.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4370 (HY000): tde_method parameter is invalid

• OceanBase error code: 4370

• Cause: The value of tde_method for the tenant is invalid.

• Solution: Adjust the value of tde_method.

ERROR 4371 (HY000): kms server connect failed, may be kms server is down

• OceanBase error code: 4371

• Cause: A connection to Key Management Service (KMS) failed to be established.

• Solution: Make sure that KMS is available.

ERROR 4372 (HY000): kms server is busy, try again

• OceanBase error code: 4372

• Cause: The KMS server is busy.

• Solution: Try again.

ERROR 4373 (HY000): kms server update key conflict at the same time, please try again

• OceanBase error code: 4373

• Cause: A conflict occurred when multiple master keys were updated at a time.

• Solution: Try again.

ERROR 4374 (HY000): value larger than specified precision allowed for this column

• OceanBase error code: 4374

• Cause: The precision of the current value is greater than the precision defined for the field.

• Solution: Adjust the value or the field definition.

ERROR 4375 (HY000): observer has disk error

• OceanBase error code: 4375

• Cause: The storage disk is faulty.

• Solution: Check whether the disk is faulty and replace the corresponding server.

ERROR 4376 (HY000): unimplemented feature

• OceanBase error code: 4376

• Cause: OceanBase Database does not support this feature.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4377 (HY000): fatal internal error in [%.*s]

• OceanBase error code: 4377

• Cause: OceanBase Database encountered an unexpected internal error, such as a program execution failure.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4378 (HY000): cluster name conflict

• OceanBase error code: 4378

• Cause: The specified cluster name already exists.

• Solution: Specify another cluster name.

ERROR 4379 (HY000): heap table has reached max row size, cannot insert anymore

• OceanBase error code: 4379

• Cause: No more data can be inserted into the table without a primary key.

• Solution: Create a table and import the data of the original table to the new table.

ERROR 4381 (HY000): Not supported, deprecated MySQL feature

• OceanBase error code: 4381

• Cause: Float(m,d) or double(m,d) was used to define the floating-point type with precision when data types were specified.

• Solution: Use decimal(m,d) rather than float(m,d) or double(m,d) to specify exact decimal numerals.

ERROR 4383 (HY000): transaction id is not ready

• OceanBase error code: 4383

• Cause: No ID range is available for the Transaction ID allocator to use.

• Solution: Retry the acquisition process until it times out.

ERROR 4386 (HY000): Do not allow removing leader

• OceanBase error code: 4386

• Cause: An internal error occurred. Migration is not supported because the migration source is a leader log-only replica.

• Solution: Troubleshooting is not required.

ERROR 4387 (HY000): Failed to switch resource group

• OceanBase error code: 4387
• MySQL error code: 13937

ERROR 4388 (HY000): Unexpected internal error happen, please checkout the internal errcode

• OceanBase error code: 4388

• Cause: An unexpected internal error occurs.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4389 (HY000): Processing time is too long

• OceanBase error code: 4389

• Cause: The task processing time is too long.

• Solution: This is an internal error code. If this error is returned, contact OceanBase Technical Support for troubleshooting.

ERROR 4390 (HY000): Schema of remote server is not refreshed yet

• OceanBase error code: 4390

• Cause: The local or remote schema is not refreshed. Some of the OBServer nodes may not be restarted or may be abnormal.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4391 (HY000): ddl sstable version range cross

• OceanBase error code: 4391

• Cause: DDL statements for automatic and manual SSTable compactions conflict.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4392 (HY000): disk is hung

• OceanBase error code: 4392
• Cause: The disk is faulty.
• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4393 (HY000): observer start process failure

• OceanBase error code: 4393

• Cause: The observer process fails to start because an internal component or service is initialized.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4394 (HY000): observer stop process failure

• OceanBase error code: 4394
• Cause: An internal component or service error occurs when the observer process exits.
• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4395 (HY000): observice start process has failure

• OceanBase error code: 4395
• Cause: The observer process fails to start because an internal component or service is initialized.
• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4396 (HY000): Worker thread panic, thread may be terminated or hung

• OceanBase error code: 4396
• Cause: A worker thread aborts execution due to an exception.
• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4399 (HY000): Unit status is not expected

• OceanBase error code: 4399
• Cause: The tenant is migrated when you import data in direct load mode.
• Solution: Retry the failed SQL statement for direct load.

ERROR 4400 (HY000): Autoinc cache's autoinc version is not equal to request's autoinc version

• OceanBase error code: 4400
• Cause: The version of the cached auto-increment column values is inconsistent with the requested version.
• Solution:
  1. Make sure that the version of the auto-increment column values is the same as the requested version.
  2. Clear the cached auto-increment column values to regenerate new values.

ERROR 4402 (HY000): Kill Client Session failed

• OceanBase error code: 4402

• Cause: The operation to terminate the client session failed.

• Solution: Before you terminate a client session, make sure that the session is active and can be terminated.

ERROR 4403 (HY000): OS params check failed, because the operating system has improper parameter configurations

• OceanBase error code: 4403

• Cause: The OBServer node detects that an operating system parameter is set to an invalid value.

• Solution: Find the parameter that is incorrectly set in the ERROR logs, confirm the value range of the parameter, and modify the parameter value.