Compare fails with "ERROR: Uable to lock table/row "owner"."tablename" to maintain consistent vie (4291857)

When running compare, the compare errors out and the following errors are observed in the compare logs (*sp_desvr* logs) located in source's $SP_SYS_VARDIR/log directory:

061: COMPARE CURRENT STATUS:Thu Jun 18 09:35:02 2009 (elapsed 6.434288 seconds),  FAILED to lock table/rows. (de_trans_get_read_consistent_view,L1443:de_log_line,L323)
061: ERROR: Uable to lock table/row "owner"."tablename" to maintain consistent view; see name_desvr-14043-*.log for detail (de_thrdmgr_sub_main,L1409:de_trans_get_read_consistent_view,L1471)

Compare is not able to lock the source table briefly to get a snapshot.

Compare needs to lock the source and target tables for a very brief period.  This is to get the consistent view of source and target rows. This locking is non-intrusive for the most part. If, however, some long running, uncommitted transactions exist on source table, then this will interfere with the locking. The workaround may be to run compare during lean times or run it again with the hope that the transactions will be committed in due course and will not interfere with compare.

It may be noted that during the repair phase the target table is locked and this lock can be intrusive in the sense that users may not be able to access the target table during that time for making changes. On target this should not be an issue since there is no direct user activity on target tables.