List:General Discussion« Previous MessageNext Message »
From:Joshua Gordon Date:June 3 2009 4:10am
Subject:binlog questions
View as plain text  
We outputted the bin log using the following command:

mysqlbinlog -v --base64-output=DECODE-ROWS oo-mysql1-bin.000087

We then looked in this file and found some odd things.  For example
there is the below insert statement:

### INSERT INTO panel.history
### SET
###   @1=-182667600 (4112299696)
###   @7=NULL


The table structure for history is:

CREATE TABLE `history` (
  `historyid` int(11) NOT NULL AUTO_INCREMENT,
  `panelid` int(11) DEFAULT NULL,
  `projectid` int(11) DEFAULT NULL,
  `resultid` int(11) DEFAULT NULL,
  `pulldate` datetime DEFAULT NULL,
  `resultdate` datetime DEFAULT NULL,
  `senddate` datetime DEFAULT NULL,
  `sendcount` int(11) DEFAULT NULL,
  `bouncecount` int(11) DEFAULT NULL,
  `link` char(128) DEFAULT NULL,
  `projectgroupcode` int(11) DEFAULT NULL,
  `vendorid` int(10) unsigned DEFAULT NULL,
  `ipaddress` char(15) DEFAULT NULL,
  `enddate` datetime DEFAULT NULL,
  `bloodhoundid` int(10) unsigned DEFAULT NULL,
  `incentive` int(4) unsigned DEFAULT NULL,
  PRIMARY KEY (`historyid`),
  KEY `RESULTDATE` (`resultdate`),
  KEY `PULLDATE` (`pulldate`),
  KEY `PANELID_PROJECTID` (`panelid`,`projectid`),
  KEY `PROJECTGROUPCODE` (`projectgroupcode`),
  KEY `projectid_vendorid` (`projectid`,`vendorid`),
  KEY `PROJECTIDb` (`projectid`) USING BTREE,
  KEY `bloodhoundid` (`bloodhoundid`)
) ENGINE=ndbcluster DEFAULT CHARSET=latin1


So it is trying to put a negative value in for the first column?

Then you have stuff like:

### INSERT INTO panel.history
### SET
###   @1=1169499418
###   @7=348123-41-35 05:64:02

That looks valid but there is no row in the history table with that
historyid so why isn't it there?  all in all it seems very inconsistent
with the columns it uses and what shows up etc..  any insight would be
appreacited thank you.
Thread
Replication problems: slave fails to updateProemial2 Jun
  • binlog questionsJoshua Gordon3 Jun