By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,282 Members | 1,617 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,282 IT Pros & Developers. It's quick & easy.

Stolen Agent Question

P: n/a
Hello,

DBM Snapshot shows that MAXAGENTS parameter has to be increased on the
database because of high value in agent_stolen monitor element. (Pasted
below for reference)

/home/cardmnt] db2 get snapshot for dbm | grep -i agent
High water mark for agents registered = 143
High water mark for agents waiting for a token = 0
Agents registered = 143
Agents waiting for a token = 0
Idle agents = 68
Agents assigned from pool = 6123829
Agents created from empty pool = 145
Agents stolen from another application = 282
High water mark for coordinating agents = 43
Max agents overflow = 0
Gateway connection pool agents stolen = 0

But before increasing the MAXAGENTS parameter directly I decided to
monitor it again hence I reset the monitor elements, but even after
resetting the agent_stolen monitor element shows the same old value of
282.

/home/cardmnt] db2 reset monitor all
DB20000I The RESET MONITOR command completed successfully.

/home/cardmnt] db2 get snapshot for dbm | grep -i agent
High water mark for agents registered = 143
High water mark for agents waiting for a token = 0
Agents registered = 143
Agents waiting for a token = 0
Idle agents = 68
Agents assigned from pool = 6123830
Agents created from empty pool = 145
Agents stolen from another application = 282
High water mark for coordinating agents = 43
Max agents overflow = 0
Gateway connection pool agents stolen = 0

Does this mean that DBM level monitor elements cannot be reset ? or Am
I missing something?

Thanks,
Sam.

Sep 5 '06 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.