How to proactively look for out of sync for all tables in replication?
Since Shareplex only reports an out of sync once it encounters the out of sync condition, you will not be able to see all hidden out of sync on target by simply issuing “show sync”. A proactive way to do it would be to either create a config file containing all tables in replication, or if the number of tables is very large, create multiple config files so that each of them contain a subset of replicating tables and in the process include all replicating tables in one of such config files. You can then issue the command “compare using <config file>” or “compare using <config file> quickcheck” via sp_ctrl on these config files at different time so as to ascertain that the tables contained in such config files are in sync:
On source:
sp_ctrl>compare using <config file>
or
sp_ctrl>compare using <config file> quickcheck
The advantage of using the “quickcheck” option is that the compare will stop when encountering the first out of sync and in the process will avoid comparing the complete table. This will save time. If running compare on all tables in replication at once, you may have problems if the tables are very large and/or the # of such tables is very large. This is the reason you can split them into various config files. If wishing to fix the out of sync proactively, you can use “repair using” instead of “compare using”. You can also use “copy using <config file>” instead of “rapair using”. The copy will work much faster than repair but is not recommended for a two way replication as the corrective messages applied by Oracle’s Import utility on the secondary side would loop back to primary and this is undesirable. Another thing to note is, the config file need not necessarily be the active config file.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center