Posted: 27 Mar 2018 11:59 EDT Last activity: 12 Aug 2019 11:06 EDT
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.
I am facing the same problem, even forcing the time for example 11:59:59, at the clipboard appears correctly, but when it is saved on database it goes as 1:59:59 AM for the next day, does someone knows how to avoid that?
Posted: 2 years ago
Posted: 12 Aug 2019 2:02 EDT
Naresh Saketi (NareshS9)
Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write Post button here. Once created, please reply back here with the URL of the new post.
You may also refer this discussion link as a reference in the new thread.