Configure a Replicat process to configure Replicat for a pluggable database (PDB). Replicat can operate in any of the available modes within an Oracle multitenant container database.

1. On the target system, create the Replicat parameter file using GGSCI command line interface.

   EDIT PARAMS name

   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.

   Basic parameters for the Replicat group in nonintegrated mode:

   REPLICAT repe
   USERIDALIAS ggeast
   ASSUMETARGETDEFS
   MAP hr.*, TARGET hr2.*;
   

   Basic parameters for the Replicat group in integrated Replicat mode:

   REPLICAT repw
   DBOPTIONS INTEGRATEDPARAMS(parallelism 6)
   USERIDALIAS ggwest
   ASSUMETARGETDEFS
   MAP hr.*, TARGET hr2.*;
   

   Parameter	Description
   REPLICAT group	group is the name of the Replicat group.
   DBOPTIONS DEFERREFCONST	Applies to Replicat in nonintegrated mode. DEFERREFCONST sets constraints to DEFERRABLE to delay the enforcement of cascade constraints by the target database until the Replicat transaction is committed. See DBOPTIONS for additional important information.
   DBOPTIONS INTEGRATEDPARAMS (parameter[, ...])	This parameter specification applies to Replicat in integrated mode. It specifies optional parameters for the inbound server. See Additional Parameter Options for Integrated Replicatfor additional important information about these DBOPTIONS options.
   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. For more information, see Establishing Oracle GoldenGate Credentials
   MAP [container.]schema.object, TARGET schema.object;	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. Terminate this parameter statement with a semi-colon. To exclude objects from a wildcard specification, use the MAPEXCLUDE parameter. For more information and for additional options that control data filtering, mapping, and manipulation, see MAP in Parameters and Functions Reference for Oracle GoldenGate.

   Basic parameters for the Replicat group in parallel Replicat mode:

   REPLICAT repe
   USERID ggadmin, PASSWORD ***
   MAP_PARALLELISM 3
   MIN_APPLY_PARALLELISM 2
   MAX_APPLY_PARALLELISM 10
   SPLIT_TRANS_RECS 60000
   MAP *.*, TARGET *.*;

   Parameter	Description
   MAP_PARALLELISM	Configures number of mappers. This controls the number of threads used to read the trail file. The minimum value is 1, maximum value is 100 and the default value is 2.
   APPLY_PARALLELISM	Configures number of appliers. This controls the number of connections in the target database used to apply the changes. The default value is four.
   MIN_APPLY_PARALLELISM MAX_APPLY_PARALLELISM	The Apply parallelism is auto-tuned. You can set a minimum and maximum value to define the ranges in which the Replicat automatically adjusts its parallelism. There are no defaults. Do not use with APPLY_PARALLELISM at same time.
   SPLIT_TRANS_REC	Specifies that large transactions should be broken into pieces of specified size and applied in parallel. Dependencies between pieces are still honored. Disabled by default.
   COMMIT_SERIALIZATION	Enables commit FULL serialization mode, which forces transactions to be committed in trail order.
   Advanced Parameters
   LOOK_AHEAD_TRANSACTIONS	Controls how far ahead the Scheduler looks when batching transactions. The default value is 10000.
   CHUNK_SIZE	Controls how large a transaction must be for parallel Replicat to consider it as large. When parallel Replicat encounters a transaction larger than this size, it will serialize it, resulting in decreased performance. However, increasing this value will also increase the amount of memory consumed by parallel Replicat.

3. If using integrated Replicat or parallel Replicat in integrated mode, add the following parameters to the Extract parameter file:

   • LOGALLSUPCOLS: This parameter ensures the capture of the supplementally logged columns in the before image. It's the default parameter and shouldn't be turned off or disabled. It is valid for any source database that is supported by Oracle GoldenGate. For Extract versions older than 12c, you can use GETUPDATEBEFORES and NOCOMPRESSDELETES parameters to satisfy the same requirement. The database must be configured to log the before and after values of the primary key, unique indexes, and foreign keys.

   • The UPDATERECORDFORMAT parameter set to COMPACT: This setting causes Extract to combine the before and after images of an UPDATE operation into a single record in the trail. This is the default option and it is recommended that you don't change the default setting.

4. 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. See Additional Parameter Options for Integrated Replicat for additional configuration considerations.
5. Save and close the file.