Question: I notice that GoldenGate
uses data pump to replicate data. Is this the esame
data pump that does export (expdp) and import(impdp).
Answer: No, when Oracle acquired GoldenGate,
they inherited the utility named data pump, and oracle now
has two distinct tools called data pump:
Data Pump export/import: This
is a command-line utility used to backup individual tables
and schemas into flat files and import from flat files.
Goldengate Data Pump extract:
This is a process in Goldengate that takes
and applies archived redo logs to a remote database.
So there we
have it, two separate and distinct utilities named Data
Configure Data Pump for
To avoid the primary extract
failure in case of network disconnections, the secondary
group epmp02 is
configured. The data pump extract routes the data to the
target system leaving the primary extract dedicated to
perform change data capture only. The data pump uses the
to send data as is, unaltered.
rmttrail identifies the remote trail name followed by
the list of tables.
From within GGSCI
command-line prepare parameter file
saved on the default location of ./dirprm/ directory.
GGSCI (ggs-source) 1> EDIT PARAMS
USERID ggs_admin@S1E2, PASSWORD oracle
RMTHOST ggs-target, MGRPORT 7812
the secondary group in GoldenGate
add extract command creates the secondary group. The data pump
reads the local trail file identified by the option
GGSCI (ggs-source) 2> ADD EXTRACT
epmp02, EXTTRAILSOURCE ./dirdat/sb
GGSCI (ggs-source) 3> ADD RMTTRAIL ./dirdat/tb,
EXTRACT epmp02, MEGABYTES 128
the secondary extract in GoldenGate
Upon successful startup of
the data pump group, local trail transaction are shipped
over TCP/IP to the designated server by
manager port, mgrport.
GGSCI (ggs-source) 9> START EXTRACT
Sending START request to MANAGER ...
EXTRACT EPMP02 starting
Before proceeding to
configure the change data delivery group, we verify the data
pump status is running,
remote trail is created, and remote trail files are
receiving transactional data. In case of errors, we correct
the cause of the error and re-attempt restarting the
GGSCI (ggs-source) 10> INFO EXTRACT
Last Started 2015-10-30 19:14
00:00:00 (updated 00:00:05 ago)
Log Read Checkpoint