Source Systems

Configure the Manager process and primary Extract groups for the source systems.

To configure the Manager process

1. On each source, configure the Manager process according to the instructions in Chapter 3, "Configuring Manager and Network Communications."

2. In each Manager parameter file, use the PURGEOLDEXTRACTS parameter to control the purging of files from the trail on the local system.

To configure the primary Extract groups

1. On each source, use the ADD EXTRACT command to create a primary Extract group.

For documentation purposes, these groups are called ext_1 and ext_2.

Command on source_1:

ADD EXTRACT ext_1, {TRANLOG | INTEGRATED TRANLOG}, BEGIN time [option[, ...]]

Command on source_2:

ADD EXTRACT ext_2, {TRANLOG | INTEGRATED TRANLOG}, BEGIN time [option[, ...]]

See Reference for Oracle GoldenGate for Windows and UNIX for detailed information about these and other ADD EXTRACT options that may be required for your

installation.

2. On each source, use the ADD EXTTRAIL command to create a local trail.

Command on source_1:

ADD EXTTRAIL local_trail_1, EXTRACT ext_1 Command on source_2:

ADD EXTTRAIL local_trail_2, EXTRACT ext_2

Use the EXTRACT argument to link each Extract group to the local trail on the same system. The primary Extract writes to this trail, and the data-pump reads it.

3. On each source, use the EDIT PARAMS command to create a parameter file for the primary Extract. Include the following parameters plus any others that apply to

your database environment. For possible additional required parameters, see the Oracle GoldenGate installation and setup guide for your database.

Parameter file for ext_1:

-- Identify the Extract group:

EXTRACT ext_1

-- Specify database login information as needed for the database:

[SOURCEDB dsn_1][, USERIDALIAS alias]

-- Log all scheduling columns if using integrated Replicat LOGALLSUPCOLS

-- Specify the local trail that this Extract writes to -- and the encryption algorithm:

ENCRYPTTRAIL algorithm EXTTRAIL local_trail_1

-- Specify tables and sequences to be captured:

SEQUENCE [container.|catalog.]owner.sequence;

TABLE [container.|catalog.]owner.table;

Parameter file for ext_2:

-- Identify the Extract group:

EXTRACT ext_2

-- Specify database login information as needed for the database:

[SOURCEDB dsn_2][, USERIDALIAS alias]

-- Log all scheduling columns if using integrated Replicat or CDR LOGALLSUPCOLS

-- Specify the local trail that this Extract writes to -- and the encryption algorithm:

ENCRYPTTRAIL algorithm EXTTRAIL local_trail_2

-- Specify tables and sequences to be captured:

SEQUENCE [container.|catalog.]owner.sequence;

TABLE [container.|catalog.]owner.table;

To configure the data pumps

1. On each source, use the ADD EXTRACT command to create a data pump Extract group. For documentation purposes, these pumps are called pump_1 and pump_2.

Command on source_1:

ADD EXTRACT pump_1, EXTTRAILSOURCE local_trail_1, BEGIN time Command on source_2:

ADD EXTRACT pump_2, EXTTRAILSOURCE local_trail_2, BEGIN time

Use EXTTRAILSOURCE as the data source option, and specify the name of the trail on the local system

2. On each source, use the ADD RMTTRAIL command to create a remote trail on the target.

Command on source_1:

ADD RMTTRAIL remote_trail_1, EXTRACT pump_1 Command on source_2:

ADD RMTTRAIL remote_trail_2, EXTRACT pump_2

Use the EXTRACT argument to link each remote trail to a different data pump. The data pump writes to this trail over TCP/IP, and a Replicat reads from it.

See Reference for Oracle GoldenGate for Windows and UNIX for additional ADD RMTTRAIL options.

3. On each source, use the EDIT PARAMS command to create a parameter file for the data pump group. Include the following parameters plus any others that apply to your database environment.

Parameter file for pump_1:

-- Identify the data pump group:

EXTRACT pump_1

-- Specify database login information as needed for the database:

[SOURCEDB dsn_1][, USERIDALIAS alias]

-- Decrypt the data only if the data pump must process it.

-- DECRYPTTRAIL

-- Specify the name or IP address of the target system -- and optional encryption of data over TCP/IP:

RMTHOST target, MGRPORT port_number, ENCRYPT encryption_options

-- Specify the remote trail and encryption algorithm on the target system:

ENCRYPTTRAIL algorithm RMTTRAIL remote_trail_1

-- Allow mapping, filtering, conversion or pass data through as-is:

[PASSTHRU | NOPASSTHRU]

-- Specify tables and sequences to be captured:

SEQUENCE [container.|catalog.]owner.sequence;

TABLE [container.|catalog.]owner.table;

Parameter file for pump_2:

-- Identify the data pump group:

EXTRACT pump_1

-- Specify database login information as needed for the database:

[SOURCEDB dsn_2][, USERIDALIAS alias]

-- Decrypt the data only if the data pump must process it.

-- DECRYPTTRAIL

-- Specify the name or IP address of the target system -- and optional encryption of data over TCP/IP:

RMTHOST target, MGRPORT port_number, ENCRYPT encryption_options

-- Specify the remote trail and encryption algorithm on the target system:

ENCRYPTTRAIL algorithm RMTTRAIL remote_trail_2

-- Allow mapping, filtering, conversion or pass data through as-is:

[PASSTHRU | NOPASSTHRU]

-- Specify tables and sequences to be captured:

SEQUENCE [container.|catalog.]owner.sequence;

TABLE [container.|catalog.]owner.table;

Use NOPASSTHRU if the data pump will be filtering or converting data, and also use the SOURCEDB and USERIDALIAS parameters as appropriate for the database, to enable definitions lookups. If the data pump will not be filtering or converting data, use PASSTHRU to bypass the lookups.

7.3.2 Target System

Configure the Manager process and primary Replicat groups for the target system.

To configure the Manager process

1. Configure the Manager process. See Chapter 3, "Configuring Manager and Network Communications" for instructions.

2. In the Manager parameter file, use the PURGEOLDEXTRACTS parameter to control the purging of files from the trail.

To configure the Replicat groups

1. On the target, create a Replicat checkpoint table (unless using Oracle integrated Replicat). See Section 14.3, "Creating a Checkpoint Table" for instructions.

2. On the target, use the ADD REPLICAT command to create a Replicat group for each remote trail that you created. For documentation purposes, these groups are called rep_1 and rep_2.

Command to add rep_1:

ADD REPLICAT rep_1

[, INTEGRATED | COORDINATED [MAXTHREADS number]]

, EXTTRAIL remote_trail_1, BEGIN time Command to add rep_2:

ADD REPLICAT rep_2

[, INTEGRATED | COORDINATED [MAXTHREADS number]]

, EXTTRAIL remote_trail_2, BEGIN time

Use the EXTTRAIL argument to link the Replicat group to the trail.

See Reference for Oracle GoldenGate for Windows and UNIX for detailed information about these and other options that may be required for your installation.

3. On the target, use the EDIT PARAMS command to create a parameter file for each Replicat group. Include the following parameters plus any others that apply to your database environment. For possible additional required parameters, see the Oracle GoldenGate installation and setup guide for your database.

Parameter file for rep_1:

-- Identify the Replicat group:

REPLICAT rep_1

-- State whether or not source and target definitions are identical:

SOURCEDEFS full_pathname | ASSUMETARGETDEFS

-- Specify database login information as needed for the database:

[TARGETDB dsn_3][, USERIDALIAS alias]

-- Specify error handling rules:

REPERROR (error, response)

-- Specify tables for delivery and threads if using coordinated Replicat:

MAP [container.|catalog.]owner.table, TARGET owner.table[, DEF template]

[, THREAD (thread_ID)]

[, THREADRANGE (thread_range[, column_list])]

;

Parameter file for rep_1:

-- Identify the Replicat group:

REPLICAT rep_2

-- State whether or not source and target definitions are identical:

SOURCEDEFS full_pathname | ASSUMETARGETDEFS

-- Specify database login information as needed for the database:

[TARGETDB dsn_3][, USERIDALIAS alias]

-- Specify error handling rules:

REPERROR (error, response)

-- Specify tables for delivery and threads if using coordinated Replicat:

MAP [container.|catalog.]owner.table, TARGET owner.table[, DEF template]

[, THREAD (thread_ID)]

[, THREADRANGE (thread_range[, column_list])]

;

You can use any number of MAP statements for any given Replicat group. All MAP statements for a given Replicat group must specify the same objects that are contained in the trail that is linked to the group.

8

8

Configuring Oracle GoldenGate to Maintain a

In document Goldengate 12c (Page 85-91)