6. Using the Replicator Server : How Server Behavior Is Controlled : Server Processing Activity : Lock Contention Detection
 
Share this page                  
Lock Contention Detection
From the first time a record is manipulated in a distributed transaction until the last record of that transaction is processed, records applicable to the transaction are locked in the local and the target database and remain locked until the final COMMIT (or ROLLBACK) statement is issued.
Lock timeout is controlled by the Lock Timeout (-TOTn) flag, where n is the number of seconds. Ingres Replicator waits to obtain a lock before aborting the transaction and reprocessing the replication. The recommended value for n is 30 or greater. The default value is 60. The -TOTn flag can only be set in the configuration file; therefore, to change the value of -TOTn, you must stop and restart the server after editing the configuration file.
Important!  If deadlocking is a problem in your environment, replication can make the situation worse. If you are unable to resolve a deadlock, see Strategies for Avoiding Deadlock (see page Strategies for Avoiding Deadlock. If the problem persists, contact Customer Support for assistance.