DB2 - Problembeschreibung
Problem IT02523 | Status: Geschlossen |
ASYNCHRONOUS BACKGROUND AGENTS NOT RESPECTING THE DB2_PMODEL_SETTINGS=MAX_BACKGROUND_SYSAPPS REGISTRY VARIABLE | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
ome asynchronous background agents are not respecting the DB2_PMODEL_SETTINGS=MAX_BACKGROUND_SYSAPPS:<value> registry variable. This can affect the anonymous block cleanup (db2abc) agents, the asynchronous background process (db2abp) agents, and possibly other background agents. This can result is having a huge number of background agents and hitting the following: db2diag.log: 2014-05-26-14.23.46.652268+120 I112351807E1894 LEVEL: Severe PID : 18968 TID : 140654302717696 PROC : db2sysc 0 INSTANCE: db2isnt1 NODE : 000 DB : SAMPLE APPHDL : 0-60251 APPID: *LOCAL.DB2.140527094611 AUTHID : DB2INST1 HOSTNAME: db2host EDUID : 2174 EDUNAME: db2taskp (SAASPRD) 0 FUNCTION: DB2 UDB, base sys utilities, sqeIcoordCB::DispatchIndependentDBAgent, probe:110 MESSAGE : ZRC=0xFFFFFB37=-1225 SQL1225N The request failed because an operating system process, thread, or swap space limit was reached. CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) [0] 0x00007FFFEF2EBF12 _ZN11sqeIcoordCB26DispatchIndependentDBAgentEiP5sqlcaP13SQLKD_TA SK_IDPvPKcP16SQLE_CLIENT_INFOP16SQLEX_AUTHINFO_TP12SQLZ_APP_HDL + 0x9D2 [1] 0x00007FFFEC47FD38 _ZN14ABPIcoordAgent16spawnIcoordAgentERK8sqeAgentbPK17ABPTaskPro ContextR5sqlcab + 0xD8 [2] 0x00007FFFEC479854 _ZN13ABPDispatcher10spawnAgentERK8sqeAgentPK17ABPTaskProContextb bb + 0x64 [3] 0x00007FFFF0914582 _ZN13ABPDispatcher34spawnAgentsForReadyTaskProContextsERK8sqeAge nt + 0xA2 [4] 0x00007FFFEC47A01F _ZN13ABPDispatcher20getTaskProAssignmentERK8sqeAgentRP17ABPTaskP roContext + 0x22F [5] 0x00007FFFEC47316B _ZN8ABPAgent20getTaskProAssignmentERP17ABPTaskProContext + 0x5B [6] 0x00007FFFEC472D6C _ZN8ABPAgent4mainEP17ABPTaskProContext + 0x15C [7] 0x00007FFFEC47F62C _Z18abpAgentEntryPointP8sqeAgentP17ABPTaskProContext + 0x4C [8] 0x00007FFFEF29B14D _Z26sqleIndCoordProcessRequestP8sqeAgent + 0x12BD [9] 0x00007FFFEF2A9896 _ZN8sqeAgent6RunEDUEv + 0x2B6 [10] 0x00007FFFF084C054 _ZN9sqzEDUObj9EDUDriverEv + 0xF4 [11] 0x00007FFFF009F6C7 sqloEDUEntry + 0x2F7 [12] 0x00007FFFF7BC79D1 /lib64/libpthread.so.0 + 0x79D1 [13] 0x00007FFFEA32DB7D clone + 0x6D | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All Platforms * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 LUW Version 10.1 Fixpack 5 or Later. * **************************************************************** | |
Local-Fix: | |
Lösung | |
First Fixed in DB2 LUW Version 10.1 Fixpack 5. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 13.06.2014 14.07.2015 01.12.2015 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.5 |