This issue has been migrated from Redmine: https://dev.icinga.com/issues/2092
Created by Tommi on 2011-11-19 20:31:45 +00:00
Status: Resolved (closed on 2011-11-23 19:36:25 +00:00)
Target Version: 1.6
Last Update: 2011-12-03 11:30:23 +00:00 (in Redmine)
Starting with icinga 1.6 all dates are stored as local timestamps in the database. Before there was a diffent behavior storing and retrieving dates for each database system, which was difficult to handle for frontend apps. Therefore datatypes has been changed for mysql from DATETIME to TIMESTAMP and for oracle from DATE to LOCAL TIMESTAMP (0). Postgresql is already using TIMESTAMP. IDO2DB will set session timezone to UTC and store all unix timestamp (which are UTC per definition) with UTC. Please make sure your system returns Unix timestamps as real UTC based values (like "date -u '+%s'")
Make sure your database session runs in the same timezone in which the existing dates has been stored (e.g.your local timezone oracle:"select sessiontimezone from dual;"), if you are running the upgrade script.
Additional for your convinience in oracle you should set your session timestamp format to the value you want,e.g "alter session set nls_timestamp_format='YYYY-MM-DD HH24:MI:SS';" or similar.
Now you can see entries from different icinga installations which are in different time zones into the same database and regardless from where you accessing it, all entries are returned in your local time zone.
Updated by Wolfgang on 2011-11-19 22:31:29 +00:00
changed in git master
Updated by mfriedrich on 2011-11-23 14:41:03 +00:00
Updated by Tommi on 2011-11-23 17:29:41 +00:00
because of #2106 the sentence Postgresql is already using TIMESTAMP must be changed into Postgresql is already using TIMESTAMP, but changed to TIMESTAMP WITH TIME ZONE
Sorry for reopen this.
Updated by Wolfgang on 2011-11-23 19:36:25 +00:00
fixed in r1.6