Problem:
While creating a KPI with a time filter based on timestamp (schema type DateTime) or on Date as shown below, the monitor model crashes when it tries to process and update the value of the KPI. You will also see ERR 0697 in SystemErr.log (or in your console view if debugging from WID or RAD).
| Figure 1 |
IXJXE0778E: [ERR 0697] Strict date and time comparison rules are in effect. If any date or time values include time zones, all date and time values must include time zones.
Resolution:
The time filter expects a timestamp or date which contains a time zone value so you need to adjust the timezone (or date) to include time zone to avoid such problem. If your timestamp metric has ID “Last Update Timestamp”, then create a new metric called “Adjusted Last Update Timestamp” which is calculated using the following XPath function:
fn:adjust-dateTime-to-timezone(Last_Update_Timestamp)
| Figure 2 |
In case your original metric is a date with ID “Last_Update_Date”, then use the XPath function below instead:
fn: fn:adjust-date-to-timezone(Last_Update_Date)
Next step is to change the KPI time filter to use the new adjusted metric as shown below:
| Figure 3 |
No comments:
Post a Comment