When analyzing a customer’s GoldenGate deployment after a server reboot, I found a weird extract, which reported RUNNING. However, it was not extracting anything at all. Its report files were full of ABENDING entries. Here is a description of the problem, and what could have avoided this. managedProcessSettings ADD EXTRACT/ADD REPLICAT over the REST API accepts a managedProcessSettings object. It…
In a previous post about updating the profiles of all extracts and replicats at once, I wrote that a profile does not apply to distribution paths. With GoldenGate 23.26.4.0.0, that is no longer true. When looking at the help of ADD DISTPATH in the adminclient, it shows a new PROFILE clause: A distribution path or a receiver path can now…
I often need to retrieve report files or logs from GoldenGate deployments, and I wanted to find ways of automating this. Hence this blog, about retrieving all available logs with GoldenGate REST API. I previously wrote about the GoldenGate log files. Some of them (extract.log, replicat.log and others) are in fact just filters of other logs (ggserr.log or restapi.log). These…
While testing EVENTACTIONS (SUSPEND) on an extract, I noticed that nothing in INFO tells you the process is suspended. The extract shows as RUNNING, the lag might look fine for a while, and yet it has stopped capturing. You may use SUSPEND on purpose (to pause an extract when a specific DDL goes by, for instance). Or someone else put…
In a recent blog, I explained how instantiation filtering works. DBOPTIONS ENABLE_INSTANTIATION_FILTERING makes a replicat discard any record whose commit CSN is at or below a table’s instantiation CSN. It applies everything above it. This replicat parameter should be kept during the whole initial load process. At some point the replicat has processed past the instantiation boundary for every table,…
