Getting Started with IBM Data Studio for DB2

156 Getting Started with IBM Data Studio for DB2
3. Highlight the Database Availability row and click Edit.
4. Ensure that the Enabled option is selected.
5. In the Critical section, deselect the Quiesced option.
6. In the Warning section, select the Quiesced option.
7. Click OK.
After the monitoring refresh occurs on the Health Summary page, you will see the Data
Server Status change from Critical (Red) to Warning (Yellow). The Warning Count should
now be raised by 1. Do not be alarmed if the Critical Count is still showing 1. The counts
are a cumulative (summary) history of how many alerts have occurred within the past xx
minutes. If you select the critical alert, you will also see that there is now an end time for it,
meaning that the alert has closed. The start-end time duration is the time during which this
problem was present.
Finally, follow these steps to un-quiesce the database:
1. Open a DB2 command window.
2. Connect to the database with the following command:
db2 connect to GSDB
3. Unquiesce the database with the following command:
db2 unquiesce db
After the monitoring refresh occurs on the Health Summary page, you should see the Data
Server Status change from Warning (yellow) back to Normal (green). The previous warning
alert should also end. After the situation has returned to normal, you can still determine that
the database was quiesced because this information is reflected in the summary counts, as
well as in the Alert List page for that time duration.
4.10.5 Connections
The Connections Alert warns you when there are too many connections to a database at
the same time. By default, the Connections Alert is turned off, but preset to generate a
warning alert if the number of connections detected is greater than or equal to 100, and a
critical alert if greater than or equal to 150. Typically, you need to decide what number
constitutes a critical level, and what constitutes a warning level. What may be a perfectly
reasonable limit for one database may not be so for another database.
For this exercise, follow these steps to lower the thresholds for the alert, so you don't have
to create over 100 connections to trigger the alert:
1. Navigate to the Health Alerts Configuration page.
2. Select the database that you want to use for this scenario.
3. Highlight the Connections row and click Edit.
4. Select the Enabled option if it is not already selected.