5 Checklist for Deploying Oracle Unified Directory
This chapter contains a checklist for deploying only Oracle Unified Directory.
Table 5-1 Oracle Unified Directory Deployment Checklist
| Requirement | Check when Verified |
|---|---|
|
Identify and verify the latest Oracle Unified Directory patches and updates. For more information, see "Information Center: Overview Oracle Unified Directory (OUD) (Doc ID 1418884.2)" on My Oracle Support. |
|
|
If you are using an Oracle Linux Enterprise 6 64-bit machine, ensure that you have installed the additional i686 packages before running the Oracle Unified Directory installer. For more information, see "Checking the System Requirements for Oracle Unified Directory" in Installing Oracle Unified Directory. |
|
|
Ensure that your system has sufficient RAM memory for JVM heap and database cache. For more information, see "Configuring the JVM, Java, and Database Cache Options for Oracle Unified Directory" in Installing Oracle Unified Directory. |
|
|
Ensure that your system has sufficient disk space to store the generated log files and replication metadata in addition to other data stored in LDAP. Note: The server log files can consume up to 1GB of disk space with default server settings. In replicated environments, the change log database can grow up to 30-40 GB with loads of 1,000mods/sec. For information about setting the log file size, see "Support to Configure the Name of Rotated Log Files Using Local Time Stamp" in Administering Oracle Unified Directory. |
|
|
Ensure that you have tuned the JVM and Oracle Unified Directory to improve scalability and performance. For more information, see "Configuring the JVM, Java, and Database Cache Options for Oracle Unified Directory" in Installing Oracle Unified Directory. |
|
|
On Linux machines, ensure that the maximum file descriptor limit per process is set to For more information, see "Software Requirements" in the Release Notes for Oracle Unified Directory. |
|
|
On Windows machines, verify that the administrator has access rights on the instance path when Oracle Unified Directory is set up to run as a Windows Service. For more information, see "Software Requirements" in the Release Notes for Oracle Unified Directory. |
|
|
Ensure that appropriate database indexes are configured and initialized to handle specific search pattern, especially for attributes defined in custom user schema. |
|
|
Ensure that every existing Oracle Unified Directory server was started at the time new Oracle Unified Directory server(s) were added to the replication topology. |
|
|
Ensure that full network connectivity is enabled between every Oracle Unified Directory Replication Server. Every Oracle Unified Directory Replication server can connect to each other (firewall ports enabled, DNS resolution, and so on). |
|
|
Verify that every replicated Oracle Unified Directory directory server was properly initialized with same data (same generation ID). For more information about generation ID usage, see "Understanding the Oracle Unified Directory Replication Model" in Administering Oracle Unified Directory. |
|
|
When initializing a new server with LDIF import, ensure that the LDIF is not older than the replication purge delay (4 days, by default). For more information about replication purge delay, see "Purging Historical Information" in Administering Oracle Unified Directory. |
|
|
If you plan to use binary copy to initialize servers, or restore servers, or to do both, ensure that database index configuration is consistent across Oracle Unified Directory servers. For more information about indexing, see "Indexing Directory Data" in Administering Oracle Unified Directory. |
|
|
Run the For more information about |
|
|
Examine Oracle Unified Directory error log files, and confirm that no errors are reported. Note: For information about logging, see the section, "Monitoring Oracle Unified Directory and ODSEE Replication Status in Deployments Using Replication Gateways" in Administering Oracle Unified Directory. |
|
|
Examine the Oracle Unified Directory access logs to identify issues, such as insufficient privileges or unindexed searches. In the access logs, search for the strings:
|
|
