Using the Post Upgrade Reports in Release 7


A new and often overlooked new feature in the upgrade path to release 7 is the introduction of a html based report/log, the PostRUPInstaller Report, related to the timings and success of the upgrade itself.  This can be very useful when data is needed to compile management reports, compare one upgrade to another, plan a production upgrade after running an upgrade on a pre-production environment, or if you just want an easy way to obtain a comprehensive view of the upgrade.

Main Article

As discussed above, Release 7 of Fusion Applications has a new .html report available that provides a complete, end to end view of the completed upgrade.  Let’s have a look into the contents of the report so you know what you can find inside.

Where to Find the Report

The report location is referenced in the Fusion Applications upgrade Guide 11g Release  7 (11.1.7) in the Post-Upgrade Tasks for Oracle Fusion Applications section 5.2.  If you have performed a chained upgrade, going from Release 5 to Release 6 and then upgrading to Release 7, the Release 6 upgrade PostRupInstaller Report can be found in the following location in your installation:

<span class="italic">FA_ORACLE_HOME</span>/admin/FUSION/log/fapatch/fapatch_11.1.6.0:

  While the report for Release 7 can be found here:


Now let’s look at the report itself, it is broken into two main sections, the header and the body.

The Header

In the header section you will find status for each of two parts of the RUP Installer, including start and end times, elapsed time as well as idle time. It looks like this:


The elapsed time and idle time are two of the most interesting points from the header section, as they provide a definitive measurement regarding how this particular upgrade ran as well as how it stacks up to previous upgrades which may have been performed.  Notice, it will also tell you if errors occurred at any point in the upgrade.

The Body

The body of the report provides you with the status of each step including the task name, number of attempts made, status, start time, end time, elapsed time, and most importantly the log file and a link to it for the step.


The log file link is very useful for taking a deeper dive into the details of any issue that may have occurred.  The links are good because they provide two things for your upgrade teams:
1) An excellent visual connection of which logs associate with a specific step in the process

2) Quick and easy access to the logs themselves

So, when gathering statistics on your upgrade, the PostRUPInstaller Report is a very useful new feature in the chained upgrade and upgrade for Release 7 functionality.

The PostRUPInstaller Report is also an excellent planning tool for use when planning your production upgrades, the contents of the report will list issues you may have encountered when performing the upgrade to a pre-production environment, allowing you to address issues; such as incorrect customizations that may have been left partially implemented, or flex fields that were left partially customized yet never deployed. Many of these types of clean up items can be addressed prior to the production upgrade starting and allowing more efficient use of your upgrade window.




Add Your Comment