#rest

In a previous blog, I went through the full procedure of renaming a GoldenGate extract from the adminclient. I included all necessary steps to avoid missing transactions. Doing this by hand is

In a previous post, I shared the OGGRestAPI Python client I built for the GoldenGate REST API. Since then, I kept using it on production deployments, fixing it and adding new features along the way.

In a previous blog, I presented how to set up a distribution path between two GoldenGate deployments both secured with NGINX. The method I used there was purely through the Web UI. But GoldenGate

I already covered out-of-place patching from the web UI, but patching tasks should be automated, and clicking through the same screens for every deployment can get repetitive. Let's do the exact same

When doing complex operations with GoldenGate, checking for long running transactions is mandatory if you don't want to miss transactions. Let's look at two ways of retrieving such information, first

The 23.26.3.0.0 release update of GoldenGate 26ai (July 2026) ships a small but welcome usability change, listed in the *New Enhancements section of the release notes: > Bug 39415027: Generic -

When automating your GoldenGate deployment management, you might want to create path connections with the GoldenGate REST API. This is an important aspect when connecting GoldenGate deployments with

Is it possible to create a new GoldenGate deployment with the REST API ? This is the question I will try to answer in this blog, based on my experience with the REST API. I will dive in what is done

*Updated in June 2026, based on the latest version of the client. In this blog, I provide GoldenGate administrators with a fully working, production-ready Python client to efficiently handle

In this blog post, I will guide you on how to query the restapi.log file of your GoldenGate deployments more efficiently. These logs are a valuable source of information for GoldenGate administrators

When playing around with the GoldenGate REST API, you might have encountered the OGG-08116 error. It happens when using the *Create Connection REST API call, with the following endpoint given in the

Oracle GoldenGate REST API has been around for quite some time now, but I've yet to see it used in practice at customers. Every time I tried to introduce it, it was some sort of novelty. Mainly