Getting started

Creating a migration from an Oracle or Postgres database to EDB Postgres AI involves several steps.

Prerequisite: Ensure you have Java 17 or later installed.

1. Create a destination Postgres database cluster: Ensure you have created and configured a destination database. This can be a database in an HCP-managed cluster, or in a self-managed Postgres instance.

2. Prepare the source database schema: In your source machine, prepare the source database by exporting it and excluding unsupported constraints. Then, import the adapted schema to the target database.

3. Install the EDB DMS Reader: In your source machine, install the EDB DMS Reader from the EDB repository.

4. Optional - Install the EDB DMS Writer: Perform this step only if you want to migrate data to a destination database outside of the Hybrid Control Plane. In your destination machine, install the EDB DMS Writer from the EDB repository.

5. Prepare your Oracle or Postgres database: In your source/destination machine, prepare the database by altering settings and creating users that are required for the migration. Ensure your database can accept SSL connections.

6. Configure the EDB DMS Reader: In the Hybrid Control Plane portal, download dedicated migration credentials. In your source machine, configure the EDB DMS Reader by exporting environment variables that allow the Reader to connect to the source. Execute the Reader.

7. Optional - Configure the EDB DMS Writer: Perform this step only if you want to migrate data to a destination database outside of the Hybrid Control Plane. In your destination machine, configure the EDB DMS Writer by exporting environment variables that allow the Writer to connect to the destination. Execute the Writer.

8. Create a new migration: In the EDB Postgres AI Console, create a new migration by selecting the source generated by the Reader in the Console, and selecting the target database you created for this purpose.

9. Mark the Migration as completed: In the EDB Postgres AI Console, mark the migration as completed to stop the streaming process.

10. Reapply any excluded constraints: Apply the constraints you excluded from the schema migration in the new database.

11. Verify the migration completed successfully: Use LiveCompare to ensure the target database has the same data as the source database.