Configuring a checkpoint table for the Replicat process is highly recommended whenever possible. While support for checkpoint tables varies across Oracle GoldenGate (OGG) and database versions, they are mandatory for certain Replicat types in modern OGG releases:

As of OGG 19.27, OGG 21.18, and OGG 23.8, a checkpoint table is required for Integrated Replicat.

Why This Matters

If a Replicat process crashes during the window where:

• A commit is issued to the target database, and the checkpoint file is being updated; it is theoretically possible that only one of these two operations succeeds. This can result in:
  • Duplicate data (if the commit succeeded but checkpoint didn’t)
  • Data loss (if checkpoint was updated but commit didn’t succeed)

A checkpoint table eliminates this risk by providing atomic, transactionally consistent checkpointing inside the database.

What About Extract?

• Extract processes do not use checkpoint tables.
• Instead, Extract relies on checkpoint files and trail file metadata to ensure accurate recovery.

Version-Specific Consideration

Since requirements evolve, always check the official Oracle GoldenGate documentation for:

• Version-specific requirements
• Supported Replicat types
• Database compatibility

Final Thoughts

If the version and architecture support it, always use a checkpoint table for Replicat. It is a critical component for ensuring data integrity, recoverability, and operational safety in production environments.