Question

6
Replies
1271
Views
Ravikanth Pokuri (RavikanthP5163)
EvonSys

EvonSys
US
RavikanthP5163 Member since 2016 1 post
EvonSys
Posted: March 27, 2018
Last activity: August 12, 2019
Posted: 27 Mar 2018 11:59 EDT
Last activity: 12 Aug 2019 11:06 EDT
Closed

Daylight Saving Time - Date Time is saved to database incorrectly

We are on Pega 7.1.7 with Oracle 11g database server. We found an issue after the Daylight Saving Time correction is made on 3/11. All the date time properties are saved to the database table with one hour older time. For example, when we submit a case at 11:44 AM, the update date time is saved as "2018-03-27 10:44:45.375" in the save query that appears in tracer on merge to the work table. But the commit date time is updated correctly in the database table as it is sent as sysdate in the query. This discrepancy occurs in all Pega database tables such as work, assign, history etc.

We checked the server time, and it works properly. The database has an updated timezone version file (version 14). The database's sysdate gives the correct time. Please provide us any pointers to understand the root cause of the issue. The other problems, we suspect, caused by this issue are locking errors, SLAs processing future assignments etc.

Data Integration System Administration
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.