Upgrade Summary Report This report summarizes the actions taken, provides tools to resolve conflicts between customizations and the upgrade, and provides information to help estimate time for upgrades to other instances. Figure 1. Upgrade Summary Report: Database Upgrade Highlights Table 1. Screen elements Screen element Description From version Previous version of the instance To version Upgraded version of the instance Started When the upgrade process started Finished When the upgrade process finished Duration How long the upgrade process took Skipped In the example, 24 Skipped of 7016 changes reads as: 24 Skipped - Total number of customizations that were skipped, skipped manual merge, or skipped in error, and the file changed in the distribution since the last upgrade of the instance. These are the number of records the system did not upgrade because of conflicts between customizations and the upgrade. 7016 Changes - Total number of file changes in the distribution since the last upgrade of the instance, plus all inserts and deletes. Note: The manner in which upgrade records are counted was changed in the Jakarta release, which may render different record counts than in previous releases. Review Skipped Updates Click to reconcile conflicts that caused the system to skip some updates Node Upgrades Figure 2. Upgrade Summary Report: Node Upgrades The Node Upgrades section shows the status of the upgrade for each node in the instance. The color of the icon denotes the status, as illustrated by the legend (key) and to the right of the node icons. To see details about a node, position the cursor above the icon for that node. An arrow points to the node selected, and the information below the icons pertains to that node. Schema Changes to Clone-excluded TablesFigure 3. Upgrade Summary Report: Schema Changes to Clone-excluded tables The Schema Changes to Clone-excluded Tables section shows a list of tables affected by the upgrade that were clone-excluded when you cloned the production instance to this instance. Because clone-excluded tables are empty, upgrading them takes less time than upgrading those same tables on the production instance. To estimate how much longer the production upgrade takes, note the size of the clone-excluded tables on the production instance. Top 10 Fix Scripts by DurationFigure 4. Upgrade Summary Report: Top 10 Fix Scripts by Duration The Top 10 Fix Scripts by Duration helps you understand which fix scripts required the most time. Top 10 Schema Changes by DurationFigure 5. Upgrade Summary Report: Top 10 Schema Changes by Duration The Top 10 Schema Changes by Duration helps you understand which schema changes required the most time.