Archives of the TeradataForum
Message Posted: Thu, 01 Nov 2012 @ 22:14:16 GMT
Even in a production environment, you can test Locking Logger without impacting your users. Here's a simple example of how to test the impact of a Teradata Database lock:
An EXCLUSIVE lock or a HUT lock can block an ACCESS lock...
A simple test:
create database testdb as perm=1000000;
user1 issues: locking table testdb.testtbl in exclusive mode bt;
user2 issues: sel * from testdb.testtbl;
user1 issues: et;
In this scenario user2 will wait until user1 issues an et;...
If no other console utilities are active, dumplocklog will run in "screen 1" on the control node. You can monitor the results of the run by issuing: "cnsterm 1" from a command prompt on this node. This will take you to "screen 1" and you can monitor the response to your "cnsrun" input. To exit, enter "break-key".
|Copyright 2016 - All Rights Reserved|
|Last Modified: 23 Jun 2019|