maxuproc

Hi Akki,

the reason is that your application servers has opened more connections to the database. DB2 uses at least one process for each client connection. It needs more if you activate intra partition parallelism or you run on a partitioned database (used for SAP BI systems). In BI environment the developer are using more and more secondary connects. If you have upgraded your application, this could also a reason for more connections. If you don't run a BI system and you don't have changed the intra partition parallelism parameter, you probably have added SAP work processes or increased the number of Java connections. If none of this is correct, you should check which user and which client has opened the connections. Just do a [code]db2 list applications[/code] it'll show one line per connection. It shows also the client program opened the connection (second column). It should show only disp+work (dw.) or db2jcc_ and some db2 instance processes db2taskd and db2stmm. Every thing else should be investigated.

May be you check your system with the following command:

[code]> db2 list applications | sed -e '1,/^-----/d' | awk '{ user[$2]++; }END{ for (f in user) { printf "%-20.20s %d\n", f, user[f]; }}'[/code]

It should show only processes like those I listed above.

Best regards

Ralph