Blog

When doing complex operations with GoldenGate, checking for long running transactions is mandatory if you don't want to miss transactions.

While upgrading GoldenGate to 26ai for a DB2 z/OS source, I had to update the IBM Data Server Driver for ODBC and CLI (*CLI Driver, in short) alongside it.

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.

Since version 7.0.11, MongoDB natively supports OpenID Connect (OIDC) authentication.

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 -…

In this blog, I will present the new features introduced with the latest release (2.5.0) of the MongoDB DMK.

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.

Every time I work on database migrations with GoldenGate, I have the same talks with application teams about missing primary keys. Especially when it comes to LOB replication with GoldenGate.

GoldenGate is a powerful replication tool, but it is so versatile that you should always check whether what you intend to do is supported or not.

I recently wrote about NGINX reverse proxy reconfiguration after creating or deleting a deployment in GoldenGate.

For some customers, the end of support for GoldenGate 19c in May this year and the migration to Microservices Architecture mean that they have to adapt their patching procedures (if they had any !).

Configuring an NGINX reverse proxy for GoldenGate is well documented by Oracle, but what is not is the implication of adding or removing deployments.