time to integer issue

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
vinsashi
Participant
Posts: 150
Joined: Mon Aug 20, 2007 4:52 am
Location: singapore

time to integer issue

Post by vinsashi »

Hi,
my db2 source contains one filed UPDATE_Z the datatype is 'time'
and reference data is teradata and on filed UPDATE_Z datatype is "integer ' but format is "99:99:99".we are doing lookup but job getting abort. and target is teradata and datatype is integer with fomrat "99:99:99.


Adance Thanks
v..........
samyamkrishna
Premium Member
Premium Member
Posts: 258
Joined: Tue Jul 04, 2006 10:35 pm
Location: Toronto

Re: time to integer issue

Post by samyamkrishna »

Hi ,

What is the error message you are getting.
vinsashi
Participant
Posts: 150
Joined: Mon Aug 20, 2007 4:52 am
Location: singapore

Post by vinsashi »

unable convert time to int32 error getting....
samyamkrishna
Premium Member
Premium Member
Posts: 258
Joined: Tue Jul 04, 2006 10:35 pm
Location: Toronto

Post by samyamkrishna »

at the source do a time to string and at the target do the opposite(string to time).
It should work.


I had faced the same issue
Doing this has solved the issue.

Also can you post the table structure of the target table here.( the time columns )
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Sorry but there's no such thing as an integer with a format. Once you add any kind of external format (like "99:99:99") then it becomes a string. As noted, compare them as such or remove the formatting and compare the integers.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply