|
|
Archives of the TeradataForum
Message Posted: Wed, 31 Mar 2004 @ 16:45:36 GMT
Subj: | | Re: Ab-Initio and "AMP lock table overflow" |
|
From: | | Walter, Todd A |
If a process does a very large number of single row operations (INSERT, UPDATE, DELETE) without performing a commit, Teradata will accumulate a
very large number of single row locks. These locks that are acquired singly will not be esclated to a table lock - that happens if we see it
coming while planning one request but not if it happens one record at a time. Using Teradata this way will also cause the entire set of updates to
be rolled back if the process fails, probably not what you intend.
I am not familiar with the O-table component. Obviously it is performing single row updates. Are you running it on an ANSI session where
autocommit is not in effect?
| |