-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hallo Btrivieans!

since some days we got the followning messeages in the pvsw.log on the server
(win2000, Pervasice SQL 8.x)


02-10-2006 01:04:25 NTMKDE 000004C4 NTDBSMGR.EXE SERVER-XYZ W
Page server invalidation list is full
02-11-2006 01:02:00 NTMKDE 000004C4 NTDBSMGR.EXE SERVER-XYZ W
Page server invalidation list is full
02-14-2006 01:04:06 NTMKDE 000004C4 NTDBSMGR.EXE SERVER-XYZ W
Page server invalidation list is full

Do you know waht this means, and if we can or even have to do something against?

(I can not find anything about "invalidation list" on pervasive.com nor in the
documentation...)

Any hint will be wellcome!

Reagsrds from Jena
M.Malarski
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3-cvs (MingW32)
Comment: GnuPT 2.7.6
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFD8d4GjJri453BSEQRAoPFAJ4+UuhjdkG5WUuzrhd5Wr DWGUGHuwCg8UZ1
fcCBL/dKqSRinvGdso2yvAQ=
=M4pY
-----END PGP SIGNATURE-----

Well, the good news is that occasionally getting that message means
that everything is working (mostly) the way it should be.

Pervasive.SQL V8 added a new feature called the "Client Cache Engine".
Roughly speaking it is a database engine running on the client that
does read-only caching. It makes page IO requests to the server for
data. The flip side is that being a cache there has to be some way to
get rid of stale pages in it. The server keeps track of which pages
in the files change and send those lists to the clients that are
running the cache engine.. 8.0 had issues with that process.

This looks to be the more typical "occasional" inval list full. It
may just be that there are some clients on your network that are not
running the cache engine. As such the engine can't send them the
inval list for their cache since it isn't running so it occasionally
builds up to the point where it just dumps the list (and tells the
cache engines that are running to flush everything since it "lost
track)

If you are on a current release (I suggest 8.7) and everybody is using
the client cache engine (it has to be the same version as the server)
then I would not expect to see those messages. Likewise if nobody
uses the cache engine you won't see the message either.

Leonard

On Tue, 14 Feb 2006 14:41:26 +0100, nmm
<Mircea.Malarski (AT) onlinehome (DOT) de> wrote: