asked on

IBM UDB: Consumes memory until the application server crashes...

We use Rational ClearQuest and have recently converted to use DB2Express-C for the backend. I have only modified two configuration parameters: the MON_HEAP_SZ and the ASLHEAPSZ. The server appears to be consuming memory until it is using 1.7 GB of virtual memory and then DB2 starts writing an "Insufficient System Resources" error to db2diag. The problem is only resolved by restarting the server. The machine is running Windows Server 2000 and has 1 GB of physical RAM.

momi_sabag

hi

does this happens if you are not using the ClearQuest tool,
that is
can you make a test, where you run queries and application against you Db2 without invoking the clear quest and see if it consume so much memory ?

NorCal2612

ASKER

I could do that...

I suspect that db2 keeps creating new agents for each query or connection and is not releasing them. Could this be related somehow to my values for MAXAGENTS, NUM_POOLAGENTS and/or MAX_CONNECTIONS? Currently they are set to 200, 100 and 200. We only have around 15 ClearQuest users max. Typically it will be about 9 to 11 active users at any given time.

NorCal2612

ASKER

Also... Is it possible to see how many agents are registered at any given moment?

NorCal2612

ASKER

Hrm... I also have a 250 page 16KB bufferpool for my database... is this too big?

momi_sabag

you can see how many applications are logged in using the list applications command
if you know you have 15 users max, you should consider setting the above parameters to lower values
a 250 pages of 16kb buffer pool consumes 4mb of storage, so it's not too big at all

NorCal2612

ASKER

This is really the only error in the application event log....

2006-12-12-10.53.21.000000 Instance:DB2 Node:000
PID:2036(db2syscs.exe) TID:3664 Appid:C0A80D2D.JB05.016D82135750
access plan manager sqlra_cache_mem_please Probe:20 Database:CQDATA

ADM4500W A package cache overflow condition has occurred. There is no error
but this indicates that the package cache has exceeded the configured maximum
size. If this condition persists, you may want to adjust the PCKCACHESZ DB
configuration parameter.

ASKER CERTIFIED SOLUTION

ghp7000

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

NorCal2612

ASKER

ghp7000,

I will try your suggestions today.

Thanks for the response. :)