Date to be loaded to be manipulated

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
dscabtest
Participant
Posts: 1
Joined: Mon May 25, 2009 7:16 am

Date to be loaded to be manipulated

Post by dscabtest »

Hi,

I am very new to DataStage and I see that one is supposed to look through the forum to check if the question has been answered earlier, and I have. However, I wasn't lucky enough.
Could anyone please tell me how to best handle the case of a moving a date from one oracle table to another.
I have a date read from an Oracle table (one schema) and whilst moving it through the transform it is a timestamp (because there are no date types in DS). I need to load that timestamp field into the target oracle table (another schema) that expects a date. How do I handle this so that no warnings are generated.

Thanks,

Cameron
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Welcome! :D

You are aware that Oracle DATE fields are, in essence, a Timestamp as they carry a time portion, yes? Have you tried simply carrying it through your job as a timestamp and loading it as such?

ps. The TIMESTAMP data type in Oracle adds fun stuff like milliseconds and TZ awareness, but for regular date and/or timestamp information people still use a DATE field.
-craig

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