1.1 Release Notes

This document describes the new features, major changes, and the known issues in Oracle GoldenGate Veridata Release 23c. This release was certified with English only, other languages may work but not fully tested.

1.1.1 New Features and Changes in Oracle GoldenGate Veridata 23c

This section summarizes the new features and significant product changes for Oracle GoldenGate Veridata in 23c release.

Parent topic: Release Notes

1.1.1.1 New Features and Changes in Oracle GoldenGate Veridata 23c (23.4.0.0.0) - August 2025

Support for Snowflake

Support for Snowflake is now available, including key functionalities such as data comparison, data repair, and the generation of Repair SQL. This enhancement enables seamless data comparison between Snowflake databases, as well as between Snowflake and other heterogeneous database systems, whether as a source or as a target.

Fast compare

A new Fast Compare feature has been introduced, enabling users to perform data comparisons based on row counts. A new comparison type option is now added to Profile>General offering two modes: Full and Row Count.
  • To perform comparison based on row count, select the Row Count option.
  • To perform a complete data comparison, select the Full option.

Ability to create auto partitions for subset of a table

You can now create auto partitions for a table subset. Subset of table is selected by setting Row partitions in the compare pair. If you create auto partitions for a table and specify Row partition for any auto partition, then it is reflected in all auto partitions as it represents the same table.

Additional preference option for default view for Monitor Jobs page

A new option for the default view for Monitor pages is added in the User Preferences on the Home page. You can set either Completed Jobs or Running Jobs as the default page to display when you open the Monitor Jobs page on the navigation menu. The default is set to the Completed Jobs page.

1.1.1.2 New Features and Changes in Oracle GoldenGate Veridata 23c (23.3.0.0.0) - May 2025

Oracle GoldenGate Veridata Release 23c (23.3.0.0.0) includes the following new and changed features:

Support 2-way SSL between Veridata Server and NSK C-agent

2-way SSL support between Veridata Server and NSK C-agent has been added.

1.1.1.3 New Features and Changes in Oracle GoldenGate Veridata 23c (23.2.0.0.0) - January 2025

Oracle GoldenGate Veridata Release 23c (23.2.0.0.0) includes the following new and changed features:

Extend support to display approximate total row number to non-Oracle databases

Support has been extended to display approximate total row numbers to non-Oracle databases, such as SQL Server, MySQL, PostgreSQL, DB2 LUW, and DB2 I.

Support for Oracle Database 23ai

Oracle GoldenGate Veridata now supports Oracle database 23ai.

Rest API now retrieves available logs

REST APIs for retrieving logs based on log level, log type (api, perf, or both) and last lines from logs have been added.

1.1.1.4 New Features and Changes in Oracle GoldenGate Veridata 23c (23.1.0.0.0)

Oracle GoldenGate Veridata Release 23c (23.1.0.0.0) includes the following new and changed features.

New Modernized User Interface

Oracle GoldenGate Veridata 23c comes with a newly designed modernized user interface which is more intuitive. See the Oracle GoldenGate Home page in Oracle GoldenGate Veridata Documentation.

New Built-In Repository Database

You do not have to maintain a separate repository database for Oracle GoldenGate Veridata. Oracle GoldenGate Veridata 23c comes with built-in repository database which is MySQL. For more information, see Oracle GoldenGate Veridata Architecture in Oracle GoldenGate Veridata Documentation.

No more dependency on Oracle Fusion Middleware

Oracle WebLogic was the application server used in Oracle GoldenGate Veridata. Starting from Oracle GoldenGate Veridata 23c, there is no more dependency on Fusion Middleware, as Oracle WebLogic has been replaced with a light-weight Helidon application server. For more information, see Oracle GoldenGate Veridata Architecture in Oracle GoldenGate Veridata Documentation.

Simplified Installation

The installation of Oracle GoldenGate Veridata 23c has been made simple, which is now a two-step process:
  1. Install Oracle GoldenGate Veridata.
  2. Run the vdtca.sh to configure Oracle GoldenGate Veridata.
For more information, see Installing and Running Oracle GoldenGate Veridata in Oracle GoldenGate Veridata Documentation.

Export/Import Utility

Starting from Oracle GoldenGate Veridata 23c, the Export and Import utilities are also available in Oracle GoldenGate Veridata UI. For more information, see Utilities in Oracle GoldenGate Veridata Documentation.

REST API

Oracle GoldenGate Veridata 23c is supported with REST APIs. For more information, see REST API for GoldenGate Veridata.

User Management

There are various roles in Oracle GoldenGate Veridata and these roles are categorized into various User Groups. The users can be assigned to these User Groups accordingly. For more information, see User Management in Oracle GoldenGate Veridata Documentation.

Single command to start Oracle GoldenGate Veridata

Start from Oracle GoldenGate Veridata 23c, you need just a single command to start Oracle GoldenGate Veridata. You do not have to start the Application server and Veridata Server separately.

Enhanced Report

Oracle GoldenGate Veridata 23c comes up with new enhanced way of displaying the Job reports.

Behavioral Changes

VGPP Utility

Starting from Oracle GoldenGate Veridata 23c, the GoldenGate Parameter Processing for Veridata (VGPP) has been deprecated. It has been integrated with the Import utility. The Import utility can accept both the file formats .xml and .prm as inputs to perform the Oracle GoldenGate Veridata configurations.

User Management

Oracle GoldenGate Veridata 23c comes with enhanced User Management. You can now create, delete, edit, users, and user groups from the Oracle GoldenGate Veridata User Interface itself. For more information, see User Management in Oracle GoldenGate Veridata Documentation.

1.1.1.5 New Features and Changes in Oracle GoldenGate Veridata C Agent for HP NonStop (23.3.0.0.0) — May 2025

Oracle GoldenGate Veridata 23.3.0.0.0 C Agent for HP NonStop

Oracle GoldenGate Veridata Agent now supports 2-way SSL in HP Nonstop.

1.1.2 Corrected Problems

This section contains information about bugs that have been corrected in 23c release. For questions on specific bugs or ticket numbers, consult Oracle Customer Support. SR is the Oracle Support SR number, and BugDB is the bug identification number.

Parent topic: Release Notes

1.1.2.1 Release 23.4.0.0.0 — July 2025

38138653 - Upgrading MySQL Repository for Oracle Veridata 23.3 to Meet Security Audit Requirements

This issue has been fixed. MySQL repository used in Oracle Veridata 23.4 now complies with the audit requirements.

38063130 - 23c Veridata application does not display icons when there is no internet

This issue has been fixed. Launch Veridata UI in offline mode, the icons displayed are now empty boxes, and you can navigate to the pages.

38027260 - VDT23c - Incorrect info shown in Pie graph for In-Sync Tables

This issue has been fixed. Pie graph shows in-sync for tables on running jobs.

38027172 - VDT23c-Delta is not getting enabled for a specific or multiple tables

This issue has been fixed. Delta processing changes are now registered and applied after you click the save button.

38003764 - Create Group and Compare Pair feature does not work, after upgrade to veridata to 23.3

This issue has been fixed. For VGPP with multiple catalogs, catalog was fetched for non-container databases. This issue is fixed so that the catalog is only fetched for container databases.

37963017 - [UI] Issue with Partition Name Mismatch in Veridata 23.2. But Veridata 12c works

This issue has been fixed.

37854508 - Unable to fetch schemas during compare pair creation in case of Oracle database in some specific scenarios

This issue has been fixed. Unable to fetch schemas during compare pair creation or compare pair update in case of Oracle database, when PDB is linked to multiple Service names, or when PDB name and service name are different. The fix is that if the PDB service is not accessible, the service mentioned in the JDBC URL is substituted with the CDB service.

37084214 - Warning while repairing Binary Double datatype

This issue has been fixed.

37507078 - Postgres: 42.7.4 (default) connector shows schemas as catalog

This issue has been fixed. Only the database mentioned in jdbc url is shown in the catalog dropdown.

37457241 - Postgres: Array To Vector Comparison shows same data as different

This issue has been fixed.

Parent topic: Corrected Problems

1.1.2.2 Release 23.3.0.0.0 — May 2025

Bug 37663474 - Loading of Preview tab in Create Groups and Compare Pairs is slow

This issue has been fixed. While creating Groups and Compare Pairs, the Preview tab loads faster.

Bug 37662582 - Incorrect Sorting by number of rows for Running Jobs

This issue has been fixed. The Sort by number of Rows feature works properly in the Running Jobs page now.

Bug 37589450 - Create Group and Compare Pair-Search is not working as expected

This issue has been fixed. When you filter using the complete partition name, only the table name and the partition you have looked up are displayed.

Bug 37457463 - Coos Join hangs with tables having duplicate records

This issue has been fixed. Duplicates are handled in the COOS join and the comparison does not get stuck now.

Bug 37515829 - Unable to edit Row Partitions

This issue has been fixed. The Row Partitions field is now editable.

Bug 37821092 - Veridata 23c job cancelled automatically without any error message/ Veridata MySQL DB Crashing

This issue has been fixed.

Parent topic: Corrected Problems

1.1.2.3 Release 23.2.0.0.0 — January 2025

Bug 37163212 - User provided Group and Job names are not honored during parameter file import

This issue has been fixed. User Provided Group name and Job name are now considered during the import of the parameter file.

Bug 37160801 - Monitoring repair job filter by date requires timestamp

This issue has been fixed. The timestamp has been included now during the monitoring of repair job filter by date. The supported format now is yyyy-MM-dd'T'HH:mm:ss'Z'. For example, 2024-03-13T18:30:00Z.

Bug 37094623 - Compare Pair table is not fully shown if one of the CPs is failed to repair

This issue has been fixed. The Compare Pair table is being shown as expected.

Parent topic: Corrected Problems

1.1.3 Known Issues and Workarounds

This section details the known issues and any workarounds for the Oracle GoldenGate Veridata Release 23c release.

Parent topic: Release Notes

1.1.3.1 Release 23.4.0.0.0 — August 2025

Bug 38268134 - Unable to exclude columns from comparison by unchecking 'Use' column when columns are mapped

Workaround: To remove column from comparison, change target to empty value from dropdown and save. This will remove the column from comparison.

Bug 38097790 - Overall repair status shows OutOfSync when repaired in multiple iterations (Partial repair)

Workaround Do a complete repair in place of a partial one, by selecting Repair from the More Actions dropdown or by selecting the Repair from the Compare pair table.

Bug 38027246 - Group and Compare Pairs stuck when creating 2500 partitions for single table

Workaround: This issue has no workaround. You have to wait on Group and Compare Pairs creation page, as it takes longer to load. It appears to be hung, whereas it is just slowed.

1.1.3.2 Release 23.3.0.0.0 — May 2025

Bug 37666767 - Repair fails for MariaDB:FLOAT.

The issue occurs when an update query is unable to locate a row due to the inclusion of the existing value in the WHERE clause. This behavior is also present in the MySQL instance.

Workaround: Navigate to the user's profile Repair category and set the Check changed values option to No instead of Use System Default.

Bug 37666738 - Repair fails for MariaDB:TIME

The issue occurs when an update query is unable to locate a row due to the inclusion of the existing value in the WHERE clause.

This behavior is also present in the MySQL instance.

Workaround: Navigate to the user's profile Repair category and set the Check changed values option to No instead of Use System Default.

Bug 37666690 - Repair fails for MariaDB:VARCHAR

For both MySQL and MariaDB, Oracle GoldenGate Veridata's repair currently works only when the VARCHAR value is less than 32,767 bytes (fewer than 32,767 characters for single-byte character sets, latin1).

For multi-byte character sets in MySQL and MariaDB, this threshold translates into lower character limits:
  • utf8 (3 bytes/char): maximum supported length = 10,922 characters
  • utf8mb4 (4 bytes/char): maximum supported length = 8,191 characters

Bug 37888195 - NSK: Dictionary & record structure not fetched in Enscribe compare pair column mapping

Dictionary and table structure not saved and fetched in Enscribe Compare Pair column mapping.

Bug 37457241 - postgres : Array To Vector Comparison shows same data as different

Array To Vector Comparison shows same data as different. Even though the values are identical, the underlying format is different. Therefore, it is always be shown as out-of-sync. Repair doesn't work as well from Array to Vector Data Type.

Bug 36287277 - Singlestore - Run repair failed for Date and Timestamp datatypes

Repair fails for DATE and TIMESTAMP column data.

Bug 36285419 - Job execution failed for singlestore to oracle blob column

Comparison failed for BLOB column while performing comparison between Singlestore (Source) to Oracle (Target).

Bug 36279870 - Singlestore to Oracle Run repair failed for Insert with warning

Repair fails when primary key column has space (' ').

Bug 36276833 - Run Repair failed for Singlestore DateTime type

Repair fails for DATETIME Datatype.

Bug 35605136 - Run Repair failed for Text (Singlestore) to XML (Oracle) Datatype

Repair fails for Singlestore TEXT Datatype to Oracle XML Datatype.

Bug 35542455 - Singlestore - Comparison after successful Run Repair shows OOS

Comparison after successful repair shows Out-Of-Sync rows, when the column data has space (' ').

1.1.3.3 Release 23.2.0.0.0 — January 2025

Bug 37507723 - Postgres Array to Vector Comparison and repair does not work.

Array To Vector Comparison shows same data as different. Even though the values are identical, the underlying format is different. Therefore, it is always be shown as out-of-sync. Repair doesn't work as well from Array to Vector Data Type.

Bug 37466943 - Oracle to Postgres- Hetero Vector Comparison shows incorrect result

Comparison of Oracle Vector with Postgres Vector does not show appropriate results.

Bug 37502398 - Oracle Vector : Float Values are not repaired correctly ( precision issue)

For a few float values in Oracle 23ai Vector datatype, the row value does not get repaired as expected because of precision issue(s).

Bug 37515829 - Unable to edit Row Partitions

In the Groups and Compare Pairs page, the Row Partitioning is disabled by default, though it is enabled.

Workaround: Disable the Row Partitioning toggle switch and enable it again.

Bug 37507078 - Postgres: 42.7.4 (default) connector shows schemas as catalog

When you use postgresql-42.7.4.jar (the default jar in veridata Server) for postgres agent and then create a connection, schemas are shown as catalogs while creating Groups and Compare Pairs.

Bug 37084214 - Warning message is displayed while repairing Binary Double datatype

The Binary double datatype when found out-of-sync, does not get repaired because of the limitation in ojdbc11-23.2.0.0 driver.

1.1.3.4 Release 23.1.0.0.0 — October 2024

Bug 37165991 - Repair monitoring API does not have all the repair row counts in the response

When a repair job is running, the API services has row counts for rows with different repair status (Pending, Successful, Failed, Skipped, and Running) and the repair types (insert, update, and delete) are set to zero.

This gets updated to correct values only when the entire job with all the compare pairs gets completed.

Bug 36813621 - First Login doesn't work at times

If you try to login for the first time after a long gap, then the login is not successful, at times. This can happen when VPN is disconnected and then reconnected.

Workaround: Click the Login button again.

1.1.4 Getting Help with My Oracle Support

Use My Oracle Support to find knowledge solutions, workaround, and other information that is reported by customers, partners, and Oracle employees. My Oracle Support also enables you to open a Service Request. If a patch is required to resolve a service request, you will receive instructions on how to download it from My Oracle Support.

Note:

If you purchased Oracle GoldenGate Veridata and support through a distributor, contact your distributor instead of attempting to create a service request through My Oracle Support.

Parent topic: Release Notes

1.1.4.1 Creating an Oracle GoldenGate Support Case

If you cannot find an answer to your question or problem in the Knowledge Base, you can open a support case with Oracle Support by following these steps:

  1. Go to http://support.oracle.com.

  2. Select your language and then log in with your email and Oracle password.

  3. Click the Service Requests tab.

  4. Click Create SR.

  5. Complete the form, referring to the Help at the top of the application window if necessary.

1.1.5 Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Parent topic: Release Notes