4000 ~ 4499

This error code range indicates general error codes.

ERROR 4000 (HY000) : Common error

• OceanBase error code: 4000

• Cause: Common error codes.

• Solution: Contact technical support for assistance.

Related issues:

• Error 4000 in EXPLAIN SQL
• One of the error scenarios in pushdown grouping aggregation

ERROR 4001 (HY004) : Object type error

• OceanBase error code: 4001

• Cause: Type error.

• Solution: Contact technical support for assistance.

ERROR 4003 (42000) : Array index out of range

• OceanBase error code: 4003

• Cause: Array index out of bounds.

• Solution: Contact technical support for assistance.

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

• OceanBase error code: 4004

• Cause: Listening service failed to start due to network disconnection.

• Solution: Select an available port and restart the observer process.

ERROR 4005 (HY000) : The object is initialized twice

• OceanBase error code: 4005

• Cause: Object is initialized repeatedly.

• Solution: Contact technical support for assistance.

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

• OceanBase error code: 5388

• Compatible MySQL error code: 4005

• Cause: An orphan object is created or inherited when operating on a user.

• Solution: Check for permissions or delete the corresponding object.

ERROR 4006 (HY000) : The object is not initialized

• OceanBase error code: 4006

• Cause: The object is not initialized.

• Solution: Contact technical support for assistance.

Related issues:

• Error -4006/-4343 during major compaction

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

• Compatible MySQL error code: 4006

• Cause: An orphan object is created or inherited when operating on a user.

• Solution: Delete the corresponding object.

ERROR 4008 ( HY000 ) : End of iteration

• OceanBase error code: 4008

• Cause: Iteration has ended.

• Solution: Contact technical support for assistance.

ERROR 4009 (58030 ) : IO error

• OceanBase error code: 4009

• Cause: An I/O-related system call, such as READ or WRITE, failed.

• Solution: Contact technical support for assistance.

Related issues:

• OBServer startup failed, error code 4009
• OBServer startup failed, error code 4009
• Unable to clean up historical backup files, reported -4009 error

ERROR 4010 (HY000) : Wrong RPC command version

• OceanBase error code: 4010

• Cause: The RPC command version is incorrect.

• Solution: Contact technical support for assistance.

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: Execution timed out.

• Solution:

  • Reduce execution time through performance tuning.

  • Set a larger timeout period.

  • Contact technical support for assistance.

Related issues:

• Bootstrap failed, error code 4012
• Tenant locality change failed, major compaction timed out
• mysqldump tool data export error, error code 4012
• Disk failure causing major compaction timeout, SQL execution timeout
• SELECT DBA_OB_LS_LOCATIONS timed out in a user tenant, error -5150
• OceanBase Database reports timeout or hangs directly, error 4012

ERROR 4012 (HY000) : Task timeout and not executed

• OceanBase error code: 4049

• Compatible MySQL error code: 4012

ERROR 4012 (HY000) : RPC session not found

• OceanBase error code: 4067

• Compatible MySQL error code: 4012

ERROR 4012 (HY000) : RPC send error

• OceanBase error code: 4121

• Compatible MySQL error code: 4012

ERROR 4012 (HY000) : RPC post error

• OceanBase error code: 4122

• Compatible MySQL error code: 4012

ERROR 4012 (HY000) : Timeout

• OceanBase error code: 4664

• Compatible MySQL error code: 4012

Related issue cases:

• Analyze large wide tables slowly and exhaust tenant memory
• Primary/standby database synchronization is normal, but switchover succeeds only after multiple retries
• Initiating data backup reports -4012 timeout

ERROR 4012 (HY000) : Statement is timeout

• OceanBase error code: 6004

• Compatible 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

• Compatible MySQL error code: 4012

Related issue cases:

• Transaction timeout, error code ERROR 4012

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

• OceanBase error code: 6212

• Compatible MySQL error code: 4012

ERROR 4012 (25000) : Transaction result isunknown

• OceanBase error code: 6225

• Compatible MySQL error code: 4012

ERROR 4012 (25000) : transaction rpc timeout

• OceanBase error code: 6230

• Compatible MySQL error code: 4012

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

• OceanBase error code: 4013

• Cause: Memory allocation failed.

  • Physical memory is exhausted.
  • A single memory allocation exceeds 4 GB.
  • The memory usage of the CTX, tenant, or server reaches the upper limit.

• Solution: Contact technical support for assistance.

Related issues:

• Insufficient IO memory for OBServer startup
• Error 4013 during the IO step of an ARM architecture-based benchmark
• Standby cluster unresponsive in a primary-standby cluster architecture, error code 4013
• Insufficient workspace memory, error code 4013
• migrate unit error: -4013, allocated memory exceeds 4 GB
• UDF scenario: transaction start causes transaction limit exceeded error -4013
• Major compaction: ob_micro_block_cache module error: failed to allocate value, -4013
• Differences between error codes 4013 and 4030 in OceanBase Database
• One of the scenarios where SQL execution reports 4013 and tenant memory suddenly increases by 500
• Dynamic memory leak in the sqlexecuter module
• OBServer log flush: record concurrent fifoallocator alloc mem failed(total_size=1793,ret=-4013)
• PS block memory fragmentation causes execution to report -4013
• Analyze large wide tables slowly and exhaust tenant memory
• SQL parsing phase error -4013, tenant memory full
• Execute UDF error -4013
• Unreasonable vm.max_map_count configuration may cause severe memory leaks
• Fast memory writes cause tenant memory full error -4013
• [Standby cluster unresponsive in a primary-standby cluster architecture, error code 4013](https://www.oceanbase.com/knowledge-base/oceanbase-database-20000000045

ERROR 4014 (HY000) : Inner state error

• OceanBase error code: 4014

• Cause: Internal state exception.

• Solution: Contact technical support for assistance.

ERROR 4015 (HY000) : System error

• OceanBase error code: 4015

• Cause: Internal error code.

• Solution: Contact technical support for assistance.

Related issues:

• Bootstrap failure, error code 4015
• OBServer startup error: -4015, super block v1 size not match
• Process flow when OceanBase physical backup media space is full

ERROR 4016 (HY000) : Internal error

• OceanBase error code: 4016

• Cause: An internal error code.

• Solution: Contact technical support for assistance.

Related issues:

• OBServer startup failure, error code 4016
• Bootstrap failure, error code 4016 (cluster_id setting out of valid range)
• Bootstrap Error 4016: no qualified primary zone for system
• OBServer restart failure, error code 4016
• -4016 reported during cluster minor compaction, persists after multiple retries
• LLVM memory allocation failure causes PL call to core
• GROUP_CONCAT function error, error code 4016
• MySQL-compatible mode time interval calculation error, error code 4016
• Backup and restore failure for data tables with index status UNUSABLE/ERROR
• ANALYZE TABLE error -4016
• -4016 reported during execution of CASE WHEN statements in PL
• sys_connect_by_path() function failure, error code OBE-00600
• Using TO_NUMBER function on nchar in Oracle-compatible mode of OceanBase Database reports Internal error
• SQL execution reports ErrorCode = 4016, SQLState = HY000, Details = Internal error
• SQL query reports internal error OBE-00600
• SQL execution with multiple IN and vector expressions reports error 4016
• Query range extraction reports error 4016
• Oracle-compatible tenant executes recursive CTE and reports error: -4016, Internal error
• MySQL-compatible tenant SQL execution reports error: -4016 Internal error
• Data collation type inconsistency causes major compaction to report -4016
• OBKV-Table queryAndAppend operation result does not meet expectations and client reports error during prefix query
• Backup error 4016, exceeds backup meta data size
• NFS directory not mounted as required causes continuous log errors
• Log archiving cannot stop, reports invalid archive_round
• Archiving gets stuck in stopping state after stopping archiving
• Physical restore error -4016
• OceanBase cross-machine restore locate_file_by_log_id reports -4016 error
• Restore failure error -4016, last_restore_log_id mismatch

ERROR 4017 (HY000) : Entry already exist

• OceanBase error code: 4017

• Cause: The data already exists.

• Solution: Contact technical support for assistance.

Related issues:

• Hierarchical query reports error -4017 due to different parameter values

ERROR 4018 (HY000) : Entry not exist

• OceanBase error code: 4018

• Cause: The data does not exist.

• Solution: Contact technical support for assistance.

Related issues:

• OBServer startup exception, log shows: -4018, incomplete logs
• Delete server error, error code 4018
• Emergency method for refreshing the location cache
• Backup and restore error 4018 archive_key file not exist after version upgrade

ERROR 4019 (HY000) : Size overflow

• OceanBase error code: 4019

• Cause: Space overflow.

• Solution: Contact technical support for assistance.

Related issues:

• log item too long ret=-4019
• Parallel DML (PDML) performance not meeting expectations
• Different result sets from_unixtime function

ERROR 4020 (HY000) : Reference count is not zero

• OceanBase error code: 4020

• Cause: The reference count is not zero.

• Solution: Contact technical support for assistance.

ERROR 4021 (HY000) : Conflict value

• OceanBase error code: 4021

• Error cause: The database encountered a logical error, typically a code error.

• Solution: Contact technical support for assistance in troubleshooting.

ERROR 4022 (HY000) : Item not set

• OceanBase error code: 4022

• Error cause: The value is not set.

• Solution: Contact technical support for assistance in troubleshooting.

ERROR 4023 (HY000) : Try again

• OceanBase error code: 4023

• Error cause: Retry is required.

• Solution: Retry or contact technical support for assistance in troubleshooting.

Related issue cases:

• Major compaction timeout, error code 4023
• OceanBase index creation hangs, system reports error -4023

ERROR 4024 (HY000) : Buffer not enough

• OceanBase error code: 4024

• Error cause: Insufficient space.

• Solution: Contact technical support for assistance in troubleshooting.

Related issue cases:

• SHOW PROXYSESSION statement error, error code 4024
• OceanBase database major compaction hangs and reports -4024
• INSERT ALL error -4024, Buffer not enough

ERROR 4025 (HY000) : Partial failed

• OceanBase error code: 4025

• Error cause: In a batch task, some operations succeeded while others failed.

• Solution: Contact technical support for assistance in troubleshooting.

ERROR 4026 (02000) : Nothing to read

• OceanBase error code: 4026

• Cause: No data to read.

• Solution: Contact technical support for assistance.

Related issue:

• Transaction scheduler context leakage in XA + Nested SQL rollback scenarios

ERROR 4027 (HY000) : User account %.*s@%.*s is directly or indirectly granted to the role %.*s@%.*s. The GRANT would create a loop

• OceanBase error code: 5373

• Compatible MySQL error code: 4027

• Cause: The user account %.*s@%.*s has been directly or indirectly granted to the role %.*s@%.*s, creating a circular grant.

• Solution: Check the authorization relationships between user accounts and roles to ensure no circular grants exist.

ERROR 4028 (HY000) : Log entry not continuous

• OceanBase error code: 4028

• Cause: File IDs are discontinuous.

• Solution: Contact technical support for assistance.

ERROR 4029 (HY000) : Schema error

• OceanBase error code: 4029

• Cause: Failed to obtain the schema.

• Solution: Contact technical support for assistance.

Related issue:

• Error -4029 reported during upgrade to version 3.1.2: primary and standby schema versions differ

ERROR 4030 (HY000) : Over tenant memory limits

• OceanBase error code: 4030

• Cause: The tenant's memory resources are insufficient.

• Solution: Increase the tenant's memory resources.

Related issues:

• Memory limit exceeded, error code 4030
• Handle the issue of RS leaderless and clog prompts ret=-4030 after restarting three nodes of the SYS tenant
• Differences between error codes 4013 and 4030 in OceanBase Database
• Reasons for the "Over tenant memory limits" error when inserting data into OceanBase Database

ERROR 4031 (HY004) : Unknown object

• OceanBase error code: 4031

• Cause: An unknown object.

• Solution: Contact technical support for assistance.

ERROR 4033 (HY000) : Serialize error

• OceanBase error code: 4033

• Cause: Serialization failed.

• Solution: Contact technical support for assistance.

ERROR 4034 (HY000) : Deserialize error

• OceanBase error code: 4034

• Cause: Deserialization failed.

• Solution: Contact technical support for assistance.

ERROR 4035 (HY000) : Asynchronous IO error

• OceanBase error code: 4035

• Cause: A system call related to asynchronous I/O failed.

• Solution: Contact technical support for assistance.

ERROR 4036 (HY000) : Need retry

• OceanBase error code: 4036

• Cause: Retry is required.

• Solution: Retry, or contact technical support for assistance.

ERROR 4037 (HY000) : Too many sstable

• OceanBase error code: 4037

• Cause: Excessive SSTables, typically due to too frequent minor compactions.

• Solution: Scale out to reduce the load on a single server, or contact technical support for assistance.

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

• OceanBase error code: 4038

• Cause: The current partition is not serving as the leader.

• Solution: Rerun the current statement or transaction.

Related issues:

• Error 4038 occurs after an R replica switchover because the location cache cannot be refreshed

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

• OceanBase error code: 4039

• Cause: SQL throttling.

• Solution: Contact technical support for assistance.

ERROR 4041 (HY000) : Decrypt error

• OceanBase error code: 4041

• Cause: Decryption failed.

• Solution: Contact technical support for assistance.

ERROR 4045 (HY000) : pushdown status changed

• OceanBase error code: 4045

• Error cause: Internal error code.

• Solution: Contact technical support for assistance.

ERROR 4046 (HY000) : Storage schema is not valid

• OceanBase error code: 4046

• Cause: The storage layer SCHEMA is invalid.

• Solution: Contact technical support for assistance.

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

• OceanBase error code: 4047

• Cause: The Medium Info is invalid.

• Solution: Contact technical support for assistance.

ERROR 4048 (HY000) : Not registered

• OceanBase error code: 4048

• Cause: An internal error code.

• Solution: Contact technical support for assistance.

ERROR 4050 (HY000) : Not the object

• OceanBase error code: 4050

• Cause: The objects do not match.

• Solution: Contact technical support for assistance.

ERROR 4052 (HY000) : Corrupted log entry

• OceanBase error code: 4052

• Cause: An invalid log entry, typically caused by hardware or disk errors that result in corrupted log data read from disk.

• Solution: Contact the DBA to investigate hardware issues, or contact technical support for assistance.

ERROR 4055 (HY000) : Invalid entry

• OceanBase error code: 4055

• Cause: An internal state exception.

• Solution: Contact technical support for assistance.

ERROR 4057 (HY000) : Decimal overflow warning

• OceanBase error code: 4057

• Cause: Data precision exceeds the limit.

• Solution: Reduce the precision of the input data.

ERROR 4058 (HY000) : Decimal overflow error

• OceanBase error code: 4058

• Cause: Data precision exceeds the limit.

• Solution: Reduce the precision of the input data.

ERROR 4060 (HY000) : Divide error

• OceanBase error code: 4060

• Cause: Division error.

• Solution: Contact technical support for assistance.

ERROR 4061 (HY000) : Not a decimal

• OceanBase error code: 4061

• Cause: Type error.

• Solution: Contact technical support for assistance.

ERROR 4062 (HY104) : Decimal precision error

• OceanBase error code: 4062

• Cause: Number precision issue.

• Solution: Contact technical support for assistance.

ERROR 4063 (HY000) : Empty range

• OceanBase error code: 4063

• Cause: Failed to obtain the query range for the LIKE condition.

• Solution: Contact technical support for assistance.

Related issues:

• View access exception in nested synonym scenarios

ERROR 4064 (HY000) : Session killed

• OceanBase error code: 4064

• Error cause: The session was terminated.

• Solution: Contact the system administrator or database administrator.

ERROR 4065 (HY000) : Log not sync

• OceanBase error code: 4065

• Error cause: Replica logs are out of sync.

• Solution: Contact technical support for assistance.

ERROR 4068 (HY000) : Invalid log

• OceanBase error code: 4068

• Error cause: The log is invalid.

• Solution: Contact technical support for assistance.

ERROR 4070 (HY000) : Invalid data

• OceanBase error code: 4070

• Error cause: The data is invalid.

• Solution: Contact technical support for assistance.

Related issues:

• OBServer startup failure, error code 4070
• OceanBase error: read info block data failed(ret=-4070)

ERROR 4071 (HY000) : Already done

• OceanBase error code: 4071

• Error cause: The operation is already completed.

• Solution: Contact technical support for assistance.

ERROR 4072 (HY000) : Operation canceled

• OceanBase error code: 4072

• Error cause: The operation was canceled.

• Solution: Contact technical support for assistance.

ERROR 4074 (HY000) : Log not aligned

• OceanBase error code: 4074

• Error cause: The logs are not aligned.

• Solution: Contact technical support for assistance.

ERROR 4075 (HY000) : Log entry missed

• OceanBase error code: 4075

• Error cause: The log could not be found.

• Solution: Contact technical support for assistance.

ERROR 4076 (HY000) : Need wait

• OceanBase error code: 4076

• Error cause: Waiting is required.

• Solution: Contact technical support for assistance.

ERROR 4077 (0A000) : Not implemented feature

• OceanBase error code: 4077

• Error cause: The feature is not implemented.

• Solution: Contact technical support for assistance.

Related issue cases:

• Error using nlssort: -4077, unsupported feature

ERROR 4080 (HY013) : exceed memory limit

• OceanBase error code: 4080

• Error cause: An internal error code. It is primarily used to determine the condition for persisting intermediate results of SQL operators.

• Solution: Memory exhaustion can occur in various scenarios. You must first identify the cause of the memory exhaustion.

Related issues:

• Cause of OB_EXCEED_MEM_LIMIT error code 4080
• Error "easy exceed memory limit" for OceanBase cluster memory exhaustion

ERROR 4084 (02000) : No result

• OceanBase error code: 4084

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

• Solution: Contact Technical Support for assistance.

ERROR 4085 (HY000) : Queue overflow

• OceanBase error code: 4085

• Cause: Queue length overflow.

• Solution: Contact Technical Support for assistance.

ERROR 4090 (HY000) : Table log_id range no continuous

• OceanBase error code: 4090

• Cause: The log ranges between SSTables within a partition are not continuous.

• Solution: Contact Technical Support for assistance.

ERROR 4098 (HY000) : Term not match

• OceanBase error code: 4098

• Cause: Replica proposal_id does not match.

• Solution: Contact Technical Support for assistance.

ERROR 4103 (42000) : Data checksum error

• OceanBase error code: 4103

• Cause: A data checksum error occurred.

• Solution: Contact OceanBase Technical Support for troubleshooting.

Related issues:

• Inconsistent replica checksum data caused by purge concurrency
• Major compaction error, error code 4103
• checksum error ret=-4103

ERROR 4104 (HY000) : Initialize error

• OceanBase error code: 4104

• Cause: Initialization failed.

• Solution: Contact technical support for assistance.

ERROR 4105 (HY000) : Rowkey order error

• OceanBase error code: 4105

• Cause: Primary key sorting error.

• Solution: Contact technical support for assistance.

ERROR 4107 (HY000) : block switched when fill commitlog

• OceanBase error code: 4107

• Cause: The buffer used by Group Commit needs to be switched.

• Solution: Contact technical support for assistance.

ERROR 4108 (HY000) : Physic data checksum error

• OceanBase error code: 4108

• Cause: Physical data checksum error, possibly due to disk media failure or a program bug.

• Solution: Check for hardware issues or contact technical support for troubleshooting.

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

• OceanBase error code: 4109

• Cause: State mismatch.

• Solution: Contact technical support for assistance.

ERROR 4111 (HY000) : block need freeze

• OceanBase error code: 4111

• Cause: Block needs to be frozen.

• Solution: Contact technical support for assistance.

ERROR 4112 (HY000) : block frozen

• OceanBase error code: 4112

• Cause: The block has been frozen.

• Solution: Contact technical support for assistance.

ERROR 4113 (HY000) : In FATAL state

• OceanBase error code: 4113

• Cause: The state is invalid.

• Solution: Contact technical support for assistance.

ERROR 4114 (08S01) : In STOP state

• OceanBase error code: 4114

• Cause: The OBServer node is already in the stop process.

• Solution: If this error persists for a long time, contact technical support for assistance.

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

• OceanBase error code: 4119

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

• Solution: Contact technical support for assistance.

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 technical support for assistance.

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 technical support for assistance.

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 technical support for assistance.

Related issues:

• Slow system login caused by using temporary tables
• DBLINK error -4152, null value when accessing remote tables

ERROR 4154 (HY000) : Internal SQL client error

• OceanBase error code: 4154

• Cause: An internal SQL client error occurred.

• Solution: Contact technical support for assistance.

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 technical support for assistance.

Related issues:

• An error occurred during a PL call. Error code: 4161 or OBE-00600 -->

ERROR 4162 (HY000) : reserved lease not enough

• OceanBase error code: 4162

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

• Solution: Contact technical support for assistance.

ERROR 4165 (HY000) : Empty result

• OceanBase error code: 4165

• Error cause: The result set is empty.

• Solution: Contact technical support for assistance.

ERROR 4168 (HY000) : Invalid log module id

• OceanBase error code: 4168

• Cause: The log module ID is invalid.

• Solution: Contact technical support for assistance.

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

• Error code in OceanBase Database: 4169

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

• Solution: Contact technical support for assistance.

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

• Error code in OceanBase Database: 4170

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

• Solution: Contact technical support for assistance.

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

• Error code in OceanBase Database: 4171

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

• Solution: Contact technical support for assistance.

ERROR 4172 (HY000) : Index out of range

• Error code in OceanBase Database: 4172

• Cause: The index is out of range.

• Solution: Contact technical support for assistance.

ERROR 4175 (42000) : Out of range

• Error code in OceanBase Database: 4175

• Cause: The value is out of range.

• Solution: Contact technical support for assistance.

ERROR 4177 (42000) : Schema version too old

• Error code in OceanBase Database: 4177

• Cause: The local schema version is outdated.

• Solution: Contact technical support for assistance.

ERROR 4179 (HY000) : %s not allowed

• Error code in OceanBase Database: 4179

• Cause: The feature is not supported.

• Solution: Contact technical support for assistance.

Related issues:

• An error occurred while stopping the OBServer node. Error code: 4179
• An error occurred while modifying the locality of a tenant during an upgrade. Error code: 4179 (not allowed)
• Failed to modify the primary zone. Error code: 4179
• An error occurred while creating a standby cluster by using OCP. Error code: 4179
• An error occurred while performing a restore. Error code: 4179
• After a manual rollback upon a cluster upgrade failure, an error occurred while performing a restore job. Error code: 4179
• An error occurred while creating a table by using the CTAS statement in a MySQL tenant. Error code: 4179
• An error occurred while dropping a column during a major compaction for a cluster. Error code: 4179
• Failed to change a non-partitioned table to a partitioned table
• Error message "table and tablegroup use different partition options not allowed" is returned -->

ERROR 4180 (HY000) : No empty entry

• OceanBase error code: 4180

• Cause: The corresponding data item is not null.

• Solution: Contact technical support for assistance.

ERROR 4181 (42S01) : Already exist

• OceanBase error code: 4181

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

• Solution: Contact technical support for assistance.

ERROR 4182 (HY000) : Value not found

• OceanBase error code: 4182

• Cause: The value was not found.

• Solution: Contact technical support for assistance.

ERROR 4183 (HY000) : Key out of range

• OceanBase error code: 4183

• Cause: The key is out of range.

• Solution: Contact technical support for assistance.

ERROR 4184 (53100) : ChunkServer out of disk space

• OceanBase error code: 4184

• Cause: The disk is full.

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

Related issues:

• Error message "Fail to alloc data block, (ret=-4184)" is printed in the logs of OceanBase Database
• Error message "4184: ChunkServer out of disk space" is printed in the logs
• An error occurred during backup for an OceanBase cluster. Error code: 4184 (exit)
• An error indicating insufficient disk space is returned for an SQL query. Error code: 4184 -->

ERROR 4185 (HY000) : Column group '%.*s' not found

• OceanBase error code: 4185

• Cause: The specified column group was not found.

• Solution: Verify whether the name of the specified column group is correct. Make sure that this column group exists or enter a correct column group name.

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

• OceanBase error code: 4186

• Cause: The compression library was not found.

• Solution: Contact technical support for assistance.

ERROR 4187 (HY000) : Item not match

• OceanBase error code: 4187

• Cause: A value mismatch occurred.

• Solution: Contact technical support for assistance.

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

• OceanBase error code: 4189

• Cause: The macro block type does not exist.

• Solution: Contact technical support for assistance.

ERROR 4191 (HY000) : partition group is removed

• OceanBase error code: 4191

• Cause: The partition has been deleted.

• Solution: No action is required.

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

• Error code in OceanBase Database: 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 technical support for assistance.

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

• OceanBase error code: 4201

• Cause: The HASH value does not exist.

• Solution: Contact technical support for assistance.

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

• OceanBase error code: 4204

• Cause: The HASH operation times out.

• Solution: Contact technical support for assistance.

ERROR 4205 (HY000) : hash map/set retry

• OceanBase error code: 4205

• Error cause: The HASH operation needs to be retried.

• Solution: Contact technical support for assistance.

ERROR 4206 (HY000) : hash map/set full

• OceanBase error code: 4206

• Cause: The HashMap instance is full.

• Solution: Contact technical support for assistance.

ERROR 4208 (HY000) : wait next packet timeout

• OceanBase error code: 4208

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

• Solution: Contact technical support for assistance.

ERROR 4209 (HY000) : partition has not leader

• OceanBase error code: 4209

• Cause: The partition has no leader.

• Solution: Contact technical support for assistance.

ERROR 4210 (HY000) : prepare major freeze failed

• OceanBase error code: 4210

• Cause: The preparation for a major compaction failed.

• Solution: Contact technical support for assistance.

ERROR 4211 (HY000) : commit major freeze failed

• OceanBase error code: 4211

• Cause: The commit of a major freeze failed.

• Solution: Contact technical support for assistance.

ERROR 4212 (HY000) : abort major freeze failed

• OceanBase error code: 4212

• Cause: The rollback of a major freeze failed.

• Solution: Contact technical support for assistance.

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 technical support for assistance.

ERROR 4216 (HY000) : curl error

• OceanBase error code: 4216

• Cause: A libcurl access error occurred.

• Solution: Contact technical support for assistance.

Related issues:

• OBServer startup error: -4216, call web service failed
• OCP cluster creation error, error code 4216

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.

Related issues:

• Unable to perform major compaction, error code 4217

ERROR 4218 (HY000) : prepare freeze failed

• OceanBase error code: 4218

• Error cause: Preparation for freeze failed.

• Solution: Contact technical support for assistance.

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

• OceanBase error code: 4220

• Error cause: Invalid SQL client.

• Solution: Contact technical support for assistance.

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

• OceanBase error code: 4221

• Error cause: RPC client not initialized.

• Solution: Contact technical support for assistance.

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

• OceanBase error code: 4222

• Error cause: Time type conversion error.

• Solution: Contact technical support for assistance.

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

• OceanBase error code: 4223

• Error cause: Time type conversion error.

• Solution: Contact technical support for assistance.

ERROR 4225 (HY000) : Partition entry not exists

• OceanBase error code: 4225

• Error cause: Partition does not exist.

• Solution: Contact technical support for assistance.

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

• OceanBase error code: 4232

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

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

ERROR 4233 (HY000) : smaller than container lower bound

• OceanBase error code: 4233

• Cause: Less than the lower bound of the container.

• Solution: Please contact technical support for assistance.

ERROR 4234 (HY000) : bigger than container upper bound

• OceanBase error code: 4234

• Cause: Greater than the upper bound of the container.

• Solution: Please contact technical support for assistance.

ERROR 4236 (HY000) : ObConfig return error code

• OceanBase error code: 4236

• Cause: OceanBase Database encountered an error when accessing ConfigServer.

• Solution: Check the obconfig_url parameter to determine whether ConfigServer 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 in the Config Server content does not match the actual cluster name.

• Solution: Check the obconfig_url parameter and contact technical support for assistance.

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

• OceanBase error code: 4239

• Cause: Kernel error.

• Solution: Contact technical support for assistance.

ERROR 4240 (HY000) : No join order generated

• OceanBase error code: 4240

• Cause: Kernel error.

• Solution: Contact technical support for assistance.

ERROR 4241 (HY000) : No join path generated

• OceanBase error code: 4241

• Cause: Kernel error.

• Solution: Contact technical support for assistance.

ERROR 4242 (HY000) : Schema error

• OceanBase error code: 4242

• Cause: The executor failed to obtain the schema.

• Solution: Contact technical support for assistance.

ERROR 4243 (HY000) : file not opened

• OceanBase error code: 4243

• Cause: The file was not opened.

• Solution: Contact technical support for assistance.

ERROR 4244 (HY000) : Timer task has been scheduled

• OceanBase error code: 4244

• Error cause: A timer task has already been registered.

• Solution: Contact technical support for assistance.

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

• OceanBase error code: 4245

• Error cause: No timer task has been registered.

• Solution: Contact technical support for assistance.

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 technical support for assistance.

ERROR 4247 (HY000) : unknown debug sync point

• OceanBase error code: 4247

• Error cause: The debug sync point does not exist.

• Solution: Contact technical support for assistance.

ERROR 4248 (HY000) : task is interrupted while running

• OceanBase error code: 4248

• Error cause: The distributed execution scheduler was interrupted and exited prematurely.

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

ERROR 4250 (HY000) : module is not running

• OceanBase error code: 4250

• Error cause: The module has not been started.

• Solution: Contact technical support for assistance.

ERROR 4251 (HY000) : partition not valid

• OceanBase error code: 4251

• Error cause: Invalid partition.

• Solution: Contact technical support for assistance.

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: Reduce the length of 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 DBA to check hardware issues, replace faulty machines, or perform data recovery.

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 technical support for assistance.

Related issue cases:

• OB_MINOR_FREEZE_NOT_ALLOW(-4263)
• Minor compaction failed, with the error message "Minor freeze not allowed now" returned
• Too many frozen memtables ret=-4263 -->

ERROR 4264 (HY000) : Log out of disk space

• OceanBase error code: 4264

• Cause: The log disk is fully occupied.

• Solution: Contact technical support for assistance.

Related issue case:

• Error 4264 reported when the disk usage of the OBServer server log directory exceeds the limit

ERROR 4265 (HY000) : Rpc connect error

• OceanBase error code: 4265

• Error cause: RPC connection establishment failed.

• Solution: Contact technical support for assistance.

ERROR 4266 (HY000) : minor merge not allow

• OceanBase error code: 4266

• Error cause: Minor compaction is temporarily not allowed.

• Solution: Contact technical support for assistance.

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

• OceanBase error code: 4270

• Error cause: The partition status is abnormal.

• Solution: Contact technical support for assistance.

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 technical support for assistance.

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

• OceanBase error code: 4273

• Error cause: There are insufficient free memory blocks in the cache.

• Solution: Try adjusting the memory or reducing the load, or contact technical support for assistance.

Related issue cases:

• can not find enough memory block to wash
• OBServer log error -4273

ERROR 4274 (HY000) : sync wash memblock timeout

• OceanBase error code: 4274

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

• Solution: Contact technical support for assistance.

ERROR 4278 (HY000) : last log is not complete

• OceanBase error code: 4278

• Cause: The last log is incomplete, possibly due to a power failure or sudden fault.

• Solution: Restart the OBServer, or contact technical support for assistance.

ERROR 4279 (HY000) : table is deleted

• OceanBase error code: 4279

• Cause: The table has already been deleted.

• Solution: Check if the SQL statement accesses a deleted table.

ERROR 4280 (HY000) : version range not continues

• OceanBase error code: 4280

• Cause: The version range is not continuous.

• Solution: Contact technical support for assistance.

ERROR 4281 (HY000) : io buffer is invalid

• OceanBase error code: 4281

• Cause: The IO buffer is invalid.

• Solution: Contact technical support for assistance.

ERROR 4282 (HY000) : partition is removed

• OceanBase error code: 4282

• Cause: The partition has already been deleted.

• Solution: Check if you operated on a deleted partition, or contact technical support for assistance.

ERROR 4283 (HY000) : gts is not ready

• OceanBase error code: 4283

• Cause: The GTS service is not ready yet.

• Solution: Contact technical support for assistance.

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

• OceanBase error code: 4286

• Cause: The baseline has been merged.

• Solution: Contact technical support for assistance.

ERROR 4287 (HY000) : minor sstable version range cross

• OceanBase error code: 4287

• Cause: Version ranges of SSTables have an intersection.

• Solution: Contact technical support for assistance.

ERROR 4288 (HY000) : memtable cannot minor merge

• OceanBase error code: 4288

• Cause: A minor compaction of the MemTable failed.

• Solution: Contact technical support for assistance.

ERROR 4289 (HY000) : task exist

• OceanBase error code: 4289

• Cause: Duplicate task.

• Solution: Contact technical support for assistance.

ERROR 4290 (HY000) : cannot allocate disk space

• OceanBase error code: 4290

• Cause: Insufficient disk space.

• 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: Change the object name to one that is not used by any object in the namespace.

ERROR 4298 (HY000) : %s does not exist

• OceanBase error code: 4298

• Compatible MySQL error code: 4298

• Cause: The specified sequence does not exist.

• Solution: Make sure that the sequence name is correct, and that you have the privilege to perform required operations on this sequence.

ERROR 4300 (HY000) : invalid sequence name

• OceanBase error code: 4300

• Cause: The specified sequence name is invalid.

• Solution: Rename the sequence.

ERROR 4301 (HY000) : duplicate MAXVALUE/NOMAXVALUE specifications

• OceanBase error code: 4301

• Cause: Duplicate MAXVALUE or NOMAXVALUE settings exist.

• Solution: Remove the duplicate MAXVALUE or NOMAXVALUE.

ERROR 4302 (HY000) : duplicate MINVALUE/NOMINVALUE specifications

• OceanBase error code: 4302

• Cause: Duplicate MINVALUE or NOMINVALUE settings exist.

• Solution: Remove the duplicate MINVALUE or NOMINVALUE.

ERROR 4303 (HY000) : duplicate CYCLE/NOCYCLE specifications

• OceanBase error code: 4303

• Cause: Duplicate CYCLE or NOCYCLE settings exist.

• Solution: Remove the duplicate CYCLE or NOCYCLE.

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: Remove the conflicting MAXVALUE or NOMAXVALUE definition.

ERROR 4307 (HY000) : conflicting MINVALUE/NOMINVALUE specifications

• OceanBase error code: 4307

• Cause: Conflicting MINVALUE or NOMINVALUE settings exist.

• Solution: Remove the conflicting MINVALUE or NOMINVALUE definition.

ERROR 4308 (HY000) : conflicting CYCLE/NOCYCLE specifications

• OceanBase error code: 4308

• Cause: Conflicting CYCLE or NOCYCLE settings exist.

• Solution: Remove the conflicting CYCLE or NOCYCLE definition.

ERROR 4309 (HY000) : conflicting CACHE/NOCACHE specifications

• OceanBase error code: 4309

• Cause: Conflicting CACHE or NOCACHE settings exist.

• Solution: Remove the conflicting CACHE or NOCACHE definition.

ERROR 4310 (HY000) : conflicting ORDER/NOORDER specifications

• OceanBase error code: 4310

• Cause: Conflicting ORDER or NOORDER settings exist.

• Solution: Remove the conflicting ORDER or NOORDER.

ERROR 4311 (HY000) : cannot alter starting sequence number

• OceanBase error code: 4311

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

• Solution: Do not change the START WITH value.

ERROR 4312 (HY000) : duplicate INCREMENT BY specifications

• OceanBase error code: 4312

• Cause: INCREMENT BY is repeatedly defined.

• Solution: Remove the duplicate INCREMENT BY.

ERROR 4313 (HY000) : duplicate START WITH specifications

• OceanBase error code: 4313

• Cause: START WITH is repeatedly defined.

• Solution: Remove the duplicate START WITH.

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

• OceanBase error code: 4314

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

• Solution: A statement without any options is meaningless.

ERROR 4315 (HY000) : sequence number not allowed here

• OceanBase error code: 4315

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

• Solution: Remove the auto-increment columns.

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: Ensure the auto-increment column name is correct and you have the necessary permissions to execute the operation.

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

• OceanBase error code: 4317

• Cause: Parameters in the CREATE SEQUENCE or ALTER SEQUENCE statement must be integers.

• 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 nonzero integer

• OceanBase error code: 4318

• Cause: The value of INCREMENT must be a non-zero integer.

• Solution: Specify a non-zero integer value for INCREMENT.

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

• OceanBase error code: 4319

• Cause: The parameter value of the auto-increment column exceeds the allowed maximum value.

• 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 must be less than the value of MAXVALUE.

• Solution: Specify a value for MINVALUE that is less than the value 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 must be less than the difference between MAXVALUE and MINVALUE.

• Solution: Specify a value for INCREMENT that is less than the difference between MAXVALUE and MINVALUE.

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 cannot be less than the value of MINVALUE.

• Solution: Ensure that the value of START WITH is not less than the value of MINVALUE.

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

• OceanBase error code: 4323

• Error cause: The given value for MINVALUE is greater than the current value.

• Solution: Ensure that the minimum value MINVALUE is less than the current value.

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

• OceanBase error code: 4324

• Error cause: The value of START WITH is greater than the value of MAXVALUE.

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

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

• OceanBase error code: 4325

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

• Solution: Ensure that the maximum value 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

• Error cause: The value of the parameter in the CACHE clause must be greater than 1.

• Solution: Specify a value for the parameter in the CACHE clause that is greater than 1.

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

• OceanBase error code: 4327

• Error cause: A parameter in a CREATE SEQUENCE or ALTER SEQUENCE statement is out of range.

• Solution: Specify a parameter value within the valid range.

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 length or cache fewer values.

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

• OceanBase error code: 4329

• Cause: A descending auto-increment column must have a specified MINVALUE.

• Solution: Recreate the sequence with a specified MINVALUE.

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

• OceanBase error code: 4330

• Cause: An ascending auto-increment column must have a specified MAXVALUE.

• Solution: Recreate the sequence with a specified MAXVALUE.

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

• OceanBase error code: 4331

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

• Solution: Recreate the 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: Change the auto-increment column so that new values can be requested.

ERROR 4333 (HY000) : divisor is equal to zero

• OceanBase error code: 4333

• Cause: The divisor is equal to zero.

• Solution: Contact technical support for assistance.

ERROR 4334 (HY000) : fail to decrypt data

• OceanBase error code: 4334

• Cause: Decryption failed.

• Solution: Contact technical support for assistance.

Related issues:

• OceanBase Database Error ret=-4334

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: Failed to store the directory structure.

• Solution: Contact OceanBase Technical Support for troubleshooting.

Related Issues:

• Failed to start the OBServer node. Error code: 4337
• Error message "4377, message loop is interrupted" is returned during PDML execution
• An error occurred while executing the UPDATE statement. Error code: 4377
• Error message "fatal internal error" is returned during the execution of the DELETE statement in OceanBase Database in MySQL-compatible mode
• A correctness error occurred while executing a DML operation on a table with a full-text index. Error code: 4337
• A correctness error occurred in a PDML scenario with multiple tables -->

ERROR 4338 (HY000) : open twice

• OceanBase Error Code: 4338

• Cause: File opened repeatedly.

• 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: Not opened.

• Solution: Contact OceanBase Technical Support for troubleshooting.

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

• OceanBase error code: 4341

• Cause: The weak-consistency read service is not started.

• Solution: Contact technical support for assistance.

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

• OceanBase error code: 4342

• Cause: The disk status is abnormal.

• Solution: Contact technical support for assistance.

ERROR 4343 (HY000) : tenant schema is not full

• OceanBase error code: 4343

• Cause: The local tenant schema version is outdated.

• Solution: Contact technical support for assistance.

Related issue cases:

• Error -4006/-4343 during major compaction

ERROR 4344 (HY000) : invalid timestamp

• OceanBase error code: 4344

• Cause: The timestamp is invalid.

• Solution: Enter a valid timestamp.

ERROR 4345 (HY000) : dir not empty

• OceanBase error code: 4345

• Cause: The directory is not empty.

• Solution: Check whether the installation directory of OceanBase is correct.

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

• OceanBase error code: 4346

• Cause: The local schema version is outdated.

• Solution: Contact technical support for assistance.

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

• OceanBase error code: 4347

• Cause: The specified ROLE does not exist.

• Solution: Ensure the ROLE name you are using is correct.

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

• OceanBase error code: 4348

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

• Solution: Use a different name.

ERROR 4349 (HY000) : duplicate privilege listed

• OceanBase error code: 4349

• Cause: Duplicate privileges or ROLE were specified in the GRANT or REVOKE statement.

• Solution: Remove the duplicate privileges or ROLE.

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

• OceanBase error code: 4350

• Cause: The Keystore already exists. A tenant can create only one Keystore.

• Solution: Check whether a Keystore has already been created.

ERROR 4351 (HY000) : the keystore is not exist

• OceanBase error code: 4351

• Cause: The Keystore does not exist.

• Solution: Check whether a Keystore has already been created.

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

• OceanBase error code: 4352

• Cause: The password for the Keystore is incorrect.

• Solution: Use the correct password.

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

• OceanBase error code: 4353

• Cause: You attempt to create a tablespace that already exists.

• Solution: Create a new tablespace with a different name.

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

• OceanBase error code: 4354

• Cause: The tablespace does not exist.

• Solution: Check whether you are accessing a non-existent tablespace.

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

• OceanBase error code: 4355

• Cause: A non-empty tablespace cannot be deleted.

• Solution: Ensure the tablespace is empty before deleting it.

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

• OceanBase error code: 4356

• Cause: The data precision of the BINARY_DOUBLE type exceeds the limit.

• Solution: Reduce the precision.

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

• OceanBase error code: 4357

• Cause: The data precision of the NUMBER type exceeds the limit.

• Solution: Reduce the precision.

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

• OceanBase error code: 4358

• Cause: The data precision of the NUMBER type exceeds the limit.

• Solution: Reduce the precision.

ERROR 4359 (HY000) : the keystore is not open

• OceanBase error code: 4359

• Error 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

• Error cause: The master key does not exist.

• 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 technical support for assistance.

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

• OceanBase error code: 4362

• Error cause: The BY ACCESS or BY SESSION clause is not allowed in NOAUDIT.

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

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

• OceanBase error code: 4363

• Cause: Auditing this type of object is not supported.

• Solution: Contact technical support for assistance.

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

• OceanBase error code: 4364

• Cause: DDL statements cannot be audited using the BY SESSION method.

• Solution: Remove 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 needs to be split into finer granularity. This error code is returned to notify the execution scheduler to re-split and retry.

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

ERROR 4368 (HY000) : cluster %s not exist

• OceanBase error code: 4368

• Cause: An internal error occurred in the Config Server when accessing cluster information, indicating the cluster does not exist.

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

ERROR 4369 (HY000) : fail to get master key

• OceanBase error code: 4369

• Cause: Failed to obtain the master key.

• Solution: Contact technical support for assistance.

ERROR 4370 (HY000) : tde_method parameter is invalid

• OceanBase error code: 4370

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

• Solution: Check the value of tde_method.

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

• OceanBase error code: 4371

• Error cause: The KMS service connection failed.

• Solution: Check the availability of the KMS service.

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

• OceanBase error code: 4372

• Error cause: The KMS service is busy.

• Solution: Please try again.

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

• OceanBase error code: 4373

• Error cause: A conflict occurred during concurrent updates to the master key.

• Solution: Please try again.

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

• OceanBase error code: 4374

• Error cause: The precision of the value is greater than the precision defined for the field.

• Solution: Adjust the value or modify the field definition.

ERROR 4375 (HY000) : observer has disk error

• OceanBase error code: 4375

• Error cause: Storage disk failure.

• Solution: Check for disk failures and replace the corresponding server.

ERROR 4376 (HY000) : unimplemented feature

• OceanBase error code: 4376

• Error cause: OceanBase Database does not support this feature.

• Solution: Contact technical support for assistance.

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

• OceanBase error code: 4377

• Error cause: An unexpected internal error occurred in OceanBase Database, possibly due to abnormal program execution.

• Solution: Contact technical support for assistance in troubleshooting.

ERROR 4378 (HY000) : cluster name conflict

• OceanBase error code: 4378

• Error cause: Cluster name conflict.

• Solution: Set a different 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

• Error cause: Declaring a precise floating-point data type using float(m,d) / double(m,d).

• Solution: Use the fixed-point decimal(m,d) type instead of float(m,d) / double(m,d) to specify exact decimals.

ERROR 4383 (HY000) : transaction id is not ready

• OceanBase error code: 4383

• Error cause: The Transaction ID allocator has no available ID range.

• Solution: Retry to obtain an ID until timeout.

ERROR 4386 (HY000) : Do not allow removing leader

• OceanBase error code: 4386

• Cause: Internal error code. The migration source is a log replica leader and cannot be migrated.

• Solution: No action required.

ERROR 4387 (HY000) : Failed to switch resource group

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

• Solution: Contact technical support for assistance.

ERROR 4389 (HY000) : Processing time is too long

• OceanBase error code: 4389

• Cause: The task processing time is too long.

• Solution: Internal error code. If returned, contact technical support for assistance.

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 SSTable returns a cross version range.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4392 (HY000) : disk is hung

• Error code in OceanBase Database: 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 reported an error when the observer process exited.
• Solution: Contact technical support for assistance.

ERROR 4395 (HY000) : observice start process has failure

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

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

• Error code in OceanBase Database: 4399
• Cause: The tenant is migrated when you import data through direct load.
• 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

• Error code in OceanBase Database: 4400
• Cause: The version of the cached auto-increment column values is inconsistent with the requested version.
• Solution:
  1. Check the auto-increment column value version: Verify that the auto-increment column value version is correct and consistent with the requested version.
  2. Clear the auto-increment column value cache: Try clearing the auto-increment column value cache to regenerate the auto-increment column value.

ERROR 4401 (HY000) : Client Session need be killed

• OceanBase error code: 4401

• Error code in MySQL: 4401

• Cause: The client session was not terminated.

• Solution: Verify whether the client session needs to be terminated. If yes, terminate the session by taking proper measures, for example, using an appropriate command or tool.

ERROR 4402 (HY000) : Kill Client Session failed

• OceanBase error code: 4402

• Error cause: The operation to terminate the client session failed.

• Solution: Before attempting to terminate a session, ensure that the target 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.

ERROR 4408 (HY000) : Migrate tx data not continues

• oceanbase error code: 4408

• Cause: The transaction data table on the source side of the migration was recycled. During the copy process on the destination side, the transaction data table was found to be discontinuous, resulting in a failure and an error. A retry is attempted.

• Solution: In most cases, the issue can be resolved after a retry. If the problem persists, please contact OceanBase technical support for further assistance.