Berkeley DB Library Version Change Log

Changes between and
Changes between and
Changes between and
New Features in 6.0.19
Database or Log File On-Disk Format Changes
Database Environment Changes
Concurrent Data Store Changes
Access Method Changes
API Changes
SQL-specific API Changes
Tcl-specific API Changes
Java-specific API Changes
C#-specific API Changes
Replication Changes
Locking Subsystem Changes
Logging Subsystem Changes
Memory Pool Subsystem Changes
Mutex Subsystem Changes
Transaction Subsystem Changes
Test Suite Changes
Utility Changes
Configuration, Documentation, Sample Apps, Portability and Build Changes
Example Changes
Miscellaneous Bug Fixes
Deprecated Features
Known Bugs

This is the changelog for Berkeley DB 12c Release 1 (library version

Changes between and

  1. The database record format for databases containing BLOBs has changed in Any database from version or earlier that contains BLOBs must be upgraded before it can be opened by this or any later version of Berkeley DB. Databases without BLOBs do not require upgrading.

  2. Correct a problem with DB_LOCKDOWN which would cause an mlock error ENOMEM on some operating systems. [#21379]

  3. Fixed an error which prevented encrypted databases from being upgraded correctly. [#22215]

  4. Fixed a bug where opening a partition database would fail if the range keys did not fit within a single database page. [#22280]

  5. Fixed several build failures for different configurations on QNX. [#22310]

  6. Databases containing BLOBs are now portable between machines of opposite endianness. [#22455]

  7. Fixed a bug that would prevent a client from rejoining the group when it had been deleted from the replication group earlier. [#22460]

  8. Update the db_dump and db_printlog utilities to use a -D option to control the amount of data printed. [#22485]

  9. Old log files will once again be automatically removed in the SQL API. [#22521]

  10. When a removed site rejoins a two-site replication group with DB_REPMGR_CONF_2SITE_STRICT turned off, defer its election so that the rejoining site does not prematurely elect itself master with only its own vote when the other site is already master. [#22683]

  11. DB_ENV->close() now detaches from the environment's mmap and shared memory regions even when a panic error (DB_RUNRECOVERY) has been returned. [#22805]

  12. Fixed a bug the would cause an environment panick when creating in-memory heap databases on certain endian machines. [#22929]

  13. Empty directories in the BLOB directory will now be deleted after executing a non-transaction protected remove operation on a BLOB enabled database. [#22935]

  14. All BLOB files will now be deleted when removing a BLOB enabled database that contains subdatabases. [#22938]

  15. Fixed a bug where a Replication Manager subordinate process could fail its automatic takeover as the replication process because it is unnecessarily waiting for acknowledgements from other sites before the connections to these sites are properly established. [#22998]

  16. Aborting the creation of a BLOB-enabled database will no longer leave various support files in the environment. [#23000]

Changes between and

  1. Updated the PHP API to work with PHP 5.4 and above. [#22594]

Changes between and

  1. Updated LICENSE file to reflect change to AGPL. [#22590]

New Features in 6.0.19

  1. Added an alternate storage format called blobs, which improves the read and update performance of very large data items. Interface available through C, C#, C++ and Java APIs. [#19332]

  2. Added several pragmas to the SQL layer that configure and give information on HA SQL applications, such as the number of sites in the replication group, or configuring election priority of a site. [#20227]

  3. Added a BDBSQL_CONCURRENT_CONNECTIONS flag to the SQL API to allow database locking to be disabled. Useful when there are only readers in the database. [#20928]

  4. When running Replication Manager in multiple processes, if the replication process quits and there is an available subordinate process, the subordinate process automatically takes over as the replication process. [#20969]

  5. Added replication views/partial replication feature. Feature available through C, C#, C++ and Java APIs. [#21062]

  6. DPL enhancements to work with JDK7. [#21101]

  7. Added encryption support for the Android JDBC driver. [#21129]

  8. Applications which use snapshot isolation and long-running transactions will, in many instances, see reduced use of the cache. This leads to improved performance by reducing the need for temporary freezer files. [#21324]

  9. Added mpool stat fields st_mvcc_resued, st_oddfsize_detect and st_oddfsize_resolve to C#. [#21325]

  10. Added support database partitioning in C# APIs. [#21474]

  11. Added a per-thread cache for the locker struct which stores lock identifiers, such as transaction ids or the locker id returned by DB_ENV->lock_id(). This can improve concurrency of programs which use DB_ENV->set_thread_count(). [#21591]

  12. Port utilities to Windows Mobile. [#21636]

  13. Expose 3 new repmgr stat values and a new DB_REPMGR_SITE flag value to C# and Java APIs. [#21687]

  14. Added support for localizing error messages in UTF-8 characters, and added a section about how to build localized library and an ICU example in Programmer's Reference Guide. [#21280]

Database or Log File On-Disk Format Changes

  1. The log file format changed between and

Database Environment Changes

  1. Redundant whitespaces are now ignored in DB_CONFIG lines pertaining to directories. [#20158]

  2. Fixed bugs when attempting to open non-DB files as if they were databases. If encryption was active, an assertion failure would occur. If encryption was not active, the error message "BDB0178 Encrypted database: no encryption flag" would incorrectly imply that a password was required. [#21408]

  3. DB_ENV->open(DB_REGISTER) now detects whether a panic has occurred in the environment. If so it returns DB_RUNRECOVERY. Prior to this, the panic state was not detected, which might have caused a hang. [#22805]

Concurrent Data Store Changes

  1. None

Access Method Changes

  1. Fixed a bug that could allocate a heap data page in a region after the region creation has been undone. [#20939]

  2. Fixed a bug in heap that prevented it from working in mixed-endian configurations. [#21016]

  3. Enhance the search performance for Btree access method when the keys share a common prefix. [#21216]

  4. Fixed bugs with the byte swapping of heap pages. Now heap databases can be moved between little-endian and big-endian architectures. [#21387]

  5. Fix a race condition where a cursor in the process of being cleaned up could be accessed by another thread of control. [#21714]

  6. Duplicating the position of a cursor on a partitioned database will no longer result in a crash. [#22195]

  7. Fixed an assertion error when closing a joined cursor. [#22398]

API Changes

  1. Change the sequence's cachesize and the delta parameter of DB_SEQUENCE->get to be of type u_int32_t instead of int32_t. [#21552]

  2. Fixed a bug with the DB_MPOOLFILE->set_maxsize API. In previous releases the file was allowed to grow one page larger than the configured limit. [#21867]

  3. Change the comparison function in DB->set_bt_compare, DB->set_dup_compare and DB->set_h_compare to accept an extra 'size_t *locp' parameter. [#22235]

SQL-specific API Changes

  1. Added the PRAGMA large_record_opt, which when enabled can improve the read and update performance of very large records. [#19332]

  2. Added support for multi-process access to the database in SQL HA applications. [#21050]

  3. In-memory databases can now be created without passing the flag SQLITE_OPEN_CREATE. [#21456]

  4. Fix a bug in the SQL API where setting the page size to 64 K would cause an error. Also fixed an associated memory leak in SQL online backup. [#21460]

  5. Add bdbsql_log_buffer pragma to allow setting of log buffer size. [#21471]

  6. Upgraded SQLite to version 3.7.13. [#21641]

  7. Fixed a mutex leak with multi-prcess access to the database in SQL HA applications. [#21714]

  8. Fixed a bug that could cause jdbc build to fail on ARM-Linux using gnueabi gcc. [#22123]

  9. Upgraded SQLite to version [#22349]

  10. Upgraded ADO.NET to version [#22405]

Tcl-specific API Changes

  1. Support blob storage APIs in Tcl. [#19332]

Java-specific API Changes

  1. Fixed a bug where EnvironmentConfig.setCreateDir() was not correctly configuring the environment. [#21127]

  2. Fixed a bug where Database.verify() was not correctly configuring the db. [#22401]

  3. Fixed a false error message that could be printed when creating a transaction on a replication client in Java. [#21671]

C#-specific API Changes

  1. Clean up many C# build warnings. [#22285]

  2. Fixed SWIG typemap defintions for C# interface. [#18509]

Replication Changes

  1. Fixed several assertion failures that could result when using failchk and replication. [#19765]

  2. Provide an error when the local site defined during internal initialization is inconsistent with an earlier definition. [#20870]

  3. Fixed a bug where replication clients were incorrectly flushing the log when the DB_TXN_WRITE_NOSYNC flag was specified. [#20964]

  4. Fixed a bug where a valid invocation of the DB_ENV->repmgr_start() method would fail after a previous invocation that supplied an invalid nthreads parameter value. A BDB3640 error was being incorrectly generated. [#21289]

  5. Fixed a bug where the calculation of the number of required master lease grants enforced that a transaction must be present on a strict majority of replication group sites. It is sufficient that a transaction be present on at least half of the replication group sites, which in some cases reduces the number of required lease grants. [#21329]

  6. Fixed a recovery issue on the client where an incorrect checkpoint was being selected causing recovery to go to an incorrect point. [#21342]

  7. Fixed a bug that could result in a crash due to an incorrect re-request on a site that just won an election. [#21344]

  8. Fixed a bug where logs would never get archived if there are 2 sites and various combinations of failures. [#21448]

  9. Fixed a bug where we were not detecting the fact that DB_TXN_SNAPSHOT was being used with an HA client. Clients are by definition read only, so snapshot transactions are not permitted. [#21601]

  10. Fixed a bug where the determination of whether or not a site is peer was incorrectly determined. [#21722]

  11. Fixed a bug where a Replication Manager master could stop functioning after accepting an obsolete group membership site list from another site. [#21804]

  12. Reduce the multiple data streams that can sometimes occur if rerequest times are shorter than the time it takes to switch log files or perform a checkpoint at a client site. [#21843]

  13. Fixed a bug that a site is removed unexpectedly from the replication group when the replication group loses the old master's confirmation of adding the site during a master change. [#21875]

  14. Fixed a bug where a master site could crash when removing a site if the removed site closes its connections before the master completes its final steps of the operation. [#22050]

  15. Fixed a bug where an election never happens after the loss of the master when master leases are in use. [#22120]

Locking Subsystem Changes

  1. Fixed a bug that could cause a trap if a lock timeout occured while opening a database. [#21098]

  2. Fixed a hang which could occur if there were no more space for lockers. [#21774]

  3. Fixed a potential race condition when building the deadlock detection graph which, under rare conditions, might cause a invalid address fault. [#22261]

Logging Subsystem Changes

  1. Fixed a bug that DB_ENV->log_get_config did not work correctly when it was called before DB_ENV->open. [#21359]

Memory Pool Subsystem Changes

  1. Fixed a bug in the DB_ENV->get_cache_max API that caused it to return an incorrect value and a bug in the DB_ENV->set_cachesize API that caused incorrect behavior when changing the size of an existing cache. [#21146]

  2. Fixed a race condition occurring when trying to get information about a file and the file is being extended by the OS. [#21193]

  3. Corrected error messages in several memory pool configuration functions. [#21779]

  4. Fixed several memory leak items identified by Purify runs. [#22283]

Mutex Subsystem Changes

  1. Fixed an undefined symbol error (MUTEX_IS_OWNED) when configuring with --enable-diagnostic --disable-mutexsupport. [#21145]

  2. Fix a bug where we were not properly aligning mutexes in DB_PRIVATE regions when the application configured an alignment. [#21491]

  3. Fix a race condition between DB_ENV->failchk() and the allocation of a mutex. [#21796]

  4. Limit the default mutex spin count to be at most 200, to avoid excessive spinning on systems with hundreds of hyperthreads. [#21463]

Transaction Subsystem Changes

  1. None

Test Suite Changes

  1. Added support for get/set_heapsize. [#21510]

Utility Changes

  1. Fixed a bug where calling DB->set_partition with a key array required users to keep the memory array valid until after the database was opened. [#18350]

  2. Fixed a bug that caused DB_ENV->backup to stop early if DB_BACKUP_FILES was not set and a non-DB file was in the data directory. [#21076]

  3. Fixed a problem with db_hotbackup's -F option, which could cause a segmentation violation. Also replaced an unclear error message. [#21184]

  4. Fixed three problems with db_hotbackup's backup of transaction logs. A hot backup did not use any configured log directory, but would try to open the logs in the environment home. The second fix corrected an error path, in which the memory was freed by the wrong function, possibly causing a guard byte error. The third fix fixed the issue that a wrong message would be displayed when only "-l" was specified. [#21313]

  5. Fixed a spurious "No such file or directory" (ENOENT) error when running db_archive in an environment with an empty queue database. [#21541]

  6. Fixed bugs in compaction of large keys in the upper levels of btrees. [#21569]

  7. Most utilities no longer operate on replication clients which are being automatically initialized. The DB_REP_LOCKOUT error is now returned. [#21593]

  8. Fixed a resource leak in the db->verify() function for btrees. The bug would slow down verification and possibly cause it to run out of memory. [##21917]

  9. Removed a potential hang when compacting databases with many duplicates. [#21975]

  10. Fixed a bug where we were not returning an error when trying to compact a heap database. [#22063]

  11. Fixed a bug in the error handling of db_log_verify which would cause a segmenation violation if there were not enough space to create its temporary databases. [#22187]

Configuration, Documentation, Sample Apps, Portability and Build Changes

  1. Fix an odbc configure issue which was causing ODBC build failure with SQL API. [#21490]

  2. Disabled encryption by default in SQL API on Linux, completed build options for encryption in SQL and SQL JDBC on Linux, Windows and Android, and updated build process for the three platforms in Installation Guide. [#21872]

  3. Use "-xO2" as the default optimization level for the Sun Workshop compiler. [#22057]

  4. Fix an "opcode not supported" error on MIPS platforms whose assembler defaults to the MIPS1 instruction set. [#22065]

  5. Provide a consistent way to turn on/off encryption for db,sql,jdbc libraries on Unix. [#22158]

  6. Added the compile option CONFIG_TEST when using debug mode in the db_csharp Windows project, to be consistent with the db Windows project. [#22300]

Example Changes

  1. Port the C bulk example to C++. [#19541]

Miscellaneous Bug Fixes

  1. Fixed a race condition that could cause a crash if 2 processes opened the same SQL database at the same time. [#21041]

  2. Fixed an assert failure in the btree comparison function which caused memory to be allocated to the wrong thread. [#21232]

  3. Fixed a race condition in the SQL handle cache locking code. [#21265]

  4. Fixed a bug in the SQL code that prevented the table from being created when BDBSQL_FILE_PER_TABLE is defined. [#21417]

  5. Fixed a bug that some fields of the partition key DBTs returned from DB->get_partition_keys may not be initialized. [#21474]

  6. Fixed a bug that prevented a sub-database from being created under the directory identified in DB->set_create_dir. [#21603]

  7. Fixed a bug where dbenv->mp_mtxcount was not being used correctly. [#21768]

  8. Cleaned a few variable initialization problems that were causing failures on 64-bit Windows. [#21850]

  9. Improved the randomness of the 20 byte unique fileid generator on Windows. [#22470]

  10. Fixed a possible assertion failure in the XA Transaction Manager feature. [#22450]

Deprecated Features

  1. Tornado 2.0 is not supported, and VxWorks versions older than 6.9 are not supported. [#21877]

Known Bugs

  1. Prepared transactions may not remove databases. An error EINVAL message will be returned by TXN->prepare() if the transaction removed any databases.

  2. The latest version of the ADO.NET driver uses a new database connection close function that does not clean up the database completely, leaving transactions active. In our build projects that we distribute we added the preprocessor definition INTEROP_LEGACY_CLOSE so the older version will be used. Removing this can cause hangs.

  3. The db_log_verify utility does not currently implement support for the "-D" option. Also, the "-d" option does not work for an environment with multiple databases. For environments with sub-databases, some unexpected warnings will be thrown. [#22136]

  4. Aborting a prepared transaction that removes a database or does operations on a blob cannot undo the operations (although the call to txn->prepare throws an error if a user tries to do that). [#22226]

  5. Using the DB_FAILCHK flag with just the DB_RECOVER flag can cause processes to hang. DB_RECOVER will cause the environment to be rebuilt, and when DB_FAILCHK is specified, it runs fail check as the last step in the open. It is done afer the environment has been rebuilt. There isnt anything for fail check to really do in this case. The hang can occur if a separate process also uses this combination which would mean the environment is rebuilt again and it could conflict with the first process if it is doing the fail check. [#22419]

  6. A rare race condition in the XA transaction manager can return the error XAER_PROTO in a one-phase commit. [#22450]