内容发布更新时间 : 2024/5/2 9:42:18星期一 下面是文章的全部内容请认真阅读。

Oracle(r) GoldenGate Veridata Readme

11g Release 2 (11.2.1.0.0) December 2012

Oracle GoldenGate Veridata Readme for 11g Release 2 (11.2.1.0.0) Copyright (c) 2005, 2012, 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 software or related documentation is delivered to the U.S.

Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related

documentation and technical data delivered to U.S. Government customers are \pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the

restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software 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 which may

create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any

liability for any damages caused by use of this software in dangerous applications.

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 and documentation may provide access to or information on 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. 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.

Contents

Oracle GoldenGate Veridata 11g Release 2 (11.2.1.0.0) New Features

Support for Sybase and New DB2 Versions Oracle Query Hint

Security Support for the Oracle Wallet Simplified Access to Report Errors Server Consolidation Installer Enhancements

Support for Multibyte Object Names

Documentation Enhancements and Corrections Deprecated Parameters and Commands

server.nsort_compare_function_pool_size Sorting Retry Limit Sorting Retry Interval Documentation Addendum Installation and Upgrades

Installer 11.2.1 Enhancements Update Notes Known Issues

Oracle GoldenGate Veridata 11g Release 2 (11.2.1.0.0)

New Features

The following enhancements are included in Oracle GoldenGate Veridata 11g Release 2.

Support for Sybase and New DB2 Versions

The following databases are now supported for comparisons:

. Sybase 15.x which introduces support for string_NFC and SYBTIME. . DB2 LUW 9.7 which introduces a timestamp with the potential for picosecond precision if supported by the database. . DB2 z/OS 10

Oracle Query Hint

The user can define a hint that will be passed to the Oracle query

processor to help optimize a query. This can be defined for the Intial Compare and Confirm Out-Of-Sync categories in the Profile Settings of the Profile Configuration, Edit Profile screen.

Security Support for the Oracle Wallet

To standardize and improve the security of Oracle GoldenGate Veridata, the Oracle Wallet has been implemented for the storage of passwords. The implementation is done automatically by the install program. The changes include:

. A new vericom command that allows the repository password to be changed. On Windows:

Shell> vericom.bat -reset_password [password] On UNIX or Linux;

Shell> vericom.sh -reset_password [password]

If you do not enter a password on the command line, you will be prompted for one. After you enter a password, vericom connects to the database to verify that it is valid.

To activate the change, bring down the Oracle GoldenGate Web User Interface and restart.

. A requirement that the user backup the veridata_home/web/conf

directory prior to changing the server configuration or Tomcat users. Simplified Access to Report Errors

When the user hovers over a compare pair status icon, information is

displayed similarly to a tooltip. If there is an error, the error message is displayed; eliminating the need for the user to go to the report page for the comparison to see the error message. This is implemented only for completed comparisons. If there is no error, the status is displayed.

Server Consolidation

Changes were made to the Oracle GoldenGate Veridata services that include: . Replacement of the separate Oracle GoldenGate Veridata Server with Java based services managed by Tomcat.

. Replacement of the licensed Nsort product with internal sorting routines.

Installer Enhancements

The following new features and screens are now included in the installer program.

Assign User for Windows Service

If you are installing Oracle GoldenGate Veridata as a Windows service, you now identify the user that will start the service. A new installer screen allows you to select either:

. Logon as a Local System: Check this option to log on as LocalSystem when the service is started.

. Logon as a Specific User: Enter the user name and password to use to start the service. If you specify a user, that user must be granted LogonAsService privilege or the service will not start.

When you upgrade a system that is installed as a Windows service and

started by LocalSystem, a new screen is enabled. It gives you the option to identify a new login to start the service or continue as LocalSystem. If you specify a new login, that user must be granted LogonAsService privilege or the service will not start

Import Users during Installation

When running the installer to create a new 11.2.1.0 Oracle GoldenGate Veridata installation, a new screen allows you to specify how the Tomcat Oracle GoldenGate Veridata users will be created. You can choose to either:

. Use the Tomcat Web Service administrative tool to manually create users after the installation.

. Have the installation program import users from an existing Oracle GoldenGate Veridata installation.

If you elect to import the users, the next screen will ask you to enter the existing installation directory and the administrator's user name and password.

Support for Multibyte Object Names

In addition to supporting multibyte data, Oracle GoldenGate Veridata now supports multibyte object names, such as table, column, and compare pair names.

Note: If you use an Oracle or MySQL database as your repository, it must support storing these multibyte names.

Documentation Enhancements and Corrections

As of 11gR2, the Oracle GoldenGate Veridata Administrator's Guide is output as HTML as well as PDF. The formatting now conforms more closely to the Oracle standard.

Deprecated Parameters and Commands

server.nsort_compare_function_pool_size - This parameter, which set the size of the Nsort compare function pool, has been deprecated as of release 11.2.1.0.0.

Sorting Retry Limit - This parameter, which controlled the number of

times that a comparison was retried if the program could not reserve the amount of virtual memory that it needed, is deprecated as of release 11.2.1.0.0. This was set in the Oracle GoldenGate Web User Interface. Sorting Retry Interval - This parameter, which controlled the amount of time that a comparison waited between attempts to reserve virtual memory if the initial attempt fails, is deprecated as of release 11.2.1.0.0.

Documentation Addendum

This section serves as an addendum to the Oracle GoldenGate Veridata Administrator's Guide. It includes items that have not been covered in the guides due to changes made to the product or documentation after document publication.

There are no items that have been identified at this time as not covered in the online Help or the Oracle GoldenGate Veridata Administrator's Guide.

Installation and Upgrades

The installation file downloaded from Oracle is not compressed using gzip; instead it is a standard .zip file. To uncompress the download, please use the zlib ZIP utilities.

You can download the utility here: http://ftp.bsi2.com/pub/oss/ZIP.tar.Z Additional information on this utility can be found here: http://ftp.bsi2.com/pub/oss/ZIP.README

Oracle GoldenGate Veridata can be installed using a graphical installer or a command line installer. For detailed instructions on how to run

these installers see the Oracle GoldenGate Veridata Administrator's Guide.

Installer 11.2.1 Enhancements

Capability for 1) setting the user that will start Oracle GoldenGate Veridata as a Windows service and 2) importing users from an existing Oracle GoldenGate Veridata installation is included for the 11.2.1

release. Refer to the Installer Enhancements section for details on these new capabilities.

Update Notes

The following points highlight some of the considerations for updating your Oracle GoldenGate Veridata to the new 11.2.1 release. You should

refer to the update procedures in release 11.2.1 of the Oracle GoldenGate Veridata Administrator's Guide for details. . Java Requirements

Java 1.6.0 or later is required for release 11.2.1 Oracle GoldenGate Veridata agents. . New Properties

Several new properties are included in release 11.2.1. The new Oracle GoldenGate Veridata properties are handled by the upgrade. You will need to set the new JDBC driver property as explained in upgrade instructions in the Oracle GoldenGate Veridata Administrator's Guide. . JDBC Drivers

Check the JDBC driver jars that are included with the Oracle GoldenGate Veridata Agent installation. These jar files have changed for some databases.

For example, connections to Oracle databases now require ojdbc6.jar instead of ojdbc5.jar, so the property in the agent.properties file should be server.jdbcDriver=ojdbc6.jar. . Teradata

The Teradata driver is not included with the Oracle GoldenGate Veridata installation files, leaving it to the user to secure an appropriate

driver. Since 11.2.1 testing for Teradata used the 14.00.00.14 Teradata JDBC driver, it is recommended that you use this or a later version of the Teradata 14.00.xx.xx JDBC driver. . Upgrades from 3.0

An in-place upgrade to 11.2.1.0.0 from Oracle GoldenGate Veridata version 3 is allowed only if that version 3 has been upgraded to release 3.0, patch 3.0.0.11 and your Tomcat version is at least 5.5.35. To check your Tomcat version on UNIX/Linux: cd install_directory/web/bin

Then enter one of the following two commands, depending on the shell: Setenv JRE_HOME ../..jre Export JRE_HOME=../../jre ./version.sh

To check on Windows:

cd install_directory/web/bin set JRE_HOME=../../jre version.bat

Known Issues

Release 11gR1 (11.2.1.0.0) of Oracle GoldenGate Veridata:

. Does not automatically upgrade the Tomcat web server if upgrading from a version of Veridata prior to 3.0.11.2. To upgrade to the Tomcat server found in Veridata 11.2.1.0.0: stop Veridata, rename the Veridata root

directory, install the Veridata 11.2.1.0.0 to the original directory name, and copy specific files and directories from the old to the new installation. For details on this, see My Oracle Support document 1506992.1.

. Is not supported for Solaris 5.10 (32 bit) on i386. . Has the following issues:

. #13947797: On Linux 64 bit systems, there is a java issue that

interferes with the entry of passwords when running the installer. The work-around is to click the Next or Back button and then return to the

entry window and enter the password. The identifier of the java issue is SCIM-BUGS-2569128.

. #13948608: When upgrading Oracle GoldenGate Veridata, old files that contain passwords are not deleted. The names of these files fall into the range VERIDATA.001 to VERIDATA.999. The user should delete these files after testing has shown that the update was successful and the system is operating successfully.

. #14804397: The following fields that indicate the state of delta

processing are not being written to the Initial Compare section of the comparison report:

Delta Processing enabled Delta Processing base time

. #14809443: Oracle GoldenGate Veridata does not allow an Enscribe job to both 1) specify partitions and 2) use server sorting. However, Veridata does not generate an error when this is done. The agent ignores the partition, potentially transferring extra rows and causing Veridata to compare and report out-of-sync outside of the appropriate range.

. #15875098: When vericom runs a comparison for a compare-pair that has default partitions defined, and one of -pS, -pSq, -pSA1, -pSA2, -pSH1, -pSH2, -pT, -pTq, -pTA1, -pTA2, -pTH1, or -pTH2 is specified, the default partition defined on the opposite side is ignored.

For example, a compare-pair has a source default partition named

defPartition and a SQL WHERE clause 'COL1 < 100'. If vericom is used to run this compare-pair with '-pTq COL1 < 200', defPartition is not applied to the source side, but 'COL1 < 200' is applied to the target side. To work around this, force vericom to apply the default partition by specifying it explicitly. For the example above, specify vericom -pTq 'COL1 < 200' -pS defPart.