Hello.
> so I have 3 questions > > how did this duplicate key happen, there was no error in my application > logs on the master as I would expect? Research and compare master binary logs and slave relay logs to find what statement on the master produced the error. 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/Binary_log.html Do you have the difference in table definitions on the master and slave (different engines for example)? Do you have fresh MySQL versions? > did i do wrong by restarting the slave? After restart the error could occur again. > > is is possible to remidy the situation without re-coyping the data > files? Very often it is simpler to setup replication again after removing the causes of errors. > tony <[EMAIL PROTECTED]> wrote: > Hi > I set up replication for the first time last week. 1 master 1 slave. > > Everything worked fine for 1 week, i checked out a couple of records > this morning to check everything was still working and the slave had > stopped. show slave status showed that there had been a duplicate key > error, the record that was the duplicate did indeed exist and so did > many after it. > > I did slave stop and slave start, then show slave status now indicateds > that it is moving further through the master log but records i update > are not getting into the slave, and it is now about a full day behind. > > so I have 3 questions > > how did this duplicate key happen, there was no error in my application > logs on the master as I would expect? > > did i do wrong by restarting the slave? > > is is possible to remidy the situation without re-coyping the data > files? > > thanks in advance, current status below (the slave is incrementing but > always a little behind the master as there is a lot of queries going on) > > show master status; > +------------------+------------+--------------+------------------+ > | File | Position | Binlog_Do_DB | Binlog_Ignore_DB | > +------------------+------------+--------------+------------------+ > | mysql-bin.000004 | 1033832609 | | | > +------------------+------------+--------------+-------------- > > > slow slave status \G > *************************** 1. row *************************** > Slave_IO_State: Waiting for master to send event > Master_Host: 192.168.10.5 > Master_User: repl > Master_Port: 3306 > Connect_Retry: 60 > Master_Log_File: mysql-bin.000004 > Read_Master_Log_Pos: 1035462332 > Relay_Log_File: clank-relay-bin.000003 > Relay_Log_Pos: 1024944283 > Relay_Master_Log_File: mysql-bin.000003 > Slave_IO_Running: Yes > Slave_SQL_Running: No > Replicate_Do_DB: > Replicate_Ignore_DB: > Replicate_Do_Table: > Replicate_Ignore_Table: > Replicate_Wild_Do_Table: > Replicate_Wild_Ignore_Table: > Last_Errno: 1062 > Last_Error: Error 'Duplicate entry '1787' for key 1' on > query. Default database: ''. Query: 'INSERT INTO > > dbseContentManagement.tblDailySpecial > ( intProductUid > ,fltPrice1Thx > ,fltPrice2Thx > ,fltPrice3Thx > ,fltPrice4Thx > ,fltPrice1Xyz > ,fltPrice2Xyz > ,fltPrice3Xyz > ,fltPrice4Xyz > ,boolIsEmailProduct > ,boolIsFixedSpecials > ,boolIsFixedHomepage > ,strDate > ) > VALUES > > (1081,0.500000,0.450000,0.400000,0.350000,0.600000,0.600000,0.600000,0.600000,0,0,0,'20050823')' > Skip_Counter: 0 > Exec_Master_Log_Pos: 1024944197 > Relay_Log_Space: 2109204794 > Until_Condition: None > Until_Log_File: > Until_Log_Pos: 0 > Master_SSL_Allowed: No > Master_SSL_CA_File: > Master_SSL_CA_Path: > Master_SSL_Cert: > Master_SSL_Cipher: > Master_SSL_Key: > Seconds_Behind_Master: NULL > > > -- 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]
