Shulou(Shulou.com)06/01 Report--

This article mainly introduces the methods to solve the common mistakes in mysql, hoping to supplement and update some knowledge for you. If you have any other questions you need to know, you can continue to follow my updated article in the industry information.

Solve the problem that mysql uses binary log to recover data report error: ERROR 1781 (HY000) at line 16: @ @ SESSION.GTID_NEXT cannot be set to UUID:NUMBER when @ @ GLOBAL.GTID_MODE = OFF.

Solution:

Configure gtid option

Before configuration:

Mysql > show global variables like 'gtid_mode'

ERROR 2006 (HY000): MySQL server has gone away

No connection. Trying to reconnect...

Connection id: 24

Current database: gold

+-+ +

| | Variable_name | Value |

+-+ +

| | gtid_mode | OFF |

+-+ +

1 row in set (0.10 sec)

After configuration:

Mysql > set @ @ GLOBAL.GTID_MODE = OFF_PERMISSIVE

Mysql > show global variables like 'gtid_mode'

+-+ +

| | Variable_name | Value |

+-+ +

| | gtid_mode | OFF_PERMISSIVE |

+-+ +

1 row in set (0.00 sec)

Resolve ERROR 1062 (23000): Duplicate entry'4' for key 'PRIMARY'

Before configuration:

Resolve:

Mysql modifies the primary key to grow itself

Alter table test change id id int AUTO_INCREMENT

Read the above methods to solve the common mistakes of mysql, hoping to bring some help to you in practical application. Due to the limited space in this article, it is inevitable that there will be deficiencies and need to be supplemented. If you need more professional answers, you can contact us on the official website for 24-hour pre-sales and after-sales to help you answer questions at any time.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.