Mailing-List: contact users-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@directory.apache.org
Received-SPF: pass (nike.apache.org: domain of chungonn@greenfossil.com
 designates 203.174.82.19 as permitted sender)
Message-ID: <497BE681.5090503@greenfossil.com>
Date: Sun, 25 Jan 2009 12:11:45 +0800
From: Cheong Chung Onn <chungonn@greenfossil.com>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: users@directory.apache.org
Subject: Deleting of schema fails due to dependencies
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-newmediaexpress-MailScanner-Information: Please contact the ISP for more
 information
X-newmediaexpress-MailScanner: Not scanned: please contact your Internet
 E-Mail Service Provider for details
X-MailScanner-From: chungonn@greenfossil.com
X-Virus-Checked: Checked by ClamAV on apache.org

Hi All,

This is another clarification we have regarding ApacheDS behavior. We 
have created our own schema with its own definition of Attributes and 
ObjectClasses. We managed to successfully import it into both ApacheDS 
and OpenLdap (old-style format).

When we want to delete the schema on ApacheDS using Studio, we were 
alerted with the following cryptic error messages -

     Error while deleting entry
    [LDAP: error code 53 - UNWILLING_TO_PERFORM: failed for     Del request
            Entry :
    '1.3.6.1.4.1.18060.0.4.0.2.1=1.3.6.1.4.1.30274.1.3.1,2.5.4.11=attributetypes,2.5.4.3=technetium,2.5.4.11=schema'
    : The attributeType with OID 1.3.6.1.4.1.30274.1.3.1 cannot be
    deleted until all entities using this attributeType have also been
    deleted.  The following dependees exist: [1.3.6.1.4.1.30274.1.4.2]]
      [LDAP: error code 53 - UNWILLING_TO_PERFORM: failed for     Del
    request
            Entry :
    '1.3.6.1.4.1.18060.0.4.0.2.1=1.3.6.1.4.1.30274.1.3.1,2.5.4.11=attributetypes,2.5.4.3=technetium,2.5.4.11=schema'
    : The attributeType with OID 1.3.6.1.4.1.30274.1.3.1 cannot be
    deleted until all entities using this attributeType have also been
    deleted.  The following dependees exist: [1.3.6.1.4.1.30274.1.4.2]]


We managed to hunt down the problem after much investigation. The 
problem lies with our new ObjectClass definition which is referencing 
the new Attributes. The only way to delete our schema is first we must 
delete the ou=objectclasses entries in our schema, then delete the 
entire schema.

This restriction also will cause an inter-lock situation if we would to 
create a hierarchy of attributes in the same schema. In our previous 
schema, we had created some hierarchy of Attributes and the nightmare 
starts when we tried to delete the schema. ApacheDS will complained 
about the dependees exists. Eversince we understood ApacheDS 
requirements, we have painstakingly remove all the hierarchies in our 
Attributes.

Is deleting ObjectClasses entries is a necessary step before deleting a 
schema?

Regards
chung-onn