Monday Jun 27, 2016

Oracle Berkeley DB Java Edition 7.0 Announced

Oracle Berkeley DB Java Edition 7.0 is now available for download.

Download Page – Click Here

Documentation Page – Click Here

Oracle Berkeley DB Java Edition Version 7.0 – New Feature

· Time-To-Live – efficient aging out of “expired” data – This is a common IoT requirement.

Berkeley DB JE continues to enable the most powerful embedded database solutions

· Pure Java library

· Handle TBs of data with a small, lightweight, embedded library

· Flexible, transactional data management engine

· Runs on a variety of operating systems and platforms.

· Over 50 open source software projects embed BDB -- check them out on Wikipedia

· Various options for APIs

· Industrial quality and battle tested

Supporting Assets and Resources:

Collateral and sales assets continue to be updated.

· Oracle Berkeley DB Web Site

· Oracle Berkeley DB blog

· Oracle Berkeley DB Java Edition Datasheet

· Oracle Berkeley DB Family Datasheet

LinkedIn Group –

Twitter @berkeleydb

Community Berkeley DB –

Community for Berkeley DB Java Edition -

Blogs -

Tuesday May 31, 2016

Update for Oracle Berkeley DB - Version 6.1.29

Oracle is pleased to announce an update to Berkeley DB (BDB), version 6.1.29.  We want to make sure that some important features that are in our latest release (6.2.23) are available to those of you who continue to use the 6.1 release.

The highlights include:

  • A new utility db_convert which will convert a database to the endianness of the machine it is running on.
  • Encryption can be enabled when Binary Large Object (BLOB)  files are stored external to the database.
  • An improved vote comparison routine used to select a new master in HA.

Please go to :    to download this release, 6.1.29.

Check out the change log for details on all the changes in this 6.1.29 update release.  Click Here.

Friday Apr 22, 2016

Oracle Open World 2016 - Call for Proposals

The call for proposals for Oracle Open World 2016 is open.  Please submit your proposals by May 9, 2016.  The proposal web site is:

 Submit if you have an interesting use of Oracle Berkeley Database to talk about. 

Monday Apr 18, 2016

Oracle Berkeley Database (BDB) 6.2 Announced

Oracle Berkeley Database Version 6.2 ( is now available for download.

Download Page – Click Here

Documentation Page – Click Here

Oracle Berkeley Database Version 6.2 – New Features

· Slices – provides significantly better scalability on large SMP machines as compared to the previous release.

· Write Forwarding – No longer are application writes restricted to the Master node when this feature is enabled.  Simple write operations can now be performed on the replica and BDB-HA will forward the writes to the Master automatically.

· BDB as a Stand-Alone Server Gives user an out-of-the-box solution to a key-value database in a client-server architecture.

· SQL Performance Enhancements – Index-based SQL query performance has been improved by as much as 40% out of the box when compared to BDB 6.1.

· Authentication – User authentication has been added to the BDB SQL API.  The database can now be set up to authenticate users prior to them accessing data in the database.  The new authentication capability, coupled with existing encryption, can be used to create secure, high performance embedded database applications.

Berkeley DB continues to enable the most powerful embedded database solutions

· Handle TBs of data with a 1MB library

· Flexible, lightweight, transactional data management engine

· Runs on a wide variety of operating systems and platforms ranging from low power ARM devices to clusters of high-end servers

· Over 50 open source software projects embed BDB -- check them out on Wikipedia

· Completely customizable, with choice of 5 different access methods

· Industrial quality and battle tested

Supporting Assets and Resources

Collateral and sales assets continue to be updated.

· Oracle BDB Web Site

· Oracle BDB Blog web site – continue to check for new blogs

· Oracle BDB Database Product Family Datasheet

· Oracle BDB Database Datasheet

LinkedIn Group -

Twitter berkeleydb

What others are saying:

Open source Fedora package maintainer, Lubomir Rintel, says "Berkeley DB has quietly served behind the scenes as the database for the RPM Package Manager.   It has proven itself time and time again as a robust and efficient storage engine.   It stores the meta information of the installed rpms.  Under heavy workloads, BDB proves itself reliable. Countless people that use popular Linux distributions have used BDB through RPM and never knew it.  With this new release,   BDB continues its tradition of being a solid storage engine"

Oracle Tape Product Manager, Dan Deppen, says "Berkeley DB is integral to  Oracle StorageTek Storage Archive Manager (SAM-QFS).  We have been embedding Berkeley DB in our product for over a decade and it is vital to our disk archiving feature which is used to send files to remote data centers to enable disaster recovery.  Performance and scalability are critical because SAM-QFS supports some of the largest archive customers in the world.   HPC sites, research centers, national libraries and other customers requiring massive scalability and high reliability depend on SAM-QFS and Berkeley DB to maintain availability of their critical data."

Questions & Help

External Email Alias

Thursday Jun 12, 2014

Data management in unexpected places

Data management in unexpected places

When you think of network switches, routers, firewall appliances, etc., it may not be obvious that at the heart of these kinds of solutions is an engine that can manage huge amounts of data at very high throughput with low latencies and high availability.

Consider a network router that is processing tens (or hundreds) of thousands of network packets per second. So what really happens inside a router? Packets are streaming in at the rate of tens of thousands per second. Each packet has multiple attributes, for example, a destination, associated SLAs etc. For each packet, the router has to determine the address of the next “hop” to the destination; it has to determine how to prioritize this packet. If it’s a high priority packet, then it has to be sent on its way before lower priority packets. As a consequence of prioritizing high priority packets, lower priority data packets may need to be temporarily stored (held back), but addressed fairly. If there are security or privacy requirements associated with the data packet, those have to be enforced. You probably need to keep track of statistics related to the packets processed (someone’s sure to ask). You have to do all this (and more) while preserving high availability i.e. if one of the processors in the router goes down, you have to have a way to continue processing without interruption (the customer won’t be happy with a “choppy” VoIP conversation, right?). And all this has to be achieved without ANY intervention from a human operator – the router is most likely to be in a remote location – it must JUST CONTINUE TO WORK CORRECTLY, even when bad things happen.

How is this implemented? As soon as a packet arrives, it is interpreted by the receiving software. The software decodes the packet headers in order to determine the destination, kind of packet (e.g. voice vs. data), SLAs associated with the “owner” of the packet etc. It looks up the internal database of “rules” of how to process this packet and handles the packet accordingly. The software might choose to hold on to the packet safely for some period of time, if it’s a low priority packet.

Ah – this sounds very much like a database problem. For each packet, you have to minimally

· Look up the most efficient next “hop” towards the destination. The “most efficient” next hop can change, depending on latency, availability etc.

· Look up the SLA and determine the priority of this packet (e.g. voice calls get priority over data ftp)

· Look up security information associated with this data packet. It may be necessary to retrieve the context for this network packet since a network packet is a small “slice” of a session. The context for the “header” packet needs to be stored in the router, in order to make this work.

· If the priority of the packet is low, then “store” the packet temporarily in the router until it is time to forward the packet to the next hop.

· Update various statistics about the packet.

In most cases, you have to do all this in the context of a single transaction. For example, you want to look up the forwarding address and perform the “send” in a single transaction so that the forwarding address doesn’t change while you’re sending the packet. So, how do you do all this?

Berkeley DB is a proven, reliable, high performance, highly available embeddable database, designed for exactly these kinds of usage scenarios. Berkeley DB is a robust, reliable, proven solution that is currently being used in these scenarios.

First and foremost, Berkeley DB (or BDB for short) is very very fast. It can process tens or hundreds of thousands of transactions per second. It can be used as a pure in-memory database, or as a disk-persistent database. BDB provides high availability – if one board in the router fails, the system can automatically failover to another board – no manual intervention required. BDB is self-administering – there’s no need for manual intervention in order to maintain a BDB application. No need to send a technician to a remote site in the middle of nowhere on a freezing winter day to perform maintenance operations.

BDB is used in over 200 million deployments worldwide for the past two decades for mission-critical applications such as the one described here. You have a choice of spending valuable resources to implement similar functionality, or, you could simply embed BDB in your application and off you go! I know what I’d do – choose BDB, so I can focus on my business problem. What will you do?

Wednesday Jun 22, 2011

New Release of Oracle Berkeley DB

We are pleased to announce that a new release of Oracle Berkeley DB, version, is available today.

Our latest release includes yet more value added features for SQLite users, as well as several performance enhancements and new customer-requested features to the key-value pair API.  We continue to provide technology leadership, features and performance for SQLite applications.  This release introduces additional features that are not available in native SQLite, and adds functionality allowing customers to create richer, more scalable, more concurrent applications using the Berkeley DB SQL API.

This release is compelling to Oracle’s customers and partners because it:

  • delivers a complete, embeddable SQL92 database
  • as a library under 1MB size
  • drop-in API compatible with SQLite version 3
  • no-oversight, zero-touch database administration
  • industrial quality, battle tested Berkeley DB B-TREE for concurrent transactional data storage

New Features Include:

  • MVCC support for even higher concurrency
  • direct SQL support for HA/replication
  • transactionally protected Sequence number generation functions
    • lower memory requirements, shared memory regions and faster/smaller memory on startup
  • easier B-TREE page size configuration with new ''db_tuner" utility

New Key-Value API Features Include:

  • HEAP access method for constrained disk-space applications (key-value API)
  • faster QUEUE access method operations for highly concurrent applications -- up 2-3X faster! (key-value API)
  • new X/open compliant XA resource manager, easily integrated with Oracle Tuxedo (key-value API)
    • additional HA/replication management and communication options (key-value API)

and a lot more!

BDB is hands-down the best edge, mobile, and embedded database available to developers.

Downloads available today on the Berkeley DB download page

Product Documentation


Information about Berkeley DB products directly from the people who build them.


« July 2016