Create the Replicated Tables

29-8 Oracle® Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator See Working with Changed Data Capture in the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator for more conceptual information and detailed instructions on CDC.

29.3.5 Configure and Start Oracle GoldenGate Processes

The JKM generates in the LOCAL_TEMP_DIR a folder named after the source and target object groups. This folder contains the following: ■ The Readme.txt file that contains detailed instructions for configuring and starting the Oracle GoldenGate processes. ■ The src folder that contains configuration files to upload on the source server, in the Oracle GoldenGate installation directory. ■ The stg folder that contains configuration files to upload on the staging server, in the Oracle GoldenGate installation directory. The detailed instructions, customized for your configuration, are provided in the readme file. These instructions include:

1. Uploading or copying files from the src folder to the source server.

2. Uploading or copying files from the stg folder to the staging server.

3. Running on the source server the OBEY file generated by the JKM for starting the

Extract process, using the ggsci command line.

4. Generating on the source server definition file using the defgen command line.

5. Copying this definition file to the staging server.

6. If the initial load option is used:

■ Running on the staging server the OBEY file generated by the JKM for the initial load, using the ggsci command line. ■ Running on the source server the OBEY file generated by the JKM for the initial load, using the ggsci command line.

7. Finally Running on the staging server the OBEY file generated by the JKM for the

starting the Replicat processes, using the ggsci command line. See the Oracle GoldenGate documentation on OTN for more information on OBEY files, the ggsci and defgen utilities.

29.3.6 Design Interfaces Using Replicated Data

You can use the data in the replicated data as a source in your integration interfaces. This process is similar to using a source datastore journalized in consistent set mode. See Using Changed Data: Consistent Set Journalizing in the the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator for more information.

29.4 Advanced Configuration

This section includes the following advanced configuration topics: Note: Although this CDC configuration supports consistent set journalizing, it is not required to order datastores in the Journalized Table tab of the model after adding them to CDC. Oracle GoldenGate 29-9 ■ Initial Load Method ■ Tuning Replication Performances ■ One Source Multiple Staging Configuration

29.4.1 Initial Load Method

The staging tables contain a replica of the structure and data from the source tables. The Oracle GoldenGate processes capture changes on the source tables and apply them to the target. Yet the staging tables must be initially loaded with the original content of the source tables. You can use the following methods to perform the initial load: ■ Using Oracle GoldenGate: A specific GoldenGate process loads the whole content of the source tables into the staging tables. ■ Using Oracle Data Integrator: The Generate Interfaces IN option of Oracle Data Integrators Common Format Designer. This method uses ODI interfaces to transfer the data. ■ Using database backuprestore tools to copy data and structures.

29.4.2 Tuning Replication Performances

The following KM options can be used to improve replication performances: ■ COMPATIBLE: This Oracle-specific option affects the use of the PURGE key word and the way statistics using DBMS_STATS or ANALYZE are collected. Set this value to the database version of your staging server. ■ NB_APPLY_PROCESS: Number of Oracle GoldenGate Apply processes created on the staging server. ■ TRAIL_FILE_SIZE: Size of the Oracle GoldenGate trail file in Megabytes. For the NB_APPLY_PROCESS and TRAIL_FILE_SIZE parameters, see the Oracle GoldenGate Documentation on OTN for more information on performance tuning.

29.4.3 One Source Multiple Staging Configuration

It is possible to set up a configuration where changes are captured on a single source and replicated to several staging servers. The example below illustrates how to set this up in a typical configuration. Replication should source from source server SRC and replicate in both STG1 and STG2 staging servers. 1. Configure CDC for STG1 with the following configuration: ■ SRC_OGG_OBJECT_GROUP = SRC ■ SRC_SETUP_OGG_PROCESSES = YES ■ STG_OGG_OBJECT_GROUP = STG1 ■ STG_SETUP_OGG_PROCESSES = YES ■ ENABLE_ODI_CDC= YES 2. Start the journal and follow the instructions in the readme to set up the Oracle GoldenGate processes in SRC and STG1. 3. Configure CDC for STG2 with the following configuration: