Failed when add using ldapadd command

Hi

I have two directory server located at UAT and development

when i run "ldapadd -D "cn=Directory Manager" -w password -f somefile.ldif " on my DEVELOPMENT Server

it ran through and records get added to the directory server

However when i run the same command on mu UAT server pointing to directory server sitting on that server it always gives me

"Invalid Format : ldapadd"

After further checking i found that some attribute value are null example as below

dn: uid=lala,o=us.com

mail: yes@com.com

address:

Because of address attribute is null the directory server in uat always complaining that i cannot add this entry

the confusing part is it ran successfully in my development

i checked both directory server and both are having schema checking disabled mode?

Is there any particular configuration that specify the attribute value cannot be null or something?

Thanks

[964 byte] By [just_a_kid83a] at [2007-11-27 9:01:47]
# 1
Are you using the same version of ldapadd ?I don't think that we are shipping ldapadd anymore with Sun Directory Server, but I could be wrong.Anyway, ldapadd = ldapmodify -aLudovic.
ludovicpa at 2007-7-12 21:31:46 > top of Java-index,Web & Directory Servers,Directory Servers...
# 2

what do u meant by that?

but i can still run ldapadd in my UAT Server box and the Solaris OS does not complain

I tested using ldapmodify -a it still gives me something like below

ldapmodify: invalid format (line 3 of entry: uid=leerongl1, ou=Users, o=yes.com.sg)

ldapmodify: invalid format (line 3 of entry: uid=teokailo1, ou=Users, o=yes.com.sg)

After i checked the entry in my ldif file. it appears some attribute have some null value for example

dn: uid=yennyng1, ou=Users, o=yes.com.sg

roomNumber: h

givenName: Yenny Ng

mobile: 93475786

objectClass: top

objectClass: person

objectClass: organizationalPerson

objectClass: inetOrgPerson

objectClass: users

facsimileTelephoneNumber:78964

ou: Sales Admin

uid: yennyng1

[b]mail:[/b]

cn: user

groups: SYS ADMIN

telephoneNumber: 8

pager: 8765

o: TPC

sn: Ng

warehouseid: 111

warehouseid: 144

warehouseid: 145

warehouseid: 147

warehouseid: 153

warehouseid: 188

warehouseid: 191

personalTitle: Ms

title: Admin Assistant

userPassword: {SHA}jhnnaUUCK2fR/e8HvQKVxUaTDyY=

As you can see mail attribute have some null value..

After i enter/fill in that attribute and i run it again. it ran okay.

So i was wondering if there is any constraint on attribute when we import to directory server and how to disable them?

Thanks

just_a_kid83a at 2007-7-12 21:31:46 > top of Java-index,Web & Directory Servers,Directory Servers...
# 3
Below are my UAT Directory Server VersionSun Microsystems, Inc.Sun-ONE-Directory/5.2 B2003.143.0020And my Development ServerSun Microsystems, Inc.Sun Java(TM) System Directory Server/5.2_Patch_4 B2005.230.0041Thanks
just_a_kid83a at 2007-7-12 21:31:46 > top of Java-index,Web & Directory Servers,Directory Servers...
# 4

> what do u meant by that?

I think he means, are you using the same version of ldapadd (or ldapmodify) for both cases?

There are several different variants of these tools, depending on your OS and what LDAP software you have installed.

But regardless, you should avoid importing data with blank or null-valued attributes, even if it was permitted by ldapmodify. I suggest you remove all such attributes from your input LDIF file.

gtholberta at 2007-7-12 21:31:46 > top of Java-index,Web & Directory Servers,Directory Servers...