Page 1 of 1

Issue with loading 0x0 instead of null in datastage 8.7

Posted: Wed Oct 09, 2013 8:52 am
by srini27
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

Posted: Wed Oct 09, 2013 9:29 am
by chulett
Are you seeing that only for CHAR fields?

Posted: Wed Oct 09, 2013 9:56 am
by srini27
Yes...The issue is only for CHAR fields.

Posted: Wed Oct 09, 2013 9:56 am
by ArndW
And what is your APT_STRING_PADCHAR defined as? (and what was it in your previous version)?

Posted: Wed Oct 09, 2013 10:50 am
by chulett
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.