Oracle GoldenGate 11gR1 New Features Overview

Oracle GoldenGate 11gR1 New Features Overview 1 - 2

Oracle GoldenGate 11gR1
Oracle GoldenGate 11gR1 enables the exchange and manipulation of data at the transaction level among multiple, heterogeneous platforms across the enterprise. Its modular architecture gives you the flexibility to extract and replicate selected data records, transactional changes, and changes to DDL (data definition language) across a variety of topologies.

Oracle GoldenGate 11gR1 New Features Overview 1 - 3

Key Capabilities and Technology Differentiators
Oracle GoldenGate works in heterogeneous environments, across different databases and hardware types. Its modular architecture gives the user the flexibility to extract and replicate selected data records, transactional changes, and changes to DDL (data definition language) across a variety of topologies. Oracle GoldenGate further differentiates itself from other technologies with: • Performance – moving large volumes of data very efficiently while maintaining very low lag times/latency. • Extensibility and Flexibility – meeting a wide range of customer solutions and integration needs with an open, modular architecture. • Reliability – overall architecture is extremely resilient against potential interruptions and easy to recover.

Oracle GoldenGate 11gR1 New Features Overview 1 - 4

Oracle GoldenGate 11gR1 New Features
The new features introduced in Oracle GoldenGate 11gR1 are broken-up into four separate categories: platforms and infrastructure, performance, manageability, and flexibility. The subsequent lessons cover these features in further detail.

Oracle GoldenGate11gR1 New Features Overview 1 - 5

Oracle GoldenGate11gR1 New Features Overview 1 - 6

Oracle GoldenGate 11gR1 New Features Overview .

Oracle GoldenGate 11gR1 New Features Overview 2 .2 .

Oracle GoldenGate11gR1 New Features Overview 2 .3 .

Oracle GoldenGate 11gR1 New Features Overview 2 .2 Oracle GoldenGate 11gR1 provides support for the latest version of the Oracle database providing the same heterogeneous capabilities as with previous versions of the Oracle database.0.4 .Oracle Database 11.2.

Oracle GoldenGate11gR1 New Features Overview 2 . To overcome the limitations of conventional storage. Oracle Exadata Storage Servers use a massively parallel architecture to dramatically increase data bandwidth between the database server and storage.Oracle Exadata Storage Server Oracle Exadata Storage Servers combine Oracle's smart storage software and Oracle's industry-standard Sun hardware to deliver the highest industry's highest database storage performance.5 .

6 .MySQL Oracle GoldenGate 11gR1 now offers extended support for MySQL. In this version.1. logbased Capture from MySQL 5.15 or later is supported (Delivery does not have this restriction) and is achieved by natively reading and parsing the MySQL transaction logs. Oracle GoldenGate11gR1 New Features Overview 2 .

Oracle GoldenGate11gR1 New Features Overview 2 .7 .

8 .Oracle GoldenGate11gR1 New Features Overview 2 .

9 .Oracle GoldenGate11gR1 New Features Overview 2 .

10 . there is one new requirement for the installation for 2008 when the user that issues the INSTALL ADDSERVICE ADDEVENTS command from the dos prompt. However.SQL Server 2008 Oracle GoldenGate 11gR1 now offers extended support for Microsoft database versions by adding log-based Capture to the current Delivery support of SQL Server 2008. Oracle GoldenGate11gR1 New Features Overview 2 . similar to the functionality for SQL Server 2000 and 2005. The standard TRANDATA is sufficient. there is no need to setup Microsoft SQL Server replication components such as distributer database and publisher. Finally. This is achieved by scraping the logs to capture the changed data. they must be logged in as the Admin user.

Oracle GoldenGate11gR1 New Features Overview 2 .11 .

12 .Oracle GoldenGate11gR1 New Features Overview 2 .

Oracle GoldenGate11gR1 New Features Overview 2 .13 .

14 .Oracle GoldenGate11gR1 New Features Overview 2 .

Oracle GoldenGate11gR1 New Features Overview 2 .15 .

16 .Oracle GoldenGate11gR1 New Features Overview 2 .

Oracle GoldenGate11gR1 New Features Overview 2 .17 .

18 .Oracle GoldenGate11gR1 New Features Overview 2 .

Oracle GoldenGate 11gR1 New Features Overview .

Oracle GoldenGate 11gR1 New Features Overview 3 .2 .

3 .Oracle GoldenGate11gR1 New Features Overview 3 .

no matter how many open (uncommitted) transactions there were at the time that Extract stopped. NOTE: Before modifying this parameter from its default settings.Bounded Recovery A new Bounded Recovery feature has been added that guarantees an efficient recovery after the Extract stops for any reason. nor how old they were. Bounded Recovery sets an upper boundary for the maximum amount of time that it would take for Extract to recover to the point where it stopped and then resume normal processing.4 . Oracle GoldenGate 11gR1 New Features Overview 3 . it is highly recommended to contact Oracle support for guidance. planned or unplanned.

Oracle GoldenGate11gR1 New Features Overview 3 .5 .

For Oracle Databases 10g and later. Oracle GoldenGate11gR1 New Features Overview 3 .Reduce LOB Fetching LOB capture differs between earlier and later versions of the Oracle database. all LOBs are captured from the redo log. whether they are stored in-row or out-of-row (some exceptions may apply).6 . all in-row LOBs are captured from the redo log but out-of-row LOBs are fetched from the database. In Oracle Database versions earlier than 10g.

Oracle GoldenGate11gR1 New Features Overview 3 .7 .

New in Oracle GoldenGate 11g.8 . the default connection from Replicat uses OLE DB to connect to the target database (instead of ODBC).Microsoft OLE DB OLE DB is an API designed by Microsoft for accessing different types of data stored in a uniform manner. Oracle GoldenGate11gR1 New Features Overview 3 .

9 .Oracle GoldenGate11gR1 New Features Overview 3 .

Oracle GoldenGate11gR1 New Features Overview 3 . since it prevents duplicate operations. the following concerns must be addressed for their effect on data integrity: • IDENTITY seeds on the target are not updated. so data integrity cannot be certain on the target. • CHECK constraints are not enforced. ON DELETE CASCADE and triggers are disabled. This is beneficial to Replicat. • ON UPDATE CASCADE.Emulating a Replication User OLE DB can be configured to use the replication user by using the DBOPTIONS parameter with the USEREPLICATIONUSER option. • Foreign key constraints are not enforced.10 . When the replication user is used. but may not be appropriate for the target applications and might require modification to the code of the constraint or trigger to ensure data integrity. A partitioning scheme is needed to avoid primary key violations unless the target is read-only.

11 .Oracle GoldenGate11gR1 New Features Overview 3 .

Oracle GoldenGate11gR1 New Features Overview 3 .12 .

using DYNSQL offers the best efficiency and most throughput. Oracle GoldenGate11gR1 New Features Overview 3 . However.Dynamic SQL Dynamic SQL is a programming technique that enables a user to build SQL statements dynamically at runtime. In Oracle GoldenGate. there may be some circumstances where NODYNSQL proves to be faster and more efficient. With DYNSQL (default value).13 . In most environments. the DYNSQL and NODYNSQL parameters are used to control the way that SQL statements are formed. Replicat uses dynamic SQL to compile a statement once and then execute it many times with different bind variables. With NODYNSQL. Replicat uses literal SQL statements with the bind variables resolved.

14 .Oracle GoldenGate11gR1 New Features Overview 3 .

Oracle GoldenGate 11gR1 New Features Overview .

2 .Oracle GoldenGate 11gR1 New Features Overview 4 .

Oracle GoldenGate11gR1 New Features Overview 4 .3 .

4 . The value of this parameter can be changed so that Replicat can work within existing application timeouts and other database requirements on the target database. To verify if Replicat is currently backing out a timed-out transaction. you can use the following command: GGSCI> SEND REPLICAT group. STATUS Performing transaction timeout recovery Waiting for data at logical EOF after transaction timeout recovery Oracle GoldenGate 11gR1 New Features Overview 4 .Long-Running Transactions The TRANSACTIONTIMEOUT parameter prevents an uncommitted Replicat target transaction from holding locks on the target database and consuming its resources unnecessarily.

Replicat remembers the position in the trail of the beginning of the first sources transaction in the current transaction. When TRANSACTIONTIMEOUT is enabled.5 . Oracle GoldenGate 11gR1 New Features Overview 4 . in case the transaction must be abended or retried. Replicat also saves the position of the first record of the current source transaction and will use that position as the logical end-of-file (EOF) if it is triggered.TRANSACTIONTIMEOUT Parameter During normal operations.

6 . lightweight and robust manner. in a flexible.Activity Logging The Activity Logging subsystem is a set of software components that record application activity in a variety of formats. Information captured by the Activity Logging API is used to diagnose normal application processing and new program logic under development. Oracle GoldenGate 11gR1 New Features Overview 4 . It can also provide additional details when application operation fails unexpectedly.

Schema Modifications If the DDL has changed in a heterogenous replication environment. Oracle GoldenGate11gR1 New Features Overview 4 . then the target side sourcedefs files must be modified to continue .7 .

8 .Oracle GoldenGate11gR1 New Features Overview 4 .

Oracle GoldenGate 11gR1 New Features Overview .

Oracle GoldenGate 11gR1 New Features Overview 5 .2 .

3 .Oracle GoldenGate11gR1 New Features Overview 5 .

4 .Oracle GoldenGate11gR1 New Features Overview 5 .

5 .Oracle GoldenGate11gR1 New Features Overview 5 .

6 . The example above shows how MAPSESSIONSCHEMA works to allow the mapping of a source session schema to another schema on the target.DDL Enhancements: Mapping Schemas The MAPSESSIONSCHEMA parameter enables a source session schema to be mapped to a different session schema on the target. The following DDL capture and mapping configurations are for Extract and Replicat. Oracle GoldenGate11gR1 New Features Overview 5 .

7 . A new UPDATEMETADATA option of the DDLOPTIONS parameter notifies Replicat on the system where DDL originated that this DDL was propagated to the other system. Oracle GoldenGate11gR1 New Features Overview 5 . This keeps Replicat's metadata cache synchronized with the current metadata of the local database. and that Replicat should now update its object metadata cache to match the new metadata.DDL Enhancements: Active-active Bi-Directional Configuration Oracle GoldenGate 11gR1 offers support for DDL in an active-active bi-directional configuration. This is for the Oracle platform only.

To use this option.Suppressing Triggers and Cascading Deletes The SUPPRESSTRIGGERS parameter prevents triggers from firing on target objects that are configured for replication with Oracle GoldenGate. the Replicat user must be an Oracle Streams administrator which can be granted by invoking dbms_goldengate_auth.grant_admin_privilege.8 . This alleviates the need to manually disable triggers and constraints. Oracle GoldenGate11gR1 New Features Overview 5 .

9 .Oracle GoldenGate11gR1 New Features Overview 5 .

Oracle GoldenGate11gR1 New Features Overview 5 .10 .

Oracle GoldenGate11gR1 New Features Overview 5 .11 .

Oracle GoldenGate11gR1 New Features Overview 5 .12 .

Oracle GoldenGate 11gR1 New Features Overview .

2 .Oracle GoldenGate 11gR1 New Features Overview 6 .

3 . LOBSALWAYSNOINDEX sets LOB replication to ALWAYS_REPLICATE (which always replicates the LOB data whether or not it has changed in a transaction).New Oracle GoldenGate 11gR1 GGSCI: Trandata Commands For Sybase. Note that all of the correct options are set by default. LOBSALWAYSNOINDEX does not mark the table to use an index on replication which provides the following benefit of no lock being held while ADD TRANDATA is being executed. the LOBs argument controls how the database propagates LOB data for the specified table. Oracle GoldenGate11gR1 New Features Overview 6 .

4 .New Oracle GoldenGate 11gR1 GGSCI: Miscellaneous Commands A new ALLOWNESTED command enables the use of nested OBEY files. A nested OBEY file is one that contains another OBEY file. Oracle GoldenGate11gR1 New Features Overview 6 . An attempt to run a nested OBEY file in the default mode of NOALLOWNESTED will cause an error.

Oracle GoldenGate11gR1 New Features Overview 6 . or any combination of those types When you use SYSLOG in the GLOBALS parameter file. the Manager setting overrides the GLOBALS setting for the Manager process. warning. This parameter is available to both the GLOBALS parameter file and/or Manager parameter file. it controls message filtering for all of the Oracle GoldenGate processes on the system.5 . This enables you to use separate settings for Manager and all of the other Oracle GoldenGate processes. or error messages. If used in both the GLOBALS and Manager parameter files. When it appears in a Manager parameter file.New Oracle GoldenGate 11gR1 GLOBALS Parameters SYSLOG filters the types of Oracle GoldenGate messages that are written to the system logs. it controls messages filtering only for the Manager process. you can: • • • include all Oracle GoldenGate messages suppress all Oracle GoldenGate messages filter to include information. With SYSLOG.

Oracle GoldenGate11gR1 New Features Overview 6 . it is highly recommended to contact Oracle support for guidance. It guarantees an efficient recovery after Extract stops for any reason. NOTE: Before modifying this parameter from its default settings. planned or unplanned. no matter how many open (uncommitted) transactions there were at the time that Extract stopped.New Oracle GoldenGate 11gR1 Extract: Tuning Parameters Bounded Recovery is a component of the general Extract checkpointing facility. See Lesson 3: Performance Enhancements for additional information.6 . nor how old they were.

New Oracle GoldenGate 11gR1 General Parameter Syntax Updates Use the COMPRESSUPDATES and NOCOMPRESSUPDATES parameters for Extract to control the way columns are written to the trail record fro update operations. This becomes the default when a table definition does not include a primary key or unique index. NOCOMPRESSUPDATES sends all of the columns to the trail. while restricting the amount of data that must be processed. Oracle GoldenGate11gR1 New Features Overview 6 . This provides enough information to update the correct target record. causes Extract to write only the primary key and the changes columns of a row to the trail for update operations. COMPRESSUPDATES and NOCOMPRESSUPDATES apply globally for all TABLE statements in a parameter field. the default. DBOPTIONS • CONNECTIONPORT <port>: Valid for Replicat for multi-daemon MySQL. COMPRESSUPDATES.7 . Specifies the TCP/IP port.

grant_admin_privilege. which can be granted by invoking dbms_goldengate_auth. USEREPLICATIONUSER enables the SQL Server NOT FOR REPLICATION flag. LOBWRITESIZE <bytes>: Valid for Replicat for Oracle. The replication user is not a SQL Server user or account. USEREPLICATIONUSER: (Valid for Replicat for SQL Server) Configures Replicat to perform target DML operations as the SQL Server replication user. To use this option. Prevents triggers from firing on target objects that are configured for replication with Oracle GoldenGate. writing in larger blocks prevents excessive I/O. The higher the value.New Oracle GoldenGate 11gR1 General Parameter Syntax Updates (cont).8 . The LOB data is stored in a buffer until this size is reached. The default is to use OLE DB. Not valid if USEREPLICATIONUSER is enabled.5 and later patches. If used with an Oracle version that does not support this functionality. You can use this parameter for Oracle 10. Because LOBs must be written to the database in fragments. • • • • • • Oracle GoldenGate11gR1 New Features Overview 6 . the fewer I/O calls that are made by Replicat to the database server to write the whole LOB to the database.2. • DEFERREFCONST: Valid for Replicat for Oracle. This argument determines the memory buffer size to allocate for each embedded LOB attribute that is in an Oracle object type. Note: Replicat always uses ODBC to connect to the database catalog to obtain metadata. The default is NOSUPPRESSTRIGGERS.0. and for Oracle 11. CONNECTIONPORT <port>: Valid for Replicat for multi-daemon MySQL. DEFERREFCONST will be ignored without returning a notification to the GoldenGate log.7 and later. but is a property of the database connection. SUPPRESSTRIGGERS | NOSUPPRESSTRIGGERS: Valid for Replicat for Oracle. Delays referential integrity constraint checking and enforcement by the database until the Replicat transaction is committed.0.0. instead of manually disabling the triggers.2 and later. See Lesson 3: Performance Enhancements for additional details. This argument determines the memory buffer size to allocate for each embedded LOB attribute that is in an Oracle object type. Specifies the TCP/IP port. will cause Replicat to abend.2. LOBBUFSIZE <bytes>: Valid for Extract for Oracle. the Replicat user must be an Oracle Streams administrator. Specifies a fragment size for each LOB that Replicat writes to the target database. USEODBC: (Valid for Replicat for SQL Server) Configures Replicat to use ODBC to perform DML operations.2. You can use this parameter instead of disabling the constraints on the target tables if the database is Oracle version 9.

consult the Oracle GoldenGate Windows and UNIX Reference Guide version 11gR1 (11. update supplemental logging for tables that are renamed.1).1. Use ADDTRANDATA to: - enable Oracle’s supplemental logging automatically for new tables created with a CREATE TABLE. update supplemental logging for tables where unique or primary keys are added or dropped. to update supplemental logging for tables affected by an ALTER TABLE to add or drop columns. For a more detailed look into the other arguments.9 .New Oracle GoldenGate 11gR1 General Parameter Syntax Updates DDLOPTIONS • ADDTRANDATA [ABEND | RETRYOP <RETRYDELAY <seconds> MAXRETRIES <retries>]: Valid for Extract (Oracle and Teradata). Oracle GoldenGate11gR1 New Features Overview 6 .

New Oracle GoldenGate 11gR1 General Parameter Syntax Updates (cont). Forces the schema of an unqualified object in the Replicat DDL statement to be that of the Replicat session schema. PASSWORD ENCRYPTKEY [ DEFAULT | ENCRYPTKEY <keyname>]: • • To use the encryption options. Oracle GoldenGate11gR1 New Features Overview 6 . On the target. and that Replicat should now update its object metadata cache to match the new metadata. . . .10 . Wildcards are not supported.DEFAULT specifies that the passwords were encrypted by using a random key generated by Oracle GoldenGate. Enables a source session schema to be mapped to (transformed to) a different session schema on the target.ENCRYPTKEY <keyname> specifies that passwords were encrypted with a userdefined method and specifies a lookup key in an ENCKEYS file on the target system. instead of the schema in an ALTER SESSION SET CURRENT_SCHEMA statement. the password is decrypted automatically without requiring an ENCKEYS file. You can use multiple MAPSESSIONSCHEMA parameters to map different schemas. Directs Extract to encrypt all passwords in source DDL before writing the DDL to the trail. you must first generate the encrypted password with the ENCRYPT PASSWORD command in GGSCI. MAPSESSIONSCHEMA <source_schema> TARGET <target_schema>: MAPSESSIONSCHEMA overrides any mapping of schema names that is based on master or derived object names.<target_schema> is the session schema that is set with ALTER SESSION set CURRENT_SCHEMA on the target. • Valid for Extract for Oracle. . Use in an active-active bidirectional configuration.<source_schema> is the session schema that is set with ALTER SESSION set CURRENT_SCHEMA on the source. • Valid for Replicat (Oracle only). This keeps Replicat’s metadata cache synchronized with the current metadata of the local database. This parameter notifies Replicat on the system where DDL originated that this DDL was propagated to the other system. PASSWORD ENCRYPTKEY [ DEFAULT | ENCRYPTKEY <keyname>]: Valid for Replicat (Oracle only). For more information about Oracle GoldenGate encryption options. USEOWNERFORSESSION: Valid for Replicat (Oracle only). which is the default behavior. see the Oracle GoldenGate Windows and UNIX Administrator’s Guide.

. Override in regular mode: Use COMPLETEARCHIVEDLOGONLY to force Extract to wait until an archived log is completely written to disk before beginning to read it. Override in ALO mode: Use NOCOMMPLETEARCHIVEDLOGONLY to force Extract to start processing an archived log immediately when it becomes available.11 . Default in archived log only (ALO) mode: Forces Extract to wait for the complete archived log to be written to disk. without waiting for it to be written to disk. Oracle GoldenGate11gR1 New Features Overview 6 .Default in regular mode: Extract starts processing an archived log immediately when it becomes available.New Oracle GoldenGate 11gR1 General Parameter Syntax Updates TRANLOGOPTIONS • COMPLETEARCHIVEDLOGONLY: (Oracle) Overrides the default Extract processing of archived logs.

0. NODDLCHANGEWARNING will prevent those messages from accumulating in the Oracle GoldenGate log. then the last 500MB. Some DDL changes do not cause Extract to abend. If Extract begins reading at the first byte. and finally the middle 1000MB. This API uses the database server to access the redo and archive logs. DBLOGREADERBUFSIZE <buffer size>: (Oracle) Specifies the size of the read buffer that Extract uses when capturing from an Oracle ASM instance when DBLOGREADER is being used. The maximum buffer size when using the default OCI buffer is 1024000 bytes. The default is 1024000 bytes. so it expects source and target metadata to remain constant. than what you specify for DBLOGREADERBUFSIZE. it will abend when it reaches the break in the byte sequencing. • This parameter applies when copying production (source) archive logs to a secondary database where they will serve as the data source. Some Oracle programs do not build the archive log from the first byte to the last byte in sequential order. The default behavior (without this parameter) is to capture Oracle direct-load INSERTs. DBLOGREADER: (Oracle) Causes Extract to use a newer API that is available as of Oracle 10.2. DBLOGREADER enables Extract to use a read buffer size of up to 4 MB in size. but instead may copy the first 500MB. so that the problem can be corrected. for example. When using a buffer size that is larger than 1024000. so that they do not have to reside in ASM. but the warning still will be logged whenever such changes occur. • • • • Oracle GoldenGate11gR1 New Features Overview 6 .New Oracle GoldenGate 11gR1 General Parameter Syntax Updates (cont). This option applies to Oracle logs with log compatibility of Oracle 10g or later. When used. or larger. NODDLCHANGEWARNING: (SQL Server) Forces Extract not to log a warning when a DDL operation is made to a source object for which Extract is capturing data. Oracle GoldenGate does not support DDL capture and replication for SQL Server. You can use the DBLOGREADERBUFSIZE option to specify a buffer size. SKIPDIRLOADINSERT: (Oracle) Causes Extract to skip all Oracle direct-load INSERTs. The default is to report a warning. The database must contain the libraries that contain the API modules and must be running. Specify a buffer of up to 4MB. Waiting for the whole file to be written prevents this problem. A larger buffer may improve the performance of Extract when redo rate is high. you must change the BUFSIZE parameter to a value that is equal to.12 .5.

Oracle GoldenGate11gR1 New Features Overview 6 .13 .

Oracle GoldenGate11gR1 New Features Overview 6 .14 .

Oracle GoldenGate 11gR1 New Features Overview .

2 .Oracle GoldenGate 11gR1 New Features Overview 7 .

issue the following command until you see a message that there is no more data to process: INFO REPLICAT <group> Oracle GoldenGate11gR1 New Features Overview 7 .3 .1 of Oracle GoldenGate into a new directory by following the directions for a new installation for your database and platform. This procedure creates a new DDL environment.1.4 Perform the following steps to upgrade an Oracle GoldenGate 10. Install v11.1. 2.1: 1. stop DDL activity on the source database and allow Replicat to apply the changes that are in the trail to the target. See the installation instructions for your supported database. You do not need to create the subdirectories. To preserve the continuity of source and target structures. To determine when Replicat is finished. You only need to complete the steps to the point where the programs have been expanded. (Oracle source database if using DDL replication) There are numerous changes to the DDL triggers and objects that need to be rebuilt.Upgrading to Oracle GoldenGate 11gR1 from Oracle GoldenGate 10.4 instance to Oracle GoldenGate 11gR11. but removes DDL history.

Upgrading to Oracle GoldenGate 11gR1 from Oracle GoldenGate 10. (Oracle source database if using DDL replication) Follow the instructions in “Rebuilding the DDL environment” on slide 10 and then return to the follow steps. and then the Manager process. Start all of the Oracle GoldenGate processes. 5. 6. starting with Extract and Replicat processes.4 (cont). Stop all of the Oracle GoldenGate processes. and then Extract and Replicat. Move the files and programs that you expanded from your new directory into your existing Oracle GoldenGate directory.4 . starting with Manager. GGSCI> STOP EXTRACT <group> GGSCI> STOP REPLICAT <GROUP> GGSCI> STOP MANAGER 4. 3. GGSCI> START MANAGER GGSCI> START EXTRACT <group> GGSCI> START REPLICAT <GROUP> Oracle GoldenGate11gR1 New Features Overview 7 .

5 and earlier (for upgrading specifically on z/OS.1.1. Oracle GoldenGate11gR1 New Features Overview 7 . Install v11. You do not need to create the subdirectories.4 Perform the following steps to upgrade the target database only from an Oracle GoldenGate v10.1 of Oracle GoldenGate into a new directory by following the directions for a new installation for your database and platform.4 and to Oracle GoldenGate v9. See the installation instructions for your supported database. there are some additional steps that may be required.x prior to 10. Remove the CACHESTATEMENTS option of BATCHSQL if being used in the Replicat parameter file.5 . 2. You only need to complete the steps to the point where the programs have been expanded.Upgrading to Oracle GoldenGate 11gR1 from Version(s) Prior to Oracle GoldenGate 10. Stop Replicat and then Manager: GGSCI> STOP REPLICAT <GROUP> GGSCI> STOP MANAGER 3. Reference Upgrading to Oracle GoldenGate v11g Release 1 (11.1)): 1.

Move the files and programs that you expanded from your new directory into your existing Oracle GoldenGate directory.6 . 5.Upgrading to Oracle GoldenGate 11gR1 from Version(s) Prior to Oracle GoldenGate 10.4 (cont). Start Manager and then Replicat: GGSCI> START MANAGER GGSCI> START REPLICAT <GROUP> Oracle GoldenGate11gR1 New Features Overview 7 . 4.

You do not need to create the subdirectories.4 Perform the following steps to upgrade an Oracle GoldenGate 10.1. (Oracle source database if using DDL replication) There are numerous changes to the DDL triggers and objects that need to be rebuilt. This procedure creates a new DDL environment. To preserve the continuity of source and target structures.4 instance to Oracle GoldenGate 11gR11.Upgrading to Oracle GoldenGate 11gR1 from Oracle GoldenGate 10.1: 1. but removes DDL history. You only need to complete the steps to the point where the programs have been expanded.1. 2. stop DDL activity on the source database and allow Replicat to apply the changes that are in the trail to the target. To determine when Replicat is finished. See the installation instructions for your supported database.7 .1 of Oracle GoldenGate into a new directory by following the directions for a new installation for your database and platform. issue the following command until you see a message that there is no more data to process: INFO REPLICAT <group> Oracle GoldenGate11gR1 New Features Overview 7 . Install v11.

Start all of the Extract and data-pump groups: GGSCI> START EXTRACT <group> Oracle GoldenGate11gR1 New Features Overview 7 .5 | 10. starting with Extract and Replicat processes. OSS. This includes the online Extracts and initial-load Extracts. Remove the TRANSMEMORY parameter from any Extract parameter file. 7. and then the Manager process. Move the files and programs that you expanded from your new directory into your existing Oracle GoldenGate directory. A new Oracle GoldenGate trail header was added in v10.4} 10. 8.1. GGSCI> START MANAGER 9. (Oracle source database if using DDL replication) Follow the instructions in “Rebuilding the DDL environment” on slide 10 and then return to the follow steps. GGSCI> STOP EXTRACT <group> GGSCI> STOP REPLICAT <GROUP> GGSCI> STOP MANAGER 4. Start only the Manager process.8 . This ensures that the trails that the new version of Oracle GoldenGate writes are backwards compatible with the downstream Oracle GoldenGate environments and that the downstream Replicats can process the data. and z/OS. ETROLLOVER 11. 3. This applies to all platforms except NonStop. In order to switch to this new format successfully. If not upgrading the target to v11.Upgrading to Oracle GoldenGate 11gR1 from Oracle GoldenGate 10. Stop all of the Oracle GoldenGate processes.1.4 (cont). 6. Remove the CACHESTATEMENTS option of BATCHSQL if being used in the Replicat parameter file. RMTTRAIL <trail> FORMAT RELEASE {9. 5. modify the Extract that is sending data to the target (usually a data pump but could be the primary Extract) to include the FORMAT RELEASE option in the RMTTRAIL parameter. you must roll over each trail with the following command to all of the appropriate Extract and data-pump groups: ALTER EXTRACT <group>.0 | 9.

Oracle GoldenGate11gR1 New Features Overview 7 .9 .

Rebuilding the DDL Environment to a Clean State For Oracle databases, to completely remove, and then reinstall, the Oracle GoldenGate DDL object in preparation for an upgrade to Oracle GoldenGate v11.1.1, perform the following steps: 1. After stopping the source Oracle GoldenGate processes, change directories to the Oracle GoldenGate installation directory. 2. Run SQL*Plus and log in as a user that has SYSDBA privileges. 3. Disable all sessions that ever issued DDL. Otherwise the database might generate an ORA-04021 error. 4. Run the ddl_disable script to disable the DDL trigger. 5. Run the ddl_remove script to remove the Oracle GoldenGate DDL trigger, the DDL history and marker tables, and other associated objects. This script produces a ddl_remove_spool.txt file that logs the script output and a ddl_remove_set.txt file that logs current user environment settings in case they are needed for debugging.

Oracle GoldenGate11gR1 New Features Overview 7 - 10

Rebuilding the DDL Environment to a Clean State (cont). 6. Run the marker_remove script to remove the Oracle GoldenGate marker support system. This script produces a marker_remove_spool.txt file that logs the script output and a marker_remove_set.txt file in case they are needed for debugging. 7. Run the marker_setup script to reinstall the Oracle GoldenGate marker support system. You will be prompted for the name of the Oracle GoldenGate schema. 8. Run the ddl_setup script. You will be prompted for: - The name of the Oracle GoldenGate DDL schema. - The installation mode. Use the INITIALSETUP mode. This mode drops and recreates existing DDL objects before creating new objects. 9. Run the role_setup script to recreate the Oracle GoldenGate DDL role. 10. Grant the role you just created to all Oracle GoldenGate users under which the following Oracle GoldenGate processes run: Extract, Replicat, GGSCI, and Manager. You might need to make multiple grants if the processes have different user names. 11. Run the ddl_enable.sql script to enable the DDL trigger. 12. Return to the upgrade procedure that you were following.

Oracle GoldenGate11gR1 New Features Overview 7 - 11

Oracle GoldenGate11gR1 New Features Overview 7 - 12

Oracle GoldenGate11gR1 New Features Overview 7 .13 .

Oracle GoldenGate 11gR1 New Features Overview .

Oracle GoldenGate 11gR1 New Features Overview 8 .2 .

3 .Oracle GoldenGate 11gR1 New Features Overview 8 .

4 .Property Templates to Use with Flat File A new flat file writer property. {writer}.template. Oracle GoldenGate11gR1 New Features Overview 8 . This property specifies the name of the template of typical properties that is to be used for that flat file writer. has been added for the implementation of property templates.

Oracle GoldenGate11gR1 New Features Overview 8 . If the user hasn't specified it. For each property in the template. The template settings can be overridden by setting the property in the properties file. the system first checks to see if that property is set in the properties file itself.Property Templates The property templates presets certain properties based on common usage.5 . the template setting is used.

Oracle GoldenGate writes directly to the underlying database tables without creating the log entries.Siebel Remote Support When Oracle GoldenGate is used with Siebel applications.6 . Oracle GoldenGate for Flat File 11gR1 writes transactions to a set of rolling files in a specific format understood by the Siebel DMUTL tool. Only changes made through the Siebel application server are written to the remote log. Oracle GoldenGate11gR1 New Features Overview 8 . remote users do not see changes made to Siebel by Oracle GoldenGate.

afterfirst .A flat file writer output format added for Siebel remote integration that specifies a hexadecimal value as the byte order marker (BOM) to be written to the beginning of the file. Oracle GoldenGate11gR1 New Features Overview 8 . files. groupcols .data.datetime.removecolon .userexit.code .7 .A flat file writer output format property added for Siebel remote integration that controls whether or not the column names. before values and after values are grouped together. the date and time column values are written to the output files in the default format of the Oracle GoldenGate trail.A general property added for • • Siebel remote integration that controls whether or not a colon is written between the date and time. YYYYMMDD:HH:MI:SS. When set to false.A flat file writer data content property added for Siebel remote • integration that controls whether or not the after image is written before the before image when includebefores is set to true.FFFF.Siebel Remote Support • goldengate.bom.

This is required when accumulating the number of operations in a transaction.userexit. Oracle GoldenGate11gR1 New Features Overview 8 .buffertxs=true . The quote policy will be applied. • begintx.metacols.8 . The following metadata columns have also been added: • %COLNAME – The value in the named column.metacols . endtx. • “<value>” – Any literal. These marker records are written (with end of line delimiters) to the output files before and after the operation records that make up the transaction.A general property added for Siebel remote integration that specifies that the transactions are to be buffered in memory.Two flat file writer metadata column • properties added for Siebel remote integration that specify the metadata columns to use to mark the beginning and end of a transaction. • numops – The number of operations in the current transaction.Siebel Remote Support (cont). • numcols – The number of columns to be output. goldengate.

rollover.rollover.The rollover may be based on a specific time. Oracle GoldenGate11gR1 New Features Overview 8 .9 . This is enabled using the new files.Files may be rolled over based on the Julian commit timestamp.data.timetype parameter. • Rollover at a specified time .data.rollover.attime parameter. This is enabled using the new files. This is enabled using the new files.Flexible File Rollover There are three different rollover settings that can be used: • Rollover based on commit timestamp .multiple parameter. • Synchronized rollover of multiple files .data.All currently open files may be rolled over at the same time.

policy.datatypes – Only specific data types are quoted • dsv. Oracle GoldenGate11gR1 New Features Overview 8 . or datetime data types are to be quoted when dsv.Quote Policy Enhancements Two new properties allow the user to specify certain criteria on data types that are placed in quotes: • dsv.default – Only dates and chars are quoted .always – All metadata columns and column values are quoted .datatypes – Controls whether integer.quotes.never – No metadata column or column values are quoted .quotes. float. character.10 .policy is set to datatypes.policy – Controls the policy for applying quotes by allowing the user to select from the options: .quotes.

11 .Oracle GoldenGate11gR1 New Features Overview 8 .

Oracle GoldenGate11gR1 New Features Overview 8 .12 .

13 .Oracle GoldenGate11gR1 New Features Overview 8 .

Oracle GoldenGate11gR1 New Features Overview 8 .14 .

It creates a normalized definition of tables based on the property settings and other parser-specific data definition values.15 .Source and Target Definitions Oracle GoldenGate for Java includes a Gendef utility that generates an Oracle GoldenGate source definitions file from the properties defined in a properties file. Oracle GoldenGate11gR1 New Features Overview 8 .

16 .Oracle GoldenGate11gR1 New Features Overview 8 .

17 .Oracle GoldenGate11gR1 New Features Overview 8 .

Sign up to vote on this title
UsefulNot useful