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 IT02081 Status: Geschlossen

Error DIA8003C in db2diag.log when applications were forced off in order to
pursue an exclusive connection in the Database.

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
Error  message in db2diag.log instead of report only Information 
message: 
 
2014-05-21-02.41.12.785000-360 I59232777F594        LEVEL: Error 
PID     : 2104                 TID : 3216           PROC : 
db2syscs.exe 
INSTANCE: DB2                  NODE : 000           DB   : LOCAL 
APPHDL  : 0-33884              APPID: *LOCAL.DB2.140521084120 
AUTHID  : DB2ADMIN             HOSTNAME: xxxxxxxxxxxxx 
EDUID   : 3216                 EDUNAME: db2agent (LOCAL) 
FUNCTION: DB2 UDB, catalog services, 
sqlrl_findFn_encap_sysfunc_access, probe:130 
RETCODE : ZRC=0x80040003=-2147221501=SQLD_INTRP "USER INTERRUPT 
DETECTED" 
          DIA8003C The interrupt  has been received. 
 
Looking at  event log records the agent 3216 received 
interrupted with a FORCE: 
 
[NODE000 : db2agent : 05/21/2014 02:41:12.787815] 
---------------------------------------------------------------- 
EDUID: 952      Event: SQLE_DIAG_EVENT          Sequence No: 
000/677895 
 
ID Type: None 
Diag String: "EvmMgrStat:LocalStop2:LOCAL   " 
 
The problem only happens in a PureScale environment, all system 
applications were forced off in order to pursue an exclusive 
connection in Database. 
That means which someone requested an exclusive connection to 
database and it was granted by first forcing all system apps. 
This action behaves properly, however instead of it receives an 
error message,  it must returns an information note about the 
forced off to get an exclusive connection to the database.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 in version 10.1 Fix Pack 5.                   * 
****************************************************************
Local-Fix:
Ignore the Error message in db2diag.log.
Lösung
First fixed in version 10.1 Fix Pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
28.05.2014
27.07.2015
27.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList