This content has been marked as final. Show 2 replies
From the installation guide:
Database requirements Database storage engine ● Oracle GoldenGate supports the InnoDB storage engine for a source MySQL database. ● To preserve transaction boundaries for a MySQL target, create or alter the target tables to the InnoDB transactional database engine instead of the MyISAM engine. MyISAM will cause Replicat records to be applied as they are received, which does not guarantee transaction integrity even with auto-commit turned off. You cannot roll back a transaction with MyISAM.
Put a trigger on them to always populate a table stored in InnoDB? Seriously, I think that is your only way. The problem is that not until InnoDB 5.1 was there even enough data in the MySQL redo logs to even properly replicate changes to a row of data.
MyISAM has a lot of good qualities and a lot of those have to do with performance but that is at the expense of those data not showing up in the redo logs and hence preclude them from being replicated.