Skip to content

Replicat

Import order matters for GoldenGate instantiation filtering

When migrating a large database with GoldenGate, most of the volume is sometimes in old partitions which no longer change. A common shortcut is to move them first with expdp/impdp, even before GoldenGate is set up. Everything else, the active partitions and the non-partitioned tables, is exported once the extract is running, with PREPARECSN set. Instantiation filtering then makes the… 

Removing instantiation filtering from a GoldenGate replicat

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 instantiation CSN. It applies everything above it. This replicat parameter should be kept during the whole initial load process. At some point the replicat has processed past the instantiation boundary for every table,… 

GoldenGate 26ai AutoSchema TYPEMAP: overriding the default datatype mapping

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 Oracle one during an initial load. It worked, but one choice was not mine: the NUMBER primary key became a varchar(50). Automatic Schema Evolution takes its datatypes from a… 

GoldenGate 26ai automatic schema evolution: creating missing tables during an initial load

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. For anything else, you write the CREATE TABLE statements yourself, with the datatypes you choose, or choose another initial load method. The Automatic Schema Evolution feature launched in GoldenGate 26ai… 

GoldenGate instantiation CSN explained

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. But when migrating a database or just performing the initial load of a single table to prepare a GoldenGate replication, the known procedure is very often still the old one: start an extract, note… 

DDL filtering in GoldenGate extract and replicat

When replicating data with GoldenGate, you often want DDL changes (table alterations, new tables, dropped indexes, etc.) to follow alongside DML. But replicating all DDL is sometimes dangerous (TRUNCATE, DROP TABLE) or simply impossible (architecture differences between source and target). DDL filtering gives you precise control over this. This blog covers multiple aspects, including latest changes introduced in GoldenGate 26ai:… 

OGG-02454 Trail not found in checkpoint file when migrating a Coordinated Replicat

When migrating a Coordinated Replicat for a client, I faced a very specific OGG-02454 error that I wanted to share. When using the migration utility on a Classic Architecture Coordinated Replicat, every attempt failed at the checkpoint conversion step with OGG-02454 Trail … not found in checkpoint file. Because the migration utility rolls back the entire migration on any hard… 

Bulk update of GoldenGate extract profiles

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 REST API. Because even if you set a new profile as default with the {“isDefault”: true} flag, previously created extracts and replicats will not…