Not able to get a Connection for db2Pool
Hi All
Greetings.
I am facing the below Error message in the Application logs:
Not able to get a Connection for db2Pool
Some few orders are failing with above message.
Below are my DBM configurations.
Priority of agents (AGENTPRI) = SYSTEM
Agent pool size (NUM_POOLAGENTS) = AUTOMATIC(100)
Initial number of agents in pool (NUM_INITAGENTS) = 0
Max number of coordinating agents (MAX_COORDAGENTS) = AUTOMATIC(200)
Max number of client connections (MAX_CONNECTIONS) = AUTOMATIC(MAX_COORDAGENTS)
Can you please give inputs to resolve this Problem.
Greetings.
I am facing the below Error message in the Application logs:
Not able to get a Connection for db2Pool
Some few orders are failing with above message.
Below are my DBM configurations.
Priority of agents (AGENTPRI) = SYSTEM
Agent pool size (NUM_POOLAGENTS) = AUTOMATIC(100)
Initial number of agents in pool (NUM_INITAGENTS) = 0
Max number of coordinating agents (MAX_COORDAGENTS) = AUTOMATIC(200)
Max number of client connections (MAX_CONNECTIONS) = AUTOMATIC(MAX_COORDAGENTS)
Can you please give inputs to resolve this Problem.
ASKER
Hi Thomas
There is no related error message or warning in the diag log.
Please find the attachment for the DBM cfg file.
Please let me know for any further inputs.
DBMCFG.txt
There is no related error message or warning in the diag log.
Please find the attachment for the DBM cfg file.
Please let me know for any further inputs.
DBMCFG.txt
Hi,
Ok I see that your DB2 instance is configured for at least 60 GB.
Look at the db cfg for your database and calculate how much bufferpool etc are % of the 60 GB.
Then calculte the <max number of connections (MAX_COORDAGENTS) in your case 200> * < sum of application heap and memory found in the db cfg output >
If 60GB + <max number of connections (MAX_COORDAGENTS) in your case 200> * < sum of application heap and memory found in the db cfg output > is greater than the total OS memory then you need to increase the memory or tune the appl heap to a lower values (if possible - that can result in other performance problems).
If the above is not the case you need to trace your db2 client connections and/or look into the db2diag.log in your db2 client for errors/clues on this.
Regards,
Tomas Helgi
Ok I see that your DB2 instance is configured for at least 60 GB.
Look at the db cfg for your database and calculate how much bufferpool etc are % of the 60 GB.
Then calculte the <max number of connections (MAX_COORDAGENTS) in your case 200> * < sum of application heap and memory found in the db cfg output >
If 60GB + <max number of connections (MAX_COORDAGENTS) in your case 200> * < sum of application heap and memory found in the db cfg output > is greater than the total OS memory then you need to increase the memory or tune the appl heap to a lower values (if possible - that can result in other performance problems).
If the above is not the case you need to trace your db2 client connections and/or look into the db2diag.log in your db2 client for errors/clues on this.
Regards,
Tomas Helgi
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Post the db2 dbm cfg output as well as any related error in the db2diag.log.
Also look at the database config db2 db cfg for <your databasename>.
The OS memory must be big enough for the database + <number of connections> * < sum of application heap and memory >
That is the memory of the machine running your DB2 must be large enough to handle the size of your database (bufferpools, heaps etc) + <number of concurrent connections> * < sum of application heap and memory >
Regards,
Tomas Helgi