Vlad has done some interesting examination of the
index handling code and offered a second possible
explanation of these errors.

My theory requires that the server or at least one
of server processes crash. Without crashes, my
theoretical problem can't occur.

Vlad's theory requires that entries be removed and
inserted in the same value range to the extend that
an index page first splits and is then recombined.


So, for those of you who have highly concurrent
applications running 1.5.3 Classic and are seeing
occasional corrupt indexes with a wrong page type
in the index (expected 7 encountered 5) - do your
environments resemble either of these?


Regards,


Ann