Issues With Wrapped Packages After Impdp
(Doc ID 1909287.1)
Last updated on MARCH 27, 2019
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [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.
After importing to a target 220.127.116.11 or a 18.104.22.168 database some wrapped packages are invalid and cannot be compiled.
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_BODY
ORA-39082: Object type PACKAGE BODY:"TC"."MY_PKG" created with compilation warnings
After import with impdp to a 22.214.171.124 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 126.96.36.199 or 188.8.131.52 or 184.108.40.206 ...
This package body in 220.127.116.11 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 18.104.22.168 or 22.214.171.124.
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