Hi everybody

We have PSQL.7 SP3 on W2K (SP4).

Sometimes we can found the following entry in the PVSW.LOG file:

08-28-2003 14:36:35 NTMKDE 00000834 NTDBSMGR.EXE MWBDB01
E System Error: 112.23.0

Has anybody an idea what problem this is? None of the users reports any
problem. Any help is welcome!


--
Regards
Rolf Ackermann

Rolf,

Systemerror 112.23.0:

112 : internal error in IO_subsys
23 : Operation Code : Get Direct/Chunk
0 : OS errorcode : none

Most IO_subsys errors are the result of file corruption. You might
want to try rebuilding the file and see if that solves your problem.

Strange thing is that you get this error on a Get Direct, which would
imply you already have position and thus that the requested info
should already be in Pervasives cache. There should be no need for
additional I/O unless the record has a large variable length part that
hasn't all been read into cache or unless you're cache is being
swapped out to disk by the OS.


On Thu, 28 Aug 2003 14:45:12 +0200, Rolf Ackermann
<rolf.ackermann (AT) spin (DOT) ch> wrote:


Gordon Bos
Q-RY Solutions
+31-(0)15-2564035

http://www.q-ry.nl/

OR, it could be that the application is tracking records by physical
position somehow, and periodically a deleted record gets accessed. Since
the record may no longer exist, the GetDirect fails. In this case, this
error would NOT indicate corruption, but rather just indicates poorly
designed code.
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Pervasive.SQL Service & Support Classes ***
Chicago: September 16-18: See our web site for details!

Gordon wrote:

Thought about that, but figured this would require external index
files. Never seen anyone use them, so I tossed it out ;-)

On 30 Aug 2003 04:51:31 GMT, Bill Bach <bbach (AT) cncdsl (DOT) com> wrote:


Gordon Bos
Q-RY Solutions
+31-(0)15-2564035

http://www.q-ry.nl/

Actually, not all apps need to use this. I have seen this status code come
back from an application in the past -- just users trying to recall records
that had been recently deleted, yet still in someone's scroll window (since
GetNextExtended returns this data)...
BB

Gordon wrote: