The Recommended Method To Resolve Discoverer EUL Corruption Or Failed EUL Upgrade Issues
Last updated on SEPTEMBER 27, 2016
Applies to:Oracle Discoverer - Version 4.1.37 and later
Information in this document applies to any platform.
***Checked for relevance on 27-Nov-2012***
4.1.xx, 9.0.2.xx, 9.0.4.xx, 10.1.2.xx, 11.1.1.xx
When upgrading an EUL the process may fail with various ORA-XXXX error messages.
One example is "Error: "The 4.1 End User Layer is corrupt - to upgrade this EUL you must first drop it and restore it from backup"."
This usually happens when a constraint has been disabled and invalid data was then subsequently entered into the table(s). Unfortunately, since there is no method to check the data, the invalid information will remain until an upgrade is performed. Then, during the upgrade process the data is checked and the upgrade then fails.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms