Issue with loading 0x0 instead of null in datastage 8.7

srini27 · Post by **srini27** » Wed Oct 09, 2013 8:52 am

Hi,

In Datastage 8.7 , we are seeing 0x0 getting inserted in target database (Oracle) instead of null . we should have null value inserted if incoming data for a particular filed is empty.

please advise me on this issue.

Thanks
Srinivas

chulett · Post by **chulett** » Wed Oct 09, 2013 9:29 am

Are you seeing that only for CHAR fields?

srini27 · Post by **srini27** » Wed Oct 09, 2013 9:56 am

Yes...The issue is only for CHAR fields.

ArndW · Post by **ArndW** » Wed Oct 09, 2013 9:56 am

And what is your APT_STRING_PADCHAR defined as? (and what was it in your previous version)?

chulett · Post by **chulett** » Wed Oct 09, 2013 10:50 am

Not sure if there's a previous version involved but the default padding character is "0x0" and you'd need to change that to "0x20" (via the APT variable that Arnd noted) so that it pads with spaces.