Happy New Year! 🎉
Because nothing says “end of the year” like firing up a test lab, breaking a GoldenGate extract, and realizing that Oracle 11g still has unfinished business with you. I spent the last hours of the year chasing an error that politely reminded me: old databases never really retire — they just wait 😀
Nothing fancy. Just a simple setup. Or at least… that’s what I thought at the beginning.
The goal was straightforward: capture data from an Oracle 11gR2 (11.2.0.4) database using Oracle GoldenGate Integrated Extract, running from a centralized GoldenGate extract hub using remote integrated capture with a newer GoldenGate build (21c)
I’ve done this dozens of times with 12c and above. 11g though… well, 11g always has a way of reminding you that it’s old, but not that old 🙂
The Setup (Quick Context)
Source database: Oracle 11g Enterprise Edition 11.2.0.4 (OEL 7.x 64)
Capture mode: Integrated Extract
GoldenGate binaries: 21.x
Capture host: centralized GoldenGate extract hub using remote integrated capture(Linux OEL 8.X 64)
Simple test table, simple inserts.
Everything registered fine. Extract attached to LogMiner. No privilege errors. No Streams issues.
So far, so good. And then…
The Symptom :
Out of nowhere, the extract stopped. Running info all showed this … Opening the report file made it very clear this wasn’t a generic failure. Right at the bottom:
GGSCI (postgrequebec.quebdomain as ggreplication@DB11G) 31> info all
Program Status Group Lag at Chkpt Time Since Chkpt
MANAGER RUNNING
EXTRACT STOPPED EXT11G 00:00:00 00:11:14
GGSCI (postgrequebec.quebdomain as ggreplication@DB11G) 32> view report EXT11G
2025-12-30 15:41:53 INFO OGG-06604 Connected to database DB11G, CPU info: CPU Count 1, CPU Core Count 1, CPU Socket Count 1.
2025-12-30 15:41:53 INFO OGG-06618 Database DB11G Platform: Linux x86 64-bit.
2025-12-30 15:41:57 INFO OGG-02248 Logmining server DDL filtering enabled.
2025-12-30 15:41:59 INFO OGG-02068 Integrated capture successfully attached to logmining server OGG$CAP_EXT11G using OGGCapture API.
2025-12-30 15:41:59 INFO OGG-02089 Source redo compatibility version is: 11.2.0.4.0.
2025-12-30 15:41:59 INFO OGG-15446 Extract configured as resource group.
2025-12-30 15:41:59 INFO OGG-02086 Integrated Dictionary will be used.
2025-12-30 15:41:59 INFO OGG-02710 Database metadata information is obtained from source database.
2025-12-30 15:41:59 WARNING OGG-02901 Replication of UDT and ANYDATA from redo logs is not supported with the Oracle compatible parameter setting. Using fetch instead.
2025-12-30 15:41:59 INFO OGG-02776 Native data capture is enabled for Oracle NUMBER data type.
2025-12-30 15:41:59 INFO OGG-01971 The previous message, 'INFO OGG-02776', repeated 1 times.
Source Context :
SourceModule : [ggdb.ora.ddl]
SourceID : [../gglib/ggdbora/ddlora.c]
SourceMethod : [metadata_from_logminer]
SourceLine : [1270]
ThreadBacktrace : [15] elements
: [/home/gg_adminremote/ogghome_21c/libgglog.so(CMessageContext::AddThreadContext())]
: [/home/gg_adminremote/ogghome_21c/libgglog.so(CMessageFactory::CreateMessage(CSourceContext*, unsigned int, ...))]
: [/home/gg_adminremote/ogghome_21c/libgglog.so(_MSG_(CSourceContext*, int, CMessageFactory::MessageDisposition))]
: [/home/gg_adminremote/ogghome_21c/extract()]
: [/home/gg_adminremote/ogghome_21c/extract(RedoAPI::createInstance(ggs::gglib::ggdatasource::DataSource*, ggs::gglib::ggapp::ReplicationContext*))]
: [/home/gg_adminremote/ogghome_21c/extract(ggs::er::OraTranLogDataSource::setup())]
: [/home/gg_adminremote/ogghome_21c/extract(ggs::gglib::ggapp::ReplicationContext::establishStartPoints(char, ggs::gglib::ggdatasource::DataSourceParams const&))]
: [/home/gg_adminremote/ogghome_21c/extract(ggs::gglib::ggapp::ReplicationContext::initializeDataSources(ggs::gglib::ggdatasource::DataSourceParams&))]
: [/home/gg_adminremote/ogghome_21c/extract()]
: [/home/gg_adminremote/ogghome_21c/extract(ggs::gglib::MultiThreading::MainThread::ExecMain())]
: [/home/gg_adminremote/ogghome_21c/extract(ggs::gglib::MultiThreading::Thread::RunThread(ggs::gglib::MultiThreading::Thread::ThreadArgs*))]
: [/home/gg_adminremote/ogghome_21c/extract(ggs::gglib::MultiThreading::MainThread::Run(int, char**))]
: [/home/gg_adminremote/ogghome_21c/extract(main)]
: [/lib64/libc.so.6(__libc_start_main)]
: [/home/gg_adminremote/ogghome_21c/extract()]
2025-12-30 15:41:59 ERROR OGG-02912 Patch 17030189 is required on your Oracle mining database for trail format RELEASE 12.2 or later.
2025-12-30 15:41:59 ERROR OGG-01668 PROCESS ABENDING.
Understanding What Actually Went Wrong
This is one of those GoldenGate errors that looks scary but is actually very precise once you read it slowly. GoldenGate was telling me: “Hey, I’m trying to write trail records using a 12.2+ trail format, but your 11g database can’t mine redo in that format unless you patch it.”
Specifically: Integrated Extract defaults to newer trail formats. Oracle 11g cannot mine 12.2+ trail formats, unless you apply Patch 17030189 (logminer GG Dictionary support: missing attributes) on the 11g database home. And in most environments… patching 11g is not happening.
Here’s the subtle trap: You install GoldenGate 19c / 21c and configured Integrated Extract. You don’t explicitly set a trail format — GoldenGate assumes: “Modern source, modern trail”. But 11g is not modern, even 11.2.0.4, the best version of 11g, still has limits. So GoldenGate happily starts… and then politely crashes.
The Options on the Table .. At this point, there were only three real choices:
Option 1: Patch the 11g database “Apply Patch 17030189 to the database home”.
Pros: Allows newer trail formats
Cons: Risky, operationally heavy, often blocked by policy, definitely not “lab friendly”
Option 2: Force an Older Trail Format. Tell GoldenGate to behave like it’s 2012 again.
Pros: No database patching, fully supported, safe and predictable
Cons: You give up newer trail features (more on that later). for me, option 2 was the obvious choice and in fact for many where client don’t want to change anything on the 11g database as its old and so far stable or patching will require additional planning and change requests and other operational risks etc.
Option 3: Using a workaround by using in-build OGG script prvtlmpg.plb.
Pros: Simple, straight forward, fast.
Cons: In production environments, this workaround introduces additional operational and audit risk, requires database-side intervention, and often triggers formal change and approval processes. It is particularly inconvenient in remote or centralized GoldenGate architectures, where GoldenGate is intentionally decoupled from the source database host. Since it alters mining-side database behavior, it is less clean and less maintainable than applying the official Oracle patch or avoiding the issue altogether by enforcing a compatible trail format.
The Fix That I Used.
The fix itself was simple, but order matters. You stop the impacted extract, delete the existing trail (trail headers stores the format), update the extract param file with a new flagh/parameter “FORMAT RELEASE “. Recreate the trail file and start your extract.
GGSCI (postgrequebec.quebdomain as ggreplication@DB11G) 36> DELETE EXTTRAIL ./dirdat/e1
Deleting extract trail ./dirdat/e1 for Extract group EXT11G.
GGSCI (postgrequebec.quebdomain as ggreplication@DB11G) 38> ADD EXTTRAIL ./dirdat/e1, EXTRACT ext11g
EXTTRAIL added.
GGSCI (postgrequebec.quebdomain as ggreplication@DB11G) 41> view params EXT11G
EXTRACT ext11g
USERIDALIAS ogg_11g
TRANLOGOPTIONS INTEGRATEDPARAMS (MAX_SGA_SIZE 512)
EXTTRAIL ./dirdat/e1, FORMAT RELEASE 11.2
DISCARDFILE ./dirrpt/ext11g.dsc, APPEND, MEGABYTES 50
REPORTCOUNT EVERY 30 MINUTES, RATE
TABLE ELEVENGTOFABRIC.TESTREPLTAB;
GGSCI (postgrequebec.quebdomain as ggreplication@DB11G) 52> info all
Program Status Group Lag at Chkpt Time Since Chkpt
MANAGER RUNNING
EXTRACT RUNNING EXT11G 00:00:03 00:00:06
]The Moment of Truth —> Lag was moving. SCNs were advancing. Trail RBAs were increasing. No more abends. No more patch complaints. That’s when you know you’re done.
Why FORMAT RELEASE 11.2 Is Safe (and When It’s Not) ? Let’s be clear, this isn’t a hack. This is documented, supported behavior.
What You Lose —> Newer GoldenGate metadata, Some advanced DDL capture details, Newer datatype handling
What You Keep —> Full DML capture (INSERT / UPDATE / DELETE), Stability, Compatibility
Your sanity
For 11g source systems, especially ones you don’t want to touch, this is the correct trade off.
Final Thoughts
This issue is a perfect example of why GoldenGate work is never just about syntax. Everything was “correct”: Privileges, Integrated capture, Registration ..but one missing line quietly broke the entire pipeline. If you’re running 11g with modern GoldenGate, remember this: Old database. Old trail format or be ready to patch.
And honestly… forcing FORMAT RELEASE 11.2 was the smarter move in this case where we totally avoided any modifications on the source system and continue remote extraction.
Hope It Helped!
Prashant Dixit
Tales From A Lazy Fat DBA 