DB2 - Problem description
Problem IC95393 | Status: Closed |
A FAILURE TO START DB2VEND PROCESS MIGHT RESULT IN SELF-KILLING OF AN INSTANCE | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
Under a rare condition when db2vend failed to fork/execv, it might result in sending a SIGKILL to all processes in the db2 process group. In other words , the db2 instance might be killed" The symptom of the problem : 2013-05-01-08.47.16.419967-240 I217554772A3810 LEVEL: Event PID : 13500438 TID : 68519 PROC : db2sysc 0 INSTANCE: db2isnt NODE : 000 DB : DATABASE APPHDL : 0-44710 APPID: 10.150.128.42.55001.13050112432 AUTHID : DB2INSTOWNER EDUID : 68519 EDUNAME: db2agent (DATABASE) 0 FUNCTION: DB2 UDB, oper system services, sqlossig, probe:10 MESSAGE : Sending SIGKILL to the following process id DATA #1 : signed integer, 4 bytes 0 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.5 Fix Pack 3. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 Version 10.5 Fix Pack 3. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 27.08.2013 27.02.2014 27.02.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.3 | |
10.5.0.3 |