Pythian Blog: Technical Track

GoldenGate: relative or absolute path for trail files?

by Michael Dinh on Jan 11, 2019 12:00:00 AM

When implementing GoldeGate solutions, something as simple as path to trail files can create havoc. What is the correct path for trail format? It depends. There is one important factor to consider. 
You can change any of the attributes specified with the ADD EXTRACT command, except for the following:
 
 Altering an Extract specified with the EXTTRAILSOURCE option.
 
 Altering the number of RAC threads specified with the THREADS option.
Reference: Oracle® GoldenGate Reference for Oracle GoldenGate for Windows and UNIX (ALTER EXTRACT) The above restriction could be an influencing factor when deciding to use absolute path. Using relative path for trail files:
  1. Need to create symbolic link originally if not residing from GoldenGate Home.
  2. No need to recreate symbolic link when relocating trail.
  3. No need to recreate extract when relocating trail.
  4. No need to modify parameter for GoldenGate extracts/replicats/manager when relocating trail.
  5. Need to create multiple symbolic links for GoldenGate on RAC.
  6. Need to create new symbolic links for trail using out-of-place GoldenGate upgrade.
Using absolute path for trail files:
  1. No need to create symbolic link originally.
  2. No need to recreate symbolic link when relocating trail.
  3. Need to recreate extract when relocating trail.
  4. Need to modify parameter for GoldenGate extracts/replicats/manager when relocating trail.
  5. No need to create multiple symbolic links for GoldenGate on RAC.
  6. No need to create new symbolic links for trail using out of place GoldenGate upgrade.
Hopefully, this will help to decide in choosing the correct path for GoldenGate trail.
Topics: Oracle Big Data Mongodb Technical Track Replication Goldengate

No Comments Yet

Let us know what you think

See all

See all

Subscribe by email
Follow us
Love Your Data
Pythian Logo

© 2024 All rights reserved.