DB2 - Problembeschreibung
Problem IT03832 | Status: Geschlossen |
DB2 IS NOT ABLE TO ACCEPT AN INCOMING CONNECTION IF NUMBER OF INSTANCE THREADS EXCEEDS RLIMIT_NPROC LIMIT | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
DB2 database will not be able to accept an incoming connection if the number of processes/threads (that includes all DB2 EDUs) running as instance owner exceeds RLIMIT_NPROC. In such scenario the following message will be logged in the db2diag.log: 2014-01-01-12.00.00.000000+000 E41002E402 LEVEL: Error (OS) PID : 15370 TID : 140737131833088PROC : db2sysc 0 INSTANCE: db2insp1 NODE : 000 EDUID : 17 EDUNAME: db2tcpcm 0 FUNCTION: DB2 UDB, oper system services, sqloSpawnEDU, probe:80 MESSAGE : ZRC=0x8300000B=-2097151989 CALLED : OS, -, pthread_create OSERR: EAGAIN (11) NPROC limit is defined only on GNU/Linux operating system. This APAR will address the issue by overriding default limit for db2sysc process when instance is started. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Linux * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10.5 Fix Pack 5 or higher. * **************************************************************** | |
Local-Fix: | |
Increase NPROC limit for instance owner and restart the instance. On recent kernel versions the limit of running process can be changed using proc virtual filesystem: $ echo -n "Max processes=<n_soft>:<n_hard>" > /proc/<pid>/limits where pid is PID of db2sysc process and n_soft, n_hard are desired soft and hard limits respectively, e.g: $ echo -n "Max processes=10240:65535" > /proc/15370/limits | |
Lösung | |
Fixed in DB2 version 10.5 Fix Pack 5. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 18.08.2014 26.02.2016 26.02.2016 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.5 |