After replication runs between two Endpoint Protection Managers (SEPM), dbvalidator reports broken links in the database.
ConfigServer-0.log 2018-10-29 17:38:05.866 THREAD 8095068 INFO: Adding LuContent entry in LuDownloadedContentArray.xml from: {810D5A61-809F-49c2-BD75-177F0647D2BA} Seq#: 181029020 FULL: true{TargetId: C909BA98974B3E39FFE2F93B96D3F054} IFD: false IRD: true{TargetId: 88EA1ADD51658BDD7ED5196866C8518C, Target: 181029005} 2018-10-29 17:38:05.928 THREAD 8095068 FINE: updateMetadata: UPDATE BASIC_METADATA SET CHECKSUM = ?, CONTENT = ?, DELETED = ?, OWNER = ?, TIME_STAMP = ?, TYPE = ?, USN = ?, NAME = ?, DESCRIPTION = ?, REF_ID = ?, LAST_MODIFY_TIME = ?, DISABLED = ? WHERE ID = CONVERT(CHAR(32),?) , ID: 6028C6E625754ECE4312D41CB963A039 2018-10-29 17:38:08.090 THREAD 8095068 FINE: updateMetadata finished. 2018-10-29 17:38:08.090 THREAD 8095068 FINE: Deadlock victim, killed by database as product design! transaction (process id 58) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. rerun the transaction.
dbvalidator-0.log 2018-10-31 12:58:33.125 THREAD 1 WARNING: DatabaseValidationTask> logNodeDetails>> TargetId:[88EA1ADD51658BDD7ED5196866C8518C] TargetType:[PhysicalFile] ObjectTypeName:[ObjReference] ParentObjectTypeName :[IncrementalReverseDelta] Parent's TopLevelObject's GUID:[6028C6E625754ECE4312D41CB963A039]
The SEPM attempts to re-run database updates that fail due to a deadlock. However, the SEPM updates multiple objects in a single transaction so attempting the entire transaction again can create broken links.
{FIXED_DOWNLOAD_LATEST_SEP.EN_US}