Subject | Re: [ib-support] gbak error (2nd post) |
---|---|
Author | Duilio Foschi |
Post date | 2002-02-08T07:40:19Z |
David,
yes, it seems that the db was corrupted.
I had to delete it and pump again data into it.
Coming to how:
I played a lot with the db: deleting and re-creating constraints, fields
and whole tables, etc
But I always used SQL or the visual i/f of QuickDesk
One thing comes to mind: sometimes I abruptly halted a transaction from
Delphi using CTRL-F2: could this corrupt the db ?
Thank you
Duilio
yes, it seems that the db was corrupted.
I had to delete it and pump again data into it.
Coming to how:
>1. You were playing around with command line tools ;-)no: I just learnt a little bit how to use gbak
>2. The W2000 machine crashedno. I am amazed to see a MS product working 4 weeks w/o crashing :)
>3. You were using IBConsole or some other admin tool known to beI mostly used WISQL and QuickDesk.
>seriously buggy
I played a lot with the db: deleting and re-creating constraints, fields
and whole tables, etc
But I always used SQL or the visual i/f of QuickDesk
>4. You were using different connect strings from Windows clientno
>machines.
>5. You were mixing remote and local access to the same database (I'mno
>pretty sure that's a no-no, from what I've read, but I've never tried
>it myself ;-))
One thing comes to mind: sometimes I abruptly halted a transaction from
Delphi using CTRL-F2: could this corrupt the db ?
>Hopefully, it means you were using a test database that can behappily this was - more or less - the case: the db was not yet in production
>re-created from a script... :-)
Thank you
Duilio