Archives of the TeradataForum
Message Posted: Fri, 05 Dec 2003 @ 13:22:36 GMT
The PMON could as well tell you about the various locked scenarios in Teradata and can be used to abort the sessions too.
If the object is locked by utility locks (e.g. arc locks, this happens if you do not specify release lock in your archive script) then you may issue 'release lock db_name.table_name' from bteq.
release lock load_db.t1; *** Command accepted. *** Total elapsed time was 1 second. BTEQ -- Enter your DBC/SQL request or BTEQ command:
There is another mechanism for lock manipulations, but I feel it is NOT MEANT FOR EVERYONE !!!!!
I rather suggest not to use it ever & do it by aborting the sessions properly as lock manipulations may lead to invalid session contexts which may result in serious problems.
This is very obvious from the Warning that comes up at the time of program invocation itself.
/tpasw/bin>lokcns Warning! This program provides capability to create dummy locks or release a lock. This program is not intented for customer used and is existed solely to unit test certain lock manager function. Any problem resulted from execution of this program. will not be responsible by NCR. Action: [S]et normal lock/Set [M]essage lock, [R]elease lock/Release s[P]ecific lock, [I]nit/[T]erminate row range, Retain [C]ertain locks, Query lock m[O]de, [A]bort a trans. [Q]uit. Enter S, M, R, P, I, T, C, O, A or Q. Q
|Copyright 2016 - All Rights Reserved|
|Last Modified: 23 Jun 2019|