I think I'm getting a bit out of my depth with helping on this one, but here's 
some more info that may be of some use:

I took a backup of one of the databases that get indices corrupted often (at 
least once a week) when using 2.1.3 and restored it onto our FB 2.1.4 server.

I then did a validation, and checked the Firebird.log - nothing.

I opened our app, and did quite a few things to the database, then did another 
validation, and checked the Firebird logs again - still nothing.

So, I'm relieved to say, my 2.1.3 index corruption problem (that occurs during 
processing) has not migrated into a problem that occurs as soon as you restore 
on 2.1.4. ;-)

At least with your problem though, you can reproduce it at will, so that's a 
good start to getting it fixed..

Just a suggestion: Could you not make some random changes to your data to make 
contents of the data irrelevant, and then submit the database for debugging?













------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

Reply via email to