Oracle Cloud Infrastructure Documentation

Supported Outbound Replication Scenarios

MySQL HeatWave Service supports various outbound replications scenarios. In all scenarios, the replica must be the same version as, or a higher version of MySQL than, the DB system source.

Table 14-1 Supported Outbound Replication Scenarios

Source Target Details
  • Standalone DB system
  • High availability DB system
  • Standalone DB system with HeatWave1
  • High availability DB system with HeatWave2
 On-premise MySQL instance Supported - This replication scenario requires an additional network configuration to bridge the local network and the VCN to which the DB system is attached. You can use VPN Connect, FastConnect, or OpenVPN Access Server.
Note

Replication fails if a Lakehouse external table is created in the DB system with HeatWave Lakehouse enabled.
  • Standalone DB system
  • High availability DB system
  • Standalone DB system with HeatWave1
  • High availability DB system with HeatWave2
 MySQL installed on a compute instance Supported
Note

Replication fails if a Lakehouse external table is created in the DB system with HeatWave Lakehouse enabled.
Standalone DB system
  • Standalone DB system
  • High availability DB system
 Supported
High availability DB system
  • Standalone DB system
  • High availability DB system
 Supported
Standalone DB system with HeatWave1
  • Standalone DB system
  • High availability DB system
 Supported
High availability DB system with HeatWave2
  • Standalone DB system
  • High availability DB system
 Supported
Standalone DB system with HeatWave1
  • Standalone DB system with HeatWave
  • High availability DB system with HeatWave
 Supported
  • On target, HeatWave load and unload operations are deferred until next HeatWave recovery reload. During replication only intent is registered.
  • Explicitly loading tables on target may cause load failure during HeatWave recovery. If tables are independently loaded or unloaded at both sides, the HeatWave data on source and target can get out-of-sync.
High availability DB system with HeatWave2
  • Standalone DB system with HeatWave
  • High availability DB system with HeatWave
 Supported
  • On target, HeatWave load and unload operations are deferred until next HeatWave recovery reload. During replication only intent is registered.
  • Explicitly loading tables on target may cause load failure during HeatWave recovery. If tables are independently loaded or unloaded at both sides, the HeatWave data on source and target can get out-of-sync.

1 Prior to MySQL 8.3.0-u2, you cannot perform outbound replication from a DB system with HeatWave Lakehouse enabled.

2 Prior to MySQL 8.3.0-u2, you cannot enable Lakehouse on a high availability DB system with HeatWave.