1. Grouping Tables into Different Extract Groups
2. Using Oracle GoldenGate Macros
- For tables with low activity rates, you should group under one extract group.
- For tables with high activity rates, you should configure them with their own extract group.
- For datatypes requires FETCHCOLS operations, you should avoid mixing it with extract group where majority of datatypes don't need FETCHCOLS.
teradata_instance_1.mac:
MACRO #odbc_connect
BEGIN
sourcedb TDINST1, useridalias ogguser
END;
This allows you to externalize common parameters that might be used by multiple extract/replicat groups. In production environment, you will have multiple and even hundreds of extract/replicat groups. Externalizing the common setup in macro file is a good practice.
3. Using Oracle GoldenGate Pump
EXTRACT EXEPUMP
PASSTHRU
RMTHOST adc18739.us.oracle.com, MGRPORT 7809, COMPRESS
RMTTRAIL ./dirdat/pe
TABLE *;
In general, you will always use the parameter PASSTHRU for the best performance. This setup allows data pump to move the data without accessing the database or interpreting the incoming data.
4. Thinking of Using DEFGEN Files
5. Checking Primary Keys
Hope these rules are helpful and can save time for your next project.