Hi,
Oracle does not have a timestamp datatype. Therefore, timestamp fields intended for an Oracle target will need to be converted to a [b]date[/b] datatype.
Hi Craig,
You are absolutely correct. It's time for me to throw away my Oracle 7 Server SQL Language Reference Manual and also to notify Ascential to update their DataStage EE training manual. Thanks.
It's certainly not a valid number - it has two "-" characters in it for a start. What is the data type of the target column? Are you using generated or user-defined SQL?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
The error suggests that it is trying to take in a numeric data type column (specified within the datastage), change it to timestamp and see how it works.
Success consists of getting up just one more time than you fall.
loveojha2 wrote:The error suggests that it is trying to take in a numeric data type column (specified within the datastage), change it to timestamp and see how it works.
Sometimes it gives the same error if timestamp is not inserted in proper format.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'