We are running DB2 V8 on Solaris 9. Last week we upgraded from FP7 to
FP13. Everything seemed to be fine, but yesterday we were confronted
with a strange behavior of the DB2 governor.
An application server process was forced by the governor with this log
message:
2006-10-23-12.51.43 0 FORCE applname `panh030` authid `ARNRUN`
applid C0A80401.O256.0 3A012212902` coord 0 (line 56) ET 4294967295
The rule on line 56 is a general rule to force processes with 10 hours
of idletime or uowtime. Both didn't apply to the process in question.
But the interesting fact is the "ET 4294967295" entry. In hex this is
0xffffffff equaling -1. That looks very much like an signed-unsigned
issue. I also found a closed APAR about a similar problem (IY73972,
http://www-1.ibm.com/support/docview...d=swg1IY73972). The problem
was fixed in FP11, but it seems there is another problem.
Has anyone seen this before?
Paul Herger