Ldap-Preventing "Bad Xml" Errors; Lum Cache Refresh No Longer Persistent; Management - Novell OPEN ENTERPRISE SERVER - PLANNING AND IMPLEMENTATION GUIDE 12-2010 Implementation Manual

6.10 LDAP—Preventing "Bad XML" Errors
If you are using Novell eDirectory 8.7.3x, time outs are possible when you search from iManager
for eDirectory objects, such as NCP Server objects, Volume objects, and Cluster objects. This is
because the Object Class attribute is not indexed by default. The LDAP sub-tree search can take
over 30 seconds, which causes the query to time out. For example, a Cluster objects search from the
Cluster Options page returns the error:
Bad XML found during parsing when accessing cluster options
We recommend that you create a value index on the objects' Object Class attribute. (Object Class is
considered an attribute for indexing purposes.) This helps to reduce the time needed for the subtree
search from over 30 seconds to 10 to 50 milliseconds. For instructions, see
the Novell eDirectory 8.8 Administration
Building indexes speeds up the subtree search, even if some partitions being searched do not contain
these types of objects. For example, searching for a Cluster object in a context that contains only
users is not expected to return results; however, the Object Class search is still performed, and
benefits from having an index present.
The subtree search performance issue is resolved in the eDirectory 8.8.x release with the addition of
the AncestorID feature.

6.11 LUM Cache Refresh No Longer Persistent

In reponse to customer requests for improved LDAP performance, persistent searching for new
Linux-enabled users and groups has been disabled in OES 2 SP3. This means that when a user or
group is enabled for Linux access, it is not immediately listed in some of the interfaces, such as the
GUI file browser.
For most installations this is not an issue. However, persistent searching can be turned on by editing
the
/etc/nam.conf
Alternatively, you can shorten the LUM cache refresh period (default is 8 hours). You can adjust the
refresh period by editing the
nam.conf
You can also refresh the cache immediately by using the
For more information, see
Administration

6.12 Management


Section 6.12.1, "iManager RBS Configuration with OES 2," on page 67

Section 6.12.2, "Storage Error in iManager When Accessing a Virtual Server," on page 67

Section 6.12.3, "Truncated DOS-Compatible Short Filenames Are Not Supported at a Terminal
Prompt," on page 67
66 OES 2 SP3: Planning and Implementation Guide
file and changing the
persistent-cache-refresh-period
file and restarting LUM using the
"What's New" in the
Guide.
Guide.
parameter from
persistent-search
command.
rcnamcd restart
namconfig cache_refresh
OES 2 SP3: Novell Linux User Management
"Creating an Index" in
to .
no yes
parameter in the
/etc/
command.