2 Prepare to Migrate Data Integration Platform Cloud GoldenGate Configuration to Oracle Cloud Marketplace

To ensure that the migration succeeds and to minimize manual steps, make sure that the following prerequisites are met, in addition to the regular GoldenGate migration.

In this document, the Data Integration Platform Cloud GoldenGate environment will be referred as old environment. Also, the GoldenGate environment on Oracle Cloud Infrastructure Marketplace will be referred to as the new environment.

• In the new environment, the GoldenGate instance will be able to connect to the source/target Database with the same GoldenGate credential alias in old environment. This might involve some network configuration/access rule adjustment, if the remote agent of old environment were running outside of Oracle Cloud Infrastructure, for example, on-premise. Certain network access or NAT rule must be revised to allow the GoldenGate running in the new environment to connect directly into the Database on premise. If this can’t be done, then GoldenGate Oracle Cloud Infrastructure Marketplace can’t be used to replace your Data Integration Platform Cloud instance.
• In the new environment, the last GoldenGate trail file that was written or read will present in the same trail file location to retain the proper trail release format.
• If any customized configuration or component has been added to your Data Integration Platform Cloud remote agent in the old environment, all these must be moved over to the new environment manually by the users, and are not covered in this guide.

  For example,

  • Customized GoldenGate processes created manually

  • Additional GoldenGate components installed and configure manually, such as OEM Plugin, Veridata etc.

  • Any customized scripts that monitor and manage GoldenGate processes