8 Configuring Capture in Classic Mode

This chapter contains instructions for configuring the Oracle GoldenGate capture process in classic mode.

This chapter includes the following sections:

Note:

To switch an active Extract configuration from integrated to classic mode, perform these configuration steps and then see Administering Oracle GoldenGate for Windows and UNIX.

8.1 Prerequisites for Configuring Classic Capture

The guidelines in the following sections should be satisfied before configuring Extract in integrated mode.

  1. Chapter 3, "Preparing the Database for Oracle GoldenGate"

  2. Chapter 4, "Establishing Oracle GoldenGate Credentials"

  3. Chapter 5, "Choosing Capture and Apply Modes"

  4. Create the Oracle GoldenGate instance on the source system by configuring the Manager process. See Administering Oracle GoldenGate for Windows and UNIX.

  5. Additionally, review the guidelines in Administering Oracle GoldenGate for Windows and UNIX.

8.2 What to Expect from these Instructions

These instructions show you how to configure a basic Extract parameter (configuration) file for the primary Extract, which captures transaction data from the data source, and for a data-pump Extract, which propagates captured data that is stored locally in a trail from the source system to the target system. Your business requirements probably will require a more complex topology, but this procedure forms a basis for the rest of your configuration steps.

By performing these steps, you can:

  • get the basic configuration files established.

  • build upon them later by adding more parameters as you make decisions about features or requirements that apply to your environment.

  • use copies of them to make the creation of additional parameter files faster than starting from scratch.

Note:

These instructions do not configure Oracle GoldenGate to perform DDL capture or replication. To support DDL, create the parameter files and then see the following chapters:

Appendix D, "Installing Trigger-Based DDL Capture"

Chapter 13, "Configuring DDL Support"

8.3 Configuring the Primary Extract in Classic Capture Mode

These steps configure Extract to capture transaction data in classic mode. See Chapter 5, "Choosing Capture and Apply Modes" for more information about Extract modes.

  1. In GGSCI on the source system, create the Extract parameter file.

    EDIT PARAMS name
    

    Where: name is the name of the primary Extract.

  2. Enter the Extract parameters in the order shown, starting a new line for each parameter statement. See Table 8-1 for more information and parameter descriptions.

    Basic parameters for the primary Extract in classic capture mode

    EXTRACT finance
    USERIDALIAS tiger1 
    LOGALLSUPCOLS
    ENCRYPTTRAIL AES192
    EXTTRAIL /ggs/dirdat/lt
    SEQUENCE hr.employees_seq;
    TABLE hr.*;
    

    Table 8-1 Basic Parameters for Primary Extract in Classic Capture Mode

    Parameter Description
    EXTRACT group
    

    group is the name of the Extract group. For more information, see Reference for Oracle GoldenGate for Windows and UNIX.

    USERIDALIAS alias
    

    Specifies the alias of the database login credential of the user that is assigned to Extract. This credential must exist in the Oracle GoldenGate credential store. For more information, see Chapter 4, "Establishing Oracle GoldenGate Credentials."

    LOGALLSUPCOLS

    Writes all supplementally logged columns to the trail, including those required for conflict detection and resolution and the scheduling columns required to support integrated Replicat. (Scheduling columns are primary key, unique index, and foreign key columns.) You configure the database to log these columns with GGSCI commands. See Section 3.2, "Configuring Logging Properties".

    UPDATERECORDFORMAT COMPACT

    Combines the before and after images of an UPDATE operation into a single record in the trail. This parameter is valid for Oracle databases version 12c and later to support Replicat in integrated mode. Although not a required parameter, UPDATERECORDFORMAT COMPACT is a best practice and significantly improves Replicat performance. See Reference for Oracle GoldenGate for Windows and UNIX for more information.

    ENCRYPTTRAIL algorithm
    

    Encrypts the local trail. For more information about Oracle GoldenGate trail encryption options, see Administering Oracle GoldenGate for Windows and UNIX.

    EXTTRAIL pathname
    

    Specifies the path name of the local trail to which the primary Extract writes captured data. For more information, see Reference for Oracle GoldenGate for Windows and UNIX

    {TABLE | SEQUENCE} schema.object;
    

    Specifies the database object for which to capture data.

    • TABLE specifies a table or a wildcarded set of tables.

    • SEQUENCE specifies a sequence or a wildcarded set of sequences.

    • schema is the schema name or a wildcarded set of schemas.

    • object is the table or sequence name, or a wildcarded set of those objects.

    See Administering Oracle GoldenGate for Windows and UNIX for information about how to specify object names with and without wildcards.

    Terminate the parameter statement with a semi-colon.

    To exclude tables from a wildcard specification, use the TABLEEXCLUDE parameter. See Reference for Oracle GoldenGate for Windows and UNIX for more information about usage and syntax.

    For more information and for additional TABLE options that control data filtering, mapping, and manipulation, see Reference for Oracle GoldenGate for Windows and UNIX.


  3. Enter any optional Extract parameters that are recommended for your configuration. You can edit this file at any point before starting processing by using the EDIT PARAMS command in GGSCI. For more information, see the Reference for Oracle GoldenGate for Windows and UNIX.

  4. Save and close the file.

8.4 Configuring the Data Pump Extract

These steps configure the data pump that reads the local trail and sends the data across the network to a remote trail. The data pump is optional, but recommended. For more information about data pumps, see Administering Oracle GoldenGate for Windows and UNIX.

  1. In GGSCI on the source system, create the data-pump parameter file.

    EDIT PARAMS name
    

    Where name is the name of the data pump Extract.

  2. Enter the data-pump parameters in the order shown, starting a new line for each parameter statement. Your input variables will be different. See Table 8-2 for descriptions.

    Basic parameters for the data-pump Extract group:

    EXTRACT extpump
    USERIDALIAS tiger1
    RMTHOST fin1, MGRPORT 7809 ENCRYPT AES192, KEYNAME securekey2
    RMTTRAIL /ggs/dirdat/rt
    SEQUENCE hr.employees_seq;
    TABLE hr.*;
    

    Table 8-2 Basic Parameters for a Data-pump Extract

    Parameter Description
    EXTRACT group
    

    group is the name of the data pump Extract. For more information, see Reference for Oracle GoldenGate for Windows and UNIX.

    USERIDALIAS alias
    

    Specifies the alias of the database login credential of the user that is assigned to Extract. This credential must exist in the Oracle GoldenGate credential store. For more information, see Chapter 4, "Establishing Oracle GoldenGate Credentials".

    RMTHOST hostname, MGRPORT portnumber,[, ENCRYPT algorithm KEYNAME keyname]
    
    • RMTHOST specifies the name or IP address of the target system.

    • MGRPORT specifies the port number where Manager is running on the target.

    • ENCRYPT specifies optional encryption of data across TCP/IP.

    For additional options and encryption details, see Reference for Oracle GoldenGate for Windows and UNIX.

    RMTTRAIL pathname
    

    Specifies the path name of the remote trail. For more information, see Reference for Oracle GoldenGate for Windows and UNIX.

    {TABLE | SEQUENCE} schema.object;
    

    Specifies a table or sequence, or multiple objects specified with a wildcard. In most cases, this listing will be the same as that in the primary Extract parameter file.

    • TABLE specifies a table or a wildcarded set of tables.

    • SEQUENCE specifies a sequence or a wildcarded set of sequences.

    • schema is the schema name or a wildcarded set of schemas.

    • object is the name of a table or sequence, or a wildcarded set of those objects.

    See Administering Oracle GoldenGate for Windows and UNIX for information about how to specify object names with and without wildcards.

    Terminate this parameter statement with a semi-colon.

    To exclude tables or sequences from a wildcard specification, use the TABLEEXCLUDE or SEQUENCEEXCLUDE parameter after the TABLE statement.

    For more information and for additional TABLE options that control data filtering, mapping, and manipulation, see Reference for Oracle GoldenGate for Windows and UNIX.


  3. Enter any optional Extract parameters that are recommended for your configuration. You can edit this file at any point before starting processing by using the EDIT PARAMS command in GGSCI. For more information, see the Reference for Oracle GoldenGate for Windows and UNIX.

  4. See Appendix A, "Optional Parameters for Integrated Modes" for additional configuration considerations.

  5. Save and close the file.