IBM Support

Error "Namekey conflict with lock-file /tmp/SQLDIR.LK0. Trying another lock" in db2diag log file

Technote (troubleshooting)


Problem(Abstract)

What does error "Namekey conflict with lock-file /tmp/SQLDIR.LK0. Trying another lock" mean?

Symptom

Error in the db2diag log file:

2014-08-27-06.02.04.648053-300 I1179182E582  LEVEL: Error
PID : 9486 TID : 139909847312128  PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000    DB : SAMPLE
APPHDL : 0-20305     APPID: *LOCAL.db2inst1.140827110204
AUTHID : DB2INST1
EDUID : 23802      EDUNAME: db2agent (SAMPLE) 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.


Cause

The SQLDIR.LK0 file is used by DB2 to serialize access to all the filesystems when creating/deleting directories.

It only can be deleted while the instance is down (and *only* when the instance is down). However, as a general rule, we should not need to access/modify/delete the directory anyway.

This can usually occur after an installation or upgrade fails to clean up the SQLDIR.LK0 file from the /tmp directory.


Resolving the problem

1. Bring down all DB2 instances on the server.

db2stop

2. Check the /tmp directory for the SQLDIR.LK0 file. Remove the file if it exists in the directory .

3. Bring the instance back up and monitor to see if the error comes back.

Document information

More support for: DB2 for Linux, UNIX and Windows
Install/Migrate/Upgrade - Fixpak

Software version: 9.5, 9.7, 10.1, 10.5

Operating system(s): AIX, Linux, Windows

Reference #: 1683234

Modified date: 18 November 2015