Create data verification resources

Learn to the create the resources you need to work with data verification in OCI GoldenGate.

About data verification deployments

To use data verification, you must create at least one Veridata Agent and one Veridata Server deployment. The number of Agent deployments you need depends on the number of source and target connections for which to verify data. Create an Agent deployment for each database connection, and one GoldenGate connection for each Agent. For example, if you have two database connections, then you must create two Agent deployments and two GoldenGate connections. Assign a database connection to each Agent deployment (one connection per Agent), and then assign the two GoldenGate connections to the Server deployment.

Before you proceed, ensure that you review the following articles:.

Before you begin

Before you create Veridata Server or Agent deployments, review the following requirements:

Ensure that you have the appropriate policies added if you want to:
- Enable public deployment console access in the Advanced options. OCI GoldenGate creates a load balancer in your tenancy VCN on your behalf. To ensure successful creation of the deployment and load balancer, you must have the appropriate policies, quotas, and limits in place.
- Use Zero Trust Packet Routing (ZPR) to control access to this deployment.
Depending on your source and target technology types, you may need more than one deployment. If you're not sure how many deployments you need for your solution, see Example topologies for details.

Create a Veridata agent deployment

To create a Veridata agent deployment:

In the Console navigation menu, select Oracle AI Database, and then select GoldenGate.
On the Deployments page, select Create deployment.
In the Create deployment panel, enter a name and optionally, a description.
If creating this deployment for GoldenGate on Multicloud, select your Subscription.
1. From the Compartment dropdown, select the compartment in which the Resource Anchor resides
2. Select the Multicloud partner region.
3. Select your Partner availability zone. The available options populate based on the selected Multicloud partner region.
From the Compartment dropdown, select a compartment in which to create the deployment.
For Automatically select the best availability domain placement:
- Select this option for the service to select the Availability domain and Fault domain on your behalf.
- Deselect this option to select the Availability domain and Fault domain yourself.
For Choose a deployment type, select Data verification.
From the Select a technology dropdown, select Oracle GoldenGate Veridata Agent.
For Version, the latest version is automatically selected. Select Change version to select a different version.

Learn more about versions.
Select one of the following options:
- Development or testing: Sets up a deployment with recommended defaults for a development or testing environment. The minimum number of OCPUs is 1.
- Production: Sets up a deployment with recommended default of 4 OCPUs with auto-scaling enabled for a production environment. The minimum number of OCPUs needed is 3, with auto-scaling enabled.
For Select OCPU enter the number or select Change shape to use the slider to choose the number of Oracle Compute units (OCPUs) to use.

Note: One OCPU is equivalent to 16gb of memory. For more information, see OCPU management and billing.
(Optional) Select Auto scaling.

Note: Auto scaling enables OCI GoldenGate to scale up to three times the number of OCPUs you specify for OCPU Count, up to 24 OCPUs. For example, if you specify your OCPU Count as 2 and enable Auto Scaling, then your deployment can scale up to 6 OCPUs. If you specify your OCPU Count as 20 and enable Auto Scaling, OCI GoldenGate can only scale up to 24 OCPUs.
From the Private Subnet in <Compartment> dropdown, select the subnet to which a private endpoint is created from the OCI GoldenGate service tenancy. This ensures that the deployment is always available over this subnet, as long as the policies for this subnet allow access.

To select a subnet in a different compartment, select Change compartment.

Note: You can only select a private subnet when creating or updating a deployment.
(Optional) Select Show advanced options for network and security options, and to add tags for resource management.
1. In the Maintenance section:
  1. Select Customize maintenance window to define the start of the maintenance window to upgrade the deployment.
  2. (Optional) For Major release auto-upgrade period in days, enter the number of days, between 0 and 365.
  3. (Optional) For Bundle release auto-upgrade period in days, enter the number of days, between 0 and 180 days.
  4. (Optional) For Security patch auto-upgrade period in days, enter the number of days, between 0 and 14 days.
  5. Select Enable minor release auto-upgrade, and, optionally, enter the number of days.
    
    Note: Learn more about scheduling upgrades.
2. In the Security attributes section, add a security attribute to control access to this deployment using Zero Trust Packet Routing (ZPR).
3. In the Tags section, add tags to help track the resources within your tenancy. Select + Additional tag to add more tags. Learn more about tagging.
Select Create to create the deployment, or select Save as Stack to save this configuration to Resource Manager.

If you select Save as stack, then the Save as stack panel opens, where you can optionally provide a name and description for the stack and select the compartment to save it in. Learn more about Resource Manager.

Next, create a connection and assign it to the Veridata Agent deployment.

Create a Veridata server deployment

To create a Veridata agent deployment:

In the Console navigation menu, select Oracle AI Database, and then select GoldenGate.
On the Deployments page, select Create deployment.
In the Create deployment panel, enter a name and optionally, a description.
If creating this deployment for GoldenGate on Multicloud, select your Subscription.
1. From the Compartment dropdown, select the compartment in which the Resource Anchor resides
2. Select the Multicloud partner region.
3. Select your Partner availability zone. The available options populate based on the selected Multicloud partner region.
From the Compartment dropdown, select a compartment in which to create the deployment.
For Automatically select the best availability domain placement:
- Select this option for the service to select the Availability domain and Fault domain on your behalf.
- Deselect this option to select the Availability domain and Fault domain yourself.
For Choose a deployment type, select Data verification.
From the Select a technology dropdown, select Oracle GoldenGate Veridata server.
For Version, the latest version is automatically selected. Select Change version to select a different version.

Learn more about versions.
Select one of the following options:
- Development or testing: Sets up a deployment with recommended defaults for a development or testing environment. The minimum number of OCPUs is 1.
- Production: Sets up a deployment with recommended default of 4 OCPUs with auto-scaling enabled for a production environment. The minimum number of OCPUs needed is 3, with auto-scaling enabled.
For Select OCPU enter the number or select Change shape to use the slider to choose the number of Oracle Compute units (OCPUs) to use.

Note: One OCPU is equivalent to 16gb of memory. For more information, see OCPU management and billing.
(Optional) Select Auto scaling.

Note: Auto scaling enables OCI GoldenGate to scale up to three times the number of OCPUs you specify for OCPU Count, up to 24 OCPUs. For example, if you specify your OCPU Count as 2 and enable Auto Scaling, then your deployment can scale up to 6 OCPUs. If you specify your OCPU Count as 20 and enable Auto Scaling, OCI GoldenGate can only scale up to 24 OCPUs.
From the Private Subnet in <Compartment> dropdown, select the subnet to which a private endpoint is created from the OCI GoldenGate service tenancy. This ensures that the deployment is always available over this subnet, as long as the policies for this subnet allow access.

To select a subnet in a different compartment, select Change compartment.

Note: You can only select a private subnet when creating or updating a deployment.
For Choose a License type, Bring your own license (BYOL) is the only valid license type for this deployment type. Enable BYOL OCPU limit to control the number of OCPUs covered by BYOL. The minimum number of OCPUs covered is 1.
(Optional) Select Show advanced options for network and security options, and to add tags for resource management.
1. In the Maintenance section:
  1. Select Customize maintenance window to define the start of the maintenance window to upgrade the deployment.
  2. (Optional) For Major release auto-upgrade period in days, enter the number of days, between 0 and 365.
  3. (Optional) For Bundle release auto-upgrade period in days, enter the number of days, between 0 and 180 days.
  4. (Optional) For Security patch auto-upgrade period in days, enter the number of days, between 0 and 14 days.
  5. Select Enable minor release auto-upgrade, and, optionally, enter the number of days.
    
    Note: Learn more about scheduling upgrades.
2. In the Security attributes section, add a security attribute to control access to this deployment using Zero Trust Packet Routing (ZPR).
3. In the Tags section, add tags to help track the resources within your tenancy. Select + Additional tag to add more tags. Learn more about tagging.
Select Create to create the deployment, or select Save as Stack to save this configuration to Resource Manager.

If you select Save as stack, then the Save as stack panel opens, where you can optionally provide a name and description for the stack and select the compartment to save it in. Learn more about Resource Manager.

Ensure that you create a Veridata Agent deployment for each source and target connection, and assign an agent to each connection. Then, assign the connections to the Veridata Server deployment.

Create connections

Create a database connection for each source and target for which to verify data. OCI GoldenGate Veridata supports the following connection types:

Ensure that you create and assign a Veridata Agent deployment to each database connection.

Create a GoldenGate connection for each Veridata Agent deployment, and then assign the GoldenGate connections to the Veridata Server deployment.

Assign a connection to a deployment

Use the following instructions to assign a database connection to a Veridata Agent deployment or a GoldenGate connection to a Veridata Server deployment.

Ensure that you have connections created for your source and target technologies.

Note: If using connections with password secrets, the deployment you’re assigning the connection to must be able to access the connection’s password secrets. Ensure that you add the policy: allow dynamic-group <group-name> to read secret-bundles in <location> to your compartment or tenancy.

To assign a connection to a deployment:

On the deployment details page, select Assigned connections.
Select Assign connection.
In the Assign connection dialog, select a connection from the dropdown. If you want to select a connection from a different compartment, select Change Compartment.
Select Assign connection.

The selected connection appears in the Assigned connections list. You can also view and manage this relationship from the Connection details page under Assigned deployments.

Note: If a connection with a dedicated endpoint remains unassigned for seven days, then the service converts it to a shared endpoint.

When you assign a connection to a deployment, GoldenGate removes disallowed characters from the name you entered and trims it to 30 characters in length. The name must only contain alphanumeric characters, and follow the alias pattern: ^[a-zA-Z][a-zA-Z0-9_#$]*$. If a connection with the same alias is already assigned, a number is automatically added to the new alias name.