dbms error 19

dbms error 19

Post by Barry van » Sat, 12 Mar 2005 20:31:49

Hi all,

Maybe a bit offtopic but it is a problem we encounter more and more at our
clients' sites. Sometimes we get a "DBMS error during fetch operation: 19"
on the magic status bar. It occurs in different screens / different tasks of
our application. However, we cannot reproduce this message, because it doesn't
occur every time we activate those screens/tasks.

We use magic 9 with Pervasive 8 (server engines and local engines), on
Windows2000/Windows2003 platforms. Anyone any idea?

Thanks in advance
Met vriendelijke groet,

Barry van den Reek
Support Manager
Liemar Automatiseringen BV

Tel. : 0031 40 248 4041
Fax : 0031 40 248 3771
website : http://www.yqcomputer.com/

De informatie in dit document heeft een vertrouwelijk karakter en is
dientengevolge uitsluitend bestemd voor de geadresseerde(n). Indien u
niet als geadresseerde bent aangeduid, dient u zich te onthouden van
kennisneming, openbaarmaking en verveelvoudiging van de informatie die
dit document bevat. Indien dit document u kennelijk onbedoeld heeft bereikt,
verzoeken wij u onverwijld contact met ons op te nemen en dit document
te vernietigen. Aan dit bericht kunnen geen rechten worden ontleend.

dbms error 19

Post by John » Wed, 16 Mar 2005 04:36:09

Hi Barry,
Is your Pv8 install patched to SP1 or higher? We had an intermittemt
error19 occur in our application. Never resolved it as such but SP1 made it





dbms error 19

Post by Barry van » Wed, 16 Mar 2005 21:38:39

I'll check that, thanks


dbms error 19

Post by Barry van » Sat, 19 Mar 2005 23:54:22

SP1 didn't solve the problem, anyone another idea? Probably SP2?

Can anybody tell me what the error means?


Message posted via http://www.yqcomputer.com/

dbms error 19

Post by Leonar » Mon, 21 Mar 2005 14:55:23

From: http://www.yqcomputer.com/
19: The application encountered an unrecoverable error
To ensure file integrity, recover the file as described in
Pervasive.SQL User's Guide.
Might want to double check the pvsw.log in the windows directory on
both the client and the server and see if anything is logged.

SP1 probably should have fixed it. I found this in the history notes
for SP1. http://www.yqcomputer.com/
44171 The Client Cache engine could return a status 19 from Extended
Get Operations on a file that has been opened with a read-only handle
if the records that are being cached are updated by another client
that has the file opened read-write.
Since the client cache engine runs on the client machine you did patch
the clients to SP1? or better the SP1 hot fix.
Since SP1 (both client and server right?) did not resolve it, you
could try turning off the client cache engine.


On Fri, 18 Mar 2005 14:54:22 GMT, "Barry van den Reek via

dbms error 19

Post by Barry van » Wed, 23 Mar 2005 17:44:48

Thanks Leonard, they said they had installed SP1, but not on the client.
After this, the error was gone (for the time being)