This quickstart example demonstrates how to set up and run a replication between HeatWave on OCI and Autonomous Data Warehouse using OCI GoldenGate.

To successfully complete this quicktart, you must have the following:

• OCI Bastion, to connect to HeatWave on OCI, load the sample database, and perform inserts
• A HeatWave on OCI database to serve as the source database
• An Autonomous Data Warehouse instance to serve as the target database

1. Download the sample data script, and then run the script on the HeatWave on OCI database to create the database and load the data.
2. Create a ggadmin user using the following script. Remember to replace <ggadmin-password> with a valid password:

   CREATE USER 'ggadmin' IDENTIFIED BY '<ggadmin-password>';
   GRANT SELECT, REPLICATION SLAVE, REPLICATION CLIENT, CREATE,CREATE VIEW, EVENT, INSERT, UPDATE, DROP,EXECUTE, DELETE ON *.* TO 'ggadmin';

3. Open port 3306, through which OCI GoldenGate can connect.
   1. In the Oracle Cloud console, locate the subnet that the HeatWave on OCI database uses.
   2. In the security list of the subnet, create an Ingress rule for port TCP/3306.
4. Download the target schema scripts, and then run the scripts in the Autonomous Data Warehouse instance to create the schema and tables. You can use the Autonomous Data Warehouse Database Actions SQL tool to run the scripts:
   1. In the Oracle Cloud console, open the Autonomous Data Warehouse database details page, and then click Database Actions.
   2. In Database Actions, under Development, click SQL.
   3. In the SQL tool, copy and paste the script from OCIGGLL_OCIGGS_SETUP_USERS_ADW.sql into the SQL worksheet, and then click Run Script. If successful, the Script Output tab displays confirmation messages.
   4. Clear the SQL worksheet, and then copy and paste only the Create Table scripts from OCIGGLL_OCIGGS_SRC_MIRROR_USER_SEED_DATA.sql. The data will be loaded in a later task.

      Tip:

      You may need to run each Create Table statement separately for the SQL tool to execute the scripts successfully.
   5. To verify the tables were created successfully, close the SQL window and reopen it again. In the Navigator tab, look for the SRC_OCIGGLL schema, and then select the tables from their respective dropdowns.

1. Create a deployment for the source HeatWave on OCI database.
2. Create a deployment for the target Autonomous Data Warehouse.
3. Create a connection to the source HeatWave on OCI database.
4. Create connection for the target Autonomous Data Warehouse.
5. Create a connection to GoldenGate, and then assign this connection to the source MySQL deployment.
6. Assign the source connection to the source MySQL deployment.
7. Assign the target connection to the target Oracle deployment.

1. On the Deployments page, select the MySQL deployment created in Task 1.
2. On the deployment details page, click Launch Console.
3. Sign in to the source MySQL deployment console using the Administrator credentials specified when you created the deployment in Task 1.
4. In the navigation menu, select DB Connections.
5. Review the credentials for the HeatWave on OCI connection. Take note of the Domain and Alias.
6. Add and run an Change Data Capture Extract with the follow values:
   • For Extract Type, select Change Data Capture.
   • For Process Name, enter a name for the Extract process.
   • For Domain, select the domain.
   • For Alias, select the alias.
   • For Extract Trail Name, enter a name for the Trail file.
   • On the Parameter File page, add the following:

     TABLE SRC_OCIGGLL.*;

7. Add and run an Initial Load Extract with the follow values:
   • For Extract Type, select Initial Load Extract.
   • For Process Name, enter a name.
   • On the Parameter File page, add the following:

     TABLE SRC_OCIGGLL.*;

1. On the Deployments page, select the target Autonomous Database deployment.
2. On the deployment details page, click Launch Console, and then log in as the admin user.
3. If using IAM credential store, proceed to the Create a Distribution Path step. If using GoldenGate credential store, create a user with which the source GoldenGate uses to connect to the target GoldenGate.
   1. In the navigation menu, click User Administration.
   2. Click Add New User (plus icon), complete the fields as follows, and then click Submit:
      • For Username, enter ggsnet.
      • For Role, select Operator.
      • Enter the password twice for verification.
4. In the source PostgreSQL deployment console, create a Path Connection for the user created in the previous step.
   1. In the navigaton menu, click Path Connections.
   2. Click Add Path Connection (plus icon), complete the fields as follows, and then click Submit:
      • For Credential Alias, enter dpuser.
      • For User ID, enter ggsnet
      • For Password, enter the same password used in the previous step.
5. Create a Distribution Path.
   1. In the service menu bar, click Distribution Service, and then click Add Distribution Path (plus icon).
   2. Complete the Add Path form as follows:
      • On the Path Information page:
        1. For Path Name, enter a name for this path.
        2. Click Next.
      • On the Source Options page:
        1. For Source Extract, leave blank.
        2. For Trail Name, enter the Initial Load Extract trail name (I1).
        3. Click Next.
      • On the Target Options page:
        1. For Target, select wss.
        2. For Target Host, enter the target deployment URL, without the https:// or any trailing slashes.
        3. For Port Number, enter 443.
        4. For Trail Name, enter I1.
        5. For Target Authentication Method, select UserID Alias.
        6. For Domain, enter the domain name created in the previous step.
        7. For Alias, enter the alias created in the previous step (dpuser).
        8. Click Next.
   3. Click Create and Run.
   You return to the Distribution Service page where you can review the path created.
6. Review the Distribution Path:
   1. Click Receiver Service.
   2. Review the Distribution Path details.

1. In the target OCI GoldenGate deployment console, add a checkpoint table.
   1. Open the navigation menu and then click DB Connections.
   2. Click Connect to database SourceATP.
   3. In the navigation menu, click Checkpoint.
   4. In the Checkpoint page, click Add Checkpoint (plus icon).
   5. For Checkpoint Table, enter SRCMIRROR_OCIGGLL.CHECKTABLE.
   6. Click Submit.

      Tip:

      The screen will not refresh on submit. To confirm the checkpoint table was added, enter the SRCMIRROR_OCIGGLL.CHECKTABLE into the search field and then click Search.
2. Add the Replicat:
   1. Click Administrator Service, and then click Add Replicat (plus icon).
   2. On the Add Replicat page, complete the following form fields, and then click Next.
      • For Replicat type, select Nonintegrated Replicat.
      • For Process Name, enter a name, such as RIL.
   3. On the Replicat Options page, complete the following form fields, and then click Next:
      • For Name, enter the name of the Trail from Task 2 (I1).
      • For Domain, select the domain for the Autonomous Database connection.
      • For Alias, select the alias of the Autonomous Database connection.
      • For Checkpoint Table, select the Checkpoint table you created in Step 1.
   4. On the Managed Options page, leave the fields as they are, and click Next.
   5. On the Replicat Parameters page, add the following mapping, and then click Create and run:

      MAP SRC_OCIGGLL.*, TARGET SRCMIRROR_OCIGGLL.*;

   You're returned to the Overview page, where you can review the Replicat details.
3. Select the Replicat (RIL) and view its Details.
4. Click Statistics and review the number of Inserts. Refresh the page.
   • If the number of Inserts doesn't change, then all the records from the Initial Load have been loaded and you can stop the Replicat (RIL)
   • If the number of Inserts continues to increase, then keep refreshing the page until the Initial Load records are all loaded before continuing.

1. In the Oracle Cloud console, open Database Actions from the Autonomous Data Warehouse database details page.
2. In Database Actions, under Development, click SQL.
3. In the SQL tool, enter each of the following statements into the worksheet and click Run Statement:

   SELECT * FROM SRCMIRROR_OCIGGLL.SRC_CITY;
   SELECT * FROM SRCMIRROR_OCIGGLL.SRC_CUSTOMER;

1. In the source deployment console, click Distribution Service.
2. Click Add Distribution Path.
3. Complete the Add Path form as follows:
   1. On the Path Information page:
      1. For Path Name, enter a name.
      2. Click Next.
   2. On the Source Options page:
      1. For Source Extract, select the Integrated Extract (ECDC).
      2. For Trail Name, select the Integrated Extract trail file (C1).
      3. Click Next.
   3. On the Target Options page:
      1. For Target, select wss.
      2. For Target Host, enter the target deployment console URL (you can find this on the deployment details page, without the https:// or any trailing slashes.
      3. For Port Number, enter 443.
      4. For Trail Name, enter C1.
      5. For Target Authentication Method, select UserID Alias.
      6. For Domain, enter the domain name.
      7. For Alias, enter the alias.
   4. Click Create Path and Run.
4. In the target deployment console, click Receiver Service, and then review the Receiver path created.

1. Add the Replicat with the following values:
   1. On the Replicat Information page:
      • For Replicat Type, select Coordinated Replicat.
      • For Process Name, enter a name, such as RCDC.
   2. On the Replicat Options page:
      • For Replicat Trail, enter the name of the Trail from Task 2 (C1).
      • For Domain, select the domain for the Autonomous Database connection.
      • For Alias, enter the Credential Alias.
      • For Checkpoint Table, select the Checkpoint table you created.
   3. On the Replicat Parameters page, add the following mapping, and then click Create and run:

      MAP SRC_OCIGGLL.*, TARGET SRCMIRROR_OCIGGLL.*;

2. On the Administration Service Overview page, select the Replicat for Initial Load (RIL) and view its Details.
3. Click Statistics and review the number of Inserts. Refresh the page.
   • If the number of Inserts doesn't change, then all the records from the Initial Load have been loaded and you can stop the Replicat (RIL)
   • If the number of Inserts continues to increase, then keep refreshing the page until the Initial Load records are all loaded before continuing.
4. Return to the Administration Service Overview page and then start the Coordinated Replicat (RCDC).
5. After starting the Coordinated Replicat, review its Details and Statistics to view the number of Inserts.

1. In OCI Bastion, create an SSH port forwarding session using MySQL IP and port 3306. Add your public SSH key.
2. Connect to MySQL in Cloud Shell using your private key and port 3306.
3. After connecting successfully, run the following command:

   mysqlsh admin@localhost:3306 --sql

4. Run the following script to perform inserts into the HeatWave on OCI database:

   use SRC_OCIGGLL;
   Insert into SRC_OCIGGLL.SRC_CITY (CITY_ID,CITY,REGION_ID,POPULATION) values (1000,'Houston',20,743113);
   Insert into SRC_OCIGGLL.SRC_CITY (CITY_ID,CITY,REGION_ID,POPULATION) values (1001,'Dallas',20,822416);
   Insert into SRC_OCIGGLL.SRC_CITY (CITY_ID,CITY,REGION_ID,POPULATION) values (1002,'San Francisco',21,157574);
   Insert into SRC_OCIGGLL.SRC_CITY (CITY_ID,CITY,REGION_ID,POPULATION) values (1003,'Los Angeles',21,743878);
   Insert into SRC_OCIGGLL.SRC_CITY (CITY_ID,CITY,REGION_ID,POPULATION) values (1004,'San Diego',21,840689);
   Insert into SRC_OCIGGLL.SRC_CITY (CITY_ID,CITY,REGION_ID,POPULATION) values (1005,'Chicago',23,616472);
   Insert into SRC_OCIGGLL.SRC_CITY (CITY_ID,CITY,REGION_ID,POPULATION) values (1006,'Memphis',23,580075);
   Insert into SRC_OCIGGLL.SRC_CITY (CITY_ID,CITY,REGION_ID,POPULATION) values (1007,'New York City',22,124434);
   Insert into SRC_OCIGGLL.SRC_CITY (CITY_ID,CITY,REGION_ID,POPULATION) values (1008,'Boston',22,275581);
   Insert into SRC_OCIGGLL.SRC_CITY (CITY_ID,CITY,REGION_ID,POPULATION) values (1009,'Washington D.C.',22,688002);
   commit;

5. In the source MySQL deployment console, select the Change Data Capture Extract name, and then click Statistics. Verify that SRC_OCIGGLL.SRC_CITY has 10 inserts.
   Note
   
   If the Extract captured no inserts, then restart the Extract.

1. Monitor performance.
2. Manage Trail files.