#ogg

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.

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.

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…

In my blog about the new automatic schema evolution feature in GoldenGate 26ai, I was replicating the following table from Oracle to PostgreSQL: The replicat created a PostgreSQL table from an…

In a previous blog, I noted that there might be a bug with the Maximum Input Characters setting in GoldenGate 26ai AI Service. The bug was confirmed by Oracle, so let's see what it is exactly.

For as long as I have used GoldenGate, an initial load had one prerequisite: the target tables must already exist. Data Pump takes care of it between two Oracle databases.

When automating your GoldenGate deployments, or tearing down a test environment, handling trail files is important.

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.

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.

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.

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.

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

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.

*Update: this bug seems to be corrected with the latest GoldenGate patch (23.26.2.0.1). If you face this error, try to patch your GoldenGate deployments.

If you are licensed for the GoldenGate Management Pack, using the Enterprise Manager plug-in for GoldenGate improves monitoring and management of your deployments.

GoldenGate logs are a powerful source of information when debugging or analyzing your deployments. However, some of these logs have a rather low retention period in active deployments.

Recently, I wrote about deleting a GoldenGate deployment with the REST API, and when investigating this issue, I remembered a limitation of the configuration assistant, which I wanted to talk about.

In this blog, I will explain what needs to be done when registering GoldenGate targets behind NGINX reverse proxy in the Enterprise Manager.

Recently, I was asked how to recreate a GoldenGate deployment if the password for the Security user (the first user created with the deployment) was lost.

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…

GoldenGate logs are a powerful source of information when troubleshooting or analyzing your deployments. However, there is at least one log file per service in the Microservices Architecture.

Setting up a distribution path is an important step when connecting two GoldenGate deployments. However, there are so many connection options that it's hard to know how to proceed.

After working on a GoldenGate deployment recently, I felt that the OGG-30007 error would be worth writing about. This error happens when registering certificates in GoldenGate.

In GoldenGate, processes have a few options that can be managed to fit your needs.

Your GoldenGate certificates should be granted by a trusted Certificate Authority, which normally handles the monitoring of certificates.

As part of a GoldenGate setup automation, changing the Default profile of your extracts and replicats seems like a good start if you don't want to deal with custom profiles or changing each…

Let me tell you a story about how I discovered an undocumented role in GoldenGate that could break your automation.

Among all the automation I was doing around a GoldenGate installation for DB2, I recently ended up with an INS-85037 error when running the configuration assistant oggca.sh.

When automating your GoldenGate deployment management, you might want to create path connections with the GoldenGate REST API.

The GoldenGate migration utility provided by Oracle allows you to quickly upgrade your classic architecture into GoldenGate 26ai with Microservices Architecture.

While migrating a GoldenGate classic architecture setup with the migration utility, I recently had the following OGG-12020 error: It is a very cryptic error at first glance, but let's try to…

When running the GoldenGate migration utility, which I presented in a previous blog post, you might encounter the following warning on USERID syntax: This is not really a surprise, since USERID…

When patching GoldenGate Classic Architecture, you might encounter an OGG-08048 error when restarting your extracts and replicats.

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 recently had an issue with the GoldenGate credential store at a customer when patching a GoldenGate 19c setup with the latest 19.30 patch.

When playing around with the GoldenGate REST API, you might have encountered the OGG-08116 error.

Another day, another not-so-documented GoldenGate error, this time about the OGG-10556 error, which I had when setting up replication on a new GoldenGate installation.

I was recently setting up GoldenGate for a client when I was struck by a ORA-44001 error.