Description of problem:

customer's system are often updated for years, instead of adding fresh and clean and up to date RHEL-8 and RHEL-7 systems into an IdM topology.

this often result in some parameters that are no long properly tuned as databases and usage grow overtime.

one example is the IPA LDAP server with the configuration parameter called nsslapd-db-locks.

there has been a customer case and situation with an updated system to RHEL-7.8, but carrying an older setting.

dn: cn=config,cn=ldbm database,cn=plugins,cn=config
nsslapd-db-locks: 10000

the newer default had been 50K in RHEL-8.2 and RHEL-7.8


so the file
/usr/share/ipa/updates/10-config.update

could re-tune

dn: cn=config,cn=ldbm database,cn=plugins,cn=config
nsslapd-db-locks: 50000


but on the other hand, this may overwrite those deployments that had been manually tuned with higher values like 100 or 200K dblocks


the symptom is typically an IPA LDAP error with this string:
id2entry - db error 12 (Cannot allocate memory) 


Version-Release number of selected component (if applicable):
RHEL-8
RHEL-7
389-ds-base


How reproducible:
N/A , this is about old configurations carried overtime by RHEL IdM application successive updates

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: