My Oracle Support Banner

Do we need to restart server to take effect nsslapd-db-transaction-batch-val parameter change? (Doc ID 1633649.1)

Last updated on MARCH 11, 2014

Applies to:

Oracle Directory Server Enterprise Edition - Version 5.2 to [Release 5.0 to 11gR1]
Information in this document applies to any platform.



When we change nsslapd-db-transaction-batch-val parameter by dsconf (with property name db-batched-transaction-count),
"Directory Server must be restarted for changes to take effect" message is shown.
# ./dsconf set-server-prop -p 389 db-batched-transaction-count:5
Enter "cn=Directory Manager" password:
Directory Server must be restarted for changes to take effect.

# ./ldapsearch -D "cn=Directory Manager" -w password -p 389 -b "cn=config,cn=ldbm database,c
n=plugins,cn=config" objectclass=extensibleObject nsslapd-db-transaction-batch-val
version: 1
dn: cn=config,cn=ldbm database,cn=plugins,cn=config
nsslapd-db-transaction-batch-val: 5
dn: cn=default indexes, cn=config,cn=ldbm database,cn=plugins,cn=config
We can change this parameter directly by ldapmodify too.

But even we do not restart the server after changing nsslapd-db-transaction-batch-val value, the performance seems improved.

manual says as follows:
This attribute can be dynamically modified using ldapmodify.

To take effect the parameter change, do we really need to restart the server?
Or dsconf message is wrong and we don't need to restart the server with either case, dsconf or ldapmodify?


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

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