About data verification

Verify data in OCI GoldenGate using the Veridata deployment type. Learn more about Veridata.

Veridata is a data comparison and repair solution that identifies, reports, and automatically fixes data discrepancies between different databases without interrupting ongoing processes. It empowers you to confidently make critical decisions based on reliable, up-to-date information.

Data verification concepts

The following concepts are essential for working with OCI GoldenGate Veridata.

• Veridata Agent: Interacts with source or target databases to retrieve blocks of data rows, column-level detail, and runs queries for repairs. Each connection requires its own agent.

• Veridata Server: Compares data, reports out of sync data, and repairs data. The server also coordinates jobs across other Veridata components. Assign connections to the Veridata server deployment to connect agents to the server.

Supported connection types for data verification

OCI GoldenGate Veridata currently supports the following Oracle Databases:

• Oracle Autonomous AI Database

• Oracle AI Database

• Oracle Exadata

• Oracle AI Database@AWS - Autonomous Database

• Oracle AI Database@AWS - Exadata

• Oracle AI Database@Azure - Autonomous Database

• Oracle AI Database@Azure - Exadata

• Oracle AI Database@Google Cloud - Autonomous Database

• Oracle AI Database@Google Cloud - Exadata

• Amazon RDS for Oracle

Sizing considerations for Data Verification deployments

Ensure that you first review Metering and billing to learn about Oracle Compute Unit (OCPU) selection and scaling.

OCI GoldenGate verification OCPU usage is calculated based on the following factors:

• Number of Compare pairs running concurrently:

  • Guidance was determined using Compare pairs with one source table compared to one target table per compare job.

  • Grouping many tables into one compare job can increase OCPU usage beyond these baselines.

• Primary key (PK) availability:

  • Data verification deployments use hashing techniques to efficiently compare data between source and target tables.

  • The processing requirements are lower for tables with a Primary Key (Has PK) compared to tables without a Primary Key (No PK).

The following tables list the estimated number of OCPUs required based on the number of Compare pairs running concurrently for Veridata Server and Veridata Agents deployments:

Table - Veridata Server deployments

Number of concurrent Compare pairs	OCPUs used for Compare pairs with primary keys	OCPUs used for Compare pairs without primary keys
1 to 2	1	2
3 to 5	2	3
6 to 10	3	5
11 to 14	4	6
15 to 16	4	7

Table - Veridata Agent deployments

Number of concurrent Compare pairs	OCPUs used for Compare pairs with primary keys	OCPUs used for Compare pairs without primary keys
1 to 3	1	1
4 to 6	2	2
7 to 10	3	3
11 to 15	3	4
16	4	4

Note: Sizing values are planning estimates based on controlled performance testing and are intended as a baseline starting part, not a guarantee of performance or completion time.