Working With Oracle® Solaris 11.2 Directory and Naming Services: LDAP

Exit Print View

Updated: July 2014
 
 

Creating Virtual List View Indexes With Oracle Directory Server Enterprise Edition

For large maps, LDAP virtual list view (VLV) indexes must be used to ensure LDAP searches return complete results. For information about setting up VLV indexes on the Oracle Directory Server Enterprise Edition, see the Sun Java System Directory Server Enterprise Edition 6.2 documentation.

VLV search results use a fixed page size of 50000. If VLVs are used with Oracle Directory Server Enterprise Edition, both the LDAP server and N2L server must be able to handle transfers of this size. If all of your maps are known to be smaller than this limit, you do not need to use VLV indexes. However, if your maps are larger than the size limit or you are unsure of the size of all maps, use VLV indexes to avoid incomplete returns.

If you are using VLV indexes, set up the appropriate size limits as follows:

  • On the Oracle Directory Server Enterprise Edition: nsslapd-sizelimit attribute must be set greater than or equal to 50000 or –1. See the idsconfig(1M) man page.

  • On the N2L server: nisLDAPsearchSizelimit attribute must be set greater than or equal to 50000 or zero. For more information, see the NISLDAPmapping(4) man page.

After VLV indexes have been created, activate them by running dsadm with the vlvindex option on the Oracle Directory Server Enterprise Edition server. See the dsadm(1M) man page for more information.

VLVs for Standard Maps

Use the Oracle Directory Server Enterprise Edition idsconfig command to set up VLVs if the following conditions apply:

  • You are using Oracle Directory Server Enterprise Edition.

  • You are mapping standard maps to RFC 2307bis LDAP entries.

VLVs are domain specific, so each time idsconfig is run, VLVs are created for one NIS domain. Therefore, during the NIS-to-LDAP transition, you must run idsconfig once for each nisLDAPdomainContext attribute included in the NISLDAPmapping file.

VLVs for Custom and Nonstandard Maps

You must manually create new Oracle Directory Server Enterprise Edition VLVs for maps, or copy and modify existing VLV indexes, if the following conditions apply:

  • You are using the Oracle Directory Server Enterprise Edition.

  • You have large custom maps or have standard maps that are mapped to nonstandard DIT locations.

To view existing VLV indexes, type the following command:

% ldapsearch -h hostname -s sub -b "cn=ldbm database,cn=plugins,cn=config" "objectclass=vlvSearch"