My Oracle Support Banner

ODSEE - How to Configure and Monitor the 'db-locks' Configuration (Doc ID 2789203.1)

Last updated on JULY 08, 2021

Applies to:

Oracle Directory Server Enterprise Edition - Version 5.1 and later
Information in this document applies to any platform.

Goal

The db-configured-locks attribute is the monitoring attribute for the db-locks configuration.

The db-configured-locks monitoring attribute is in the entry -
cn=database, cn=monitor, cn=ldbm database, cn=plugins, cn=config

The db-locks configuration attribute is by default 20k, and is in stored in the entry -
cn=config,cn=ldbm database,cn=plugins,cn=config

Reference: nsslapd-db-locks man page

The default configuration of 20k should be enough, but when this error is logged (in the ODSEE errors log) -

libdb: Lock table is out of available lock entries

where operations can fail with "err=1" in the access log, testing should be done in a non-Production environment to incrementally increase the db-locks configuration.

This KM doc goes over how to configure db-locks, verify the configuration of db-locks using db-configured-locks, and use db-max-locks to verify the error.

According to the dse.ldif man page -

nsslapd-db-max-locks
Maximum number of locks used by the database since the last startup.

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.