From: Borut Maricic [mailto:borut.mari...@borut.eu] >Oh, yes, unfortunately we have. >In fact, we became aware of this for the first time under 2.1.4
Just some more info here. When you restore a database, it looks at your index definitions, and current data, and builds the indices from that. That is why backing up and restoring will rectify the problem (temporarily, till a new corruption occurs) I find I only see the index error in Firebird.log after doing a Database Validation (which doesn't fix the error, just reports it) So, if I just optimise, the problem just gets fixed with no signs of a problem being posted to the Firebird.log (|just letting you know, so you are aware where and when these messages are seen) I think Vlad is going to need a copy of your database you get to the bottom of the problem, so if you're customer is not going to allow that, it's going to be a problem :-( I have 4 or 5 large clients with this problem, and I am in the process of convincing them to try 2.1.4. We have a few other sites who have updated, but they never had a problem before, and are not noticing any difference at all between versions, so that's good but nothing conclusive yet with regards to index corruptions. Will post the results here, as soon as I have them... Are there perhaps any other messages in your Firebird.log apart from the index corruption ones? Maya ------------------------------------------------------------------------------ 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
