Re: How to free inodes in Linux without killing processes
- From: Tanel Poder <tanel@xxxxxxxxxx>
- To: Oracle-L Group <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 14 Jul 2010 18:50:32 +0800
Hi,
You can truncate the file using "*> **file.trc" *that has usually worked for
me.
The other option is to delete the file, then connect to the background
process which holds the file descriptor open using oradebug and issue an
ORADEBUG CLOSE_TRACE *however* I wouldn't connect to critical background
processes with oradebug at all, even if you're running simple commands like
close trace.
So, truncating the file is a better option...
--
Tanel Poder
http://blog.tanelpoder.com
http://tech.e2sn.com
On Wed, Jul 14, 2010 at 6:32 PM, amonte <ax.mount@xxxxxxxxx> wrote:
> Hi all
>
> One of databases (10.2.0.4) is filling up it's bdump, cdump and udump
> directories, deleting the files does not free any space because the inode is
> still being hold by many processes.
>
> One way to free the space is killing the processes however pmon, smon are
> holidng the files so killing them instance will sink. I wonder if there is
> any better way to handle this? Or any way to prevent this happening (for
> example instead of deleting echo /dev/null to the file? my experience with
> this is that it does not work)
>
>
> This is Linux x86-64
>
> Alex
>
Other related posts:
