I encountered this problem with the same release of DataStage. It was caused by an Oracle 9i extract with the same target field specified twice. Perhaps that was just an "instigator", but when you get one of these esoteric error messages, start with your latest changes. DataStage error mes...