12c (12.1.3)
E50475-05
 Home |  Contents |  Contact Us |
Go to main content
| Oracle® GoldenGate Veridata Release Notes 12c (12.1.3) E50475-05 |
|
| PDF · Mobi · ePub |
Release Notes
12c (12.1.3)
E50475-05
December 2015
This document describes the new features, major changes, and the known issues in Oracle GoldenGate Veridata Release 12c (12.1.3).
This release note contains the following sections:
This section summarizes the new features and significant product changes for Oracle GoldenGate Veridata in 12c (12.1.3) release.
Oracle GoldenGate Veridata Release 12c (12.1.3) includes the following new and changed features.
Oracle GoldenGate Veridata now supports the use of the Informix Dynamic Server (IDS) database in the 12.1.3.0.1 release.
The new heterogeneous Repair feature in Veridata updates the target database and facilitates in repairing the out-of-sync data in live environments. For more information, see "Repairing out-of-sync Jobs" in Oracle GoldenGate Veridata User's Guide.
The new Scripting tool allows you to bypass the interface and bulk load comparison configurations from an XML file directly into the Oracle GoldenGate Veridata repository. This reduces the time required to define repetitive tasks, create re-usable configurations and ensures that the test configuration mirrors the production environment. For more information, see Chapter 5, "Using the Veridata Scripting Utility" in Administering Oracle GoldenGate Veridata.
The Oracle GoldenGate Veridata 12.1.3 provides IPv6 support for java agents.
The Purging feature helps you remove unwanted job reports and data to keep the disk size and report volume in control. For more information, see Oracle GoldenGate Veridata Online Help.
Oracle GoldenGate Veridata 12.1.3 supports Single Sign-on (SSO) mechanism for authentication. To configure SSO, you should set the SSO properties for Veridata Server and configure the logout URL for the SSO session. For more information, see Section 1.2, "Configuring Single Sign-on for Oracle GoldenGate Veridata" in Administering Oracle GoldenGate Veridata.
Oracle GoldenGate Veridata 12.1.3 supports the following security enhancements:
Support for Secure Sockets Layer (SSL) Communication - Oracle GoldenGate Veridata supports both Secure Sockets Layer (SSL) and plain socket communication between the Veridata Server and multiple Veridata Agents that are connected over a network. For more information, see Section 2.2, "Configuring an SSL Connection between Veridata Server and Veridata Agents" in Administering Oracle GoldenGate Veridata.
Added new security roles to Oracle GoldenGate Veridata users - You can assign security roles to the users of Oracle GoldenGate Veridata to control their access to the functions that are performed by the software, some of which expose selected data values from the database. For more information, see Section 2.4, "Securing Access to Oracle GoldenGate Veridata Web Interface by Defining User Roles" in Administering Oracle GoldenGate Veridata.
Oracle GoldenGate Veridata provides you with an option to encrypt the comparison report files (.rpt, .oos, .oosxml). For more information, see Section 2.5, Encrypting Report Files, in Administering Oracle GoldenGate Veridata.
Oracle GoldenGate Veridata has been using Tomcat Version 5.5.X as its web server. From this release, Oracle GoldenGate Veridata uses Oracle Universal Installer (OUI) to install and configure the Oracle WebLogic Server domain that hosts the Veridata. For more information on Oracle universal installer, see Installing and Configuring Oracle GoldenGate Veridata.
The Oracle GoldenGate Veridata documentation library has been reorganized and improved as follows:
New library pages - The documentation library is organized in a task-based structure to make it easier to locate information about the task or feature. The familiar listing by book is also available under the Books tab.
New Guides - New guides are added to the Oracle GoldenGate Veridata 12.1.3 documentation library.
Administering Oracle GoldenGate Veridata - This document describes how to deploy and administer Oracle GoldenGate Veridata.
Installing and Configuring Oracle GoldenGate Veridata - This document describes how to use the Oracle GoldenGate Monitor and Veridata installation program to install and configure Oracle GoldenGate Veridata.
Upgrading Oracle GoldenGate Veridata - This document describes how to upgrade an existing Oracle GoldenGate Veridata 11g (11.2.1) environment to 12c (12.1.3).
Veridata User's Guide - This document describes the features of Oracle GoldenGate Veridata Web User Interface.
This section lists the parameters that are no longer used in this new release. These parameters are deprecated in the veridata.cfg file.
server.persistence_db_type
server.persistence_db_name
server.persistence_db_port
server.persistence_db_username
server.persistence.oracle.tns_admin
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 21687175 - Finished job - view by job just hangs
An issue with the Finished Jobs page taking too much time to load when Veridata repository contains too much data was fixed.
Bug 21899828 - Implicitly Veridata Data Type Conversion Leads Slow SQL Plan
An issue with Veridata using timestamp mapping for DATE column was fixed.
Bug 19277798 - Translating database characters based on DB settings and not app settings
The raw bytes are retrieved from the database and used to specify the character set used to decode the data before encoding it as UTF-8 for comparison.
Bug 20664517 - Veridata column validation on DB2 for i fails FILE not found.
The schema used to query the SYSCOLUMNS view was corrected.
Bug 19662941 - Bytes on Out of Sync Details page not being populated
The number of out-of-sync and repaired bytes was corrected and the values are displayed in the UI.
Bug 20456834 - The Veridata schema release checks do not work
The repository schema version is now checked during application initialization and an error occurs when with attempts to access an invalid release.
Bug 20488347 - Move jelly SQL scripts to a JAR file instead of copying files directly
The jelly scripts have been moved to single JAR file and the path to this new file was added to the manifest of rcu_veridata.jar.
Bug 20562546 - The Veridata server is corrupting COOS lookup messages
The confirm-out-of-sync (COOS) records are now thread safe.
Bug 20089668 - Veridata repair fails repair fetch query failed on unsupported data conversion
The repair fetch query was modified to use the correct JDBC method for the data type and the requested conversion.
Bug 20063478 - Veridata repair apply failed: code: 17003, msg: 'Invalid column index'
The repair method was modified to accept trailing spaces in VARCHAR columns.
Bug 19649778 - JAVA heap error on comparison of table with more than 158 columns
A missing attribute in the logon request sent to the Veridata Agent was added.
Bug 19604515 - Comparison would occasionally hang
The comparison job functionality was modified to handle incomplete compressed messages.
Bug 19649778 - Java heap error on comparison of table with more than 158 columns
The fetch-batch-size attribute is now included in the logon request sent to the Veridata Agent to avoid OutOfMemoryError errors.
Initial Release.
The following sections describe the known issues in Oracle GoldenGate Veridata 12c (12.1.3) release:
This section lists the general known issues in Oracle GoldenGate Veridata 12c release.
Section 5.1.3, "Missing Error Messages for Jobs that Fail Early"
Section 5.1.4, "Unable to Delete Connections with Multibyte Connection Names"
Section 5.1.6, "Veridata Incorrectly Reports Out-Of-Sync Rows for XML Type Content"
Section 5.1.7, "Oracle User Defined Nested Table Comparison gives False Results"
Section 5.1.9, "Cannot Disable Triggers on Sybase Database for Repair Jobs"
The Progress DataDirect Connect Series Open Database Connectivity drivers do not support the use of INTERVAL, BIGINT, or BIGSERIAL functions with Informix databases.
The Veridata Agent may fail with an OutOfMemoryError when tables are defined with numerous VARCHAR2 (4000) columns. The fetch-batch-size attribute is now included in the logon request sent to the Veridata Agent.
When a job is submitted, its completion status is saved in report files and repository. However, if a job fails too early before it is successfully submitted there is no message displayed on the UI or in any repository records. For example, if the configuration file veridata.cfg contains an invalid character for the report file path, and if you run a job from the UI, then no report files or repository record is created. The job terminates without throwing any error message.
Using the Veridata Web User Interface, if you create a new connection with a multibyte connection name and if the Veridata installation uses Oracle database as the repository, then after altering the default character set, connection name is displayed incorrectly in the existing connection list. But such connections cannot be deleted from the UI.
Test to Production (T2P) repository migration scripts are not available for non-oracle databases. Oracle GoldenGate Veridata 12c (12.1.3) provides repository data migration scripts only for Oracle database. For more information, see section "Moving from a Test to Production Environment" in Administering Oracle GoldenGate Veridata.
When the source and target database have different character sets, Veridata reports out -of-sync records for XML type content.
As a workaround, create views to select data in the same format on source and target databases and run Veridata comparison job on these views. For more details, see Doc ID 1633756.1 on My Oracle Support at: https://support.oracle.com.
When Oracle User Defined (UDT) nested table columns are compared in Oracle GoldenGate Veridata 12c, it incorrectly reports in-sync and out-of-sync rows.
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.
For Repair jobs, Veridata allows you to disable triggers for the database by setting a value for the Disable DB Triggers Session Based option in the user interface. However, this option does not work as expected for Sybase database.
This section lists the configuration issues in Oracle GoldenGate Veridata 12c release.
If you are using a non-oracle database as the Veridata repository, you should create the WebLogic domain by using the vdtCreateCompactDomain script provided with the Veridata 12c (12.1.3) installation. For more information, see "Configuring a Compact Domain for MYSQL and MSSQLSERVER Databases" in Installing and Configuring Oracle GoldenGate Veridata.
After running this script, no log files are created. All details are displayed on the console.
Oracle JRockit JVM is not supported in Oracle GoldenGate Veridata 12c (12.1.3) release. Install JDK 1.7.0_15 on the machine where you run Veridata instance and set JAVA_HOME and PATH environment variables with the JDK 1.7 path. For more information, see section 2.2.1 "Install JDK 1.7 on the Target Machine" in Installing and Configuring Oracle GoldenGate Veridata.
This section lists the upgrade issues in Oracle GoldenGate Veridata 12c release.
Section 5.3.1, "Veridata 11g Reports are Not Copied to 12c WebLogic Domain after Upgrade"
Section 5.3.2, "Veridata 11g Users are not Migrated to 12c WebLogic Domain after Upgrade"
When you upgrade Veridata from 11g (11.2.1) to 12c (12.1.3), user reports are not copied to the new webLogic domain but the users can access the old reports. For more information, see "Verifying Veridata Report Files" in Upgrading Oracle GoldenGate Veridata.
Oracle GoldenGate Veridata 11g (11.2.1) users will not be migrated to 12c (12.1.3) WebLogic domain after the upgrade. You should create users using WebLogic Server Administration console as described in section "Securing Access to Oracle GoldenGate Veridata by Defining User Roles" in Administering Oracle GoldenGate Veridata.
The Online Help in the Run Options dialog on the Repair Jobs page contains wrong field descriptions.
To learn about the settings on this dialog, see Online Help for the Repair section in the Edit Profile Settings page.
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.To view the Oracle GoldenGate Knowledge Base, follow these steps:
Go to http://support.oracle.com.
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:
Go to http://support.oracle.com.
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 http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
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.1.3)
E50475-05
Copyright © 2013, 2015, 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.