Cluster Health Monitor (CHM) is a tool provided by Oracle to automatically collect the usage of the operating system's resources (CPU, memory, SWAP, process, I/O, network, etc.). The CHM collects data once per second. These system resource data are very helpful for diagnosing node restart, hang, instance eviction (eviction), performance problem, etc. of cluster system. In addition, users can use CHM to detect some problems such as high system load, memory anomalies and so on, so as to avoid more serious problems.
the CHM is installed by default in the following versions :
11.2.0.2 and later Oracle Grid Infrastructure for Linux (not including Linux Itanium), Solaris (Sparc 64 and x86-64)
11.2.0.3 and later versions of Oracle Grid Infrastructure for AIX, Windows (not including Windows Itanium).
CHM Service Introduction (The following processes can be viewed using the Ps-ef|grep command):
1. System Monitor Service (Osysmond): This service runs on all nodes, Osysmond sends the resource usage of each node to cluster logger service, which will Databases that are received and saved to the CHM.
2, Cluster Logger Service (ologgerd): In a cluster, Ologgerd will have a host point (master), and a standby node (standby). When Ologgerd fails to start after the current node encounters a problem, it is enabled on the standby node.
we can use the command to view the CHM running state
crsctl stat res -t -init
CHM Repository: Used to store collected data, which, by default, will be present under Grid Infrastructure home, requiring 1 GB of disk space, each of which consumes approximately 0.5GB of space per day. You can use Oclumon to adjust its storage path and the amount of space allowed (up to 3 days of data can be saved).
Simple command Operation :
1. View current directory settings
oclumon manage -get reppath
2. View the current collection size (note units in seconds)
oclumon manage -get repsize
3. Modify the Path
oclumon manage -repo reploc /soft/chm/
4, modify the size
oclumon manage -repos resize 60000
ways to get CHM data :
1. Using grid_home/bin/diagcollection.pl
- First, determine the primary node of the cluster logger service
-
oclumon manage -get master
- Use ROOT to execute the following command on the master node
<grid_home>/bin/diagcollection.pl-collect-chmos-incidenttime inc_time-incidentduration Duration
Incidenttime is the time from which data is obtained, in the form of mm/dd/yyyy24hh:mm:ss, and incidentduration refers to how long it takes to get the start time.
For example:
Diagcollection.pl-collect-crshome/u01/app/11.2.0/grid-chmoshome /u01/app/11.2.0/grid-chmos-incidenttime 06/ 15/201412:30:00-incidentduration 00:05
After running this command, the CHM data is generated in the file chmosData_rac2_20140615_1237.tar.gz.
2. Use Oclumon to obtain CHM data
Oclumon Dumpnodeview[[-Allnodes] |[-n node1 node2] [-< Span class= "PLN" >last "duration" ] | [-s "time_stamp" -e "time_stamp" ] [-v] [-]] [-h
#(-s表示开始时间,-e表示结束时间)
For example:
oclumon dumpnodeview -allnodes -v -s "2012-06-15 07:40:00" -e "2012-06-15 07:57:00" > /tmp/chm1.txt
oclumon dumpnodeview -n node1 node2 -last "12:00:00" >/tmp/chm1.txt
oclumon dumpnodeview -allnodes -last "00:15:00" >/tmp/chm1.txt
Close and open CHM (executed at each node using a grid)
This shuts down the Linux-like service stop, which is automatically turned on after a reboot, and the system IO drops after shutting down
#关闭
crsctl stop res ora.crf -init
#启动
crsctl start res ora.crf -init
Disabling and enabling CHM(similar to chkconfig) using the root user
#禁用
crsctl modify resource ora.crf -attr "AUTO_START=never" -init
#启用
crsctl modify resource ora.crf -attr "AUTO_START=always" -init
refer to Oracle's official documentation :
http://docs.Oracle.com/cd/E11882_01/rac.112/e16794/troubleshoot.htm#CWADD92242
Oracle? Clusterware Administration and Deployment Guide
11g Release 2 (11.2)
Part number E16794-17
My Oracle Support documentation :
Cluster Health Monitor (CHM) FAQ (Doc ID 1328466.1)
CHM and UI:
Http://www.oracle.com/technetwork/database/clustering/downloads/ipd-download-homepage-087212.html
http://blog.csdn.net/mhmds/article/details/72843249
About Oracle Cluster Health Monitor (CHM)