Recommended Baseline Configuration for GoldenGate Data Streams
Learn about the starting settings for GoldenGate Data Streams. Configure the stream so that change records are delivered reliably, formatted consistently, and enriched with the metadata downstream applications need.
The following recommendations include delivery quality, JSON message structure, CloudEvents, schema and table metadata, transaction information, and handling of large values.
These settings provide a safe baseline for new users, which can then be adjusted after testing the stream with the intended workload and consumers.
| Setting | Recommended starting value | Reason |
|---|---|---|
| Quality of service | exactlyOnce |
Suppresses service-detectable duplicates and fails rather than silently skipping when a saved position is unavailable. |
| JSON model | op |
Preserves explicit before and after objects for CDC processing. |
| CloudEvents | false initially |
Start with the native GoldenGate record shape; enable CloudEvents when the integration standard requires it. |
| Schema records | true |
Allows the consumer to validate and discover every record type at runtime. |
| Object metadata | true |
Provides table column metadata and key information. |
| Stream metadata | true |
Provides producer and source context. |
| Metadata fields | qualifiedTable, opType, opTs, pos, xid, plus csn, opSeqno, transInd, and primaryKeys for enterprise consumers |
Supports routing, recovery, transaction analysis, and diagnostics without parsing pos. |
| Large values | Keep defaults until representative load testing is complete | Prevents unexpectedly large frames and memory pressure. |