This discussion is archived
1 Reply Latest reply: Apr 19, 2012 8:29 PM by user11188564 RSS

BDBSQL and db_stat (locks) report - not correct

user11188564 Newbie
Currently Being Moderated
The db_stat report when used for BDBSQL is not a valid report. It shows entires for threads/processes which no longer exists. Also, I have a thread that shows in a "WAIT" state that is not waiting for a lock - it is not even in a BDB call (confirmed by pstack) : Here is a sample report

25 READ 1 HELD sandm.db:table01102 handle 14085
25 READ 1 HELD sandm.db:table01102 handle 0
800049dd dd= 7 locks held 0 write locks 0 pid/thread 12020/1 flags 8 pr
iority 100
800000b3 dd=29 locks held 0 write locks 0 pid/thread 5464/1 flags 8 pri
ority 100
800000b4 dd=28 locks held 0 write locks 0 pid/thread 5466/1 flags 8 pri
ority 100
2b dd=25 locks held 1 write locks 0 pid/thread 5464/5 flags 10 pri
ority 100
2b WRITE 1 WAIT sandm.db:table01102 handle 8279
2b READ 3 HELD sandm.db:table01102 handle 0
800049e7 dd= 6 locks held 0 write locks 0 pid/thread 12020/1 flags 8 pr
iority 100
31 dd=24 locks held 1 write locks 1 pid/thread 5464/5 flags 10 pri
ority 100
31 WRITE 1 HELD sandm.db:table01102 handle 14875
800000c0 dd=27 locks held 0 write locks 0 pid/thread 5464/1 flags 8 pri
ority 100
37 dd=23 locks held 2 write locks 1 pid/thread 5464/5 flags 10 pri
ority 100
37 WRITE 1 HELD sandm.db:table01102 handle 14385
37 READ 6 HELD sandm.db:table01102 handle 0


Thread 5464/5 is not insidea /bdb call - I have verified this by using a pstack call.

Thanks for your help.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points