--- In firebird-support@yahoogroups.com, "Ann W. Harrison"
<aharrison@...> wrote:

> Did you use the -g switch on gbak? Although gbak
> doesn't use indexes to find data, it will touch
> indexes when doing garbage collection.

Okay, it works without garbage collection.

> Dropping and recreating that index should also make the
> database usable.

> >
> > Is there any known problem of this combination (VARCHAR and
> > UNIQUE) under high load? Now my first attempt to solve this
> > problem is to remove the "UNIQUE" (the GUID is unique anyway).
>
> No... The problem is that a page has been lost from the index
> which should not be affected by uniqueness - just by the frequency
> of use. In particular, delete and update activity.
>...

Okay, the DB was corrupt today once again (same index as always). I
have removed the index now and I am waiting if it crashes again. The
table is used to send messages (~20 per second) between applications,
and after receiving they will be deleted - doesn't seem to be a good
idea. It's interesting that it's always the same index that get's
corrupt. So the solution could be to mark received messages instead
and delete them from time to time?

Thank you very much!
Mark