My Oracle Support Banner

Issues With Wrapped Packages After Impdp (Doc ID 1909287.1)

Last updated on MARCH 27, 2019

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 11.2]
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.


NOTE: The document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

After importing to a target or a database some wrapped packages are invalid and cannot be compiled.

ORA-39082: Object type PACKAGE BODY:"TC"."MY_PKG" created with compilation warnings

After import with impdp to a database with remap_schema, for the wrapped procedures, the character “/”, which is normally also used as a package body end code, is changed.
For example, the difference is between these lines in or or ...

This package body in is “malformed” and invalid.

Importing a dumpfile containing a wrapped package (or other PLSQL source) that has the SQL terminator character '/' as the last character of a line of wrapped text raises a PLSQL error, e.g.:
  ORA-39082 Object type PACKAGE_BODY:<SCHEMA><PACKAGE_NAME> created with compilation warnings.


Import or migration to or


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

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