mysqldump 导出数据库报错“does not exist when using LOCK TABLES”
2013-07-29 17:01
791 查看
mysqldump 导出数据库报错“does not exist when using LOCK TABLES”
现象如下:
[user@tz-manage01 ~]$ mysqldump -uroot -p2008 schedule >schedule.sql
mysqldump: Got error: 1449: The user specified as a definer ('kevin'@'192.168.16.0/255.255.255.0') does not exist when using LOCK TABLES
[user@tz-manage01 ~]$ mysqldump -uroot -p2008 -h192.168.18.52 -x schedule >/tmp/schedule.sql
mysqldump: Got error: 1449: The user specified as a definer ('user'@'192.168.16.0/255.255.255.0') does not exist when using LOCK TABLES
排查解决:
1.
在网上查了一下,说root用户访问权限不够,于是为root用户授权;
grant all privileges on *.* to root@"192.168.0.0/255.255.0.0" identified by "2008";
1.1
确认root授权成功;
mysql> SELECT DISTINCT CONCAT('User: ''',user,'''@''',host,''';') AS query FROM mysql.user;
+-------------------------------------------------+
| query |
+-------------------------------------------------+
| User: 'root'@'%'; |
| User: 'root'@'localhost'; |
+-------------------------------------------------+
9 rows in set (0.00 sec)
1.2
授权完成,再次执行dump语句;
[user@tz-manage01 ~]$ mysqldump -uroot -p2008 -h192.168.18.52 schedule >/tmp/schedule.sql
mysqldump: Got error: 1449: The user specified as a definer ('user'@'192.168.16.0/255.255.255.0') does not exist when using LOCK TABLES
1.3
发现执行还是报错,于是测试导出一个mysql其它数据库试一下,发现能够正常导出,说明不是权限问题。
[user@tz-manage01 ~]$ mysqldump -uroot -p2008 -h192.168.18.52 monitor >/tmp/schedule.sql
[user@tz-manage01 ~]$ ll /tmp/
-rw-rw-r--. 1 user user 4550638 Jul 29 16:46 schedule.sql
1.4,解决
经以上排查,确认应该是schedule 数据库在使用状态,所以导出数据时报错,在mysqldump时使用 -x 选项解决此问题。
--lock-all-tables,-x
在开始导出之前,提交请求锁定所有数据库中的所有表,以保证数据的一致性。这是一个全局读锁,并且自动关闭 --single-transaction 和 --lock-tables 选项。
[user@tz-manage01 ~]$ mysqldump -uroot -p2008 -h192.168.18.52 -x schedule >/tmp/schedule.sql
-rw-rw-r--. 1 user user 786 Jul 29 16:47 schedule.sql
本文出自 “康建华” 博客,请务必保留此出处http://michaelkang.blog.51cto.com/1553154/1259799
现象如下:
[user@tz-manage01 ~]$ mysqldump -uroot -p2008 schedule >schedule.sql
mysqldump: Got error: 1449: The user specified as a definer ('kevin'@'192.168.16.0/255.255.255.0') does not exist when using LOCK TABLES
[user@tz-manage01 ~]$ mysqldump -uroot -p2008 -h192.168.18.52 -x schedule >/tmp/schedule.sql
mysqldump: Got error: 1449: The user specified as a definer ('user'@'192.168.16.0/255.255.255.0') does not exist when using LOCK TABLES
排查解决:
1.
在网上查了一下,说root用户访问权限不够,于是为root用户授权;
grant all privileges on *.* to root@"192.168.0.0/255.255.0.0" identified by "2008";
1.1
确认root授权成功;
mysql> SELECT DISTINCT CONCAT('User: ''',user,'''@''',host,''';') AS query FROM mysql.user;
+-------------------------------------------------+
| query |
+-------------------------------------------------+
| User: 'root'@'%'; |
| User: 'root'@'localhost'; |
+-------------------------------------------------+
9 rows in set (0.00 sec)
1.2
授权完成,再次执行dump语句;
[user@tz-manage01 ~]$ mysqldump -uroot -p2008 -h192.168.18.52 schedule >/tmp/schedule.sql
mysqldump: Got error: 1449: The user specified as a definer ('user'@'192.168.16.0/255.255.255.0') does not exist when using LOCK TABLES
1.3
发现执行还是报错,于是测试导出一个mysql其它数据库试一下,发现能够正常导出,说明不是权限问题。
[user@tz-manage01 ~]$ mysqldump -uroot -p2008 -h192.168.18.52 monitor >/tmp/schedule.sql
[user@tz-manage01 ~]$ ll /tmp/
-rw-rw-r--. 1 user user 4550638 Jul 29 16:46 schedule.sql
1.4,解决
经以上排查,确认应该是schedule 数据库在使用状态,所以导出数据时报错,在mysqldump时使用 -x 选项解决此问题。
--lock-all-tables,-x
在开始导出之前,提交请求锁定所有数据库中的所有表,以保证数据的一致性。这是一个全局读锁,并且自动关闭 --single-transaction 和 --lock-tables 选项。
[user@tz-manage01 ~]$ mysqldump -uroot -p2008 -h192.168.18.52 -x schedule >/tmp/schedule.sql
-rw-rw-r--. 1 user user 786 Jul 29 16:47 schedule.sql
本文出自 “康建华” 博客,请务必保留此出处http://michaelkang.blog.51cto.com/1553154/1259799
相关文章推荐
- mysqldump 导出数据库报错 “does not exist when using LOCK TABLES”
- mysqldump 导出数据库报错“does not exist when using LOCK TABLES”
- mysqldump 导出数据库报错“does not exist when using LOCK T
- Centos下_MysqL5.7在使用mysqldump命令备份数据库报错:mysqldump: Got error: 1449: The user specified as a definer ('fk_system'@'localhost') does not exist when using LOCK TABLES
- mysqldump报错'The user specified as a definer ('root'@'%') does not exist when using LOCK TABLES'
- Got error: 1449: The user specified as a definer ('root'@'%') does not exist when using LOCK TAB
- 【转】 The user specified as a definer ('root'@'') does not exist when using LOCK TALBE
- Got error: 1449: The user specified as a definer ('root'@'%') does not exist when using LOCK TAB
- mysqldump: Got error: 1066: Not unique table/alias: 'dept' when using LOCK TABLES
- mysqldump: Got error: 1146: Table 'performance_schema.cond_instances' doesn't exist when using LOCK
- 用mysqldump备份数据库时出现when using LOCK TABLES
- mysqldump: Got error: 1146: Table 'performance_schema.cond_instances' doesn't exist when using LOCK
- mysql -- mysqldump错误:Got error: 1044: Access denied for user ... when using LOCK TABLES (转载)
- 使用mysqldump备份时出现“when using LOCK TABLES”错误的解决方法
- 在给mysql数据库备份时,报错: mysqldump: Got error: 145: Table '.\shengdaxcom\pre_forum_thread' is marked as c rashed and should be repaired when using LOCK TABLES
- mysqldump备份数据库时出现when using LOCK TABLES的提示
- mysql -- mysqldump错误:Got error: 1044: Access denied for user ... when using LOCK TABLES
- mysqldump: 1044 Access denied when using LOCK TABLES
- mysqldump备份数据库时出现when using LOCK TABLES
- mysqldump备份数据库时出现when using LOCK TABLES