Hi I installed Openldap-2.3.27. how can I create ldif format file for "cn=testApp, cn=jdbc, dc=production, dc=net" which worked for old Openldap server.
I was able to create a ldif file for "cn=jdbc, dc=production, dc=net" which inturn produces entries with out giving any problem
but if I use two "cn" names in ldif it is giving problems
Thks&Rgds --Venkat
Hi Here is my LDIF file
dn: dc=production,dc=net objectClass: dcObject objectClass: organization dc: production o: Production
dn: cn=jdbc,dc=production,dc=net objectClass: top objectClass: extensibleObject
dn: cn=testApp,cn=jdbc,dc=production,dc=net fnDbFactoryName: OCCDataSourceFactory fnDbCacheScheme: DYNAMIC fnDbMaxLimit: 10 fnDbUser: testApp objectClass: fnDbConPool fnDbPasswd: testApp fnDbMinLimit: 2 fnDbURL: jdbc:oracle:thin:@test.com:1521:test
in slapd.conf
suffix "dc=production, dc=net" rootdn "testApp, cn=jdbc, dc=production, dc=net"
and I am getting a error like below
ldap_add: Internal (implementation specific) error (80) additional info: no structuralObjectClass operational attribute
Can you tell me where I am missing by the way same ldif file worked with old Openldap server
Thanks in advance
-----Original Message----- From: paul kölle [mailto:pkoelle@gmail.com] Sent: Thursday, April 05, 2007 12:10 PM To: Venkat Reddy Valluri Cc: openldap-software@openldap.org Subject: Re: LDIF format question for Openldap-2.3.27
Venkat Reddy Valluri schrieb: [snipp]
but if I use two "cn" names in ldif it is giving problems
Can you please post relevant parts of your LDIF files and the error message?
thanks Paul
On 4/5/07, Venkat Reddy Valluri wrote:
dn: cn=testApp,cn=jdbc,dc=production,dc=net fnDbFactoryName: OCCDataSourceFactory fnDbCacheScheme: DYNAMIC fnDbMaxLimit: 10 fnDbUser: testApp objectClass: fnDbConPool fnDbPasswd: testApp fnDbMinLimit: 2 fnDbURL: jdbc:oracle:thin:@test.com:1521:test
You are missing the objectClass and cn attributes in your entry.
Svend
On 4/5/07, Svend Sorensen wrote:
On 4/5/07, Venkat Reddy Valluri wrote:
dn: cn=testApp,cn=jdbc,dc=production,dc=net fnDbFactoryName: OCCDataSourceFactory fnDbCacheScheme: DYNAMIC fnDbMaxLimit: 10 fnDbUser: testApp objectClass: fnDbConPool fnDbPasswd: testApp fnDbMinLimit: 2 fnDbURL: jdbc:oracle:thin:@test.com:1521:test
You are missing the objectClass
I didn't see the objectClass line. Is fnDbConPool a structural objectClass?
and cn attributes in your entry.
Yeah! I added the cn values to both entries, but still it didn't work Yeah fnDbConPool is a structural objectClass.
dn: cn=jdbc,dc=production,dc=net objectClass: top objectClass: extensibleObject cn: jdbc
dn: cn=testApp,cn=jdbc,dc=production,dc=net fnDbFactoryName: OCCDataSourceFactory fnDbCacheScheme: DYNAMIC fnDbMaxLimit: 10 fnDbUser: testApp objectClass: fnDbConPool fnDbPasswd: testApp fnDbMinLimit: 2 fnDbURL: jdbc:oracle:thin:@test.com:1521:test cn : workSmart
-----Original Message----- From: openldap-software-bounces+venkat.valluri=quinnfable.com@OpenLDAP.org [mailto:openldap-software-bounces+venkat.valluri=quinnfable.com@OpenLDAP .org]On Behalf Of Svend Sorensen Sent: Thursday, April 05, 2007 2:28 PM To: openldap-software@openldap.org Subject: Re: LDIF format question for Openldap-2.3.27
On 4/5/07, Svend Sorensen wrote:
On 4/5/07, Venkat Reddy Valluri wrote:
dn: cn=testApp,cn=jdbc,dc=production,dc=net fnDbFactoryName: OCCDataSourceFactory fnDbCacheScheme: DYNAMIC fnDbMaxLimit: 10 fnDbUser: testApp objectClass: fnDbConPool fnDbPasswd: testApp fnDbMinLimit: 2 fnDbURL: jdbc:oracle:thin:@test.com:1521:test
You are missing the objectClass
I didn't see the objectClass line. Is fnDbConPool a structural objectClass?
and cn attributes in your entry.
Yeah! I added the cn values to both entries, but still it didn't work Yeah fnDbConPool is a structural objectClass.
dn: cn=jdbc,dc=production,dc=net objectClass: top objectClass: extensibleObject cn: jdbc
dn: cn=testApp,cn=jdbc,dc=production,dc=net fnDbFactoryName: OCCDataSourceFactory fnDbCacheScheme: DYNAMIC fnDbMaxLimit: 10 fnDbUser: testApp objectClass: fnDbConPool fnDbPasswd: testApp fnDbMinLimit: 2 fnDbURL: jdbc:oracle:thin:@test.com:1521:test cn : testApp
-----Original Message----- From: Venkat Reddy Valluri Sent: Thursday, April 05, 2007 3:15 PM To: openldap-software@openldap.org Subject: RE: LDIF format question for Openldap-2.3.27
Yeah! I added the cn values to both entries, but still it didn't work Yeah fnDbConPool is a structural objectClass.
dn: cn=jdbc,dc=production,dc=net objectClass: top objectClass: extensibleObject cn: jdbc
dn: cn=testApp,cn=jdbc,dc=production,dc=net fnDbFactoryName: OCCDataSourceFactory fnDbCacheScheme: DYNAMIC fnDbMaxLimit: 10 fnDbUser: testApp objectClass: fnDbConPool fnDbPasswd: testApp fnDbMinLimit: 2 fnDbURL: jdbc:oracle:thin:@test.com:1521:test cn : workSmart
-----Original Message----- From: openldap-software-bounces+venkat.valluri=quinnfable.com@OpenLDAP.org [mailto:openldap-software-bounces+venkat.valluri=quinnfable.com@OpenLDAP .org]On Behalf Of Svend Sorensen Sent: Thursday, April 05, 2007 2:28 PM To: openldap-software@openldap.org Subject: Re: LDIF format question for Openldap-2.3.27
On 4/5/07, Svend Sorensen wrote:
On 4/5/07, Venkat Reddy Valluri wrote:
dn: cn=testApp,cn=jdbc,dc=production,dc=net fnDbFactoryName: OCCDataSourceFactory fnDbCacheScheme: DYNAMIC fnDbMaxLimit: 10 fnDbUser: testApp objectClass: fnDbConPool fnDbPasswd: testApp fnDbMinLimit: 2 fnDbURL: jdbc:oracle:thin:@test.com:1521:test
You are missing the objectClass
I didn't see the objectClass line. Is fnDbConPool a structural objectClass?
and cn attributes in your entry.
--On Thursday, April 05, 2007 3:20 PM -0400 Venkat Reddy Valluri venkat.valluri@quinnfable.com wrote:
Yeah! I added the cn values to both entries, but still it didn't work Yeah fnDbConPool is a structural objectClass.
dn: cn=jdbc,dc=production,dc=net objectClass: top objectClass: extensibleObject cn: jdbc
dn: cn=testApp,cn=jdbc,dc=production,dc=net fnDbFactoryName: OCCDataSourceFactory fnDbCacheScheme: DYNAMIC fnDbMaxLimit: 10 fnDbUser: testApp objectClass: fnDbConPool fnDbPasswd: testApp fnDbMinLimit: 2 fnDbURL: jdbc:oracle:thin:@test.com:1521:test cn : testApp
So, what is the error you get? I mean, we can play guessing games with you all day, but I tire of them pretty quickly. Why not share the error message too?
--Quanah
-- Quanah Gibson-Mount Senior Systems Software Developer ITS/Shared Application Services Stanford University GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
This is the error messgae I am getting
ldap_add: Internal (implementation specific) error (80) additional info: no structuralObjectClass operational attribute
Thanks for your respone so quickly In earlier mail it was a typo.
-----Original Message----- From: Quanah Gibson-Mount [mailto:quanah@stanford.edu] Sent: Thursday, April 05, 2007 3:49 PM To: Venkat Reddy Valluri; openldap-software@openldap.org Subject: RE: LDIF format question for Openldap-2.3.27
--On Thursday, April 05, 2007 3:20 PM -0400 Venkat Reddy Valluri venkat.valluri@quinnfable.com wrote:
Yeah! I added the cn values to both entries, but still it didn't work Yeah fnDbConPool is a structural objectClass.
dn: cn=jdbc,dc=production,dc=net objectClass: top objectClass: extensibleObject cn: jdbc
dn: cn=testApp,cn=jdbc,dc=production,dc=net fnDbFactoryName: OCCDataSourceFactory fnDbCacheScheme: DYNAMIC fnDbMaxLimit: 10 fnDbUser: testApp objectClass: fnDbConPool fnDbPasswd: testApp fnDbMinLimit: 2 fnDbURL: jdbc:oracle:thin:@test.com:1521:test cn : testApp
So, what is the error you get? I mean, we can play guessing games with you all day, but I tire of them pretty quickly. Why not share the error message too?
--Quanah
-- Quanah Gibson-Mount Senior Systems Software Developer ITS/Shared Application Services Stanford University GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
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 ':'.
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@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 ':'.
--On Thursday, April 05, 2007 5:14 PM -0400 Venkat Reddy Valluri venkat.valluri@quinnfable.com wrote:
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
You don't understand what he said. What he said was, you were missing a structural objectClass for the jdbc entry, which you will need to have before you can add it.
--Quanah
-- Quanah Gibson-Mount Senior Systems Software Developer ITS/Shared Application Services Stanford University GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
I have structural obejct class fnDbConPool for cn=testApp here I am using jdbc as a tree struture but not like a structural obejct class like below --dc=production, dc=net --jdbc --testApp1 url structural obejct class fnDbConPool min max --testApp2 url min max
here why should I need structural obejct class for jdbc???
-----Original Message----- From: Quanah Gibson-Mount [mailto:quanah@stanford.edu] Sent: Thursday, April 05, 2007 9:00 PM To: Venkat Reddy Valluri; openldap-software@openldap.org Subject: RE: LDIF format question for Openldap-2.3.27
--On Thursday, April 05, 2007 5:14 PM -0400 Venkat Reddy Valluri venkat.valluri@quinnfable.com wrote:
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
You don't understand what he said. What he said was, you were missing a structural objectClass for the jdbc entry, which you will need to have before you can add it.
--Quanah
-- Quanah Gibson-Mount Senior Systems Software Developer ITS/Shared Application Services Stanford University GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
--On Friday, April 06, 2007 9:59 AM -0400 Venkat Reddy Valluri venkat.valluri@quinnfable.com wrote:
I have structural obejct class fnDbConPool for cn=testApp here I am using jdbc as a tree struture but not like a structural obejct class like below --dc=production, dc=net --jdbc --testApp1 url structural obejct class fnDbConPool min max --testApp2 url min max
here why should I need structural obejct class for jdbc???
Because its required for all entries to have a structural objectClass. These things are objects, they need something to say what it is that they are. ;)
--Quanah
-- Quanah Gibson-Mount Senior Systems Software Developer ITS/Shared Application Services Stanford University GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
Venkat Reddy Valluri writes:
(...) here why should I need structural obejct class for jdbc???
Look, go and learn about LDAP, otherwise you'll keep messing up.
http://en.wikipedia.org/wiki/LDAP http://www.ldapman.org/articles/intro_to_ldap.html http://www.ldapman.org/articles/tree_design.html
And when you don't know LDAP, at least try what you are told to try instead of raising objections based on your misunderstanding of how it works.
--On Thursday, April 05, 2007 3:14 PM -0400 Venkat Reddy Valluri venkat.valluri@quinnfable.com wrote:
Yeah! I added the cn values to both entries, but still it didn't work Yeah fnDbConPool is a structural objectClass.
dn: cn=jdbc,dc=production,dc=net objectClass: top objectClass: extensibleObject cn: jdbc
dn: cn=testApp,cn=jdbc,dc=production,dc=net fnDbFactoryName: OCCDataSourceFactory fnDbCacheScheme: DYNAMIC fnDbMaxLimit: 10 fnDbUser: testApp objectClass: fnDbConPool fnDbPasswd: testApp fnDbMinLimit: 2 fnDbURL: jdbc:oracle:thin:@test.com:1521:test cn : workSmart
What in the world makes you think
cn: workSmart
is the RDN value for this entry? I suggest you examine the jdbc entry, and see if you can discover the correlation between the value for cn there (RDN value) and the values in the DN.
--Quanah
-- Quanah Gibson-Mount Senior Systems Software Developer ITS/Shared Application Services Stanford University GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
--On Thursday, April 05, 2007 12:34 PM -0400 Venkat Reddy Valluri venkat.valluri@quinnfable.com wrote:
Hi Here is my LDIF file
dn: dc=production,dc=net objectClass: dcObject objectClass: organization dc: production o: Production
dn: cn=jdbc,dc=production,dc=net objectClass: top objectClass: extensibleObject
I take it you don't understand the requirements of LDIF/LDAP. There must be an RDN attribute defined in the entry. Therefore, this entry requires at least one cn value, which must be
cn: jdbc
dn: cn=testApp,cn=jdbc,dc=production,dc=net fnDbFactoryName: OCCDataSourceFactory fnDbCacheScheme: DYNAMIC fnDbMaxLimit: 10 fnDbUser: testApp objectClass: fnDbConPool fnDbPasswd: testApp fnDbMinLimit: 2 fnDbURL: jdbc:oracle:thin:@test.com:1521:test
Same as above. This requires the corresponding RDN value.
--Quanah
-- Quanah Gibson-Mount Senior Systems Software Developer ITS/Shared Application Services Stanford University GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
openldap-software@openldap.org