DB2 - Problem description
Problem IT39347 | Status: Closed |
ERROR ADM7009E AFTER UPGRADING TO 11.5 | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
db2diag.log shows every 5 seconds this message: 2021-11-23-08.09.46.496000+060 E104370841F508 LEVEL: Error PID : 3268 TID : 4936 PROC : db2syscs.exe INSTANCE: DB2 NODE : 000 HOSTNAME: XXXXXXXXXX EDUID : 4936 EDUNAME: db2tcpcm 0 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. 2021-11-23-08.09.46.512000+060 I104371351F473 LEVEL: Error PID : 3268 TID : 4936 PROC : db2syscs.exe INSTANCE: DB2 NODE : 000 HOSTNAME: XXXXXXXXXX EDUID : 4936 EDUNAME: db2tcpcm 0 FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:126 MESSAGE : Return code from sqleGetAgent = DATA #1 : Hexdump, 4 bytes 0x000000DE36D4F614 : 1C00 0F81 .... | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All user using DB2 11.5 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to 11.5 FP7 or higher * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * All user using DB2 11.5 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to 11.5 FP7 or higher * **************************************************************** | |
Comment | |
Upgrade to 11.5.8 or higher | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 09.12.2021 13.04.2022 13.04.2022 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |