On-premise MySQL instance |
- Standalone DB system
- High availability DB system
- Standalone DB system with HeatWave cluster
- High availability DB system with HeatWave cluster
|
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 cluster
- High availability DB system with HeatWave cluster
|
Standalone DB system |
Supported |
- Standalone DB system
- High availability DB system
- Standalone DB system with HeatWave cluster
- High availability DB system with HeatWave cluster
|
High availability DB system |
Supported |
- Standalone DB system
- High availability DB system
|
Standalone DB system with HeatWave cluster |
Supported |
- Standalone DB system with HeatWave cluster
- High availability DB system with HeatWave cluster
|
Standalone DB system with HeatWave cluster |
Supported
- On target, HeatWave cluster load and unload operations are deferred until next HeatWave cluster recovery reload. During replication only intent is registered.
- Explicitly loading tables on target may cause load failure during HeatWave cluster recovery. If tables are independently loaded or unloaded at both sides, the HeatWave cluster data on source and target can get out-of-sync.
|
- Standalone DB system
- High availability DB system
|
High availability DB system with HeatWave cluster |
Supported |
- Standalone DB system with HeatWave cluster
- High availability DB system with HeatWave cluster
|
High availability DB system with HeatWave cluster |
Supported
- On target, HeatWave cluster load and unload operations are deferred until next HeatWave cluster recovery reload. During replication only intent is registered.
- Explicitly loading tables on target may cause load failure during HeatWave cluster recovery. If tables are independently loaded or unloaded at both sides, the HeatWave cluster data on source and target can get out-of-sync.
|