Bad index pages - fix without gbak backup/restore possible?

[Kjell Rilbe]

Hi,

We suffered a very unexpected server shutdown and after restart, our DB
apparently has two index page errors (reported by gfix).

As far as I understand this means than an index (possibly two) has some
corruption, but no data has been lost.

Can this be fixed without a gbak backup/restore cycle? How?

I would imagine something like 1) identify affected index/indexes
(how?), 2) drop and recreate them.

I'm trying to save time here - since backup restore will take about half
a day.

Mvh,
Kjell

[Dimitry Sibiryakov]

Kjell Rilbe wrote 30.11.2021 18:12:
>
> Can this be fixed without a gbak backup/restore cycle? How?
>
> I would imagine something like 1) identify affected index/indexes (how?), 2)
> drop and recreate them.

ALTER INDEX ... ACTIVE is enough. Dropping is hard for constraint support
indexes.

--
WBR, SD.

[Karol Bieniaszewski]

You can simply try

 

ALTER INDEX INDEX_NAME ACTIVE;

 

regards,

Karol Bieniaszewski

--

You received this message because you are subscribed to the Google Groups "firebird-support" group.

To unsubscribe from this group and stop receiving emails from it, send an email to firebird-suppo...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/firebird-support/460dc7a6-5c52-95af-cef7-96c33fc282c1%40marknadsinformation.se.

 

[Kjell Rilbe]

Thanks to both Dimitry and Karol. Sounds good.

But how do I identify which index it is that's affected?

Kjell

Den 2021-11-30 kl. 18:23, skrev Karol Bieniaszewski:

> You can simply try
>
> ALTER INDEX INDEX_NAME ACTIVE;
>
> regards,
>
> Karol Bieniaszewski
>

> *Od: *Kjell Rilbe <mailto:kjell...@marknadsinformation.se>
> *Wysłano: *wtorek, 30 listopada 2021 18:12
> *Temat: *[firebird-support] Bad index pages - fix without gbak

[Fabiano SCI]

Take a look at the firebird.log file. Index name(s) could be there.