Upgrade history missing: cannot determine current version

The sys_upgrade_history table contains corrupted or incomplete records from previous upgrades, preventing version verification. (high likelihood)

Database corruption or deletion has affected the sys_upgrade_history table, removing critical upgrade tracking records. (high likelihood)

A previous upgrade process was interrupted or failed, leaving the upgrade history in an inconsistent state. (medium likelihood)

Custom modifications or business rules on the sys_upgrade_history table are preventing proper read operations. (medium likelihood)

Instance cloning or migration issues have resulted in missing or mismatched upgrade history data. (low likelihood)

Step 1: Navigate to System Definition > Tables and verify that the sys_upgrade_history table exists and is accessible without errors.

Step 2: Check the sys_upgrade_history table directly by going to System Diagnostics > Upgrades > Upgrade History to see if any records are displayed.

Step 3: Review the System Log at System Diagnostics > Log > Application Log for additional error details related to database access or table corruption.

Step 4: Check for any custom business rules, ACLs, or UI policies on the sys_upgrade_history table that might be blocking read operations.

Step 5: Verify the current instance version by navigating to System Diagnostics > Stats and comparing against expected upgrade version numbers.

Step 6: If the table appears corrupted or empty, open a ServiceNow support case with High priority as this requires database-level investigation and potential data recovery.

Step 7: Do not attempt to manually insert upgrade history records without ServiceNow support guidance, as this can create additional upgrade complications.

Step 8: Once support resolves the upgrade history issue, restart any pending upgrade processes from the System Diagnostics > Upgrades interface.