Every DBA’s will generate pre and post invalid report before patching activity in oracle application environments. Comparing pre and post reports will give an insight about the invalids generated by patch.
Oracle support has released EBS Invalid Object Utility which performs detailed analysis about the invalids that helps oracle support in viewable html formal.
This utility is not meant to be a recompile utility, especially if you have a large number of invalid objects. UTLRP.sql is still the best recompile method. This utility is meant to help with invalid object compile errors when there are a manageable number of invalids, perhaps 100 or less.
It displays all invalid objects and meta-data in single html report.
- Displays all Invalid Objects and meta-data in a single HTML Report, including:
- Owner, Object Name, Object Type
- Source Code for Objects (truncated to 20 lines to reduce report size)
- Database Object Versions and File System Versions (for apps packages)
- Compile Errors from DBA_ERRORS
- Quick View Summary of all invalid objects, their types and schemas
- Cross-references your current list of invalids with known objects from the Upgrade Guide of Droppable Objects*
- Cross References DBA_OBJECTS.TIMESTAMP and AD Patching tables to show objects creation date/modified date in relation to the last 100 days of patches applied
- Provides insight on which patches might have caused the invalid object
References:
EBS Invalid Object Utility (Doc ID 2214169.1)
