Novell 5.1 Data Access Issues

[RHankinsJr]

I am using Novell 5.1 with sp9 overlay ( the latest, I think it is 9 ). With Windows XP Pro workstations using the latest client for them available from the site.

I am having some issues with accessing data on it.

1) When I access data from one machine then close that file, the server does not release that file for approx 30 seconds.

2) May be related to 1. When a lock occurs on a multiuser data file, that lock is not always released when it should be on the server.

3) On a multiuser file ( DBase style DBF ) sometimes the information from one workstation is not written to the file, yet the information from the another workstation writes out fine. It is random as to which workstation gets it's information written out.

I would be very interested in getting these items lined out, a quick fulltext search netted me no useable results. Hopefully someone else has experienced these issues as well.

TIA,

RHankinsJr

Richard L. Hankins Jr.
Senior Programmer
Auction Services, Inc.

 

[marvhuffaker]

This is probably because of 'enhanced' file caching that is enabled on the server. I turn it off on every server I touch, it causes big problems with databases.

On the server console, type this command:

SET CLIENT FILE CACHING ENABLED=OFF


Add the same command to the top of the AUTOEXEC.NCF file to make sure this setting stays configured. AUTOEXEC.NCF can be found in the SYS:SYSTEM folder.

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

http://www.redjuju.com

 

[RHankinsJr]

If I set file caching off and attempt to shut off type 2 oplocks as well, what settings should be on the workstations?

Will I still need to turn the oplocks off on the XP machines or should I leave them turned on as default?

Thanks In Advance,


Richard L. Hankins Jr.
Senior Programmer
Auction Services, Inc.

 

[marvhuffaker]

When you turn them off at the server, there is nothing that needs to be done on the workstation.

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

http://www.redjuju.com

 

[marvhuffaker]

I also would like to point out that this setting can be changed on the fly, it takes effect immediately, and you don't have to reboot the server.

There is no adverse effect on the client workstations, so it's not something that has to take a lot of thought or extensive planning to implement. Just turn it off and be done with it.

Marvin

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

http://www.redjuju.com