Archives of the TeradataForum
Message Posted: Wed, 25 Feb 2003 @ 21:33:07 GMT
The behaviour is completely as expected of Teradata.
The advantage of using Deleting a table with MLOAD far outweigh the advantages of SQL Delete. Remeber that in MLOAD Delete you have the maximum possible access to the Table rather than SQL Delete and it is restartable too (from where it left last time after Teradata recovery), with no Transient Journal. It is only in the Application phase that you will not have access to the table and you must have accessed this table in the Application Phase. Check the MLOAD logs to see where MLOAD process is at that moment.
If you still want to access info during this MLOAD phase use an ACCESS Lock, which is compatible.
You get hell lot of info from MLOAD logs again not possible in SQL processes.
In the second example of yours, if there is WRITE LOCK a READ LOCK will also work and that is why you get the output. A Write Lock and then a Read Lock are compatible. Not the reverse.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|