Re: binlog not containing all the queries.
- Replication Format you are using ?
**we are usind Deafult Statement base , And wt happen if i start to use row based replication format is it create any issue if i moved to rowbase suddenly ?
- Trigger code also replicated to slave ?
**Yes we created trigger on master so its there on slave too.
- I think you destination table also contains auto-increment column and you also inserting auto-increment column from source to destination through trigger.
**No, we are using "insert into <table> set column = <value>" excluding primary key value
- Please provide show create table to trace the exact problem.
**show create table Prepaid_SubscriberCardBalanceTxnInfo
CREATE TABLE `Prepaid_SubscriberCardBalanceTxnInfo` (
`SubscriberCardBalanceTxnInfoID` bigint(8) unsigned NOT NULL AUTO_INCREMENT,
`TxnInfoTime` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
`TrInfoType` tinyint(1) unsigned NOT NULL,
`CrDR` varchar(5) NOT NULL,
`SubscriberCardID` bigint(8) unsigned NOT NULL,
`SubscriberCardValidityID` bigint(8) unsigned NOT NULL,
`OpeningBalance` decimal(15,6) NOT NULL,
`Amount` decimal(15,6) NOT NULL,
`ClosingBalance` decimal(15,6) NOT NULL,
`TrInfoDesc` varchar(50) NOT NULL,
PRIMARY KEY (`SubscriberCardBalanceTxnInfoID`),
KEY `TxnInfoTime` (`TxnInfoTime`),
KEY `TrInfoType` (`TrInfoType`),
KEY `SubscriberCardID` (`SubscriberCardID`),
KEY `SubscriberCardValidityID` (`SubscriberCardValidityID`),
CONSTRAINT `Prepaid_SubscriberCardBalanceTxnInfo_ibfk_1` FOREIGN KEY (`SubscriberCardID`) REFERENCES `Prepaid_SubscriberCard` (`SubscriberCardID`) ON DELETE CASCADE ON UPDATE CASCADE,
CONSTRAINT `Prepaid_SubscriberCardBalanceTxnInfo_ibfk_2` FOREIGN KEY (`SubscriberCardValidityID`) REFERENCES `Prepaid_SubscriberCardValidity` (`SubscriberCardValidityID`) ON DELETE CASCADE ON UPDATE CASCADE
) ENGINE=InnoDB AUTO_INCREMENT=340521 DEFAULT CHARSET=latin1 ROW_FORMAT=COMPACT