This range indicates transaction layer error codes, including those related to transactions, MVCC, and clogs.
ERROR 6001 (25000) : Transaction set changed during the execution
OceanBase error code: 6001
Cause: An update request must first read data before updating it. If the data changes before the update, this error code is returned to the upper layer, and the operation is retried.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 6002 (25000) : Transaction idle timeout occurred, please rollback the transaction, set the variable ob_trx_idle_timeout to a larger value and then restart the transaction
OceanBase error code: 6278
Compatible MySQL error code: 6002
ERROR 6002 (25000) : transaction needs rollback
OceanBase error code: 6224
Compatible MySQL error code: 6002
ERROR 6002 (25000) : Transaction exiting
OceanBase error code: 6223
Compatible MySQL error code: 6002
ERROR 6002 (25000) : transaction context count reach limit
OceanBase error code: 6234
Compatible MySQL error code: 6002
ERROR 6002 (HY000) : Transaction context does not exist
OceanBase error code: 6213
Compatible MySQL error code: 6002
ERROR 6002 (25000) : Partition is frozen
OceanBase error code: 6214
Compatible MySQL error code: 6002
ERROR 6002 (25000) : Transaction is killed
OceanBase error code: 6211
Compatible MySQL error code: 6002
ERROR 6005 (HY000) : Try lock row conflict
OceanBase error code: 6005
Cause: The lock acquisition failed during the update operation. This error code is returned to the upper layer, and the operation is retried.
Solution: An internal error code. Contact technical support for assistance.
ERROR 6201 (25000) : Clock out of order
OceanBase error code: 6201
Cause: An internal error code. The background clock thread runs every 1 ms. If the time interval between two runs exceeds 10 ms, this error code is reported.
Solution: If this error occurs frequently, check whether the server load is too high or the server clock is unstable.
ERROR 6203 (25000) : Mask set has no node
OceanBase error code: 6203
Cause: A node does not exist in the mask set container.
Solution: An internal error code. Contact technical support for assistance.
ERROR 6204 (HY000) : Transaction has been decided
OceanBase error code: 6204
Cause: Indicates that the transaction has been prepared for commit.
Solution: An internal error code. Contact technical support for assistance.
ERROR 6205 (HY000) : Transaction state invalid
OceanBase error code: 6205
Cause: The transaction state machine is abnormal.
Solution: An internal error code. Contact technical support for assistance.
ERROR 6206 (HY000) : Transaction state not changed
OceanBase error code: 6206
Cause: The state machine does not require a transition.
Solution: An internal error code. Contact technical support for assistance.
ERROR 6208 (HY000) : Transaction message invalid
OceanBase error code: 6208
Cause: Invalid transaction message.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 6209 (HY000) : Transaction message type invalid
OceanBase error code: 6209
Cause: Invalid message type.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 6215 (HY000) : Partition is not frozen
OceanBase error code: 6215
Cause: This error code is unused.
Solution: No action required.
ERROR 6219 (HY000) : Transaction invalid log type
OceanBase error code: 6219
Cause: Invalid log type.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 6220 (HY000) : SQL sequence illegal
OceanBase error code: 6220
Cause: The SQL statement sequence is invalid.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 6221 (HY000) : Transaction context cannot be killed
OceanBase error code: 6221
Cause: The current transaction context cannot be terminated.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 6222 (HY000) : Transaction state unknown
OceanBase error code: 6222
Cause: Unknown transaction status.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 6227 (HY000) : Partition is not stopped
OceanBase error code: 6227
Cause: The partition is not set to the stopped state.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 6228 (HY000) : Partition has been stopped
OceanBase error code: 6228
Cause: The partition is set to the stopped state.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 6229 (HY000) : Partition has been blocked
OceanBase error code: 6229
Cause: The partition is set to the blocked state.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 6231 (HY000) : replica is not readable
OceanBase error code: 6231
Cause: The current replica is unreadable. Return to the upper layer and retry.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 6232 (HY000) : Partition is splitting
OceanBase error code: 6232
Cause: The partition is splitting. Return to the upper layer and retry.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 6233 (HY000) : Transaction has been commited
OceanBase error code: 6233
Cause: The transaction has been committed.
Solution: An internal error code. Contact technical support for assistance.
ERROR 6235 (25000) : can't serialize access for this transaction
OceanBase error code: 6235
Cause: The transaction cannot be serialized.
Solution: The client must roll back the transaction and execute it again.
ERROR 6236 (HY000) : transaction weak read version is not ready
OceanBase error code: 6236
Cause: A weak-consistency read version number could not be generated.
Solution: An internal error code. Contact technical support for assistance.
ERROR 6237 (HY000) : gts standby is invalid
OceanBase error code: 6237
Cause: The standby GTS service is invalid.
Solution: An internal error code. Contact technical support for assistance.
ERROR 6238 (HY000) : gts update failed
OceanBase error code: 6238
Cause: An internal update in the GTS service failed.
Solution: An internal error code. Contact technical support for assistance.
ERROR 6239 (HY000) : gts is not serving
OceanBase error code: 6239
Cause: The GTS service is not enabled.
Solution: An internal error code. Contact technical support for assistance.
ERROR 6240 (HY000) : pg partition not exist
OceanBase error code: 6240
Cause: The partition group does not exist.
Solution: An internal error code. Contact technical support for assistance.
ERROR 6241 (HY000) : transaction statement need retry
OceanBase error code: 6241
Cause: The statement needs to be retried. The current transaction may be writing logs or requesting data from a follower.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 6243 (HY000) : local schema is not new enough, replaying logs of user table from standby cluster needs to wait for schema refreshing
OceanBase error code: 6243
Cause: The local schema is not fresh enough, and log replay needs to be retried.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 6244 (HY000) : out of transaction threshold
OceanBase error code: 6244
Cause: The transaction exceeds the
_max_trx_sizelimit.Solution: Adjust the transaction size.
ERROR 6245 (XAE04) : Unknown XID
OceanBase error code: 6245
Cause: The
xidin the XA transaction request is invalid.Solution: This is an internal error code. The corresponding return value for an XA transaction is
-4. After the Transaction Manager (TM) captures this return value, contact technical support to further confirm the cause.
ERROR 6246 (XAE07) : The command cannot be executed when global transaction is in this state
OceanBase error code: 6246
Cause: An error occurred during the execution of an XA transaction statement.
Solution: This is an internal error code. The corresponding return value for an XA transaction is
-7. After the Transaction Manager (TM) captures this return value, contact technical support to further confirm the cause.
ERROR 6247 (XAE08) : The XID already exists
OceanBase error code: 6247
Cause: An XA transaction with the same XID already exists when executing
XA_START.Solution: This is an internal error code. The corresponding return value for an XA transaction is
-8. After the Transaction Manager (TM) captures this return value, contact technical support to confirm the cause.
ERROR 6248 (XAE09) : Some work is done outside global transaction
OceanBase error code: 6248
Cause: A transaction context already exists when executing XA transaction statements.
Solution: This is an internal error code. The corresponding return value for an XA transaction is
-9. After the Transaction Manager (TM) captures this return value, technical support personnel need to check the business logic to ensure that XA transaction statements are not being executed within a transaction.
ERROR 6249 (XAE05) : Invalid arguments were given
OceanBase error code: 6249
Cause: The participation of XA transaction statements is invalid.
Solution: This is an internal error code. The corresponding return value for an XA transaction is
-5. After the Transaction Manager (TM) captures this return value, contact technical support to confirm the cause.
ERROR 6250 (XAE03) : Resource manager error occurred in the transaction branch
OceanBase error code: 6250
Cause: An unexpected error occurred when executing XA transaction statements.
Solution: This is an internal error code. The corresponding return value for an XA transaction is
-3. After the Transaction Manager (TM) captures this return value, contact technical support to confirm the cause.
ERROR 6251 (HY000) : Routine invoked in an improper context
OceanBase error code: 6251
Cause: XA transaction statements were called in an inappropriate context.
Solution: This is an internal error code. The corresponding return value for an XA transaction is
-6. After the Transaction Manager (TM) captures this return value, contact technical support to confirm the cause.
ERROR 6252 (XA100) : Rollback was caused by an unspecified reason
OceanBase error code: 6252
Cause: The XA transaction has been rolled back for an unknown reason.
Solution: This is an internal error code. The corresponding return value for an XA transaction is
100(XA_RBBASE). The Transaction Manager (TM) must identify this return value.
ERROR 6253 (XA106) : Transaction branch took long
OceanBase error code: 6253
Cause: The XA transaction has been rolled back due to a timeout.
Solution: This is an internal error code. The corresponding return value for an XA transaction is
106(XA_RBBASE + 6), which must be recognized by the Transaction Manager (TM).
ERROR 6254 (HY000) : Transaction was read-only and has been committed
OceanBase error code: 6254
Cause: The XA transaction is a read-only transaction, and XA_PREPARE is executed.
Solution: This is an internal error code. The corresponding return value for an XA transaction is
3, which must be recognized by the Transaction Manager (TM).
ERROR 6255 (HY000) : Routine returned with no effect and may be re-issued
OceanBase error code: 6255
Cause: The XA statement request cannot be completed immediately and needs to be retried.
Solution: This is an internal error code. The corresponding return value for an XA transaction is
4, which must be recognized by the Transaction Manager (TM).
ERROR 6256 (HY000) : Row has not been locked
OceanBase error code: 6256
Cause: The row lock has not been acquired.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 6257 (HY000) : Empty partition group
OceanBase error code: 6257
Cause: The partition list of the partition group is empty.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 6265 (HY000) : object lock does not exist
OceanBase error code: 6265
Cause: Related to table locking; the corresponding lock on the table does not exist.
Solution: This is an internal error code. Contact technical personnel for assistance.
ERROR 6266 (HY000) : object lock exists
OceanBase error code: 6266
Cause: Table lock related. The corresponding lock operation already existed during locking, i.e., duplicate locking.
Solution: An internal error code. Please contact technical personnel for assistance.
ERROR 6267 (HY000) : Try lock object conflict
OceanBase error code: 6267
Cause: Table lock related. A lock conflict occurred during locking.
Solution: A reserved error code, not yet enabled.
ERROR 6268 (HY000) : No log callbacks available
OceanBase error code: 6268
Cause: The number of unprocessed log callbacks for a single transaction has reached the upper limit, preventing further log commits.
Solution: Retry and wait for log layer callbacks.
ERROR 6275 (HY000) : object lock not completed, and can not unlock
OceanBase error code: 6275
Cause: When unlocking with DDL, the corresponding table lock transaction has not ended.
Solution: An internal error code. Please contact technical personnel for assistance.
ERROR 6276 (HY000) : there is an unlock operation doing, unlock conflict
OceanBase error code: 6276
Cause: When unlocking with DDL, another unlock operation already exists but has not ended.
Solution: An internal error code. Please contact technical personnel for assistance.
ERROR 6277 (HY000) : scn is out of bounds of memtable
OceanBase error code: 6277
Cause: Setting the SCN for the MemTable exceeds its boundary limits.
Solution: An internal error code. If displayed as ERROR, please contact technical support for assistance; if displayed as WARN, it indicates normal operation.
ERROR 6280 (HY000) : Transaction cost too much without commit or rollback
- OceanBase error code: 6280
- Cause: The transaction has been active for a long time, preventing row locks from being released.
- Solution: Analyze the business scenario to determine whether the long-running transaction is expected.
ERROR 6281 (HY000) : Transaction commit cost too much
- OceanBase error code: 6281
- Cause: The transaction commit or rollback took too long, resulting in an abnormal transaction commit.
- Solution: Contact technical support for assistance.
ERROR 6290 (HY000) : Transaction rollbacked as no rows were affected
- OceanBase error code: 6290
- Cause: In scenarios involving hotspot row aggregation optimization, if a data modification operation is performed within a transaction but ultimately no data rows are affected, the entire transaction is automatically rolled back.
- Solution: Verify that the SQL statement and data state comply with business logic.
ERROR 6302 (HY000) : log scan runnable thread stop
OceanBase error code: 6302
Cause: Internal error. During the restart of OceanBase AI Database, the process receives signals such as
kill -15, causing it to exit. Theobserver.logfile reports the above error code.Solution: Restart the process.
ERROR 6303 (HY000) : no log ever scanned
OceanBase error code: 6303
Cause: Internal error. Liboblog failed to find the logs for the corresponding partition on the OBServer node.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 6308 (HY000) : external executor handle do not finish
OceanBase error code: 6308
Cause: Internal error. When Liboblog requests the OBServer node to pull logs for a partition based on the start timestamp using the
start_log_id, it supports resuming from a breakpoint. If a partition is not fully processed in this RPC, this error code is returned to Liboblog, which then determines and executes the subsequent logic.Solution: This is an internal error code. Contact technical support for assistance.
ERROR 6309 (HY000) : cursor not exist
OceanBase error code: 6309
Cause: Internal error. Indicates that the corresponding
log_idcannot be found in the index log storage.Solution: This is an internal error code. Contact technical support for assistance.
ERROR 6310 (HY000) : stream not exist
OceanBase error code: 6310
Cause: Internal error. When the stream ID carried in a request executed by Liboblog cannot be found in the OBServer node's memory, this error code is reported.
Solution: This is an internal error code. Please contact technical support for assistance.
ERROR 6311 (HY000) : stream busy
OceanBase error code: 6311
Cause: An internal error occurred. Liboblog executed two RPC requests simultaneously for the same stream, resulting in this error code.
Solution: This is an internal error code. Please contact technical support for assistance.
ERROR 6312 (HY000) : file recycled
OceanBase error code: 6312
Cause: An internal error occurred. The
CLog Fileread based on the information recorded in theIndex Loghas been recycled, resulting in this error code.Solution: This is an internal error code. Please contact technical support for assistance.
ERROR 6313 (HY000) : replay eagain cost too much time
OceanBase error code: 6313
Cause: An internal error occurred. Confirmed logs have been submitted to the replay engine, but the replay engine returns OB_EAGAIN (indicating a retry is needed) for an extended period due to some reason, resulting in this error code.
Solution: This is an internal error code. Please contact technical support for assistance.
ERROR 6314 (HY000) : member change log sync failed
OceanBase error code: 6314
Cause: An internal error occurred. A member change task failed due to reasons such as leader switchover and needs to be re-executed.
Solution: This is an internal error code. Please contact technical support for assistance.
ERROR 6315 (HY000) : no need batch ctx
OceanBase error code: 6315
Cause: An internal error. The internal state for the first-phase commit optimization of distributed transactions in OceanBase AI Database is being processed automatically.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 6316 (HY000) : too large log id
OceanBase error code: 6316
Cause: An internal error. This error occurs when the LogId corresponding to a log exceeds the processing range of the current partition. For a leader, it indicates that the number of transactions being processed in parallel exceeds the partition's capability. For a follower, it indicates that the replica is significantly behind the leader node.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 6317 (HY000) : alloc log id need retry
OceanBase error code: 6317
Cause: An internal error. This indicates that the number of concurrently executing transactions exceeds the log system's processing capacity, and the transaction engine will attempt a retry.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 6318 (HY000) : transaction one pc not allowed
OceanBase error code: 6318
Cause: An internal error. This indicates that the first-phase commit of a distributed transaction cannot be executed.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 6319 (HY000) : need rebuild
OceanBase error code: 6319
Cause: An internal error. This indicates that a replica is significantly behind in logs and needs to perform a
Rebuildto catch up with the data.Solution: This is an internal error code. Contact technical support for assistance.
ERROR 6321 (HY000) : ob invalid batch size
OceanBase error code: 6321
Cause: An internal error.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 6322 (HY000) : ob clog slide timeout
OceanBase error code: 6322
Cause: An internal error occurred. This indicates that the execution time of confirmed logs committed by the logging system to the replay engine for a single partition exceeds the preset system value. As a result, processing for this partition stops, and the task moves on to the next partition.
Solution: This is an internal error code. Contact technical support for assistance.
ERROR 6325 (HY000) : ob clog disk hang
OceanBase error code: 6325
Cause: The disk containing clog logs is hung.
Solution: Check the disk status and database load.
ERROR 6329 (HY000) : pdml sql need retry under sequence number reorder
OceanBase error code: 6329
Cause: A PDML query statement needs to be retried under sequence number reordering.
Solution: Rerun the PDML query statement after the sequence numbers are reordered.
ERROR 6330 (HY000) : user data disk is almost full
OceanBase error code: 6330
Cause: The user data disk is nearly full.
Solution: Clean up or increase the user data disk space to ensure sufficient capacity for storing user data.
ERROR 6333 (HY000) : attempt to access a transactional temp table already in use
- OceanBase error code: 6333
- Cause: Both transactional temporary tables and session-level temporary tables may be in an "in use" state, causing new access requests to be denied.
- Solution: Release the occupation of the temporary table.
ERROR 6400 (HY000) : tablet_freeze timeout
- OceanBase error code: 6400
- Cause: Partition-level freeze.
- Solution: Contact technical support for assistance.