To configure the Manager process
1. On each source, configure the Manager process according to the instructions in Chapter 3.
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
3. 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.
Extract_1
ADD EXTRACT <ext_1>, {TRANLOG | INTEGRATED TRANLOG}, BEGIN <time>
[, THREADS <n>]
Extract_2
ADD EXTRACT <ext_2>, (TRANLOG | INTEGRATED TRANLOG}, BEGIN <time>
[, THREADS <n>]
❍ For TRANLOG and INTEGRATED TRANLOG, see the Oracle GoldenGate Windows and UNIX Reference Guide. INTEGRATED TRANLOG enabled integrated capture for an Oracle database.
Figure 13 Configuration for data warehousing
Creating a data warehousing configuration
Extract_1
ADD EXTTRAIL <local_trail_1>, EXTRACT <ext_1>
Extract_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.
5. 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.
Extract_1
-- Identify the Extract group:
EXTRACT <ext_1>
-- Specify database login information as needed for the database:
[SOURCEDB <dsn_1>][, USERID <user>][, PASSWORD <pw>
[<encryption options>]]
-- Specify the local trail that this Extract writes to -- and encryption options:
ENCRYPTTRAIL <encryption options>
EXTTRAIL <local_trail_1>
-- Specify tables to be captured:
TABLE <owner>.<table>;
Extract_2
-- Identify the Extract group:
EXTRACT <ext_2>
-- Specify database login information as needed for the database:
[SOURCEDB <dsn_2>][, USERID <user>][, PASSWORD <pw>
[<encryption options>]]
-- Specify the local trail that this Extract writes to -- and encryption options:
ENCRYPTTRAIL <encryption options>
-- Specify tables to be captured:
TABLE <owner>.<table>;
To configure the data pumps
6. 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.
Data pump_1
ADD EXTRACT <pump_1>, EXTTRAILSOURCE <local_trail_1>, BEGIN <time>
Data pump_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.
Creating a data warehousing configuration
7. On each source, use the ADD RMTTRAIL command to create a remote trail on the target.
Source_1
ADD RMTTRAIL <remote_trail_1>, EXTRACT <pump_1>
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.
8. 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.
Data pump_1
-- Identify the data pump group:
EXTRACT <pump_1>
-- Specify database login information as needed for the database:
[SOURCEDB <dsn_1>][, USERID <user>][, PASSWORD <pw>
[<encryption options>]]
-- Specify decryption if the input trail is encrypted.
DECRYPTTRAIL <encryption options>
-- Specify the name or IP address of the target system -- and optional encryption of data over TCP/IP:
RMTHOST <target>, MGRPORT <portnumber>, ENCRYPT <encryption options>
-- Specify the remote trail and encryption options on the target system:
ENCRYPTTRAIL <encryption options>
RMTTRAIL <remote_trail_1>
-- Allow mapping, filtering, conversion or pass data through as-is:
[PASSTHRU | NOPASSTHRU]
-- Specify tables to be captured:
TABLE <owner>.<table>;
Creating a data warehousing configuration
Data pump_2
-- Identify the data pump group:
EXTRACT <pump_2>
-- Specify database login information as needed for the database:
[SOURCEDB <dsn_2>][, USERID <user>][, PASSWORD <pw>
[<encryption options>]]
-- Specify decryption if the input trail is encrypted.
DECRYPTTRAIL <encryption options>
-- Specify the name or IP address of the target system -- and optional encryption of data over TCP/IP:
RMTHOST <target>, MGRPORT <portnumber>, ENCRYPT <encryption options>
-- Specify the remote trail and encryption options on the target system:
ENCRYPTTRAIL <encryption options>
RMTTRAIL <remote_trail_2>
-- Allow mapping, filtering, conversion or pass data through as-is:
[PASSTHRU | NOPASSTHRU]
-- Specify tables to be captured:
TABLE <owner>.<table>;
❍ Use NOPASSTHRU if the data pump will be filtering or converting data, and also use the SOURCEDB and USERID 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.
Target system
To configure the Manager process
9. Configure the Manager process according to the instructions in Chapter 3.
10. In the Manager parameter file, use the PURGEOLDEXTRACTS parameter to control the purging of files from the trail.
To configure the Replicat groups
11. 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.
Replicat_1
ADD REPLICAT <rep_1>, EXTTRAIL <remote_trail_1>, BEGIN <time>
Replicat_2
ADD REPLICAT <rep_2>, EXTTRAIL <remote_trail_2>, BEGIN <time>
❍ Use the EXTTRAIL argument to link the Replicat group to the trail.
12. 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.
Creating a data warehousing configuration
Replicat_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>][, USERID <user>][, PASSWORD <pw>
[<encryption options>]]
-- Specify decryption if the input trail is encrypted.
DECRYPTTRAIL <encryption options>
-- Specify error handling rules:
REPERROR (<error>, <response>) -- Specify tables for delivery:
MAP <owner>.<table>, TARGET <owner>.<table>[, DEF <template name>];
Replicat_2
-- 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>][, USERID <user>][, PASSWORD <pw>
[<encryption options>]]
-- Specify decryption if the input trail is encrypted.
DECRYPTTRAIL <encryption options>
-- Specify error handling rules:
REPERROR (<error>, <response>) -- Specify tables for delivery:
MAP <owner>.<table>, TARGET <owner>.<table>[, DEF <template name>];
❍ 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.