DataPump Export (EXPDP) Error ORA-39095 Dump File Space Has Been Exhausted
ERROR:
ORA - 39095 : " dump file space has been exhausted. Unable to allocate 4096 bytes"
job system.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.
REASON:
Limited the number of files in DUMPFILE parameter with limited FILESIZE , i.e.:
full=Y
directory=<DIRECTORY_NAME>
dumpfile=<DUMP_NAME>_1.dmp,<DUMP_NAME>_2.dmp,<DUMP_NAME>_3.dmp,<DUMP_NAME>_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=<DUMP_NAME>_%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. To avoid the ORA-39095 error by reducing number of files needed, a workaround would be to specify a bigger FILESIZE parameter.
filesize=10G
3. If this is inconvenient, then another option is to use this syntax:
dumpfile=<DUMP_NAME>1_%U.dmp, <DUMP_NAME>2_%U.dmp, <DUMP_NAME>3_%U.dmp
which can expand up to 3*99 files.
If encountering problems containing the dump in a single directory using this solution, we may use below:
dumpfile=<DIR_NAME1>:<DUMP_NAME>1_%U.dmp, <DIR_NAME2>:<DUMP_NAME>2_%U.dmp, <DIR_NAME3>:<DUMP_NAME>3_U.dmp
Post a Comment
Post a Comment