Oracle® GoldenGate Veridata

Release Notes

12c (12.2.1.2)

E78471-03

December 2017

This document describes the new features, major changes, and the known issues in Oracle GoldenGate Veridata Release 12c (12.2.1.2.0).

This release note contains the following sections:

New Features and Changes in Oracle GoldenGate Veridata 12c (12.2.1.2)

This section summarizes the new features and significant product changes for Oracle GoldenGate Veridata in 12c (12.2.1.2) release.

Oracle GoldenGate Veridata Release 12c (12.2.1.2) includes the following new and changed features.

Encrypted Password for Vericom

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.

Automatic Repair After Compare

You can use the Repair option to automatically kick off a Repair after a comparison completes and has confirmed out of sync data exists.

Automatically Manage Memory

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.

Compare Configurations

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.

Export Utility

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 12.2.1.2.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 veridata_scripting scripts.

Delta Processing

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.

Database Support Changes

  • 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.

Deprecated Parameters and Settings

This section lists the parameters and settings that are no longer used in this new release. These parameters are deprecated in the veridata.cfg file.

Corrected Problems

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:

Release 12.2.0.1.3 — December 2017

Bug 24517103— Silent installation of Domain in Oracle GoldenGate Veridata

The silent installation domain creation issue was fixed. The domain_silent.sh, which has is responsible for domain creation was introduced.

Bug 26223552— Silent Installation - RCU not detecting Oracle GoldenGate Veridata - component name is incorrect

The issue of missing component was fixed by adding the Veridata Repository component for Oracle GoldenGate while running Repository Configuration Utility (RCU).

BUG 26364205 - Veridata_import.sh script hung issue

The issue of Oracle GoldenGate Veridata Veridata_import.sh script hanging after Updating profiles in VERIDATA_server1-diagnostic.log was fixed by adding a new zlib.buffer.flush.size property file to the veridata.cfg file and agent.properties.sample file both on the server side as well as on the agent side. The default value is 1000000.

BUG 25462427 - Oracle GoldenGate Veridata compare fails java.lang.NullPointerException

The issue of a NullPointerException occuring while running the Compare Pair functionality was fixed by adding a check to read the buffer only when it has bytes in it. The exception occurred when there is no room to hold data chunks in a particular run leading to an empty or null buffer.

BUG 26787395 - Import.sh jobs validating at backend but at GUI it shows status unknown

When importing settings using the Veridata Import functionality, although the validation of compare pairs were successful, the actual status was not shown in UI. This issue was fixed by running Veridata_import.sh with proper compare pairs in the import file; on successful execution of the script, the correct validation status gets displayed on the UI.

BUG 26767803 - Very slow import of groups configuration

The issue of slow import of group configurations is fixed.

BUG 26008206 - Trying to do the pair configuration pegs CPU at 100%

The comparison of data replication issue is fixed by the usage of correct binaries.

Release 12.2.0.1.3 — October 2017

Bug 26307629 — CAGT - CAgent: Agent message (999): null 

The error message has been corrected. This can occur from the NSK agent when the table being evaluated has a large number of partitions.

Release 12.2.1.2.170515 — May 2017

Bug 25766243 - OGGV-50005: Unable to parse XML file 

Corrected an issue with the Veridata scripting export feature creating invalid an XML file when the compare-pair has column exclude and delta config elements enabled. 

Release 12.2.1.2.170215 — February 2017

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.

Release 12.2.1.2.0 — October 2016

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.

Release 12.2.1.0.0 ­— March 2016

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.

Release 12.2.1.0.0 ­— October 2015

Initial Release.

Known Issues and Workarounds

This section details the known issues and any workarounds for the Oracle GoldenGate Veridata Release 12c (12.2.1) release.

General Known Issues

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.

Database Related Issues

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

The INTERVAL, BIGINT, and 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 SMALLINT, INTEGER, and 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.

Upgrade Issues

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

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.

Using the Oracle GoldenGate Knowledge Base

To view the Oracle GoldenGate Knowledge Base, follow 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 Knowledge tab.

  4. 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.

  5. Under Task, select the type of query you want to make, such as Troubleshoot.

  6. Under Version, select the version of Oracle GoldenGate that you are using.

  7. 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.

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.

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.


Oracle GoldenGate Veridata Release Notes, 12c (12.2.1.2)

E78471-03

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.

This guide is intended for installers, database administrators, and system administrators who are installing, configuring and running Oracle GoldenGate.

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.

Accessible Access to Oracle Support

Oracle customers who 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.

The following text conventions are used in this document:

Convention Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, such as "From the File menu, select Save." Boldface also is used for terms defined in text or in the glossary.

italic

italic

Italic type indicates placeholder variables for which you supply particular values, such as in the parameter statement: TABLE table_name. Italic type also is used for book titles and emphasis.

monospace

MONOSPACE

Monospace type indicates code components such as user exits and scripts; the names of files and database objects; URL paths; and input and output text that appears on the screen. Uppercase monospace type is generally used to represent the names of Oracle GoldenGate parameters, commands, and user-configurable functions, as well as SQL commands and keywords.

UPPERCASE

Uppercase in the regular text font indicates the name of a utility unless the name is intended to be a specific case.

{ }

Braces within syntax enclose a set of options that are separated by pipe symbols, one of which must be selected, for example: {option1 | option2 | option3}.

[ ]

Brackets within syntax indicate an optional element. For example in this syntax, the SAVE clause is optional: CLEANUP REPLICAT group_name [, SAVE count]. Multiple options within an optional element are separated by a pipe symbol, for example: [option1 | option2].