When automating your GoldenGate deployments, or tearing down a test environment, handling trail files is important. In fact, deleting an extract or a replicat does not delete the trail files it was writing to or reading from. It leaves the trail resource itself behind too, causing confusion (or worse) later. Indeed, a fresh extract writing to the same trail name/path…
While working on a client’s GoldenGate 26ai environment, I ran into a NFS-related replication issue that could have been serious, had it happened in production. Here is what happened and how the issue was fixed. The client’s GoldenGate extract was running on a dedicated server, capturing changes from an Oracle 19c source database. Trail files were written on an NFS.…
Since the beginning of the year, I had the opportunity to upgrade many GoldenGate setups to 26ai. On two of them, I was facing an issue regarding purge tasks that I could not solve. Since it took quite some time to finally find a solution, I figured it was worth documenting. The client had two GoldenGate 26ai installations running on…
Depending on the location of your GoldenGate trail files, you might have to use the convchk utility to relocate them before migrating to the Microservices Architecture. Oracle has the following restrictions for using the migration utility: Absolute path names for trail files. Classic trail file MUST reside in ./dirdat (or a subdirectory within it). If the trail file reside in another directory,…
