Solution : https://service.sap.com/sap/support/notes/690449 (SAP Service marketplace login required)
Summary :
The SAP transport buffer lock file (SID.LOB) issue arises when the OS doesn't release the lock on the file, which is meant to prevent simultaneous access by multiple tp processes. This file should be deleted post-transport buffer update by tp.exe and resides typically in the \\hostname\sapmnt\trans\tmp directory. If the .LOB file still appears locked, verification steps involve checking the presence of the process ID from the .LOB content or, if absent, using "net file" to remove the network handle and then manually deleting the .LOB file. Persistent issues suggest disabling opportunistic locking by tweaking the registry at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanserver\Parameters.
Key words :
hkey_local_machine\system\currentcontrolset\services\lanmanserver\ parametersenableoplocks, $\usr\sap\trans\tmp\<sid>, \\<hostname>\sapmnt\trans\tmp folder, \\<hostname>\sapmnt\trans\tmp\<sid>, \\ <hostname>\sapmnt\trans\tmp\ <sid>, net file <file id> /close, latest windows service pack, tp processes access simultaneously, opportunistic locking agorithm leads, opportunistic locking algorithm problem
Related Notes :
| 1223360 | Composite SAP Note: Performance optimization during import |
| 132536 | Improved semaphore mechanism in tp |
| 12746 | WARN <file> is already in use (), I'm waiting 5 sec |