7/3/25, 19:58 Document 430221.
1
Copy right (c) 2025, Oracle. A ll rights reserv ed. Oracle Confidential.
How To Reload Datapump Utility EXPDP/IMPDP (Doc ID 430221.1)
In this Document
Goal
Solution
References
APPLIES TO:
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database - Enterprise Edition - Version [Link] and later
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Information in this document applies to any platform.
GOAL
How to reload DATAPUMP utility? This may be required in different situations, like hanging issues, internal errors, data
dictionary incompatibility, etc, all of them related to initiating phase of DataPump.
SOLUTION
In some cases DataPump utility may get corrupted and we need to recreate DataPump utility to overcome internal
corruption. To do this, run specified scripts for Oracle version that you are running as given below. In a RAC environment,
run the scripts only on one instance.
Note: Run the following as sysdba user:
SQL> connect / as sysdba
For Oracle version 10.1 :
-- 1. [Link] orders the installation of all its components including the Metadata API which was
previously installed separately.
SQL> @$ORACLE_HOME/rdbms/admin/[Link]
-- 2. [Link] will create DBMS procedures for DATAPUMP
SQL> @$ORACLE_HOME/rdbms/admin/[Link]
For Oracle version 10.2:
-- 1. [Link] will Re-Install DataPump types and views
SQL> @$ORACLE_HOME/rdbms/admin/[Link]
[Link] 1/4
7/3/25, 19:58 Document 430221.1
-- Note:
-- If XDB is installed, then it is required to run "[Link]" script also.
-- Use this code to verify if XDB is installed:
SQL> select substr(comp_name,1,30) comp_name,
substr(comp_id,1,10) comp_id,
substr(version,1,12) version,
status
from dba_registry;
-- Sample output if XDB installed,
Oracle XML Database XDB -version- VALID
-- [Link] will re-install tde_library packages
SQL> @$ORACLE_HOME/rdbms/admin/[Link]
-- 3. [Link] will Re-Install DataPump packages
SQL> @$ORACLE_HOME/rdbms/admin/[Link]
-- [Link] will Re-Install DBMS DataPump objects
SQL> @$ORACLE_HOME/rdbms/admin/[Link]
-- 5. To recompile invalid objects, if any
SQL> @$ORACLE_HOME/rdbms/admin/[Link]
For Oracle version 11g and higher prior to 12c:
-- 1. Run catproc script, [Link]
For running [Link], please refer to
Note:863312.1 - Best Practices for running catalog, catproc and utlrp script
NOTE: IMPORTANT!
The catproc script should be run after the database has been
opened with STARTUP UPGRADE.
The catproc script should NOT be run when the database is
opened with unrestricted access. This can cause the database
to experience performance issues, invalid objects and can
even lead to a hanging situation.
[Link] 2/4
7/3/25, 19:58 Document 430221.1
-- [Link] recompile invalid objects, if any
SQL> @$ORACLE_HOME/rdbms/admin/[Link]
Note: For Oracle release [Link], there is no [Link] in $ORACLE_HOME/rdbms/admin.
To reload DataPump in Oracle release [Link], please use the above steps shown for "For Oracle version 11g and
higher prior to 12c".
For Oracle version 12c:
Note 1: Prior rebuilding DP catalog in [Link] CDB , install Patch 25139545 as alerted in Document 2175021.1 - "Alert
- Multitenant Customers: The objects created by the post-install steps of [Link] Generic DataPump Patches Are not
Shared Across All PDBS".
Failure of Datapatch on Multitenant Environment Can Cause DataPump Dictionary Inconsistency in Pluggable
Database (PDB), see Document 2327652.1.
Note 2: For issues regarding KU$ Invalid Objects Owned by SYS after upgrading or applying datapatch, refer to
Document 2289785.1 to rebuild Datapump.
On Multitenant Environment, for Oracle versions 12.1, 12.2, 18c, 19c, 21c, and 23ai:
-- 1. To rebuild the DataPump packages with the following steps.
Under the ORACLE_HOME, execute:
cd rdbms/admin
-- run the [Link] in the CDB with all of the PDBs open
Syntax:
$ORACLE_HOME/perl/bin/perl [Link] -d /u01/oracle -l <logging directory> -b <prefix for logfile
of dpload for each PDB> [Link]
Where:
-l - directory to use for spool log files; for example, /tmp
-b - base name for log and spool file names; for example, dp_rebuild_log_base_name
For example, at OS prompt
cd $ORACLE_HOME/rdbms/admin
$ORACLE_HOME/perl/bin/perl [Link] -d /u01/oracle -l /tmp -b dp_rebuild_log_base_name [Link]
NOTE: After [Link] is run via [Link], to recompile any invalid objects, [Link] can be run
in all containers vi [Link] as well, e.g.
host perl $ORACLE_HOME/rdbms/admin/[Link] -n 1 -l /path_for_logs -b name_for_logs
$ORACLE_HOME/rdbms/admin/[Link];
This command can be run several times to compile objects which did not get processed during the
first run.
[Link] 3/4
7/3/25, 19:58 Document 430221.1
Also, if there are Data Pump components that are still invalid in any one container, [Link] can
be run individually in that container, e.g.
connect / as sysdba
alter session set container = <PDB_NAME>
@[Link]
On Non-Multitenant Environment, for Oracle version 12c and higher:
-- 1. Rebuild the DataPump packages with the following steps.
Under the ORACLE_HOME, execute:
cd rdbms/admin
-- run SQL*Plus as sysdba
@[Link]
-- 2. To recompile invalid objects, if any
SQL> @$ORACLE_HOME/rdbms/admin/[Link]
Additional Resources
Community: Database Utilities
Still have questions? Use the above community to search for similar discussions or start a new discussion on this subject.
REFERENCES
NOTE:863312.1 - Best Practices for running catalog, catproc and utlrp script
NOTE:1932340.1 - 12c:How to execute preupgrade script [Link] in Multitenant environment ?
NOTE:1641557.1 - Script To Verify The DataPump Catalog
NOTE:2289785.1 - KU$ Invalid Objects Owned by SYS after Applying April 2017 Critical Patch Update
NOTE:2175021.1 - Alert - Multitenant Customers: The objects created by the post-install steps of [Link] Generic
DataPump Patches Are not Shared Across All PDBS
Didn't find what you are looking for?
[Link] 4/4
