File locked errors

[dcbennett007]

Hi there, we are running an old database program called Advanced
Revelations. On Netware 4.11 the program ran flawlessly, but since we have
upgraded our file server to Netware 6, we have been getting file lock
errors on DB files. At first we suspected our backups as the time that the
file lock errors started corrosponded with the backup times. Over the
weekend I had our backup Novell server running with the DB open and I got
the same message. There weren't any backups running on it at all.
We have gone to straight IP as well as updated our NLM's and we haven't
been able to figure this one out.
Does anyone have any ideas?

Thanks in advance
Derrick

 

[marvhuffaker]

Make sure you are on NW6SP4 (or NW6SP3 + NSS Patches). And run these commands from the console, and then put them in the AUTOEXEC.NCF to make sure they never get turned back on.

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

Try that and report back.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[terry712]

not seen arev for a long time
imagine the settings above should fix it
what client are you using - is it running in a dos window?

i still have a few servers running arev but i'm afraid they are 3.12 -- and clients are using netx (yep no vlm there yet)

 

[dcbennett007]

Thanks for the replies.
Sorry, I should have specified a little more.
Server is Netware 6 SP4
NLM's were updated to a universal driver

I ran those 2 SET commands at the console and they were both already set to off.

terry, yeah it is a bit of an archaic DB program
Client machines are running Windows NT/XP with NW client 4.83 SP1/SP2 The user interface is a DOS window. We are in the midst of updating Arev to v 3.12 so we can use the open insight interface, but currently it is v 2.12

Originally when we first updated to Netware6, we thought it was the backup software as we use Legato Networker and St. Bernard's Open File Manager. The OFM version we were using wasn't compatible with NW6 and wasn't syncronizing with the server. I recently updated that so that everything sync's up. And the files it is showing that it locks are not any of the DB files.
So now we are kind of stumped.

 

[terry712]

are pc's same?

assume that pc's are ip only and server is ip only as well - no scmd

in monitor i assume one person locks db and program has issues until you kick this persson?

i cant really think what to suggest

 

[marvhuffaker]

Do you guys get any errors on the console (or in SYS$LOG.ERR)? When the files lock, are you able to clear the connection or do you have to bring the server down to release them?



Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[dcbennett007]

PC's are running straight IP. IPX was removed from the Novell Client.
Typically what happens is, the user is logged into the DB and creating files etc... and all of a sudden they will get the error
"Error while writing data." "path\filename is a read only file"
and they can usually exit the program and log back in and it will be ok again. Files are mainly DB system/background files not the "file/entry" that the user is creating.
On occassion, the server will get a little worse off and we will have to down it.

Only message in SYS$LOG.ERR is
5-26-2004 3:13:54 am: SERVER-5.60-1533
Severity = 4 Locus = 3 Class = 6
Device "[V098-A4-D4:0] Open File Manager Synchronized Device" deactivated due to driver unload

But this is after the backup is complete and the OFM will deactivate itself.

Thanks again for the replies. I am really looking forward to resolving this

 

[Ed Andres]

I would look at the most recent client version 4.91sp1a. I had a similar locking issue with a Foxpro database using just the 4.9 client and the update seemed to fix the problem.

HTH
Ed