mysql slave不能同步Last_SQL_Error Error Duplicate entry

最新推荐文章于 2024-02-21 15:22:51 发布
原创 最新推荐文章于 2024-02-21 15:22:51 发布 · 536 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#mysql #slave

本文介绍了一种在MySQL从库上遇到错误时，通过设置全局变量SQL_SLAVE_SKIP_COUNTER为1来跳过特定错误的方法。这有助于在不中断复制的情况下解决从库上的临时问题。

slave stop;

set GLOBAL SQL_SLAVE_SKIP_COUNTER=1;

slave start;

《MySQL系列-主从相关》MySQL主从同步问题记录
https://blog.datasource.space
05-14 2565
1.MySQL主从同步Slave_SQL_Running错误 2.MySQL从库Error:"You cannot 'Alter' a log table..." 3.MySQL从库Slave_IO_Running异常，Last_IO_Error: Got fatal error 1236 from master when reading data from binary log
故障分析 | Sql_slave_skip_counter 使用不规范对复制的影响
ActionTech的博客
08-09 640
规范使用 sql_slave_skip_counter ，如果操作不当，极有可能跳过其他 events ，并造成主从数据不一致。如果数据库数据量较小，大约60G左右，建议重做复制。数据量超过60G大小，可以在 sql_slave_skip_counter 跳过之前，看一下当前 binlog event group 执行了哪些操作。对于1032、1062错误尽量修补数据，让复制进程在从库应用变更。...
Slave SQL: Error 'Duplicate entry '3301' for key
chuoshan4222的博客
11-03 212
下午slave服务器报错 SlaveSQL:Error'Duplicateentry'3301'forkey'PRIMARY''onquery.Defaultdatabase:'sdm16315584_db'.Query:'INSERTINTO`lzh_ve...
mysql slave error_Mysql slave error
weixin_29813667的博客
01-19 132
140109 15:13:13 [Note] Slave: received end packet from server, apparent master shutdown:140109 15:13:13 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'mysql-binlog.0008...
Mysql slave error
weixin_34315665的博客
03-13 147
140109 15:13:13 [Note] Slave: received end packet from server, apparent master shutdown:140109 15:13:13 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'mysql-...
mysql slave error_mysql slave error
weixin_33842051的博客
02-26 166
空间不足，导致同步停止130906 13:25:52 [ERROR] log /data/mysql/var/mysql-relay-bin.000332 listed in the index, but failed to stat130906 13:25:52 [ERROR] Error counting relay log space130906 13:31:50 [ERROR] log /...
mysql slave duplicate entry_mysql slave不能同步Last_SQL_Error: Error ‘Duplicate entry ‘
05-20
3. 如果错误信息是 "Duplicate entry"，则可以手动跳过该 SQL 语句。在从库上执行以下命令： STOP SLAVE; SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1; START SLAVE; 这里的 "1" 表示跳过一个 SQL 语句，如果错误...
Last_Errno: 1062，Last_Error: Error Duplicate entry
09-10
在使用MySQL数据库时，经常可能会遇到一些错误提示，其中“Last_Errno: 1062, Last_Error: Error Duplicate entry”是一个比较常见的错误。这个错误通常出现在执行数据插入（INSERT）或更新（UPDATE）操作时，导致...
mysql> SELECT * FROM performance_schema.replication_applier_status_by_worker \G *************************** 1. row *************************** CHANNEL_NAME: WORKER_ID: 1 THREAD_ID: NULL SERVICE_STATE: OFF LAST_ERROR_NUMBER: 0 LAST_ERROR_MESSAGE: LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241752528 LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.872259 LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.872259 LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:07:20.962510 LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 2025-10-04 08:07:20.964174 APPLYING_TRANSACTION: APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION_RETRIES_COUNT: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_RETRIES_COUNT: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 *************************** 2. row *************************** CHANNEL_NAME: WORKER_ID: 2 THREAD_ID: NULL SERVICE_STATE: OFF LAST_ERROR_NUMBER: 0 LAST_ERROR_MESSAGE: LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241752527 LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.871746 LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.871746 LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:07:20.961392 LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 2025-10-04 08:07:20.963864 APPLYING_TRANSACTION: APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION_RETRIES_COUNT: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_RETRIES_COUNT: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 *************************** 3. row *************************** CHANNEL_NAME: WORKER_ID: 3 THREAD_ID: NULL SERVICE_STATE: OFF LAST_ERROR_NUMBER: 1062 LAST_ERROR_MESSAGE: Worker 3 failed executing transaction '5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241752529' at master log mysql_bin.040867, end_log_pos 15254660; Could not execute Write_rows event on table kk_control.control_site_venue_bet_statistics; Duplicate entry '2025-09-29-5-28-TY' for key 'control_site_venue_bet_statistics.unique_index', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log mysql_bin.040867, end_log_pos 15254660 LAST_ERROR_TIMESTAMP: 2025-10-04 08:07:20.962997 LAST_APPLIED_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241752516 LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.807107 LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.807107 LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:07:20.785319 LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 2025-10-04 08:07:20.787189 APPLYING_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241752529 APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.874823 APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.874823 APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:07:20.962589 LAST_APPLIED_TRANSACTION_RETRIES_COUNT: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_RETRIES_COUNT: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 *************************** 4. row *************************** CHANNEL_NAME: WORKER_ID: 4 THREAD_ID: NULL SERVICE_STATE: OFF LAST_ERROR_NUMBER: 0 LAST_ERROR_MESSAGE: LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241752456 LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.660213 LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.660213 LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:07:20.707483 LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 2025-10-04 08:07:20.708907 APPLYING_TRANSACTION: APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION_RETRIES_COUNT: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_RETRIES_COUNT: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 *************************** 5. row *************************** CHANNEL_NAME: WORKER_ID: 5 THREAD_ID: NULL SERVICE_STATE: OFF LAST_ERROR_NUMBER: 0 LAST_ERROR_MESSAGE: LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241752459 LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.664357 LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.664357 LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:07:20.708929 LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 2025-10-04 08:07:20.711737 APPLYING_TRANSACTION: APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION_RETRIES_COUNT: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_RETRIES_COUNT: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 *************************** 6. row *************************** CHANNEL_NAME: WORKER_ID: 6 THREAD_ID: NULL SERVICE_STATE: OFF LAST_ERROR_NUMBER: 0 LAST_ERROR_MESSAGE: LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241748791 LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:06:02.424222 LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:06:02.424222 LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:06:02.412803 LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 2025-10-04 08:06:02.413778 APPLYING_TRANSACTION: APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION_RETRIES_COUNT: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_RETRIES_COUNT: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 *************************** 7. row *************************** CHANNEL_NAME: WORKER_ID: 7 THREAD_ID: NULL SERVICE_STATE: OFF LAST_ERROR_NUMBER: 0 LAST_ERROR_MESSAGE: LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241748792 LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:06:02.424239 LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:06:02.424239 LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:06:02.412833 LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 2025-10-04 08:06:02.413784 APPLYING_TRANSACTION: APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION_RETRIES_COUNT: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_RETRIES_COUNT: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 *************************** 8. row *************************** CHANNEL_NAME: WORKER_ID: 8 THREAD_ID: NULL SERVICE_STATE: OFF LAST_ERROR_NUMBER: 0 LAST_ERROR_MESSAGE: LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241748686 LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:06:02.304209 LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:06:02.304209 LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:06:02.292898 LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 2025-10-04 08:06:02.293895 APPLYING_TRANSACTION: APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION_RETRIES_COUNT: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_RETRIES_COUNT: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 8 rows in set (0.00 sec) mysql>
最新发布
10-05
在MySQL复制架构中，错误1062表示插入重复键值，此次是Worker 3执行事务'5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241752529'时，在表`kk_control.control_site_venue_bet_statistics`的`unique_index`键上出现了...
mysql slave error_mysql slave error处理
weixin_35810223的博客
01-19 645
0.关键点:1.show slave status\G; 查看挂了的原因2.一般处理完后要tcp校验一下3.如果是宕机或者实例重启，在主库执行start slave前要在备库上看看有没有回滚进程ps aux | grep magiclog ，如果有 magiclog 进程在执行说明在回滚。回滚过程中不能执行start slave，不然会报各种slave err1.报错:文件中位点>文件大小G...
mysql1201_MySQL启动slave报错ERROR1201(HY000)
weixin_35076634的博客
02-02 417
MySQL 启动slave报错 ERROR 1201 (HY000) ,原来是有两个文件要删掉。估计是昨天其他人测试没有成功的时候生成的。配置了MySQL的复制，启动slave的时候报错如下：mysql> start slave;ERROR 1201 (HY000): Could not initialize master info structure; more error message...
mysql slave错误_Mysql slave 同步错误解决
weixin_30873333的博客
01-19 604
分析解决master 数据库提供服务，slave数据库作报表服务器，通过mysqlbin log做主从同步。从报表数据来看，缺少了从10/28到现在(11/18)之前的数据，比对master、slave数据库主要表数据，发现：10/28之后的slave库数据缺失，一致未同步。查看slave mysql同步状态：关注图中黄色字段：Slave_IO_Running: YesSlave_SQL_Runn...
mysql slave error处理
zhangjikuan的专栏
11-02 2895
备库挂了：slave io/sql thread error 0.关键点: 1.show slave status\G; 查看挂了的原因 2.一般处理完后要tcp校验一下 3.如果是宕机或者实例重启，在主库执行start slave前要在备库上看看有没有回滚进程ps aux | grep magiclog ，如果有 magiclog 进程在执行说明在回滚。回滚过程中不能执行star
mysql slave duplicate entry_slave 报Duplicate entry for key
weixin_36064512的博客
02-17 645
今天slave机器报如下错误[ERROR] Slave SQL: Error 'Duplicate entry '7301' for key 'PRIMARY'' on query. Default database: 'rt_roledb0301'. Query: 'insert into gm_proc_run_info (run_name, des, err_code) values ('p...
记一次 MySQL 数据库主从同步异常问题分析（Last_Errno: 1782）
wzy0623的专栏
02-21 632
Last_Errno: 1782 复制错误分析及处理
mysql slave duplicate entry_mysql主从库同步错误：1062 Error 'Duplicate entry '1438019'&nb...
weixin_29061509的博客
01-27 396
mysql主从库同步错误：1062 Error 'Duplicate entry '1438019' for key'PRIMARY'' on querymysql主从库在同步时会发生1062 Last_SQL_Error: Error ‘Duplicate entry‘的问题：显然这个问题是因为插入重复主键导致从库不工作了，错误消息如下mysql> show slave status\G;...
mysql 主从 duplicate entry,MySQL中主从复制重复键问题修复方法
weixin_31515619的博客
03-17 468
-------------------quote begin------------------------ 3. If you decide that you can skip the next statement from the master, issue the following statements: mysql> SET GLOBAL SQL_SLAVE_SKIP_COUNTE...
mysql 主从 duplicate entry_Mysql 主从备份 Duplicate entry for key PRIMARY
weixin_32493245的博客
02-03 953
昨天检查mysql数据库 master-slave同步 是否出问题，果然出乎意料。进入mysqlSHOW SLAVE STATUS\G;出现：Slave_SQL_Running: No原因是：[ERROR] Slave SQL: Error 'Duplicate entry '349' for key 'PRIMARY'' on query.[ERROR] Error running query...
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值