From: Clif H. <cl...@di...> - 2002-04-05 14:28:05
|
> > Hi, > > maybe this is a really simple question but at the moment i am not able to help > myself out. > > I have a script that checks the entries on my ldap for updates or changes. > Ordinarily I get the data in a csv file go through it and check if the entry on > the ldap differs. If I check the values of the attributes it works fine an > changes them if needed. But if the whole DN of the dataset has changed I read > some attributes from the Dataset on the LDAP, delete the old entry and after all > I create the dataset with the new DN and a mix of new values (f.e. mail) and old > values (f.e. password) I get error messages from my db2 database like "[IBM][CLI > Driver][DB@/6000] SQL0954C Not enough storage is available in the application > heap to process the statement. SQLSTATE=5701" even if I increase the application > heap to an enormous size it works not in a stable way. > Maybe the way I handle datasets with modified dn's is wrong. Is there an easier > possibility to change the dn (not the realtive !) ? > > Thanks for your support. > > Cheers > Martin > Martin, Instead of deleting the old ldap entry why not do a modrdn on the entry. This changes the dn, and possibly the naming attribute - depends on option selection, but keeps all of the attribute data intact. Then all you would have to do is update the attribute data. The Examples pod has examples on how to do a modrdn command. As for the db2 errors, I can not help you with them. Regards, Clif |