OVDB upgrade question.

[Heath Kehoe]

>
>Going to upgrade from a late July to release to the 10-02 release.  The
>db_upgrade procedure mentions using the -s option to handle duplicate
>keys.  I don't believe there should be duplicate keys in the overview
>data, so this should be a non-issue, but I'm not sure if it still makes a
>difference on the on-disk structures, per the man page.
>
>So if anybody has done this, which option did you use?
>

The db_upgrade command won't do what you need here.  Especially if you
are not changing your BerkeleyDB version.  The changes from the original
ovdb to the one in the current current snapshots require some rearranging
of the data stored in the database, which is handled by the ovdb_init
tool.  db_upgrade will only upgrade the low-level file format of the
databases (which you need to do when upgrading BerkeleyDB from 2.x to
3.x or from 3.0.x to 3.1.x).

After building the new INN, run 'ovdb_init -u' as the news user to perform
any necessary upgrades.  I have docs for this on
http://www.avalon.net/~hakehoe/inn/ovdb2/ .

As for duplicate keys, ovdb does not use the duplicate keys feature of
BerkeleyDB, so the -s option for db_upgrade is not relevant.  But you
can just use 'ovdb_init -u' to perform upgrades, as it does what
db_upgrade does, in addition to the ovdb-specific changes.

-heath