The simdbmu service fails to start after adjusting or correcting time in Symantec Security Information Manager (SSIM) 4.7.x
Last Updated October 24, 2011
After installing SSIM you notice the time is in the future and you correct it via the command line, while logged in as simuser, using the WEB UI to change the time, or configuring a NTP server. The simdbmu service then fails to start after the time is corrected.
The simdbmu.log file will have errors that begin with this line when the service attempts to start:
The reason why simdbmu does not come up when moving date backward to the correct time is because simdbmu uses certain procedures/functions provided by IBM DB2. The SNAPSHOT_TBS_CFG is one of the functions, which is causing this issue.
For example, you install SSIM with a system date 24 hours in the future, and after installation you configure SSIM so an NTP server will manage the system time. The NTP server will then set the system time back 24 hours. But the IBM DB2 functions' creation time is still the 24 hours in the future and until that time has passed these functions will not be available for the simbdmu process.
If you were to login as db2admin run these commands and query from the db2 command line utility:
db2 connect to sesa
db2 "select FUNCNAME,CREATE_TIME from SYSCAT.FUNCTIONS" | grep SNAPSHOT_TBS_CFG"
You will get name of the DB2 function and time it was created. In this case the creation time would be in the future. The simdbmu process cannot run a function with a future date. This is known limitation from the DB2 if the time is moving backward by X minutes then the Functions created within X minutes before the change may not be resolved for X minutes after the change. See the link from IBM on restrictions and issues when changing dates
This will correct itself once the corrected time has passed the install time. In most cases it will be a short time such as 1- 2 hours to overnight. But if the time is far into the future and you cannot wait for the install time to pass, the only option at this time is to reinstall SSIM with the correct date and system time. This is working as designed for IBM DB2 and we cannot modify this behavior
Imported Document ID: TECH168701
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe