TD MLOAD truncating 11th character of CHAR(11) input -- why?

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
lmoose1
Premium Member
Premium Member
Posts: 28
Joined: Wed Sep 13, 2006 12:56 pm
Location: Kansas City

TD MLOAD truncating 11th character of CHAR(11) input -- why?

Post by lmoose1 »

A new Teradata MLOAD parallel job loads one column of a table from a dataset -- the column is of type/size CHAR(11). The TD MLOAD job reads the file, but wants to truncate the data by one character. Everything across the board is CHAR(11). No truncation is needed. The data gets loaded, but is wrong -- it is missing the final 11th character.

WE get the same results with a sequential file as input.

Here is the warning I'm getting:
TW_PAVE_SKUS,0: Warning: At row 1, link "SEQL_PAVE_PP_INTO_E1DW_WORK_PAVE_SKUS", while processing column "SKU"
Value "1000BBA4106" truncated to "1000BBA410"

Argh!!! Any ideas?
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

1. Verify that it really is Char(11), not Char(10). (I have to ask.)
2. Verify that there are no non-printing characters in the data.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
keshav0307
Premium Member
Premium Member
Posts: 783
Joined: Mon Jan 16, 2006 10:17 pm
Location: Sydney, Australia

Post by keshav0307 »

what is the data format? FASTLOAD or VARTEXT?
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

This sounds... familiar. Perhaps a carefully chosen search would turn something up.
-craig

"You can never have too many knives" -- Logan Nine Fingers
lmoose1
Premium Member
Premium Member
Posts: 28
Joined: Wed Sep 13, 2006 12:56 pm
Location: Kansas City

unicode seems to have been the culprit

Post by lmoose1 »

I had turned unicode on in the column metadata info as I was getting an error about type conversion from string to ustring. When I ran it without the unicode setting on the target columns, it loaded correctly without truncation. Guess there's always more to learn about unicode...
lmoose1
Premium Member
Premium Member
Posts: 28
Joined: Wed Sep 13, 2006 12:56 pm
Location: Kansas City

FYI: format was FASTLOAD.

Post by lmoose1 »

Any thoughts on whether FASTLOAD or VARTEXT would make a difference?
Post Reply