oplocks and client file caching ?
I´m having some thought about oplocks and client file caching.
Once in a while I get error messages on the nw console (one server running
nw6.5.5 and one nw6.0.5), the messages looks something like this:
Station 199 (task 6) timed out waiting for an op-lock on file <filename>
held by station 181
Could these problems be resolved by:
SET CLIENT FILE CACHING ENABLED = OFF
SET LEVEL 2 OPLOCKS ENABLED = OFF
Also, is it possible that these settings could result in some unwanted