Re: repair hangs?

Toby,

the guys who contacted me couldn't tell me anything
about the circumstances which led to the corruption
(system crash, ...). They tried to get things running 
again and thus made it impossible to trace things with
timestamps and the like. All i would like to do is to recover
the database at least partially. Because my knowledge of
mckoi internals converges to zero i do not have the
slightest idea how to accomplish that or wether it is
possible at all. Any hints? Thanx,

Christoph

Am Dienstag, 7. Februar 2006 03:57 schrieb Tobias Downer:
> Christoph,
>
> This can sometimes happen if a record has a corrupt header.  Often it
> indicates overwritten pages in a data file which leads to unrecoverable
> records.  Do you remember if there was any specific event before this
> problem occurred?  These sorts of problems occur under specific
> circumstances that can usually be avoided.
>
> Toby.
>
> Christoph Walzer wrote:
> > Hi,
> >
> > we are using mckoy1.0.3 as the dbms
> > for antville. Unfortunately the database
> > seems to be corrupted. Starting the repair
> > tool yields
> > ....
> > + Repairing V2MasterTableDataSource 108APP_AV_SYSLOG
> > - Store: [ JournalledFileStore: 108APP_AV_SYSLOG ]
> > + 3 area repairs:
> >   Area pointer: 54664
> >   Area size: 144
> >   Area pointer: 54536
> >   Area size: 128
> >   Area pointer: 54504
> >   Area size: 32
> > + Rebuilding free bins.
> > - Store repair complete.
> > - Checking record integrity.
> >
> > At this stage it seems to hang (after 2 hours with
> > a CPU usage of about 98% i gave up). The
> > overall data size is about 7MB. So I cannot
> > imagine that the repair tool takes that long.
> > Any ideas? Thanx in advance,
> >
> > Christoph
>
> ---------------------------------------------------------------
> Mckoi SQL Database mailing list  http://www.mckoi.com/database/
> To unsubscribe, send a message to [email protected]