-------------------------------------------------
030605 3:27:19 Slave: did not get the expected error running query from master - expected: 'Got error %d from table handler'
(1030), got 'no error' (0)
030605 3:27:19 Slave: error running query 'delete from page_cache_2003_06_04 where FILEKEY = '0''
030605 3:27:19 Error running query, slave aborted. Fix the problem, and re-start the slave thread with "mysqladmin start-slave". We stopped at log 'ebldb05p2-bin.630' position 354859069
030605 3:27:19 Slave thread exiting, replication stopped in log 'ebldb05p2-bin.630' at position 354859069
-------------------------------------------------
030610 3:17:02 Slave: did not get the expected error running query from master - expected: 'Got error %d from table handler'
(1030), got 'no error' (0)
030610 3:17:02 Slave: error running query 'delete from page_cache_2003_06_09 where FILEKEY = '0''
030610 3:17:02 Error running query, slave aborted. Fix the problem, and re-start the slave thread with "mysqladmin start-slave". We stopped at log 'ebldb05p2-bin.654' position 189278930
030610 3:17:02 Slave thread exiting, replication stopped in log 'ebldb05p2-bin.654' at position 189278930
-------------------------------------------------
I can successfully run the SQL on the slave manually and it obviously has run successfully on the master. The only thing which I could think of being a possible cause of problem is that the query takes almost 16min to run. Is there some parameter which says the slave should abort a query if it takes more than a certain amount of time ?
Also what does it mean when the slave gives the following error
error 'unexpected success or fatal error' on query 'delete from page_cache_2003_06_10 where FILEKEY = '0''
Mithun
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
