DB2 - Problem description
Problem IC65094 | Status: Closed |
USER INTERRUPT MAY BE DETECTED BY EVENT MONITOR IN DB2DIAG.LOG WHEN THE LAST CONNECTION IS TERMINATED. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
The customer may see the following error message from event monitor when the last agent is terminated. If there is only one db2agent is connecting to the database, and when the connection is terminated, all system applications will be forced off. This is the expected behavior. Although the message level is "Error", this message can safely be ignored. 2009-07-19-12.50.02.210646+540 I434208A646 LEVEL: Error PID : 647294 TID : 17433 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-37858 APPID: *LOCAL.DB2.090719035005 AUTHID : DB2INST1 EDUID : 17433 EDUNAME: db2evmti (S_349) 0 FUNCTION: DB2 UDB, database monitor, sqmEvmonWriter::postActivation, probe:30 CALLED : DB2 UDB, database monitor, sqmEvmonWriter::updateEvmonActivates RETCODE : ZRC=0x80040003=-2147221501=SQLD_INTRP "USER INTERRUPT DETECTED" DIA8003C The interrupt has been received. DATA #1 : String, 5 bytes S_349 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error description field for more information. * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 9.5 FixPack 6. * **************************************************************** | |
Local Fix: | |
Activating database can avoid the message logged in db2diag.log. | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 UDB Version 9.5 FixPack 6. | |
Workaround | |
see LOCAL FIX. | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC68438 IC68439 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 10.12.2009 22.06.2010 22.06.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP6 | |
Problem solved according to the fixlist(s) of the following version(s) |