System information

Known Issues and Limitations
Part Number 817-5216 Page 27 of 32
Searches based on a substring filter for the telephonenumber attribute fail if the filter contains a blank
space directly after the ‘*’ substring (#4866642)
db2ldif produces unexpected errors when sub-suffixes are given in the -s option (#4889077)
When indexes are configured with nsMatchingRule, db2ldif and ldif2db issue an “unknown index rule”
warning which means that the index created does not include the matching rule (#4995127)
Workaround
Use
db2ldif.pl
and
ldif2db.pl
instead of
db2ldif
and
ldif2db
as they do not issue “unknown
index rule” warnings and create the index with the matching rule.
Unless an output file is defined as an absolute path, the db2ldif command (and the db2ldif option of the
directoryserver command) creates the output file under /installdir/bin/slapd/server/sparcv9 as opposed
to under /ServerRoot/slapd-serverID as stated in the Directory Server Administration Guide (#5029598)
Directory Server Plug-ins
If two entries with duplicate uids are added to Directory Server simultaneously, then UID uniqueness is
not enforced (#4987124)
If the plug-in configuration entry attribute values in the dse.ldif end with extra blank spaces, Directory
Server will either fail to start or behave in unexpected ways (#4986088)
When the Pass-Through Authentication plug-in (PTA plug-in) detects that a suffix configured for
pass-through authentication is local to the machine, the plug-in is not automatically disabled
(#4938821)
If you have two Directory Server instances DS1 and DS2 with your Configuration Directory Server
installed on DS1, and you subsequently replicate the
o=NetscapeRoot
configuration information to
DS2, as opposed to automatically disabling the PTA plug-in will continue to point to DS1for any
o=NetscapeRoot
relevant searches despite the fact that the information is now local.
When running a search on a non-existent base DN, the post-operation plug-in function is not called
(#5032637)
Product documentation states that post-operation plug-ins are called after a client request has been
processed whether or not the operation completes successfully. However when performing a
search on an non-existent base DN, this does not happen.