Re: Sudden logical log overuse??

In article <2c2u1k$s9s$1@DIALix.oz.au> rob@DIALix.oz.au (Rob Mascaro) writes: >Hi, >Can someone point me in the right direction to look for logical log >space filling up too fast. ... >How can I determine what the problem is?? >Thanks, >Rob. Look at your tbstat -u command. Do a ps -fp <pid> on each of the PIDs. Which is the oldest? That might be the one. Look at the Locks column on tbstat -u. That might be the one. The only way to tell for sure is to do a tblog on the current log. Look for checkpoint records. The user that did a BEGIN WORK first, and has not yet committed is the one who is holding your logs. Jim Burks jburks@promus.com Database Administrator The Promus Companies Memphis, TN