We have discovered a problem where applications that specify Berkeley DB's encryption or data checksum features on Queue databases with extent files, the database data will not be protected. This is obviously a security problem, and we encourage you to upgrade these applications to the 4.2 release as soon as possible.

The Queue databases must be dumped and reloaded in order to fix this problem. First build the Berkeley DB 4.2 release, then use your previous release to dump the database, and the 4.2 release to reload the database. For example:

db-4.1.25/db_dump -P password -k database | db-4.2.xx/db_load -P password new_database

Note this is only necessary for Queue access method databases, where extent files were configured along with either encryption or checksums.