> However, the important thing to note is, that backing up and restoring
> does not rectify the problem! Backing up and restoring finish their
> respective jobs without problems, but the validation problem is
> *immediately* there (i.e. without any usage of the DB between restoring
> and validating).
Interesting. Could you provide DDL of table and index ? Also tell us what
is charset of database.
> The index build during restore creates this problem with these two large
> DBs absolutely always, i.e. corruption is in this case apparently always
> repeatable. (We experienced such a thing never before, as either backup or
> restore fail, or they do not fail but there is no more validation problem
> immediately afterwards. Well, not so in this story.)
Is it reproducible ? I.e. if you restore same backup few times it have
missed
entries every time ? What if you restore same backup at the another machine ?
>> 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 :-(
>
> It is unfortunately out of the question that we make these DBs available.
> I know that this would be great help, but am unable to change it. On the
> other hand, we would be more than willing to use any beta, gamma :) or
> possibly special test builds for testing this, in order to help Vlad.
It is too early to discuss special builds or to ask you to provide copy of
database.
Regards,
Vlad
------------------------------------------------------------------------------
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
