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

• OCI Bastion, to connect to HeatWave on OCI Database, load the sample database, and perform inserts.
• A HeatWave on OCI Database to serve as the source database.
• An Azure Event Hubs namespace and an event hub created
  Note
  
  Kafka Surface is not enabled in Azure Event Hubs Basic Tier. Standard or Premium tier is required.

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.

1. Create a MySQL deployment for the source HeatWave on OCI database.
2. Create a Big Data deployment for the target Azure Event Hubs.
3. Create a connection to the source MySQL Heatwave Database.
4. Create an Azure Event Hubs connection.
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 Big Data 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. Open the navigation menu, and then select Configuration.
5. Review the credentials for the MySQL Database Server connection. Take note of the Domain and Alias.
6. Return to the Administration Service Overview page.
7. On the Administration Service Overview page, click Add Extract (plus icon).
8. On the Extract Type page, select Change Data Capture Extract, and then click Next.
9. Complete the Extract Options as follows, and then click Next:
   1. For Process Name, enter a name for the Extract, such as CDCEXT.
   2. For Credential Domain, select the domain from Step 5.
   3. For Credential Alias, select the alias from Step 5.
   4. For Trail Name, enter a two-character trail name, such as C1.
10. Enable Remote if capturing from a MySQL Database that is not using global transaction identifiers (GTIDs).
11. On the Extract Parameters page, add the following:

    TABLE SRC_OCIGGLL.*;

12. Click Create and Run.

    You're returned to the Administration Service Overview page, where you can observe the Extract starting.

1. On the Deployments page, select the target Big Data deployment.
2. On the deployment details page, click Launch Console.
3. Create a user for the Distribution Path:
   1. Open the navigation menu, and then click Administrator.
   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 MySQL deployment console, create a credential for the user created in the previous step.
   1. Open the navigaton menu, and then select Configuration.
   2. Click Add Credential (plus icon), complete the fields as follows, and then click Submit:
      • For Credential Domain, enter GGSNetwork.
      • For Credential Alias, enter dpuser.
      • For Database Name, you can enter any name and leave the Database Server and Port fields blank, or use the default values.
      • For User ID, enter ggsnet.
      • For Password, enter the same password used in the previous step.
5. Create a Distribution Path:
   1. In the source MySQL deployment console, click Distribution Service, and then click Add Path (plus icon).
   2. Complete the following fields, and click Create and Run:
   • For Path Name, enter a name for this path.
   • For Source Extract, select the Change Data Capture Extract (CDCEXT).
   • For Trail Name, select the Change Data Capture Extract trail file (C1).
   • For Target Authentication Method, select UserID Alias.
   • For Target, select wss.
   • For Target Host, enter the target OCI GoldenGate deployment console URL, without the https:// or any trailing slashes.
   • For Port Number, enter 443.
   • For Trail Name, enter C1.
   • For Domain, enter the domain name created in the previous step.
   • For Alias, enter the alias created in the previous step.

   You're returned to the Distribution Service Overview page where you can review the path created.

6. In the target OCI GoldenGate Big Data deployment console, review the Receiver path created as a result of the Distribution path:
   1. Click Receiver Service.
   2. Review the Receiver path details.

1. In Big Data deployment, click Administrator Service, and then click Add Replicat (plus icon).
2. Add a Replicat with the following values:
   1. On the Replicat Information page, under Replicat type, select Classic Replicat, and enter a Process Name.
   2. On the Replicat Options page:
      • For Trail Name, enter the name of the Trail from Task 2.
      • For Target, select a Azure Event Hubs.
      • For Alias, select the Azure Event Hubs connection created in Task 1.
   3. On the Replicat Parameters page, leave the default.
   4. On the Properties File page, provide a topic name for topicMappingTemplate.
   5. Click Create and Run.

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.
6. In target Big Data deployment console, select the Replicat name and then click Statistics. Verify that SRC_OCIGGLL.SRC_CITY has 10 inserts.
7. In Azure Event Hubs, you can check the message statistics.