Configure a Replicat Parameter File

Configure a Replicat parameter file to configure Replicat against a pluggable database. Replicat can operate in any mode within a pluggable database. These steps configure the Replicat parameter file.
  1. On the target system, create the Replicat parameter file using Oracle GoldenGate command line interface.

    EDIT PARAMS groupname

    Where: name is the name of the Replicat group.

  2. Enter the Replicat parameters in the order shown, starting a new line for each parameter statement.
    Here is the sample Replicat parameter file:
    REPLICAT repe
    USERIDALIAS ggeast DOMAIN OracleGoldenGate
    
    -- In case of Parallel Replicat:
    MAP_PARALLELISM 2
    APPLY_PARALLELISM 4
    SPLIT TRANS_RECS 50000
    
    -- In case of Integrated Replicat:
    DBOPTIONS INTEGRATEDPARAMS(PARALLELISM 4)
    DBOPTIONS INTEGRATEDPARAMS(EAGER_SIZE 20000)
    
    DDL EXCLUDE ALL
    DDLERROR default discard
    REPERROR (default,discard)
    DDLOPTIONS REPORT
    SOURCECATALOG DBEAST MAP hr.*, TARGET hr.*;
    

    Parameter Description

    REPLICAT group

    group is the name of the Replicat group.

    USERIDALIAS alias

    Specifies the alias of the database login credential of the user that is assigned to Replicat. This credential must exist in the Oracle GoldenGate credential store.

    DBOPTIONS INTEGRATEDPARAMS (parameter[, ...])

    This parameter specification applies to Replicat in integrated mode. It specifies optional parameters for the inbound server.

    MAP [container.]schema.object | library/file | library/file(member), TARGET [container.]schema.object | library/file | library/file(member);

    Specifies the relationship between a source table or sequence, or multiple objects, and the corresponding target object or objects.

    • MAP specifies the source table or sequence, or a wildcarded set of objects.
    • TARGET specifies the target table or sequence or a wildcarded set of objects.
    • container is the name of a container, if the source database is a multitenant container database.
    • 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 objects.
    • 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 this parameter statement with a semi-colon.

    To exclude objects from a wildcard specification, use the MAPEXCLUDE parameter.

  3. Enter any optional Replicat parameters that are recommended for your configuration. You can edit this file at any point before starting processing by using the EDIT PARAMS command.
  4. Save and close the file.