6000 - 6999

These error codes indicate transaction layer-related errors, including transaction, multi-version concurrency control (MVCC), and clog errors.

ERROR 6001 (25000): Transaction set changed during the execution

• Error code in OceanBase Database: 6001

• Cause: An update request takes effect after data is read. If data is changed before the update, this error is returned to the upper layer, and the system retries the request.

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

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

• Error code in OceanBase Database: 6278

• MySQL error code: 6002

ERROR 6002 (25000): transaction needs rollback

• Error code in OceanBase Database: 6224

• MySQL error code: 6002

ERROR 6002 (25000): Transaction exiting

• Error code in OceanBase Database: 6223

• MySQL error code: 6002

ERROR 6002 (25000): transaction context count reach limit

• Error code in OceanBase Database: 6234

• MySQL error code: 6002

ERROR 6002 (HY000): Transaction context does not exist

• Error code in OceanBase Database: 6213

• MySQL error code: 6002

ERROR 6002 (25000): Partition is frozen

• Error code in OceanBase Database: 6214

• MySQL error code: 6002

ERROR 6002 (25000): Transaction is killed

• Error code in OceanBase Database: 6211

• MySQL error code: 6002

ERROR 6005 (HY000): Try lock row conflict

• Error code in OceanBase Database: 6005

• Cause: The update operation failed to add a lock. This error is returned to the upper layer, and the system retries the operation.

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

ERROR 6201 (25000): Clock out of order

• Error code in OceanBase Database: 6201

• Cause: An internal error occurred. The background clock thread runs once every 1 ms. This error occurs if the time interval between two consecutive thread executions exceeds 10 ms.

• Solution: If this error occurs frequently, check whether the server is overloaded or the server clock is unstable.

ERROR 6203 (25000): Mask set has no node

• Error code in OceanBase Database: 6203

• Cause: The mask set container does not contain the specified node.

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

ERROR 6204 (HY000): Transaction has been decided

• Error code in OceanBase Database: 6204

• Cause: A transaction commit has been initiated.

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

ERROR 6205 (HY000): Transaction state invalid

• Error code in OceanBase Database: 6205

• Cause: The transaction state machine is abnormal.

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

ERROR 6206 (HY000): Transaction state not changed

• Error code in OceanBase Database: 6206

• Cause: The state machine does not need to be modified.

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

ERROR 6208 (HY000): Transaction message invalid

• Error code in OceanBase Database: 6208

• Cause: The transaction message is invalid.

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

ERROR 6209 (HY000): Transaction message type invalid

• Error code in OceanBase Database: 6209

• Cause: The message type is invalid.

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

ERROR 6215 (HY000): Partition is not frozen

• Error code in OceanBase Database: 6215

• Cause: This error code is useless.

• Solution: Troubleshooting is not required.

ERROR 6219 (HY000): Transaction invalid log type

• Error code in OceanBase Database: 6219

• Cause: The log type is invalid.

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

ERROR 6220 (HY000): SQL sequence illegal

• Error code in OceanBase Database: 6220

• Cause: The sequence of SQL statements is invalid.

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

ERROR 6221 (HY000): Transaction context cannot be killed

• Error code in OceanBase Database: 6221

• Cause: The current transaction context cannot be terminated.

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

ERROR 6222 (HY000): Transaction state unknown

• Error code in OceanBase Database: 6222

• Cause: The transaction status is unknown.

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

ERROR 6227 (HY000): Partition is not stopped

• Error code in OceanBase Database: 6227

• Cause: The partition is not stopped.

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

ERROR 6228 (HY000): Partition has been stopped

• Error code in OceanBase Database: 6228

• Cause: The partition has been stopped.

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

ERROR 6229 (HY000): Partition has been blocked

• Error code in OceanBase Database: 6229

• Cause: The partition has been blocked.

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

ERROR 6231 (HY000): replica is not readable

• Error code in OceanBase Database: 6231

• Cause: The current replica is not readable. This error is returned to the upper layer, and the system retries the operation.

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

ERROR 6232 (HY000): Partition is splitting

• Error code in OceanBase Database: 6232

• Cause: The partition is being split. This error is returned to the upper layer, and the system retries the operation.

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

ERROR 6233 (HY000): Transaction has been commited

• Error code in OceanBase Database: 6233

• Cause: The transaction has been committed.

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

ERROR 6235 (25000): can't serialize access for this transaction

• Error code in OceanBase Database: 6235

• Cause: The transaction cannot be serialized.

• Solution: Roll back the transaction on the client and try again.

ERROR 6236 (HY000): transaction weak read version is not ready

• Error code in OceanBase Database: 6236

• Cause: No version number is generated for weak consistency read.

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

ERROR 6237 (HY000): gts standby is invalid

• Error code in OceanBase Database: 6237

• Cause: The standby Global Timestamp Service (GTS) instance is invalid.

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

ERROR 6238 (HY000): gts update failed

• Error code in OceanBase Database: 6238

• Cause: An internal update of GTS failed.

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

ERROR 6239 (HY000): gts is not serving

• Error code in OceanBase Database: 6239

• Cause: GTS is disabled.

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

ERROR 6240 (HY000): pg partition not exist

• Error code in OceanBase Database: 6240

• Cause: The partition group does not exist.

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

ERROR 6241 (HY000): transaction statement need retry

• Error code in OceanBase Database: 6241

• Cause: The request needs to be retried. The current XA transaction may be writing logs but the rollback savepoint requires a retry, or a branch of the transaction may be running but another branch requires a retry.

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

ERROR 6243 (HY000): local schema is not new enough, replaying logs of user table from standby cluster needs to wait for schema refreshing

• Error code in OceanBase Database: 6243

• Cause: The local schema is outdated, and log replay needs to be retried.

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

ERROR 6244 (HY000): out of transaction threshold

• Error code in OceanBase Database: 6244

• Cause: The transaction size exceeds the upper limit specified by _max_trx_size.

• Solution: Adjust the transaction size.

ERROR 6245 (XAE04): Unknown XID

• Error code in OceanBase Database: 6245

• Cause: The xid value of the XA transaction is invalid.

• Solution: This is an internal error code. The returned value for the XA transaction is -4. After the transaction manager (TM) receives the returned value, contact OceanBase Technical Support to analyze the error cause.

ERROR 6246 (XAE07): The command cannot be executed when global transaction is in this state

• Error code in OceanBase Database: 6246

• Cause: The system encountered an error when executing the statement for the XA transaction.

• Solution: This is an internal error code. The returned value for the XA transaction is -7. After the transaction manager (TM) receives the returned value, contact OceanBase Technical Support to analyze the error cause.

ERROR 6247 (XAE08): The XID already exists

• Error code in OceanBase Database: 6247

• Cause: Before the system executes the XA_START statement, an XA transaction with the same xid value already exists.

• Solution: This is an internal error code. The returned value for the XA transaction is -8. After the transaction manager (TM) receives the returned value, contact OceanBase Technical Support to analyze the error cause.

ERROR 6248 (XAE09): Some work is done outside global transaction

• Error code in OceanBase Database: 6248

• Cause: Before the system executes the statement for the XA transaction, the transaction context already exists.

• Solution: This is an internal error code. The returned value for the XA transaction is -9. After the TM receives the returned value, contact OceanBase Technical Support to check the business logic to ensure that the statement is not executed in the transaction.

ERROR 6249 (XAE05): Invalid arguments were given

• Error code in OceanBase Database: 6249

• Cause: Parameters in the statement for the XA transaction are invalid.

• Solution: This is an internal error code. The returned value for the XA transaction is -5. After the transaction manager (TM) receives the returned value, contact OceanBase Technical Support to analyze the error cause.

ERROR 6250 (XAE03): Resource manager error occurred in the transaction branch

• Error code in OceanBase Database: 6250

• Cause: An unexpected error occurred when the system executed the statement for the XA transaction.

• Solution: This is an internal error code. The returned value for the XA transaction is -3. After the transaction manager (TM) receives the returned value, contact OceanBase Technical Support to analyze the error cause.

ERROR 6251 (HY000): Routine invoked in an improper context

• Error code in OceanBase Database: 6251

• Cause: The statement for the XA transaction is called in an inappropriate context.

• Solution: This is an internal error code. The returned value for the XA transaction is -6. After the transaction manager (TM) receives the returned value, contact OceanBase Technical Support to analyze the error cause.

ERROR 6252 (XA100): Rollback was caused by an unspecified reason

• Error code in OceanBase Database: 6252

• Cause: The XA transaction has been rolled back due to an unknown reason.

• Solution: This is an internal error code. The returned value for the XA transaction is 100 (XA_RBBASE). Use the TM to recognize the returned value.

ERROR 6253 (XA106): Transaction branch took long

• Error code in OceanBase Database: 6253

• Cause: The XA transaction has been rolled back due to a timeout error.

• Solution: This is an internal error code. The returned value for the XA transaction is 106 (XA_RBBASE + 6). Use the TM to recognize the returned value.

ERROR 6254 (HY000): Transaction was read-only and has been committed

• Error code in OceanBase Database: 6254

• Cause: The XA transaction is read-only, and the XA_PREPARE statement is executed.

• Solution: This is an internal error code. The returned value for the XA transaction is 3. Use the TM to recognize the returned value.

ERROR 6255 (HY000): Routine returned with no effect and may be re-issued

• Error code in OceanBase Database: 6255

• Cause: The statement for the XA transaction cannot be executed immediately. The execution needs to be retried.

• Solution: This is an internal error code. The returned value for the XA transaction is 4. Use the TM to recognize the returned value.

ERROR 6256 (HY000): Row has not been locked

• Error code in OceanBase Database: 6256

• Cause: The row has not been locked.

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

ERROR 6257 (HY000): Empty partition group

• Error code in OceanBase Database: 6257

• Cause: The partition list of the partition group is empty.

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

ERROR 6265 (HY000): object lock does not exist

• Error code in OceanBase Database: 6265

• Cause: The corresponding lock does not exist in the locked table.

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

ERROR 6266 (HY000): object lock exists

• Error code in OceanBase Database: 6266

• Cause: When the lock operation is performed on the table, the same lock already exists.

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

ERROR 6267 (HY000): Try lock object conflict

• Error code in OceanBase Database: 6267

• Cause: The locks conflict when the lock operation is performed on the table.

• Solution: This error code is reserved.

ERROR 6268 (HY000): No log callbacks available

• Error code in OceanBase Database: 6268

• Cause: The number of logs that are not called back has reached the maximum value for a single transaction. No more logs can be committed.

• Solution: Retry and wait for the log callback.

ERROR 6275 (HY000): object lock not completed, and can not unlock

• Error code in OceanBase Database: 6275

• Cause: When the DDL operation for unlocking is performed, the table lock transaction is not completed.

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

ERROR 6276 (HY000): there is an unlock operation doing, unlock conflict

• Error code in OceanBase Database: 6276

• Cause: When the DDL operation for unlocking is performed, another unlock operation is still in progress.

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

ERROR 6277 (HY000): scn is out of bounds of memtable

• Error code in OceanBase Database: 6277

• Cause: The configured SCN has exceeded the MemTable boundary limit.

• Solution: This is an internal error code. If ERROR is returned, contact OceanBase Technical Support for troubleshooting. If WARN is returned, troubleshooting is not required.

ERROR 6280 (HY000): Transaction cost too much without commit or rollback

• Error code in OceanBase Database: 6280
• Cause: The row lock cannot be released due to the long transaction lifetime.
• Solution: Analyze the business scenario to check whether the long transactions are as expected.

ERROR 6281 (HY000): Transaction commit cost too much

• Error code in OceanBase Database: 6281
• Cause: An error occurred when a transaction is committed due to its long commit or rollback period.
• Solution: Contact OceanBase Technical Support for troubleshooting.

ERROR 6302 (HY000): log scan runnable thread stop

• Error code in OceanBase Database: 6302

• Cause: An internal error occurred. During the restart of OceanBase Database, the process receives the kill -15 command and exits. In this case, this error is generated in the observer.log file.

• Solution: Restart the process.

ERROR 6303 (HY000): no log ever scanned

• Error code in OceanBase Database: 6303

• Cause: An internal error occurred. The liboblog instance finds no logs for the partition on the corresponding OBServer node.

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

ERROR 6308 (HY000): external executor handle do not finish

• Error code in OceanBase Database: 6308

• Cause: An internal error occurred. When a liboblog instance identifies the start_log_id value corresponding to the specified start timestamp and uses the value to pull logs from the relevant OBServer node by using remote procedure calls (RPCs), resumable requests are supported. If the start_log_id value cannot be identified, this error is returned to the liboblog instance. Then, the liboblog instance determines and implements the subsequent logic.

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

ERROR 6309 (HY000): cursor not exist

• Error code in OceanBase Database: 6309

• Cause: An internal error occurred. The corresponding log_id value is not found in the index log storage.

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

ERROR 6310 (HY000): stream not exist

• Error code in OceanBase Database: 6310

• Cause: An internal error occurred. The stream corresponding to the stream ID carried in the request initiated by the liboblog instance is not found in the memory of the OBServer node.

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

ERROR 6311 (HY000): stream busy

• Error code in OceanBase Database: 6311

• Cause: An internal error occurred. The liboblog instance initiates two RPCs for the same stream.

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

ERROR 6312 (HY000): file recycled

• Error code in OceanBase Database: 6312

• Cause: An internal error occurred. The clog file read based on the information recorded in the index logs has been recycled.

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

ERROR 6313 (HY000): replay eagain cost too much time

• Error code in OceanBase Database: 6313

• Cause: An internal error occurred. Confirmed logs are submitted to the replay engine, but the replay engine keeps returning the OB_EAGAIN message, which indicates that a retry is required.

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

ERROR 6314 (HY000): member change log sync failed

• Error code in OceanBase Database: 6314

• Cause: An internal error occurred. The member change task failed due to reasons such as leader switchover and must be executed again.

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

ERROR 6315 (HY000): no need batch ctx

• Error code in OceanBase Database: 6315

• Cause: An internal error occurred. The one-phase commit status of the distributed transaction in OceanBase Database is abnormal.

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

ERROR 6316 (HY000): too large log id

• Error code in OceanBase Database: 6316

• Cause: An internal error occurred. The log ID is beyond the range accepted by the current partition. For a leader, this error indicates that the number of transactions being processed in parallel exceeds the processing capacity of the current partition. For a follower, this error indicates that the follower is out of sync with the leader.

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

ERROR 6317 (HY000): alloc log id need retry

• Error code in OceanBase Database: 6317

• Cause: An internal error occurred. The number of transactions being processed in parallel exceeds the processing capacity of the log system, and the transaction engine initiates a retry.

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

ERROR 6318 (HY000): transaction one pc not allowed

• Error code in OceanBase Database: 6318

• Cause: An internal error occurred. One-phase commit of the distributed transaction failed.

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

ERROR 6319 (HY000): need rebuild

• Error code in OceanBase Database: 6319

• Cause: An internal error occurred. Logs of a follower are out of sync with the leader, and the rebuild operation must be performed to supplement the log data.

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

ERROR 6321 (HY000): ob invalid batch size

• Error code in OceanBase Database: 6321

• Cause: An internal error occurred.

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

ERROR 6322 (HY000): ob clog slide timeout

• Error code in OceanBase Database: 6322

• Cause: An internal error occurred. When the log system submits confirmed logs of a partition to the replay engine, the execution duration of the logs exceeds the preset value of the system. In this case, the log system stops processing tasks of the current partition and proceeds to the next partition.

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

ERROR 6400(HY000): tablet_freeze timeout

• Error code in OceanBase Database: 6400
• Cause: A partition-level freeze timed out.
• Solution: Contact OceanBase Technical Support for troubleshooting.