Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Can't Do
Priority: Major
Fix Version/s: None
Affects Version/s: 8.12.13.6_4
Component/s: OData
Labels:
None

Workaround:

Workaround Exists
Workaround Description:

Hide

We changed the timezone of the DataVirt server to be UTC and re-started DataVirt, and the odata query was successful. (In this case, the SQL was generated with 08:52 local time, which the database matched to the correct records with 08:52Z). For now, we will update the Data Virt servers to run in UTC time. I can have this fix in Dev/ Sit within the hour

Show
We changed the timezone of the DataVirt server to be UTC and re-started DataVirt, and the odata query was successful. (In this case, the SQL was generated with 08:52 local time, which the database matched to the correct records with 08:52Z). For now, we will update the Data Virt servers to run in UTC time. I can have this fix in Dev/ Sit within the hour

Description

The incoming odata4 request is requesting the records at 08:52Z (specifying UTC time). The DataVirt server (running in US/Chicago time) converts that into SQL to ask the database for records at 03:52 (with no timezone specifier... should be in local time, or US/Chicago). The database should recognize that the 03:52 Local time should be converted back to 08:52Z to match the DB records, however, it is not. This (and other tests), leads us to the conclusion that the database session/connection is actually not using US/Chicago (-5:00) timezone, but is instead using the UTC timezone. Unfortunately, we were not able to confirm either in the logs or in the configuration, where the connection was being set up in UTC timezone.

Attachments

Activity

People

Assignee:: Oscar Arribas Arribas

Reporter:: Deborah Steigner (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2018/06/04 4:29 PM

Updated:: 2020/10/07 12:15 PM

Resolved:: 2018/07/02 3:53 PM