My Oracle Support Banner

Data Pump Import Failed With ORA-39126 ORA-3237 ORA-6512 (Doc ID 815763.1)

Last updated on MARCH 01, 2021

Applies to:

Oracle Database - Enterprise Edition - Version 10.1.0.2 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 03-Oct-2014***

Symptoms

You have successfully performed a data pump export (expdp) from your production environment and are attempting to import the dumpfile into your test environment. All objects are VALID and the character sets are compatable. However, when you try to import you receive the following errors:

Starting "SYSTEM"."SYS_SQL_FILE_FULL_02": system/******** parfile=<FILENAME>.par
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.LOAD_METADATA [TABLE_DATA:"SYSTEM"."SYS_SQL_FILE_FULL_02"]
SELECT process_order, flags, xml_clob, NVL(dump_fileid, :1), NVL(dump_position, :2), dump_length, dump_allocation, grantor, object_row, object_schema, object_long_name, processing_status, processing_state, base_object_type, base_object_schema, base_object_name, property, size_estimate, in_progress FROM "SYSTEM"."SYS_SQL_FILE_FULL_02" WHERE process_order between :3 AND :4 AND processing_state <> :5 AND duplicate = 0 ORDER BY process_order
ORA-03237: Initial Extent of specified size cannot be allocated in tablespace (TEMP_GROUP)

ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.KUPW$WORKER", line 6351

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.