At 2/17/2004 08:34 AM, Helen Borrie wrote:

>At 08:06 AM 17/02/2004 -0500, you wrote:
> >
> >I noticed the same type of entries in the Firebird log. However, they have
> >no context as to which table the problem belongs to, just the page
> >number. Is there some way to tell from the entries in the log just what
> >table(s) may have a problem? I noticed two different contiguous sets of
> >page numbers, and am now wondering if there were two different tables
> >affected.
>
>No, it's quite normal for data from a table to be spread over different
>blocks of disk.

Ok, so given these entries in the Firebird.log, what is the next
step? Running gfix -v -f will just cause the same entries to be made in
the log. I can't remember right now what the output of gfix is in this
case, but I'm sure it is just as helpful <g>.

If it wasn't for the entries in the backup log, I would never have known
what table(s), index(s), etc are involved. As it is looking right now,
doing an index inactive/active allowed the backup to complete successfully
without errors. I am running a restore of this backup file just to make
sure. However, I could very well have assumed the entire DB was trashed
and started rebuilding my backup from two nights ago.

Bob M..