RE: Golden Gate and table sync checking
- From: "Crisler, Jon" <Jon.Crisler@xxxxxxx>
- To: <dmann99@xxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Fri, 15 Oct 2010 17:07:17 -0400
The user wants the ability to do active-active replication, but there
appears to be limited to no conflict resolution. What happens if the
user updates the secondary DB with info that conflicts with the primary
? Also, Shareplex already had a compare / repair utility for table
checking....seems odd that one would have to buy another option for GG
to do that. I would think that would be a firm requirement for the
basic product.
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of David Mann
Sent: Friday, October 15, 2010 4:50 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: Re: Golden Gate and table sync checking
Best bet is to use VeriData unless you have some other way to check. If
you are just interested in making sure records appear on the target then
you can do a minus query across a DB link. If you want to make sure
every field matches, rolling you own method will be a resource-intensive
pain.
I have used the early versions of Veridata for Oracle->Oracle
comparisons. We had the same tables and schema structure on source and
target (no ETL or anything to complicate issues)... we were just using
GoldenGate for data movement so long running reports reports didn't have
to run against an OLTP databases.
Behind the scenes it calculated a checksum for each row and compared the
source rows to the target rows. Generally more efficient than comparing
the two table outright. If the row checksum differed then I believe it
will do some more inspection to determine what columns are different
between the source and target. The version I used only reported issues,
did nothing to resolve them. Newer versions may have more functionality.
--
Dave Mann
www.brainio.us
www.ba6.us - Database Stuff - http://www.ba6.us/rss.xml
Other related posts:
