REPLICAT group

• group is the name of the Replicat group that you created with the ADD REPLICAT command.

Configures Replicat as an online process with checkpoints.

{SOURCEDEFS path} |
ASSUMETARGETDEFS

• Use SOURCEDEFS if the source and target tables have different definitions. Specify the source data-definitions file generated by DEFGEN.

• Use ASSUMETARGETDEFS if the source and target tables have the same definitions.

Specifies how to interpret data definitions.

For Oracle databases that use multi-byte character sets, you must use SOURCEDEFS (with a DEFGEN-generated definitions file) if the source semantics setting is in bytes and the target is in characters. This is required even when the source and target data definitions are identical.

[DEFERAPPLYINTERVAL n unit]

• n is a numeric value for the amount of time to delay before applying transactions. Minimum is set by the EOFDELAY parameter. Maximum is seven days.

• unit can be:

  S | SEC | SECS | SECOND | SECONDS | MIN | MINS | MINUTE | MINUTES | HOUR | HOURS | DAY | DAYS

Optional. Specifies an amount of time for Replicat to wait before applying its transactions to the target system.

[TARGETDB dsn | container | catalog]
[, USERIDALIAS alias options |
, USERID user, options]

Specifies database connection information.

TARGETDB specifies the target datasource name (DSN). See TARGETDB in Reference for Oracle GoldenGatefor more information .

USERID and USERIDALIAS specify database credentials if required.

HANDLECOLLISIONS

Specifies collision handling. Use only if you are performing an initial load concurrently with starting online processing and the source database will remain active during the load. HANDLECOLLISIONS resolves the results of the copy with the ongoing replicated transactional changes. It resolves insert operations for which the row already exists and update and delete operations for which the row does not exist. It can be used globally for all MAP statements in a parameter file or within a MAP statement, or both.

SOURCECATALOG

Specifies a default container in a source Oracle multitenant container database. Enables the use of two-part names (schema.object) where three-part names otherwise would be required for those databases. You can use multiple instances of this parameter to specify different default containers or catalogs for different sets of MAP parameters.

MAP [container. | catalog.]owner.object,
TARGET owner.object[, DEF template]
[THREAD (thread_ID)]
[THREADRANGE (thread_range[, column_list])]
[COORDINATED]
;

Specifies a relationship between a source object or objects and a target object or objects. MAP specifies the source object, and TARGET specifies the target object.

For the source object, specify the fully qualified name of the object or a fully qualified wildcarded specification for multiple objects. For an Oracle multitenant container database the source object name must include the name of the container or catalog unless SOURCECATALOG is used.

For the target object, specify only the owner.object components of the name, regardless of the type of database. Replicat can only connect to one Oracle container. Use a separate Replicat process for each container or catalog to which you want to apply data.

See Specifying Object Names in Oracle GoldenGate Input for guidelines for specifying object names in parameter files.

The THREAD, THREADRANGE, and COORDINATED options are valid for Replicat when in coordinated mode. They enable you to partition the workload to one or more specific Replicat threads. See in Reference for Oracle GoldenGatefor syntax and usage.

The DEF option specifies a definitions template.

CATALOGEXCLUDE

SCHEMAEXCLUDE

MAPEXCLUDE

EXCLUDEWILDCARDOBJECTSONLY

Parameters that can be used in conjunction with one another to exclude specific source objects from a wildcard specification in the associated MAP statement.