Oracle GoldenGate 11.1.1 patch set

Oracle(r) GoldenGate Patch Set Notes 11.1 for Oracle GoldenGate Oracle(r) GoldenGate Patch Set Notes 11.1 for Open GoldenGate August 2010 These patch set notes accompany the Oracle GoldenGate 11.1.1 patch set. This document contains the following sections: * Patch Set Overview * Critical Patch Updates * Accessing the Latest Version of this Document * System Requirements * Preinstallation Tasks * Installation Tasks * Known Issues 1 Patch Set Overview Patch sets are a mechanism for delivering fully tested and integrated product fixes. Patch sets provide bug fixes only; they do not include new functionality and they do not require certification on the installed system. Patch sets include all of the libraries that have been rebuilt to implement the bug fixes in the set. All of the fixes in the patch set have been tested and are certified to work with each other. Because the patch set includes only low impact patches, it does not require you to certify applications or tools against the server. You can apply the Oracle GoldenGate release 11.1.x patch set to any Oracle GoldenGate 11.1.x installation. 2 Critical Patch Updates Review the latest Critical Patch Updates, and recent change list, please read the Release Notes. 3 Accessing the Latest Version of this Document The latest version of this document can be found on Oracle's Support site. 4 System Requirements Check your platform-specific installation guide for a list of supported operating systems. 5 Preinstallation Tasks Complete the following preinstallation tasks before installing the patch set: * Review Known Preinstallation Issues * Oracle Dynamic Build Installation * Oracle on Solaris * Oracle DDL Replication * Teradata ODBC Driver Update * SQL Server 2000 Non-Native SQL Server driver requirements * SQL Server 2005 CU6 Upgrade / Installation changes * DB2 z/OS Library Considerations * COMPRESSEDUPDATE changes for DB2 LUW, DB2 z/OS, and SQL Server * AIX Minimum Library Requirements * Oracle Virtual Machine Policy * HP-UX aC++ Requirements 5.1 Review Known Preinstallation Issues There are many changes in default parameters, and in the way the some parameters function. Before upgrading to 11.1 you may need to modify your EXTRACT or REPLICAT parameter files. Please follow the documented Installation and Upgrade instructions for this release. The installation and upgrade procedures for Windows are documented on the support download site. Please follow the procedures at the site to ensure correct installation or upgrade. The following list highlights the significant changes that you will encounter before or during the upgrade process. 5.2 Oracle Dynamic Build Installation Oracle GoldenGate for Oracle builds can now be downloaded using dynamic linked libraries instead of static linked libraries. Dynamic linked library applications require the library paths to be set up correctly so that the application knows where to find them. The following parameters will need to be correctly set in the environment in order to capture or apply data to the proper database. $ORACLE_HOME = the Oracle software installation directory. $ORACLE_SID = the instance GGS is connecting to $LD_LIBRARY_PATH = the location to the Oracle Library files (or the correct library path environment variable from below) $PATH= needs to include the Oracle bin path For each OS platform the load library path variable used to resolve library references can be different when executing the GGS software. AIX references LIBPATH environment variable. HPUX references SHLIB_PATH environment variable. SUN, Tru64 and LINUX references LD_LIBRARY_PATH environment variable. The library path must be correctly configured to point to the proper libraries for the version you will be capturing from. Contract your Oracle Administrator for details on where the proper Oracle libraries are located. 5.3 Oracle on Solaris In Solaris 9 and Solaris 10 environments, there is a known memory leak that could affect our product and cause Extract to Abend. Due to this issue, the build from Oracle GoldenGate may not completely address the problem. We recommend that customers apply a Solaris patch to their systems. Based on the information below, the patch 119963-15 should be applied. BUG ID: 6514832 libumem complains on redzone violation in std::deque even with 119963-08 http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6514832 The patch for Solaris 10 is here: http://sunsolve.sun.com/search/document.do?assetkey=1-21-119963-15-1 This patch for Solaris 9 is here: http://sunsolve.sun.com/search/document.do?assetkey=1-21-111712-23-1 5.4 Oracle DDL Replication The DDL trigger has been modified with this release. Please rebuild the DDL trigger using the method outlined in the Oracle GoldenGate Administration Guide in the Configuring DDL Synchronization chapter. 5.5 Teradata ODBC Driver Update Due to Oracle GoldenGate improvements for Teradata, please use the updated ODBC drivers whenever connecting to a Teradata environment: * Use ODBC driver version 3.6.0.5 or greater for the TTU 8.2 family, V2R6.x. * Use ODBC driver version 12.0.0.4 or greater for the V12 family. * Use ODBC driver version 13.0.0.2 or greater for the V13 family. 5.6 SQL Server 2000 Non-Native SQL Server driver requirements In order to use the non-Native SQL Server ODBC client for Oracle GoldenGate, you will need to make sure that a patch is applied to SQL Server first. This patch is publicly documented in 950565. The patch can be downloaded here: FIX: Error message when you insert data to a table that contains two image columns by using the SQL Server ODBC driver: "[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid locator de- referenced" Windows XP Service Pack 2, x86-based versions File name File version File size Date Time Odbcbcp.dl l 2000.85.1133. 0 24,576 28-Mar- 2008 13:5 4 Sqlsrv32.dl l 2000.85.1133. 0 442,36 8 28-Mar- 2008 13:5 4 Windows XP Service Pack 3, x86-based versions File name File version File size Date Time Odbcbcp.dl l 2000.85.3000. 0 24,576 28-Mar- 2008 13:4 7 Sqlsrv32.dl l 2000.85.3000. 0 442,36 8 28-Mar- 2008 13:4 7 5.7 SQL Server 2005 CU6 Upgrade / Installation changes In Cumulative Update 6 for SQL Server 2005, Microsoft has enabled new functionality that will allow Oracle GoldenGate to capture from tables without primary keys. If this is a brand new environment that does not have Oracle GoldenGate already installed, you must use the SQL Server 2000 installation / upgrade instructions in the Oracle GoldenGate Installation Guide for SQL Server. There is no need to use any of aspects of Microsoft's native Replication. If you already have Oracle GoldenGate installed, and are planning on upgrading your SQL Server 2005 environment to CU 6 or higher, please follow this procedure. (Note: It does require downtime, so please plan appropriately.) If you have SQL Server Native Replication for other objects of the database you cannot have Oracle GoldenGate replicate tables without primary keys, even with CU6. Adding supplemental logging on these tables will cause the native SQL Server replication to stop working. 1. Ensure that the source database is quiesced and there are no further transactions to process. 2. Ensure that Oracle GoldenGate Capture is reading the current log position and that all open transactions have been committed and Captured. 3. Stop Extract 4. In SQL Server Management Studio, expand the instance. 5. If SQL Native Replication is in use for any database in the Instance, only remove the Oracle GoldenGate Publication. a. Expand the Replication folder and the Local Publications folder. b. Delete the GoldenGate Publication. c. Skip ahead to Instruction 8. 6. Right-click the