2.4 ALLOWDUPTARGETMAP | NOALLOWDUPTARGETMAP

Valid For

Extract and Replicat

Not valid for Oracle Database when running with integrated Replicat or Parallel Replicat in Integrated mode. 

Description

Use the ALLOWDUPTARGETMAP and NOALLOWDUPTARGETMAP parameters to control whether or not the following are accepted in a parameter file:

  • In an Extract parameter file: duplicate TABLE parameters for the same source object if the COLMAP option is used in any of them. By default, Extract abends on duplicate TABLE statements when COLMAP is used.

  • In a Replicat parameter file: duplicate MAP statements for the same source and target objects. By default, duplicate MAP statements cause Replicat to abend.

If ALLOWDUPTARGETMAP is not specified and the same source and target tables are mapped more than once, only the first MAP statement is used and the others are ignored.

Default

NOALLOWDUPTARGETMAP

Syntax

ALLOWDUPTARGETMAP | NOALLOWDUPTARGETMAP

Examples

Example 1   

The following Extract parameter file is permissible with ALLOWDUPTARGETMAP enabled.

EXTRACT extcust
USERIDALIAS tiger1
EXTTRAIL dirdat/aa
TABLE ogg.tcustmer;
EXTTRAIL dirdat/bb
TABLE ogg.tcustmer, TARGET ogg.tcustmer, COLMAP (USEDEFAULTS, col1=id, col2=name);  
Example 2   

The following Replicat parameter file is permissible with ALLOWDUPTARGETMAP enabled.

REPLICAT repcust
USERIDALIAS tiger1
SOURCEDEFS /ggs/dirdef/source.def
ALLOWDUPTARGETMAP
GETINSERTS
GETUPDATES
IGNOREDELETES
MAP ggs.tcustmer, TARGET ggs.tcustmer, COLMAP (USEDEFAULTS, deleted_row = 'N');
IGNOREINSERTS
IGNOREUPDATES
GETDELETES
UPDATEDELETES
MAP ggs.tcustmer, TARGET ggs.tcustmer, COLMAP (USEDEFAULTS, deleted_row = 'Y');

Also see About Parallel Replicat.