Skip to main content

DataPump Export (EXPDP) Error ORA-39095 Dump File Space Has Been Exhausted

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






If you like please follow and comment
Labels:

Comments

Post a Comment

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...
Post a Comment
Read more

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...
Post a Comment
Read more

How to make flash work on IE or Edge with IE Compatibility

How to make flash work on IE or Edge with IE Compatibility With flash been ended from 1-Jan-2021, many applications using flash have stopped working the way they were built (like OEM, OBIEE, etc). The option you have to upgrade.  This method will give a workaround in IE or Edge in IE compatibility mode without upgrading. 1. Verify you have installed flash.ocx on your desktop. Typically, flash.ocx file is located in C:\Windows\System32\Macromed\Flash or C:\Windows\SysWOW64\Macromed\Flash according to your laptop OS system. 2. Edit mms.cfg from the location as a System Administrator In the case of the 64bit system, it might have mms.cfg under C:\Windows\SysWOW64\Macromed\Flash 3. Add below options into mms.cfg file. Note: AllowListUrlPattern list is an example. The URLs need to be replaced to your hosts those have Flash pages. SilentAutoUpdateEnable=0 AutoUpdateDisable=1 EOLUninstallDisable=1 EnableAllowList=1 AllowListUrlPattern=http://www.google.com/ AllowListUrlPattern=http://goo...
Post a Comment
Read more