|
Archives of the TeradataForumMessage Posted: Thu, 26 Mar 2009 @ 16:35:07 GMT
We already have policies for blocking alerts, but it's already too late to learn about the locks. Since this are already after the fact. PMON only shows BLOCKING, not LOCKS. SHOWLOCKS only show HUT locks (i.e: ARCMAIN) , not transactional locks. What we would like to know if there is an active lock on the database/table somewhere (via SQL or command line) to integrated this into our monitoring system and get alerted. One example is if somebody is on BTEQ doing transaction QUERY (begin transaction... etc), and forgot or takes awhile to commit/rollback, we would like to see those. Same as an application doing transaction SQL, but hanged in the middle (or got caught up into something). We would like to run this LOCK Check beforehand before we run a big jobs late at night... We don't want to get called when blocking is already happening caused by a LOCK from way back 5hours ago, we would like to learn the locks ahead of time and take actions.
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||