Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
Using High Availability Monitors > Chapter 3 Monitoring Database Resources

Creating Database Monitoring Requests

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

You can create monitor requests for each database that the database server supports. What specific values you use depends on your system's configuration and available resources. For example, you may monitor database server status or database status to reflect the health of your system. The example values in Table 3-6 “Sample Database Monitor Requests” and Table 3-7 “Sample Server Monitor Requests” assume optimum system conditions and represent sample monitor request values.

Table 3-6 Sample Database Monitor Requests

Resources to monitorMonitoring Parameters
NotifyValueOption
statuswhen value is =UNAVAILABLEINITIAL
allocatedwhen value changesn/an/a
usedwhen value is >=some number of kilobytes less than the allocated valueINITIAL
usage1when value is>80REPEAT

 

  1. Indicates database is approaching capacity.

Table 3-7 Sample Server Monitor Requests

Resources to monitorMonitoring Parameters
NotifyValueOption
statuswhen value is not equalUPINITIAL
allowed_
max_
connects
when value changesn/an/a
commitsat each intervaln/an/a
commits_
per_sec
when value is>some number depending on your expectation of database usageINITIAL
connectswhen value is>=some number less than the allowed_max_
connects
value
INITIAL

disk_reads

at each intervaln/an/a

disk_reads_per_sec

when value is

>some number depending on your expectation of database usage

INITIAL

disk_
writes
at each intervaln/an/a
disk_
writes_
per_sec

when value is

>some number depending on your expectation of database usage

INITIAL

logical_
reads
at each intervaln/an/a
logical_
reads_per_sec

when value is

>some number depending on your expectation of database usage

INITIAL

logical_
writes
at each intervaln/an/a
logical_
writes_
per_sec

when value is

>some number depending on your expectation of database usage

INITIAL

peak_
connects
1
at each intervaln/an/a

read_cache_hit_rate

when value is

<80

INITIAL

startedwhen value changesn/an/a
uptimeat each intervaln/an/a
usage1when value is>80INITIAL

write_cache_hit_rate

when value is

<80

INITIAL

 

  1. If it keeps increasing over time, this could be an indication that a configuration parameter needs to be increased.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 1997, 2003 Hewlett-Packard Development Company, L.P.