Topic
1 reply Latest Post - ‏2013-10-08T11:49:52Z by Rudolf Bargholz
Rudolf Bargholz
Rudolf Bargholz
4 Posts
ACCEPTED ANSWER

Pinned topic RESOLVED: Cannot connect to database - SQL1224N , SQLSTATE=55032

‏2013-10-08T11:09:57Z |

Hi,

DB2 Express C 9.1 WIN x86 64 bit

When connecting to a database we see the following errors in the db2diag.log:

 

2013-10-08-12.43.37.373000+120 I5447F406          LEVEL: Event
PID     : 8636                 TID  : 10848       PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:19
DATA #1 : String, 37 bytes
Agent overflow for system application
DATA #2 : Hexdump, 4 bytes
0x000000000633C324 : C800 0000                                  ....

This error is repeated very often, and then the following:

2013-10-08-12.43.37.451000+120 I25847F289         LEVEL: Error
PID     : 8636                 TID  : 19508       PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleGetAgent, probe:70
MESSAGE : Agent not allocated, sqlcode = -1226

2013-10-08-12.43.37.451000+120 E26138F430         LEVEL: Error
PID     : 8636                 TID  : 19508       PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000
FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:125
MESSAGE : ADM7009E  An error was encountered in the "TCPIP" protocol support.  
          A possible cause is that the maximum number of agents has been
          exceeded.

2013-10-08-12.43.37.451000+120 I26570F395         LEVEL: Error
PID     : 8636                 TID  : 19508       PROC : db2syscs.exe
INSTANCE: DB2                  NODE : 000
FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126
MESSAGE : Return code from sqleGetAgent =
DATA #1 : Hexdump, 4 bytes
0x0000000006FFFC44 : 36FB FFFF                                  6...

The db2 connect returns the following error:

C:\>db2 connect to MYDB user db2admin using xxxxxxxxxx
SQL1224N  Der Datenbankmanager kann keine neuen Anforderungen akzeptieren, hat
alle derzeit in Verarbeitung befindlichen Anforderungen beendet oder hat
speziell Ihre Anforderung auf Grund eines mit Ihrer Anforderung bestehenden
Problems beendet.  SQLSTATE=55032

In the DB Manager the MAXAGENTS was 200. I tried increasing this value to 10'000, but the error messages we see after the connect and in the db2diag.log remain the same.

Does anyone have an idea what I might do to resolve this problem, or what the case might be?

Regards

Rudolf Bargholz

Updated on 2013-10-08T11:50:27Z at 2013-10-08T11:50:27Z by Rudolf Bargholz
  • Rudolf Bargholz
    Rudolf Bargholz
    4 Posts
    ACCEPTED ANSWER

    RESOLVED: Cannot connect to database - SQL1224N , SQLSTATE=55032

    ‏2013-10-08T11:49:52Z  in response to Rudolf Bargholz

    Hi,

    Sorry for the noise.

    After a long morning bout of feeling terrible because a customer was not able to work, I noticed that the "db2 list node directory" and "db2 list database directory" looked strange. When databases are catalogued to a local drive, there is no need for a node, and nomally a "db2 list node directory" will return an empty result set, but in this case some of the databases on the server were on the node "D:", others were on a node that mapped to the ip address of the server. I think DB2 got mixed up, because uncataloging all of the databases and nodes, and then adding them again resolved the problem and I was again able to log on to the four DB2 again that did not work all morning.

    Regards

    Rudolf