This topic describes the error messages for user tenants in OceanBase AI Database.
Error message format
OceanBase AI Database is highly compatible with MySQL, which is reflected not only in common MySQL features and the MySQL client-server protocol but also in the native error messages of OceanBase AI Database, which are compatible with MySQL. Therefore, the error message format for user tenants in OceanBase AI Database is consistent with MySQL.
The error message format is as follows:
ERROR <err_num> (<sql_stat>) : err_msg
The parameters are described as follows:
err_numindicates the error code.sql_statindicates the SQL STATE.err_msgindicates the error message.
Variables in error messages
To help you locate and resolve errors, OceanBase AI Database embeds parameters into error messages. In this topic, these parameters are displayed as percent signs (%).
Example:
ERROR 4626 (HY000) : resource pool '%s' has already been granted to a tenant
The actual message may be displayed as follows:
ERROR 4626 (HY000) : resource pool 'pool1' has already been granted to a tenant
Error message reference table
The following table describes the system error codes, their values, and descriptions.
Error Code Range |
Description |
|---|---|
| 0001 ~ 3999 | Compatibility with MySQL error messages.
|
| 4000 ~ 4499 | General error code. |
| 4500 ~ 4999 | Root service error code. |
| 5000 ~ 5999 | SQL statements, WITH clauses, and factoring error codes. |
| 6000 ~ 6999 | Transactions, MVCC, and clog error codes. |
| 7000 ~ 7999 | Error code of the election module. |
| 8000 ~ 8999 | Fatal error. When the client receives an error within this range, it must close the SQL connection. |
| 9000 ~ 9499 | Backup and recovery, and STORAGE 3.0 error codes. |
| 9500 ~ 9999 | Procedural Language (PL) error codes. |
| 22998, 30926, 38104, 38105 | BLOB/CLOB error codes. |