Acknowledging the DB2ServerOK alarm

Use this task to take the DB2ServerOK parameter out of an alarm state and to reset it to a normal state. The alarm indicates that the DB2 server has been stopped. Taking this action does not bring the DB2 server back online. If you have not configured the PATROL KM to restart the server automatically when this parameter goes into an alarm state, you have to bring the server back online manually.

Also, if the KM fails to restart the server, the DB2ServerOK parameter goes to an alarm state and you will have to take further action to restart the server.

1. Right-click on the icon labeled Parameters in the DB2 instance icon container window.
2. From the menu, select Acknowledge DB2ServerOK Alarm.
   • For the DB2 UDB EE component, the DB2ServerOK parameter stops blinking. Steps 3 and 4 do not apply to the DB2 UDB EE component.
   • For the DB2 UDB EEE component, the Acknowledge DB2ServerOK dialog box appears. Complete Steps 3 and 4.
3. Select one of the following options to indicate on which node you want to acknowledge the alarm:
   • Acknowledge DB2ServerOK on current mode in ALARM state acknowledges the alarm on the current node. The DB2ServerOK parameter on the current node will stop blinking.
   • Acknowledge DB2ServerOK on all nodes in ALARM state acknowledges the alarms on all nodes. All DB2ServerOK parameters on all nodes in an alarm state will stop blinking.

4. Click OK.

   Note

   If the DB2ServerOK parameter is in an alarm state and you have the Restart Server option configured, ensure that the server has restarted. Then, reset the alarm.

Where to go from here

For more information about the DB2ServerOK parameter and alarm, see the following sections:The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.