What effects does a change of the system time (for example, from daylight saving time to standard time) have on the MaxDB database?
The MaxDB kernel works with the local time. When you change to daylight saving time, you do not have to change the time manually at database level. If a time interval occurs twice as the result of a time change, the system cannot determine at which of the two identical points of time it should stop when you perform a point-in-time recovery with an end time in the duplicate interval. In this case, you cannot perform the recovery with a target time that is located in the second interval. If you wanted to execute a point-in-time recovery at the second point of time, you would have to work with the IO sequence number. However, a function for easy retrieval of the IO sequence number from the log is currently not available in the MaxDB versions available. (PTS: 1134130) Problems do not occur during the recovery if you execute a Save Data during a time change, which means that the start time of the backup is later than the end time, and that subsequent log backups may be executed before the b
Related Questions
- How does changing the system time affect Oracle (for example, when daylight saving time is switched to standard time, and vice versa)?
- What effects does a change of the system time (for example, from daylight saving time to standard time) have on the MaxDB database?
- Does the Plugwise system take account of daylight saving time?
