how to use process monitor to view file lock

This scenario appears to be common on Windows, and more specifically, the 'external process' is often a virus scanner or OS backup. In that event, it is expected behavior for DB2 to shut down.

These messages suggests there have a software that run around the time of the panic/crash that may be holding a file that was supposed to be accessed by only DB2, but somehow was locked by this external process/software. Pagekey: PPNum:97039Īnd the db2pd -tablespace output, we can identify the locked file was container for a table space. ĭATA #3 : Buffer page descriptor, PD_TYPE_SQLB_BPD, 128 bytes PID : 9052 TID : 8748 PROC : db2syscs.exeįUNCTION: DB2 UDB, buffer pool services, sqlbClnrAsyncWriteCompletion, probe:40 OSERR : 33 'The process cannot access the file because another process has locked a portion of the file.' PID : 9052 TID : 6516 PROC : db2syscs.exeįUNCTION: DB2 UDB, oper system services, sqloDispatchNBlocks, probe:110 Here is a snippet of the logged messages around the time of the crashes:

How to use process monitor to view file lock