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 on the target. The data pump is optional, but recommended.

  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 Extract parameters in the order shown, starting a new line for each parameter statement. Your input variables will be different.

    Basic parameters for the data-pump Extract group:

    EXTRACT extpump
SOURCEDB mypump, USERIDALIAS myalias
RMTHOST fin1, MGRPORT 7809 ENCRYPT AES192, KEYNAME securekey2
RMTTRAIL /ggs/dirdat/rt
TABLE hr.*;
    Parameter Description 
    EXTRACT group

    group is the name of the data pump Extract. 

    SOURCEDB database, USERIDALIAS alias

    Specifies the real name of the source DB2 LUW 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.

    		 
    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. 

    RMTTRAIL pathname

    Specifies the path name of the remote trail. 

    TABLE 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 is a required keyword.

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

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

    Only the asterisk (*) wildcard is supported for DB2 LUW. The question mark (?) wildcard is not supported for this database.

    Terminate the parameter statement with a semi-colon.

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

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

  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.