This content has been marked as final. Show 3 replies
Yes , You can use the different version of OGG, No issues, But better to understand that patch usage , in case if that patch related to that your requirement (ex. in bi directional replication) then apply the same in to your source. in case if one way replication requirment then there is no chance for issues since your target environment OGG binary only having extra features.
user3608173 wrote:You can mix & match versions of GG, for example 10.4, 11.1, 11.2, 12.1, etc; just set the trail format to the lowest common denominator. For example if you have 10.4 and 11.2, set the trail format on the "capture" extract prm file to "format release 10.4". If you have 11.2 and 11.1, set the trail format on the capture process to "11.1". The default trail format for any release is the same as the release version of the software; e.g, GG v11.2 by default generates trail format release 11.2. You can always send an older trail format transparently to a newer version of GG; if sending a data from a newer version of GG to an older version (e.g., 11.2 => 11.1) then you must set the trail format. And once the trail format is established at the source "extract", it can't be changed downstream.
We need to syncronize data from one oracle db to another.
On the source db ,there is a goldengate in version 220.127.116.11.2
On the target db , there is a goldengate in version 18.104.22.168.2_05
It seems only little patch between that. Is there any problem to use these two different version OGG to syncronize data?