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

SQLBLOCKALLDIRS, PROBE:910 IS REPORTED AS ERROR IN DB2DIAG.LOG FILE, SHOULD
BE REPORTED AS WARNING INSTEAD

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
The following message might be written to the db2diag.log file: 
 
2014-03-19-11.45.03.444914+060 I34084694E574       LEVEL: Error 
PID     : 54847                TID  : 139675868063488 PROC : 
db2sysc 0 
INSTANCE: xxxxx               NODE : 000          DB   : yyy 
APPHDL  : 0-8926               APPID: *LOCAL.xxxxx.140319104505 
AUTHID  : XXXXX 
EDUID   : 285                  EDUNAME: db2agent (yyy) 0 
FUNCTION: DB2 UDB, buffer pool services, sqlbLockAllDirs, 
probe:910 
MESSAGE : ZRC=0x800F00AD=-2146500435=SQLO_NLCK_NAMEKEY_CONFLICT 
"Unknown" 
DATA #1 : <preformatted> 
Namekey conflict with lock-file /tmp/SQLDIR.LK0. Trying another 
lock. 
 
As the database continues working with a different lock without 
problem, this message should not be reported as an ERROR. 
This APAR will change the message to be reported as a WARNING 
instead.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5.                      * 
****************************************************************
Local-Fix:
Lösung
First fixed in DB2 Version 10.1 Fix Pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
20.08.2014
17.07.2015
17.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList