Oracle Cloud Infrastructure Documentation

Supported Inbound Replication Scenarios

MySQL HeatWave Service supports various inbound replications scenarios. In all scenarios, the DB system must be the same version as, or a higher version of MySQL than, the source. The minimum supported version of MySQL for a replication source is 5.7.9.

Table 13-4 Supported Inbound Replication Scenarios

Source Target Details
On-premise MySQL instance
  • Standalone DB system
  • High availability DB system
  • Standalone DB system with HeatWave
  • High availability DB system with HeatWave
 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.
MySQL installed on a compute instance
  • Standalone DB system
  • High availability DB system
 Supported
  • Standalone DB system
  • High availability DB system
  • Standalone DB system with HeatWave
  • High availability DB system with HeatWave
 Standalone DB system Supported
  • Standalone DB system
  • High availability DB system
  • Standalone DB system with HeatWave
  • High availability DB system with HeatWave
 High availability DB system Supported
  • Standalone DB system
  • High availability DB system
 Standalone DB system with HeatWave Supported
  • Standalone DB system with HeatWave
  • High availability DB system with HeatWave
 Standalone 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.
  • Standalone DB system
  • High availability DB system
 High availability DB system with HeatWave Supported
  • Standalone DB system with HeatWave
  • High availability 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.