|
Archives of the TeradataForumMessage Posted: Thu, 03 Feb 2011 @ 13:54:40 GMT
Hi Sanjeev, Let me correct my previous statement: the relase mload function is executed BEFORE the multiload starts. I guess the developers wanted to be sure that there is no lock from previous failed MLOAD jobs. Anyway, I can't really question that logic right now, so let's just accept it as a fact. So it seems that the function could not obtain an exclusive lock on the table, right? In this case, release mload function waits or it gives an error? I assume it waits, because it is not a deadlock situation. So, it would mean that there was some kind of lock (read, hash or any other) that avoids release mload function to obtain an exclusive lock. Am I right? Thanks, Tomas Gorner
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||