#extract

While testing EVENTACTIONS (SUSPEND) on an extract, I noticed that nothing in INFO tells you the process is suspended.

When migrating a large database with GoldenGate, most of the volume is sometimes in old partitions which no longer change.

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.

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

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.

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.

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.

After writing blogs about Default profile updates and a bug affecting profiles in GoldenGate 26ai, I realized it would be a good idea to present a quick way to update all processes at once with the…

Classic Extracts have been deprecated in GoldenGate 19c and shouldn't be part of your GoldenGate replications for a long time now.