Hi,
I have a client running Pervasive 2000 SP2 on a Win2000 Server. Every few
weeks the NTDBSMGR will hang, taking 100%CPU and stopping users access.
Stopping and Starting pervasive services will only fix the problem fro a
short period. Rebooting server will fix it for a few weeks. We are unable
to patch this site to 2000i due to another file locking problem.

PVSW.LOG entry corresponding to the time of the problem:

System Error: 620.5.33 File: D:\DATABASE\DATA\YYY.MKD

I can't find anything on Pervasive's website about this error.

I am guessing it is some sort of memory leak?

Any ideas?


John

Probably not actually a Pervasive problem.

The syntax of the "System Error:" entry in the pvsw.log is
620. - Specific location in the database engine. 600's are Win32
specific.
..5. - is the Btrieve API op-code.
..33 - is the status code returned by the OS.

In this case I look up the Win32 Status 33 and get:
33,ERROR_LOCK_VIOLATION,The process cannot access the file because
another process has locked a portion of the file.

So the database engine has logged that the OS says the file is locked
"BY ANOTHER PROCESS".

In order of likelyhood:
1) Anti-virus software. Exclude the data files from real-time
anti-virus scans. You may see a significant performance improvement
as well as getting rid of these locks.
2) Backup Software. Use Continuous operations.
3) other.

To really dig to the bottom of it you may want to try "filemon" from
www.sysinternals.com . It will let you filter by filename (if it
always the same) or wildcard. I do not think anti-virus will show up
though as it is a hook in the file IO, not actual file IO.

Leonard

On Thu, 15 Jan 2004 13:32:38 +1300, "John Anisy"
<j.anisy (AT) cchlawbase (DOT) co.nz> wrote:

"John Anisy" <j.anisy (AT) cchlawbase (DOT) co.nz> wrote

I'm not positive by I think you can free updates for that engine on
pervasive.com to bring it up to 2000i SP4.

--
Brad Kunkel
Integrated Business, Inc.

The continuous operations at this site wasnt working and that is probably
the problem. Got it sorted and tested it and when taking the files off
continuous operations the engine stopped responding, Pervasive KB says this
is a problem with SP2 releasing from continuous ops when the file is in use,
(which is kind of the point) - defect 29318 . resolution was to patch to
SP3 which we can't do. Might just have to put up with it.


"Leonard" <lharvey (AT) austin (DOT) rr.com> wrote