<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Oracle Administration Unix on Oracle Scripts</title><link>https://www.oraclescripts.com/series/oracle-administration-unix/</link><description>Recent content in Oracle Administration Unix on Oracle Scripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>OracleScripts.com</copyright><lastBuildDate>Wed, 29 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.oraclescripts.com/series/oracle-administration-unix/index.xml" rel="self" type="application/rss+xml"/><item><title>Delete the 500 Oldest Files in a Directory (Oracle DBA)</title><link>https://www.oraclescripts.com/post/delete-500-oldest-files-unix-dba/</link><pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.oraclescripts.com/post/delete-500-oldest-files-unix-dba/</guid><description>
&lt;h2 id="delete-the-500-oldest-files-in-a-directory-oracle-dba"&gt;Delete the 500 Oldest Files in a Directory (Oracle DBA)&lt;/h2&gt;
&lt;h2 id="purpose"&gt;Purpose&lt;/h2&gt;
&lt;p&gt;Oracle's diagnostic destination (&lt;code&gt;DIAGNOSTIC_DEST&lt;/code&gt;), audit file destination (&lt;code&gt;AUDIT_FILE_DEST&lt;/code&gt;, also known as &lt;code&gt;adump&lt;/code&gt;), and per-process trace directories collect thousands of small files over time. Inode counts, not bytes, are usually the limit that bites first — many filesystems cap directory entries or per-filesystem inodes well below the disk's byte capacity. The one-liner below — taken straight from the shutdownabort.com DBA Quick Guides (Andrew Barry, 2007–2013, preserved via the Wayback Machine as the anchor source for this post) — deletes the &lt;strong&gt;500 oldest files&lt;/strong&gt; in the current directory in one shot. It is the quickest way to free up enough headroom to keep the database running while a longer-term retention strategy is put in place.&lt;/p&gt;</description></item><item><title>List Files Opened by an Oracle Process with lsof -p</title><link>https://www.oraclescripts.com/post/lsof-find-files-opened-by-process-oracle/</link><pubDate>Tue, 28 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.oraclescripts.com/post/lsof-find-files-opened-by-process-oracle/</guid><description>
&lt;h2 id="list-files-opened-by-an-oracle-process-with-lsof--p"&gt;List Files Opened by an Oracle Process with lsof -p&lt;/h2&gt;
&lt;h2 id="purpose"&gt;Purpose&lt;/h2&gt;
&lt;p&gt;&lt;code&gt;lsof&lt;/code&gt; (LiSt Open Files) is the UNIX tool for inspecting which processes have which files open. For an Oracle DBA it is the fastest answer to four common questions: which datafiles is this server process touching, which trace file is &lt;code&gt;PMON&lt;/code&gt; writing into right now, why is &lt;code&gt;df&lt;/code&gt; reporting more space used than &lt;code&gt;du&lt;/code&gt;, and which library is the database currently mapped against. The one-liner below — taken straight from the shutdownabort.com DBA Quick Guides (Andrew Barry, 2007–2013, preserved via the Wayback Machine as the anchor source for this post) — is the smallest possible invocation: list every file held open by one process, identified by its PID.&lt;/p&gt;</description></item></channel></rss>