SiteScope User's Guide
DB2 Monitor
The SiteScope DB2 Monitor allows you to monitor the availability and performance statistics of an IBM DB2 database. The error and warning thresholds for the monitor can be set on as many as ten DB2 server performance statistics.
Usage Guidelines
The DB2 Monitor allows you to monitor DB2 servers for availability and proper function. You can monitor multiple parameters or counters with a single monitor instance. This allows you to watch server loading for performance, availability, and capacity planning. Create a separate DB2 Monitor instance for each IBM DB2 server in your environment.
The following are several key requirements for using the DB2 Monitor:
- The DB2 client files and libraries must be copied to the machine where SiteScope is running. The DB2 client Control Center must be installed on the SiteScope server.
- In the DB2 Control Center console, the system you want to monitor must be added to the Systems list. In Add System dialog box, enter the information required:
- System Name: <db2_server_name>
- Remote Instance:DB2
- Host Name: <db2_server_name>
- Service Name: <db2_server_port> (the default is port 50000)
Click Retrieve and then click OK.
- A remote DB2 instance needs to be added to the <db2_server_name> node in the Control Center Console. Select the <db2_server_name> node and select to add and Instance. Enter the information required in the dialog box:
- Remote Instance: DB2
- Instance Name:<database_name_used_for_DB2_monitor>
- Host Name: <db2_server_name>
- Service Name: <db2_server_port> (the default is port 50000)
Then click OK.
The default run schedule for this monitor is every 10 minutes, but you can change it to run more or less often using the Update every setting.
Completing the DB2 Monitor Form
To display the DB2 Monitor Form, either click the Edit link for an existing DB2 Monitor in a monitor table, or click the Add a new Monitor to this Group link on a group's detail page and choose the Add DB2 Monitor link.
Complete the items on the DB2 Monitor form as follows. When the required items are complete, click the Add Monitor button.
- Server
- Choose the server you want to monitor. Use the choose server link to view the server selection screen. or to enter a path name to a server. The server selection screen presents the following options:
- Server:
- Username: Enter the DB2 database username for the DB2 server. This is usually a DB2 administrator username.
- Password: Enter the password for the user specified above.
- Instance: Enter the DB2 database instance name that you want to monitor. For example, DB2 is a default instance created by DB2 installation.
- Counters
- Choose the server performance parameters or counters you want to check with this monitor. The table list to the right of this item displays those currently selected for this monitor. Use the choose counters link to bring up the counters selection screen. check or clear the check boxes on the choose counters screen to select between one to ten counters to monitor on this server. The performance parameters or counters available for the DB2 Monitor are included in the table at the bottom of this page
- Update every
- Enter how frequently the monitor should check the Database server. The drop-down list to the right of the text box lets you specify time increments of seconds, minutes, hours, or days. You must specify a time increment of at least 15 seconds.
- Title (Optional)
- Enter a name for this monitor. This name appears in the Name text box on the monitor table when you open the group's detail page. If you don't enter a name, a default name will be created.
Advanced Options
The advanced options give you the ability to customize error and warning thresholds. If you choose not to set them, SiteScope will use preset defaults if available. If a default is not available, SiteScope will not be able to utilize the condition.
- Disable
- Check this box to temporarily disable this monitor and any associated alerts. To
enable the monitor again, clear the box.
- Verify Error
- Check this box if you want SiteScope to automatically run this monitor again if it detects an error. When an error is detected, the monitor will immediately be scheduled to run again once.
Note: In order to change the run frequency of this monitor when an error is detected, use the Update every (on errors) option below.
Note: The status returned by the Verify Error run of the monitor will replace the status of the originally scheduled run that detected an error. This may cause the loss of important performance data if the data from the verify run is different than the initial error status.
Warning: Use of this option across many monitor instances may result in significant monitoring delays in the case that multiple monitors are rescheduled to verify errors at the same time.
- Update Every (on error)
- This options allows you to set a new monitoring interval for monitors that have registered an error condition. For example, you may want SiteScope to monitor this item every 10 minutes normally, but as often as every 2 minutes if an error has been detected. Note that this increased scheduling will also affect the number of alerts generated by this monitor.
- Schedule (Optional)
- By default, SiteScope's monitors are enabled every day of the week. You may, however, schedule your monitors to run only on certain days or on a fixed schedule. Choose the Edit schedule link to create or edit a monitor schedule. For information about creating schedules, read these instructions.
- Monitor Description (Optional)
- Enter any additional information to describe this monitor. The Monitor Description can include HTML tags such as the <BR> <HR>, and <B> tags to control display format and style. The description will appear on the Monitor Detail page.
- Report Description (Optional)
- Enter a description for the report for this monitor that will make it easier to understand what this monitor does. The description will appear on Management Reports and on the info list for the monitor.
- Depends On (Optional)
- To make the running of this monitor dependent on the status of another monitor or monitor group, use the drop-down list to select the monitor or group on which this monitor is dependent. Select None to remove any dependency.
- Depends Condition (Optional)
- If you choose to make the running of this monitor dependent on the status of another monitor, choose the status condition that the other monitor or monitor group should have in order for the current monitor to run normally. The current monitor will be run normally as long as the monitor or group on which it depends reports the condition selected in this option.
- List Order (Optional)
- By default, new monitors are listed last on the Monitor Detail page. You may use the drop-down list to choose a different placement for this monitor.
Setting Monitor Status Thresholds
SiteScope Application Monitors allow you to set multiple threshold conditions to determine the status reported by each monitor. The individual conditions are combined as logical OR relationships so that when one or more of the conditions (for example any of the conditions for Error if) are met the monitor status is set to the applicable condition. If multiple conditions are met for more than one status condition (such as conditions for both error and for warning), the status for the monitor is set to the highest valued condition. Thus a match of an error condition and a warning condition would be reported as an error status, error being the highest value, warning the next highest and good the lowest value.
- Error if
-
Use one or more of the selection boxes in this item to define one or more error conditions for this monitor. Use the drop-down lists in these items to change error threshold(s) relative to the counters you have selected to check with this monitor.
After choosing a counter or parameter, use the comparison operator drop-down list to specify an error threshold such as: >= (greater than or equal to), != (not equal to), or < (less than) and enter a comparison value in the box provided. Comparison values should be entered as whole numbers.
- Warning if
- Use one or more of the selection boxes in this item to define one or more warning conditions for this monitor. Use the drop-down lists in these items to change warning threshold(s) relative to the counters you have selected to check with this monitor. Set these value relative to those you set for the error threshold in the Error if item.
- Good if
- You can set this monitor to return a good status for certain conditions. You may define those conditions here. Complete this item as you would for the Error if and Warning if items.
Counters available for the DB2 Monitor
| direct_write_reqs | pool_index_writes |
| rem_cons_in | direct_read_time | pool_read_time |
| rem_cons_in_exec | direct_write_time | prefetch_wait_time |
| local_cons | cat_cache_lookups | pool_data_to_estore |
| local_cons_in_exec | cat_cache_inserts | pool_index_to_estore |
| con_local_dbases | cat_cache_overflows | pool_data_from_estore |
| agents_registered | cat_cache_heap_full | pool_index_from_estore |
| agents_waiting_on_token | pkg_cache_lookups | direct_reads |
| idle_agents | pkg_cache_inserts | direct_writes |
| agents_from_pool | pkg_cache_num_overflows | direct_read_reqs |
| agents_created_empty_pool | appl_section_lookups | direct_write_reqs |
| agents_stolen | appl_section_inserts | direct_read_time |
| comm_private_mem | sec_logs_allocated | direct_write_time |
| inactive_gw_agents | log_reads | cat_cache_lookups |
| num_gw_conn_switches | log_writes | cat_cache_inserts |
| sort_heap_allocated | total_log_used | cat_cache_overflows |
| post_threshold_sorts | locks_held | cat_cache_heap_full |
| piped_sorts_requested | lock_list_in_use | pkg_cache_lookups |
| piped_sorts_accepted | deadlocks | pkg_cache_inserts |
| appls_cur_cons | lock_escals | appl_section_lookups |
| appls_in_db2 | x_lock_escals | appl_section_inserts |
| total_sec_cons | lock_timeouts | uow_log_space_used |
| num_assoc_agents | lock_waits | locks_held |
| sort_heap_allocated | lock_wait_time | deadlocks |
| total_sorts | locks_waiting | lock_escals |
| total_sort_time | rows_deleted | x_lock_escals |
| sort_overflows | rows_inserted | lock_timeouts |
| active_sorts | rows_updated | lock_waits |
| total_hash_joins | rows_selected | lock_wait_time |
| total_hash_loops | int_rows_deleted | locks_waiting |
| hash_join_overflows | int_rows_updated | uow_lock_wait_time |
| hash_join_small_overflows | int_rows_inserted | rows_deleted |
| pool_data_l_reads | static_sql_stmts | rows_inserted |
| pool_data_p_reads | dynamic_sql_stmts | rows_updated |
| pool_data_writes | failed_sql_stmts | rows_selected |
| pool_index_l_reads | commit_sql_stmts | rows_written |
| pool_index_p_reads | rollback_sql_stmts | rows_read |
| pool_index_writes | select_sql_stmts | int_rows_deleted |
| pool_read_time | uid_sql_stmts | int_rows_updated |
| pool_write_time | ddl_sql_stmts | int_rows_inserted |
| files_closed | int_auto_rebinds | open_rem_curs |
| pool_async_data_reads | int_commits | open_rem_curs_blk |
| pool_async_data_writes | int_rollbacks | rej_curs_blk |
| pool_async_index_writes | int_deadlock_rollbacks | acc_curs_blk |
| pool_async_index_reads | binds_precompiles | open_loc_curs |
| pool_async_read_time | agents_stolen | open_loc_curs_blk |
| pool_async_write_time | num_assoc_agents | static_sql_stmts |
| pool_async_data_read_reqs | total_sorts | dynamic_sql_stmts |
| pool_lsn_gap_clns | total_sort_time | failed_sql_stmts |
| pool_drty_pg_steal_clns | sort_overflows | commit_sql_stmts |
| pool_drty_pg_thrsh_clns | total_hash_joins | rollback_sql_stmts |
| prefetch_wait_time | total_hash_loops | select_sql_stmts |
| pool_data_to_estore | hash_join_overflows | uid_sql_stmts |
| pool_index_to_estore | hash_join_small_overflows | ddl_sql_stmts |
| pool_data_from_estore | pool_data_l_reads | int_auto_rebinds |
| pool_index_from_estore | pool_data_p_reads | int_commits |
| direct_reads | pool_data_writes | int_rollbacks |
| direct_writes | pool_index_l_reads | int_deadlock_rollbacks |
| direct_read_reqs | pool_index_p_reads | binds_precompiles |
Copyright © 2003 Mercury Interactive Corporation.
All rights reserved.
