-
Title
Why does compare lock Production tables when SharePlex Source database is a Oracle standby database? -
Description
SharePlex Source database is an Oracle standby database but when compare is executed it creates the consistency table locks on the Production database. Why is this? -
Cause
Compare/Repair will lock the table it is comparing on the Production database that feeds the Oracle Standby Database. This is as per design, SharePlex uses Oracle standby database for reading archive redo logs alone.
-
Resolution
In the same way that SharePlex creates the SharePlex user and internal tables on the Production database rather than the Source Standby database, the compare/repair utility will lock the table to be compared on the Production database so that it can obtain a consistent view of the data.
When SharePlex is installed and ora_setup executed, the TNS entry for the Production database is requested so that SharePlex can connect and create the SharePlex user and internal tables.
So it is correct that the compare/repair lock it on the Production database rather than the Source Standby database.