Re: [Exist-open] Triggering Backups from XQuery corrupts DB - REPRODUCIBLE always

[Wolfgang M. <wol...@ex...>]

I just saw the same exceptions a few days ago and had a quick look at
it. I will need some further investigation, but I suspect it could as
well be an error within the consistency check rather than within
eXist. The consistency check will report failures like the following:

ERR_DOM_INDEX:
Failed to access node 1.834.3 through dom.dbx index. Wrong storage
address. Expected: -1; got: 325146204176472

which indicates that an index entry was missing for node 1.834.3. This
index, however, is not absolutely necessary and eXist should continue
to work correctly.

> Moving forward to new eXist, the same script CORRUPTS DB everytime it runs.

Do you mean the consistency check script corrupts the db? Then we miss
some information. Or just that it reports a possible inconsistency -
as shown above?

The exceptions you posted - and which I can see as well - come from
the consistency check. They should to my best knowledge not be
critical to the functioning of the db. It's an indication that
something might be wrong, either in the consistency check itself or
the database index - we have to see. I'll do some further
investigations tomorrow.

Wolfgang