Migrating a MySQL Instance to HeatWave Service
When deploying a new HeatWave DB system, customers may want to migrate existing data in a MySQL instance to the HeatWave DB system. The MySQL instance can be running on-premises, in other cloud vendors as managed or unmanaged services, or a HeatWave Service instance.
You can employ one of the following methods to migrate your data from a MySQL instance to a HeatWave DB system:
Use the Database Migration Service
You can use the Oracle Cloud Infrastructure (OCI) Database Migration Service to migrate a MySQL instance to HeatWave Service.
Database Migration Service supports both offline and online migrations. Offline migration only loads a snapshot of the data from the source database to the target database. During offline migration, your application needs to be offline too in order to migrate the application to use the target database without transaction loss. Online migration enables the replication of all data and metadata transactions from the source to the target database, committed after the initial load.
Do the following to migrate a MySQL instance to HeatWave Service:
- Prepare the MySQL source database for online migration. See Preparing MySQL Databases for Migration.
- Create MySQL connection objects to the source and target databases. See Creating MySQL connections.
- Create a MySQL migration object. See Creating MySQL migrations.
- Validate and run the migration job. See Managing Migration Jobs.
Related Topics
Manually Export and Import the Data
You can perform the export and import steps to migrate the data from a MySQL instance to a HeatWave DB system by using the Console and MySQL Shell.
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 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.
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.
- Create an Object Storage bucket to store the exported data. See Creating an Object Storage Bucket.
- (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.
- Export the MySQL instance to an Object Storage bucket. See Exporting a MySQL Instance.
- 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.
- (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.