Hi!
I don't have that documentation but I recently faced that problem
while filling a GDB with the contents of a DBF. There's a physical
limitation of 2Gb per file and if you reach it Interbase doesn't report
anything, it just behaves oddly. I mean, I couldn't make changes
like adding constraints, but I still could query the database. (?)
As you say, I couldn't apply the gfix neither (it got connected but
hung up). I had to backup and restore with the multiple files option,
slicing the database in 4 chunks of 1Gb (just to be safe, I expected
3 Gb of data).
Hope this helps you in some way.

Pablo

> Has anyone any documentation on the GDB file physical

structure?

> I'm facing a lot of customers reporting corrupted databases,

many of

> them being corrupted beyond the capability of gfix. (i.e. I could

not

> even connect to the database). I really dont know how a

database can

> become so corrupt that even Connect() fails -- I guess my

customers have

> a special gift or they like to play with the computer's power cord.

So I

> thought I might write a tool to diagnose/repair these problems or

to

> save the available data in a newly created database, but I can't

seem to

> find any description on the GDB file.
>
> Thanks in advance.
> Stefan
>
>
> ----------------------------------------------------------------------
> -- Get a NextCard Visa, in 30 seconds! 1. Fill in the brief

application

> 2. Receive approval decision within 30 seconds 3. Get rates as

low as

> 2.9% Intro or 9.9% Fixed APR Apply NOW!
> http://click.egroups.com/1/975/3/_/679568/_/955113841/
> ----------------------------------------------------------------------
> --
>
> Community email addresses:
> Post message: IBDI@onelist.com
> Subscribe: IBDI-subscribe@onelist.com
> Unsubscribe: IBDI-unsubscribe@onelist.com
> List owner: IBDI-owner@onelist.com
>
> Shortcut URL to this page:
> http://www.onelist.com/community/IBDI
>