Due to bug 12711827 in 11.2.0.2, huge CHM(Cluster Health Monitor) files can be created in Grid Home. You can apply Patch 10165314 to fix this issue. As quick fix, you can stop the resource ora.crf and cleanup files. You can find files location using below command
[root@devdb-002 devdb-002]# $ORACLE_GRID/bin/oclumon manage -get reppath
CHM Repository Path = /oragrid/product/11.2.0.2/crf/db/devdb-002
Done
e.g List of files on one of my dev box. Notice that crfclust.bdb grew to 96G
[root@devdb-002 devdb-002]# ls -lhtr
total 106G
-rw-r----- 1 root root 8.0K Mar 22 03:01 repdhosts.bdb
-rw-r----- 1 root root 24K Mar 22 03:10 __db.001
-rw-r----- 1 root root 8.0K Mar 22 03:11 crfconn.bdb
-rw-r--r-- 1 root root 115M Jan 20 00:56 devdb-002.ldb
-rw-r----- 1 root root 16M Jan 20 07:02 log.0000064367
-rw-r----- 1 root root 1.2M Jan 20 07:08 __db.005
-rw-r----- 1 root root 56K Jan 20 07:08 __db.006
-rw-r----- 1 root root 2.4G Jan 20 07:08 crfloclts.bdb
-rw-r----- 1 root root 16M Jan 20 07:09 log.0000064368
-rw-r----- 1 root root 2.1M Jan 20 07:09 __db.004
-rw-r----- 1 root root 2.6M Jan 20 07:09 __db.003
-rw-r----- 1 root root 392K Jan 20 07:09 __db.002
-rw-r----- 1 root root 1.5G Jan 20 07:09 crfts.bdb
-rw-r----- 1 root root 2.3G Jan 20 07:09 crfhosts.bdb
-rw-r----- 1 root root 2.0G Jan 20 07:09 crfcpu.bdb
-rw-r----- 1 root root 96G Jan 20 07:09 crfclust.bdb
-rw-r----- 1 root root 2.2G Jan 20 07:09 crfalert.bdb
Stop the resource ora.crf and then cleanup files
[root@devdb-002 devdb-002]# $ORACLE_GRID/bin/crsctl stop res ora.crf -init
CRS-2673: Attempting to stop 'ora.crf' on 'devdb-002'
[root@devdb-002 devdb-002]#rm -f *.bdb
Recent Comments