From f240463b041028e8afc2bfa891fa04f367b6017e Mon Sep 17 00:00:00 2001 From: ireneontheway Date: Mon, 20 Jul 2020 14:27:00 +0800 Subject: [PATCH 1/9] Update error-codes.md --- error-codes.md | 169 ++++++++++++++++--------------------------------- 1 file changed, 55 insertions(+), 114 deletions(-) diff --git a/error-codes.md b/error-codes.md index d988a6853798d..e0f8f3d2a54fd 100644 --- a/error-codes.md +++ b/error-codes.md @@ -13,6 +13,12 @@ This document describes the problems encountered during the use of TiDB and prov TiDB is compatible with the error codes in MySQL, and in most cases returns the same error code as MySQL. For a list of error codes for MySQL, see [Server Error Message Reference](https://dev.mysql.com/doc/refman/5.7/en/server-error-reference.html). In addition, TiDB has the following unique error codes: +> **Note:** +> +> Some errors are internal errors. Normally, TiDB handles the errors rather than return to the user. So it is not listed here. +> +> If you encounter the errors that is not listed here, contact PingCAP for support or seek help in the official forum. + * Error Number: 8001 The memory used by the request exceeds the threshold limit for the TiDB memory usage. @@ -133,29 +139,9 @@ In addition, TiDB has the following unique error codes: The field fails to obtain the default value. This error is usually used internally, and is converted to a specific type of error for external applications. -* Error Number: 8039 - - Index offset is out of range. - -* Error Number: 8042 - - The state of table schema does not exist. - -* Error Number: 8043 - - The state of column information does not exist. - -* Error Number: 8044 +* Error Number: 8040 - The state of index does not exist. - -* Error Number: 8045 - - Invalid table data. - -* Error Number: 8046 - - The state of column information is invisible. + Unsupported operations are performed. For example, operating lock table on View and Sequence. * Error Number: 8047 @@ -163,72 +149,81 @@ In addition, TiDB has the following unique error codes: * Error Number: 8048 - An unsupported database isolation level is set. + An unsupported database isolation level is set. If you cannot modify the codes by using third-party tools or frameworks, use `tidb_skip_isolation_level_check` to bypass this check. -* Error Number: 8049 + {{< copyable "sql" >}} - It fails to load the privilege related table. + ```sql + set @@tidb_skip_isolation_level_check = 1; + ``` * Error Number: 8050 An unsupported privilege type is set. + See [privilege management](/privilege-management.md#tidb-各操作需要的权限) for the solution. + * Error Number: 8051 - Unknown field type. + Unknown data type is encountered when TiDB parses the Exec argument list sent by the client. If you encounter this error, check the client. If the client is normal, contact PingCAP for support or seek help in the official forum. * Error Number: 8052 - The serial number of the data packet from the client is incorrect. - -* Error Number: 8053 + The serial number of the data packet from the client is incorrect. If you encounter this error, check the client. If the client is normal, contact PingCAP for support or seek help in the official forum. - An invalid auto-incrementing column value is obtained. * Error Number: 8055 - The current snapshot is too old. The data may have been garbage collected. - -* Error Number: 8056 - - Invalid table ID. - -* Error Number: 8057 - - Invalid field type. + The current snapshot is too old. The data may have been garbage collected. You can increase the value of `tikv_gc_life_time` to avoid this problem. The new version of TiDB automatically reserves data for long-running transactions. Usually this error does not occur. + + See [garbage collection overview](/garbage-collection-overview.md) and [garbage collection configuration](/garbage-collection-configuration.md). -* Error Number: 8058 + {{< copyable "sql" >}} - You apply an automatic variable type that does not exist. + ```sql + update mysql.tidb set VARIABLE_VALUE="24h" where VARIABLE_NAME="tikv_gc_life_time"; + ``` * Error Number: 8059 - It fails to obtain an auto-random ID. + The auto-random ID is exhausted and cannot be allocated. There is no way to recover from such errors currently. It is recommended to use bigint when using the auto random function to obtain the maximum number of assignment. And try to avoid manually assigning values to the auto random column. + + See [auto random](/auto-random.md) for reference. * Error Number: 8060 - Invalid auto-incrementing offset. + Invalid auto-incrementing offset. Check the values of `auto_increment_increment` and `auto_increment_offset`. * Error Number: 8061 Unsupported SQL Hint. + See [Optimizer Hints](/optimizer-hints.md) to check and modify the SQL Hint. + * Error Number: 8062 An invalid token is used in SQL Hint. It conflicts with reserved words in SQL Hint. + See [Optimizer Hints](/optimizer-hints.md) to check and modify the SQL Hint. + * Error Number: 8063 The limited memory usage set in SQL Hint exceeds the upper limit of the system. The setting in SQL Hint is ignored. + See [Optimizer Hints](/optimizer-hints.md) to check and modify the SQL Hint. + * Error Number: 8064 It fails to parse SQL Hint. + See [Optimizer Hints](/optimizer-hints.md) to check and modify the SQL Hint. + * Error Number: 8065 An invalid integer is used in SQL Hint. + See [Optimizer Hints](/optimizer-hints.md) to check and modify the SQL Hint. + * Error Number: 8066 The second parameter in the `JSON_OBJECTAGG` function is invalid. @@ -241,15 +236,15 @@ In addition, TiDB has the following unique error codes: * Error Number: 8102 - Unable to read the plugin definition information. + Unable to read the plugin definition information. Check the configuration related to the plugin. * Error Number: 8103 - The plugin name is incorrect. + The plugin name is incorrect. Check the configuration of the plugin. * Error Number: 8104 - The plugin version does not match. + The plugin version does not match. Check the configuration of the plugin. * Error Number: 8105 @@ -257,15 +252,15 @@ In addition, TiDB has the following unique error codes: * Error Number: 8106 - The plugin defines a system variable whose name does not begin with the plugin name. + The plugin defines a system variable whose name does not begin with the plugin name. Contact the developer of the plugin to modify. * Error Number: 8107 - The loaded plugin does not specify a version, or the specified version is too low. + The loaded plugin does not specify a version, or the specified version is too low. Check the configuration of the plugin. * Error Number: 8108 - Unsupported execution plan type. + Unsupported execution plan type. This error is an internal error. If you encounter this error, contact PingCAP for support or seek help in the official forum. * Error Number: 8109 @@ -289,10 +284,6 @@ In addition, TiDB has the following unique error codes: The table schema related in the `EXECUTE` statement has changed after the `Prepare` statement is executed. -* Error Number: 8114 - - Unknown execution plan type. - * Error Number: 8115 It is not supported to prepare multiple lines of statements. @@ -301,17 +292,13 @@ In addition, TiDB has the following unique error codes: It is not supported to prepare DDL statements. -* Error Number: 8118 - - Executor build fails. - * Error Number: 8120 - The `start tso` of transactions cannot be obtained. + The `start tso` of transactions cannot be obtained. Check the state/monitor/log of the PD server and the network between the TiDB server and the PD server. * Error Number: 8121 - Privilege check fails. + Privilege check fails. Check the privilege configuration of the database. * Error Number: 8122 @@ -319,83 +306,35 @@ In addition, TiDB has the following unique error codes: * Error Number: 8123 - An SQL query with aggregate functions returns non-aggregated columns, which violates the `only_full_group_by` mode. + An SQL query with aggregate functions returns non-aggregated columns, which violates the `only_full_group_by` mode. Modify the SQL or disable the `only_full_group_by` mode. * Error Number: 8200 The DDL syntax is not yet supported. -* Error Number: 8201 - - TiDB is currently not the DDL owner. - -* Error Number: 8202 - - The index cannot be decoded. - -* Error Number: 8203 - - Invalid DDL worker. - -* Error Number: 8204 - - Invalid DDL job. - -* Error Number: 8205 - - Invalid DDL job mark. - -* Error Number: 8206 - - The DDL operation in `re-organize` phase timed out. - -* Error Number: 8207 - - Invalid storage nodes. - -* Error Number: 8210 - - Invalid DDL state. - -* Error Number: 8211 - - Panic occurs during the DDL operation in `re-organize` phase. - -* Error Number: 8212 - - Invalid split range of Region. - -* Error Number: 8213 - - Invalid DDL job version. + See [compatibility of MySQL DDL](/mysql-compatibility.md#ddl) for reference. * Error Number: 8214 - The DDL operation is terminated. + The DDL operation is terminated by the operation of admin cancel. * Error Number: 8215 - `ADMIN REPAIR TABLE` fails. + `ADMIN REPAIR TABLE` fails. If you encounter this error, contact PingCAP for support or seek help in the official forum. * Error Number: 8216 Invalid automatic random columns. -* Error Number: 8221 - - Incorrect Key encoding. - -* Error Number: 8222 - - Incorrect index Key encoding. + See [auto random](/auto-random.md) to modify. * Error Number: 8223 - This error occurs when detecting that the data is not consistent with the index. + This error occurs when detecting that the data is not consistent with the index. If you encounter this error, contact PingCAP for support or seek help in the official forum. * Error Number: 8224 - The DDL job cannot be found. + The DDL job cannot be found. Check the job id which is specified by the restore operation. * Error Number: 8225 @@ -409,6 +348,8 @@ In addition, TiDB has the following unique error codes: Unsupported options are used when creating Sequence. + See [Sequence documentation](/sql-statements/sql-statement-create-sequence.md#参数说明) to find the list of the supported options. + * Error Number: 8229 The transaction exceeds the survival time. From b73a0363ca64ac83e8fb841151dfcd42d57a3288 Mon Sep 17 00:00:00 2001 From: ireneontheway Date: Mon, 20 Jul 2020 15:07:26 +0800 Subject: [PATCH 2/9] Update error-codes.md --- error-codes.md | 82 +++++++++++++++++++++++++++++++++++++++----------- 1 file changed, 65 insertions(+), 17 deletions(-) diff --git a/error-codes.md b/error-codes.md index e0f8f3d2a54fd..b3914d386c8e2 100644 --- a/error-codes.md +++ b/error-codes.md @@ -17,7 +17,7 @@ In addition, TiDB has the following unique error codes: > > Some errors are internal errors. Normally, TiDB handles the errors rather than return to the user. So it is not listed here. > -> If you encounter the errors that is not listed here, contact PingCAP for support or seek help in the official forum. +> If you encounter the error that is not listed here, contact PingCAP for support or seek help in the official forum. * Error Number: 8001 @@ -149,7 +149,9 @@ In addition, TiDB has the following unique error codes: * Error Number: 8048 - An unsupported database isolation level is set. If you cannot modify the codes by using third-party tools or frameworks, use `tidb_skip_isolation_level_check` to bypass this check. + An unsupported database isolation level is set. + + If you cannot modify the codes by using third-party tools or frameworks, use `tidb_skip_isolation_level_check` to bypass this check. {{< copyable "sql" >}} @@ -165,11 +167,15 @@ In addition, TiDB has the following unique error codes: * Error Number: 8051 - Unknown data type is encountered when TiDB parses the Exec argument list sent by the client. If you encounter this error, check the client. If the client is normal, contact PingCAP for support or seek help in the official forum. + Unknown data type is encountered when TiDB parses the Exec argument list sent by the client. + + If you encounter this error, check the client. If the client is normal, contact PingCAP for support or seek help in the official forum. * Error Number: 8052 - The serial number of the data packet from the client is incorrect. If you encounter this error, check the client. If the client is normal, contact PingCAP for support or seek help in the official forum. + The serial number of the data packet from the client is incorrect. + + If you encounter this error, check the client. If the client is normal, contact PingCAP for support or seek help in the official forum. * Error Number: 8055 @@ -236,15 +242,21 @@ In addition, TiDB has the following unique error codes: * Error Number: 8102 - Unable to read the plugin definition information. Check the configuration related to the plugin. + Unable to read the plugin definition information. + + Check the configuration related to the plugin. * Error Number: 8103 - The plugin name is incorrect. Check the configuration of the plugin. + The plugin name is incorrect. + + Check the configuration of the plugin. * Error Number: 8104 - The plugin version does not match. Check the configuration of the plugin. + The plugin version does not match. + + Check the configuration of the plugin. * Error Number: 8105 @@ -252,15 +264,21 @@ In addition, TiDB has the following unique error codes: * Error Number: 8106 - The plugin defines a system variable whose name does not begin with the plugin name. Contact the developer of the plugin to modify. + The plugin defines a system variable whose name does not begin with the plugin name. + + Contact the developer of the plugin to modify. * Error Number: 8107 - The loaded plugin does not specify a version, or the specified version is too low. Check the configuration of the plugin. + The loaded plugin does not specify a version, or the specified version is too low. + + Check the configuration of the plugin. * Error Number: 8108 - Unsupported execution plan type. This error is an internal error. If you encounter this error, contact PingCAP for support or seek help in the official forum. + Unsupported execution plan type. This error is an internal error. + + If you encounter this error, contact PingCAP for support or seek help in the official forum. * Error Number: 8109 @@ -294,11 +312,15 @@ In addition, TiDB has the following unique error codes: * Error Number: 8120 - The `start tso` of transactions cannot be obtained. Check the state/monitor/log of the PD server and the network between the TiDB server and the PD server. + The `start tso` of transactions cannot be obtained. + + Check the state/monitor/log of the PD server and the network between the TiDB server and the PD server. * Error Number: 8121 - Privilege check fails. Check the privilege configuration of the database. + Privilege check fails. + + Check the privilege configuration of the database. * Error Number: 8122 @@ -306,7 +328,9 @@ In addition, TiDB has the following unique error codes: * Error Number: 8123 - An SQL query with aggregate functions returns non-aggregated columns, which violates the `only_full_group_by` mode. Modify the SQL or disable the `only_full_group_by` mode. + An SQL query with aggregate functions returns non-aggregated columns, which violates the `only_full_group_by` mode. + + Modify the SQL or disable the `only_full_group_by` mode. * Error Number: 8200 @@ -320,7 +344,9 @@ In addition, TiDB has the following unique error codes: * Error Number: 8215 - `ADMIN REPAIR TABLE` fails. If you encounter this error, contact PingCAP for support or seek help in the official forum. + `ADMIN REPAIR TABLE` fails. + + If you encounter this error, contact PingCAP for support or seek help in the official forum. * Error Number: 8216 @@ -330,11 +356,15 @@ In addition, TiDB has the following unique error codes: * Error Number: 8223 - This error occurs when detecting that the data is not consistent with the index. If you encounter this error, contact PingCAP for support or seek help in the official forum. + This error occurs when detecting that the data is not consistent with the index. + + If you encounter this error, contact PingCAP for support or seek help in the official forum. * Error Number: 8224 - The DDL job cannot be found. Check the job id which is specified by the restore operation. + The DDL job cannot be found. + + Check the job id which is specified by the restore operation. * Error Number: 8225 @@ -350,12 +380,22 @@ In addition, TiDB has the following unique error codes: See [Sequence documentation](/sql-statements/sql-statement-create-sequence.md#参数说明) to find the list of the supported options. +* Error Number: 8228 + + Unsupported types are specified when using `setval` on Sequence. + + See [Sequence documentation](/sql-statements/sql-statement-create-sequence.md#示例) to find the example of the function. + * Error Number: 8229 The transaction exceeds the survival time. Commit or roll back the current transaction, and start a new transaction. +* Error Number: 8230 + + TiDB currently does not use Sequence as the default value on newly added columns. + * Error Number: 9001 The PD request timed out. @@ -406,7 +446,15 @@ In addition, TiDB has the following unique error codes: * Error Number: 9008 - Too many requests are sent to TiKV at the same time. The number exceeds limit. + Too many requests are sent to TiKV at the same time. The number exceeds limit. + + Increase `tidb_store_limit` or set it to `0` to remove the limit on the traffic of requests. + +* Error Number: 9010 + + TiKV cannot process this raft log. + + Check the state/monitor/log of the TiKV server. ## Troubleshooting From 5864d8337b7434dc6ddc9f59dd0b3cb086cb4bdf Mon Sep 17 00:00:00 2001 From: ireneontheway Date: Mon, 20 Jul 2020 15:15:13 +0800 Subject: [PATCH 3/9] Update error-codes.md --- error-codes.md | 1 - 1 file changed, 1 deletion(-) diff --git a/error-codes.md b/error-codes.md index b3914d386c8e2..5ffec3fc2b1b2 100644 --- a/error-codes.md +++ b/error-codes.md @@ -177,7 +177,6 @@ In addition, TiDB has the following unique error codes: If you encounter this error, check the client. If the client is normal, contact PingCAP for support or seek help in the official forum. - * Error Number: 8055 The current snapshot is too old. The data may have been garbage collected. You can increase the value of `tikv_gc_life_time` to avoid this problem. The new version of TiDB automatically reserves data for long-running transactions. Usually this error does not occur. From 7d897923ef5e5a444467b173ddb204bafccc7c94 Mon Sep 17 00:00:00 2001 From: ireneontheway Date: Mon, 20 Jul 2020 16:38:27 +0800 Subject: [PATCH 4/9] Update error-codes.md --- error-codes.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/error-codes.md b/error-codes.md index 5ffec3fc2b1b2..b08e1018a35cc 100644 --- a/error-codes.md +++ b/error-codes.md @@ -163,7 +163,7 @@ In addition, TiDB has the following unique error codes: An unsupported privilege type is set. - See [privilege management](/privilege-management.md#tidb-各操作需要的权限) for the solution. + See [Privileges required for TiDB operations](/privilege-management.md#privileges-required-for-tidb-operations) for the solution. * Error Number: 8051 @@ -377,13 +377,13 @@ In addition, TiDB has the following unique error codes: Unsupported options are used when creating Sequence. - See [Sequence documentation](/sql-statements/sql-statement-create-sequence.md#参数说明) to find the list of the supported options. + See [Sequence documentation](/sql-statements/sql-statement-create-sequence.md#parameters) to find the list of the supported options. * Error Number: 8228 Unsupported types are specified when using `setval` on Sequence. - See [Sequence documentation](/sql-statements/sql-statement-create-sequence.md#示例) to find the example of the function. + See [Sequence documentation](/sql-statements/sql-statement-create-sequence.md#examples) to find the example of the function. * Error Number: 8229 From 097d91329a1923c1ba169af2303dd529ef9f4d80 Mon Sep 17 00:00:00 2001 From: ireneontheway <48651140+ireneontheway@users.noreply.github.com> Date: Mon, 20 Jul 2020 16:41:26 +0800 Subject: [PATCH 5/9] Update error-codes.md It does not show in the Chinese version. --- error-codes.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/error-codes.md b/error-codes.md index b08e1018a35cc..899d2bbdd28ed 100644 --- a/error-codes.md +++ b/error-codes.md @@ -431,12 +431,6 @@ In addition, TiDB has the following unique error codes: Extend the interval of GC Life Time. -* Error Number: 9500 - - A single transaction is too large. - - See [the error message `transaction too large`](/faq/tidb-faq.md#the-error-message-transaction-too-large-is-displayed) for the solution. - * Error Number: 9007 Transactions in TiKV encounter write conflicts. From 1a4e01f97dbf3759860522c8329f23f47b77833e Mon Sep 17 00:00:00 2001 From: ireneontheway <48651140+ireneontheway@users.noreply.github.com> Date: Tue, 21 Jul 2020 21:42:17 +0800 Subject: [PATCH 6/9] Apply suggestions from code review Co-authored-by: Keke Yi <40977455+yikeke@users.noreply.github.com> --- error-codes.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/error-codes.md b/error-codes.md index 899d2bbdd28ed..3e862dd91e739 100644 --- a/error-codes.md +++ b/error-codes.md @@ -15,9 +15,9 @@ In addition, TiDB has the following unique error codes: > **Note:** > -> Some errors are internal errors. Normally, TiDB handles the errors rather than return to the user. So it is not listed here. +> Some error codes stand for internal errors. Normally, TiDB handles the errors rather than return to the user, so some error codes are not listed here. > -> If you encounter the error that is not listed here, contact PingCAP for support or seek help in the official forum. +> If you encounter an error code that is not listed here, [contact PingCAP](mailto:info@pingcap.com) for support. * Error Number: 8001 From 40f3417d3da1980fe2735d4e48260ebae20c3dff Mon Sep 17 00:00:00 2001 From: ireneontheway Date: Tue, 21 Jul 2020 21:48:48 +0800 Subject: [PATCH 7/9] Update error-codes.md --- error-codes.md | 20 +++++++++++++------- 1 file changed, 13 insertions(+), 7 deletions(-) diff --git a/error-codes.md b/error-codes.md index 3e862dd91e739..381e2c6949108 100644 --- a/error-codes.md +++ b/error-codes.md @@ -35,7 +35,7 @@ In addition, TiDB has the following unique error codes: If the data in a row is not consistent with the index when executing the `ADMIN CHECK TABLE` command, TiDB returns this error. This error is commonly seen when you check the data corruption in the table. - You can contact PingCAP for support or seek help in the official forum. + You can [contact PingCAP](mailto:info@pingcap.com) for support. * Error Number: 8004 @@ -85,7 +85,7 @@ In addition, TiDB has the following unique error codes: Invalid transactions. If TiDB finds that no transaction ID (Start Timestamp) is obtained for the transaction that is being executed, which means this transaction is invalid, this error is returned. - Usually this error does not occur. If you encounter this error, contact PingCAP for support or seek help in the official forum. + Usually this error does not occur. If you encounter this error, [contact PingCAP](mailto:info@pingcap.com) for support. * Error Number: 8025 @@ -169,13 +169,13 @@ In addition, TiDB has the following unique error codes: Unknown data type is encountered when TiDB parses the Exec argument list sent by the client. - If you encounter this error, check the client. If the client is normal, contact PingCAP for support or seek help in the official forum. + If you encounter this error, check the client. If the client is normal, [contact PingCAP](mailto:info@pingcap.com) for support. * Error Number: 8052 The serial number of the data packet from the client is incorrect. - If you encounter this error, check the client. If the client is normal, contact PingCAP for support or seek help in the official forum. + If you encounter this error, check the client. If the client is normal, [contact PingCAP](mailto:info@pingcap.com) for support. * Error Number: 8055 @@ -277,7 +277,7 @@ In addition, TiDB has the following unique error codes: Unsupported execution plan type. This error is an internal error. - If you encounter this error, contact PingCAP for support or seek help in the official forum. + If you encounter this error, [contact PingCAP](mailto:info@pingcap.com) for support. * Error Number: 8109 @@ -345,7 +345,7 @@ In addition, TiDB has the following unique error codes: `ADMIN REPAIR TABLE` fails. - If you encounter this error, contact PingCAP for support or seek help in the official forum. + If you encounter this error, [contact PingCAP](mailto:info@pingcap.com) for support. * Error Number: 8216 @@ -357,7 +357,7 @@ In addition, TiDB has the following unique error codes: This error occurs when detecting that the data is not consistent with the index. - If you encounter this error, contact PingCAP for support or seek help in the official forum. + If you encounter this error, [contact PingCAP](mailto:info@pingcap.com) for support. * Error Number: 8224 @@ -431,6 +431,12 @@ In addition, TiDB has the following unique error codes: Extend the interval of GC Life Time. +* Error Number: 9500 + + A single transaction is too large. + + See [the error message `transaction too large`](/faq/tidb-faq.md#the-error-message-transaction-too-large-is-displayed) for the solution. + * Error Number: 9007 Transactions in TiKV encounter write conflicts. From eb6663ab481252740c97fc9997fa8bc4517d161e Mon Sep 17 00:00:00 2001 From: ireneontheway <48651140+ireneontheway@users.noreply.github.com> Date: Thu, 23 Jul 2020 13:34:47 +0800 Subject: [PATCH 8/9] Apply suggestions from code review Co-authored-by: Keke Yi <40977455+yikeke@users.noreply.github.com> --- error-codes.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/error-codes.md b/error-codes.md index 381e2c6949108..fd489e3998ade 100644 --- a/error-codes.md +++ b/error-codes.md @@ -15,7 +15,7 @@ In addition, TiDB has the following unique error codes: > **Note:** > -> Some error codes stand for internal errors. Normally, TiDB handles the errors rather than return to the user, so some error codes are not listed here. +> Some error codes stand for internal errors. Normally, TiDB handles the error rather than return it to the user, so some error codes are not listed here. > > If you encounter an error code that is not listed here, [contact PingCAP](mailto:info@pingcap.com) for support. @@ -151,7 +151,7 @@ In addition, TiDB has the following unique error codes: An unsupported database isolation level is set. - If you cannot modify the codes by using third-party tools or frameworks, use `tidb_skip_isolation_level_check` to bypass this check. + If you cannot modify the codes because you are using a third-party tool or framework, consider using `tidb_skip_isolation_level_check` to bypass this check. {{< copyable "sql" >}} @@ -191,7 +191,7 @@ In addition, TiDB has the following unique error codes: * Error Number: 8059 - The auto-random ID is exhausted and cannot be allocated. There is no way to recover from such errors currently. It is recommended to use bigint when using the auto random function to obtain the maximum number of assignment. And try to avoid manually assigning values to the auto random column. + The auto-random ID is exhausted and cannot be allocated. There is no way to recover from such errors currently. It is recommended to use bigint when using the auto random feature to obtain the maximum number of assignment. And try to avoid manually assigning values to the auto random column. See [auto random](/auto-random.md) for reference. @@ -329,7 +329,7 @@ In addition, TiDB has the following unique error codes: An SQL query with aggregate functions returns non-aggregated columns, which violates the `only_full_group_by` mode. - Modify the SQL or disable the `only_full_group_by` mode. + Modify the SQL statement or disable the `only_full_group_by` mode. * Error Number: 8200 @@ -339,7 +339,7 @@ In addition, TiDB has the following unique error codes: * Error Number: 8214 - The DDL operation is terminated by the operation of admin cancel. + The DDL operation is terminated by the `admin cancel` operation. * Error Number: 8215 @@ -349,7 +349,7 @@ In addition, TiDB has the following unique error codes: * Error Number: 8216 - Invalid automatic random columns. + The usage of automatic random columns is incorrect. See [auto random](/auto-random.md) to modify. @@ -363,7 +363,7 @@ In addition, TiDB has the following unique error codes: The DDL job cannot be found. - Check the job id which is specified by the restore operation. + Check whether the job id specified by the `restore` operation exists. * Error Number: 8225 @@ -393,7 +393,7 @@ In addition, TiDB has the following unique error codes: * Error Number: 8230 - TiDB currently does not use Sequence as the default value on newly added columns. + TiDB currently does not support using Sequence as the default value on newly added columns, and reports this error if you use it. * Error Number: 9001 From fb8fae91a27f6ea01376472cf0a2d6a584c01abf Mon Sep 17 00:00:00 2001 From: ireneontheway <48651140+ireneontheway@users.noreply.github.com> Date: Fri, 24 Jul 2020 10:40:39 +0800 Subject: [PATCH 9/9] Update error-codes.md Co-authored-by: Keke Yi <40977455+yikeke@users.noreply.github.com> --- error-codes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/error-codes.md b/error-codes.md index fd489e3998ade..b919939c906b0 100644 --- a/error-codes.md +++ b/error-codes.md @@ -141,7 +141,7 @@ In addition, TiDB has the following unique error codes: * Error Number: 8040 - Unsupported operations are performed. For example, operating lock table on View and Sequence. + Unsupported operations are performed. For example, you perform a table locking operation on a view or a sequence. * Error Number: 8047