Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Mon, 05 Apr 2004 @ 11:15:57 GMT

  <Prev Next>   <<First <Prev Next> Last>>  

Subj:   Re: Hexadecimal value for char-Mload error
From:   Victor Sokovin

This new formulation suggests that you are facing a problem with the input file layout definition. When you said that NULLIF worked for you but you did not want to use it because of the performance issues, you did not mention that you had the same layout problem with it. And I think you must have had it with NULLIF, right?

I would suggest to check whether the input file layout is suitable for MultiLoad at all. I read your last message as though you can have records in which the first field may be missing. In this case ML might take the second field and attempt to convert it to DECIMAL, and the conversion would fail because your second field (the indicator) contains chars. If that is true, this layout issue has nothing to do with "NULLIF vs. CASE", and you put together two different questions in one.

Do you have any influence on the layout of the input file? If so, you might consider the ML VARTEXT format and use a delimiter between fields in the input file.



  <Prev Next>   <<First <Prev Next> Last>>  
  Top Home Privacy Feedback  
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 15 Jun 2023