MySQL Forums
Forum List  »  Replication

Replication trashing indexes ?
Posted by: Steve Tempest
Date: March 01, 2005 05:11AM

Hi all,

I'm running 4.1.10 and I've noticed that running the following command:

create table Transactions^M
(^M
TransactionNo integer not null
auto_increment,^M
Month integer default
null,^M
CardNo char(20) not null,^M
AccountNo BIGINT,^M
SiteCode integer,^M
TransTime DateTime,^M
TransValue Decimal(6,2),^M
PanInd char(1),^M
Flag char(1),^M
PayMethod char(1),^M
PointsAwarded integer,^M
InputFile varchar(25),^M
ReceiptNo char(10),^M
EFTTransNo integer,^M
CreationDate DateTime,^M
CreatedBy varchar(20),^M
UNIQUE KEY(Month,TransactionNo),^M
INDEX( CardNo )^M
) ENGINE=MERGE UNION=( Transactions200401,
Transactions200402, Transactions200403, Transactions200404,
Transactions200405, Transactions200406, Transactions200407,
Transactions200408, Transactions200409, Transactions200410,
Transactions200411, Transactions200412, Transactions200501,
Transactions200502, Transactions200503) INSERT_METHOD=NO;


Ignore the ^M's they have come out of the binary log.

On the replication server the index to some of the tables (but strangely not all) has been set to 1024 bytes.
I've run a repair table on them all and now they are fine.

Anyone else had similar problems or know what might be doing this ?

Options: ReplyQuote


Subject
Views
Written By
Posted
Replication trashing indexes ?
3031
March 01, 2005 05:11AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.