|
Problem IT03886
|
Status: Closed |
SQLBLOCKALLDIRS, PROBE:910 IS REPORTED AS ERROR IN DB2DIAG.LOG FILE, SHOULD BE REPORTED AS WARNING INSTEAD |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - 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 10.1 Fix Pack 5. *
**************************************************************** |
| Local Fix: |
|
| Solution |
First fixed in DB2 Version 10.1 Fix Pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 20.08.2014
17.07.2015
17.07.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
