[Translated from mos] In 11gR2 rac environment, the file system usage is tight, and lsof shows many oraagent_oracle.l10 (deleted) and 11gr2rac
In 11gR2 rac environment, the file system usage is tight, and lsof shows many oraagent_oracle.l10 (deleted)
Reference Original:
High Space Usage and "lsof" Output Shows comment 'oraagent _ oracle. l10 (deleted) 'in GI environment (Doc ID 1598252.1)
Applicable:
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.
Symptoms:
Using the df command, we can see that the file system usage of GI home is quite high, but the du command does not see any files using all the space.
In this example, df shows that 95% (about 89 GB) is used, but du shows that only 34 GB is used.
The lsof command shows that many oraagent_oracle.l10 files are marked as deleted (---> Note: You can use lsof | grep deleted to locate the files deleted by deleted ), because handle keeps holding these files that have been deleted by deleted, the OS cannot recycle this part of the space.
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)
Cause:
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
Solution:
The bug fix is pinned ded 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