From: divesh kamra
Date: December 5 2012 7:04am
Subject: Re: MySQL Replication Error
List-Archive: http://lists.mysql.com/mysql/228769
Message-Id: <CAHPcvmzg4VUGiK2RONTk+1=S6=2g1vwCq270YoaFAqv3WHB_=Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=f46d040838657eabfa04d015964c

--f46d040838657eabfa04d015964c
Content-Type: text/plain; charset=ISO-8859-1

Hi

first check this thought application end

or

There is another way

slave-skip-errors=1062 -----------> in my.cnf and restart mysql


On Sat, Dec 1, 2012 at 4:30 AM, Reindl Harald <h.reindl@stripped>wrote:

>
>
> Am 30.11.2012 23:52, schrieb Rick James:
> > Possible causes:
> > * Someone is writing to the Slave
>
> that is why the option "read-only" exists for my.cnf
>
> > * The Slave was not in synch with the Master.
> > * Schemas are different between Master and Slave
>
> should not happen if the slave is properly cloned
> as a binary copy of the stopped master and secured
> with "read-only"
>
>
>
>
>
>
>

--f46d040838657eabfa04d015964c--