On 07.07.2014 14:11, Nico Kadel-Garcia wrote: > On Mon, Jul 7, 2014 at 7:14 AM, Branko Čibej <br...@wandisco.com> wrote: >> On 07.07.2014 12:48, Nico Kadel-Garcia wrote: >>> On Mon, Jul 7, 2014 at 3:23 AM, Branko Čibej <br...@wandisco.com> wrote: >>>> On 06.07.2014 23:54, Andreas Stieger wrote: >>>> Berkeley DB databases can always be upgraded from older BDB versions with >>>> db_upgrade, if the BDB version on the new server is incompatible with the >>>> one on the old server. Nothing else should really matter. >>>> >>> This is not necessarily reliable. I've encountered at least 4 BDB >>> environments that worked as they were, but for which 'db_upgrade' was >>> impossible. It even paid serious consulting rates while I backported a >>> bunch of CentOS tools to work with an old BDB environment that someone >>> had hand built and not written a usable 'export' function for. >>> >>> I have never found BDB to be stable or reliable enough for production use. >> That's an answer to a different question. :) > Clipping some material: no, it's not a different question. BDB > databases *cannot* always be upgraded with db_upgrade, I thought I was > clear about that.
The question that started this thread was why a BDB database could not be opened. The answer is, because the BDB back-end was not built. We don't even know that the old and new BDB versions are different. -- Brane -- Branko Čibej | Director of Subversion WANdisco // Non-Stop Data e. br...@wandisco.com
