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.

The steps to set up the data pump are:
  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 H-* for descriptions.

    Basic parameters for the data-pump Extract group using two-part object names:

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

    Basic parameters for the data-pump Extract group using three-part object names (including a pluggable database):

    EXTRACT extpump
    USERIDALIAS tiger1
    RMTHOST fin1, MGRPORT 7809 ENCRYPT AES192, KEYNAME securekey2
    RMTTRAIL /ggs/dirdat/rt
    TABLE test.ogg.tab1;
    SOURCECATALOG pdb1
    SEQUENCE hr.employees_seq;
    TABLE hr.*;
    SOURCECATALOG pdb2
    TABLE sales.*;
    TABLE acct.*;
    
    Parameter Description
    EXTRACT group

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

    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, see 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.

    RMTTRAIL pathname

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

    SOURCECATALOG container

    Use this parameter when the source database is a multitenant container database. Specifies the name of a pluggable database that is to be used as the default container for all subsequent TABLE and SEQUENCE parameters that contain two-part names. This parameter enables you to use two-part object names (schema.object) rather than three-part names (container.schema.object). It remains in effect until another SOURCECATALOG parameter is encountered or a full three-part TABLE or SEQUENCE specification is encountered. Use this parameter when the source database is a multitenant container database. See Reference for Oracle GoldenGate for more information about SOURCECATALOG.

    {TABLE | SEQUENCE} [container.]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.

    • container is the name of the root container or pluggable database that contains the table or sequence, if this source database is a multitenant container database. See the SOURCECATALOG description in this table.

    • 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 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.

  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 and Optional Parameters for Integrated Modes for additional configuration considerations..
  4. Save and close the file.