DataPump Import (Impdp) Fails with ORA-39006, ORA-39065, ORA-4063, ORA-6508
(Doc ID 1641316.1)
Last updated on JULY 02, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1 and laterGen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
The DataPump import log shows errors like below:
Import: Release 11.2.0.3.0 - Production on Thu Sep 5 10:41:01 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning option
ORA-39006: internal error
ORA-39065: unexpected master process exception in DISPATCH
ORA-04063: package body "SYS.DBMS_METADATA_UTIL" has errors
ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_METADATA_UTIL"
ORA-39097: Data Pump job encountered unexpected error -6508
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning option
ORA-39006: internal error
ORA-39065: unexpected master process exception in DISPATCH
ORA-04063: package body "SYS.DBMS_METADATA_UTIL" has errors
ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_METADATA_UTIL"
ORA-39097: Data Pump job encountered unexpected error -6508
Changes
Database was recently upgraded from 10g to 11g and the July CPU patch was applied.
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 |
| Changes |
| Cause |
| Solution |
| References |