IBM Support

Exception_Shared_LastUpdateDtNotMatched may occur during data loading

Troubleshooting


Problem

InfoSphere MDM Server is rejecting records with the error message "Exception_Shared_LastUpdateDtNotMatched"

Symptom

When executing the InfoSphere MDM Server batch processor in multiple-thread mode to process data loading, the following error message is reported in the file batchLoadFail.out:

[Exception_Shared_LastUpdateDtNotMatched:] Another transaction has
updated the database record you are trying to update. Cannot update
record at this time, please try again

Resolving The Problem

This is a valid validation in InfoSphere MDM Server used to prevent the same data from being modified by multiple-threads at the same time. This issue can be resolved by re-submitting the failed transaction. A new feature for the batch processor, deadlockRetry, was introduced with InfoSphere MDM Server version 8.0.1, which you can configure to resolve this issue.

Set the following items in the batch.properties to implement this feature to re-submit the failed transaction:


    deadlockRetryErrorCode = <ReasonCode>109</ReasonCode>

    deadlockMaxRetries = 3


[{"Product":{"code":"SSPVUA","label":"IBM InfoSphere Master Data Management Server"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"InfoSphere Master Content for InfoSphere Master Data Management Server","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF027","label":"Solaris"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"}],"Version":"8.0.1;8.5","Edition":"All Editions","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 June 2018

UID

swg21427107