Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Wed, 30 Nov 2005 @ 19:56:46 GMT

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

Subj:   Re: How to leave an intentional lock for testing
From:   Al MacGowan

  Right; but I thought the OP wanted a utility-level lock, the one which, say, counts towards the magic limit of 15 concurrent utility loads (if we are talking about the limits prior to V2R6.1, the maximum should be set higher on the latest release but the limit still exists). I don't think this part of the test can be mimicked by transaction-level locks.  

Good call - The "transactional locking" doesn't work, as MLOAD just waits it out. (Found that the long way) - I'm trying to find a case where I can blow up an MLOAD on the target table .. Someone had mentioned a NULL into a NOT NULL column might do it. I'm working on that at the moment. Unfortunately, time and other tasks seem to always get in the way...

Alistair MacGowan
Senior Database Administrator

  <Prev Next>   <<First <Prev Next> Last>>  
  Top Home Privacy Feedback  
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 28 Jun 2020