Skip to content

[package list]

DB

License information

Oracle employs a dual licensing model that offers customers a choice of either our open source license or a commercial license. Our open source license is OSI-certified and permits use of Berkeley DB in open source projects or in applications that are not distributed to third parties.

Our commercial license permits closed-source distribution of an application to third parties and provides business assurance. Please address your request for commercial licensing to berkeleydb-info_us@oracle.com.

The full licensing information can be found on the Oracle Berkeley DB licensing page.

User documentation

What is DB?

Oracle Berkeley DB is a family of embedded key-value database libraries providing scalable high-performance data management services to applications. The Berkeley DB products use simple function-call APIs for data access and management.

Berkeley DB enables the development of custom data management solutions, without the overhead traditionally associated with such custom projects. Berkeley DB provides a collection of well-proven building-block technologies that can be configured to address any application need from the hand-held device to the data center, from a local storage solution to a world-wide distributed one, from kilobytes to petabytes.

Pre-installed modules (and EasyConfigs)

To access module help and find out for which stacks and partitions the module is installed, use module spider DB/<version>.

EasyConfig:

Technical documentation

EasyBuild

Version 18.1.40 from CPE 21.06 onwards

  • The EasyConfig file is a direct port of the EasyBuilders one with some documentation updates.

  • For LUMI/22.12: Switch to the improved way of specifying checksums.

Archived EasyConfigs

The EasyConfigs below are additonal easyconfigs that are not directly available on the system for installation. Users are advised to use the newer ones and these archived ones are unsupported. They are still provided as a source of information should you need this, e.g., to understand the configuration that was used for earlier work on the system.