Shulou(Shulou.com)05/31 Report--

This article will explain in detail how to solve the problem of MySQl error reporting @ @ GLOBAL.GTID_PURGED can only be set when @ @ GLOBAL.GTID_MODE = ON. The editor thinks it is very practical, so I share it with you as a reference. I hope you can get something after reading this article.

Dump a databases data in the SLAVE of one MySQL database and want to import it into another machine's database, but an error is reported:

Warning: Using a password on the command line interface can be insecure.

ERROR 1839 (HY000) at line 24: @ @ GLOBAL.GTID_PURGED can only be set when @ @ GLOBAL.GTID_MODE = ON.

The reason for the error is that gtid is opened in the original database, and the-- set-gtid-purged=on parameter needs to be specified in the mysqldump statement.

Is it possible that mysqldump took a long time to complete the data, and then scp also took a long time to get to the target machine, and found that there was no way to report this error? Need to re-mysqldump?

Definitely not. Just add the-f parameter when importing, for example:

Mysql-uroot-pSunstar2012Hecom888ser8686-h57.93.xx.xx-f cus_DEMO < / alidata1/backup/gl/gl/cus_DEMO_gl.sql

This is the end of the article on "MySQl error reporting @ @ GLOBAL.GTID_PURGED can only be set when @ @ GLOBAL.GTID_MODE = ON". I hope the above content can be helpful to you, so that you can learn more knowledge. if you think the article is good, please share it for more people to see.

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.