<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>OPatch on Oracle Scripts</title><link>https://www.oraclescripts.com/tags/opatch/</link><description>Recent content in OPatch on Oracle Scripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>OracleScripts.com</copyright><lastBuildDate>Wed, 13 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.oraclescripts.com/tags/opatch/index.xml" rel="self" type="application/rss+xml"/><item><title>Unpacking Oracle Patch and Install Media with cpio</title><link>https://www.oraclescripts.com/post/cpio-unzip-oracle-patch-media/</link><pubDate>Wed, 13 May 2026 00:00:00 +0000</pubDate><guid>https://www.oraclescripts.com/post/cpio-unzip-oracle-patch-media/</guid><description>
&lt;h2 id="unpacking-oracle-patch-and-install-media-with-cpio"&gt;Unpacking Oracle Patch and Install Media with cpio&lt;/h2&gt;
&lt;h2 id="purpose"&gt;Purpose&lt;/h2&gt;
&lt;p&gt;Before Oracle began shipping all patches as &lt;code&gt;.zip&lt;/code&gt; files, the standard delivery format for Oracle install media and large patch bundles was &lt;code&gt;cpio&lt;/code&gt; — a tape archive format that predates tar and is still the underlying format used inside every RPM package. DBAs working with Oracle 8i, 9i, and early 10g installations, or with older patch archives from Oracle MetaLink, received media on tape or in &lt;code&gt;.cpio&lt;/code&gt; files and used &lt;code&gt;cpio -idmv&lt;/code&gt; to stage it for installation.&lt;/p&gt;</description></item></channel></rss>