 |
 |
Archives of the TeradataForum
Message Posted: Wed, 28 Jan 2009 @ 09:57:30 GMT
| Subj: | | Re: Concurrent change conflict on database -- try |
| |
| From: | | Victor Sokovin |
| | If any SQL in other session tries to resolve the column via an express request to DBC.TVFIELDS after delete in step (5) and between the
insert that happens in step (6) , then it will not find an entry and, depending on the circumstances, will result in a '3916', a '3598, or a
'3810' error. | |
| | DR 114480: Sporadic 3916 Requested Information not in Dictionary while collecting statistics. | |
| | has been closed as a duplicate of: | |
| | DR 120304: Provide a general solution for the concurrency issues in parser. | |
| | DR 120304 is considered as very high risk to implement within current GCA version, this fix is not targeted to a DBS version earlier than
TD 13 at this point of time. | |
This looks like an answer to the question Joseph and I posted in November 2005 in the following thread:
www.teradataforum.com/teradata/20051116_180435.htm
It's been a long time ago of course but I seem to recall that the issue was high priority back then as well, especially on the sales &
marketing level.
I don't know about this case but sometimes lowering priorities turns out to be beneficial. Teradata management, how about stopping the
marketing people from spreading false hopes, saving funds while doing that, and then investing more funds into the good old R&D again? Just an
idea.
Victor
| |
