mysqldump: Couldn’t execute ‘SELECT @@GTID_MODE...
在使用MySQL 5.6的mysqldump备份5.6以前版本的MySQL时会遇到异常 mysql
mysqldump: Couldn't execute 'SELECT @@GTID_MODE': Unknown system variable 'GTID_MODE' (1193)
形成此错误的缘由是由于5.6引入了Global Transaction Identifiers (GTIDs) 。GTIDs可让主从结构复制的跟踪和比较变得简单。mysqldump会试图查询这个系统变量，但这个变量在5.6以前的版本中不存在，因此产生错误。的方法很简单。在mysqldump后加上–set-gtid-purged=OFF命令。 sql
mysqldump -h dbHost -u dbuser dbName --set-gtid-purged=OFF
相关文章
- 1. mysqldump: Couldn't execute 'SELECT @@GTID_MODE':
- 2. mysqldump:Couldn't execute ‘SELECT @@GTID_MODE':Un
- 3. mysqldump: Couldn't execute 'SELECT COLUMN_NAME
- 4. mysqldump: Couldn't execute 'SELECT COLUMN_NAME, JSON_EXTRACT(HISTOGRAM, '$."n
- 5. mysqldump 导出提示Couldn't execute SELECT COLUMN_NAME...
- 6. mysqldump: Couldn't execute 'show table status '解决方法
- 7. Couldn't execute 'SELECT COLUMN_NAME, JSON_EXTRACT(HISTOGRAM, '$."number-of-b
- 8. 导出提示Couldn't execute 'SELECT COLUMN_NAME,JSON_EXTRACT(HISTOGRAM, '$."number-of-buckets-specified"')
- 9. DataGrip 导出表结构和数据 mysqldump: Couldn't execute
- 10. mysqldump
- 更多相关文章...
- • PDOStatement::execute - PHP参考手册
- • ASP Execute 方法 - ASP 教程
- • 漫谈MySQL的锁机制
- • 三篇文章了解 TiDB 技术内幕 —— 说计算
相关标签/搜索
每日一句
-
每一个你不满意的现在，都有一个你没有努力的曾经。
欢迎关注本站公众号,获取更多信息
相关文章
- 1. mysqldump: Couldn't execute 'SELECT @@GTID_MODE':
- 2. mysqldump:Couldn't execute ‘SELECT @@GTID_MODE':Un
- 3. mysqldump: Couldn't execute 'SELECT COLUMN_NAME
- 4. mysqldump: Couldn't execute 'SELECT COLUMN_NAME, JSON_EXTRACT(HISTOGRAM, '$."n
- 5. mysqldump 导出提示Couldn't execute SELECT COLUMN_NAME...
- 6. mysqldump: Couldn't execute 'show table status '解决方法
- 7. Couldn't execute 'SELECT COLUMN_NAME, JSON_EXTRACT(HISTOGRAM, '$."number-of-b
- 8. 导出提示Couldn't execute 'SELECT COLUMN_NAME,JSON_EXTRACT(HISTOGRAM, '$."number-of-buckets-specified"')
- 9. DataGrip 导出表结构和数据 mysqldump: Couldn't execute
- 10. mysqldump