New Features for DBA’s

Subscribe to Posts by Email


 

Subscriber Count

    696

Disclaimer

All information is offered in good faith and in the hope that it may be of use for educational purpose and for Database community purpose, but is not guaranteed to be correct, up to date or suitable for any particular purpose. db.geeksinsight.com accepts no liability in respect of this information or its use. This site is independent of and does not represent Oracle Corporation in any way. Oracle does not officially sponsor, approve, or endorse this site or its content and if notify any such I am happy to remove. Product and company names mentioned in this website may be the trademarks of their respective owners and published here for informational purpose only. This is my personal blog. The views expressed on these pages are mine and learnt from other blogs and bloggers and to enhance and support the DBA community and this web blog does not represent the thoughts, intentions, plans or strategies of my current employer nor the Oracle and its affiliates or any other companies. And this website does not offer or take profit for providing these content and this is purely non-profit and for educational purpose only. If you see any issues with Content and copy write issues, I am happy to remove if you notify me. Contact Geek DBA Team, via geeksinsights@gmail.com

Pages

Example 16: Different Versions of Goldengate Replication

Is it possible to have goldengate replicate between 10g database and 11g database or viceversa.

Answer, Yes.

Its not the databases versions , since Since goldengate trail files are independent to database and they contain their own format of trail files by reading redo/archive log files. And this trail files are only means for replication.

But if the target version of goldengate is lower than source version then this could be an issue, due to header format maintain the version in extract trail files.

Consider this scenario

Source Target
11gR2 Database 10G/11gR1 Database
11gR2 GG Software 11GR1 GG Software
Extract will generate trails in 11gR2 Format Replicat will try to read those extract trail and file with

ERROR OGG-01389 File header failed to parse tokens. File /data/ggate/ex10919, last offset 100, data: 0x

To overcome this, The extract parameter FORMAT must be added to target version so that extract maintains the trail file headers in lower version format as like target. As you see the format release is matched with target gg version above.

./ggsci

edit params ext3

extract ext3
userid ggs_owner, password ggs_owner
rmthost 192.168.56.109, mgrport 7809
rmttrail /data/ggate/ex00, format release 11.1
table test.myobj6;

Once added, alter the extract to start over from next trail file using etrollover. (new sequence will be generated)
ggsci> alter extract ext3, etrollover

On Target side, alter the replication process to start read from new extrail sequence

ggsci> alter replicat rep1 extseqno 1

Should now the replicate process proceed without issue.