GoldenGate - Oracle to MSSQL - handling DDL replication abends on replicat

Question

Sorry for the cross-post. I clearly failed to actually read the "there's a GoldenGate forum" sticky...
Hello -
Very much a GoldenGate noob here, so please excuse me if I fumble on the terms / explanations - still learning.
We've recently been lucky enough to have a GoldenGate pump put into our campus environment to support our data warehouse. We don't manage the pump or source systems - just the target.
Pump: GoldenGate 11.1.1.1
Source: Oracle 11g
Target: MSSQL 2008R2
~5,000 tables of hugely varying sizes
The extract is apparently configured to push DDL changes, which is clearly not going to work with a MSSQL 2008 R2 target. We're getting abend messages on the replicat and I'd like to know if we can bypass them on the replicat or need to ask that the extract process be modified to exclude DDL operations.
The replicat error logs show exception:
OGG-00453: DDL Replication is not supported for this database
On the replicat I've tried including:
DDL EXCLUDE ALL
DDLERROR DEFAULT DISCARD (or DDLERROR DEFAULT IGNORE - neither let the process continue)
The replicat just abends with the same OGG-00453 exception.
My question: Can I gracefully handle these abends on the replicat? Or do I need to request the extract be updated with "DDL EXCLUDE ALL." Ideally, we can handle this on the replicat - I'm trying to be considerate of the main GoldenGate admin's time and also avoid any disruption of the extract.
Any direction / info / ideas much appreciated.
Thank you,
Eric

Answer 1

924681 wrote:
Sorry for the cross-post. I clearly failed to actually read the "there's a GoldenGate forum" sticky...
Hello -
Very much a GoldenGate noob here, so please excuse me if I fumble on the terms / explanations - still learning.
We've recently been lucky enough to have a GoldenGate pump put into our campus environment to support our data warehouse. We don't manage the pump or source systems - just the target.
Pump: GoldenGate 11.1.1.1
Source: Oracle 11g
Target: MSSQL 2008R2
~5,000 tables of hugely varying sizes
The extract is apparently configured to push DDL changes, which is clearly not going to work with a MSSQL 2008 R2 target. We're getting abend messages on the replicat and I'd like to know if we can bypass them on the replicat or need to ask that the extract process be modified to exclude DDL operations.
The replicat error logs show exception:
OGG-00453: DDL Replication is not supported for this database
On the replicat I've tried including:
DDL EXCLUDE ALL
DDLERROR DEFAULT DISCARD (or DDLERROR DEFAULT IGNORE - neither let the process continue)
The replicat just abends with the same OGG-00453 exception.
My question: Can I gracefully handle these abends on the replicat? Or do I need to request the extract be updated with "DDL EXCLUDE ALL." Ideally, we can handle this on the replicat - I'm trying to be considerate of the main GoldenGate admin's time and also avoid any disruption of the extract.
Any direction / info / ideas much appreciated.
Thank you,
EricI find strange that DDLERROR DEFAULT IGNORE does not work, are you sure you placed it properly? did you restarted the replicats after doing the change?
Why dont you try specifying the error like:
DDLERROR <error> IGNORE