You can use an option in my.cnf slave-skip-error=<list> error nums separated by ,.
The error below means that the master had a shutdown event and the slave can't tell if it added / deleted / changed that row or not. I wouldn't advise in skipping this error less you want your data to be inconsistent or you can recover from the possible skipped slave event. -->-----Original Message----- -->From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] -->Sent: Monday, August 18, 2003 2:51 PM -->To: [EMAIL PROTECTED] -->Subject: Replication Problem --> --> -->I am having a problem with replication in MySQL 4.0.13. I have a -->my.cnf file in the data directory of the slave that should exclude a -->specific table in one of my databases from replication. I am getting -->the following error message: --> --> "error 'unexpected success or fatal error' on query 'UPDATE -->excludedDB.excludedTABLE.....' ". --> --> I am sure the syntax is correct in the my.cnf I am excluding several --> -->other tables and that seems to be working fine. The above query is -->for software that is in beta so it is not running all of the time. I -->can use SET GLOBAL SQL_SLAVE_SKIP_COUNTER to by-pass them for now but --> -->I need to find a permanent solution. Any help would be greatly -->appreciated. --> -->Thanks, --> -->-- -->Ed Pauley II -->Bloodstock Research Information Services -->Phone: (859) 223-4444 ext. 297 -->E-mail: [EMAIL PROTECTED] -->Web: http://www.brisnet.com --> --> --> -->-- -->MySQL General Mailing List -->For list archives: http://lists.mysql.com/mysql -->To unsubscribe: -->http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
