Archives of the TeradataForum

Message Posted: Mon, 31 Aug 2010 @ 00:32:50 GMT

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

This generic DeadLock message could happen for many reasons. We had similar issues and there were multiple actions that we took. We found that each ETL had job logging statement into a specific table and this table was heavily used.

We have advised to appropriate logging statement to resolve the problem. For some cases, the logging table had a bad PI resulting in table level lock escalation.

You could try any of the above.

Good Luck!

Thanks,

Vinay Bagare

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