Live Reporting with OGG

Reporting configuration:

Source system

To configure the Manager process
Step 1: On the source, configure the Manager process according to the instructions in tutorial

Step 2: On the source configure the Extract group, use the ADD EXTRACT command to create an Extract group.

GGSCI (HOME-03-DB12) 18> ADD EXTRACT extrpt, TRANLOG, BEGIN now -- see OGG Reference

EXTRACT added.

Step 3: On the source, use the ADD RMTTRAIL command to specify a remote trail to be created on the target system. Use the EXTRACT argument to link this trail to the Extract group.

GGSCI (HOME-03-DB12) 21> ADD RMTTRAIL Y:\dirdat\rt, EXTRACT extrpt

RMTTRAIL added.

Step 4: On the source, use the EDIT PARAMS command to create a parameter file for the Extract

group. Include the following parameters plus any others that apply to your database environment.

GGSCI (HOME-03-DB12) 22> edit params extrpt

-- Identify the Extract group:

EXTRACT extrpt

-- Specify database login information as needed for the database (source):

USERID ggs_owner@homedev, PASSWORD ggs_owner;

-- Specify the name or IP address of the target system:

RMTHOST HOME-03-DB12, MGRPORT 7809;

-- Specify the remote trail on the target system:

RMTTRAIL Y:\dirdat\rt;

--Specify transaction log options

TRANLOGOPTIONS ALTARCHIVELOGDEST PRIMARY W:\DEST_1; -- see OGG Reference

TRANLOGOPTIONS ALTARCHIVEDLOGFORMAT HOMEDEV_%S_%R.%T.ARC;

TRANLOGOPTIONS PATHMAP D:\ORACLE\PRODUCT\10.2.0\ORADATA\HOMEDEV\HOMEDEV U:\HOMEDEV\HOMEDEV

-- Specify tables to be captured:

TABLE scott.emp; -- you can put the scott.* if you want to include all the tables.

Note: I used the above tranlogoptions , because my source database (HOMEDEV) was on 32bit windows system and OGG processes were running on another system Win64bit. I made the logs location shared for me and then used the "Map Network Drive" option in windows (64bit) to expose the location to OGG process.

Target system

Step 5: configure the Manager process on the target, configure the Manager process according to the tutotial

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

Step 6: On the target, create a Replicat checkpoint table. All Replicat groups can use the same checkpoint table.

GGSCI (HOME-03-DB12) 10> dblogin userid ggs_owner@asmdb, password ggs_owner
Successfully logged into database.
GGSCI (HOME-03-DB12) 11> ADD CHECKPOINTTABLE ggs_owner.CHKPTAB
Successfully created checkpoint table GGS_OWNER.CHKPTAB.

Step 7: On the target, use the ADD REPLICAT command to create a Replicat group. Use the EXTTRAIL argument to link the Replicat group to the remote trail.

GGSCI (HOME-03-DB12) 12> ADD REPLICAT reprpt, EXTTRAIL Y:\dirdat\rt, begin now

REPLICAT added.

Step 8: On the target, use the EDIT PARAMS command to create a parameter file for the Replicat group.

Include the following parameters plus any others that apply to your database environment.

GGSCI (HOME-03-DB12) 14> edit params reprpt

-- Identify the Replicat group:

REPLICAT reprpt
-- State whether or not source and target definitions are identical:
ASSUMETARGETDEFS   -- See GG Reference
-- Specify database login information as needed for the database:
USERID ggs_owner@asmdb, PASSWORD ggs_owner
-- Specify error handling rules:
REPERROR (, )  -- will be discussed in some other post
-- Specify tables for delivery:
MAP scott.EMP, TARGET scott.EMP;

Test your replication , make modification to your source (EMP on source db) and verify on target. 

Related Posts:

Oracle GoldenGate Tutorial Part 1 - Concepts and Architecture

Oracle GoldenGate Tutorial Part 2 - Installation (Windows 2003)

Oracle GoldenGate Tutorial Part 3 - Manager process

Oracle GoldenGate Tutorial Part 4 - Working with OGG

Live Reporting with Data Pump -GG

OGG Reference - Commands and Options

SQL Server to SQL Server Replication using GG