Valid For

Replicat on Oracle. Valid as a standalone parameter or as an option to MAP.

Description

Use MAPINVISIBLECOLUMNS and NOMAPINVISIBLECOLUMNS to control whether or not Replicat includes invisible columns in Oracle target tables for default column mapping. For invisible columns in Oracle target tables that use explicit column mapping, they are always mapped so do not require this option. MAPINVISIBLECOLUMNS is required to Automatic Conflict Detection and Resolution.

MAPINVISIBLECOLUMNS and NOMAPINVISIBLECOLUMNS can be used in two different ways. When specified at a global level, one parameter remains in effect for all subsequent MAP statements, until the other parameter is specified. When used within a MAP statement, they override the global specifications.

Default

For integrated Replicat or parallel integrated Replicat the default value is MAPINVISIBLECOLUMNS unless you explicitly specify NOMAPINVISIBLECOLUMNS in the Replicat parameter file.

For all other types of Replicat, the default is NOMAPINVISIBLECOLUMNS.

Syntax

MAPINVISIBLECOLUMNS | NOMAPINVISIBLECOLUMNS
[, THREAD (threadID[, threadID][, ...][, thread_range[, thread_range][, ...])]

THREADS (threadID[, threadID][, ...][, thread_range[, thread_range][, ...])

Specifies MAPINVISIBLECOLUMNS | NOMAPINVISIBLECOLUMNS only for the specified thread or threads of a coordinated Replicat.

threadID[, threadID][, ...]

Specifies a thread ID or a comma-delimited list of threads in the format of threadID, threadID, threadID.

[, thread_range[, thread_range][, ...]

Specifies a range of threads in the form of threadIDlow-threadIDhigh or a comma-delimited list of ranges in the format of threadIDlow-threadIDhigh, threadIDlow-threadIDhigh.

A combination of these formats is permitted, such as threadID, threadID, threadIDlow-threadIDhigh.

Examples

Example 1   

This example enables MAPINVISIBLECOLUMNS for some MAP statements while disabling it for others.

MAPINVISIBLECOLUMNS
MAP hr.emp, TARGET hr.emp2;
NOMAPINVISIBLECOLUMNS
MAP hr.dep, TARGET hr.dep2;

Example 2   

This example shows a combination of global and MAP-level use of MAPINVISIBLECOLUMNS. The MAP specification overrides the global specification for the specified table.

 
NOMAPINVISIBLECOLUMNS
MAP hr.dep, TARGET hr.dep2;
MAP hr.emp, TARGET hr.emp2, MAPINVISIBLECOLUMNS;

Example 3   

In this example, MAPINVISIBLECOLUMNS is enabled globally, but turned off for thread 3. The remaining threads 1, 2, and 4 will include invisible target columns in default column mapping.

MAPINVISIBLECOLUMNS
NOMAPINVISIBLECOLUMNS THREAD(3)
MAP hr.dep, TARGET hr.dep2, THREADRANGE(1, 4);
MAP hr.emp, TARGET hr.emp2, THREADRANGE(1, 4);