<svanderclock@...> wrote:

>
> Hello,
>
> that a bad new, on FB2.1.4 i do a gfix today and the result say
> Index Page in ERROR: 1
>
> in the firebird.log i have :
>
> SERVER22 Mon Mar 22 17:17:06 2010
> Database: E:\DATA.FDB
> Index 10 is corrupt on page 1696356 level 0. File: ..\..\..\src\jrd\validation.cpp, line: 1561
> in table TRANSAC_SEARCH_VAC_A_2 (265)

I never saw this error. It means wrong order of record numbers in duplicates chain of some index entry. Could you show DDL of this index ?

> but this must be take with precaution, because today we have a power shuntdown in the datacenter making the server shuntdown suddenly ..

I can't said if it was as reason for corruption. I recommend to run gfix -v -full every day (night) when (if) it is possible.

> but before this shuntdow, i see in the firebird log these entries :
>
> SERVER22 Mon Mar 22 15:10:23 2010
> Fatal lock manager error: invalid lock id (2438872), errno: 0

Hmm... this error usually means than engine tried to use lock which was already freed.

> SERVER22 Mon Mar 22 02:23:42 2010
> Fatal lock manager error: invalid lock id (4340656), errno: 0

Note, this second message have timestamp (02:23:42) less than first message (15:10:23). Is it really true ?

> SERVER22 Mon Mar 22 14:30:27 2010
> Fatal lock manager error: invalid lock id (2408344), errno: 0
>

Next 5 messages have the same timestamp, do you know if something special was performed at this time ? Do you use nbackup, for example ?

Regards,
Vlad