This content has been marked as final. Show 2 replies
For comparing the source/target databases you can use the DBMS_COMPARISON package.
For checking that streams is replicating OK - it's common to have a 'heartbeat' table - which is frequently updated with the current date in the source, a check is then ru in the destination that the date in the table is near current date.
grid/cloud control also has built in metrics for this if you use that.
Is there a mechanism that the source are target tables are compared on real time basis and notifications being sent informing that there is a problem ?The mechanism exists (mentioned above). But may be too expensive to execute it.
It would be more efficient to implement:
1) automatic data collision resolution
2) monitoring of queue sizes of Streams