You are on page 1of 13

Oracle® GoldenGate Patch Set Notes

11.2 for Oracle GoldenGate

Oracle® GoldenGate
Patch Set Notes

11.2 for Open GoldenGate

May 2012

These patch set notes accompany the Oracle GoldenGate 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.

2 Critical Patch Updates

Review the latest Critical Patch Updates, and recent change list, please read
the Release Notes.

The following parameters will need to be correctly set in the environment in order to capture or apply data to the proper database. 5 Preinstallation Tasks 5. and in the way the some parameters function. $ORACLE_HOME = the Oracle software installation directory. AIX references LIBPATH environment variable. $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. HPUX references SHLIB_PATH environment variable.2 Oracle Dynamic Build Installation Oracle GoldenGate for Oracle builds can now be downloaded using dynamic linked libraries instead of static linked libraries. Before upgrading to 11.1 Review Known Preinstallation Issues There are many changes in default parameters. The following list highlights the significant changes that you will encounter before or during the upgrade process. Dynamic linked library applications require the library paths to be set up correctly so that the application knows where to find them.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. 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. 5. Please follow the procedures at the site to ensure correct installation or upgrade.2 you may need to modify your EXTRACT or REPLICAT parameter files. .

4 or greater for the V12 family. OGG Does not support Sybase versions prior to 15. please use the updated ODBC drivers whenever connecting to a Teradata environment:  Use ODBC driver version 3.0. 5.2 family. or greater for the TTU 8.0.sun.3 ESD#4. 5. Due to this issue.0. the patch 119963-15 should be applied.4 Sybase 15 Support OGG for Sybase 15 requires Sybase The patch for Solaris 10 is here: http://sunsolve.  Use ODBC driver version 12. there is a known memory leak that could affect our product and cause Extract to Abend. Tru64 and LINUX references LD_LIBRARY_PATH environment variable. If this is a brand new environment that does not have Oracle .6. We recommend that customers apply a Solaris patch to their systems. Contract your Oracle Administrator for details on where the proper Oracle libraries are located.  Use ODBC driver version 13. Based on the information below. The library path must be correctly configured to point to the proper libraries for the version you will be capturing from.6 SQL Server 2005 CU6 Upgrade / Installation changes In Cumulative Update 6 for SQL Server 2005. the build from Oracle GoldenGate may not completely address the problem.x.3 and ESD#4 patch applied. BUG ID: 6514832 libumem complains on redzone violation in std::deque even with 119963-08 This patch for Solaris 9 is here: http://sunsolve.0.2 or greater for the V13 Microsoft has enabled new functionality that will allow Oracle GoldenGate to capture from tables without primary 5.3 Oracle on Solaris In Solaris 9 and Solaris 10 environments.5 Teradata ODBC Driver Update Due to Oracle GoldenGate improvements for Teradata.sun.

even with CU6.) If you have SQL Server Native Replication for other objects of the database you cannot have Oracle GoldenGate replicate tables without primary keys. 5. so please plan appropriately. Select Yes. Skip ahead to Instruction 8. 1. (Note: It does require downtime. 8. 6. Perform the SQL Server 2005 upgrade to CU6 or higher. 3. There is no need to use any of aspects of Microsoft’s native Replication.GoldenGate already installed. Stop Extract 4. expand the instance. only remove the Oracle GoldenGate Publication. In SQL Server Management Studio. Expand the Replication folder and the Local Publications folder. 9. c. this removes all publications for all databases in the instance). If SQL Native Replication is in use for any database in the Instance. Adding supplemental logging on these tables will cause the native SQL Server replication to stop working. b. 2. and are planning on upgrading your SQL Server 2005 environment to CU 6 or higher. you must use the SQL Server 2000 installation / upgrade instructions in the Oracle GoldenGate Installation Guide for SQL Server. 7. Ensure that the source database is quiesced and there are no further transactions to process. disable publishing on this server to remove the distributor database and any publications for the SQL Server instance (Note. a. Delete the GoldenGate Publication. Select Finish to complete the steps. Right-click the Replication folder and then select Disable Publishing and Distribution. . please follow this procedure. Ensure that Oracle GoldenGate Capture is reading the current log position and that all open transactions have been committed and Captured. If you already have Oracle GoldenGate installed.

this means that the files must have the "a" extended attribute. and iteration of the publication as in server/instance-database_SRC-1. Optionally. For USS. These include the following: o Agent history clean up: <Distributor database name> o Distribution clean up: <Distributor database name> o Expired subscription clean up o Reinitialize subscriptions having data validation failures o Replication agents checkup 6.7 DB2 z/OS Library Considerations The installation documentation is incorrect. Re-Issue ADD TRANDATA for all tables to be Captured. Start application/user activity. If you previously had Microsoft native replication for use with Oracle GoldenGate. the ADD Trandata commands add jobs with names based on the server. Start Extract. and “tar xvpf” should be used for expanding the tarball instead of "tar xvf" (the "p" option causes the . 3. Right-click the Replication folder and then select Distributor Properties. This will delete all local publications. Click Publishers 4. instance. 5. expand the instance 2. 10. 1. The Authorized Program Facility (APF) requires that all modules dynamically loaded by an APF-authorized program must come from APF-authorized sources. These can also optionally be deleted. Uncheck the publication. In SQL Server Management Studio. 11. database name. Additionally.1 uses some "International Components for Unicode" code which is packaged as several Dynamic Load Libraries (DLLs). you can use these steps to remove it. Oracle GoldenGate 11. 12. 5. the jobs setup in the SQLAgent for native replication can be deleted.

2.3 RDBMS.05 or newer aC++ libraries.10 Integrated Extract database requirements In order to use the new Integrated Extract functionality.2.3 xlC.0 COMMITTED XL C/C++ Runtime for AIX 5. Oracle GoldenGate requires aCC: HP aC++/ANSI C B3910B A.0.9 HP-UX aC++ Requirements On HP-UX 11.en_US. 13560925 is the bug number for the patch that should be downloaded from support.extended attributes to be restored on specific library files required to run Oracle GoldenGate). .rte 8.msg. Bug 12425035 .5.blr backport of bug 10406642 on top of 11. 5.06.2.rte 8. 5.2.0 COMMITTED XL C/C++ Runtime Installed libraries can be found using the following command from a shell prompt: lslpp -l | grep -i xlc For TDE/TSE support if you get the following error ( MISSING ROUTINE 'ZTVP52') you will also need to apply the following Oracle RDBMS BLR’s.8 AIX Minimum Library Requirements Some versions of AIX 5.3) should be used.0. The tracking bug number for Exadata 11203 bundled patch 3 is 13556853. the following database patches will need to be applied to the Oracle 11.2.blr backport of bug 10406642 on top of 10.0 COMMITTED XL C/C++ Runtime xlC.0.0 (blr #577148) do not have the latest runtime libraries required by Oracle GoldenGate. For Exadata 11.3_BP3 patch (11.0 (blr #577146) Bug 12425039 .2.aix50. Please make sure the following minimums are met: xlC. If the user who expands the tarball does not have z/OS authorization to add the "a" extended attribute.0.3. PHSS_34041 or newer is required. someone who is authorized must add the attribute using "extattr +a extract *dll". For non-Exadata *nix platforms.23 IA64.rte 8.3 databases. the EXADATA_11.0.

64bit Windows tracking bug for this 2nd patchset is 13555974 32bit Windows tracking bug for this 2nd patchset is 13555973 6 Installation Tasks Please follow the Installation and Upgrade Instructions for 11. port 7870: did not recognize command (G).5 server/collector proceeds as if the unrecognized . 7 Known Issues Review the following known issues after you apply the patch set:  General  Oracle DDL  Oracle  SQL Server  DB2 (z/OS and Windows and UNIX)  Teradata  TimesTen  Sybase  MySQL  C-tree  SQL/MX” means that the 9. the checkpoint may require older archive logs to be present in order to process the data. Windows platforms.0. the MLR tracking bug 13560925 is expected to be in the 2nd patchset for Windows on top of 11.2 located in a separate document. Please be aware that the Bounded Recovery files in versions of OGG prior to 11.2. and upon restart of Extract.2.1 are not compatible with those in 11.1 General  The warning “GGS WARNING 250 GoldenGate Collector.

command didn't happen.0 will not work on Oracle 10. Please refer to bug ticket 12742927. let “. This fix can be requested via an SR. . This includes DB2 (LUW. or HP-UX IA64 (non-Oracle) environments at this time. ‘.  DDLCOMMENTS may not work when there is a special non-alphanumeric character in the comments.SQL script. Additionally the SPNAME may not be fully qualified in DB2 z/OS v10.SQL script that was include with 11.2 Oracle DDL  Wide Characters are not supported in DDL operations. Oracle GoldenGate uses the entire value in the where clause.  The AES encryption options are not supported on AIX (Oracle). and this could prevent the record from being found. (12550561)  DDL Replication with OGG 11. 7. (9475275)  Using _ALLOWWILDCARDSCHEMAS is not compatible with THREADS >= 1. Please contact support for the correct DDL_SETUP. It could create files that are unreadable by Oracle Support and development teams.  When mapping numeric data in a key column from a column that has more precision to a column that has less precision.  SQLEXEC does not support multibyte stored procedure or queries in ODBC databases. z/OS and iSeries) as well as Teradata and PostgreSQL.  User tokens may truncate timestamp values depending on the amount of significant digits and accuracy in the source and target databases. This is just a warning message and will not cause any problems with replication. ).  Unclosed comments in DDL operations may cause replicat to abend. etc. and extract proceeds with the assumption that the target doesn't support the new 10. There is a problem with object size resolution that can cause issues with certain data types being the incorrect size which causes the trail file to become unreadable.1.1 on HP-UX should be disabled. This would include UTF16 environments where multiple bytes are used to store single byte values. (9841878)  Password changes required when a password expires do not cause DDL operation and it will be skipped.0 trail file headers.1. the update or delete statement may fail. (11771481)  The DDL_SETUP. Please do not enable DDL replication on that platform.  BINARYLAYOUT should not be used with the new tracing functionality.1.  If replicating BINARY_DOUBLE or BINARY_FLOAT please use SOURCEDEFS (mapping done in Replicat) and not TARGETDEFS.  Fetching in DB2 and Sybase may not work correctly if multiple rows require fetching in the same transaction.1. (13776169). (.2.

UTF8.x.2.2.EMP: ORA-24816: Expanded non LONG bind data supplied after actual LONG or LOB column. DDL replication can be used to capture truncates on empty tables.x and higher. this means that table-level truncates cannot be processed reliably.1. (9430534)  TRACETABLE functionality does not support TRUNCATE TABLE commands. 2005-08-04 11:02:24 GGS WARNING 218 SQL error 24816 mapping SCOTT. If not. This was fixed in Oracle 11. This means that Oracle GoldenGate cannot propagate truncate operations on empty tables. write the data to a trail first and then use Replicat to generate the files needed for the load.2.3 Oracle  EXCLUDEUSER and EXCLUDEUSERID may not function correctly if a trigger is on the table that is being captured.  FORMATXML does not accept the ORACLE and NONAMES parameters. . INT and SMALLINT. tables. There is a bug (9149420) in the Oracle database that causes the owner of the operation to be changed to the owner of the trigger in the redo log record. even if GETTRUNCATES is specified. The GETTRUNCATES parameter only supports truncates for tables.  The archive log directories must be different when using Oracle GoldenGate for Oracle RAC in ALO mode.0.0.  There is a problem using an Oracle GoldenGate direct bulk load (using the BULKLOAD parameter for Replicat and loading directly to SQL*Loader) with LOB or XMLType data that is larger than 2000 bytes.7. For this reason. For partitioned tables. Instead. It is related to decimal precision for numeric types INTEGER. as of Oracle 10.2. If desired. Similarly.  If the error below is received when the server character set is UTF8. non- partitioned. Extract may return “out of order scn” errors. Table-level truncates are not propagated if the table contains ANY empty partitions. or an ORA-01438: value larger than specified precision allowed for this column.  There is a known bug with Oracle that fetching of CLOBS > 256kb from a compressed securefile will fail. it could be related to SR 3- 1128784511.7 and higher. DDL replication can be used to capture truncates on partitioned tables that may include empty partitions.EMP to JOHN.  There is a known performance issue that can cause extract to lag behind if it is capturing a lot of changes from IOT objects with Overflow tables. See the Oracle GoldenGate documentation for more information about initial load methods. (Ticket 9427379)  As of Oracle 10. truncate operations are not logged for individual empty partitions.2. This issue is fixed in Oracle 11.x.  Extract does not support RECOVERY_PARALLELISM > 1.0. GETTRUNCATES should NOT be used on partitioned tables in Oracle versions 10.0. you will need to set the NLS_LANG to AMERICAN_AMERICA. Truncates against individual partitions are only supported using DDL replication options. truncate operations are not logged on empty. and this issue is fixed in Oracle release 11. The Oracle bug # is 7171015.  If Replicat fails on MAPPING ERROR 213.0.2. If desired.

 Oracle GoldenGate will issue an error and abend if a timestamp column is part of a key.  There is a known bug (ID 8769746) in OCI that can cause CHAR datatypes to appear as a variable length data type.  Extract does not support direct load operations on IOTs.  To support RMAN log retention on Oracle RAC.  There is a platform specific issue on Linux 64bit with Oracle 11g that causes the EVENTACTIONS (SHELL) to fail. please use the FETCHPARTIALXML parameter when capturing XMLType data. or Striped backups. You must bounce Extract in order for it to continue reading the redo logs from the remaining nodes.  When Extract is at the logical end of the redo logs in Oracle RAC.  XML data type support in Oracle 11g requires patch 11.  Oracle GoldenGate does not support Append.0.  In windows environments.  Oracle GoldenGate does not support external XML objects.  DML operations created through the use of /*+PARALLEL */ hints in RAC environments are not supported with Classic Extract. If this occurs in your environment.  SECUREFILE LOBS in Oracle 11g should be using FETCHMODCOLS on those columns to force a fetch of these datatypes. NCHAR.1. In order to resolve this issue. XMLType.7 to be applied to fix an XML streaming issue.4 SQL Server  Oracle GoldenGate cannot capture or deliver data to Windows Authenticated Owned tables. please modify the client SQLNET. and a node is shutdown using SHUTDOWN IMMEDIATE or SHUTDOWN NORMAL it will not continue processing data.  GEORASTER objects are not supported in this build. This reason is detailed in NOTE 951654.1. (13945299) 7. please use SOURCEDEFS or TARGETDEFS to work around the issue or apply the database patch to prevent the issue from occurring. BugDB 12642592. . This includes situations where a unique key is not present.  There is a known limitation that Oracle GoldenGate does not support nested XML data inside of XML fields. or NVARCHAR2 data types.ORA file and include bequeath_detach=true.  In some cases replicat may fail when apply LOB updates on a partitioned table with row movement enabled.  In addition to the documented limitations of SQLEXEC in the OGG Reference Guide. SQLEXEC does not support User Defined Data types (including SDO_GEOMETRY and GEO_RASTER). you must download and install the database patch that is provided in BUGFIX 11879974 before you add the Extract groups.

5 and above (for Teradata 13) and GG v11.1 or above.  SQL Server internal System tables and catalog tables cannot be replicated.  Extract core dumps when using both TRANLOGOPTIONS and EXCLUDEUSER parameters simultaneously.5 DB2 (z/OS and Windows and UNIX)  DDLGEN for DB2 on z/OS does not work correctly with NULL/NOT NULL constraints and TIMESTAMP datatypes. Moreover.  If the DATEFORMAT is anything other than ‘ymd’. mgr.odbc. 7. This is because the Replicate uses the ANSI standard format of ‘yyyy-mm-dd’  SQL Server Extract is not properly ignoring transactions with the ggs_repl on them. all object names should be in single-byte characters  Sortranlog extract abends when using KEYCOLS.  FORMATXML and FORMATASCII do not work correctly with DATE or TIMESTAMP datatypes.  VALUE COMPRESSION and TABLE COMPRESS options are not supported. please make sure to change it to DATEFORMAT to ‘ymd’.0.  GGSCI on z/OS now requires 48MB of memory instead of 8MB.5 or 13. such as TRANLOGOPTIONS REQUIRELONGDATACAPTURECHANGES. To have it ignore them.0.6 Teradata  Moving multi-byte data is only supported between identically configured Teradata systems (identical character sets). On Windows there are no limitations but on linux environments you must use TD ODBC 12. you must also define the full path location of the . please set any TRANLOGOPTIONS setting.prm: fcntl failure closing files” message is just an informational message and can be ignored.  Oracle GoldenGate supports remote delivery to a DB2 z/OS target utilizing DB2Connect from a server with DB2 LUW 9.x installed. If you are on Linux SLES or RHAS.0. This can be done in the parameter file by adding the line SQLEXEC “SET DATEFORMAT ‘ymd’” after the TARGETDB parameter in the REPLICAT parameter file. KEYCOLS should NOT be used in the Sortranlog extract in Teradata in v10. .0. On Windows and linux you must set the ODBC driver and the TAM should be set to UTF16 character set.  Compressed SQL Server 2008 backups are not supported  CLR and CLR based types like hierachyID and spatial are not supported  Transparent Data Encryption is no supported  Columnsets are not supported  Filestreams in 2008 are not supported 7.ini file via the ODBCINI environment variable.  The “GoldenGate Manager for DB2.

 When Server OS is UTF-8 (LANG=en_US. (OS-4600)  Encrypted data is not supported.10 C-tree  No known issues 7. use the “!” option of DELETE REPLICAT. Therefore. even using FETCHCOLS or FETCHMODCOLS.0.0.9 MySQL  In order to delete a MySQL Replicat that uses a checkpoint table. including BINARY and VARBINARY. ADD CHECKPOINTTABLE gives error message "ERROR: failed to create checkpoint table" but checkpoint table is successfully created. In such a situation. If the source and target table structures are not identical. as in “DELETE REPLICAT REP_TEST !”  Precision errors can occur when replicating data to MySQL because it is not dynamic SQL due to floating point limitations.7 TimesTen  None 7. there's a possible mismatch during mapping which would result in data integrity issue. VAMCOMPATIBILITY 1 7. this release will guarantee correct mapping only on identical source and target table structures.8 Sybase  The Sybase Replicat does not support Primary Keys that contain the binary data types. 7. use: TRANLOGOPTIONS COMMITTEDTRANLOG.  When setting up the Extract for Teradata Max Performance mode. restartappend TRANLOGOPTIONS VAMCOMPATIBILITY 1 or TRANLOGOPTIONS COMMITTEDTRANLOG. in order to support Sybase 15. 7.11 SQL/MX .UTF-8).3 or later. The work around is to execute command "info checkpointtable" first then "add checkpointtable" (FPA-3857)  There is a limitation on data mapping when dealing with more than 1 LOB columns. and these features we are requiring all Sybase customers to apply patch 15. restartappend.  Many OGG features in Sybase require support for Decimal.  TEXT and BLOB datatypes are not supported in SQLEXEC.  Array fetching for initial loads is not working properly.

HP ticket #10-090318-8875). the only Interval data type supported is Month & Day to Second. The source target SYSKEY value cannot be forced on the Target.  Extended NUMERIC data type is not currently supported  Interval data types cause unreliable replicat behavior  SQL/MX v3 ODBC driver does not allow catalog and/or schema names longer than 73 characters. This is an HP issue that has been logged with them (OS- 8839.  Certain GGSCI commands are timing out when trying to communicate with certain processes.  Outstanding HP Issues regarding SQL/MX and Oracle GoldenGate. . No Forced SYSKEY capabilities when applying to the Target. In this release.  ASSUMETARGETDEFS is not supported by SQL/MX EXTRACT.  Partial Interval Data type Support. HP ticket #10-070402-9249). This means that the SYSKEY will be automatically assigned on the Target and will not be the same value as the Source. This capability is not currently provided with the HP ODBC client.  TMFARLIB can return out of order records if the customer is using AUX Audit trails (OS-8812.  SQL/MX v3 ODBC driver will not behave predictably with anything other than unquoted uppercase catalog/schema names in the DSN. There is a current bug in the HP ODBC client that does not support the population of Interval datatypes (HP ticket # 10-070723-6463). o No Population of Interval Datatypes. Please use SOURCEDEFS instead.