Timestamp Format Changes In Hash File

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
jerome_rajan
Premium Member
Premium Member
Posts: 376
Joined: Sat Jan 07, 2012 12:25 pm
Location: Piscataway

Timestamp Format Changes In Hash File

Post by jerome_rajan »

Hi,

I have a simple job that reads from my date dimension and writes into a hash file. One of the fields of Date datatype is read as a timestamp in my oracle connector using the mask YYYY-MM-DD HH24:MI:SS. I'd expect the timestamp to read something like

Code: Select all

2014-06-11 00:00:00
But when I see the hash file where it is written, the value is stored as

Code: Select all

2014-06-11 12:00:00
Can someone help me understand why this is happening and how I can avoid this?
Jerome
Data Integration Consultant at AWS
Connect With Me On LinkedIn

Life is really simple, but we insist on making it complicated.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

The hashed file does not have any timestamp (or any other) data type. Can you perhaps make the field a little wider, to see whether there's an AM/PM designator terminating it?

You might also try setting the column definition in the Hashed File stage to have a Data Element of Timestamp.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
jerome_rajan
Premium Member
Premium Member
Posts: 376
Joined: Sat Jan 07, 2012 12:25 pm
Location: Piscataway

Post by jerome_rajan »

That's what I thought and hence was expecting the exact same value at the source to be written to the file. I'll try to widen the field and verify
Jerome
Data Integration Consultant at AWS
Connect With Me On LinkedIn

Life is really simple, but we insist on making it complicated.
Post Reply