How to check Upgrade History

vinitaraico
Tera Contributor

Hi Team,

 

Need Help to Understand Upgrade History Table, after instance Upgraded on any new security Patch /Latest releases etc ,Wanted to understand this Table . what action we have to take on skipped priority 2 records what is the impact if no action taken. wanted to explore more on Upgrade history table.Looking for some good blogs and community link to refer

 

 

3 REPLIES 3

AshishKM
Kilo Patron
Kilo Patron

Hi @vinitaraico , 

There is learning module on upgrade skipped records over nowlearning portal.

Check this out for more details.

 

AshishKM_0-1722272674461.png

 

 

https://nowlearning.servicenow.com/lxp/en/now-platform/upgrade-skipped-records?id=learning_course_pr...

 

-Thanks,
AshishKM

 


Please mark this response as correct and helpful if it helps you can mark more that one reply as accepted solution

O nice one, never knew this course existed. I'm going to check it out 😅 maybe interesting for customers 👍

 

Kind regards,

 

Mark Roethof

Independent ServiceNow Consultant

10x ServiceNow MVP

---

 

~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field

LinkedIn

Sumanth16
Kilo Patron

Hi @vinitaraico ,

 

### 1. `sys_upgrade_history_log` Table:

The `sys_upgrade_history_log` table in ServiceNow stores information related to upgrade history and logs. It records details about various upgrade processes, such as what upgrades were applied, when they were applied, and any errors or issues encountered during the upgrade. This table helps administrators track the upgrade progress and troubleshoot problems that might occur during the upgrade process.

 

### 2. "Revert To Base System" UI Action:

The "Revert To Base System" UI action is used in ServiceNow when a record in an update set or during an upgrade is skipped or ignored. When an upgrade record is skipped, it means that the changes in that record are not applied during the upgrade. The "Revert To Base System" action allows you to revert the record back to its base system state, essentially undoing any customizations or changes made to the record.

 

By clicking "Revert To Base System," you are instructing the system to discard any local changes made to that record and revert it to the state defined in the base system. This action is useful when you want to reset a record back to its original configuration, removing any customizations that might have been applied.

 

### 3. "Application Repairing":

"Application Repairing" in ServiceNow refers to a process where administrators can repair applications or modules within the platform. This typically involves fixing issues, inconsistencies, or errors that might have occurred due to various reasons, such as incorrect configurations, misapplied updates, or data problems.

 

When you initiate an application repair, ServiceNow attempts to identify and rectify any issues related to that application. The repair process can include actions like fixing broken references, reapplying configurations, or resolving data inconsistencies. ServiceNow uses its internal logic and rules to analyze the application components and apply necessary fixes to ensure the application functions correctly.

 

During the repair process, ServiceNow might log information about what issues were found and how they were resolved. The specific actions taken during the repair can vary based on the nature of the problem and the application being repaired.

 

It's important to note that repairing applications should be performed with caution, and it's advisable to thoroughly understand the implications of the repair action before initiating it, especially in a production environment.

Plz mark my solution as Accept, If you find it helpful.

 

 

Thanks & Regards,

Sumanth meda