Troubleshooting failed patches warnings

Edit online
Tracked Resource Set patch events track updates to artifacts but are mostly used to update configurations of versioned artifacts. If patch events are not applied, reports and queries on specific configurations might return incorrect results. Lifecycle Query Engine (LQE) tracks patch event errors on the data provider status administration page to help you troubleshoot.

Problem

If a patch event is not applied, Lifecycle Query Engine shows the failed patches on the Data Providers page at http://<Host_name>:<port>/lqe/web/admin/data-sources.

The reports and queries on specific configurations might return incorrect results for the incoming data from the data provider to LQE. The data problem must be detected early so that user can troubleshoot it on time. The checksum processing is implemented as a part of the normal indexing process. If the checksum from the selection resources does not match the combined XOR checksum for the versionedResource URLs, the issue is marked as an invalid update to the Lifecycle Query Engine status page.

Solution

To resolve these problems:
  1. Check the list of failed patches.

    To view failed patches on the Administration> Query & report data> Data Providers page, click the status link in the Triple Store column. The list of resources for which patch events were not applied displays.

  2. Check the list of skipped resources by clicking the status link, and then click the Skipped Resources tab. If the affected artifacts are also included in the list of the skipped resources, retry the skipped resources.
  3. Click the data provider that has failed patches. In the Settings section, check the value of Wait time before retrying failed patches or skipped resources (minutes) field and wait until the specified time is completed.
  4. Confirm that the failed patches are no longer reported on the Data Providers page.
  5. If you frequently see the failed patches, contact your support team.