internal gds software consistency check (wrong record length (183))

[devin palmer]

Hello all,

My database is corrupt. one one table when I try to select a record
I get the error:

internal gds software consistency check (wrong record length (183))

So I tried these steps:
gfix -v -f -user username -pass xxx dbfile.gdb
gfix -mend -full -ignore -user username -pass xxx dbfile.gdb
gbak -b -ignore -garbage_collect -user username -pass xxx dbfile.gdb
dbfile.gbk

when I do that I get the same error when Interbase tries to backup the
corrupted table.
Somebody please help, thank you in advance.

Devin Palmer,
Inroad Solutions

[Bjørge Sæther]

Hi !

I've got this error when I did some illegal manipulations in RDB$
tables, or when I otherwise got the metadata out of synch with the
database contents.
You could try a search at www.mers.com, the best collection of IB topics
I have seen. Try to paste this into your browser:

http://www.mers.com/cgi-bin/srchcgi.exe/EXECSEARCH?pageno=1&linktype=sea
rch&searchtext=wrong+record+length+%28183&grouptext=

...I just did...;-)
--
Bjoerge Saether
Consultant / Developer
Asker, Norway
bsaether....@online.no (remove the obvious)

devin palmer skrev i meldingen <389F49A1...@inroad.net>...

[wangrl]

I meet the same question,and I use InterBase 4.2 in Win95.Do you sure that
version 5.6 can fix it,or Borland say is that.
The web site
http://www.mers.com/cgi-bin/srchcgi.exe/EXECSEARCH?pageno=1&linktype=sea
is not include this question!

J. Jongma wrote:

> >
> > Hello all,
> >
> > My database is corrupt. one one table when I try to select a record
> > I get the error:
> >
> > internal gds software consistency check (wrong record length (183))
> >
> > So I tried these steps:
> > gfix -v -f -user username -pass xxx dbfile.gdb
> > gfix -mend -full -ignore -user username -pass xxx dbfile.gdb
> > gbak -b -ignore -garbage_collect -user username -pass xxx dbfile.gdb
> > dbfile.gbk
> >
> > when I do that I get the same error when Interbase tries to backup the
> > corrupted table.
> > Somebody please help, thank you in advance.
>

> We've been struggling with this problem for quite some time and fixed it.
> You're probably using InterBase 5.5? If so, upgrade to InterBase 5.6. It
> made the error go away for us. There is a catch though, if you keep using
> your dbfile you'll keep getting the error! You have to remake the database,
> or restore it from a backup older than the first time the problem occured.
> We tried fixing the database, but with no success.
>
> -Jorrit Jongma
> S-WARE
> sda...@dds.nl
>
> > Devin Palmer,
> > Inroad Solutions

[Claudio Valderrama C.]

I've used IB 4.2 on NT for years with no problems.
This is not to dismiss your problem, of course.
Usually, when you get weird error, you should do:
- Shut down IB
- Make a copy of your db with operating system commands
- Restart IB
- Try the options of gfix. Ok, you tried them.
- If they don't work, be careful that if the error is serious, gfix can
mangle things worse in some cases... the same that might happen with a very
bad FAT if you try to fix it with Norton Disk Doctor.
- Try to backup the database WITHOUT garbage collection. Since gfix already
modified it, try to backup the copy you made. There are other flags to
ignore more errors. in gbak
- If you are able to backup with this mode, try to restore.

C.
--
---------
Claudio Valderrama C.
Ingeniero en Informática - Consultor independiente
http://members.xoom.com/cvalde

wangrl wrote in message <38BFE0E2...@hotmail.com>...