>You might try turning off the DB2 agent. It looks like that is what the OOM killer is trying to do.
The OOM killer is not very good at killing things, imho. It attacks the processes with the most cpu+memory. After awhile, it will attach critical system functions. (We found that out with a similar situation under DB2). He only gets woken up if there is not enough memory (real+swap). Either you have to increase memory, increase swap, (or both) or reduce your workload. Regards, Jim Linux S/390-zSeries Support, SEEL, IBM Silicon Valley Labs t/l 543-4021, 408-463-4021, [EMAIL PROTECTED] *** Grace Happens ***
