From: Gleb Paharenko (gleb.paharenkoensita.net)
Date: Mon Jul 04 2005 - 10:32:29 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hello.

> | 4.0.17-standard |

It is an old version of MySQL which could contain lots of bugs. It is
strongly recommended to upgrade to the latest release 4.1.12, or if it
is impossible in your production environment to 4.0.24. Usually upgrade
solves such kind of errors. Please, next time send your messages to the
list, because the probability to obtain more help grows a lot.

>1.
>Send an output of the following statement executed both on master and
>slave:
> select version();
>
> from master :-
> ============
> mysql> select version();
> +---------------------+
> | version() |
> +---------------------+
> | 4.0.17-standard-log |
> +---------------------+
> 1 row in set (0.02 sec)
>
> mysql>
>
> from slave :-
> ===========
> mysql> select version();
> +-----------------+
> | version() |
> +-----------------+
> | 4.0.17-standard |
> +-----------------+
> 1 row in set (0.00 sec)
>
> mysql>
>
> 3.
>
> The queries are same in bin log and relay logs.
>
> 4.
> You should find where the error occurred, fix it, possibly by
> executing
> SQL query on the slave. Than 'CHANGE MASTER' to corresponding position
> in the master binary log and start slave.
> ---This may not be possible to do every time on and on every m/c.
> Can you tell any way to avoid this problem.
>
>>> Thanks,anurag.dashputrewipro.com wrote:

--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __ ___ ___ ____ __
  / |/ /_ __/ __/ __ \/ / Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__ Gleb.Paharenkoensita.net
/_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET
       <___/ www.mysql.com

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]