Blog

For more than ten years (GoldenGate 12.2, released in 2015), GoldenGate has provided a way of performing initial load of tables with a per-table instantiation CSN.

I sometimes get asked how the new AI Service of GoldenGate 26ai works, and the best way to show it is to see it in action.

When replicating data with GoldenGate, you often want DDL changes (table alterations, new tables, dropped indexes, etc.) to follow alongside DML.

I recently wanted to work on Metric Extensions automation, and realized the task was a bit more complicated than I thought. My original idea was to look into the emcli verb list, but I was unlucky.

When migrating a Coordinated Replicat for a client, I faced a very specific OGG-02454 error that I wanted to share.

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.

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 this blog, I will present the new features introduced with the latest release (2.6.0) of the MongoDB DMK.

Throughout my consulting missions, I have often been asked to rename GoldenGate extracts. While this is not a difficult task, it should still be done correctly to avoid missing transactions.

Upgrading GoldenGate when the source is DB2 for z/OS is not quite the same exercise as upgrading a GoldenGate installation for Oracle.

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.

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.