Re: bcheck Error: Bad B-Tree Node (####) Format???

In article <338DC3B3.5C16221C@datapac.com>, Rob Weight <robw@datapac.com> writes >JCHoffman wrote: > >> Both data file and index crash bcheck after showing the following >> error >> codes: >> >> ERROR: Bad B-Tree Node (####) Format (repeated many times before >> Segmentation Fault haults the process. (####) are 4-digit numbers >> (codes). >> Appears only when I check one particular data/idx file. >> >> I've tried archiving older data from this file using SQL, but I >> suspect the >> corrupted index won't allow the deletion to finish. Any way to >> rebuild this >> index without having to roll-back the entire system? >> >> Appreciate any help from the Informix Gods on this one. >> >> Best regards, >> John C. Hoffman >> Taipei, Taiwan [\\] > > Although I've never experienced this exact problem I have run into the >case where >an index is so corrupted that bcheck cannot repair it. In these cases >there is not much >you can do except try lots of different things and pray. I've found the >following things >to work/help: > >1) Make sure you have a good idea of how many records are in the >table. Use >select count(*) if you have no other way of knowing. This will be the>easiest way >to see if you loose data while trying to fix the index problem. > >2) Try unloading the table through isql without using the index(s). >This can be done >by giving no where clause or by using a field that is not in an index >in the where clause. >I suggest doing this first because my experience has been that when the >index is so bad >off that bcheck can't fix it, you usually can't drop/create it either. > Correct - I just do this then drop/rereate the table and required indicies... > >-Rob Weight >robw@datapac.com > -- David Williams