Archives of the TeradataForum
Message Posted: Fri, 18 Jun 2004 @ 11:30:29 GMT
This may not solve your particular problem (others seems to have done that), but I would like to comment on the error "%DBID.%TVMID was restructured. Resubmit." (errorcode 2641).
We had this 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".
I must admit, that I find this quite absurd - it's not something I have seen in any other database. As stated the "error" disappears when resubmitting, without any further action. In other databases Job 2 might get a timeout, but this is for some reason not build into Teradata. Any way, 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 someone would comment on this peculiar 2641-error, and maybe also why Teradata does not support timeout on locks. We have seen locks being held by daytime-users for a very long time (during the night), without anyone noticing - a timeout would discover this. Though the default timeout-level probably need to be rather high in datawarehousing, it would be very nice to have the functionality.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|