Archives of the TeradataForum

Message Posted: Fri, 07 Nov 2003 @ 22:34:06 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Rishi,

First, you need to determine the root cause of the deadlock. The Informatica message you provided suggests that this is a Teradata RDBMS error 2631. Typically this occurs when one transaction has a lock on a resource that another transaction is trying to obtain. This can be resolved by managing the workload schedule.

If the problem is easily repeatable, you might want to monitor the process through PMON to identify the object in contention. If not, the best way to monitor lock contention is to us Locking Logger. A thread on Locking Logger was recently completed. You might want to check the archives and also read up on the DumpLockLog utility.

2631 errors can also, infrequently, be caused as a result of contention on a system resource. These are more difficult to identify. The best way to identify if this problem is occurring is to check Locking Logger. If transaction that failed due to a 2631 is NOT in the Locking Logger, that means that the 2631 error was note caused by contention on a database object. Therefore, it is due to a deadlock on a system resource. The root cause and subsequent solution to this type of problem is much more difficult.

Hope this helps.

Regards,

Thomas F. Stanek
TFS Consulting, Inc.

www.tfsconsulting.com

	<Prev	Next>		<<First	<Prev	Next>	Last>>