Troubleshooting issues with completed update sets
Purpose
This article guides you through the process of troubleshooting issues with completed update sets. It provides steps to help you eliminate common causes for your problem by verifying that the configuration of your networking is correct.
Symptoms
Symptoms may include the following:
Symptoms may include the following:
- There are instance issues post-commit
- Update set shows as committed but has inconsistencies
- Not everything is updated after the update set completes
Resolution
Validate that each troubleshooting step below is true for your environment. Each step provides instructions or a link to an article to eliminate possible causes and take corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution.
- Verify that the expected records are contained in the update set. See the following article: KB0535248: Verifying that expected records are contained in the Update Set.
- Verify if you are affected by one of the Known Errors impacting update sets. See the following articles: KB0523691: Update set preview displays backed out update set data; KB0522588: Unique records are not displaying an error when previewing or committing an update set; KB0523177: Cannot commit update sets after datacenter migration; or KB0522903: Update Set Commits are unnecessarily slow due to CollisionDetector.
- Verify which records will be captured with an update set. See the following article: KB0535262: Checking which records will be captured in an Update Set.
- Troubleshoot the update set preview. See the following article: KB0535263: Troubleshooting Update Set Preview.
Note: If your problem still exists after trying the steps in this article:
|