Shulou(Shulou.com)06/01 Report--

Editor to share with you the solution to the 1146 error of the navicat newspaper, I believe that most people do not know much about it, so share this article for your reference, I hope you will learn a lot after reading this article, let's go to know it!

A 1146 error occurred during master-slave replication of MySQL. The error reason for the prompt is that the specified table cannot be found in the default data.

Show slave status\ G; actual synchronization status.

Slave_IO_Running: YESSlave_SQL_Running: NoLast_Errno: 1146Last_Error: Error 'Table' coop.Coop_Data' doesn't exist' on query. Default database: 'gcore'. Query: 'update coop.Coop_Data set State='2',NameLevel='2',CheckedTime=now (), Memo='' where DAID='18601''Skip_Counter: 0Last_SQL_Errno: 1146Last_SQL_Error: Error' Table 'coop.Coop_Data' doesn't exist' on query. Default database: 'gcore'. Query: 'update coop.Coop_Data set State='2',NameLevel='2',CheckedTime=now (), Memo='' where DAID='18601''

The reason is:

The use db_name1 is used first, and then the sql statement update db_name2.table set is executed.

Solution:

Set the slave server to ignore the error and add "slave-skip-errors = 1146" to the my.cnf file

If there are a small number of such errors, set "set global sql_slave_skip_counter=1" directly in mysql client.

The above is all the contents of this article "the solution to the error of navicat 1146". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

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.