ORA-39213: Metadata Processing is not Available – Complete Oracle Data Pump Troubleshooting Guide

📅 Last Updated: August 2026

This guide has been completely updated for Oracle Database 11g, 12c, 18c, 19c, 21c, and Oracle Database 23ai. It explains how to diagnose and resolve ORA-39213: Metadata Processing is not Available, understand the Oracle Data Pump Metadata API, reload XSL stylesheets, validate database components, and restore Data Pump functionality using Oracle Database administration best practices.

Oracle Data Pump is the recommended utility for high-speed logical backup, migration, upgrade, and data movement in Oracle Database environments. Database administrators rely on EXPDP and IMPDP to export and import schemas, tablespaces, databases, transportable tablespaces, and metadata.

One of the less common but critical Data Pump errors is ORA-39213: Metadata Processing is not Available. This error indicates that Oracle Data Pump cannot access the Metadata API required to process database object definitions during export or import operations.

In most environments, the issue occurs because the Oracle Metadata API cannot locate or use the required XSL stylesheets. Invalid Oracle components, incomplete upgrades, failed patching, or corrupted metadata objects may also cause this error.

This guide explains the Oracle Data Pump architecture, Metadata API, common causes of ORA-39213, diagnostic procedures, production-tested solutions, and Oracle DBA best practices.

Quick Solution

Reload the Oracle Metadata API XSL stylesheets by executing DBMS_METADATA_UTIL.LOAD_STYLESHEETS, verify that Oracle XML DB and related components are valid, confirm the status of the Metadata API packages, and rerun the Data Pump export or import operation.

What is ORA-39213?

ORA-39213 is an Oracle Data Pump error indicating that metadata processing is unavailable. Oracle Data Pump depends on the Metadata API to extract, transform, and recreate database object definitions such as tables, indexes, constraints, users, roles, PL/SQL objects, and grants.

If the Metadata API cannot initialize correctly, Data Pump cannot process object definitions and terminates the export or import operation.

Complete Error Message

ORA-39213:
Metadata processing is not available.

This error is frequently accompanied by additional Data Pump or Metadata API errors that provide more information about the underlying problem.

Symptoms

One or more of the following symptoms may occur:

EXPDP fails immediately after starting.
IMPDP terminates before importing metadata.
Metadata-only exports fail.
Schema export cannot begin.
Database export terminates unexpectedly.
Data Pump jobs stop with ORA-39213.
Metadata API packages generate additional errors.

Oracle Data Pump Architecture

EXPDP / IMPDP

        │

        ▼

Oracle Data Pump Engine

        │

        ▼

Metadata API

        │

        ▼

XSL Stylesheets

        │

        ▼

Oracle Dictionary

        │

        ▼

Database Objects

Oracle Data Pump communicates with the Metadata API to retrieve object definitions from the data dictionary. The Metadata API uses Oracle-supplied XSL stylesheets to transform metadata into the format required for Data Pump processing.

Understanding the Oracle Metadata API

The Oracle Metadata API provides PL/SQL packages that allow applications and utilities to retrieve, transform, and generate metadata for database objects.

Oracle Data Pump relies extensively on these packages to process:

Tables
Indexes
Views
Sequences
Users
Roles
PL/SQL packages
Functions
Procedures
Materialized views

If the Metadata API becomes unavailable, Data Pump cannot interpret object definitions correctly.

What Are XSL Stylesheets?

Oracle stores a collection of internal XSL (Extensible Stylesheet Language) documents that are used by the Metadata API to transform XML-based metadata into SQL definitions during export and import operations.

If these stylesheets are missing, corrupted, or not loaded properly, Oracle Data Pump cannot perform metadata transformations, resulting in ORA-39213.

Common Causes

Missing Metadata API XSL stylesheets.
Corrupted Oracle XML DB repository.
Incomplete Oracle Database upgrade.
Interrupted patch installation.
Invalid Metadata API packages.
Invalid Oracle XML DB component.
Corrupted database dictionary objects.
Improper manual modifications to Oracle components.

Business Impact

ORA-39213 can prevent database administrators from performing logical backups, migrations, upgrades, cloning operations, and disaster recovery procedures.

Typical production impacts include:

Failed database exports.
Migration delays.
Upgrade interruptions.
Schema cloning failures.
Disaster recovery delays.
Application deployment interruptions.
Extended maintenance windows.

Prerequisites

Oracle Database 11g or later.
SYSDBA privileges.
Access to SQL*Plus.
Oracle Data Pump utilities installed.
Permission to execute Oracle-supplied packages.
Backup before making system-level changes.

Why This Error Occurs

Oracle Data Pump depends on the Metadata API to generate SQL definitions for every object included in an export or import operation. Before metadata can be processed, Oracle initializes the Metadata API and loads the required XSL transformation stylesheets.

If these stylesheets are unavailable or the Metadata API cannot initialize successfully, Oracle cannot transform metadata into the format required by Data Pump. As a result, the export or import operation stops immediately with ORA-39213.

Oracle DBA Recommendation

Whenever ORA-39213 occurs, first reload the Metadata API stylesheets, then verify the validity of Oracle XML DB and Metadata API components before attempting more advanced recovery procedures. In most environments, this resolves the problem quickly without requiring database reinstallation.

Step 1 – Verify the Oracle Data Pump Environment

Before making any changes, verify that Oracle Data Pump utilities are functioning correctly and that you are connected to the intended database instance.

sqlplus / as sysdba

Confirm the database version.

SELECT banner_full
FROM v$version;

Step 2 – Verify Oracle Components

Check the status of Oracle database components, particularly Oracle XML DB, because Data Pump metadata processing depends on these components.

COLUMN comp_name FORMAT A45

SELECT comp_name,
       version,
       status
FROM   dba_registry
ORDER BY comp_name;

All required components should normally display a status of VALID.

Step 3 – Verify Metadata Packages

Ensure that the Metadata API packages are valid.

COLUMN object_name FORMAT A30

SELECT object_name,
       object_type,
       status
FROM   dba_objects
WHERE  object_name LIKE 'DBMS_METADATA%'
ORDER BY object_name;

All Metadata API packages should have a status of VALID.

Step 4 – Reload Metadata API XSL Stylesheets

In many cases, ORA-39213 is resolved by reloading the Oracle-supplied XSL stylesheets used by the Metadata API.

Connect as SYSDBA and execute:

EXEC DBMS_METADATA_UTIL.LOAD_STYLESHEETS;

If the procedure completes successfully without errors, the stylesheets have been reloaded into the metadata repository.

Step 5 – Recompile Invalid Objects

If invalid Oracle objects are present, recompile them before testing Data Pump again.

@?/rdbms/admin/utlrp.sql

This Oracle-supplied script recompiles invalid PL/SQL packages, procedures, functions, triggers, and views.

Step 6 – Verify Invalid Objects

After recompilation, verify whether invalid objects still exist.

SELECT owner,
       object_name,
       object_type
FROM   dba_objects
WHERE  status='INVALID'
ORDER BY owner, object_name;

Investigate any remaining invalid Oracle-supplied objects before continuing.

Step 7 – Retry the Data Pump Operation

Once the Metadata API has been repaired, rerun the original export or import.

Example export:

expdp system/password
directory=DATA_PUMP_DIR
dumpfile=full_export.dmp
logfile=full_export.log
full=y

Example import:

impdp system/password
directory=DATA_PUMP_DIR
dumpfile=full_export.dmp
logfile=import.log
full=y

If ORA-39213 no longer appears, the Metadata API has been restored successfully.

Additional Troubleshooting

If the problem persists after reloading the stylesheets, investigate the following areas:

Oracle XML DB component status.
Invalid SYS-owned objects.
Database upgrade completion.
Recent Oracle patch installation.
Alert log messages.
Trace files generated during Data Pump execution.
Data dictionary corruption.

Troubleshooting Checklist

Verify Oracle version.
Check DBA_REGISTRY component status.
Confirm Oracle XML DB is VALID.
Verify Metadata API package status.
Reload XSL stylesheets.
Run UTLRP to recompile invalid objects.
Review remaining invalid SYS objects.
Retry EXPDP or IMPDP.
Review alert logs if the problem persists.

Production Case Study

Following a database patching activity, a scheduled full database export began failing with ORA-39213: Metadata Processing is not Available. Investigation showed that Oracle XML DB remained valid, but the Metadata API could not access the required XSL stylesheets. Executing DBMS_METADATA_UTIL.LOAD_STYLESHEETS, followed by recompiling invalid objects with utlrp.sql, restored normal Metadata API functionality. The subsequent Data Pump export completed successfully without additional changes.

Oracle Data Pump Best Practices

Oracle Data Pump is the preferred utility for logical backup, migration, upgrade, and database movement. Following Oracle best practices helps reduce failures and ensures consistent export and import operations across production environments.

Always verify Oracle Database component status before large export or import operations.
Use Oracle-supplied Data Pump utilities that match the database version.
Keep Oracle XML DB and Metadata API components in a VALID state.
Review Data Pump log files after every export and import.
Perform routine health checks on the data dictionary.
Test Data Pump jobs after applying Release Updates (RUs) or Release Update Revisions (RURs).
Store dump files in secure Oracle DIRECTORY objects with appropriate permissions.
Maintain regular backups before performing database upgrades or metadata repairs.

Understanding the Metadata API

The Oracle Metadata API provides the internal framework used to extract database object definitions from the data dictionary. Rather than reading object definitions directly, Oracle Data Pump requests metadata through the DBMS_METADATA packages, which transform internal dictionary information into SQL statements and XML representations.

This architecture ensures consistent metadata generation across Oracle utilities, including Data Pump, SQL Developer, Enterprise Manager, and other Oracle management tools. If the Metadata API becomes unavailable, multiple administrative operations—not just Data Pump—may be affected.

Common Administrator Mistakes

Ignoring invalid Oracle components after patching or upgrades.
Running Data Pump immediately after an interrupted database upgrade.
Using mismatched Data Pump client and server versions without verifying compatibility.
Skipping recompilation of invalid database objects.
Overlooking Oracle XML DB status in DBA_REGISTRY.
Attempting manual modifications to Oracle-supplied metadata packages.
Ignoring warnings in Data Pump log files.
Not validating database health before scheduled exports.

Related Oracle Errors

Error	Description
ORA-31626	Job does not exist.
ORA-31655	No data or metadata objects selected for processing.
ORA-39002	Invalid Data Pump operation.
ORA-39006	Internal Data Pump error.
ORA-39065	Unexpected master process exception.
ORA-39126	Worker process unexpectedly terminated.
ORA-04063	Package or package body contains compilation errors.

Frequently Asked Questions (FAQ)

What causes ORA-39213?

The error occurs when Oracle Data Pump cannot use the Metadata API to process database object definitions. Missing or unloaded XSL stylesheets, invalid metadata packages, or invalid Oracle XML DB components are among the most common causes.

Is reloading the XSL stylesheets safe?

Yes. Oracle provides the DBMS_METADATA_UTIL.LOAD_STYLESHEETS procedure specifically to reload the Metadata API stylesheets. It is the recommended first step when ORA-39213 is encountered.

Should I rerun Data Pump after reloading the stylesheets?

Yes. Once the stylesheets have been successfully reloaded and any invalid objects have been recompiled, rerun the original EXPDP or IMPDP job to verify that metadata processing has been restored.

Can invalid Oracle components cause this error?

Yes. Invalid Oracle XML DB or Metadata API components can prevent Data Pump from processing metadata correctly. Always verify the status of components in DBA_REGISTRY.

How can I prevent ORA-39213 in production?

Keep Oracle Database fully patched, validate component status after upgrades, recompile invalid objects when necessary, monitor Data Pump logs, and perform routine database health checks before scheduled backup or migration activities.

About the Author

Rana Abdul Wahid is an Oracle Database and Oracle E-Business Suite Consultant with more than 15 years of experience in Oracle Database Administration, Oracle E-Business Suite Application DBA, Oracle Cloud Infrastructure (OCI), Oracle RAC, Oracle Data Guard, RMAN Backup & Recovery, Linux/Unix Administration, MySQL, Microsoft SQL Server, PostgreSQL, and enterprise infrastructure management.

His expertise includes Oracle Database upgrades, Data Pump migrations, backup and recovery, performance tuning, Oracle Cloud Infrastructure (OCI), Linux administration, and enterprise production support.

Learn more about the author →

Conclusion

ORA-39213 indicates that Oracle Data Pump cannot use the Metadata API required to process database object definitions. In many environments, the issue is resolved by reloading the Oracle-supplied XSL stylesheets using DBMS_METADATA_UTIL.LOAD_STYLESHEETS, verifying the validity of Oracle XML DB and Metadata API components, and recompiling invalid objects where necessary.

By following a structured troubleshooting approach—validating database components, repairing metadata infrastructure, reviewing Data Pump logs, and applying Oracle best practices—database administrators can quickly restore Data Pump functionality and minimize downtime during backup, migration, and upgrade activities.

Final Oracle DBA Recommendation

Before every production export or import, verify that Oracle XML DB and Metadata API components are VALID, ensure no critical SYS-owned objects are invalid, monitor Data Pump log files for warnings, and maintain regular database health checks. Proactive validation helps prevent ORA-39213 and improves the reliability of Oracle Data Pump operations.

Found this guide helpful? Explore more Oracle Database, Oracle Data Pump, RMAN, Oracle E-Business Suite, Linux administration, and production troubleshooting articles in the Oracle Error Codes Guide.

Search This Blog

Oracle Database Error Solutions & DBA Guide

Oracle Database Error Solutions & DBA Knowledge Base