DB2 - Problem description
Problem IC84316 | Status: Closed |
DB2 MAY HANG WHILE OPENING A FILE IF THERE IS A STALE NFS MOUNT | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
Depending on file systems mount order, DB2 instance may block if one or more NFS mounts become stale. If the NFS file system mount is stale and we need to open a file that is in a files ystem that is mounted after that NFS file system, we can hang. Another clue that you may be hitting this issue is that the thread that is hung will not produce a stack with db2pd -stacks (it will be missing from the stack files in the diagpath). You can use an OS utility (pstack, gstack, procstack) to dump the stacks and you will then find the missing stack in a call to sqloFetchAndStoreFSInfoInFileHandle and ossGetDiskInfo. Example top of the thread stack: Thread 25 (Thread 47307022133568 (LWP 12073)): #0 0x00002b067436e115 in _xstat () from /lib64/libc.so.6 #1 0x00002b06739cb288 in ossGetDiskInfo () #2 0x00002b066f7df779 in sqloFetchAndStoreFSInfoInFileHandle () #3 0x00002b066f7de1a8 in sqloopenp () from /db2/DLR/sqllib/lib64/libdb2e.so.1 (...) | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All with NFS * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fixpack 1 or later * **************************************************************** | |
Local Fix: | |
Changing the file system mount order to have NFS file systems mounted after local ones. | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
Problem first fixed in DB2 Version 10.1 Fixpack 1 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.06.2012 05.11.2012 05.11.2012 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.1 | |
10.5.0.1 |