Hi,
We are on Firebird 1.56 and recently encountered database corruption problem
with a customer. Found that forced write was turned off on the database and
after the database was restored turned it on. However on checking the next day
forced write was again turned off. We do daily sweep,
We found it the ibo components was set to forced write no and that was causing
the problem.
Thanks
--- In firebird-support@yahoogroups.com, Helen Borrie helebor@... wrote:
At 08:55 a.m. 18/07/2013, rddymanohar wrote:
Hi,
We are on Firebird 1.56 and recently encountered database corruption
We recently had database corruptions and had turned on forced write on our
databases on windows environment but we found that after we run our client
application gstat was no more showing the forced write status. We are using
Delphi and IBO components but not sure what in the application is
Hi,
One of our clients has a corrupted database (we are getting internal gds
error). Its a Firebird Database version 1.5.6, the files size is almost 7.5GB,
we are unable to recover it with the normal tools, we have run the Repair
procedure in IBFIRST aid and followed the recommended steps
Hi,
Recently we have started noticing problems at many of our customers
where the index on certain tables are either corrupted or inactive.
These are three different scenarios that we have and I hope you can give
me some info on what is causing this.
1. Index's are in the inactive state.2. Index
