Upgrade Summary Report

  • Release version: Xanadu
  • Updated August 1, 2024
  • 2 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Upgrade Summary Report

    The Upgrade Summary Report provides a comprehensive overview of the upgrade process for a ServiceNow instance. It summarizes actions taken during the upgrade, highlights conflicts between customizations and the upgrade, and offers insights to help estimate upgrade durations for other instances. This report is essential for understanding the upgrade status, resolving conflicts, and planning future upgrades efficiently.

    Show full answer Show less

    Key Features

    • Upgrade Timeline and Status: Displays the previous and upgraded instance versions, start and finish times, and total upgrade duration.
    • Skipped Updates: Identifies the number of customizations skipped during the upgrade due to conflicts, including manual merges and errors. This helps pinpoint areas requiring reconciliation.
    • Review Skipped Updates: Provides tools to address and reconcile conflicts that caused skipped updates, facilitating smoother upgrade completion.
    • Node Upgrades: Shows the upgrade status for each node in the instance with color-coded icons and detailed information on hover, allowing targeted troubleshooting.
    • Schema Changes to Clone-excluded Tables: Lists tables excluded during cloning that were affected by the upgrade. Because these tables are empty, their upgrade time is shorter, enabling customers to estimate additional time needed for production upgrades based on table sizes.
    • Top 10 Fix Scripts by Duration: Highlights the fix scripts that took the longest to execute, helping identify performance bottlenecks during the upgrade.
    • Top 10 Schema Changes by Duration: Identifies schema changes requiring the most time, assisting in optimization and planning for future upgrades.

    Key Outcomes

    • Clear visibility into the upgrade process timeline, status, and duration.
    • Identification and tools to resolve conflicts between customizations and upgrade changes, reducing upgrade errors and skips.
    • Detailed node-specific upgrade status for focused troubleshooting and validation.
    • Insight into clone-excluded table upgrades, facilitating accurate estimation of upgrade times for production environments.
    • Performance insights from fix scripts and schema changes to improve upgrade efficiency.

    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

    Top section of upgrade summary report
    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

    Node Upgrades section of upgrade summary report

    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 Tables

    Figure 3. Upgrade Summary Report: Schema Changes to Clone-excluded tables

    Schema Changes to Clone-excluded Tables section of upgrade summary report
    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 Duration

    Figure 4. Upgrade Summary Report: Top 10 Fix Scripts by Duration

    Top 10 Fix Scripts by Duration section of upgrade summary report
    The Top 10 Fix Scripts by Duration helps you understand which fix scripts required the most time.

    Top 10 Schema Changes by Duration

    Figure 5. Upgrade Summary Report: Top 10 Schema Changes by Duration

    Top 10 Schema Changes by Duration section of upgrade summary report
    The Top 10 Schema Changes by Duration helps you understand which schema changes required the most time.