Undefined attribute in ibmslapd.conf

Resolving The Problem

Check the ibmslapd.log file for an indication of the error. For example the ibmslapd.log file might have an entry similar to this:

11/03/05 11:58:04 GLPCOM024I The extended Operation plugin is successfully loaded from libloga.a.
11/03/05 11:58:04 GLPCOM013E Attribute ibm-slapdDbPw not found in schema.
11/03/05 11:58:04 GLPSRV040E Error encountered. Server starting in configuration
only mode.

This means that the attribute, ibm-slapdDbPw, is not defined to the server in
the schema files. The solution to this issue is to remove the undefined attribute (ibm-slapdDbPw in this example) and value from the ibmslapd.conf file and then restart the server. In some cases, this is the result of attempting to add an attribute that is defined manually, and typing the wrong name. For example, for the attribute in our example above, the attribute that was meant was probably ibm-slapdDbUserPW.

Save a copy of the ibmslapd.conf file before making any changes.

To check if an attribute is valid, the simplest way to check is to simply search through the schema files for the attribute. For example, if my instance was called ldapdb2, and I'd created a default instance called ldapdb2 on AIX, I could do the following:

cd /home/ldapdb2/idsslapd-ldapdb2/etc
grep -i someAttribute V3.*

The V3.* files (and any other custom schema files included) include all attributes valid for the server.