Archives of the TeradataForum

Message Posted: Tue, 07 Dec 2004 @ 08:24:13 GMT

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

Hello,

I don't think this has anything to do with join indexes being fundamentally different to other indexes.

We've had the 2641-error in the following situation

Job 1 created a NUSI on table A.

During this process, Job 2 wanted to read table A.

We did not want to schedule Job 2 after Job 1 for good reasons, so some times Job 2 had to wait for read-lock on table A.

When Job 1 finished, Job 2 got a 2641 error "Table A was restructured. Resubmit".

In BTEQ Job 2 can automatically resubmit the request if RETRY is ON (which I believe is the default for BTEQ). This is accomplished by a ".SET ERRORLEVEL (2641) SEVERITY 0" command.

So maybe this is also happening to you - when creating the join index, or maybe some of the processes runs a little bit slower due to the (extra) join index, and therefore you get into this locking situation.

Ole Dunweber
Coop Nordic

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