Details:
|
Problem:
|
The Home directory of User grid become huge
|
|
Path:
|
/app/oracle/11.2.0.4/grid/crf/db/db-node01
|
|
Key Word:
|
CRF --> CHM(Cluster Health Monitor)
|
|
Files:
|
one *.bdb(crfclust.bdb) file's size seems to be more than 88GB.
|
Reason:
I found that it seems like bug 12711827.
You can apply Patch 10165314 to fix this issue Or NOT.
As quick fix, you can Clear them manual.
Resolution:
Plan A: Clear it manual.
grid@db-node01:~$ crsctl stat res -init -t
|
-
--------------------------------------------------------------------------------
-
NAME TARGET STATE SERVER STATE_DETAILS
-
--------------------------------------------------------------------------------
-
Cluster Resources
-
--------------------------------------------------------------------------------
-
ora.asm
-
1 ONLINE ONLINE db-node01 Started
-
ora.cluster_interconnect.haip
-
1 ONLINE ONLINE db-node01
-
ora.crf
-
1 ONLINE ONLINE db-node01
-
ora.crsd
-
1 ONLINE ONLINE db-node01
-
ora.cssd
-
1 ONLINE ONLINE db-node01
-
ora.cssdmonitor
-
1 ONLINE ONLINE db-node01
-
ora.ctssd
-
1 ONLINE ONLINE db-node01 OBSERVER
-
ora.diskmon
-
1 OFFLINE OFFLINE
-
ora.drivers.acfs
-
1 ONLINE ONLINE db-node01
-
ora.evmd
-
1 ONLINE ONLINE db-node01
-
ora.gipcd
-
1 ONLINE ONLINE db-node01
-
ora.gpnpd
-
1 ONLINE ONLINE db-node01
-
ora.mdnsd
-
1 ONLINE ONLINE db-node01
-
---------------------------------------------------------------------------------
grid@db-node01:~$ crsctl stop res ora.crf -init
|
grid@db-node01:~$ crsctl stat res ora.crf -init -t
|
grid@db-node01:~$ oclumon manage -get reppath
|
-
-
CHM Repository Path = /app/oracle/11.2.0.4/grid/crf/db/db-node01
-
-
Done
|
root@db-node01:~# cd /app/oracle/11.2.0.4/grid/crf/db/db-node01
|
|
root@db-node01:/app/oracle/11.2.0.4/grid/crf/db/db-node01# rm -f *.bdb
|
|
grid@db-node01:~$ crsctl start res ora.crf -init
|
grid@db-node01:~$ crsctl stat res ora.crf -init -t
|
Plan B: Maybe, we can clear it automatically.
db-node01:/app/oracle/11.2.0.4/grid/crf/db/db-node01$ oclumon manage -get repsize
|
-
-
CHM Repository Size = 1931492640 // It is the default value, Maybe this is the bug maker. It's a time(second).
-
// This 'Size' is not about the *.bdb files' size, It's how often (s) to resize.
-
Done
grid@db-node01:/app/oracle/11.2.0.4/grid/crf/db/db-node01$ oclumon manage -repos resize 172800
|
|
// 2 days * 24 hours * 60 minutes * 60 seconds
|
-
db-node01 --> retention check successful
-
db-node02 --> retention check successful
-
New retention is 172800 and will use 3719208960 bytes of disk space
-
-
CRS-9115-Cluster Health Monitor repository size change completed on all nodes.
-
-
Done
grid@db-node01:/app/oracle/11.2.0.4/grid/crf/db/db-node01$ oclumon manage -get repsize
|
-
-
CHM Repository Size = 172800
-
-
Done
Now what?
Wait, for 2 days!
If Plan B really works, you won't have to apply the patch!
Moitoring Plan:
repsize_mon.sh:
#!/usr/bin/sh
echo `date -u "%Y%m%d"`' | '`/usr/bin/du -sk /app/oracle/11.2.0.4/grid/crf/db/db-xxx01`
crontab -l:
# Monitoring the bdb directory.
0 22 * * * /usr/bin/sh /home/oracle/cjs/repsize_mon.sh >> /home/oracle/cjs/bdb_dsk_usage.txt 2>&1
After check the bdb_dsk_usage.txt at one month later, I found the resize is always between 600M to 630M.
It really means that Plan B did works!!!
来自 “ ITPUB博客 ” ，链接：https://blog.itpub.net/25521690/viewspace-2122284/
，如需转载，请注明出处，否则将追究法律责任。
