Issue with OP-lock

[jrp611]

I have an issue with a netware 6.5 sp7 server with op-lock's

I read several tid's on the op-locks and the caching is enable=on and level 2 oplicks are also on, checked the client and also is set for on. The problem is after several weeks of the server being up, the server shows op-lock information on the server console and no one can work with the program that uses that data base.after the server is rebooted then all works for a while. I did not have this trouble with SP5. Does anyone know if something has changed or should I try to turn off the client file caching on the server.

Thanks

 

[marvhuffaker]

Here's the deal. turn off oplocks. I don't care what any TID says, turn it off.

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

The thing is, you can either fight with it and always be frustrated, or you can turn them off altogether and move on with life.

With those settings on the server, you shouldn't need anything on the client. This will help your database problems immensely. I set these settings on every server I touch.

Marvin Huffaker, MCNE
Marvin Huffaker Consulting, Inc.
A Novell Platinum Partner

http://www.redjuju.com

 

[goombawaho]

I agree with Marv - that's the way I always set my servers and NO WORRIES were the result.

 

[jrp611]

Marv,
I just changed the settings on the server and will reboot the server tonight.

Thanks for the input

 

[marvhuffaker]

No need to reboot the server, it should take effect immediately. What you should notice is that you won't see more op-lock errors show up on your console.

Also, note... The setting 'should' be sticky, but you may want to add those lines to the top of your AUTOEXEC.NCF to make sure that they don't accidentally get re-enabled. I've seen service packs reset them.

Marvin

Marvin Huffaker, MCNE
Marvin Huffaker Consulting, Inc.
A Novell Platinum Partner

http://www.redjuju.com