Oooo... it seems that you are migrating data from TDS v5.2 to SDS v6.4. Why don't you say so? Because, there could be pitfall that member of this group can help you better. Also, I never heard (encountered) a corrupted db2ldif command, because the output LDIF file is created regardless what the outcome is. So, maybe when you run db2ldif command without -j option, where all operational attributes are part of the output LDIF file, in which you are looking at it as 'strange' characters in that operational attribute data.
Also, it seems that, you did mentioned that you only need 'some data', which lead to use TDI, right? And, you solved your issue by pointing TDI to the other LDAP node, which I presumed to be a replicated LDAP node? The solution is a far fetched, but if your problem is solved, then so be it.
Yes, I heard Franz rumbling behind my neck now. :-)