This is not the solution for this problem.
The solution to the problem is to
1. To increase the MAXAGENTS parameter.
Then, the problem of sortheap error may come. If you
happen to see that error, then
2. Set the NUM_POOLAGENTS to MAXAGENTS
[APAR = IY50445]
Then the problem of paging space comes where in you will have
the large number of db2 processes consuming the major part of
the memory. Then we need to set two registry variables
DB2MEMMAXFREE=4000000 [depends]
DB2MEMDISCLAIM=YES
[as said by Abraham].
Even after this if this problem occurs, then the solution is
to go to the fixpack-5 or 6.
We went through all these stages and now we are in Fixpack-6.
We got rid of these problems but now we have the problem of slowly
growing paging space.
Hope this helps.
Partha
-----Original Message-----
From: abraham
[mailto:db2udbdba-ezmlmshield-x58128590.[Email address protected]
Sent: Monday, January 31, 2005 8:43 AM
To: LazyDBA Discussion
Subject: Re: idle process
You need to set two Registry variables to resolve idle agent holding on to
memory:
DB2MEMMAXFREE=4000000
DB2MEMDISCLAIM=YES
These two go together.
abe
"TOHare"
<db2udbdba-ezmlmshield-x63606608.[Email address protected] To:
om> "LazyDBA Discussion" <[Email address protected]
cc:
Subject: idle process
Monday January 31, 2005 06:00 AM
On a solaris server using db2 v8.1 fix pack 3 there seems to be a build up
of idle agents,
to the point where an error occurs -
PID:3862(db2ipccm 0) TID:1 Appid:none
base sys utilities sqleGetAgentFromPool Probe:97
Error getting an agent. Return code =
0xFFBEC050 : 0xFFFFFB39 ...9
2005-01-29-03.58.58.654493 Instance:db2inst1 Node:000
PID:3862(db2ipccm 0) TID:1 Appid:none
base sys utilities sqleGetAgent Probe:70
Agent not allocated, sqlcode = -1223
Is this a known problem or is it related to the db2 confioguration.
Extract from dbm cfg
Max number of existing agents (MAXAGENTS) = 800
Agent pool size (NUM_POOLAGENTS) = 400
Initial number of agents in pool (NUM_INITAGENTS) = 0
Max number of coordinating agents (MAX_COORDAGENTS) = (MAXAGENTS -
NUM_INITAGENTS)
Max no. of concurrent coordinating agents (MAXCAGENTS) = MAX_COORDAGENTS
Max number of client connections (MAX_CONNECTIONS) = MAX_COORDAGENTS
Regards,
Tom
***************************************************************
The information contained in this e-mail and any files transmitted
with it is confidential and may be subject to legal professional
privilege. It is intended solely for the use of the addressee(s).
If you are not the intended recipient of this e-mail, please note
that any review, dissemination, disclosure, alteration, printing,
copying or transmission of this e-mail and/or any file transmitted
with it, is prohibited and may be unlawful.
If you have received this e-mail by mistake, please promptly
inform the sender by reply e-mail and delete the material.
Whilst this e-mail message has been swept for the presence of
computer viruses, eircom does not, except as required by law,
represent, warrant and/or guarantee that the integrity
of this communication has been maintained nor that
the communication is free of errors, viruses, interception or
interference.
***************************************************************
---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
DB2 & UDB email list listserv db2-l LazyDBA home page