Hybrid Data Pipeline requires a system database for storing user and configuration information. System database migration is the process of migrating the data from the standing system database to a new system database, and then integrating the new system database into the standing deployment of Hybrid Data Pipeline. Database migration is supported for the following use cases.

  • If you deployed Hybrid Data Pipeline using the internal system database, you can migrate the data from this database to one of the following database systems: Microsoft Azure, Microsoft SQL Server, or PostgreSQL. You can then use the new database as an external system database for your standalone Hybrid Data Pipeline deployment.
  • If you deployed Hybrid Data Pipeline with an Oracle external system database, you can migrate data from the Oracle database to a PostgreSQL database. The PostgreSQL database can then be used as the external system database for your Hybrid Data Pipeline deployment.

For a successful migration, a new database must be set up, a provisional installation of the service must be performed, the data from the standing database must be transferred to the new database, and the standing deployment of the service must then be upgraded to use the new external database. The following general steps apply.

  1. Block all traffic coming into the service. The service itself must remain running during the migration process. By blocking traffic to the service, you ensure that no changes to the system database are made while migration is underway. Any such changes would be lost during migration.
  2. Copy, save, and secure the files in the key location specified during the initial installation or previous upgrade of the service. These files must be accessible to the product installation program for a provisional installation of the service.
  3. Set up the database that will be used to store Hybrid Data Pipeline user and configuration information. This database must meet the requirements described in System database requirements.
  4. Perform a provisional installation of the service. During the provisional installation of the service, the installation program writes the system database schema to this database. The product version must be the same as that used in the standing deployment of the service. The key location specified must point to the files you copied and saved in Step 2.
  5. Run the system database migration tool to move the data from the standing system database to the new system database. The migration of data can be performed as a single process by running the tool in EXPORT_IMPORT mode. Alternatively, data migration can be performed as a two step process: by first running the tool in EXPORT mode and then running the tool in IMPORT mode.
    Note: The individual running the migration tool must have the necessary account information, permissions, and access privileges for both the source and destination databases.
  6. Perform an upgrade on the standing deployment of the service to integrate the new system database. The product version must be the same as that used in the installation or subsequent upgrade of the service. You must specify the values of the system database created for the provisional installation of the service in Step 4.
  7. Uninstall or archive your provisional installation of the service.
  8. Unblock traffic coming into the standing deployment of the service.

The following topics provide detailed guidance and instruction for migrating the system database.