home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC68438 Status: Geschlossen

USER INTERRUPT MAY BE DETECTED BY EVENT MONITOR IN DB2DIAG.LOG WHEN THE
LAST CONNECTION IS TERMINATED.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* As same as Error description.                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 FixPack 3.                            * 
****************************************************************
Local-Fix:
Activating database can avoid the message logged in db2diag.log.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in DB2 UDB Version 9.7 FixPack 3.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
05.05.2010
27.09.2010
27.09.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP3
Problem behoben lt. FixList in der Version
9.7.0.3 FixList
9.7.0.3 FixList