RE: LDIF format question for Openldap-2.3.27
Yeah!
it mentioned that that error came from adding
cn=jdbc,dc=production,dc=net"
so as you told I tried using "cn=testApp, ou=jdbc, dc=production, dc=net" and
it worked.
So do you mean we can't create a entry with two "cn" values like
"cn=testApp, cn=jdbc, dc=production, dc=net"
if that is the case how can I convert my old database which has the format like
"cn=testApp, cn=jdbc, dc=production, dc=net"
to new database
-----Original Message-----
From: Hallvard Breien Furuseth [mailto:h.b.furuseth@usit.uio.no]
Sent: Thursday, April 05, 2007 4:49 PM
To: Venkat Reddy Valluri
Cc: openldap-software(a)openldap.org
Subject: RE: LDIF format question for Openldap-2.3.27
Venkat Reddy Valluri writes:
This is the error messgae I am getting
ldap_add: Internal (implementation specific) error (80)
additional info: no structuralObjectClass operational attribute
And hopefully it also mentioned that that error came from adding
cn=jdbc,dc=production,dc=net"
since that object lacks a structural object class. (Commonly people
abuse organizationalUnit for such objects. Which means you must add an
'ou' attribute.)
> dn: cn=jdbc,dc=production,dc=net
> objectClass: top
> objectClass: extensibleObject
> cn: jdbc
>
> (...)
> cn : testApp
Also delete the space before the ':'.
--
Regards,
Hallvard