Um I have my doubts that is correct.
First since I've defined that the delimiter is a caret, datastage shouldn't be looking for a comma.
Secondly and this disputes the buffer overflow theory because my work around was to leave the comma delimiter defined and send the data to a sequential file. Doing this I don't get the overflow error.
My work around job looks like this:
Code: Select all
[FTP Stage] ---> [Sequential File] ---->[Transformer] ---> [Database]
So my theory is that Datastage has a bug and it uses that delimiter field for something other than just as a delimiter. This isn't the first bug I've found in the FTP Stage. I have also documented in another post (
viewtopic.php?t=149853) that if you change the port number in the stage, datastage freaks out.