- 3,735,185 Users
- 2,247,137 Discussions
- 7,857,767 Comments
- 17.8K All Categories
- 3.3K Industry Applications
- 3.2K Intelligent Advisor
- 57 Insurance
- 533.3K On-Premises Infrastructure
- 137.3K Analytics Software
- 38.5K Application Development Software
- 5.1K Cloud Platform
- 109K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 70.7K Infrastructure Software
- 105K Integration
- 41.5K Security Software
22.214.171.124 impdp issue with wrapped packages
We are planning to upgrade our database to version 126.96.36.199. In our application we use the datapump tool to export data from our "core" database and import it into our "mobile" databases. This process worked perfectly before version 188.8.131.52 but when performing an import via data pump tool into a 184.108.40.206 database the import fails because one of our package gets invalid in the database during the import (we use wrapped packages).
The error is the following:
Compilation errors for PACKAGE BODY xxx.xxx
PLS-00753: malformed or corrupted wrapped unit
I checked the difference between the two databases (one where the dump file was imported from and the other where the dump file was imported into) and i found that the wrapped code of the packages are different.
In the all_source view the code of the package is stored in two rows. The last character of the first row is a "/" character in the database where the dump file was exported from. In the other database this "/" character is somehow removed from the code during the import.
This is the wrapped code part in the DB where the export was made:
And this is the wrapped code in the DB where the dump was imported into:
A "/" character is missing from the code in the DB where the import was made and the package cannot be compiled. However an additional "/" character is appended at the end of the code of the package.
Our packages was wrapped with the version of 10g but the same issue happened with another package when a re-wrapped them with a newer version of Oracle.
Did anyone encounter this issue? Is this an Oracle bug?
Thanks for your help in advance,