<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Legacy Export on Oracle Scripts</title><link>https://www.oraclescripts.com/tags/legacy-export/</link><description>Recent content in Legacy Export on Oracle Scripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>OracleScripts.com</copyright><lastBuildDate>Thu, 14 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.oraclescripts.com/tags/legacy-export/index.xml" rel="self" type="application/rss+xml"/><item><title>Oracle Export Through a Named Pipe with mknod for Space-Constrained Hosts</title><link>https://www.oraclescripts.com/post/oracle-export-via-named-pipe-mknod/</link><pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate><guid>https://www.oraclescripts.com/post/oracle-export-via-named-pipe-mknod/</guid><description>
&lt;h2 id="oracle-export-through-a-named-pipe-with-mknod-for-space-constrained-hosts"&gt;Oracle Export Through a Named Pipe with mknod for Space-Constrained Hosts&lt;/h2&gt;
&lt;h2 id="purpose"&gt;Purpose&lt;/h2&gt;
&lt;p&gt;Oracle's original Export utility (&lt;code&gt;exp&lt;/code&gt;) writes a binary dump file. On production hosts where disk space is tight — where staging a full-database dump and its compressed copy simultaneously would exhaust the filesystem — the classic workaround is a named pipe (FIFO). A named pipe looks like a file on the filesystem but has no storage: bytes written to one end are immediately readable from the other. By piping the Export directly through gzip or netcat, the dump never touches disk as an uncompressed file.&lt;/p&gt;</description></item></channel></rss>