KAVB8602-E
The service control-name could not be started because the status of the IM database service could not be confirmed. (details = reason)
The control-name process could not start because completion of IM database service startup could not be confirmed.
- S:
-
The control-name process stops.
- O:
-
Take corrective action based on the reason:
-
Reason: Processing to start or stop the IM database service is being performed.
-
Reason: The IM database service stopped.
Execute the jimdbstatus command, confirm that the IM database service is running, and then perform the next operation.
In Windows:
- Start the IM database service, and then restart JP1/IM - Manager.
In UNIX:
- Stop JP1/IM - Manager, and then re-execute the jco_start command.
If SELinux is enabled, shut down JP1/IM - Manager, set SELinux security context by executing jimdbupdate command, and then re-execute the jco_start command.
If this error occurs when the OS is starting, specify the following common definition information, and then increase the number of retries so that it does not time out.
- [logical-host-name\JP1CONSOLEMANAGER\IMDB]
- DB_START_RETRY_COUNT
-
Reason: The restart of the IM database service was interrupted.
Execute jimdbstop -f, forcibly stop the IM database service, and then perform the next operation.
In Windows:
- Start the IM database service, and then restart JP1/IM - Manager.
In UNIX:
- Re-execute the jco_start command.
-
Reason: The IM database service has not been set up.
Set up the IM database service, and then start JP1/IM - Manager.
-
Reason: The status of the IM database service could not be confirmed.
-
Reason: A system error occurred.
Collect JP1/IM data, and then contact a system administrator.
-