HelloDAV (DB2 Access View) has been created.
One of fields in Lotus has type Date/Time,
Field corresponding to it in DAV – type DATE
Checkbox “Normalize to GMT for time zone conversions” have been unchecked.
Server Domino 8.1.0
DB2 9.1.0
At viewing DAV, it was revealed, at some (not all!) lines (lotus documents) the date field has increased for 1 days.
Moreover, such bug could apper not right after document creations in lotus.
Or after recreation DAV the problem temporarily disappeared, but, then again, appeared.
I.e. if in the Lotus there is a document with date of 3/17/2010
In DB2 for days forward: 3/18/2010
Have changed type in DB2 on TIMESTAMP - has not helped in DB2: 3/18/2010 0:00:00.000000
Have changed on varchar. I thought if there will be a field text that it will save from boggus conversion – on has helped, all the same: in Lotus 3/17/2010,
And in DB2 2010-03-18-00.00.00.000000
I googled out that:
(http://www.kalechi.com/comments.nsf/dx/db2-and-Domino)
db2 access views (DAV):
Date/Time fields do not convert to db2 date fields correctly. If the Domino field has a time component then the resulting date in db2 is 1 day ahead. You have to make sure the field is @date (fieldname) in it’s translation formula for db2 to tie to the field correctly. It converts the time based on the current GMT area to GMT based time
Т.е if in Lotus the DATE/TIME field has not a time (only date), the result will be OK
If there is a time it will be +1 day.
Do anyone maybe known how bypass it problem ?
Thanks
(excuse me for my bad english)