home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT03845 Status: Closed

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

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
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 Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 10.                      * 
****************************************************************
Local Fix:
Solution
First fixed in DB2 Version 9.7 Fix Pack 10.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.08.2014
09.12.2014
09.12.2014
Problem solved at the following versions (IBM BugInfos)
9.7.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.10 FixList