Configuring the Data Pump in Golden Gate Oracle
Configure the data pump extract process.
1. Edit the parameters for the data pump as shown below:
GGSCI (sourceserver) 1> edit params PHREMD1
-- Data Pump extract for HR schema
RmtHost targetserver, MgrPort 7840
Table HR.* ;
PASSTHRU: If you aren’t doing any filtering or column mapping and your source & target object structures are identical, they must have the same column names, data types, sizes, and semantics and appear in the
same order. Using PASSTHRU improves performance by allowing GoldenGate to bypass looking up any table definitions from the database or the data-definitions file
RMTHOST & MGRPORT: Extract the remote server name and the port on which the GoldenGate manager is running. you can specify multiple remote hosts in the same parameter file to send trails to different servers.
RMTTRAIL: Use RMTTRAIL to specify the two-character remote trail name for your data pump. In this case, you use l2 as the remote trail name. Remember that l1 is the local trail. The data pump reads the local l1trail file and pumps it to the remote or target server as l2. Also notice that GoldenGate adds the same sixcharacter sequence number onto the trail-file name, starting with l2000000, then l2000001, thenl2000002, and so on
TABLE: This is the same TABLE parameter described for the Local Extract. In the example, you use wildcarding to pump all the tables in the HR schema (HR.*) to the target
server. If needed, you could filter or transform data at this point using the data pump. Instead, you just pass on all the data that the Local Extract has captured.
2. Adding the Data Pump
Set up the data-pump Extract configuration parameters, the next step is to add the datapump Extract group.
GGSCI (sourceserver) > ADD EXTRACT PHREMD1, EXTTRAILSOURCE dirdat/l1
GGSCI (sourceserver) > ADD RMTTRAIL dirdat/l2, EXTRACT PHREMD1, MEGABYTES 100
ADD EXTRACT, adds the data-pump Extract using the configuration parameters defined in the first step.
EXTTRAILSOURCE parameter of the ADD EXTRACT command tells GoldenGate to use the trail file created by the Local Extract as the source for the data-pump Extract.
ADD RMTTRAIL command adds the data-pump Extract remote trail file, assigns it to Extract PHREMD1, and gives it a size of 100MB.
3. Start and Stop the Extrace Process
GGSCI (sourceserver) > START EXTRACT PHREMD1
GGSCI (sourceserver) > STOP EXTRACT PHREMD1
4. Check the status of Extract process
GGSCI (sourceserver) 2> info extract PHREMD1
EXTRACT PHREMD1 Last Started 2011-01-14 10:25 Status RUNNING
Checkpoint Lag 00:00:00 (updated 00:00:01 ago)
Log Read Checkpoint File dirdat/l1000001
2011-01-17 15:05:33.485076 RBA 977
GGSCI (sourceserver) 3> info ext PHREMD1, detail
EXTRACT PHREMD1 Last Started 2011-01-23 16:28 Status RUNNING
Checkpoint Lag 00:00:00 (updated 00:00:00 ago)
Log Read Checkpoint File dirdat/l1000009
First Record RBA 3431
Target Extract Trails:
Remote Trail Name Seqno RBA Max MB
dirdat/l2 4 1151 100
Extract Source Begin End
dirdat/l1000009 2011-01-20 14:04 First Record
dirdat/l1000009 2011-01-14 10:22 2011-01-20 14:04
dirdat/l1000007 2011-01-12 10:59 2011-01-14 10:22
dirdat/l1000005 2011-01-07 08:38 2011-01-12 10:59
dirdat/l1000004 2011-01-07 08:38 2011-01-07 08:38
dirdat/l1000004 * Initialized * 2011-01-07 08:38
dirdat/l1000000 * Initialized * First Record
Current directory /gger/ggs/ora10
Report file /gger/ggs/dirrpt/PHREMD1.rpt
Parameter file /gger/ggs/dirprm/PHREMD1.prm
Checkpoint file /gger/ggs/dirchk/PHREMD1.cpe
Process file /gger/ggs/dirpcs/PHREMD1.pce
Stdout file /gger/ggs/dirout/PHREMD1.out
Error log /gger/ggs/ggserr.log
GGSCI (sourceserver) 2> stats ext PHREMD1
Sending STATS request to EXTRACT PHREMD1 ...
Start of Statistics at 2011-01-18 18:50:38.
Output to /gger/ggs/dirdat/l2:
Extracting from HR.EMPLOYEES to HR.EMPLOYEES:
*** Total statistics since 2011-01-15 13:54:52 ***
Total inserts 4.00
Total updates 0.00
Total deletes 2.00
Total discards 0.00
Total operations 6.00