SQL Deadlocks can occur between different processes executing the usp_SavesetFinishInsert5 stored procedure during Archiving or Journaling

book

Article ID: 100033627

calendar_today

Updated On:

Resolution

This issue has been addressed in the following release:
 
Enterprise Vault 12.2

The following link contains information about Enterprise Vault 12.2
https://www.veritas.com/docs/000115777
 
Note: For information on how to obtain Enterprise Vault 12 see: How to obtain the license key and installation download for Veritas products

Issue/Introduction

During Mailbox Archiving or Journaling, SQL Deadlocks can occur between different processes (SPIDs) of the execution of the usp_SavesetFinishInsert5 stored procedure.
The deadlock can occur when 2 different processes start within microseconds of each other to process different messages containing the same attachments

The deadlock occurs at the following section:
  
UPDATE @tbSISParts
      SET [SISPartIdentity] = sis.[SISPartIdentity]
      FROM SISPart sis 
      INNER JOIN @tbSISParts tsis
      ON tsis.[FPHashPart1] = sis.[FPHashPart1] AND tsis.[FPDistinctionByte] =
sis.[FPDistinctionByte] 
      AND sis.[FileTransactionId] = tsis.[FileTransactionId] AND tsis.[UniqueId]
= sis.[UniqueId]
      AND sis.[IdPartition] = tsis.[IdPartition] AND sis.[VaultStoreIdentity] =
tsis.[VaultStoreIdentity

Additional Information

ETrack: 3907137
Powered by Wolken Software