MySQL Bugs: #56268: IBMDB2I Engine-Updates from DB2 for i Update Master but Not Replicated to Slave

Bug #56268	IBMDB2I Engine-Updates from DB2 for i Update Master but Not Replicated to Slave
Submitted:	25 Aug 2010 19:09	Modified:	3 Apr 2011 12:33
Reporter:	Jack Collins	Email Updates:
Status:	Unsupported	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S1 (Critical)
Version:	5.1.43	OS:	IBM i
Assigned to:		CPU Architecture:	Any
Tags:	ibmdb2i, replication

Description:
If you make changes (INSERT or UPDATE) to a mysql table using DB2 for i tools such as STRSQL, JDBC or System i Navigator the mysql table will be changed as expected. However, if the mysql server is serving as a master those changes will not be replicated to the slaves.

Changes made directly to the mysql table using the mysql monitor are replicated properly from master to slave.

 

How to repeat:
1. Create a table using IBMDB2I engine with mysql monitor or any other mysql tool. 
2. Setup MASTER-SLAVE replication to another server that includes the table created in the previous step. 
3. Using mysql monitor, add a record to the table you created. If replication is setup properly the new record will appear on the slave. 
4. Use IBM i5 STRSQL or other tool to insert an additional record. This change will appear on the Master but not on any of the Slaves.

Thank you for the report.

Have you committed records inserted in step 5? Please connect using other client on master and check if you see new rows.

Thank you Sveta. Yes, I have verfied that the rows are committed.

Has anyone else seen this behavior with IBMDB2I & replication? It just looks like updates from the DB2 side are made locally but the replication event is not sent to the slaves. Just a missed step? Replication works fine when using mysql tools to update the IBMDB2I tables.

Changed severity since there is no workaround.

Sorry, but IBMDB2I storage engine (and MySQL on System i in general) is no longer supported officially.