UCMDB should be able to detect and handle a DB deadlock

UCMDB should be able to detect and handle a DB deadlock

Two different actions (one from a discovery job and one from a integration) were trying to apply changes on the same object on DB which lead to a deadlock.

UCMDB server restart was necessary to get the UCMDB up and running again.

This isn’t acceptable for a production environment, so UCMDB has to detect such a situation and solve it on their own, so that there isn’t the need for a restart and a system downtime.

There should be a way that UCMDB report such a situation or skip one action.

At the moment the only workaround is to reschedule the two jobs and hope that they won’t run at the same time in future which couldn’t be guarantee (after a restart or when a jobs take much more time than usual), so it could happen again.

Reference: QCIM1H125451 – ‘Write access is not possible due to deadlocks’

Tags (1)
1 Comment
Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes

Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.