[389-users] Creating extra backend database for sub-sub-suffix

Hi, I've this directory structure: dc=example,dc=cz + o=apps,dc=example,dc=cz + o=TCS2,o=aps,dc=example,dc=cz I would like store o=TCS2,o=aps,dc=example,dc=cz in it's own database, to be able create custom indexes only for entries under o=TCS2,o=aps,dc=example,dc=cz. When I create it this way: dsconf -D "cn=Directory Manager" -w "$pswd" \ ldap://localhost backend create \ --be-name "example_cz" --suffix="dc=example,dc=cz" dsconf -D "cn=Directory Manager" -w "$pswd" \ ldap://localhost backend create \ --be-name "TCS2_apps_example_cz" \ --suffix="o=TCS2,o=apps,dc=example,dc=cz" \ --parent-suffix="o=apps,dc=example,dc=cz" Then I'm unable find o=TCS2 under o=apps,dc=example,dc=cz: semik@doma:~$ ldapsearch -LLL -H ldaps://ldap.example.cz -D "cn=directory manager" -W -x -b o=apps,dc=example,dc=cz '(o=TCS2)' Enter LDAP Password: semik@doma:~$ But it is there: semik@doma:~$ ldapsearch -LLL -H ldaps://ldap.example.cz -D "cn=directory manager" -W -x -b o=TCS2,o=apps,dc=example,dc=cz '(o=TCS2)' Enter LDAP Password: dn: o=TCS2,o=apps,dc=example,dc=cz objectClass: top objectClass: organization o: TCS2 It is very likely because 389DS doesn't understand what I want to do. semik@doma:~$ ldapsearch -LLL -H ldaps://ldap.example.cz -D "cn=directory manager" -W -x -s base -b '' '(objectClass=*)' namingContexts nsBackendSuffix Enter LDAP Password: dn: namingContexts: o=TCS2,o=apps,dc=example,dc=cz namingContexts: dc=example,dc=cz nsBackendSuffix: example_cz:dc=example,dc=cz nsBackendSuffix: TCS2_apps_example_cz:o=TCS2,o=apps,dc=example,dc=cz When I create another database for o=apps,dc=example,dc=cz this way: dsconf -D "cn=Directory Manager" -w "$pswd" \ ldap://localhost backend create \ --be-name "example_cz" --suffix="dc=example,dc=cz" dsconf -D "cn=Directory Manager" -w "$pswd" \ ldap://localhost backend create \ --be-name "apps_example_cz" \ --suffix="o=apps,dc=example,dc=cz" \ --parent-suffix="dc=example,dc=cz" dsconf -D "cn=Directory Manager" -w "$pswd" \ ldap://localhost backend create \ --be-name "TCS2_apps_example_cz" \ --suffix="o=TCS2,o=apps,dc=example,dc=cz" \ --parent-suffix="o=apps,dc=example,dc=cz" It works: semik@doma:~$ ldapsearch -LLL -H ldaps://ldap.example.cz -D "cn=directory manager" -W -x -b o=apps,dc=example,dc=cz '(o=TCS2)' Enter LDAP Password: dn: o=TCS2,o=apps,dc=example,dc=cz objectClass: top objectClass: organization o: TCS2 semik@doma:~$ ldapsearch -LLL -H ldaps://ldap.example.cz -D "cn=directory manager" -W -x -s base -b '' '(objectClass=*)' namingContexts nsBackendSuffix Enter LDAP Password: dn: namingContexts: dc=example,dc=cz nsBackendSuffix: example_cz:dc=example,dc=cz nsBackendSuffix: apps_example_cz:o=apps,dc=example,dc=cz nsBackendSuffix: TCS2_apps_example_cz:o=TCS2,o=apps,dc=example,dc=cz In first scenario, there are two separate namingContexts o=TCS2,o=apps,dc=example,dc=cz and dc=example,dc=cz. I want to get rid of extra apps_example_cz backend database if possible. Is there a way how to NOT create database for o=apps,dc=example,dc=cz? Thanks -- ----------------------- Jan Tomasek aka Semik http://www.tomasek.cz/