Why Time stamp values is different between Agile 8.5 PLM Front end and backend oracle 8i database


In Agile 8.5 PLM, Change history and item history, the time stamp values like release date, effective date, obselete date and user action time, local client time.
All these columns are showing different values in Agile 8.5 PLM front end and different in backend Oracle 8i database.
For ex: Agile 8.5 PLM front end shows: – for effective date for a change – 8:04:28 PM, but in database it shows:- 7:04:28 PM.

Can someone explain why is the contradiction and also how can I align the data same as Agile 8.5 PLM Database? We need to extract data and time values are different and it is getting really difficult to get the done.


Agile User Asked on October 1, 2019 in Other APIs.
Add Comment
3 Answer(s)

What time zone are you in?

Agile Angel Answered on October 1, 2019.
Add Comment

I am in Eastern Standard Time.

Agile User Answered on October 1, 2019.

Do you see a difference in the time based on when daylight savings starts/ends?

on October 1, 2019.

No Keithrust, I did not see any change when daylight savings starts/ends.   Regardless of daylight savings, the time is contradicting between database and front end.

on October 1, 2019.

What is the time zone of the database server?

on October 1, 2019.
Add Comment

For our Agile system, internally, the dates on the database records are always stored in GMT time zone.  So, if you are in Agile, in US Eastern time, and you save a date and time at 11pm on Sep 30, the value in the database record will say 4am (or 5am) on Oct 1.  GMT is 4 or 5 hours ahead of EST.   Your personal user settings time zone  decide how the date is displayed when you look at it in Agile.

Agile Talent Answered on October 1, 2019.
Add Comment

Your Answer

By posting your answer, you agree to the privacy policy and terms of service.