Results 1 to 2 of 2
  1. #1
    Join Date
    Feb 2015
    Posts
    1

    Unanswered: Recommended settings for connection pooling in DB2.

    Hi,

    Users of our application are getting the below errror:
    Error:ERROR [57030] [IBM][CLI Driver] SQL1226N The maximum number of client connections are already started. SQLSTATE=57030 ERROR [57030] [IBM][CLI Driver] SQL1226N The maximum number of client connections are already started.

    When I tried to research it found out that the error is caused because of connection pooling and following settings can be changed in DB2 to troubleshoot the error:

    MAXAPPLS
    MAXAGENTS
    MAX_CONNECTIONS
    MAX_COORDAGENTS
    NUM_POOLAGENTS
    NUM_INITAGENTS
    (MAX_COORDAGENTS) = MAXAGENTS
    (MAXCAGENTS) = MAX_COORDAGENTS
    (MAX_CONNECTIONS) = MAX_COORDAGENTS

    Can anyone suggest the recommended settings for the above items, for enterprise wide application with thousands of users.

    Thanks !
    Siddhesh.

  2. #2
    Join Date
    Apr 2012
    Posts
    1,035
    Provided Answers: 18
    There is not a "one size fits all" setting.
    It requires to be tuned appropriately for your needs and your hardware resources.
    Post your DB2-server version+fixpack, and the operating-system-name.
    Post the existing values of those parameters you mention.
    Post whether the connections originate with an application-server (e.g. Websphere or similar app server), or whether the connections are from ODBC applications/JDBC applications on individual workstations. Application-Servers usually have their own pooling.

    Additionally, enterprise databases often use WLM, and configure it to force off idle connections after a configurable time . Even without WLM you can arrange for stale connections to be cleaned.
    Last edited by db2mor; 02-12-15 at 12:22.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •