home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases.informix
- Path: sparky!uunet!amgen!chriss@sam.amgen.com
- From: chriss@sam.amgen.com (Chris Silvester)
- Subject: Re: Row locks
- Message-ID: <1992Nov17.225728.14983@amgen.com>
- Sender: news@amgen.com
- Nntp-Posting-Host: csilvester
- Organization: Amgen
- References: <1992Nov17.041550.11286@panix.com>
- Distribution: usa
- Date: Tue, 17 Nov 1992 22:57:28 GMT
- Lines: 28
-
- In article <1992Nov17.041550.11286@panix.com>, clay@panix.com (Clay Irving) writes:
- >
- > We've written a program that updates several rows in a table. We assumed that
- > we may run into locking problems since these rows may be updated by another
- > program. So... We test for the lock and if we can't lock the row, we issue
- > an error message to inform the user that one of the rows can not be locked --
- > someone else has it. Now, how can we find who's locking the row? Tbmonitor
- > shows me users with locks, but it doesn't indicate what the lock is...
- >
- > There has to be a better way?...
- >
- > --
- > Clay Irving Personal: clay@panix.com {...uunet, cmc12}!panix!clay
- > New York, New York Work: clay@garpac.com {...uupsi3, 4gen}!garpac!clay
- > --
- >
-
- Back in August, someone posted an article about a script that a gentlemen
- named Dave Schmitt wrote called "listlocks" that uses tbstat, isql, awk, sort,
- join, and tr to produce a listing of locks held by users. I got a copy of it
- from somewhere, modified it slightly for our environment, and it works great.
- I believe his email address is daves@csg.gss.mot.com if you want to try to
- contact him about his script...
-
- Good luck!
-
- Chris S.
-
-