4000 ~ 4499

The error codes in this range are general error codes.

ERROR 4000 (HY000) : Common error

• OceanBase error code: 4000

• The reason for the error is a general error code.

• Resolution: Contact technical support for assistance in troubleshooting the issue.

Related cases:

• Error 4000: Explain the SQL error
• Group and Aggregation Pushdown Error Scenario 1

ERROR 4001 (HY004) : Object type error

• OceanBase error code: 4001

• Cause: Type mismatch.

• Resolution: Contact the technical support person for assistance.

ERROR 4003 (42000) : Array index out of range

• OceanBase error code: 4003

• Error: Subscript is out of bounds.

• Resolution: Contact technical support for assistance.

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

• OceanBase error code: 4004

• Reason for error: Listening services failed to start because the network connection was disconnected.

The resolution is to restart the observer process after you change the idle port.

ERROR 4005 (HY000) : The object is initialized twice

• OceanBase error code: 4005

• The cause of the error is duplicate object initialization.

• Resolution: Contact Huawei Customer Service.

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

• OceanBase Database Error Code: 5388

• Incompatible with MySQL error codes: 4005.

• Cause: The operation generates an orphaned object or inherits an orphaned object.

• Solution: Check your permissions, or delete the object.

ERROR 4006 (HY000) : The object is not initialized

• OceanBase error code: 4006

• The error is caused by the object not being initialized.

• Resolution: Contact the technical support team to troubleshoot the issue.

Sample use cases:

• Error -4006/-4343 on merge

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

• OceanBase Database error code: 5389

• Compatible with the MySQL error code: 4006

• Error: an orphaned object is created during user operation or inherited.

• Resolution: Delete the corresponding object.

ERROR 4008 ( HY000 ) : End of iteration

• OceanBase error code: 4008

• Cause: The iteration ended.

• Resolution: Contact technical support for further troubleshooting.

ERROR 4009 (58030 ) : IO error

• OceanBase Error 4009:

• Error Cause: System calls related to IO operations (such as READ or WRITE) have failed.

• Solution: Please contact technical support for further assistance.

Related case:

• OBServer fails to start, error code 4009.
• OBServer failed to start with error code 4009
• Unable to clean up historical backup files, error -4009 is returned

ERROR 4010 (HY000) : Wrong RPC command version

• OceanBase error code: 4010

• Error: An invalid RPC version is specified.

• Solution: Contact technical support for further 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 Database error: 4012

• Cause: Execution timeout.

• Solution:

  • Performance tuning can reduce time consumption.

  • Increase the timeout value.

  • Contact Technical Support for further assistance.

Case Study:

• Bootstrap fails with error code 4012
• Failed to change tenant Locality, and the major compaction times out
• mysqldump tool exporting data error, error code 4012
• Merge timeout and SQL execution timeout caused by disk failure
• ORA-5150 Error Occurs When You Query DBA_OB_LS_LOCATIONS in a Common User
• OceanBase Database reports a timeout error or hangs while the error 4012 is returned

ERROR 4012 (HY000) : Task timeout and not executed

• OceanBase error code: 4049

• MySQL-compliant error code: 4012

ERROR 4012 (HY000) : RPC session not found

• OceanBase error code: 4067

• Compatible with MySQL error code: 4012

ERROR 4012 (HY000) : RPC send error

• OceanBase error code: 4121

• Complies with 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 compatible error code: 4012

  Note

  • This field is introduced in V4.3.3 for V4.3.x.
  • This field is introduced in V4.2.5 for V4.2.x.

ERROR 4012 (HY000) : Timeout

• OceanBase error code: 4664

• MySQL compatible error code: 4012

Related issues:

• Analyze large wide tables is slow and the tenant memory is exhausted
• The primary and standby databases are synchronized, but switchover fails after multiple retries
• Data backup fails with error code -4012

ERROR 4012 (HY000) : Statement is timeout

• OceanBase error code: 6004

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

Related issues:

• Transaction timeout, error code ERROR 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 compatible error code: 4012

ERROR 4012 (25000) : Transaction result is unknown

• OceanBase error code: 6225

• MySQL compatible error code: 4012

ERROR 4012 (25000) : transaction rpc timeout

• OceanBase error code: 6230

• MySQL compatible error code: 4012

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

• OceanBase error code: 4013

• Error reason: The memory allocation failed.

  • The physical memory is exhausted.
  • The memory allocated in one operation exceeds 4 GB.
  • The memory usage of CTX, tenant, or server reaches the upper limit.

• Solution: Contact Technical Support.

Related issues:

• The I/O memory is insufficient when an OBServer node starts.
• Error 4013 occurs during the execution of the IO step of the benchmark test on an ARM server.
• The standby cluster does not respond in the primary-standby cluster architecture, and error code 4013 is returned.
• The work memory is insufficient, and error code 4013 is returned.
• Error -4013 is returned when the memory allocated exceeds 4 GB.
• Error -4013 is returned when a transaction exceeds the limit in the UDF scenario.
• The ob_micro_block_cache module returns the error message: failed to allocate value, -4013.
• What is the difference between error codes 4013 and 4030 in OceanBase Database?
• SQL execution returns error code 4013, and the memory usage of the tenant increases rapidly.
• The sqlexecuter module has a memory leak.
• OBServer returns the error message: record concurrent fifoallocator alloc mem failed(total_size=1793,ret=-4013).
• The execution returns error code -4013 because of memory fragmentation in the PS block.
• Analyze large wide tables is slow and the tenant memory is exhausted.
• The SQL parsing phase returns error code -4013, and the tenant memory is exhausted.
• The execution of the UDF returns error code -4013.
• The vm.max_map_count parameter is improperly configured, which may cause serious memory leaks.
• The tenant memory is exhausted because of high memory write speed.
• The standby cluster does not respond in the primary-standby cluster architecture, and error code 4013 is returned.

ERROR 4014 (HY000) : Inner state error

• OceanBase error code: 4014

• Error reason: The internal state is abnormal.

• Solution: Contact Technical Support.

ERROR 4015 (HY000) : System error

• OceanBase error code: 4015

• Error reason: Internal error code.

• Solution: Contact OceanBase Technical Support for assistance.

Related issues:

• Bootstrap failed, error code 4015
• OBServer startup error: -4015, super block v1 size not match
• Handling of physical backup media full in OceanBase Database

ERROR 4016 (HY000) : Internal error

• OceanBase error code: 4016

• Error reason: Internal error code.

• Solution: Contact OceanBase Technical Support for assistance.

Related issues:

• OBServer startup failed, error code 4016
• Bootstrap failed, error code 4016 (cluster_id out of range)
• Error 4016 during Bootstrap (no qualified primary zone for system)
• OBServer restart failed, error code 4016
• Cluster dump failed with error -4016, and retries did not resolve the issue
• LLVM memory allocation failure caused PL call to core
• group_concat function error, error code 4016
• Time interval calculation error in MySQL mode, error code 4016
• Data table with index status unuseable/error failed to restore after backup
• ANALYZE TABLE error -4016
• PL case when statement execution error -4016
• sys_connect_by_path() function failed, error code OBE-00600
• Internal error when using to_number function on nchar in Oracle mode
• SQL execution error: ErrorCode = 4016, SQLState = HY000, Details = Internal error
• SQL query error: Internal error OBE-00600
• SQL execution error 4016 with multiple in and vector expressions
• query range extraction error 4016
• Recursive CTE execution error: -4016, internal error in Oracle tenant
• MySQL tenant SQL execution error: -4016, internal error
• Collation type inconsistency caused merge error -4016
• OBKV-Table queryAndAppend operation result did not meet expectations and client prefix query error
• Backup error 4016, backup meta data size exceeded
• NFS directory not mounted as required caused continuous log errors
• Log archiving cannot be stopped, error invalid archive_round
• Log archiving stuck in stopping state after stopping
• Physical restore error -4016
• locate_file_by_log_id operation error -4016 in OceanBase Database
• Restore failed with error -4016, last_restore_log_id mismatch

ERROR 4017 (HY000) : Entry already exist

• OceanBase error code: 4017

• Error reason: The data already exists.

• Solution: Contact OceanBase Technical Support for assistance.

Related issues:

• Hierarchy query error -4017 due to different parameter values

ERROR 4018 (HY000) : Entry not exist

• OceanBase error code: 4018

• Error reason: The data does not exist.

• Solution: Contact technical support for assistance.

Related issues:

• OBServer fails to start. The log shows: -4018, no complete log.
• An error occurs when you delete a server. Error code: 4018.
• Emergency methods for refreshing the location cache.
• After you upgrade the version, an error occurs when you restore a backup. Error code: 4018, archive_key file not exist.

ERROR 4019 (HY000) : Size overflow

• OceanBase error code: 4019

• Error reason: The space overflows.

• Solution: Contact technical support for assistance.

Related issues:

• log item too long ret=-4019
• The performance of parallel DML (PDML) is not as expected.
• The result set of the FROM_UNIXTIME function is different.

ERROR 4020 (HY000) : Reference count is not zero

• OceanBase error code: 4020

• Error reason: The reference count is not zero.

• Solution: Contact technical support for assistance.

ERROR 4021 (HY000) : Conflict value

• OceanBase error code: 4021

• Error reason: A logical error occurs in the base database, which is generally caused by a code error.

• Solution: Contact technical support for assistance.

ERROR 4022 (HY000) : Item not set

• OceanBase error code: 4022

• Error reason: The value is not set.

• Solution: Contact technical support for assistance.

ERROR 4023 (HY000) : Try again

• OceanBase error code: 4023

• Error reason: The operation needs to be retried.

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

Related issues:

• The major compaction times out. Error code: 4023.
• OceanBase Database hangs when you create an index. The system returns an error -4023.

ERROR 4024 (HY000) : Buffer not enough

• OceanBase error code: 4024

• Error reason: The space is insufficient.

• Solution: Contact technical support for assistance.

Related issues:

• The SHOW PROXYSESSION statement returns an error. Error code: 4024.
• OceanBase Database returns an error -4024 when it is stuck during major compaction.
• The INSERT ALL statement returns an error -4024, Buffer not enough.

ERROR 4025 (HY000) : Partial failed

• OceanBase error code: 4025

• Error reason: In a batch task, some operations succeed and others fail.

• Solution: Contact technical support for assistance.

ERROR 4026 (02000) : Nothing to read

• OceanBase error code: 4026

• Error reason: No data is available for reading.

• Solution: Contact technical support for assistance.

Related issues:

• In the XA + nested SQL rollback scenario, the transaction scheduler context leaks.

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

• MySQL-compatible error code: 4027

• Error reason: User account %.*s@%.*s is directly or indirectly granted to role %.*s@%.*s, which creates a loop.

• Solution: Check the authorization relationships between user accounts and roles, and ensure that no loop exists.

ERROR 4028 (HY000) : Log entry not continuous

• OceanBase error code: 4028

• Error reason: The file IDs are not continuous.

• Solution: Contact technical support for assistance.

ERROR 4029 (HY000) : Schema error

• OceanBase error code: 4029

• Error reason: The schema cannot be obtained.

• Solution: Contact technical support for assistance.

Related issues:

• After you upgrade the database to V3.1.2, an error -4029 occurs. The primary and standby schema versions are different.

ERROR 4030 (HY000) : Over tenant memory limits

• OceanBase error code: 4030

• Error reason: The memory resources of the tenant are insufficient.

• Solution: Increase the memory resources of the tenant.

Related issues:

• Memory limit exceeded. Error code: 4030.
• After you restart three nodes of the SYS tenant, the RS node has no primary clog and returns an error ret=-4030.
• Differences between error codes 4013 and 4030 in OceanBase Database.
• Why does OceanBase Database return an error Over tenant memory limits when you insert data?

ERROR 4031 (HY004) : Unknown object

• OceanBase error code: 4031

• Error reason: The object is unknown.

• Solution: Contact technical support for assistance.

ERROR 4033 (HY000) : Serialize error

• OceanBase Database error code: 4033

• Error reason: The serialization failed.

• Solution: Contact OceanBase Technical Support.

ERROR 4034 (HY000) : Deserialize error

• OceanBase Database error code: 4034

• Error reason: The deserialization failed.

• Solution: Contact OceanBase Technical Support.

ERROR 4035 (HY000) : Asynchronous IO error

• OceanBase Database error code: 4035

• Error reason: The system call related to asynchronous I/O failed.

• Solution: Contact OceanBase Technical Support.

ERROR 4036 (HY000) : Need retry

• OceanBase Database error code: 4036

• Error reason: The operation needs to be retried.

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

ERROR 4037 (HY000) : Too many sstable

• OceanBase Database error code: 4037

• Error reason: Too many SSTables are generated. This is usually caused by frequent major compactions.

• Solution: Scale out the cluster to reduce the pressure on each server, or contact OceanBase Technical Support.

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

• OceanBase Database error code: 4038

• Error reason: The current partition does not provide services as the leader.

• Solution: Execute the current statement or transaction again.

Related issues:

• Location cache cannot be refreshed after an R replica is switched to the leader. Error 4038 is returned.

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

• OceanBase Database error code: 4039

• Error reason: The SQL statement is throttled.

• Solution: Contact OceanBase Technical Support.

ERROR 4041 (HY000) : Decrypt error

• OceanBase Database error code: 4041

• Error reason: The decryption failed.

• Solution: Contact OceanBase Technical Support.

ERROR 4045 (HY000) : pushdown status changed

• OceanBase Database error code: 4045

• Error reason: Internal error.

• Solution: Contact OceanBase Technical Support.

ERROR 4046 (HY000) : Storage schema is not valid

• OceanBase Database error code: 4046

• Error reason: The schema of the storage layer is invalid.

• Solution: Contact OceanBase Technical Support.

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

• OceanBase Database error code: 4047

• Error reason: The medium compaction information is invalid.

• Solution: Contact OceanBase Technical Support.

ERROR 4048 (HY000) : Not registered

• OceanBase Database error code: 4048

• Error reason: Internal error.

• Solution: Contact OceanBase Technical Support.

ERROR 4050 (HY000) : Not the object

• OceanBase Database error code: 4050

• Error reason: The object does not match.

• Solution: Contact OceanBase Technical Support.

ERROR 4052 (HY000) : Corrupted log entry

• OceanBase Database error code: 4052

• Error reason: The log entry is corrupted. This is usually caused by hardware or disk errors, which result in incorrect log data.

• Solution: Contact the DBA to troubleshoot the hardware issues, or contact OceanBase Technical Support.

ERROR 4055 (HY000) : Invalid entry

• OceanBase Database error code: 4055

• Error reason: Internal error.

• Solution: Contact OceanBase Technical Support.

ERROR 4057 (HY000) : Decimal overflow warning

• OceanBase Database error code: 4057

• Error reason: The data precision is exceeded.

• Solution: Reduce the precision of the input data.

ERROR 4058 (HY000) : Decimal overflow error

• OceanBase Database error code: 4058

• Error reason: The data precision is exceeded.

• Solution: Reduce the precision of the input data.

ERROR 4060 (HY000) : Divide error

• OceanBase Database error code: 4060

• Error reason: The division operation failed.

• Solution: Contact OceanBase Technical Support.

ERROR 4061 (HY000) : Not a decimal

• OceanBase Database error code: 4061

• Error reason: The data type is incorrect.

• Solution: Contact OceanBase Technical Support.

ERROR 4062 (HY104) : Decimal precision error

• OceanBase Database error code: 4062

• Error reason: The precision of the number is incorrect.

• Solution: Contact OceanBase Technical Support.

ERROR 4063 (HY000) : Empty range

• OceanBase Database error code: 4063

• Error reason: The query range of the LIKE condition cannot be obtained.

• Solution: Contact OceanBase Technical Support.

Related issues:

• A view cannot be accessed in a synonym nesting scenario.

ERROR 4064 (HY000) : Session killed

• OceanBase Database error code: 4064

• Error reason: The session is terminated.

• Solution: Contact the system administrator or database administrator.

ERROR 4065 (HY000) : Log not sync

• OceanBase Database error code: 4065

• Error reason: The logs of the replica are not synchronized.

• Solution: Contact OceanBase Technical Support.

ERROR 4068 (HY000) : Invalid log

• OceanBase Database error code: 4068

• Error reason: The log is invalid.

• Solution: Contact OceanBase Technical Support.

ERROR 4070 (HY000) : Invalid data

• OceanBase Database error code: 4070

• Error reason: The data is invalid.

• Solution: Contact OceanBase Technical Support.

Related issues:

• The OBServer node fails to start. Error code 4070 is returned.
• OceanBase Database returns an error: read info block data failed(ret=-4070).

ERROR 4071 (HY000) : Already done

• OceanBase Database error code: 4071

• Error reason: The operation is completed.

• Solution: Contact OceanBase Technical Support.

ERROR 4072 (HY000) : Operation canceled

• OceanBase Database error code: 4072

• Error reason: The operation was canceled.

• Solution: Contact OceanBase Technical Support for assistance.

ERROR 4074 (HY000) : Log not aligned

• OceanBase Database error code: 4074

• Error reason: The logs are not aligned.

• Solution: Contact OceanBase Technical Support for assistance.

ERROR 4075 (HY000) : Log entry missed

• OceanBase Database error code: 4075

• Error reason: The log entry is not found.

• Solution: Contact OceanBase Technical Support for assistance.

ERROR 4076 (HY000) : Need wait

• OceanBase Database error code: 4076

• Error reason: Waiting is required.

• Solution: Contact OceanBase Technical Support for assistance.

ERROR 4077 (0A000) : Not implemented feature

• OceanBase Database error code: 4077

• Error reason: The feature is not implemented.

• Solution: Contact OceanBase Technical Support for assistance.

Related case:

• Error -4077: The feature is not supported when nlssort is used

ERROR 4080 (HY013) : exceed memory limit

• OceanBase Database error code: 4080

• Error reason: An internal error code. It is mainly used for the condition judgment of whether to write the intermediate results of the SQL operator to the disk.

• Solution: There are multiple scenarios for exceeding the memory limit. You need to first identify the cause of the memory limit exceeded.

Related case:

• Cause of error code 4080: OB_EXCEED_MEM_LIMIT
• Error message: easy exceed memory limit is returned when the memory limit of an OceanBase cluster is exceeded

ERROR 4084 (02000) : No result

• OceanBase Database error code: 4084

• Error reason: The value of the configuration item is not found.

• Solution: Contact OceanBase Technical Support for assistance.

ERROR 4085 (HY000) : Queue overflow

• OceanBase Database error code: 4085

• Error reason: The queue length is exceeded.

• Solution: Contact OceanBase Technical Support for assistance.

ERROR 4090 (HY000) : Table log_id range no continuous

• OceanBase Database error code: 4090

• Error reason: The log ranges between SSTables in a partition are not continuous.

• Solution: Contact OceanBase Technical Support for assistance.

ERROR 4098 (HY000) : Term not match

• OceanBase Database error code: 4098

• Error reason: The proposal_id of the replica does not match.

• Solution: Contact OceanBase Technical Support for assistance.

ERROR 4103 (42000) : Data checksum error

• OceanBase Database error code: 4103

• Error reason: The data checksum is incorrect.

• Solution: Contact OceanBase Technical Support for assistance.

Related case:

• Data inconsistency in checksums of replicas caused by concurrent purges
• Merge error: error code 4103
• checksum error ret=-4103

ERROR 4104 (HY000) : Initialize error

• OceanBase Database error code: 4104

• Error reason: The initialization failed.

• Solution: Contact OceanBase Technical Support for assistance.

ERROR 4105 (HY000) : Rowkey order error

• OceanBase Database error code: 4105

• Error reason: The primary key order is incorrect.

• Solution: Contact OceanBase Technical Support for assistance.

ERROR 4107 (HY000) : block switched when fill commitlog

• OceanBase Database error code: 4107

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

• Solution: Contact OceanBase Technical Support for assistance.

ERROR 4108 (HY000) : Physic data checksum error

• OceanBase Database error code: 4108

• Error reason: The physical data checksum is incorrect. This could be due to a disk media failure or a program bug.

• Solution: Check whether the hardware is faulty. If not, contact OceanBase Technical Support for assistance.

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

• OceanBase Database error code: 4109

• Error reason: The server state or role is not as expected.

• Solution: Contact OceanBase Technical Support for assistance.

ERROR 4111 (HY000) : block need freeze

• OceanBase Database error code: 4111

• Error reason: The block needs to be frozen.

• Solution: Contact OceanBase Technical Support for assistance.

ERROR 4112 (HY000) : block frozen

• OceanBase Database error code: 4112

• Error reason: The block has been frozen.

• Solution: Contact OceanBase Technical Support for assistance.

ERROR 4113 (HY000) : In FATAL state

• OceanBase Database error code: 4113

• Error reason: The server state is invalid.

• Solution: Contact OceanBase Technical Support for assistance.

ERROR 4114 (08S01) : In STOP state

• OceanBase Database error code: 4114

• Error reason: The OBServer node is in the process of being stopped.

• Solution: If the error persists for a long time, contact OceanBase Technical Support for assistance.

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

• OceanBase Database error code: 4119

• Error reason: The RPC packet length exceeds the limit.

• Solution: Contact OceanBase Technical Support for assistance.

Related case:

• Error -4119: RPC packet to send too long is returned when an SQL statement is executed

ERROR 4120 (HY000) : Log too large

• OceanBase Database error code: 4120

• Error reason: The log is too large.

• Solution: Contact OceanBase Technical Support for assistance.

ERROR 4123 (08000) : Libeasy error

• OceanBase Database error code: 4123

• Error reason: The network initialization failed.

• Solution: Contact the system administrator or database administrator.

ERROR 4124 (HY000) : Connect error

• OceanBase Database error code: 4124

• Error reason: The server connection could not be established.

• Solution: Contact the system administrator or database administrator.

ERROR 4128 (HY000) : RPC packet is invalid

• OceanBase Database error code: 4128

• Error reason: The RPC packet format is incorrect.

• Solution: Contact the system administrator or database administrator.

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

• OceanBase Database error code: 4138

• Error reason: The data version is too old.

• Solution: Re-execute the statement or increase the undo_retention parameter.

Related issues:

• Dump error, error code 4138/OBE-01555

ERROR 4143 (42000) : Version not match

• OceanBase Database error code: 4143

• Error reason: The versions are inconsistent.

• Solution: Contact Technical Support.

ERROR 4147 (HY000) : Invalid config

• OceanBase Database error code: 4147

• Error reason: The configuration is invalid.

• Solution: Contact Technical Support.

Related issues:

• OBServer failed to load_ssl_config when starting

ERROR 4150 (42000) : Min value

• OceanBase Database error code: 4150

• Error reason: The minimum special value of an internal table is invalid.

• Solution: Contact Technical Support.

ERROR 4151 (42000) : Max value

• OceanBase Database error code: 4151

• Error reason: The maximum special value of an internal table is invalid.

• Solution: Contact Technical Support.

ERROR 4152 (42000) : Null value

• OceanBase Database error code: 4152

• Error reason: The null value of an internal table is invalid.

• Solution: Contact Technical Support.

Related issues:

• The system login is slow because of the use of temporary tables.
• DBLINK access to a remote table returns an error -4152, null value.

ERROR 4154 (HY000) : Internal SQL client error

• OceanBase Database error code: 4154

• Error reason: An internal error occurs in the SQL client.

• Solution: Contact Technical Support.

ERROR 4161 (42000) : Invalid argument num

• OceanBase Database error code: 4161

• Error reason: The number of arguments is invalid.

• Solution: Check the argument list or contact Technical Support.

Related issues:

• PL call error, error code 4161/OBE-00600

ERROR 4162 (HY000) : reserved lease not enough

• OceanBase Database error code: 4162

• Error reason: The reserved lease time is insufficient.

• Solution: Contact Technical Support.

ERROR 4165 (HY000) : Empty result

• OceanBase Database error code: 4165

• Error reason: The result set is empty.

• Solution: Contact Technical Support.

ERROR 4168 (HY000) : Invalid log module id

• OceanBase Database error code: 4168

• Error reason: The log module ID is invalid.

• Solution: Contact Technical Support.

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

• OceanBase Database error code: 4169

• Error reason: The log module name is invalid. The module name is incorrectly specified when the client sets the log level.

• Solution: Contact Technical Support.

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

• OceanBase Database error code: 4170

• Error reason: The log level is invalid. The log level is incorrectly specified when the client sets the log level.

• Solution: Contact Technical Support.

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

• OceanBase Database error code: 4171

• Error reason: The log level setting syntax is invalid. The log level is incorrectly specified when the client sets the log level.

• Solution: Contact Technical Support.

ERROR 4172 (HY000) : Index out of range

• OceanBase Database error code: 4172

• Error reason: The index is out of range.

• Solution: Contact Technical Support.

ERROR 4175 (42000) : Out of range

• OceanBase Database error code: 4175

• Error reason: The value is out of range.

• Solution: Contact Technical Support.

ERROR 4177 (42000) : Schema version too old

• OceanBase Database error code: 4177

• Error reason: The local schema version is outdated.

• Solution: Contact Technical Support.

ERROR 4179 (HY000) : %s not allowed

• OceanBase Database error code: 4179

• Error reason: The specified feature is not supported.

  The error can be caused by the following reasons:

  • The current log stream status does not allow the operation.

  • The status of the server that executes the task is abnormal.

  • The number of members in the member list reaches the upper limit.

  • The log stream replica does not exist on the specified data source.

  • The status of the server on the data source is not Alive.

  • The status of the server on the data source is Stop.

  • An R replica cannot be used as the data source for an F replica.

  • The restore of the replica on the data source fails.

  • Removing the replica will cause no primary replica.

  • The source and destination are not in the same zone.

  • In the homogeneous zone mode, you cannot modify the UNIT_NUM parameter of a resource pool to scale in or out.

  • In the homogeneous zone mode, the UNIT_NUM parameters of different resource pools are different. The UNIT_NUM parameters of all resource pools must be the same.

  • In the heterogeneous zone mode, the UNIT_NUM parameters of different resource pools under the same tenant are more than two. The UNIT_NUM parameters of all resource pools under the same tenant must be at most two.

  • During the scaling in or out of UNIT_NUM, you cannot modify the UNIT_NUM parameter to other values unless you perform a rollback.

  • During the scaling in or out of UNIT_NUM, you cannot modify the locality of the tenant.

  • During the scaling in or out of UNIT_NUM, you cannot expand the ZONE_LIST scope of the tenant resource pool.

  • During the scaling in or out of UNIT_NUM, you cannot add a new resource pool to the tenant.

  • During the scaling in or out of UNIT_NUM, you cannot merge resource pools.

  • During the scaling in or out of UNIT_NUM, you cannot migrate a unit in the DELETING state.

  • GTS is in exclusive mode. In this case, the UNIT_NUM parameter of each zone under the tenant cannot be less than 2. If GTS is in exclusive mode, the UNIT_NUM parameter of each zone under the tenant must be greater than or equal to 2.

  • GTS is in exclusive mode. In this case, you cannot specify to delete a unit or unit group in exclusive mode.

• Solution: Handle the error based on your business scenario or contact OceanBase Technical Support for troubleshooting.

Related cases:

• OBServer stops with error code 4179
• Error -4179 not allowed occurs when you modify the locality of a tenant during an upgrade
• Error 4179 occurs when you fail to modify the primary zone.
• Error 4179 occurs when you create a standby cluster through OCP.
• Error ERROR -4179 occurs when you restore data from OceanBase Database.
• After you manually roll back a failed cluster upgrade, the recovery task returns error -4179.
• Error 4179 occurs when you create a table by using the CTAS statement in a MySQL tenant.
• Error 4179 occurs when you delete a column during a cluster merge.
• You cannot convert a non-partitioned table to a partitioned table.
• Error table and tablegroup use different partition options not allowed occurs.

ERROR 4180 (HY000) : No empty entry

• OceanBase Database error code: 4180

• Error reason: The specified data item is not empty.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4181 (42S01) : Already exist

• OceanBase Database error code: 4181

• Error reason: The specified item already exists in the location cache.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4182 (HY000) : Value not found

• OceanBase Database error code: 4182

• Error reason: The specified value is not found.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4183 (HY000) : Key out of range

• OceanBase Database error code: 4183

• Error reason: The specified key is out of range.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4184 (53100) : ChunkServer out of disk space

• OceanBase Database error code: 4184

• Error reason: The disk space is full.

• Solution: Add servers to expand the disk space or contact OceanBase Technical Support for troubleshooting.

Related cases:

• The error Fail to alloc data block, (ret=-4184) occurs in the log of OceanBase Database.
• Error -4184: ChunkServer out of disk space occurs in the log.
• OceanBase Database exits with error 4184 during backup.
• Error -4184 occurs when the disk space is insufficient for an SQL query.

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

• OceanBase Database error code: 4185

• Error reason: The specified column group is not found.

• Solution: Check whether the name of the specified column group is correct and ensure that the column group exists or use the correct column group name.

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

• OceanBase Database error code: 4186

• Error reason: The specified compression library is not found.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4187 (HY000) : Item not match

• OceanBase Database error code: 4187

• Error reason: The specified value does not match.

• Solution: Contact OceanBase Technical Support for troubleshooting.

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

• OceanBase Database error code: 4189

• Error reason: The specified macro block type does not exist.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4191 (HY000) : partition group is removed

• OceanBase Database error code: 4191

• Error reason: The specified partition group is removed.

• Solution: No action is required.

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

• OceanBase error code: 4192
• Error reason: The DDL task takes too long to execute.
• Solution: Check whether the execution time of the DDL operation meets your expectations. If not, contact OceanBase support.

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

• OceanBase error code: 4200

• Error reason: The HASH value already exists.

• Solution: Contact OceanBase support.

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

• OceanBase error code: 4201

• Error reason: The HASH value does not exist.

• Solution: Contact OceanBase support.

Related cases:

• OceanBase Database returns error code 4201 during incremental backup

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

• OceanBase error code: 4204

• Error reason: The HASH operation times out.

• Solution: Contact OceanBase support.

ERROR 4205 (HY000) : hash map/set retry

• OceanBase error code: 4205

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

• Solution: Contact OceanBase support.

ERROR 4206 (HY000) : hash map/set full

• OceanBase error code: 4206

• Error reason: The HASH operation is full.

• Solution: Contact OceanBase support.

Related cases:

• SQL execution error -4206, hash map/set full

ERROR 4208 (HY000) : wait next packet timeout

• OceanBase error code: 4208

• Error reason: The wait for the next packet times out.

• Solution: Contact OceanBase support.

ERROR 4209 (HY000) : partition has not leader

• OceanBase error code: 4209

• Error reason: The partition leader does not exist.

• Solution: Contact OceanBase support.

ERROR 4210 (HY000) : prepare major freeze failed

• OceanBase error code: 4210

• Error reason: The preparation for major compaction fails.

• Solution: Contact OceanBase support.

ERROR 4211 (HY000) : commit major freeze failed

• OceanBase error code: 4211

• Error reason: The commit of major freeze fails.

• Solution: Contact OceanBase support.

ERROR 4212 (HY000) : abort major freeze failed

• OceanBase error code: 4212

• Error reason: The abort of major freeze fails.

• Solution: Contact OceanBase support.

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

• OceanBase error code: 4213

• Error reason: The last major freeze is not completed.

• Solution: Wait for the major freeze to complete, and then start a new major freeze.

ERROR 4215 (HY000) : wait major freeze response timeout

• OceanBase error code: 4215

• Error reason: The wait for the major freeze response times out.

• Solution: Contact OceanBase support.

ERROR 4216 (HY000) : curl error

• OceanBase error code: 4216

• Error reason: The libcurl access fails.

• Solution: Contact OceanBase support.

Related cases:

• 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

• Error reason: Major freeze is temporarily not allowed.

• Solution: The system may be in an upgrade or other process, and major freeze is not allowed.

Related cases:

• Major freeze fails, error code 4217

ERROR 4218 (HY000) : prepare freeze failed

• OceanBase error code: 4218

• Error reason: The preparation for freeze fails.

• Solution: Contact OceanBase support.

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

• OceanBase error code: 4220

• Error reason: The SQL client is invalid.

• Solution: Contact OceanBase support.

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

• OceanBase error code: 4221

• Error reason: The RPC client is not initialized.

• Solution: Contact OceanBase support.

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

• OceanBase error code: 4222

• Error reason: The time type conversion fails.

• Solution: Contact OceanBase support.

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

• OceanBase error code: 4223

• Error reason: The time type conversion fails.

• Solution: Contact OceanBase support.

ERROR 4225 (HY000) : Partition entry not exists

• OceanBase error code: 4225

• Error reason: The partition does not exist.

• Solution: Contact OceanBase support.

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

• OceanBase error code: 4232

• Error reason: The OBServer node or zone being accessed is not a follower.

• Solution: Internal error code. Contact OceanBase support.

ERROR 4233 (HY000) : smaller than container lower bound

• OceanBase error code: 4233

• Error reason: The value is smaller than the lower bound of the container.

• Solution: Contact OceanBase support.

ERROR 4234 (HY000) : bigger than container upper bound

• OceanBase error code: 4234

• Error reason: The value is larger than the upper bound of the container.

• Solution: Contact OceanBase support.

ERROR 4236 (HY000) : ObConfig return error code

• OceanBase Database error code: 4236

• Error reason: OceanBase Database failed to access the Config Server service.

• Solution: Check the obconfig_url parameter to determine whether the Config Server service is working properly. Contact OceanBase Technical Support for further assistance.

ERROR 4237 (HY000) : Appname mismatch with obconfig result

• OceanBase Database error code: 4237

• Error reason: The cluster name in the Config Server service does not match the actual cluster name.

• Solution: Check the obconfig_url parameter. Contact OceanBase Technical Support for further assistance.

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

• OceanBase Database error code: 4239

• Error reason: Kernel error.

• Solution: Contact OceanBase Technical Support for further assistance.

ERROR 4240 (HY000) : No join order generated

• OceanBase Database error code: 4240

• Error reason: Kernel error.

• Solution: Contact OceanBase Technical Support for further assistance.

ERROR 4241 (HY000) : No join path generated

• OceanBase Database error code: 4241

• Error reason: Kernel error.

• Solution: Contact OceanBase Technical Support for further assistance.

ERROR 4242 (HY000) : Schema error

• OceanBase Database error code: 4242

• Error reason: The execution endpoint failed to obtain the schema.

• Solution: Contact OceanBase Technical Support for further assistance.

ERROR 4243 (HY000) : file not opened

• OceanBase Database error code: 4243

• Error reason: The file is not opened.

• Solution: Contact OceanBase Technical Support for further assistance.

ERROR 4244 (HY000) : Timer task has been scheduled

• OceanBase Database error code: 4244

• Error reason: A timer task has been registered.

• Solution: Contact OceanBase Technical Support for further assistance.

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

• OceanBase Database error code: 4245

• Error reason: No timer task has been registered.

• Solution: Contact OceanBase Technical Support for further assistance.

ERROR 4246 (HY000) : parse debug sync string error

• OceanBase Database error code: 4246

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

• Solution: Contact OceanBase Technical Support for further assistance.

ERROR 4247 (HY000) : unknown debug sync point

• OceanBase Database error code: 4247

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

• Solution: Contact OceanBase Technical Support for further assistance.

ERROR 4248 (HY000) : task is interrupted while running

• OceanBase Database error code: 4248

• Error reason: The distributed execution scheduler was interrupted.

• Solution: Internal error. Contact OceanBase Technical Support for further assistance.

ERROR 4250 (HY000) : module is not running

• OceanBase Database error code: 4250

• Error reason: The module is not started.

• Solution: Contact OceanBase Technical Support for further assistance.

ERROR 4251 (HY000) : partition not valid

• OceanBase Database error code: 4251

• Error reason: The partition is invalid.

• Solution: Contact OceanBase Technical Support for further assistance.

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

• OceanBase Database error code: 4253

• Error reason: The length of the COMMENT clause at the tenant level in the DDL statement exceeds the limit.

• Solution: Reduce the length of the COMMENT clause in the DDL statement.

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

• OceanBase Database error code: 4257

• Error reason: Data compression or decompression failed. This may be because the data is damaged.

• Solution: Contact a DBA to check the hardware, replace the faulty server, or perform data recovery.

ERROR 4263 (HY000) : Minor freeze not allowed now

• OceanBase Database error code: 4263

• Error reason: Minor version freezing is temporarily not allowed.

• Solution: Contact OceanBase Technical Support for further assistance.

Related case:

• OB_MINOR_FREEZE_NOT_ALLOW(-4263)
• Dump failed Minor freeze not allowed now
• Too many frozen memtables ret=-4263

ERROR 4264 (HY000) : Log out of disk space

• OceanBase Database error code: 4264

• Error reason: The log disk has no space.

• Solution: Contact OceanBase Technical Support for further assistance.

Related case:

• OBServer server logs error 4264 due to disk space limit exceeded

ERROR 4265 (HY000) : Rpc connect error

• OceanBase Database error code: 4265

• Error reason: The RPC connection failed.

• Solution: Contact OceanBase Technical Support for further assistance.

ERROR 4266 (HY000) : minor merge not allow

• OceanBase Database error code: 4266

• Error reason: Minor version freezing is temporarily not allowed.

• Solution: Contact OceanBase Technical Support for further assistance.

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

• OceanBase Database error code: 4270

• Error reason: The partition status is abnormal.

• Solution: Contact OceanBase Technical Support for further assistance.

ERROR 4271 (HY000) : LIBEASY reach memory limit

• OceanBase Database error code: 4271

• Error reason: The memory occupied by untransmitted packets in LIBEASY exceeds the limit.

• Solution: Contact OceanBase Technical Support for further assistance.

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

• OceanBase Database error code: 4273

• Error reason: The number of free memory blocks in the cache is insufficient.

• Solution: Try to adjust the memory size or reduce the pressure, or contact OceanBase Technical Support for further assistance.

Related case:

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

ERROR 4274 (HY000) : sync wash memblock timeout

• OceanBase Database error code: 4274

• Error reason: The memory block is not released in time.

• Solution: Contact OceanBase Technical Support.

ERROR 4278 (HY000) : last log is not complete

• OceanBase Database error code: 4278

• Error reason: The last log is incomplete, which may be caused by a power outage or a sudden failure.

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

ERROR 4279 (HY000) : table is deleted

• OceanBase Database error code: 4279

• Error reason: The table has been deleted.

• Solution: Check whether the SQL statement accesses the deleted table.

ERROR 4280 (HY000) : version range not continues

• OceanBase Database error code: 4280

• Error reason: The version range is not continuous.

• Solution: Contact OceanBase Technical Support.

ERROR 4281 (HY000) : io buffer is invalid

• OceanBase Database error code: 4281

• Error reason: The I/O buffer is invalid.

• Solution: Contact OceanBase Technical Support.

ERROR 4282 (HY000) : partition is removed

• OceanBase Database error code: 4282

• Error reason: The partition has been deleted.

• Solution: Check whether the deleted partition is operated on, or contact OceanBase Technical Support.

ERROR 4283 (HY000) : gts is not ready

• OceanBase Database error code: 4283

• Error reason: The GTS service is not ready.

• Solution: Contact OceanBase Technical Support.

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

• OceanBase Database error code: 4286

• Error reason: The base table has been merged.

• Solution: Contact OceanBase Technical Support.

ERROR 4287 (HY000) : minor sstable version range cross

• OceanBase Database error code: 4287

• Error reason: The version ranges of minor SSTables overlap.

• Solution: Contact OceanBase Technical Support.

ERROR 4288 (HY000) : memtable cannot minor merge

• OceanBase Database error code: 4288

• Error reason: The MemTable cannot be minor merged.

• Solution: Contact OceanBase Technical Support.

ERROR 4289 (HY000) : task exist

• OceanBase Database error code: 4289

• Error reason: The task already exists.

• Solution: Contact OceanBase Technical Support.

ERROR 4290 (HY000) : cannot allocate disk space

• OceanBase Database error code: 4290

• Error reason: The disk space is insufficient.

• Solution: Expand the disk space, or contact OceanBase Technical Support.

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

• OceanBase Database error code: 4297

• Error reason: The name conflicts with that of another object in the same namespace.

• Solution: Change the name of the object to a name that is not used by another object in the namespace.

ERROR 4298 (HY000) : %s does not exist

• OceanBase Database error code: 4298

• MySQL compatible error code: 4298

• Error reason: The object to be operated on does not exist.

• Solution: Make sure that the sequence name is correct and that you have the required permissions on the sequence.

ERROR 4300 (HY000) : invalid sequence name

• OceanBase Database error code: 4300

• Error reason: The sequence name is invalid.

• Solution: Change the sequence name.

ERROR 4301 (HY000) : duplicate MAXVALUE/NOMAXVALUE specifications

• OceanBase Database error code: 4301

• Error reason: The MAXVALUE or NOMAXVALUE clause is specified multiple times.

• Solution: Remove the duplicate MAXVALUE or NOMAXVALUE clause.

ERROR 4302 (HY000) : duplicate MINVALUE/NOMINVALUE specifications

• OceanBase Database error code: 4302

• Error reason: The MINVALUE or NOMINVALUE clause is specified multiple times.

• Solution: Remove the duplicate MINVALUE or NOMINVALUE clause.

ERROR 4303 (HY000) : duplicate CYCLE/NOCYCLE specifications

• OceanBase Database error code: 4303

• Error reason: The CYCLE or NOCYCLE clause is specified multiple times.

• Solution: Remove the duplicate CYCLE or NOCYCLE clause.

ERROR 4304 (HY000) : duplicate CACHE/NOCACHE specifications

• OceanBase Database error code: 4304

• Error reason: The CACHE or NOCACHE clause is specified multiple times.

• Solution: Remove the duplicate CACHE or NOCACHE clause.

ERROR 4305 (HY000) : duplicate ORDER/NOORDER specifications

• OceanBase Database error code: 4305

• Error reason: The ORDER or NOORDER clause is specified multiple times.

• Solution: Remove the duplicate ORDER or NOORDER clause.

ERROR 4306 (HY000) : conflicting MAXVALUE/NOMAXVALUE specifications

• OceanBase Database error code: 4306

• Error reason: The MAXVALUE and NOMAXVALUE clauses conflict with each other.

• Solution: Remove the conflicting MAXVALUE or NOMAXVALUE clause.

ERROR 4307 (HY000) : conflicting MINVALUE/NOMINVALUE specifications

• OceanBase Database error code: 4307

• Error reason: The MINVALUE and NOMINVALUE clauses conflict with each other.

• Solution: Remove the conflicting MINVALUE or NOMINVALUE clause.

ERROR 4308 (HY000) : conflicting CYCLE/NOCYCLE specifications

• OceanBase Database error code: 4308

• Error reason: The CYCLE and NOCYCLE clauses conflict with each other.

• Solution: Remove the conflicting CYCLE or NOCYCLE clause.

ERROR 4309 (HY000) : conflicting CACHE/NOCACHE specifications

• OceanBase Database error code: 4309

• Error reason: The CACHE and NOCACHE clauses conflict with each other.

• Solution: Remove the conflicting CACHE or NOCACHE clause.

ERROR 4310 (HY000) : conflicting ORDER/NOORDER specifications

• OceanBase error code: 4310

• Error reason: conflicting ORDER or NOORDER definitions.

• Solution: remove the conflicting ORDER or NOORDER.

ERROR 4311 (HY000) : cannot alter starting sequence number

• OceanBase error code: 4311

• Error reason: cannot modify the START WITH value of an auto-increment column.

• Solution: do not change the START WITH value.

ERROR 4312 (HY000) : duplicate INCREMENT BY specifications

• OceanBase error code: 4312

• Error reason: duplicate INCREMENT BY definitions.

• Solution: remove the duplicate INCREMENT BY.

ERROR 4313 (HY000) : duplicate START WITH specifications

• OceanBase error code: 4313

• Error reason: duplicate START WITH definitions.

• Solution: remove the duplicate START WITH.

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

• OceanBase error code: 4314

• Error reason: no parameters are specified in the ALTER SEQUENCE statement.

• Solution: a statement with no options is meaningless.

ERROR 4315 (HY000) : sequence number not allowed here

• OceanBase error code: 4315

• Error reason: an auto-increment column is not allowed here.

• Solution: remove the auto-increment column.

ERROR 4316 (HY000) : sequence does not exist

• OceanBase error code: 4316

• Error reason: the auto-increment column does not exist or you do not have the required privileges.

• Solution: ensure that the auto-increment column name is correct and that you have the required privileges.

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

• OceanBase error code: 4317

• Error reason: the parameters in the CREATE SEQUENCE or ALTER SEQUENCE statement must be integers.

• Solution: specify an integer value for the specified parameter when you create or modify an auto-increment column.

ERROR 4318 (HY000) : INCREMENT must be a nonzero integer

• OceanBase error code: 4318

• Error reason: the INCREMENT value 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

• Error reason: the parameter value of the auto-increment column exceeds the maximum allowed value.

• Solution: specify a parameter with the allowed number of bits.

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

• OceanBase error code: 4320

• Error reason: in the CREATE SEQUENCE or ALTER SEQUENCE statement, the MINVALUE value must be less than the MAXVALUE value.

• Solution: specify a MINVALUE value less than the MAXVALUE value.

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

• OceanBase error code: 4321

• Error reason: in the CREATE SEQUENCE or ALTER SEQUENCE statement, the INCREMENT value must be less than the difference between MAXVALUE and MINVALUE.

• Solution: specify an INCREMENT value less than the difference between MAXVALUE and MINVALUE.

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

• OceanBase error code: 4322

• Error reason: in the CREATE SEQUENCE or ALTER SEQUENCE statement, the START WITH value cannot be less than the MINVALUE value.

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

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

• OceanBase error code: 4323

• Error reason: the specified MINVALUE value 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 reason: the START WITH value is greater than the MAXVALUE value.

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

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

• OceanBase error code: 4325

• Error reason: the MAXVALUE value 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 reason: the value of the parameter in the CACHE clause must be greater than 1.

• Solution: specify a value greater than 1 for the parameter in the CACHE clause.

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

• OceanBase error code: 4327

• Error reason: the parameter in the CREATE SEQUENCE or ALTER SEQUENCE statement is out of range.

• Solution: specify a parameter value within the range.

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

• OceanBase error code: 4328

• Error reason: the cache parameter must be less than one cycle.

• Solution: increase the cycle or cache fewer values.

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

• OceanBase error code: 4329

• Error reason: a descending auto-increment column must specify MINVALUE.

• Solution: recreate the sequence and specify MINVALUE.

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

• OceanBase error code: 4330

• Error reason: an ascending auto-increment column must specify MAXVALUE.

• Solution: recreate the sequence and specify MAXVALUE.

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

• OceanBase Database error code: 4331

• Error reason: The auto-increment column does not exist.

• Solution: Recreate the auto-increment column.

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

• OceanBase Database error code: 4332

• Error reason: The value of the auto-increment column has reached the upper limit and cannot be obtained.

• Solution: Change the auto-increment column to allow new values to be requested.

ERROR 4333 (HY000) : divisor is equal to zero

• OceanBase Database error code: 4333

• Error reason: The divisor is equal to zero.

• Solution: Contact Technical Support.

ERROR 4334 (HY000) : fail to decrypt data

• OceanBase Database error code: 4334

• Error reason: The decryption failed.

• Solution: Contact Technical Support.

Related cases:

• OceanBase Database returns an error with ret=-4334

ERROR 4335 (HY000) : fail to encrypt data

• OceanBase Database error code: 4335

• Error reason: The encryption failed.

• Solution: Contact Technical Support.

ERROR 4337 (HY000) : store directory structure error

• OceanBase Database error code: 4337

• Error reason: The storage directory structure failed.

• Solution: Contact Technical Support.

Related cases:

• The OBServer fails to start because of error code 4337
• A correctness error -4377 is returned when you execute a DML statement in parallel.
• One of the scenarios in which a correctness error 4377 is returned
• A fatal internal error is returned when you execute a DELETE statement in MySQL mode in OceanBase Database.
• A correctness error -4337 is returned when you execute a DML statement on a table that has a full-text index.
• A correctness error is returned when you use PDML and the statement involves multiple tables.

ERROR 4338 (HY000) : open twice

• OceanBase Database error code: 4338

• Error reason: The file is opened twice.

• Solution: Contact Technical Support.

ERROR 4339 (HY000) : raid super block not match

• OceanBase Database error code: 4339

• Error reason: The super block is incorrect.

• Solution: The issue may be caused by a hardware failure. Check the disks or contact Technical Support.

ERROR 4340 (HY000) : not opened

• OceanBase Database error code: 4340

• Error reason: The file is not opened.

• Solution: Contact Technical Support.

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

• OceanBase Database error code: 4341

• Error reason: The weak read service is not started.

• Solution: Contact Technical Support.

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

• OceanBase Database error code: 4342

• Error reason: The disk is in an abnormal state.

• Solution: Contact Technical Support.

ERROR 4343 (HY000) : tenant schema is not full

• OceanBase Database error code: 4343

• Error reason: The schema of the local tenant is outdated.

• Solution: Contact Technical Support.

Related cases:

• An error -4006/-4343 is returned during a major compaction.

ERROR 4344 (HY000) : invalid timestamp

• OceanBase Database error code: 4344

• Error reason: The timestamp is invalid.

• Solution: Enter a valid timestamp.

ERROR 4345 (HY000) : dir not empty

• OceanBase Database error code: 4345

• Error reason: The directory is not empty.

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

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

• OceanBase Database error code: 4346

• Error reason: The schema is outdated.

• Solution: Contact Technical Support.

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

• OceanBase Database error code: 4347

• Error reason: The ROLE does not exist.

• Solution: Make sure that the ROLE name is correct.

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

• OceanBase Database error code: 4348

• Error reason: A user or ROLE with the specified name already exists.

• Solution: Use a different name.

ERROR 4349 (HY000) : duplicate privilege listed

• OceanBase Database error code: 4349

• Error reason: The GRANT or REVOKE statement specifies duplicate privileges or ROLEs.

• Solution: Remove the duplicate privileges or ROLEs.

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

• OceanBase Database error code: 4350

• Error reason: The keystore already exists. A tenant can have at most one keystore.

• Solution: Check whether the keystore has been created.

ERROR 4351 (HY000) : the keystore is not exist

• OceanBase Database error code: 4351

• Error reason: The keystore does not exist.

• Solution: Check whether the keystore has been created.

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

• OceanBase Database error code: 4352

• Error reason: The password for the keystore is incorrect.

• Solution: Use the correct password.

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

• OceanBase Database error code: 4353

• Error reason: The tablespace already exists.

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

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

• OceanBase Database error code: 4354

• Error reason: The tablespace does not exist.

• Solution: Check whether the tablespace exists.

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

• OceanBase error code: 4355

• Error reason: A non-empty tablespace cannot be deleted.

• Solution: Confirm that the tablespace is empty before deleting it.

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

• OceanBase error code: 4356

• Error reason: The precision of the BINARY_DOUBLE data 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

• Error reason: The precision of the NUMBER data 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

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

• Solution: Reduce the precision.

ERROR 4359 (HY000) : the keystore is not open

• OceanBase error code: 4359

• Error reason: 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 reason: The master key does not exist.

• Solution: Create the master key.

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

• OceanBase error code: 4361

• Error reason: The number of active transactions in the slog exceeds the maximum limit.

• Solution: Contact Technical Support for assistance.

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

• OceanBase error code: 4362

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

• Error reason: Auditing is not supported for this type of object.

• Solution: Contact Technical Support for assistance.

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

• OceanBase error code: 4364

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

• Error reason: When the data volume exceeds 64 MB, the execution task must be split into smaller granules. This error code is returned to notify the execution scheduler to resplit and retry.

• Solution: Internal error code. Contact Technical Support for assistance.

ERROR 4368 (HY000) : cluster %s not exist

• OceanBase error code: 4368

• Error reason: An internal error occurs in the Config Server when retrieving cluster information.

• Solution: Internal error code. Contact Technical Support for assistance.

ERROR 4369 (HY000) : fail to get master key

• OceanBase error code: 4369

• Error reason: Failed to obtain the master key.

• Solution: Contact Technical Support for assistance.

ERROR 4370 (HY000) : tde_method parameter is invalid

• OceanBase error code: 4370

• Error reason: 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 reason: Failed to connect to the KMS server.

• Solution: Check the availability of the KMS server.

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

• OceanBase error code: 4372

• Error reason: The KMS server is busy.

• Solution: Retry.

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

• OceanBase error code: 4373

• Error reason: A conflict occurs during concurrent updates of the master key.

• Solution: Retry.

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

• OceanBase error code: 4374

• Error reason: The precision of the value exceeds 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

• Error reason: A storage disk error occurs.

• Solution: Check whether a disk error occurs and replace the corresponding server.

ERROR 4376 (HY000) : unimplemented feature

• OceanBase error code: 4376

• Error reason: 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 reason: An unexpected internal error occurs in OceanBase Database, which may be caused by an abnormal program execution.

• Solution: Contact Technical Support for assistance.

Related cases:

• Non-strict mode: INSERT partition pruning returns error 4377
• After a new partition is inserted into a partitioned table, an error -4377 is returned when an SQL statement is executed.

ERROR 4378 (HY000) : cluster name conflict

• OceanBase error code: 4378

• Error reason: The cluster name is duplicated.

• Solution: Set a different cluster name.

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

• OceanBase Database error code: 4379

• Cause: The number of rows that can be inserted into a table without a primary key has reached the upper limit.

• Solution: Create a new table. If needed, you can migrate data from the original table to the new table.

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

• OceanBase Database error code: 4381

• Cause: The float(m,d) or double(m,d) data type is specified to declare a floating-point number with precision.

• Solution: Use the decimal(m,d) data type to specify a decimal number with precision.

ERROR 4383 (HY000) : transaction id is not ready

• OceanBase Database error code: 4383

• Cause: The transaction ID allocator has no available ID range.

• Solution: Retry to obtain an ID until the timeout.

ERROR 4386 (HY000) : Do not allow removing leader

• OceanBase Database error code: 4386

• Cause: Internal error. The source of the migration is a log replica leader. Migration is not allowed.

• Solution: No action is required.

ERROR 4387 (HY000) : Failed to switch resource group

• OceanBase Database error code: 4387
• Compatible with MySQL error code: 13937

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

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

• Cause: The task processing time is too long.

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

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

• OceanBase Database error code: 4390

• Cause: The local or remote schema has not been refreshed. This might be because the OBServer node has not been fully restarted or has experienced an exception.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4391（HY000）：ddl sstable version range cross

• OceanBase Database error code: 4391

• Cause: The DDL SSTable returns a crossed version range.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4392 (HY000) : disk is hung

• OceanBase Database error code: 4392
• Cause: A disk error occurs.
• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4393 (HY000) : observer start process failure

• OceanBase Database error code: 4393

• Cause: The internal component or service fails to initialize during the startup of the observer process.

• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4394 (HY000) : observer stop process failure

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

ERROR 4395 (HY000) : observice start process has failure

• OceanBase Database error code: 4395
• Cause: The internal component or service fails to initialize during the startup of the observer process.
• Solution: Contact OceanBase Technical Support for troubleshooting.

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

• OceanBase Database error code: 4396
• Cause: An exception occurs during the execution of a worker thread.
• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 4399 (HY000) : Unit status is not expected

• OceanBase Database error code: 4399
• Cause: A tenant migration occurs during the execution of a direct load.
• Solution: Retry the failed direct load SQL statement.

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

• OceanBase Database error code: 4400
• Error reason: During the operation, the autoinc version of the autoinc cache is inconsistent with the autoinc version of the request.
• Solution:
  1. Check the autoinc version: Check whether the autoinc version is correct and ensure that the autoinc version of the autoinc cache is consistent with the autoinc version of the request.
  2. Clear the autoinc cache: Try to clear the autoinc cache to regenerate the autoinc value.

ERROR 4401 (HY000) : Client Session need be killed

• OceanBase Database error code: 4401

• Compatible with MySQL error code: 4401

• Error reason: The client session needs to be killed.

• Solution: Confirm whether to kill the client session and take appropriate measures to kill the session, such as using the appropriate command or tool to end the client session.

ERROR 4402 (HY000) : Kill Client Session failed

• OceanBase Database error code: 4402

• Error reason: The operation to kill the client session failed.

• Solution: Before executing the operation to kill the session, make sure that the target session is active and can be killed.

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

• OceanBase Database error code: 4403

• Error reason: The OBServer node found that the parameter settings of the operating system are unreasonable.

• Solution: Check the ERROR log to find out which parameter is set incorrectly. Then, check the correct range of the parameter in the documentation and modify it.

ERROR 4408 (HY000) : Migrate tx data not continues

• OceanBase Database error code: 4408

• Error reason: During the migration, the source transaction data table is recycled. When copying the transaction data table to the destination, the transaction data table is not continuous. The operation fails and the error is reported. The operation can be retried.

• Solution: Generally, the operation can be successful after a retry. If the operation fails continuously, contact OceanBase Technical Support for troubleshooting.

ERROR 4410 (HY000) : ls not in learner list

• OceanBase Database error code: 4410

• Error reason: During the migration or rebuild, the log stream replica of the destination is not in the learner list. This may be because the log stream replica of the destination is deleted.

• Solution: Wait for the corresponding task to automatically retry.