×

IDMWORKS Blog

How to Configure the Change Log for IBM Directory Server


The following contains installation and configuration steps that are considered maintenance mode and require down time or degraded mode of productions servers. The change log must be created prior to making any changes to the LDAP data. Add the change log after the data has been bulk loaded and after the replication agreements have been installed.

***NOTE: As with all Tips and Tricks we provide on the IDMWorks blog, use the following AT YOUR OWN RISK.  We do not guarantee this will work in your environment and make no warranties***

The following contains installation and configuration steps that are considered maintenance mode and require down time or degraded mode of productions servers.  The change log must be created prior to making any changes to the LDAP data.  Add the change log after the data has been bulk loaded and after the replication agreements have been installed.

An ITDS server must be stopped prior to adding a change log.

1. Log onto the new ITDS  server that will host the change log and switch to the root user.

$ su – root

<Enter the password>

2. Edit your path to contain the ITDS bin and sbin directories.

# export PATH=$PATH:/opt/IBM/ldap/V6.1/bin:/opt/IBM/ldap/V6.1/sbin

3. Set the umask.

# umask 022

4. Stop the ITDS LDAP server in order to install the change log on this server

NOTE: The “-I” is a capital “i”.

# idsslapd -I ldapdb2 -k

The output should look similar to the following:

GLPSRV121I Stopped directory server instance: ‘ldapdb2’.

5. Create the change log for the ITDS instance.

NOTE: The “-I” is a capital “i”.

# idscfgchglg -I ldapdb2

The output should look similar to the following:

You have chosen to perform the following actions:

GLPCCH012I Change log will be configured.

GLPCCH013I Change log maximum entries will be set to ‘1000000’.

GLPCCH014I Change log maximum age limit will be set to ‘0’ days ‘0’ hours.

Do you want to….

(1) Continue with the above actions, or

(2) Exit without making any changes:

6. Enter “1” and press Enter.

The output will be similar to the following:

GLPCCH026I Adding change log to directory server instance: ‘ldapdb2’.

GLPCTL017I Cataloging database instance node: ‘ldapdb2’.

GLPCTL018I Cataloged database instance node: ‘ldapdb2’.

GLPCTL008I Starting database manager for database instance: ‘ldapdb2’.

GLPCTL009I Started database manager for database instance: ‘ldapdb2’.

GLPCTL026I Creating database: ‘ldapclog’.

GLPCTL027I Created database: ‘ldapclog’.

GLPCTL034I Updating the database: ‘ldapclog’

GLPCTL035I Updated the database: ‘ldapclog’

GLPCCH005I Configuring change log database ‘ldapclog’ for directory server instance:

ldapdb2′.

GLPCCH006I Configured change log database ‘ldapclog’ for directory server instance:

‘ldapdb2’.

GLPCTL043I Adding local loop back to change log database: ‘ldapclog’.

GLPCTL044I Added local loop back to change log database: ‘ldapclog’.

GLPCTL011I Stopping database manager for the database instance: ‘ldapdb2’.

GLPCTL012I Stopped database manager for the database instance: ‘ldapdb2’.

GLPCTL008I Starting database manager for database instance: ‘ldapdb2’.

GLPCTL009I Started database manager for database instance: ‘ldapdb2’.

GLPCCH003I Added change log to directory server instance: ‘ldapdb2’.

7. Start the ITDS server.

NOTE: The “-I” is a capital “i”.   

# idsslapd -I ldapdb2

The output will be similar to the following:

GLPSRV041I Server starting.

GLPCOM024I The extended Operation plugin is successfully loaded from libevent.so.

GLPCOM024I The extended Operation plugin is successfully loaded from libtranext.so.

. . .

GLPSRV009I IBM Tivoli Directory (SSL), 6.0      Server started.

8. Verify that the LDAP server is running.

# idsldapsearch -p 389 -D cn=root -w <password> -s base objectclass=*

The beginning and end of the output should look like the following:

namingcontexts=CN=SCHEMA . . .

ibm-slapdisconfigurationmode=FALSE

Important! Verify that the last line, ibm-slapdisconfigurationmode, has the value of FALSE. If it is TRUE, then the server is in configuration mode because there is a problem.  Fix any problems and restart the server before going to the next step.

Questions, comments or concerns?  Feel free to reach out to us at IDMWorks.

Questions, comments or concerns? Feel free to reach out to us below, or email us at IDMWORKS to learn more about how you can protect your organization and customers.

Leave a Reply

Your email address will not be published. Required fields are marked *