The workaround for error 1840 when MySQL imports the database

Source: Internet
Author: User

1. Phenomenon

When MySQL imports the database with SQL files, it prompts the error 1840 (HY000) at line: @ @GLOBAL. Gtid_purged can only is set when @ @GLOBAL. Gtid_executed is empty.

Description: The MySQL database was just installed, has never been configured for master-slave replication, and has not been configured for Gtid master-slave replication.

  

2. Solution

After checking the online information, after the test found that the following method can solve my problem

Go to MySQL mode, reset Master

# mysql-u Root-p

Enter password

mysql> Reset Master;

  

After exiting, re-import, OK. Let the machine import the data on its own.

  

The workaround for error 1840 when MySQL imports the database

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.