Hi,

I am trying to upgrade a database from 4.2. to 4.4.

I shut down my application.
I run 4.2 db_recover:

$ db_recover -h db
db_recover: Finding last valid log LSN: file: 1 offset 109598
db_recover: Recovery starting from [1][108882]
db_recover: Recovery complete at Mon Mar 20 10:01:50 2006
db_recover: Maximum transaction ID 80000003 Recovery checkpoint
[1][109598]

I run 4.4 db_checkpoint (4.2 db_checkpoint fails because no environment
exists):

$ /network/bin/db_checkpoint -1 -h db
db_checkpoint: Skipping log file db/logs/log.0000000001: historic log
version 8
Finding last valid log LSN: file: 2 offset 0

I restart the app:

$ Schedule
Finding last valid log LSN: file: 2 offset 120
[ Berkeley DB: DbEnv "db": Skipping log file db/logs/log.0000000001:
historic log version 8 ]
[ Berkeley DB: DbEnv "db": Skipping log file db/logs/log.0000000001:
historic log version 8 ]

Seems like something is wrong with the historic log file. The old log
file never got deleted. Is it something that I need to do?

There are a few notes in this group about running your application
without RECOVER as a flag when you open your environment due to a bug
in db_checkpoint. Is this all that needs to be done to make things
correct? Is the db_checkpoint failure still a problem?

Any help appreciated,

-- Andrew Bell

Andrew,

Unfortunately the code in 4.2 db_checkpoint did not work if you did not
already have an environment created. A checkpoint is only needed if
your application runs recovery when it starts as it forces a new
version log file to be created. The log file is not deleted automaticly
since you may need it for archival purposes you can just remove it.
The message is just a warning.

Michael Ubell
Sleepycat Software.

This seems to work if I follow the procedure and use the 4.2 db_recover
and the 4.4 db_checkpoint.

Thanks for the info.