Avoid Uninstalling Edirectory; Avoid Renaming Trees And Containers; Default Static Cache Limit Might Be Inadequate; Edirectory Fails To Start Automatically After A Command Prompt Install - Novell OPEN ENTERPRISE SERVER 2 SP2 - PLANING AND IMPLEMENTATION GUIDE 11-10-2009 Implementation Manual

Section 6.6.5, "One Instance Only," on page 66
Section 6.6.6, "Special Characters in Usernames and Passwords," on page 66

6.6.1 Avoid Uninstalling eDirectory

OES services are tightly integrated with eDirectory and do not function without it.
Although the eDirectory 8.8 documentation describes how to remove and reinstall eDirectory, the
processes described do not cleanly decouple OES services, nor do they restore service connections.
As a result, not only does uninstalling eDirectory break OES services, reinstalling eDirectory does
not restore them.
If you have an issue that you believe can ony be resolved by uninstalling eDirectory, make sure you
consult with Novell Technical Services before you attempt to do so.

6.6.2 Avoid Renaming Trees and Containers

The configuration files for many OES services point to configuration data stored within eDirectory.
Although eDirectory tracks all changes internally, OES services do not. Therefore, if you rename
your eDirectory tree or one of the containers below [Root], you should expect that one or more of
your OES services will break.
If you need to rename a container or tree, make sure that you
1. Identify all of the configuration files for your OES services.
2. Assess whether the changes that you are planning impact any of your service configurations.
3. Understand and articulate the changes that are required to restore your services after renaming.
There are no automated tools in OES for resolving the configuration errors and other problems that
are caused by renaming a tree or its containers.

6.6.3 Default Static Cache Limit Might Be Inadequate

The eDirectory install in OES 2 SP2 sets a default static cache of 64 MB if an
not present in the directory.
dib
To improve performance, you can adjust the cache parameter in the
to meet your eDirectory performance requirements, depending on the database size and available
system RAM. We recommend setting the cache to 200 MB on a 2 GB RAM system and 512 MB on
4 GB RAM system.
6.6.4 eDirectory Fails to Start Automatically After a Command
Prompt Install
Although it is somewhat rare, if you install and configure eDirectory as an OES component at the
command prompt rather than through YaST, eDirectory might fail to start. If this happens, enter the
following command at the command prompt:
chkconfig -a ndsd
_ndsdb.ini
file after the install
_ndsdb.ini
Caveats for Implementing OES 2 Services
file is
65