looping on db2 get snapshot for locks on <db>

[aj]

DB2 WSE 8.1 FP5
Red Hat AS 2.1

I'm trying to monitor locks in my DB by running the following
shell script:

while true
do
db2 get snapshot for locks on <db> | head -9
sleep 3
done

When I run this, I get *lots* of the following in db2diag.log
as the shell script loops:

2005-03-18-13.20.44.197579 Instance:oltp Node:000
PID:23453(db2) TID:8192 Appid:none
oper system services sqloclose Probe:110

errno:
0xBFFEA8F4 : 0x00000009 ....

Why is this? How can I avoid filling up db2diag.log? Is there
an alternative?

TIA

allen

[Matt Emmerton]

"aj" <ro****@mcdonalds.com> wrote in message
news:11*************@news.supernews.com...

DB2 WSE 8.1 FP5
Red Hat AS 2.1

I'm trying to monitor locks in my DB by running the following
shell script:

while true
do
db2 get snapshot for locks on <db> | head -9
sleep 3
done

When I run this, I get *lots* of the following in db2diag.log
as the shell script loops:

2005-03-18-13.20.44.197579 Instance:oltp Node:000
PID:23453(db2) TID:8192 Appid:none
oper system services sqloclose Probe:110

errno:
0xBFFEA8F4 : 0x00000009 ....

Why is this? How can I avoid filling up db2diag.log? Is there
an alternative?

errno 0x00000009 = EBADF (bad file descriptor).

My guess is that once 'head' outputs out first 9 lines of the snapshot
output, it closes it's end of the pipe, and that causes DB2 to get an error
while attempting to output more information to the pipe since the pipe has
been closed.

Try the following instead and see if it makes the error messages go away:

while true
do
db2 get snapshot for locks on <db> > snap.lock
head -9 snap.lock
sleep 3
done

--
Matt Emmerton

[aj]

Worked perfectly. Thanks Matt.

aj

Matt Emmerton wrote:

"aj" <ro****@mcdonalds.com> wrote in message
news:11*************@news.supernews.com...

DB2 WSE 8.1 FP5
Red Hat AS 2.1

I'm trying to monitor locks in my DB by running the following
shell script:

while true
do
db2 get snapshot for locks on <db> | head -9
sleep 3
done

When I run this, I get *lots* of the following in db2diag.log
as the shell script loops:

2005-03-18-13.20.44.197579 Instance:oltp Node:000
PID:23453(db2) TID:8192 Appid:none
oper system services sqloclose Probe:110

errno:
0xBFFEA8F4 : 0x00000009 ....

Why is this? How can I avoid filling up db2diag.log? Is there
an alternative?

errno 0x00000009 = EBADF (bad file descriptor).

My guess is that once 'head' outputs out first 9 lines of the snapshot
output, it closes it's end of the pipe, and that causes DB2 to get an error
while attempting to output more information to the pipe since the pipe has
been closed.

Try the following instead and see if it makes the error messages go away:

while true
do
db2 get snapshot for locks on <db> > snap.lock
head -9 snap.lock
sleep 3
done

--
Matt Emmerton