<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0">
<channel>
<title><![CDATA[向东博客 专注WEB应用 构架之美 --- 构架之美，在于尽态极妍 | 应用之美，在于药到病除]]></title> 
<link>https://jackxiang.com/index.php</link> 
<description><![CDATA[赢在IT，Playin' with IT,Focus on Killer Application,Marketing Meets Technology.]]></description> 
<language>zh-cn</language> 
<copyright><![CDATA[向东博客 专注WEB应用 构架之美 --- 构架之美，在于尽态极妍 | 应用之美，在于药到病除]]></copyright>
<item>
<link>https://jackxiang.com/post//</link>
<title><![CDATA[[实践OK]mysqldump:Unknown system variable GTID_MODE 原因与解决方法,Table performance_schema.session_variables doesnt exist (1146),]]></title> 
<author>jack &lt;xdy108@126.com&gt;</author>
<category><![CDATA[数据库技术]]></category>
<pubDate>Fri, 18 Dec 2015 16:09:14 +0000</pubDate> 
<guid>https://jackxiang.com/post//</guid> 
<description>
<![CDATA[ 
	背景：升级了一下mysql到最新版本 5.7.9，博客数据没有动，后导出数据备份时出现Couldn&#039;t execute &#039;SHOW VARIABLES LIKE &#039;gtid&#92;_mode&#039;&#039;，加上 --set-gtid-purged=off出现新错误的问题，总之一堆问题，最后还是终于导出了，特别是升级后一定要重启，啥玩意，艹。<br/>实践如下，出现问题：<br/>[root@iZ25dcp92ckZ backup]# mysqldump -uroot -p -ujustwinit_mysql_database &gt; -ujustwinit_mysql_database.cn.sql<br/>Enter password: <br/>mysqldump: Couldn&#039;t execute &#039;SHOW VARIABLES LIKE &#039;gtid&#92;_mode&#039;&#039;: Table &#039;performance_schema.session_variables&#039; doesn&#039;t exist (1146)<br/><br/><br/><br/><br/>用mysqldump备份时出现下面的出错信息：<br/>mysqldump:Couldn&#039;t execute&nbsp;&nbsp;‘SELECT @@GTID_MODE&#039;:Unknown system variable &#039;GTID_MODE&#039; (1193)<br/>造成此错误的原因是因为5.6引入了Global Transaction Identifiers (GTIDs) 。GTIDs可以让主从结构复制的跟踪和比较变得简单。mysqldump会试图查询这个系统变量，但这个变量在5.6之前的版本中不存在，所以产生错误。解决的方法很简单，在mysqldump后加上–set-gtid-purged=OFF命令<br/>如：<br/>mysqldump -h(主机名或ip) -u(用户名) -p(密码) 数据库名 --set-gtid-purged=off &gt;d:/db.sql<br/><br/>From:http://www.rjkfw.com/s_3139.html<br/>___________________________________________________________________<br/><br/>[root@iZ25dcp92ckZ ~]#&nbsp;&nbsp;mysqldump&nbsp;&nbsp;--set-gtid-purged=off -uroot -p -ujustwinit_mysql_database &gt; -ujustwinit_mysql_database.cn.sql<br/>Enter password: <br/>mysqldump: Couldn&#039;t execute &#039;SHOW VARIABLES LIKE &#039;ndbinfo&#92;_version&#039;&#039;: Table &#039;performance_schema.session_variables&#039; doesn&#039;t exist (1146)<br/>解决办法：<br/>[root@iZ25dcp92ckZ ~]# mysql_upgrade -u root -p --force<br/>Enter password: <br/>Checking server version.<br/>Running queries to upgrade MySQL server.<br/>Checking system database.<br/>mysql.columns_priv&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OK<br/>mysql.db&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OK<br/>。。。。。。<br/>sys.sys_config&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OK<br/>temperature.temperature&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;OK<br/>temperature.tempsetting&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;OK<br/>Upgrade process completed successfully.<br/>Checking if update is needed.<br/><br/>再次导出：<br/>[root@iZ25dcp92ckZ ~]#&nbsp;&nbsp;mysqldump&nbsp;&nbsp;--set-gtid-purged=off -uroot -p -ujustwinit_mysql_database &gt; -ujustwinit_mysql_database.cn.sql<br/>Enter password: <br/>mysqldump: Couldn&#039;t execute &#039;SHOW VARIABLES LIKE &#039;ndbinfo&#92;_version&#039;&#039;: Native table &#039;performance_schema&#039;.&#039;session_variables&#039; has the wrong structure (1682)<br/><br/>忘记重启了，于是重启下,再次导出，出现新的错：<br/>[root@iZ25dcp92ckZ bin]#&nbsp;&nbsp;mysqldump&nbsp;&nbsp;--set-gtid-purged=off -u-ujustwinit_mysql_database_mysql_database -p -ujustwinit_mysql_database_mysql &gt; -ujustwinit_mysql_database.cn.sql<br/>Enter password: <br/>mysqldump: Got error: 1044: Access denied for user &#039;-ujustwinit_mysql_database_mysql&#039;@&#039;localhost&#039; to database &#039;-ujustwinit_mysql_database_mysql&#039; when using LOCK TABLES<br/><br/>用mysqldump备份数据库时出现when using LOCK TABLES_：<br/> --skip-lock-tables<br/>普通用户备份mysql 数据库报错<br/><br/>mysql 无lock tables权限 报Access denied for user &#039;dbuser&#039;@&#039;localhost&#039; to database &#039;db&#039; when using LOCK TABLES<br/><br/>主要原因是该用户无lock tables 该权限，处理办法：<br/><br/>1. 给该普通用户赋予lock tables 权限，建议是删除该用户，重新用mysql命令建<br/><br/>2. 加上--skip-lock-tables即可<br/><br/>mysqldump -udbuser -p dbname --skip-lock-tables &gt; dbname.sql<br/><br/><br/>3. 使用root 备份<br/><br/><br/>MySQL无lock tables权限 报Access denied for user when using LOCK TABLES：<br/>http://www.linuxidc.com/Linux/2012-01/51802.htm<br/><br/> mysqldump&nbsp;&nbsp;--set-gtid-purged=off --skip-lock-tables -u-ujustwinit_mysql_database_mysql_database -p -ujustwinit_mysql_database_mysql &gt; -ujustwinit_mysql_database.cn.sql<br/><br/>成功了：<br/>[root@iZ25dcp92ckZ bin]# mysqldump&nbsp;&nbsp;--set-gtid-purged=off --skip-lock-tables -uroot -p justwinit_mysql_database&nbsp;&nbsp;&gt; jackxiang.com.database.bak.perfected.2015.12.29.sql<br/>Enter password: <br/><br/><br/><br/>来自：http://www.amznz.com/error-native-table-performance_schema/<br/><br/><br/>
]]>
</description>
</item><item>
<link>https://jackxiang.com/post//#blogcomment</link>
<title><![CDATA[[评论] [实践OK]mysqldump:Unknown system variable GTID_MODE 原因与解决方法,Table performance_schema.session_variables doesnt exist (1146),]]></title> 
<author> &lt;user@domain.com&gt;</author>
<category><![CDATA[评论]]></category>
<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate> 
<guid>https://jackxiang.com/post//#blogcomment</guid> 
<description>
<![CDATA[ 
	
]]>
</description>
</item>
</channel>
</rss>