Replicate data from Db2 for i to Autonomous AI Lakehouse

Learn to replicate data from a Db2 for i system to Autonomous AI Lakehouse using OCI GoldenGate.

Before you begin

To successfully complete this quickstart, you must have:

• An existing on premises Db2 for i database, with users and privileges properly configured.

• An existing Autonomous AI Lakehouse instance in your Oracle Cloud tenancy, with the GGADMIN user unlocked

• Network connection from your on premises system to your Oracle Cloud tenancy using either FastConnect or VPN

• The appropriate VCN security rules to allow connection from your private subnet to your on premises Db2 for i through TCP/IP

Task 1: Create the OCI GoldenGate resources

First, create the deployments and connections:

1. Create the source Db2 for i deployment.

   Tip:

   • In the Create deployment panel, ensure you select Db2 for i for type.

   • It’s recommended to use OCI IAM for the credential store to prevent issues with log in and Distribution Paths.

2. Create the target Oracle AI Database deployment.

   Tip: In the Create deployment panel, ensure you select Oracle for type.

3. While the service creates the deployments, create the source and target connections:

   • Create the Db2 for i connection.

   • Create an Autonomous AI Database connection for the target Autonomous AI Lakehouse.

   • Create a GoldenGate server connection for the Oracle deployment.

   • Create another GoldenGate server connection for the Db2 for i deployment.

4. Assign each connection to their respective deployment.

   Tip:

   • Assign the Db2 for i connection to the Db2 for i deployment.

   • Assign the Autonomous AI Database connection to the Oracle deployment.

   • Assign the Oracle GoldenGate server connection to the Db2 for i deployment. (This lets the Db2 for i deployment connect to the Oracle deployment.)

   • Assign the Db2 for i GoldenGate server connection to the Oracle deployment. (This lets the Oracle deployment connect to the Db2 for i deployment.)

5. After the Db2 for i deployment is in an Active state, proceed to the next task.

Task 2: Set up the source deployment

Before you begin, ensure your source Db2 for i deployment is in an Active state.

1. On the source Db2 for i deployment details page, select Launch console.

2. Add and run anExtract.

   Note:

   Ensure that you:

   • Add transaction information (TRANDATA) to enable supplemental logging.

   • The Extract is running and capturing source changes before you move on to the next step.

Task 3: Set up the target deployment

1. From the target Oracle deployment details page, select Launch console.

2. Add and run a Target-Initiated Path:

   1. Select Receiver Service

   2. On the Receiver Service page, select Add Target-Initiated Path (plus icon).

   3. Complete the Add Path fields with the following values:

      1. On the Path Information page, enter a Path Name.

      2. On the Source Options page:

         1. For Source Protocol, select wss.

         2. For Source Host, select Copy next to the Console URL value on the source Db2 for i deployment details page, and then paste the value.

            Tip: Ensure that you remove the https:// and any trailing forward slashes (/) from the URL.

         3. For Port Number, enter 443.

         4. For Trail Name, enter the two-character name of the Extract created in Task 2.

         5. For Set Source Authentication Method, select OAuth.

         6. Select Next.

      3. On the Target Options page, enter the two-character name for the Target Trail, and then select Next.

      4. On the Managed Options page, select Create Path and Run.

3. Verify that the Target-Initiated Path is created and running.

Task 4: Replicate data

1. In the source Db2 for i deployment, select Distribution Service and verify theDistribution Path is running.

2. In the target Oracle deployment, add and run a Replicat.

3. After the Replicat is running, you can monitor performance.

4. Manage Trail files