DSXchange

Thanks Mike and Craig ! @Mike, That's exactly what happened in the scenario I explained. The string got truncated in the middle of multi byte character. As a workaround, I added a check to see if the 30th character is alphanumeric. If not I extract only the 29 characters to avoid and loading issue. ...

Thanks Mike for the response. In fact, we were using NVARCHAR initially. In that case, DS reads the special character as single byte. When applying SUBSTR [1,30], it extracted 31 bytes of data. But the target Oracle table has size restriction of 30 bytes. So the record was getting rejected by DB for...