Op-Lock timeout 3

[JulesBirch]

I am running NetWare 5.1 SBS. On the console a message appears from time to time - “Filesys -5.10-183 Station XX has timed out on its OP-LOCK."

Some users are complaining of freezes and slow running. Most users use an Access 97 database most of the time shared over the network.

What does the mesage mean?

Is there any way of stopping these messages from appearing?

Any help greatly appreciateed.

Jules

 

[marvhuffaker]

Best thing to do might be to just turn oplocks off..

Set these two settings:

SET CLIENT FILE CACHING ENABLED=OFF
SET LEVEL 2 OPLOCKS ENABLED=OFF

I'm not sure which one is responsible for that error, but databases generally don't play nice with them turned on.

Marvin Huffaker, MCNE

http://www.redjuju.com

 

[ITsmyfault]

op lock is short for 'opportunistic locking'. This is an issue relating to how windows deals with files on a server. . Best to just turn off oplocks/file caching and call it a day as Marvin suggested.
JM2C

here is an explanation we have in our network docs here (from a veritest report comparing Netware 6 to Win2k)

"Opportunistic locking is an option, available in both NetWare 6.0 and Windows 2000 Advanced Server, that grants clients exclusive access permissions to files available on the shared server volumes. When opportunistic locking is enabled, the client is allowed to maintain locks on the files it accesses, and subsequent read and write requests relating to the locked files can be satisfied from a local cache. By allowing the read and write activity associated with a specific file to be cached locally on the clients,
opportunistic locking can greatly enhance overall file serving performance by significantly reducing the number of read and write requests that require physical access to the server disk resources.

Opportunistic Locking is a setting that is commonly used in the real world for performance enhancement; it is not a “benchmark special” setting. It is enabled by default on Microsoft servers. Opportunistic Locking is on by default for NetWare servers and Novell Windows 2000/NT Clients. NetWare’s Windows 9x clients default to
the Opportunistic Locking setting as off.

The function improves performance overall, but can be disabled if necessary when it may cause data corruption or have other adverse affects on application performance. Situations where a customer may wish to disable the function include the use of applications where a database is shared to multiple users, such as Microsoft Access, or ACT! from Interact Commerce Corp. for example.

To disable opportunistic locking in Windows 2000 Server requires a registry edit as outlined in Microsoft’s Knowledge Base article Q296264, Configuring Opportunistic Locking in Windows 2000
(

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q296264),

which will disable Opportunistic Locking for all clients connected to that server. NetWare clients have an Advanced client property setting that controls the Opportunistic Locking ability of the client, and can be selectively enabled and disabled on a client by client basis. Opportunistic Locking can also be disabled on the NetWare server if desired, at the Client File Caching Enabled prompt in the NCP Parameters section when using the Monitor function, eliminating the function for all clients on that server.

 

[JulesBirch]

Hi

It seems that the comand SET LEVEL 2 OPLOCKS ENABLED=OFF
is not available in version 5.1 of NetWare. Is there any other command that will do the same thing?

Regards


Jules

 

[marvhuffaker]

I forgot that it's not available on NetWare 5.1.. Level 2 oplocks weren't even implemented till NetWare 6.x. So essentially it is already turned off for you. The File Cache setting should do the trick in your case.



Marvin Huffaker, MCNE

http://www.redjuju.com

 

[TheLad]

The command is available on NetWare 5.1, but it depends on what your SP level is as the command is only available in later Service Packs. The server I tested the command on is running NW5.1 SP7

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------