dbfilenamenumber This attribute gives the name of the file and provides a sequential integer identifier (starting at 0) for the file. All associated statistics for the file are given this same numerical identifier.

dbfilecachehit This attribute gives the number of times that a search requiring data from this file was performed and that the data were successfully obtained from the cache.

dbfilecachemiss This attribute gives the number of times that a search requiring data from this file was performed and that the data could not be obtained from the cache.

dbfilepagein This attribute gives the number of pages brought to the cache from this file.

dbfilepageout This attribute gives the number of pages for this file written from cache to disk.

3.4.7Database attributes under cn=index, cn=NetscapeRoot, cn=ldbm database, cn=plugins, cn=config and cn=index, cn=UserRoot, cn=ldbm database, cn=plugins, cn=config

In addition to the set of default indexes that are stored under cn=default indexes, cn=config, cn=ldbm database, cn=plugins, cn=config, custom indexes can be created for o=NetscapeRoot, o=UserRoot, and user-defined backend instances; these are stored under cn=index, cn=database_name, cn=ldbm database, cn=plugins, cn=config. Each indexed attribute represents a subentry under the cn=config information tree nodes, as shown in the following diagram:

Figure 3-2 Indexed attribute representing a subentry

For example, the index file for the aci attribute under o=UserRoot appears in the Directory Server as follows:

dn:cn=aci, cn=index, cn=UserRoot, cn=ldbm database, cn=plugins, cn=config objectclass:top

objectclass:nsIndex

cn:aci

nssystemindex:true

nsindextype:pres

These entries share all the indexing attributes listed for the default indexes in “Database attributes under cn=default indexes, cn=config, cn=ldbm database, cn=plugins, cn=config”. For further information about indexes, refer to the "Managing Indexes" chapter in the HP-UX Directory Server administrator guide.

3.4.7.1 nsSubStrBegin

By default, for a search to be indexed, the search string must be at least three characters long, without counting any wildcard characters. For example, the string abc would be an indexed search while ab* would not be. Indexed searches are significantly faster than unindexed searches, so changing the minimum length of the search key is helpful to increase the number of indexed searches.

This substring length can be edited based on the position of any wildcard characters. The nsSubStrBegin attribute sets the required number of characters for an indexed search for the beginning of a search string, before the wildcard. For example:

150 Plug-in implemented server functionality reference