Difference in Server and Datastage Director Time

[Sreedhar]

Hi

We have recently moved on to DataStage 8.1.
The server time on which the DS is installed and the time shown on the Directory are differing by 9 hours.

How do I sync these times.

Let me know if you need more information.

Regards,

[chulett]

Do you have a timezone issue?

[ray.wurlod]

You can set the times on the machines to be the same, perhaps.

You can also set an option in Director such that the difference is not checked for/reported. The "sweep it under the carpet" approach. However, all times reported in Director are server times.

[Sreedhar]

Hi,

My Unix Server on which Datastage is installed has US PST timing.
The Director time is differing by 9 hours.

" On the unix box when I type Date
Let's say the time is 1:00 pm
Now when I run a job in Director is show me a time of 9:00pm."

Yes we can set off the option in director but I don't want to do that.

My whole point is to keep both the server and the clinet in Sync.

How do we put Server and Datastage Client in Sync.

I believe there should be some setting on DSengine where we can set the US PST timings.

Regards,

[ray.wurlod]

DataStage server gets its time from the operating system time of the machine it's on.

DataStage clients get the time from the operating system time of the machine they're on.

Any difference is not the responsibility of DataStage. It is up to YOU to synchronize the machine times if this is what you desire.

[Sreedhar]

Data Stage server gets its time from the operating system time of the machine it's on.

I Agree

Data Stage clients get the time from the operating system time of the machine they're on.

I Agree

Both the Server and Client are sitting next to each other. In the same building, On the same floor. With the same Local Time on both the Machines.


Any difference is not the responsibility of Data Stage. It is up to YOU to synchronize the machine times if this is what you desire.

My question is how do I sync?

As I said before the Client machine is differing by 9 hours.

[ray.wurlod]

Right click on the clock on the right hand end of the status bar and select Adjust Date/Time from the menu.

If you don't have permission to do this, get the Administrator to do it for you.

Investigate mechanisms for synchronizing time from the network - there are myriad techniques for doing that, as an internet search will reveal.

[BradMiller]

I know that thats not the problem,sourcing the dsenv itself is giving a wrong date I dont know where its picking that date bec.. server date is correct.I found that the problem of incorrect time is due to dsenv enviroment variable and the specially LIBPATH. in that if /usr/lib is ahead of APT_ORCHOME/lib
then when we source we get the correct date
but when I start the DSEngine I get this error "
0509-150 Dependent module /usr/lib/libicui18n.a could not be loaded.
0509-103 The module has an invalid magic number."
and not able to login to Dstage
if we change it to normal like /usr/lib at the end in LIBPATH I am able to logon to Datastage but date doesnot work I mean it doesn't show up correctly in the Director.Could you please suggest me.

[ray.wurlod]

I can not reproduce this problem. The client and server times are the same, in spite of being a three-tier topology.

Information Server 8.1 with critical patch and Fix Pack 1 applied.

[Sreedhar]

Hi,

we got the problem fixed by adding this to the dsenv file.

export TZ=PST8PDT

Let me know if you need more information.

Regards,

[asorrell]

Ray - Just a FYI - I am able to reproduce this on AIX 6.1 with 8.1 with fix pack 1 and DataStage rollup 1. Will report to IBM and see what they say.

[asorrell]

Late followup (Just got asked by someone if this was ever resolved)

I filed an PMR with both the IIS team and the AIX team and they were both stumped. It wasn't until a few days later that I found out that one admin had changed the system timezone manually in UNIX instead of using AIX's SMIT admin tool.

So we "reset" the timezone using SMIT and the time difference went away!

Apparently AIX has hidden timezone settings that aren't updated correctly unless you use SMIT...

[ray.wurlod]

Ah. My Sys Admin always uses smit (or smitty, usually). Useful to know.

[kinu008]

You can set the times on the machines to be the same, perhaps.

You can also set an option in Director such that the difference is not checked for/reported. The "sweep it under the carpet" approach. However, all times reported in Director are server times.

Hello all;
We recently installed InformationServer 8.5 Enterprise Edition Fix pack 1 and migrated some server jobs from 7.5 to 8.5... so far all jobs are running fine with out any problems, except the timing issue:

I noticed that time in IS director is 4 hours ahead... here is what i did:

Actual time is 1 PM - EDT American - New york Time (in my watch )

1. Executed 'date' command in administrator - returned 17:00
2. Executed 'sh -c date' command in administrator - returned 17:00
3. Executed 'sh -c date' command in SSH (telnet) - returned 13:00

if you noticed, 'sh -c date' command is returning different values in datastage administrator and SSH (telnet) client, which is off by 4 hours...

I would really appreciate if you can help me to fix this issue.

Thanks a lot, Kiran

[PaulVL]

Look at your profile.

Which user id are you loging in with via telnet?
Is it the same user id that is executing datastage (dsadm) ?

Look at the profile of that ID. Are you setting your time zone?

How is the time on the server causing you an issue?
Are you relying upon the internal job scheduler to trigger jobs?
Are you extracting server time via a routine and using that to populate some of your date fields?