https://www.oraclescripts.com/series/oracle-backup-datapump/Recent content in Oracle Backup Datapump on Oracle ScriptsHugo -- gohugo.ioenOracleScripts.comSun, 12 Apr 2026 00:00:00 +0000https://www.oraclescripts.com/post/oracle-create-directory-command-explained/Sun, 12 Apr 2026 00:00:00 +0000https://www.oraclescripts.com/post/oracle-create-directory-command-explained/ <h2 id="oracle-create-directory-command-explained">Oracle CREATE DIRECTORY Command Explained</h2> <p>The Oracle <code>CREATE DIRECTORY</code> command creates a <strong>directory object</strong> — a logical alias inside the Oracle database that points to a real folder on the server's file system. This is one of the most used setup steps for Oracle Data Pump exports and imports, UTL_FILE file operations, BFILEs, and external tables.</p> <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1012089347386563" crossorigin="anonymous"></script> <ins class="adsbygoogle" style="display:block" data-ad-client="ca-pub-1012089347386563" data-ad-slot="5317081938" data-ad-format="auto" data-full-width-responsive="true"></ins> <script> (adsbygoogle = window.adsbygoogle || []).push({}); </script> <h2 id="what-is-an-oracle-directory-object">What Is an Oracle Directory Object?</h2> <p>A directory object does <strong>not</strong> create a real folder on the operating system. It only creates a pointer — or alias — inside Oracle that maps a name you choose to a physical path on the database server. This keeps your PL/SQL code and Data Pump jobs clean because you use the Oracle directory name instead of hard-coding full OS paths in your scripts.</p>https://www.oraclescripts.com/post/oracle-data-pump-create-the-data-pump-dir-directory/Sat, 11 Apr 2026 00:00:00 +0000https://www.oraclescripts.com/post/oracle-data-pump-create-the-data-pump-dir-directory/ <h2 id="oracle-data-pump-create-the-data_pump_dir-directory">Oracle Data Pump: Create the DATA_PUMP_DIR Directory</h2> <p>Before you can run any Oracle Data Pump export (<code>expdp</code>) or import (<code>impdp</code>) job, Oracle needs to know where to write and read dump files and log files on the server. You do this by creating a <strong>directory object</strong> inside the database that points to a real folder on the operating system. <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1012089347386563" crossorigin="anonymous"></script> <ins class="adsbygoogle" style="display:block" data-ad-client="ca-pub-1012089347386563" data-ad-slot="5317081938" data-ad-format="auto" data-full-width-responsive="true"></ins> <script> (adsbygoogle = window.adsbygoogle || []).push({}); </script> </p> <h2 id="what-this-script-does">What This Script Does</h2> <p>This one-line SQL command creates a database directory object named <code>DATA_PUMP_DIR</code> that maps to the physical path <code>/u01/ora_backup/datapump</code> on the server. Once created, Oracle Data Pump jobs can use this directory to store export dump files and log files.</p>https://www.oraclescripts.com/post/oracle-data-pump-export-schema-expdp-command-guide/Fri, 10 Apr 2026 00:00:00 +0000https://www.oraclescripts.com/post/oracle-data-pump-export-schema-expdp-command-guide/ <h2 id="oracle-data-pump-export-schema-with-expdp-command-guide">Oracle Data Pump Export Schema with expdp Command Guide</h2> <p>Oracle Data Pump's <code>expdp</code> utility lets you take a fast, flexible logical backup of any schema in your Oracle database. This post breaks down a simple schema-level export command, explains each parameter, and shows you how to run it safely. <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1012089347386563" crossorigin="anonymous"></script> <ins class="adsbygoogle" style="display:block" data-ad-client="ca-pub-1012089347386563" data-ad-slot="5317081938" data-ad-format="auto" data-full-width-responsive="true"></ins> <script> (adsbygoogle = window.adsbygoogle || []).push({}); </script> </p> <h2 id="what-this-command-does">What This Command Does</h2> <p>The command below exports all objects and data from the <code>andy</code> schema into a binary dump file stored in an Oracle directory object called <code>my_dir</code>.</p>https://www.oraclescripts.com/post/oracle-expdp-schema-export-data-pump/Thu, 09 Apr 2026 00:00:00 +0000https://www.oraclescripts.com/post/oracle-expdp-schema-export-data-pump/ <h2 id="oracle-expdp-schema-export-using-data-pump">Oracle expdp Schema Export Using Data Pump</h2> <p>Oracle Data Pump's <code>expdp</code> utility lets you export a full database schema — including tables, indexes, constraints, and data — into a portable dump file. This guide breaks down the single-line command that does exactly that for the <code>andy</code> schema. <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1012089347386563" crossorigin="anonymous"></script> <ins class="adsbygoogle" style="display:block" data-ad-client="ca-pub-1012089347386563" data-ad-slot="5317081938" data-ad-format="auto" data-full-width-responsive="true"></ins> <script> (adsbygoogle = window.adsbygoogle || []).push({}); </script> </p> <h2 id="purpose-of-this-command">Purpose of This Command</h2> <p>The goal of this command is to create a <strong>logical backup</strong> of a single Oracle database schema called <code>andy</code>. The export produces a binary dump file (<code>andy.dp</code>) saved to a pre-defined Oracle directory object (<code>my_dir</code>) on the server. This backup can later be imported into the same or a different Oracle database using <code>impdp</code>.</p>