Hi,

I have some updates. I've tried to duplicate affected table and make new
indexes, but error happens again on that newly created table. Now im
trying to backup and restore DB using 2.1.4 snapshot. Hopefully it will
work.

Milan


Dne 01.02.2010 10:39, Milan Tome� - Position napsal(a):

>
>
>
> Dne 01.02.2010 10:31, Alan McDonald napsal(a):
> >
> > > Hi all,
> > >
> > > I've problem with indexes in my DB. I did a full validation of DB and
> > > it
> > > returns 8 index errors. I looked into the log file and all of them
> > > belongs to table STREETS (it contains like 50+ millions records). So I
> > > deactivated all indices and dropped PK. Then I did full validation
> > > again
> > > with no errors. So next step was to recreate PK and activate all other
> > > indices. When it finishes I ran full validation again and there were
> > > again 8 index errors. Error message in log file is "Index 1 is corrupt
> > > (missing entries) in table STREETS (155)".
> > >
> > > I'm running Windows 2008 R2 server, Firebird 2.1.3.18185, ODS 11.1
> > >
> > > I also tried to backup and restore my DB, but restore failed with
> > > "unable to allocate memory from operating system" message.
> > >
> > > Thanks for any help
> > >
> > > Milan Tomes
> >
> > try 2.1.4 snapshot.
> > I had memory leakage(loss) with 2.1.3 due to transliteration of blob
> > fields.
> > (same OS message unable to allocate... etc)
> > I don't know what characterset you use of if you have blob fields in
> this
> > table, but it's worth a go cause it solved my problems moving to 2.1.4
> > snapshot
> > Alan
> >
>
> I'm using only binary blobs. But I'll try it.
>
> Thanks for your recommendation.
>
> Milan
>
>

[Non-text portions of this message have been removed]