Hi,
This is a known issue with DBConnect 3 (DBX-4019,DBX-4021).
The workaround that I have found is to change the value of the timestamp in the SQL query.
For example (SQL):
(SELECT *, dateadd(hh, 1, OriginalTimestamp) NewTimestamp FROM Table
The 'dateadd()' function is in the following format:
dateadd(<time unit to modify>, <modify by value>, <timestamp to modify>), <new timestap name>
Then change the date field to NewTimestamp in DBConnect. The above example adds one hour to the time field on a UTC source where Splunk is assuming it is in BST.
Just remember to:
A. Change everything back when the issue has been fixed.
B. Ensure that the new field does not conflict with any existing extractions you have.
Hope this helps.
... View more