Mystery db2agent Processes

[Evan Smith]

We're in the process of upgrading to version 8.2 from 7.2 (with hopes
that most of the issues we're currently facing will be fixed...). In
the interim, we have a new problem that has surfaced that is causing
us severe grief. A search of this newsgroup archive didn't turn up
anything. Hoping that someone else has seen this before.

Our db2agent pool is being exhausted for an unknown reason. We are not
running with INTRA_PARALLEL turned on. Generally we never see more
db2agent processes than connections to the database. We usually see an
agent attached to a database or in an idle state. What we end up
seeing is multiple db2agent processes appearing like this:

db2agent (instance)

All of these processes are owned by db2tcpcm or db2ipccm. Our
MAXAGENTS is 400. With 150 applications connected to the database
we'll see 250 of the "db2agent (instance)" processes. The rest of the
agents are linked with the database or idle.

I haven't figured out a graceful way to make these guys go away.
(Stopping and restarting the instance seems to be the only way so
far.) As long as they're there, no new connections can be obtained
into the database. (I can't even do a list applications at this
point.) It appears that anyone currently connected remains connected,
but all future connections are met with an error.

Anyone ever seen anything like this before?

The application connections come from Websphere's connection pool with
db2 client software 7.2 FP 8 on NT 4.0 service pack 6. The back end is
DB2 7.2 FP8 on AIX 4.3.

Thanks in advance,
Evan

[Bob [IBM]]

Evan - what is your setting for the configuration value NUM_INIT_AGENTS?

--

Bob
Engagement Specialist - DB2 Information Management Software - IBM Software Group
IBM Toronto Lab
[My comments are solely my own and are not meant to represent an official IBM position -
ask my cat!]

"Evan Smith" <es********@hotmail.com> wrote in message
news:23**************************@posting.google.c om...

We're in the process of upgrading to version 8.2 from 7.2 (with hopes
that most of the issues we're currently facing will be fixed...). In
the interim, we have a new problem that has surfaced that is causing
us severe grief. A search of this newsgroup archive didn't turn up
anything. Hoping that someone else has seen this before.

Our db2agent pool is being exhausted for an unknown reason. We are not
running with INTRA_PARALLEL turned on. Generally we never see more
db2agent processes than connections to the database. We usually see an
agent attached to a database or in an idle state. What we end up
seeing is multiple db2agent processes appearing like this:

db2agent (instance)

All of these processes are owned by db2tcpcm or db2ipccm. Our
MAXAGENTS is 400. With 150 applications connected to the database
we'll see 250 of the "db2agent (instance)" processes. The rest of the
agents are linked with the database or idle.

I haven't figured out a graceful way to make these guys go away.
(Stopping and restarting the instance seems to be the only way so
far.) As long as they're there, no new connections can be obtained
into the database. (I can't even do a list applications at this
point.) It appears that anyone currently connected remains connected,
but all future connections are met with an error.

Anyone ever seen anything like this before?

The application connections come from Websphere's connection pool with
db2 client software 7.2 FP 8 on NT 4.0 service pack 6. The back end is
DB2 7.2 FP8 on AIX 4.3.

Thanks in advance,
Evan

[Evan Smith]

Here are all the settings for agents:

Priority of agents (AGENTPRI) = SYSTEM
Max number of existing agents (MAXAGENTS) = 400
Agent pool size (NUM_POOLAGENTS) = 8 (calculated)
Initial number of agents in pool (NUM_INITAGENTS) = 0
Max number of coordinating agents (MAX_COORDAGENTS) = MAXAGENTS
Max no. of concurrent coordinating agents (MAXCAGENTS) = MAX_COORDAGENTS
Max number of logical agents (MAX_LOGICAGENTS) = MAX_COORDAGENTS
Max number of DARI processes (MAXDARI) = MAX_COORDAGENTS
SPM resync agent limit (SPM_MAX_RESYNC) = 20

This hasn't been a problem in the 3 years the database has been active until
last Monday. I just found out that there were Microsoft security patches put
in over the weekend on the application servers. Might this be an issue with
the DB2 client software?

Evan

"Bob [IBM]" <Bo******@canada.com> wrote in message
news:2t*************@uni-berlin.de...

Evan - what is your setting for the configuration value NUM_INIT_AGENTS?

--

Bob
Engagement Specialist - DB2 Information Management Software - IBM Software Group IBM Toronto Lab
[My comments are solely my own and are not meant to represent an official IBM position - ask my cat!]

"Evan Smith" <es********@hotmail.com> wrote in message
news:23**************************@posting.google.c om...

We're in the process of upgrading to version 8.2 from 7.2 (with hopes
that most of the issues we're currently facing will be fixed...). In
the interim, we have a new problem that has surfaced that is causing
us severe grief. A search of this newsgroup archive didn't turn up
anything. Hoping that someone else has seen this before.

Our db2agent pool is being exhausted for an unknown reason. We are not
running with INTRA_PARALLEL turned on. Generally we never see more
db2agent processes than connections to the database. We usually see an
agent attached to a database or in an idle state. What we end up
seeing is multiple db2agent processes appearing like this:

db2agent (instance)

All of these processes are owned by db2tcpcm or db2ipccm. Our
MAXAGENTS is 400. With 150 applications connected to the database
we'll see 250 of the "db2agent (instance)" processes. The rest of the
agents are linked with the database or idle.

I haven't figured out a graceful way to make these guys go away.
(Stopping and restarting the instance seems to be the only way so
far.) As long as they're there, no new connections can be obtained
into the database. (I can't even do a list applications at this
point.) It appears that anyone currently connected remains connected,
but all future connections are met with an error.

Anyone ever seen anything like this before?

The application connections come from Websphere's connection pool with
db2 client software 7.2 FP 8 on NT 4.0 service pack 6. The back end is
DB2 7.2 FP8 on AIX 4.3.

Thanks in advance,
Evan

[Bob [IBM]]

Sorry - cannot comment on how the MS update may have affected the Application Servers.

--

Bob
Engagement Specialist - DB2 Information Management Software - IBM Software Group
IBM Toronto Lab
[My comments are solely my own and are not meant to represent an official IBM position -
ask my cat!]
"Evan Smith" <es********@hotmail.com> wrote in message
news:jW*****************@newsread2.news.atl.earthl ink.net...

Here are all the settings for agents:

Priority of agents (AGENTPRI) = SYSTEM
Max number of existing agents (MAXAGENTS) = 400
Agent pool size (NUM_POOLAGENTS) = 8 (calculated)
Initial number of agents in pool (NUM_INITAGENTS) = 0
Max number of coordinating agents (MAX_COORDAGENTS) = MAXAGENTS
Max no. of concurrent coordinating agents (MAXCAGENTS) = MAX_COORDAGENTS
Max number of logical agents (MAX_LOGICAGENTS) = MAX_COORDAGENTS
Max number of DARI processes (MAXDARI) = MAX_COORDAGENTS
SPM resync agent limit (SPM_MAX_RESYNC) = 20

This hasn't been a problem in the 3 years the database has been active until
last Monday. I just found out that there were Microsoft security patches put
in over the weekend on the application servers. Might this be an issue with
the DB2 client software?

Evan

"Bob [IBM]" <Bo******@canada.com> wrote in message
news:2t*************@uni-berlin.de...

Evan - what is your setting for the configuration value NUM_INIT_AGENTS?

--

Bob
Engagement Specialist - DB2 Information Management Software - IBM Software

Group

IBM Toronto Lab
[My comments are solely my own and are not meant to represent an official

IBM position -

ask my cat!]

"Evan Smith" <es********@hotmail.com> wrote in message
news:23**************************@posting.google.c om...

We're in the process of upgrading to version 8.2 from 7.2 (with hopes
that most of the issues we're currently facing will be fixed...). In
the interim, we have a new problem that has surfaced that is causing
us severe grief. A search of this newsgroup archive didn't turn up
anything. Hoping that someone else has seen this before.

Our db2agent pool is being exhausted for an unknown reason. We are not
running with INTRA_PARALLEL turned on. Generally we never see more
db2agent processes than connections to the database. We usually see an
agent attached to a database or in an idle state. What we end up
seeing is multiple db2agent processes appearing like this:

db2agent (instance)

All of these processes are owned by db2tcpcm or db2ipccm. Our
MAXAGENTS is 400. With 150 applications connected to the database
we'll see 250 of the "db2agent (instance)" processes. The rest of the
agents are linked with the database or idle.

I haven't figured out a graceful way to make these guys go away.
(Stopping and restarting the instance seems to be the only way so
far.) As long as they're there, no new connections can be obtained
into the database. (I can't even do a list applications at this
point.) It appears that anyone currently connected remains connected,
but all future connections are met with an error.

Anyone ever seen anything like this before?

The application connections come from Websphere's connection pool with
db2 client software 7.2 FP 8 on NT 4.0 service pack 6. The back end is
DB2 7.2 FP8 on AIX 4.3.

Thanks in advance,
Evan

[Mark]

"Bob [IBM]" <Bo******@canada.com> wrote in message news:<2tppe8F22evgqU1@uni-

Sorry - cannot comment on how the MS update may have affected the Application Servers.

--

Bob
Engagement Specialist - DB2 Information Management Software - IBM Software Group
IBM Toronto Lab
[My comments are solely my own and are not meant to represent an official IBM position -

I think he is asking if the Windows updates have any effect on the DB2
clients running under Windows.

Are their any known issues (with any supported DB2 release) with DB2
servers or clients running on Windows 2000 or XP with the new MS
security pathes (or XP FP2)?