Replication or Oracle Directory Integration Platform Replication Server Configuration

Oracle Internet Directory Performance Tuning 22-11 You can modify orclnwrwtimeout by using Fusion Middleware Control or the command line. See Section 22.12.1, Modifying Instance-Specific Attributes by Using Fusion Middleware Control.

22.6 Specific Use Cases

This section describes some specific use cases that require additional tuning, in addition to Section 22.3, Basic Tuning Considerations

22.6.1 Bulk Load Operation

If you are planning a large bulkload operation, make the following changes: ■ Set the database initialization parameter pga_aggregate_target to 1-4GB for the duration of the operation, if sufficient RAM is available. ■ Increase the database temporary tablespace before loading a large number entries. You need about 1G of temporary tablespace per million entries being loaded. You can free up the tablespace after the operation.

22.6.2 Bulk Delete Operation

If you are planning a large bulkdelete operation, perform the following tasks: ■ Ensure that the database initialization parameter sga_target are tuned as described in Section 22.3.1, Database Parameters. ■ Set the database initialization parameter log_buffer to 10M. This can provide additional performance benefit. ■ Ensure that you have at least three database redo log files with at least 100MB. ■ Ensure that the undo tablespace is at least 1 GB in total size. ■ Follow the recommendations about redo logs and undo tablespace in the next section, Section 22.6.3, High LDAP Write Operations Load.

22.6.3 High LDAP Write Operations Load

If you have a high LDAP write operations load, or if you perform many bulkdelete operations, consider tuning the following values: ■ Increase the size or number of the database redo log files so that the total size is 1000-1500 MB. Other considerations affect the total size of redo logs. ■ Depending on how the disks are configured, it might be beneficial to isolate the redo log files to a dedicated set of disks. ■ Increase the undo tablespace size by adding data files to this tablespace. For most deployments, 2-4 GB should suffice. ■ Do not use the Oracle Internet Directory server entry cache. See Section 22.4.6, Server Entry Cache. ■ If neither Oracle Internet Directory replication nor DIP is deployed, disable change log generation. See Section 22.4.1, Replication or Oracle Directory Integration Platform. Table 22–6 summarizes the redo log and undo tablespace recommendations provided in this section. 22-12 Oracle Fusion Middleware Performance and Tuning Guide

22.7 Optimizing Searches

This section contains these topics: ■ Section 22.7.1, Optimizing Searches for Large Group Entries ■ Section 22.7.2, Optimizing Searches for Skewed Attributes ■ Section 22.7.3, Optimizing Performance of Complex Search Filters

22.7.1 Optimizing Searches for Large Group Entries

Searches for group entries with several thousand attribute values for either the member or uniquemember attribute can have high latency. If you find the latency unacceptably high, there are steps you can take to reduce it. The simplest step is to reduce the number of attributes you are searching for. If you do not need to retrieve all the attributes of the group entry, specify required attributes in the search request to optimize the latency.

22.7.1.1 Entry Cache Enabled Configuration

If you still see unacceptable latency, even with required attributes specified, then you can try to cache the large group entry in the entry cache. To do this, increase the value of the orclEcacheMaxEntSize attribute in the instance-specific configuration entry: cn=componentname,cn=osdldapd,cn=subconfigsubentry This attribute controls the maximum size of a cache entry. The default value is 1M. If the size of the large group entry is greater than the value of orclEcacheMaxEntSize, change it to a large enough value to ensure that the large group entry is cached.

22.7.1.2 Entry Cache Disabled Configuration.

No action is required. This configuration is enabled by default.

22.7.2 Optimizing Searches for Skewed Attributes

To service a typical search request, the Directory Server sends a SQL statement to the Oracle Database. If a given attribute has very different response times depending on Table 22–6 Redo Log and Undo Tablespace Values Attribute Value Notes Redo Log 3 logs, 100MB each Many bulkdelete operations. Redo Log Total size 1000-15000MB Large number of write operations. Undo Tablespace At least 1GB total Many bulkdelete operations. Undo Tablespace 2-4 GB Large number of write operations. Note: If you expect frequent updates to large groups, then do not use this tuning methodology. Use the Entry Cache Disabled Configuration.