rdbmsmond man page on HP-UX

Man page or keyword search:  
man Server   10987 pages
apropos Keyword Search (all sections)
Output format
HP-UX logo
[printable version]

rdbmsmond(1)							  rdbmsmond(1)

NAME
       rdbmsmond - HA Database MIB Monitor daemon

SYNOPSIS
       hostname] portnumber] timeout] retries] community]

DESCRIPTION
       The daemon is used to monitor the Relational Database Management System
       MIB for the Event Monitoring Service (EMS) using SNMP.  The daemon  can
       monitor either a local or a remote MIB.	includes a resource dictionary
       file which  is  used  by	 the  Event  Monitoring	 Service  to  identify
       resources for monitoring.

   Options
       rdbmsmond recognizes the following command-line options:

	      Write  a	syslog	message every time SNMP is queried for a moni‐
	      tored
			     resource value.

	      Perform SNMP queries against
			     hostname.	By default the local system is queried
			     to get the contents of the MIB.

	      Perform SNMP queries against
			     portnumber.   This option is useful when querying
			     proxy SNMP agents.	 By default SNMP  queries  are
			     directed against the SNMP port (161).

	      Wait	     timeout   seconds	 before	  retransmitting  SNMP
			     requests.	 By  default  5	 seconds  will	expire
			     between retransmissions.

	      Attempt to retransmit SNMP requests
			     retries  number  of  times before considering the
			     host unreachable.	The default is to retransmit 1
			     time.

	      The community string to use with the SNMP requests.  The string
			     "public" is used by default.

	      Turn on internal daemon debugging messages.
			     This  logs	 additional  information  to  the file
			     /var/opt/resmon/log/rdbmsmond.log.	      WARNING:
			     This  file	 grows	without	 bound.	 Only use this
			     option if you really need a trace.

RESOURCES
       The HA Database MIB Monitor monitors the following resources:

   Server Status
       (/rdbms/server/status/<servername>)

       The state of the database server.  Possible values are:

       The server is operational and available for processing requests

       The server is not available for processing requests.

       The server is temporarily unavailable for administrative reasons.

       The server is not accepting requests due to resource limitations.

       The server has been restarted and will be available soon.

   Server Connections
       (/rdbms/server/connects/<servername>)

       The current number of simultaneous connections to the database server.

   Server Uptime
       (/rdbms/server/uptime/<servername>)

       The length of time, in seconds, that the database server has been  run‐
       ning.   A value of zero might indicate that the database server started
       before the database SNMP subAgent.

   Server Started
       (/rdbms/server/started/<servername>)

       The date and time when the database server was  last  started,  in  the
       format YYYY/MM/DD HH:MM:SS.S.

   Server Disk Reads
       (/rdbms/server/disk_reads/<servername>)

       The number of physical reads done by the database server.

   Server Disk Reads Per Second
       (/rdbms/server/disk_reads_per_sec/<servername>)

       The number of physical reads per second done by the database server.

   Server Logical Reads
       (/rdbms/server/logical_reads/<servername>)

       The number of logical reads done by the database server.

   Server Logical Reads Per Second
       (/rdbms/server/logical_reads_per_sec/<servername>)

       The number of logical reads per second done by the database server.

   Server Read Cache Hit Rate
       (/rdbms/server/read_cache_hit_rate/<servername>)

       The  ratio  of logical reads less physical reads to logical reads, done
       by the database server.	This is a measure of the effectiveness of  the
       read  cache.  It is a floating-point number, expressed as a percentage.
       A value of 100 would imply that all reads are from the cache; in	 other
       words,  the  closer  to 100, the better the performance.	 A value of -1
       implies that no logical reads have occurred.

   Server Maximum Allowed Connections
       (/rdbms/server/allowed_max_connects/<servername>)

       The maximum number of simultaneous connections that is allowed  by  the
       database	 server.   This	 value is zero if the number of connections is
       unlimited.

   Server Peak Connections
       (/rdbms/server/peak_connects/<servername>)

       The greatest number of simultaneous connections to the database	server
       since the server started running.

   Server Connection Usage
       (/rdbms/server/usage/<servername>)

       The  percentage	of  maximum allowed connections to the database server
       that is currently active.  This value ranges from -1 to 100.   A	 value
       of  100	means that all available connections are active.  The value is
       -1 if the number of connections is unlimited.

   Server Number of Disk Writes
       (/rdbms/server/disk_writes/<servername>)

       The number of physical disk writes done by the database server.

   Server Writes Per Second
       (/rdbms/server/disk_writes_per_sec/<servername>)

       The number of physical disk writes per  second  done  by	 the  database
       server.

   Server Logical Writes
       (/rdbms/server/logical_writes/<servername>)

       The number of logical writes done by the database server.

   Server Logical Writes Per Second
       (/rdbms/server/logical_writes_per_sec/<servername>)

       The number of logical writes per second done by the database server.

   Server Write Cache Hit Ratio
       (/rdbms/server/write_cache_hit_rate/<servername>)

       The  ratio  of  logical	writes less physical writes to logical writes,
       done by the database server.  This is a measure of the effectiveness of
       the  disk  write	 cache.	 It is a floating-point number, expressed as a
       percentage.  A value of 100 would imply that all writes	are  from  the
       cache;  in  other words, the closer to 100, the better the performance.
       A value of -1 implies that no logical writes have occurred.

   Server Commits
       (/rdbms/server/commits/<servername>)

       The number of transactions completed by the database server.

   Server Commits Per Second
       (/rdbms/server/commits_per_sec/<servername>)

       The number of transactions per second completed by the database server.

   Database Status
       (/rdbms/database/status/<databasename>)

       The state of the database.  Possible values are:

       The database is currently being used by a database server.

       The database is accessible, but it is not currently being
	      used by any database server.

       The database is not accessible to any database servers.

   Database Space Allocated
       (/rdbms/database/allocated/<databasename>)

       The estimated amount of disk space, in  kilobytes,  currently  reserved
       for the database.

   Database Space Used
       (/rdbms/database/used/<databasename>)

       The  estimated  amount  of  disk space, in kilobytes, that is currently
       used in the database.  If this value exceeds the	 space	allocated  for
       the  database,  it  means  that there is no more space available in the
       database.

   Database Space Usage
       (/rdbms/database/usage/<databasename>)

       The percentage of the space allocated that is  currently	 used  in  the
       database.  This value indicates how full the database is and whether it
       is approaching maximum capacity.	 The value ranges from -1 to  100.   A
       value  of  100  indicates  that all of the allocated space is currently
       used.  If the value is -1, it means that no space  has  been  allocated
       for the database.

AUTHOR
       was developed by the Hewlett-Packard Company.

FILES
       Executable.

       Resource dictionary for
			   Describes  the location of various resources in the
			   resource  hierarchy	(e.g.  /system/server/status),
			   and	specifies  the name of the HA Database Monitor
			   executable and its command-line arguments.
       Log file for all monitors using the Event Monitoring Service, including
			   Any errors are written to this file.
       System log file.	 Some errors are written to this file as well as to
			   Also, if the option is specified,  resource	values
			   obtained  by	 the Database Monitor from SNMP agents
			   are written to this file.
       Debug log file.	If the
			   option is specified, internal debug trace  messages
			   are written to this file.

DEPENDENCIES
       must be run by the process of the Event Monitoring Service (EMS).

       The  SNMP  Master  Agent and the appropriate database subAgents must be
       running.	 For more information about these daemons, see	snmpd(1M)  and
       the appropriate documentation for the database that is being monitored.

SEE ALSO
       resls(1), ems(5), diskmond(1M), snmpd(1M), mibmond(1).

								  rdbmsmond(1)
[top]

List of man pages available for HP-UX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net