I am doing some testing for an upgrade from db-4.3.27 provided on Fedora
Core 4 to db-4.4.20.NC.

I have several existing file-based databases that in turn contain several
logical databases. I have recompiled/linked the module that interfaces
w/ db_cxx.so.N smoothly.

Here is the hitch, (after removing the environment w/ db_recover):

Using transactions i fail to open the db and receive a Db:pen: Invalid
argument. If i turn transactions off, all works fine.

I then db_dump'd w/ the 4.3 utility, and db_load'd w/ the 4.4 utility, and
all worked perfectly whether using or not using transactions w/ the same
flags as used above.

Finally, i did a db_stat to inspect a logical db inside an existing(un
dump'd/load'd) db and i receive this:

db_stat -d sp500.bdb -s ts_data
db_stat: file sp500.bdb (meta pgno = 6) has LSN [5][171021].
db_stat: end of log is [1][28]
db_stat: ts_data: unexpected file type or format
db_stat: DB->open: sp500.bdb: Invalid argument

Running the same command on the dump'd and load' db gives:

db_stat -d sp500-new.bdb -s ts_data
Wed Feb 8 12:05:23 2006 Local time
53162 Btree magic number
9 Btree version number
Little-endian Byte order
duplicates, multiple-databases Flags
2 Minimum keys per-page
32768 Underlying database page size
2 Number of levels in the tree
2540 Number of unique keys in the tree
12990 Number of data items in the tree
1 Number of tree internal pages
31694 Number of bytes free in tree internal pages (3% ff)
50 Number of tree leaf pages
370768 Number of bytes free in tree leaf pages (77% ff)
2319 Number of tree duplicate pages
30M Number of bytes free in tree duplicate pages (61% ff)
0 Number of tree overflow pages
0 Number of bytes free in tree overflow pages (0% ff)
0 Number of empty pages
0 Number of pages on the free list

The release notes say nothing has changed in the db format...can anyone
point out the stupid-user problem?

thanks,

-tom

Hmm... the release notes do say that the log format changed.

http://www.sleepycat.com/docs/ref/upgrade.4.4/disk.html

Did you follow the full steps below (particularly, forcing a checkpoint
before restarting the application?)

http://www.sleepycat.com/docs/ref/upgrade/process.html

If the application has a Berkeley DB transactional environment, and
the log files need upgrading but the databases do not, the application
may be installed in the field using the following steps:

Shut down the old version of the application.
Run recovery on the database environment using the DB_ENV->open method
or the db_recover utility.
Remove any Berkeley DB environment using the DB_ENV->remove method or
an appropriate system utility.
Archive the database environment for catastrophic recovery. See
Archival procedures for more information.
Recompile and install the new version of the application.
Force a checkpoint using the DB_ENV->txn_checkpoint method or the
db_checkpoint utility.
Restart the application.

regards,

Chris