ホームページ >データベース >mysql チュートリアル >【翻译自mos文章】在11gR2 rac环境中,文件系统使用率紧张,并且
在11gR2 rac环境中,文件系统使用率紧张,并且lsof显示有很多oraagent_oracle.l10 (deleted) 参考原文: High Space Usage and lsof Output Shows Many 'oraagent_oracle.l10 (deleted)' in GI environment (Doc ID 1598252.1) 适用于: Oracle Database - E
在11gR2 rac环境中,文件系统使用率紧张,并且lsof显示有很多oraagent_oracle.l10 (deleted)
参考原文:
High Space Usage and "lsof" Output Shows Many 'oraagent_oracle.l10 (deleted)' in GI environment (Doc ID 1598252.1)
适用于:
Oracle Database - Enterprise Edition - Version 11.2.0.3 to 12.1.0.1 [Release 11.2 to 12.1]
Information in this document applies to any platform.
症状:
使用df命令可以看到,GI home的文件系统使用率相当高,但是du命令却看不到有文件正在使用全部的空间。
在这个例子中,df 显示已经使用95%(约89GB),但是du却显示只有34GB
lsof 命令显示有很多oraagent_oracle.l10 文件被标记为deleted(--->注意:使用lsof | grep deleted 就可以定位被deleted掉的文件),因为handle 一直在持有这些被deleted掉的文件,因此os不能回收这部分空间。
oracle 121508 oracle 5w REG 253,3 10564931 6178664 /u01/app/11.2.0.3/grid/log/dm01db01/agent/crsd/oraagent_oracle/oraagent_oracle.l10 (deleted) oracle 121510 oracle 5w REG 253,3 10564931 6178664 /u01/app/11.2.0.3/grid/log/dm01db01/agent/crsd/oraagent_oracle/oraagent_oracle.l10 (deleted)
原因:
This is due to bug 17305100
While database was started by oraagent, the database processes inherit open file handles from the oraagent, but when the oraagent_oracle.l10 was deleted as expected with the normal GI log file rotation policy, those handles are not closed by the database processes
Duplicates: bug 14062031 bug 17034444
解决方案:
The bug fix is included in 11.2.0.3 GI PSU9, 11.2.0.4 GI PSU1. For 12c, at the time of this writing, the issue is still being worked via bug 17387523
The workaround is to restart database or GI