db2diaglog errors

[yerim y via DBMonster.com]

Hello there,
I am having these recurring errors on the diaglog of my DB2 server and they
are the same ones on all databases. Can someone please help me diagnose it.
What's making me nervous is the level is marked as severe.

Thank you

2005-09-10-06.18.53.984000-240 I1005918H397 LEVEL: Severe
PID : 1192 TID : 1984 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : PSU
APPHDL : 0-56 APPID: O0760528.M304.015F40101857
FUNCTION: DB2 UDB, database monitor, sqm___start_evmon, probe:40
RETCODE : ZRC=0x800D002C=-2146631636=SQLM_RC_EVPATH "path in use"

2005-09-10-06.18.54.000000-240 I1006317H456 LEVEL: Severe
PID : 1192 TID : 1984 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : PSU
APPHDL : 0-56 APPID: O0760528.M304.015F40101857
MESSAGE : event monitor name
DATA #1 : Hexdump, 17 bytes
0x659D0958 : 4442 3244 4554 4149 4C44 4541 444C 4F43 DB2DETAILDEADLOC
0x659D0968 : 4B K

2005-09-10-06.18.54.000000-240 I1006775H608 LEVEL: Severe
PID : 1192 TID : 1984 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : PSU
APPHDL : 0-56 APPID: O0760528.M304.015F40101857
MESSAGE : event monitor target
DATA #1 : Hexdump, 51 bytes
0x659D0980 : 453A 5C44 4232 5C4E 4F44 4530 3030 305C E:\DB2\NODE0000\
0x659D0990 : 5351 4C30 3030 3032 5C44 4232 4556 454E SQL00002\DB2EVEN
0x659D09A0 : 545C 6462 3264 6574 6169 6C64 6561 646C T\db2detaildeadl
0x659D09B0 : 6F63 6B ock

2005-09-10-06.18.54.015000-240 I1007385H445 LEVEL: Severe
PID : 1192 TID : 1984 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : PSU
APPHDL : 0-56 APPID: O0760528.M304.015F40101857
FUNCTION: DB2 UDB, database monitor, sqm___evmgr::log_ev_err, probe:1
MESSAGE : DiagData
DATA #1 : Hexdump, 4 bytes
0x01F88884 : 2C00 0D80 ,...
--
Message posted via DBMonster.com
http://www.dbmonster.com/Uwe/Forums....m-db2/200509/1

[Serge Rielau]

yerim y via DBMonster.com wrote:

Hello there,
I am having these recurring errors on the diaglog of my DB2 server and they
are the same ones on all databases. Can someone please help me diagnose it.
What's making me nervous is the level is marked as severe.

Thank you

2005-09-10-06.18.53.984000-240 I1005918H397 LEVEL: Severe
PID : 1192 TID : 1984 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : PSU
APPHDL : 0-56 APPID: O0760528.M304.015F40101857
FUNCTION: DB2 UDB, database monitor, sqm___start_evmon, probe:40
RETCODE : ZRC=0x800D002C=-2146631636=SQLM_RC_EVPATH "path in use"

2005-09-10-06.18.54.000000-240 I1006317H456 LEVEL: Severe
PID : 1192 TID : 1984 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : PSU
APPHDL : 0-56 APPID: O0760528.M304.015F40101857
MESSAGE : event monitor name
DATA #1 : Hexdump, 17 bytes
0x659D0958 : 4442 3244 4554 4149 4C44 4541 444C 4F43 DB2DETAILDEADLOC
0x659D0968 : 4B K

2005-09-10-06.18.54.000000-240 I1006775H608 LEVEL: Severe
PID : 1192 TID : 1984 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : PSU
APPHDL : 0-56 APPID: O0760528.M304.015F40101857
MESSAGE : event monitor target
DATA #1 : Hexdump, 51 bytes
0x659D0980 : 453A 5C44 4232 5C4E 4F44 4530 3030 305C E:\DB2\NODE0000\
0x659D0990 : 5351 4C30 3030 3032 5C44 4232 4556 454E SQL00002\DB2EVEN
0x659D09A0 : 545C 6462 3264 6574 6169 6C64 6561 646C T\db2detaildeadl
0x659D09B0 : 6F63 6B ock

2005-09-10-06.18.54.015000-240 I1007385H445 LEVEL: Severe
PID : 1192 TID : 1984 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : PSU
APPHDL : 0-56 APPID: O0760528.M304.015F40101857
FUNCTION: DB2 UDB, database monitor, sqm___evmgr::log_ev_err, probe:1
MESSAGE : DiagData
DATA #1 : Hexdump, 4 bytes
0x01F88884 : 2C00 0D80 ,...

What a great opportunity to introduce a new tool:
http://publib.boulder.ibm.com/infoce...e/r0011728.htm

db2diag -rc

Input ZRC string 'SQLM_RC_EVPATH' parsed as 0x800D002C (-2146631636).

ZRC value to map: 0x800D002C (-2146631636)
V7 Equivalent ZRC value: 0xFFFF8E2C (-29140)

ZRC class :
SQL Error, User Error,... (Class Index: 0)
Component:
SQLM ; database monitor (Component Index: 13)
Reason Code:
44 (0x002C)

Identifer:
SQLM_RC_EVPATH
Identifer (without component):
SQLZ_RC_EVPATH

Description:
path in use

Associated information:
Sqlcode -1618
SQL1618N The target path of the specified event monitor is in use by
another
event monitor.

Number of sqlca tokens : 0
Diaglog message number: 1
db2 "? SQL1618"

SQL1618N The target path of the specified event monitor is in
use by another event monitor.

Explanation:

The specified event monitor was created with the same target path
as another event monitor. This other event monitor was activated
at least once, and has left .evt and/or .ctl files in the target
path. These files may be in use by application(s) that are
reading the event information they contain.

User Response:

If the other event monitor is currently active, deactivate it.
After ensuring no application(s) are using the files it created
in the target path, remove the files. Then resubmit the SET
EVENT MONITOR statement.

Alternatively, recreate the required event monitor, specifying a
different target path, and resubmit the SET EVENT MONITOR
statement.

sqlcode : -1618

sqlstate : 51026

Cheers
Serge
--
Serge Rielau
DB2 SQL Compiler Development
IBM Toronto Lab

[RickC]

I am using this in v8 to report on sever errors in the past 24 hours:
db2diag -l severe -H 24h >> $LOG

And I use it to archive the db2diag.log file:
db2diag -A
Do you know if this is available for db2 v7?

Rick

[Serge Rielau]

RickC wrote:

I am using this in v8 to report on sever errors in the past 24 hours:
db2diag -l severe -H 24h >> $LOG

And I use it to archive the db2diag.log file:
db2diag -A
Do you know if this is available for db2 v7?

Not available in V7. You will have noticed that the format of the
db2diag.log was also changed to better support parsing.
Given that V7 is in extended support now it's unlikely you can get a
backward fit. Teh answre you will get from your friendly IBM rep will
be: Sure, use DB2 V8.2 :-)

Cheers
Serge
--
Serge Rielau
DB2 SQL Compiler Development
IBM Toronto Lab