Bug 20186278 - crfclust.bdb Becomes Huge Size Due to Sudden Retention Change (文档 ID 20186278.8)

Bug 20186278  crfclust.bdb Becomes Huge Size Due to Sudden Retention Change

Bug 20186278 - crfclust.bdb Becomes Huge Size Due to Sudden Retention Change (文档 ID 20186278.8)
 The content was last updated on: 17-FEB-2019
 Click here for details of each of the sections below.

Affects:

Product (Component)	Oracle Server (PCW)
Range of versions believed to be affected	Versions BELOW 12.2
Versions confirmed as being affected	11.2.0.4 11.2.0.3
Platforms affected	Generic (all / most platforms affected)

Fixed:

The fix for 20186278 is first included in

12.2.0.1 (Base Release) 12.1.0.2.4 (Jul 2015) Grid Infrastructure Patch Set Update (GI PSU) 11.2.0.4.7 (Jul 2015) Grid Infrastructure Patch Set Update (GI PSU) 12.1.0.2 Patch 7 on Windows Platforms 11.2.0.4 Patch 17 on Windows Platforms

Interim patches may be available for earlier versions - click here to check.

Symptoms:	Related To:
Storage Space Usage Affected	Cluster Ready Services / Parallel Server Management

Description

BDB retension time suddenly change to 1094795585 or some other huge value.
This may cause crfclust.bdb file to grow in size, as crflogd tries to keep 
data for longer retention. 
 
Rediscovery Notes
 
When hitting this problem, crflogd.log may show the retention size being 
suddenly updated to a large size. 
 
 ------------------------------------------------------------------
 2014-02-03 15:36:29.799: [ CRFLOGD][2363541248]updateDBRetention: new retention is 1094795585 seconds and 4702111234474983745 bytes
 ------------------------------------------------------------------
 
Current retention value may be checked with following command. 
If the retention value (unit: seconds) shows a large value like 
1094795585, you are likely to have hit this problem.
 
 $ oclumon manage -get repsize
 CHM Repository Size = 1094795585
 
Workaround
 
Modify BDBSIZE parameter in config file crf<hostname>.ora to 
adequately lower value. To do so, follow these steps:
 
1. Issue "$GI_HOME/bin/crsctl stop res ora.crf -init " on all the nodes of cluster.
2. Locate the config file $GRID_HOME/crf/admin/crf<hostname>.ora
3. Manually edit the crf<hostname>.ora file on every node of the cluster and
   change BDBSIZE tag entry and remove the value (set it to blank) or 
   set it to a desired value, eg. 61511. Do not delete the BDBSIZE tag itself.
4. Restart ora.crf daemon on every node.
 

 

Please note: The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. For questions about this bug please consult Oracle Support.

 

References

Bug:20186278 (This link will only work for PUBLISHED bugs)
Note:245840.1 Information on the sections in this article

---

---

REFERENCES

BUG:20186278 - TAG OCR: GET ID FAILED AND CHM DB SIZE 24 GB

 

建议关闭该功能，步骤供参考：

 

1 2 3 4

crsctl modify resource ora.crf -attr "auto_start=never" -init crsctl stop res ora.crf -init rm -rf *.bdb crsctl start res ora.crf -init