Fixes are available
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
Closed as program error.
Issuing db2stop force command may cause a trap in db2 v9.5. The trap occurred immediately after sqleKillNode sent SIGDUMP to all processes. The following messages may appear in the db2diag.log: 2009-01-27-18.104.22.168088-300 I32874473E296 LEVEL: Severe PID : 2158 TID : 183095683680 PROC : db2stop2 INSTANCE: nyqxt150 NODE : 014 FUNCTION: DB2 UDB, base sys utilities, sqleKillNode, probe:90 MESSAGE : Sending sigdump and waiting for 1 min to complete 2009-01-27-22.214.171.1242308-300 E32874770E1515 LEVEL: Critical PID : 30054 TID : 183106529632 PROC : db2ckpwd 14 INSTANCE: nyqxt150 NODE : 014 EDUID : 1 EDUNAME: db2sysc 14 FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler, probe:10 MESSAGE : ADM14001C An unexpected and critical error has occurred: "Trap". The instance may have been shutdown as a result. "Automatic" FODC (First Occurrence Data Capture) has been invoked and diagnostic information has been recorded in directory <directory name>. Please look in this directory for detailed evidence about what happened and contact IBM support if necessary to diagnose the problem. DATA #1 : Signal Number Recieved, 4 bytes 11 A stack trace with the following functions may appear in the trap file: ossDumpStackTraceEx OSSTrapFile OSSTrapFile sqlo_trce sqloEDUCodeTrapHandler sqloUNIXSignalEDU sqloDumpInstanceHandler sqlorqueInternal sqlorque2 sqlockpw_daemon_initv sqloRunInstance sqloEDUMainEntryPcj sqloEDUEntry
none Fixed in FP5.
Users Affected: All Problem Description: Issuing command db2stop force may cause a trap. The trap occurs immediately after sqleKillNode sends SIGDUMP to all processes. Messages in the db2diag.log indicate a signal 11 was received after calling function sqleKillNode. Problem Summary: Instance traps with signal 11 after issuing db2stop force command.
Problem is first fixed in Version 9.5 FixPak 5
Reported component name
DB2 UDE ESE LIN
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
DB2 UDE ESE LIN
Fixed component ID
Applicable component levels
03 May 2010