I'm running replication between two MySQL servers. This has been working
fine for a while; howver, as of yesterday replication keeps failing because
of a lock wait timeout exceeded on one of my tables.
I thought I could use the mysqlbinlog utility to figure out what queries
were being executed bef
Hi,
I've set up a master-slave MySQL configuration. When I do: LOAD DATA
FROM MASTER on the slave I get the following error: ERROR 1189: Net
error reading from master . Errorlog displays: create_table_from_dump:
failed in handler::net_read_dump() The master logs displays nothing. A
few databas
Dear Sir/Madam,
I have tried the config below, and I successfully see the replicated record in
client side but only ONCE.
After I have seen the replication works. I continued with my normal
transactional work including altering table structure.
But later when I checked the replication status. Wel
> Lutz,
>
> - Original Message -
> From: "Lutz Maibach" <[EMAIL PROTECTED]>
> To: "Heikki Tuuri" <[EMAIL PROTECTED]>
> Sent: Tuesday, August 13, 2002 5:09 PM
> Subject: Re: Rename Table in Replication failed / command missing in slave
&
Hi!
The following might fix Pete's RENAME TABLE bug:
...
August 12, 2002:
If you ran in the AUTOCOMMIT mode, executed a SELECT, and immediately after
that a RENAME TABLE, then RENAME would fail and MySQL would complain about
error 1192 'Can't execute the given command because you have active lock
If you're using InnoDB tables, replication stops the slaves from
running. Heikki said he'd try to get this fixed for 3.23.52.
--Pete
On Mon, Aug 12, 2002 at 04:05:11PM +0200, Lutz Maibach wrote:
> Hi,
>
> today I noticed a strange behaviour in MySQL 3.23.49a-Replication I can't explain.
> A
Hi,
today I noticed a strange behaviour in MySQL 3.23.49a-Replication I can't explain.
A perl-script which controls whether master- and replication-tables are equal showed
me, that a master-table was missing on both slaves (two backups are better than one
:-) )
When I controlled the master upda
Anti-SPAM: mysql, query
Gurus
I'm new to replication. Set it up this weekend and has worked
flawlessly for several days. Then I used the command:
TRUNCATE TABLE tbl;
That worked in master, but was not replicated in slave.
No mention of this in manual. Using version 3.23.49 on
master and slav
