DB2 Deadlock error messages in the db2diag.log

kschlap · #1 (**permalink**) 11-28-07, 11:06

For the last week, we've been seeing the message below (over 1,000 times) in the db2diag.log. Can someone please shed some light on what this error message means? We're concerned because we are getting deadlock error messages in the Psft application:

2007-11-28-09.39.23.964620-360 I13230487C334 LEVEL: Warning
PID : 569684 TID : 1 PROC : db2event (DB2DETAILDEADLOCK) 0
INSTANCE: <instance> NODE : 000
FUNCTION: DB2 UDB, database monitor, sqm___sqlmeiot, probe:70
MESSAGE : target type 0 failed to open DB2DETAILDEADLOCK with rc -2146631637

Thanks

n_i · #2 (**permalink**) 11-28-07, 15:44

Probably the event monitor file has reached its maximum size, and the database manager fails to activate the monitor.

stolze · #3 (**permalink**) 11-30-07, 04:43

I wouldn't even say "probably". The details for the reason code say this:

Quote:

$ db2diag -rc -2146631637

Input ZRC string '-2146631637' parsed as 0x800D002B (-2146631637).

ZRC value to map: 0x800D002B (-2146631637)
V7 Equivalent ZRC value: 0xFFFF8E2B (-29141)

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

Identifer:
SQLM_RC_EVFULL
Identifer (without component):
SQLZ_RC_EVFULL

Description:
monitor full of data

Associated information:
Sqlcode -1617
SQL1617N The specified event monitor has already reached its MAXFILES and
MAXFILESIZE limit.

Number of sqlca tokens : 0
Diaglog message number: 8052

Internet Services

Web Development

Digital Marketing

Consumer Tech