Having helped a few users with this issue I did some research and this is what I found.When the ntp daemon is initiated at boot-up it will attempt to correct the current system time that was previously loaded from the file using ntp servers.
The latest image has the file relocated to the writable data partition and a symlink in it's place.
in most cases this works well but can cause an issue if events don't happen exactly as expected at the right times during boot up.
3) Also enable the fake-hwclock service to save the current time at shutdown the same way.
Whilst nothing can be done if there is a sudden loss of power this edit will mean a graceful reboot should only lose seconds.
DB2 9.7 APAR Fix list contains list of APARs shipped for each fix pack in DB2 Version 9.7 for Linux, UNIX and Windows products.
The Severity column value of 1 is high and 4 is low.Severity column represents the severity of the PMR at the time the APAR was opened.DB2 10.5 APAR Fix list contains list of APARs shipped for each fix pack in DB2 Version 10.5 for Linux, UNIX and Windows products.What I couldn't establish specifically was if the loading of the "fake time" at boot effected the one-shot.I'm not able to do the tests at the moment but will try them at a later date, in the meantime I will assume you are correct as you appear to know the system well and it's certainly more feasible for it to work that way.Providing the time difference remains less than 1000 secs the npt daemon will then continue to check and resync the time approximately every 5-6 mins (usually cycling 4 servers, each checked at up to 1024secs intervals).