Archives of the TeradataForum

Message Posted: Mon, 06 Dec 2004 @ 16:25:07 GMT

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

Last night, during our nightly ETL window, several queries received the "2641 %DBID.%TVMID was restructured. Resubmit." error. This is the second occurrence of this error since adding a join index on a table a couple of weeks ago. According to the Teradata documentation, this error can occur when querying a table whose secondary index or join index is being added or dropped, or when the table is being renamed, among other things. We have been adding/dropping secondary indexes and renaming tables during the nightly ETL window for a couple of years now, but we NEVER saw this error until we added the join index a couple of weeks ago. I suspect there is something fundamentally different about join indexes that makes this error's window of opportunity greater. Perhaps the window of opportunity lasts for the duration of the join index's creation? Perhaps this is the same case for a secondary index, but the join index simply takes longer to create than a secondary index (in this case) which increases this error's window of opportunity? Has anyone experienced this?

thanks,

Cliff Theiss

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