Hi Ann,

>> It has happened at a few of our sites. We mostly pick it up at year

end,

>> since the system does not allow you to proceed to the new year, if it
>> thinks there is an imbalance.

>That's not good. Are you actually backing up and restoring on every
>night, or was the original problem that when you found a problem,
>you couldn't fix it overnight?

At the sites where we know it is a regular problem, we now get them to
do a backup-restore once a week. They are retail stores, so they use the
system every day, including Saturday.

>Are there any unusual characteristics of the bad indexes - e.g.
>single key, compound, ascending/descending, unique? Key types -
>character, number?

This is the result of running a DB validation:

Summary of validation errors

Number of index page errors : 477

IBE: Validation completed.

How do I see what those 477 indexes are?

I only know of one index returning wrong values, only because the system
checks and reports on that imbalance.

I have IBExpert - not sure if there is an option there to see them?

(BTW, this database has 622 non-system indices, so it is not all of them
that are corrupt)

>Have you got an example of a database with indexes that give
>the wrong answers that you can send to a developer (Vlad does much
>of the index work)? There's nothing like looking at the actual
>problem...

Found it. It is 60MB zipped.

How can I get it to you?


Thanks
Maya