I have a client running pervasive 9.0 on a Netware 6.5 platform. We
have regular corruptions on the pervasive database table. The latest
is a 16 gig file that seems to be corrupt. Pervasive returns a status
2 when you try to open the database table.

We are using Delphi 2005 as a programming language.

Any ideas or help will be much appreciated.

George van Huyssteen

georgect (AT) gmail (DOT) com wrote:
Does the problem go away when you reboot the Netware server?

I've no experience of Netware 6.5 and P.SQL yet...

There's a long standing problem with the TurboFAT on Netware 5.1 which
causes apparent database corruption. There's an NLM for 5.1 which
disables the TurboFAT and stops the problem happening.

In short, the TurboFAT is a FAT cache which sometimes gets it's self
in a mess and does not accurately reflect what is on the disk. A reboot
clears the cache and causes it to be reloaded correctly from disk.
All is well until the next TurboFAT error.

I may of course be barking up the wrong tree!

Guy
-- --------------------------------------------------------------------
Guy Dawson I.T. Manager Crossflight Ltd
gnues (AT) crossflight (DOT) co.uk

Guy Dawson wrote:
This Groupwise 7 document mentions Groupwise database problems caused
by the TurboFAT on NW 5.x and 6.x

http://www.novell.com/documentation/...s.html#aj1ag8o

and the NLMs that are available to turn the TurboFAT off.

Guy
-- --------------------------------------------------------------------
Guy Dawson I.T. Manager Crossflight Ltd
gnues (AT) crossflight (DOT) co.uk

Start with the TurboFAT problem as the most likely culprit. You can
also find the TURBOD2.EXE update on our website.

If that doesn't help, the server itself could be failing -- memory,
disk controller, disk drivers, etc. If you have a smaller file, we
might be able to do some analysis on it. Submitting a 16GB file for
analysis will take a bit longer and will be costly, but I'd be willing
to look at a small one for no charge.

If we see hardware-level corruption in there, then we can advise about
getting a new server. However, the getting TurboFAT disabled should be
first priority if not yet done.

One other question -- are you storing all parts of the large files in a
single extent? There is a switch in the PSQLv9 engine that allows you
to write either smaller, 2GB extents like PSQLV8, or to write it all as
one big extent. unfortunately, the v9.0 code has several problems with
this switch. If you are using the switch to store the file as a single
piece, then you're advised to change the switch back, and then rebuild
the file to multiple extents. This issue should be resolved with the
next Service Pack.
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive.SQL Service & Support Class - 03/27/06 ***


georgect (AT) gmail (DOT) com wrote: