Archives of the TeradataForum

Message Posted: Wed, 08 Dec 2004 @ 12:20:06 GMT

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

My theory is that many of your queries which reference the tables that are being used to build the respective JI are 'Locking For Read' instead of 'Locking for Access.' If this is the case, then the following will happen:

1) A 'Locking for Read' query is executing against one of the table used to build the respective JI (note, this step doesn't cause the problem; however, it increases the probability of the Error occuring)

2) The JI Build query (which requires 'Locking for Write' because of alterations to tableheaders) queues up behind the 'Locking for Read' query

3) All subsequent 'Locking for Read' queries come in and queue up behind the 'Locking for Write' (JI build)

4) Initial 'Locking for Read' query completes

5) JI Build ('Locking for Write') completes

6) All 'Locking for Read' queries queued up behind JI build receive Error 2641

This can happen anytime you alter a table's header (i.e., create JI, add hard and/or soft RI, etc.)

If your queries were 'Locking For Access' instead of 'Locking for Read', the chances of this happening are much smaller since no queues would be created. Without queues, you shouldn't recieve Error 2641.

Hope this helps...and someone please correct me if I've mis-spoken.

Thanks,

Clay

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