This release note contains the following sections:
This section summarizes the new features and significant product changes for Oracle GoldenGate Veridata in 12c (184.108.40.206.0) release.
Oracle GoldenGate Veridata Release 12c (220.127.116.11.0) includes the following new and changed features.
Vericom provides an option to read the password directly from the Oracle Wallet rather than providing it on the command line or in a clear text file.
You can configure your Veridata Server 12c (12.2.1) and Veridata Agent with different versions because you can perform database migrations from older versions to a newer one.
You can use the Repair option to automatically kick off a Repair after a comparison completes and has confirmed out of sync data exists.
Memory use is now dynamically allocated as needed so you only need to set the maximum memory to use, and then optionally you can specify which disk area to use as virtual memory.
Oracle GoldenGate instances for tables in replication are queried and a comparison job is automatically created with the option to run it. This is available in the UI and in Vericom so that you can invoke this from remote locations like Oracle GoldenGate Monitor.
You can selectively export your database comparison configuration to an XML file that can then be imported into the same or another repository. You can select all comparisons or a subset for export. This is supported in Oracle GoldenGate Veridata releases 11.2, 12.1.3, 12.2.1 and 18.104.22.168.0 for all databases supported in those releases. This new export utility, along with the import utility introduced in 12.1.3, replace the previous
Delta processing that allows you to process large table compares in an acceptable time frame has been enhanced to include all supported databases is no longer limited to Oracle GoldenGate NonStop.
Oracle GoldenGate Veridata now fully supports the use of the IBM DB2 for i (IAS400/iseries) database.
Oracle GoldenGate Veridata now fully supports the use of the IBM Informix database.
The free Oracle Express Edition (XE) database is now supported.
MySQL database is not supported, since Oracle WebLogic Server does not natively support this database.
The repository export utility works with all Veridata repositories from release 11g (11.2) and 12c (12.1.3) including releases that support My SQL.
Compact domain support was removed because it does not use an OPSS schema.
This section lists the parameters and settings that are no longer used in this new release. These parameters are deprecated in the
This section contains information about bugs that have been corrected. 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. The information in this section is divided into the following releases:
Bug 23578323/Bug 24455263 - Failed: OGGV-00118: Agent message (999): Unexpected zlib needs input
Corrected an issue with the use of zlib libraries incorrectly compressing and decompressing message bytes between the server and agent.
Bug 21797520 - Vericom needs password encryption
This feature provides an option to store Username and Password in Oracle Credential Store to be used for Vericom. This allows customer to create alias for Vericom user and use the alias while running Vericom and this also helps in automating Vericom run.
Bug 21910141 - OGGV-00119: Agent remote message (101): OGGV-600013: Unhandled exception
Limited the number of retries the agent makes when a JDBC connection fails to validate the connection and added improved error messages.
Bug 21909923 - Veridata slowness
Corrected the job Purge feature to properly delete the contents of repair_rows table used by Repaid jobs. This prevents the Slowness when loading the repair page after the purging of old data.
Bug 21687175- Finished Jobs page query optimization
Corrected an issue with the finished job page, which is taking too much time to load when Veridata repository contains too much data.
Bug 23039790- Veridata server crash when navigating Completed Jobs concurrent modification
Corrected an issue with the loading of the finished jobs page, which is causing StackOverFlow error.
Bug 19277798 - Translating database characters based on database settings and not Oracle GoldenGate settings
In certain circumstances, the character set used to encode character does not match the database character set has been fixed. The raw bytes are retrieved from the database and used to specify the character set to decode the data before encoding it as UTF-8 for comparison.
This section details the known issues and any workarounds for the Oracle GoldenGate Veridata Release 12c (12.2.1) release.
On Windows, the
JAVA_HOME must be set to a directory path that does not contain spaces.
Veridata Agent Incorrectly Rounds Timestamp Values for Sybase Target
The Veridata agent is incorrectly rounding off
TIMESTAMP/DATETIME/TIME values when the time part of the value ends in .998 and .999. The comparison of a
TIMESTAMP/DATETIME/TIME value from the source to a
DATETIME value from a Sybase target can be reported incorrectly as in-sync or out-of-sync when the source value ends in .998 or .999.
DB2 for i: DataDirect Driver with VARCHAR Key Columns
When using the DataDirect driver,
VARCHAR key columns are returned with trailing blanks truncated during the COOS step. This is only occurring during the COOS step when a predicated
SELECT is processed. You can workaround this issue by generating SQL statements to concatenate an empty string to the end of
VARCHAR key columns to preserve the trailing spaces.
DB2 for i: DataDirect Driver with CLOBs and CCSID 1208
When using the DataDirect driver, CLOBs declared with CCSID 1208 (UTF-8) are returned incorrectly. The correct data is inserted correctly and verified by casting the value to a BLOB then inspecting that the raw bytes were the correct UTF-8 values. There is currently no workaround for this issue because the JTOpen driver does not select these values correctly.
DB2 for i: DataDirect Driver with the DB2 Native Driver
When using the DataDirect driver and DB2 Native driver,
IDENTITY columns cannot be detected from the JDBC metadata. You can workaround this issue by querying the DB2 iSeries
SYSCOLUMNS directly to supplement the JDBC metadata.
DB2 for i: DataDirect Driver with NULLID Library
The DataDirect driver requires a DB2 package to store query execution plans. By default the NULLID library is used; if it does not exist, it is created the first time a connection is made. If the package already exists in the NULLID library and the current user does not have permission to access the package a failure occurs. The DataDirect driver has workarounds to manually create the package and to use an alternative library to store the packages, see the driver documentation for specifics.
DB2 for i: Native Driver with UTF-8
During a repair, the native driver fails when the LOB column is UTF-8 and the inserted data is multibyte. The driver does not recognize that UTF-8 expansion may require a larger buffer.
Informix: Unsupported Data Types with DataDirect JDBC Drivers
BIGSERIAL data types are not supported when using the DataDirect JDBC drivers.
Informix: Integer Minimum Value Limitation
The limitation for the minimum value of the
BIGINT data types is -(2x-1)(x is 31, 15, 63 sequentially). On a repair attempt (insert/update) of (-2x) from a non-Informix data base to an Informix data fails as repair Warning.
For the following release upgrade paths the reports and job run details are not available:
Veridata 11g MySQL to Veridata 12c (12.1.3) Oracle and SQL Server
Veridata 11g MySQL to Veridata 12c (12.2.1) Oracle and SQL Server
Veridata 12c (12.1.3) MySQL to Veridata 12c (12.2.1) Oracle and SQL Server
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.
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.
To view the Oracle GoldenGate Knowledge Base, follow these steps:
Select your language and then log in with your email and Oracle password.
Click the Knowledge tab.
Under Select a Product Line, type the name "GoldenGate" and then select an Oracle GoldenGate product from the context menu. (You may have to wait a few seconds for this list to appear). As an alternative, you can select from the drop-down list or use the Browse link to select Middleware, then Data Integration, then GoldenGate.
Under Task, select the type of query you want to make, such as Troubleshoot.
Under Version, select the version of Oracle GoldenGate that you are using.
Under Enter Search Terms, type a search keyword or multiple keywords to focus the query.
If you need help with My Oracle Support, click Help at the top of the application window.
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:
Select your language and then log in with your email and Oracle password.
Click the Service Requests tab.
Click Create SR.
Complete the form, referring to the Help at the top of the application window if necessary.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at
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.
Oracle® GoldenGate Veridata Release Notes, 12c (22.214.171.124.0)
Copyright © 2015, 2017, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.