KAMN243-D (E+L)
There is a fail of system reset or the Server who stops abnormally in the own host:aa....aa. Online server:bb....bb has the possibility that is starting in other hosts. The initial state was changed to Standby server, and it was made a start wait state.
The host of the current system cannot perform a system reset. Another possibility is that a server terminated abnormally. Since the active server might have been started by a host on another system, the startup type of the server indicated by the server alias name has been changed to a standby server to place it in an active server startup wait-state.
aa....aa: Host name
bb....bb: Server alias name
- S:
-
Continues processing.
- O:
-
Determine the cause of the server's abnormal termination. Thoroughly verify that no active servers are running on remote systems#, and then either use the wait-state server start command (monact) to make this server, currently in the startup wait-state, start as the active server, or terminate HA Monitor normally.
#: If you execute the wait-state server startup command (monact) without sufficient verification, two active servers will be running, which might result in the corruption of shared resources.