MySQL HeatWave: Channels with Delayed Replication and Generate Primary Keys

You now have more flexibility to configure channels in MySQL HeatWave for inbound replication, including hybrid deployments and migrations from on-premises or other cloud vendors to Oracle Cloud Infrastructure. Two new options exist when creating or updating an inbound replication channel: Generate Primary Keys and Replication Delay. The first option automatically generates invisible primary keys on the target tables, allowing continuous replication from a source that doesn't indicate a primary key on CREATE TABLE or ALTER TABLE statements. The second option intentionally adds a delay when applying replicated transactions on the target DB system so that the replica is continuously behind its source and can be used for recovery or reporting purposes. In the Console, find both options under the section Target DB system when you create or edit a Channel. For more information, see Creating a Replication Channel.