dear vlad,

sorry for the delay i was in travel !

> > 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 ?

Actually i backup and restore the database
the detail of the TRANSAC_SEARCH_VAC_A_2 :

TRANSAC_SEARCH_VAC_A_2 (350)
Primary pointer page: 689, Index root page: 690
Data pages: 47434, data page slots: 47434, average fill: 82%
Fill distribution:
0 - 19% = 1
20 - 39% = 0
40 - 59% = 0
60 - 79% = 690
80 - 99% = 46743

Index TRANSAC_SEARCH_1163_IDX (10)
Depth: 3, leaf buckets: 3113, nodes: 1395200
Average data length: 3.02, total dup: 6360, max dup: 4
Fill distribution:
0 - 19% = 0
20 - 39% = 9
40 - 59% = 108
60 - 79% = 10
80 - 99% = 2986

Index TRANSAC_SEARCH_1164_IDX (11)
Depth: 3, leaf buckets: 3324, nodes: 1395200
Average data length: 3.30, total dup: 0, max dup: 0
Fill distribution:
0 - 19% = 2
20 - 39% = 5
40 - 59% = 108
60 - 79% = 8
80 - 99% = 3201

Index TRANSAC_SEARCH_1165_IDX (12)
Depth: 3, leaf buckets: 3300, nodes: 1395200
Average data length: 3.84, total dup: 889232, max dup: 4477
Fill distribution:
0 - 19% = 0
20 - 39% = 12
40 - 59% = 100
60 - 79% = 14
80 - 99% = 3174

Index TRANSAC_SEARCH_1166_IDX (13)
Depth: 3, leaf buckets: 3305, nodes: 1395200
Average data length: 3.85, total dup: 889232, max dup: 4477
Fill distribution:
0 - 19% = 1
20 - 39% = 9
40 - 59% = 109
60 - 79% = 9
80 - 99% = 3177

Index TRANSAC_SEARCH_1167_IDX (14)
Depth: 3, leaf buckets: 1992, nodes: 1395200
Average data length: 0.51, total dup: 1307485, max dup: 21979
Fill distribution:
0 - 19% = 0
20 - 39% = 10
40 - 59% = 99
60 - 79% = 11
80 - 99% = 1872

Index TRANSAC_SEARCH_163_IDX (2)
Depth: 3, leaf buckets: 1751, nodes: 1395200
Average data length: 0.06, total dup: 1385193, max dup: 75747
Fill distribution:
0 - 19% = 0
20 - 39% = 0
40 - 59% = 36
60 - 79% = 3
80 - 99% = 1712

Index TRANSAC_SEARCH_164_IDX (3)
Depth: 3, leaf buckets: 1751, nodes: 1395200
Average data length: 0.06, total dup: 1385193, max dup: 75747
Fill distribution:
0 - 19% = 0
20 - 39% = 0
40 - 59% = 36
60 - 79% = 3
80 - 99% = 1712

Index TRANSAC_SEARCH_165_IDX (4)
Depth: 3, leaf buckets: 1683, nodes: 1395200
Average data length: 0.00, total dup: 1395167, max dup: 372474
Fill distribution:
0 - 19% = 0
20 - 39% = 0
40 - 59% = 11
60 - 79% = 3
80 - 99% = 1669

Index TRANSAC_SEARCH_166_IDX (0)
Depth: 3, leaf buckets: 3011, nodes: 1395200
Average data length: 0.13, total dup: 1265320, max dup: 29
Fill distribution:
0 - 19% = 0
20 - 39% = 1
40 - 59% = 2754
60 - 79% = 157
80 - 99% = 99

Index TRANSAC_SEARCH_167_IDX (5)
Depth: 3, leaf buckets: 3052, nodes: 1395200
Average data length: 2.85, total dup: 7344, max dup: 4
Fill distribution:
0 - 19% = 0
20 - 39% = 73
40 - 59% = 8
60 - 79% = 75
80 - 99% = 2896

Index TRANSAC_SEARCH_168_IDX (6)
Depth: 3, leaf buckets: 3287, nodes: 1395200
Average data length: 3.17, total dup: 9, max dup: 1
Fill distribution:
0 - 19% = 1
20 - 39% = 71
40 - 59% = 16
60 - 79% = 72
80 - 99% = 3127

Index TRANSAC_SEARCH_169_IDX (7)
Depth: 3, leaf buckets: 3244, nodes: 1395200
Average data length: 3.63, total dup: 902280, max dup: 4997
Fill distribution:
0 - 19% = 0
20 - 39% = 81
40 - 59% = 14
60 - 79% = 96
80 - 99% = 3053

Index TRANSAC_SEARCH_170_IDX (8)
Depth: 3, leaf buckets: 3252, nodes: 1395200
Average data length: 3.64, total dup: 902280, max dup: 4997
Fill distribution:
0 - 19% = 0
20 - 39% = 93
40 - 59% = 12
60 - 79% = 92
80 - 99% = 3055

Index TRANSAC_SEARCH_171_IDX (9)
Depth: 3, leaf buckets: 1961, nodes: 1395200
Average data length: 0.39, total dup: 1315505, max dup: 34464
Fill distribution:
0 - 19% = 0
20 - 39% = 76
40 - 59% = 3
60 - 79% = 77
80 - 99% = 1805

Index TRANSAC_SEARCH_3437_IDX (1)
Depth: 3, leaf buckets: 1721, nodes: 1395200
Average data length: 0.00, total dup: 1395196, max dup: 783331
Fill distribution:
0 - 19% = 0
20 - 39% = 0
40 - 59% = 3
60 - 79% = 1
80 - 99% = 1717

>
> > 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.

the problem is that gfix -v is very memory and processor intensive ! it's use close to all te available memory :( launching it every day is a little hard for a 24*24 available server :(

> > 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 ?

no, nothing special was performed at this time. we don't use nbackup (only gbak and not at this time)

thanks for all
stephane