I had the same problem, and running db4.6_recover as described fixed it.
For the benefit of others with this problem, db4.6_recover is in the db4.6-util package.
-- Paul Cassella -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
