Example 5: Configuring Secondary Extract on Source (datapump Extract)

In the previous example, we have configured the extract process which extracts the changes from source and write the trail files to target.

However, in large system this can lead to lag for extract process and may have chance of loosing data.

Hence configuring local extract apart from remote trail is also possible using datapump process (differs from database expdp/impdp datapump).

Datapump process create local trail files and send them to remote as required.

On Source	Steps	On Target	Steps
Create Table	create table mytab as select * from dba_tables	Create Table	Create table mytab as select * from dba_tables
Create Pump Extract Process	./ggsci ADD EXTRACT ext3, TRANLOG, BEGIN NOW ADD EXTTRAIL I:\ggs_source\dirdat\lt, EXTRACT ext3 ADD EXTRACT pumpext1, EXTTRAILSOURCE I:\ggs_source\dirdat\lt EDIT PARAMS ext3 ## Add the Following lines to parameter file ### EXTRACT ext3 USERID ggs_owner, PASSWORD ggs_owner EXTTRAIL I:\ggs_source>\dirdat\lt TABLE TEST.MYTAB; ## Add the Remote Trail to pump extract , ##this location should be target location ADD RMTTRAIL /u01/ggt_target/dirdat/pt, EXTRACT pumpext1 EDIT PARAMS pumpext1 ## Add the following lines to parameter file ## EXTRACT pumpext1 USERID ggs_owner, PASSWORD ggs_owner PASSTHRU RMTHOST 192.168.56.109, MGRPORT 7809 RMTTRAIL /u01/ggt_target/dirdat/pt TABLE TEST.MYTAB;	Create Replicat Process	ADD REPLICAT rep3, EXTTRAIL /u01/ggt_target/dirdat/pt EDIT PARAMS rep3 ## Add following lines to parameter file ## REPLICAT rep3 ASSUMETARGETDEFS USERID ggs_owner, PASSWORD ggs_owner MAP TEST.MYTAB, TARGET TEST.MYTAB;
Start Local and Remote Extracts Process	./ggsci START EXTRACT ext3 START EXTRACT pumpext1	Start Replicat Process	./ggsci start replicat rep3
Perform DML Operations	delete from test.mytab where rownum < 1000; commit;
Verify the data	select count(*) from test.mytab;	Verify the data	select count(*) from test.mytab;source

All about Database Administration, Tips & Tricks