Results 1 to 6 of 6
  1. #1
    Join Date
    Dec 2002
    Posts
    123

    Unanswered: Max number of client connections reached

    Hello,

    On one of our servers, when I try to connect to the database I get this error --

    SQL1226N The maximum number of client connections are already started.
    SQLSTATE=57030

    When I checked the count of db2agent, I saw that it was at 226 and this error makes sense as the value of MAXAGENTS AND MAXAPPLS was 200.

    I gave this command to update the value to 1200 --

    db2 update db cfg using MAXAGENTS 1200

    I double checked the value that I set by giving this command and get this output --

    db2 get dbm cfg | grep MAXAGENTS
    Max number of existing agents (MAXAGENTS) = 1200
    Max number of coordinating agents (MAX_COORDAGENTS) = MAXAGENTS


    when I try to connect again, I still get the same error

    db2 connect to db2name
    SQL1226N The maximum number of client connections are already started.
    SQLSTATE=57030

    Any idea how I can fix this? Is there any other parameter that I need to change? Thank you!
    Last edited by db2user; 12-04-08 at 14:28.

  2. #2
    Join Date
    Jan 2003
    Posts
    4,292
    Provided Answers: 5
    What DB2 version and OS?

    Have you looked at MAX_CONNECTIONS?

    Andy

  3. #3
    Join Date
    Dec 2002
    Posts
    123
    Hi,

    I get this --
    db2 get dbm cfg | grep MAX_CONNECTIONS
    Max number of client connections (MAX_CONNECTIONS) = MAX_COORDAGENTS

    and based on this command, it seems like MAX_CONNECTIONS is the sam as MAXAGENTS which is 1200.

    db2 get dbm cfg | grep MAXAGENTS
    Max number of existing agents (MAXAGENTS) = 1200
    Max number of coordinating agents (MAX_COORDAGENTS) = MAXAGENTS

    DB2 version in 8.2 (UDB) and its on a Linux based system

  4. #4
    Join Date
    Jan 2003
    Posts
    4,292
    Provided Answers: 5
    Have you bounced the instance since making the changes?

    Andy

  5. #5
    Join Date
    Dec 2002
    Posts
    123
    This is what I get if I try to stop the database.

    db2stop
    SQL1025N The database manager was not stopped because databases are still active.

    Then I tried to force applications --
    db2 force applications all
    SQL1226N The maximum number of client connections are already started.
    SQLSTATE=57030

    How can I get around this?

  6. #6
    Join Date
    Dec 2002
    Posts
    123
    I tried db2stop force and it seemed to solve the problem. thanks for your help!

Posting Permissions

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