db2cos script

[4.spam]

Hello.

v8.2.7 ese, WinXP

I'm trying to catch locktimeout.

1.
I issued:
db2pd -catch -911,68 db2cos
output was:
---
Error Catch #1
Sqlcode: -911
ReasonCode: 68
ZRC: 0
ECF: 0
Component ID: 0
LockName: Not Set
LockType: Not Set
Current Count: 0
Max Count: 255
Bitmap: 0x661
Action: Error code catch flag enabled
Action: Execute sqllib/db2cos callout script
Action: Produce stack trace in db2diag.log
---

2.
I created db2cos.bat file in sqllib directory with such command:
---
db2pd -db sample -locks wait -app "C:\Program Files\IBM\SQLLIB
\db2cos.rpt"
---
and reproduced simple lockwait situation.

When I run this script manually, it works and create output file with
some data.
But it seems that this db2cos script is not called automatically after
detecting locktimeout.
In the db2diag.log there are no entries like this:
---
START : Invoking sqllib/db2cos script from lock manager sqlplnfd
---
and only such entries:

--- db2diag.log entry ---
2007-05-07-09.55.00.546000+240 I4522374H842 LEVEL: Event
PID : 864 TID : 2160 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SAMPLE
APPHDL : 0-9 APPID: *LOCAL.DB2.070507051925
FUNCTION: DB2 UDB, lock manager, sqlplnfd, probe:999
DATA #1 : <preformatted>
Caught rc -2146435004. Dumping stack trace.
CALLSTCK:
[0] 0x6E1EBEC0 sqlpErrorCatchForPD + 0x17C
[1] 0x6E1EB711 sqlplnfd + 0xA15
[2] 0x6E1A7907 sqlplrq + 0x8DB
[3] 0x6E177F1D sqlischf + 0x2AF9
[4] 0x6E17632D sqlischf + 0xF09
[5] 0x6E175687 sqlischf + 0x263
[6] 0x6E1575A4 ?
sqliFirstTreeSearch.@@YAHPAUSQLI_CB@@PAUSQLI_SFGLO B@@@Z + 0x30
[7] 0x6E156B43 sqlirdk + 0x647
[8] 0x6E0BD38C ?sqldIndexFetch.@@YAHPAUSQLD_CCB@@PAK@Z + 0xF4
[9] 0x6E0BC4B8 sqldRowFetch + 0x84E
--- db2diag.log entry end ---

Question is:
have I something missed?

Thanks in advance,
Mark B.

[Jeroen van den Broek]

On May 7, 9:17 am, [e-mail] wrote:

Hello.

v8.2.7 ese, WinXP

I'm trying to catch locktimeout.

1.
I issued:
db2pd -catch -911,68 db2cos
output was:
---
Error Catch #1
Sqlcode: -911
ReasonCode: 68
ZRC: 0
ECF: 0
Component ID: 0
LockName: Not Set
LockType: Not Set
Current Count: 0
Max Count: 255
Bitmap: 0x661
Action: Error code catch flag enabled
Action: Execute sqllib/db2cos callout script
Action: Produce stack trace in db2diag.log
---

2.
I created db2cos.bat file in sqllib directory with such command:
---
db2pd -db sample -locks wait -app "C:\Program Files\IBM\SQLLIB
\db2cos.rpt"
---
and reproduced simple lockwait situation.

When I run this script manually, it works and create output file with
some data.
But it seems that this db2cos script is not called automatically after
detecting locktimeout.
In the db2diag.log there are no entries like this:
---
START : Invoking sqllib/db2cos script from lock manager sqlplnfd
---
and only such entries:

--- db2diag.log entry ---
2007-05-07-09.55.00.546000+240 I4522374H842 LEVEL: Event
PID : 864 TID : 2160 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SAMPLE
APPHDL : 0-9 APPID: *LOCAL.DB2.070507051925
FUNCTION: DB2 UDB, lock manager, sqlplnfd, probe:999
DATA #1 : <preformatted>
Caught rc -2146435004. Dumping stack trace.
CALLSTCK:
[0] 0x6E1EBEC0 sqlpErrorCatchForPD + 0x17C
[1] 0x6E1EB711 sqlplnfd + 0xA15
[2] 0x6E1A7907 sqlplrq + 0x8DB
[3] 0x6E177F1D sqlischf + 0x2AF9
[4] 0x6E17632D sqlischf + 0xF09
[5] 0x6E175687 sqlischf + 0x263
[6] 0x6E1575A4 ?
sqliFirstTreeSearch.@@YAHPAUSQLI_CB@@PAUSQLI_SFGLO B@@@Z + 0x30
[7] 0x6E156B43 sqlirdk + 0x647
[8] 0x6E0BD38C ?sqldIndexFetch.@@YAHPAUSQLD_CCB@@PAK@Z + 0xF4
[9] 0x6E0BC4B8 sqldRowFetch + 0x84E
--- db2diag.log entry end ---

Question is:
have I something missed?

Thanks in advance,
Mark B.

I'm not familiar with DB2 on Windows, so can't offer you a proven
advice.
However, as your 'script' is named 'db2cos.bat', maybe in your db2pd
command you should refer to it that way, i.e. including the .bat-
suffix? Like:
db2pd -catch -911,68 db2cos.bat

HTH

--
Jeroen

[4.spam]

Ok, I rearrange my questions:
1.
Has somebody successfully tuned call of the db2 call out script on
v8.2 on Windows?

2.
Another question:
I want to catch locktimeout situation AUTOMATICALLY with such info:
- which statement caused locktimeout
- which statement wait for lock
Is it possible at all on v8.2 on Windows?

Thanks in advance,
Mark B.