Subject | Re: [ib-support] Corrupted DB |
---|---|
Author | Jason Chapman (JAC2) |
Post date | 2002-06-18T09:44:03Z |
"Svein Erling Tysvfr" <svein.erling.tysvaer@...> wrote in
message news:3.0.1.32.20020617145245.00a606e0@[158.36.132.22]...
but I support sites with it and _never_ heard of it directly corrupting a
db, ever.
I would try everything before changing the client code. e.g.
1) Move onto another server.
2) Packet sniff every connection string
3) Don't ever do a file copy while the DB is online (even if you don't think
people are connected [I will only copy if I can changed the GDB filename or
the service is stopped]).
4) Stop sweeps (the 20000 difference between seems a little too much of a
coincidence).
Is there anything else in the logs?
I have seen the BDE kill IB5.0 with 100's of open tables on 1M row tables,
but not since 5.6.
Cheers,
JAC
message news:3.0.1.32.20020617145245.00a606e0@[158.36.132.22]...
> Hi Michael!version).
>
> >The first program (used most) connects thruogh Borland BDE (newest
>Slate it for being slow, not naturally client server, dificult to maintain,
> Whenever the BDE is involved, assume it is the guilty party unless you are
> certain there is no error (well, since the BDE has never claimed to work
> with Firebird it's guilt may be limited)!
but I support sites with it and _never_ heard of it directly corrupting a
db, ever.
I would try everything before changing the client code. e.g.
1) Move onto another server.
2) Packet sniff every connection string
3) Don't ever do a file copy while the DB is online (even if you don't think
people are connected [I will only copy if I can changed the GDB filename or
the service is stopped]).
4) Stop sweeps (the 20000 difference between seems a little too much of a
coincidence).
Is there anything else in the logs?
I have seen the BDE kill IB5.0 with 100's of open tables on 1M row tables,
but not since 5.6.
Cheers,
JAC