Archives of the TeradataForum

Message Posted: Wed, 24 Sep 2003 @ 14:11:36 GMT

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

Ivan,

Did you check for leftover HUTLOCKS from a previous ARCMAIN job? If there were no residual HUTLOCKS, you could run Locking Logger from Teradata Manager using to/from dates/times that cover the period when the problem occurred. Locking Logger is an interface to the dumplocklog console utility of the Teradata RDBMS software - note that the locklogger field in DBS Control must be enabled.

To create the report, Locking Logger joins your generated Lock Log Table with the system DBC.EventLog table to find blocked and blocking user names. You could then join your locklog table to the DBC.AccessLog by session number and date to isolate the suspect sql.

Hope this is helpful...

Lisa

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