directory-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kiran Ayyagari <kayyag...@apache.org>
Subject Re: Why ApacheDS server log says WARN: OID for name .... was not found within the OID registry
Date Fri, 01 Oct 2010 06:57:30 GMT
On Fri, Oct 1, 2010 at 11:04 AM, Sudheer Kumar <sudheerarimbra@gmail.com> wrote:
> Sorry, I accidentally sent my previous email without completing it.
>
> Hi
>
> I am using ApacheDS 1.5.5 and we have added all our custome attrubues and
> objectclasses to cn=schema,ou=schema for ex:
>
>
> Attribute:
> dn: m-oid=1.3.6.1.4.1.15265.0.36,ou=attributeTypes,cn=schema,ou=schema
> changetype: add
> objectClass: metaAttributeType
> objectClass: metaTop
> objectClass: top
> m-name: tdsCorporateDN
> m-oid: 1.3.6.1.4.1.15265.0.36
> m-singlevalue: FALSE
> m-syntax: 1.3.6.1.4.1.1466.115.121.1.12
> m-equality: caseIgnoreMatch
> m-substr: caseIgnoreSubstringsMatch
>
>
> Object class:
> dn: m-oid=1.3.6.1.4.1.15265.58,ou=objectClasses,cn=schema,ou=schema
> changetype: add
> objectClass: metaObjectClass
> objectClass: metaTop
> objectClass: top
> m-may: tdsCorporateDN
> m-name: telelogicGroup
> m-oid: 1.3.6.1.4.1.15265.58
> m-supobjectclass: groupOfUniqueNames
>
>
> Both have been added to cn=schema,ou=schema.
>
> in the server.xml I have added tdsCorporateDN in the <jdbmIndex
> attributeId="tdsCorporateDN" cacheSize="100"/> under  the
> <jdbmPartition id="RDS" cacheSize="100" suffix="dc=telelogic,dc=com"
> optimizerEnabled="true" syncOnWrite="true">
>        <indexedAttributes>.
>              <jdbmIndex attributeId="1.3.6.1.4.1.18060.0.4.1.2.1"
> cacheSize="100"/>
>          <jdbmIndex attributeId="1.3.6.1.4.1.18060.0.4.1.2.2"
> cacheSize="100"/>
>          <jdbmIndex attributeId="1.3.6.1.4.1.18060.0.4.1.2.3"
> cacheSize="100"/>
>          <jdbmIndex attributeId="1.3.6.1.4.1.18060.0.4.1.2.4"
> cacheSize="100"/>
>          <jdbmIndex attributeId="1.3.6.1.4.1.18060.0.4.1.2.5"
> cacheSize="10"/>
>          <jdbmIndex attributeId="1.3.6.1.4.1.18060.0.4.1.2.6"
> cacheSize="10"/>
>          <jdbmIndex attributeId="1.3.6.1.4.1.18060.0.4.1.2.7"
> cacheSize="10"/>
>          <jdbmIndex attributeId="dc" cacheSize="100"/>
>          <jdbmIndex attributeId="ou" cacheSize="100"/>
>          <jdbmIndex attributeId="objectClass" cacheSize="100"/>
>          <jdbmIndex attributeId="uniquemember" cacheSize="100"/>
>  <jdbmIndex attributeId="cn" cacheSize="100"/>
>   <jdbmIndex attributeId="sn" cacheSize="100"/>
>  <jdbmIndex attributeId="member" cacheSize="100"/>
>          <jdbmIndex attributeId="uid" cacheSize="100"/>
>          <jdbmIndex attributeId="tdsCorporateDN" cacheSize="100"/>
> </indexedAttributes>
>      </jdbmPartition>
>    </partitions>
>
> ..............
>
> When I start apacheds it get the following warning in the log.
>
>  WARN [org.apache.directory.server.schema.registries.DefaultOidRegistry] -
> OID for name 'tdsCorporateDN' was not found within the OID registry
IIRC this warning is not harmful
>
> Does it make any sense? Will it affect the indexing? Will my
> attribute tdsCorporateDN be indexed so that the search will be faster?
note that 1.5.5 doesn't support auto-indexing, i.e if some data already exists
before creating a new index then that index won't contain entries for
existing data.
Always define indexes before adding any data.

P.S:- this has been fixed in current trunk

HTH
Kiran Ayyagari

Mime
View raw message