Hello.
Could you examine slave relay log and master binary log to find which statement causes duplicated entry with mysqlbinlog utility. Which versions of MySQL do you use on your master and slave? See: http://dev.mysql.com/doc/mysql/en/mysqlbinlog.html http://dev.mysql.com/doc/mysql/en/slave-logs.html http://dev.mysql.com/doc/mysql/en/show-slave-status.html "MaFai" <[EMAIL PROTECTED]> wrote: > Dear mysql@lists.mysql.com: > > Our db is the innodb eng. > We have no hot backup tools to dump the data. > > If lock the table by the following cmd before we dump the data > FLUSH TABLES WITH READ LOCK; > > It seems ok,it can lock the innodb too. > But the replication would be crushed ,even it start up smoothly,due to the > duplicated entry. > > Do any one try to lock innodb tables to make the snap shot? > Since shutdown the master db would take great effect,we don't hope so. > > Best regards. > > MaFai > [EMAIL PROTECTED] > 2005-07-06 > 34955929 > > > > > > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
