You will be taking a chance if you use Read_Master_Log_Pos: 106683511. It is not guaranteed that whatever is read from master is definitely applied. The apply of the read sqls might have stopped somewhere and in that case Read_Master_Log_Pos and exec_master_log_pos might be different.
-- Thanks Alex http://blog.360.yahoo.com/alex.lurthu On 7/9/07, Ananda Kumar <[EMAIL PROTECTED]> wrote:
Hi Alex, Thanks a lot, I missed on taking the "exe_master_log position" value. If i start from Read_Master_Log_Pos: 106683511, will it cause any harm. regards anandkl On 7/9/07, Alex Arul Lurthu <[EMAIL PROTECTED]> wrote: > > Anand, > > If the dump was taken from the slave then the binlog positions that were > dumped out are that of the slave. Now you might do 2 things : > > 1. Setup a slave of your master > > To do this use the binlog positions that you obtained using the > command show slave status on your slave. The master log file will be " > mysql-bin.000029" . But your show slave output status doesnt show the > exe_master_log position. You need to use that position for setting up a new > slave of your master. > > 2. Setup a slave of your slave > > To do this use the binglog positions in your mysqldump output. > > P.S: Make sure you setup the hostnames in the change master command > appropriately. > > > -- > Thanks > Alex > http://blog.360.yahoo.com/alex.lurthu > > >
