Yes, -g solves the problem in this case.
The question is why hangs the engine without -g?
I will try to set forced writes ON and try again!

Henner

> -----Ursprüngliche Nachricht-----
> Von: news@... [mailto:news@...] Im
> Auftrag von Claudio Valderrama C.
> Gesendet: Donnerstag, 21. März 2002 10:26
> An: ib-support@yahoogroups.com
> Betreff: Re: [ib-support] Problems with gbak
>
>
> ""Henner Kollmann"" <Henner.Kollmann@...> wrote in
> message news:001101c1d0ae$59717820$1e5562c1@......
> > Found another solution: If i use gbak -GARBAGE_COLLECT everything
> > works, i can backup the database. OK, some words of the
> data history:
> >
> > 1. Inserts 2.500.000 records into the table
> > 2. Delete this 2.500.000 records
> > 3. Insert 4.500.000 record again
> >
> > After this i want to backup and restore the database to
> make a garbage
> > collection. So the using gbak -g is ok in this case. But why do the
> > engine hang while making an garbage collection in the database?
>
> Aren't you saying that -G solves the problem? When does the
> engine hang then? Anyway, there's no assurace that it's hung
> unless you hook the debugger. I think that you are observing
> a behavior that comes from forced writes turned OFF.
>
> C.
> --
> Claudio Valderrama C. - http://www.cvalde.com -

http://www.firebirdSql.org Independent developer Owner of the Interbase®
WebRing



To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/