DataPump Export (EXPDP) Error ORA-39095 Dump File Space Has Been Exhausted [ID 559692.1]

In this Document

Symptoms

Cause

Solution

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 11.2.0.2 - Release: 10.2 to 11.2

Information in this document applies to any platform.

***Checked for relevance on 23-MAR-2012***

Symptoms

You received the error message:

ORA - 39095 : " dump file space has been exhausted. Unable to allocate 4096 bytes"

jobsystem.sys_export_full_02 stops due to fatal error.

while performing DataPump export:

- when exporting a large number of tables then it completely stops

- the jobs may remain in the DataPump export tables

- no trace generated at the time of the failure.

Cause

You limited the number of files in DUMPFILE parameter with limited FILESIZE , i.e.:

full=Y

directory=dpump_dir

dumpfile=full_1.dmp,full_2.dmp,full_3.dmp,full_4.dmp

filesize=3000000000

This means max. 4 dump files with file size 3000000000 bytes (4x2.79 GB).

Solution

1. Use the dynamic format (i.e dumpfile=full_%U.dmp) :

The 'wildcard' specification for the dump file can expand up to 99 files. If 99 files have been generated before the export has completed, it will again return the ORA-39095 error.

2. If this is yet not enough and more files are needed, a workaround would be to speciyy a bigger FILESIZE parameter.

3. If this is inconvenient, then another option is to use this syntax:

dumpfile=fullexp%U.dmp, fullexp2_%U.dmp, fullexp3_%U.dmp

which can expand up to 3*99 files.

If encountering problems containing the dump in a single directory using this solution, you may prefer this syntax:

dumpfile=dmpdir1:fullexp1_%U.dmp, dmpdir2:fullexp2_%U.dmp, dmpdir3:fullexp3_U.dmp

(assuming the 3 directory objects listed above had been already created first).