Migrating a MySQL Instance to MySQL HeatWave Service

Use the Console and MySQL Shell to migrate a MySQL instance to MySQL HeatWave Service. The MySQL instance can be running on-premises, in other cloud vendors as managed or unmanaged services, or a MySQL HeatWave Service instance.

This task requires the following:
  • Permissions to access the Console, create an Object Storage bucket and upload objects into the bucket, create a DB system, and view or create a VCN configuration.
  • If you want to use replication in your data migration, you must comply with the requirements and limitations of inbound replication. See Limitations.
Do the following to migrate a MySQL instance to MySQL HeatWave Service:
Note

The optional steps allow you to migrate all new changes with replication. This reduces the switch over time to convert the DB system as the production database server.
  1. Create an Object Storage bucket to store the exported data. See Creating an Object Storage Bucket.
  2. (Optional) If you want to migrate all new changes with replication, configure the MySQL instance to be a source replication server. See Source Configuration and Creating a Replication User On a Source Server.
  3. Export the MySQL instance to an Object Storage bucket. See Exporting a MySQL Instance.
  4. Create a MySQL DB system, and import data from the Object Storage bucket to the DB system. You can import either using the data import feature or using MySQL Shell. It is recommended to import using the data import feature. See Importing Using the Data Import Feature and Importing Using MySQL Shell.
  5. (Optional) If you want to migrate all new changes with replication, set up an inbound replication from the MySQL instance (replication source) to the new MySQL DB system (replica). This updates the data in the DB system with all the changes in the MySQL instance after the initial export. See Creating a Replication Channel.