I believe some versions of 4.0 have problem with auto dropping
temporary tables in replication. The easy fix is to drop temporary
tables when you are finished with them instead of relying on mysql to
do it for you.
On Wed, 1 Sep 2004 08:16:43 -0600, Alfredo Cole <alfredo@stripped> wrote:
> I'm using MySQL 4.0, and have setup replication with one server and one slave,
> both running LM 9.1. My application creates a temporary table on the master,
> which is supposed to be deleted when the connection is closed. When that
> happens, replication stops with the following message:
> ERROR: 1051 Unknown table 'tmpclisal'
> 040831 20:16:38 Slave: error 'Unknown table 'tmpclisal'' on query
> 'DROP /*!40005 TEMPORARY */ TABLE truepos.tmpclisal', error_code=1051
> 040831 20:16:38 Error running query, slave SQL thread aborted. Fix the
> problem, and restart the slave SQL thread with "SLAVE START". We stopped at
> log 'central-bin.001' position 12475966
> Is there a problem in using temporary tables and replication? I have not found
> any clues in the manual. If there is a problem, perhaps someone can point to
> a url where I can find a solution?
> Thank you.
> Alfredo J. Cole
> Grupo ACyC
> www.acyc.com - www.clshonduras.com - SolCom
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=1