Configuring the Primary Extract

These steps configure the primary Extract to capture transaction data from a source DB2 for i and write the data to a local trail for temporary storage.

  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.

    Basic parameters for the primary Extract

    EXTRACT finance
SOURCEDB mysource, USERIDALIAS myalias 
ENCRYPTTRAIL AES192
EXTTRAIL /ggs/dirdat/lt
TABLE hr.*;
    Parameter Description 
    EXTRACT group

    group is the name of the Extract group. 

    SOURCEDB database, USERIDALIAS alias

    Specifies the real name of the source DB2 for i database (not an alias), plus 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 Database User for Oracle GoldenGate Processes. 

    ENCRYPTTRAIL algorithm

    Encrypts the local trail. 

    EXTTRAIL pathname

    Specifies the path name of the local trail to which the primary Extract writes captured data for temporary storage.

    		 
    TABLE schema.object;
TABLE library/file;
TABLE library/file(member);

    Specifies the database object for which to capture data.

    TABLE is a required keyword.

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

    object is the table name, or a wildcarded set of tables.

    library is the IBM i library name or a wildcarded set of libraries.

    file is the IBM i physical file name or a wildcarded set of physical files.

    member is the IBM i physical file member name or a wildcarded set of member names.

    When using the IBM i native name format (library/file with optional member) the only valid wildcards are a name with at least one valid character followed by a trailing asterisk (*) or *ALL which matches any name.

    Note:

    The member name is optional, and must be provided if the member names are required to be written in the trail as part of the object name. Without member names all members in a physical file be implicitly merged as a single object in the trail.

    Terminate the parameter statement with a semi-colon.

    To exclude tables from a wildcard specification, use the TABLEEXCLUDE parameter.

  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.
  4. Save and close the file.