Events captured in the hour before Daylight Saving Time (DST) ends are stored in the CMS database with an incorrect timestamp. Specifically, CA DataMinder fails to take account of clocks being adjusted backward at the end of DST, so events captured in the preceding hour are stored with a timestamp that is +1:00 hour later than it should be. In the worst case, the iConsole may report events as being captured in the wrong order. For example, the iConsole may show an email reply as being captured before the original email was sent.
The problem only affects CMSs in time zones that use DST. Also, it can only occur once a year in the 60 minute window before DST ends. Customers are unlikely to experience this anomaly because DST typically ends at a time of low business activity (for example, at 2am on a Sunday).
However, there are plausible conditions under which a customer may experience this problem. For example, consider the following setup:
But CA DataMinder incorrectly converts the timestamp for the 10:45 email to 09:45 UTC.
|
Actual |
CMS |
iConsole |
#1 |
10:45 IST (01:45 PDT) |
09:45 UTC |
11:45 IST |
#2 |
11:15 IST (01:15 PST) |
09:15 UTC |
11:15 IST |
In this example, the CMS timestamp for email #1 is incorrect. The correct timestamp, taking account of the clock adjustment at the end of DST, should be 08:45 UTC.
Note: PDT is UTC-07:00. PST is UST-08:00. IST is UTC+02:00.
Copyright © 2014 CA.
All rights reserved.
|
|