SQL Deadlocks and excessive blockings can occur when a PST Export is performed during Archiving or Journaling
Article ID: 100033572
Updated On:
Resolution
Veritas has acknowledged that the above-mentioned issue is present in the version(s) of the product(s) referenced in this article.
There are currently no plans to address this issue by way of a cumulative hotfix or service pack in the current or previous versions of the software at the present time. This issue may be resolved in a future major revision of the software at a later time, but is not scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Veritas Sales representative or the Veritas Sales group to discuss these concerns. For information on how to contact Veritas Sales, please see https://www.Veritas.com.
There are currently no plans to address this issue by way of a cumulative hotfix or service pack in the current or previous versions of the software at the present time. This issue may be resolved in a future major revision of the software at a later time, but is not scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Veritas Sales representative or the Veritas Sales group to discuss these concerns. For information on how to contact Veritas Sales, please see https://www.Veritas.com.
Issue/Introduction
In Enterprise Vault (EV) 12. x, when an archive is exported to PST while archiving or journaling is in progress, excessive blockings (an average of 60 seconds was recorded) and deadlocks can occur.
The following adhoc query has been found to block Stored procedures such as usp_finishinsertsaveset1 and result in self-deadlocks (ArchivepointIdentity, IdDateTime, and IndexSeqNo will vary)
SELECT TOP 10000
The following adhoc query has been found to block Stored procedures such as usp_finishinsertsaveset1 and result in self-deadlocks (ArchivepointIdentity, IdDateTime, and IndexSeqNo will vary)
SELECT TOP 10000
'ArchivePointIdentity'=SS.ArchivePointIdentity,'CollectionIdentity'=SS.CollectionIdentity,'IdPartition'=SS.IdPartition,ArchivedDate,ArchivedItems,ArchivedItemsSize,
CreatedDate,FileFormat,HSMType,IdChecksumHigh,IdChecksumLow,IdDateTime,IdTransaction,IdUniqueNo,IndexSeqNo,ItemSize,MeanRecallTime,MigratedFileId,ModifiedDate,
Recalls,RefCount,RelativeFileName,Restores,RetentionCategoryIdentity,StoreIdentifier,TotalCount,VaultID
FROM Saveset SS INNER JOIN Vault V ON SS.VaultIdentity = V.VaultIdentity LEFT
CreatedDate,FileFormat,HSMType,IdChecksumHigh,IdChecksumLow,IdDateTime,IdTransaction,IdUniqueNo,IndexSeqNo,ItemSize,MeanRecallTime,MigratedFileId,ModifiedDate,
Recalls,RefCount,RelativeFileName,Restores,RetentionCategoryIdentity,StoreIdentifier,TotalCount,VaultID
OUTER JOIN SavesetStore SSS ON SS.SavesetIdentity = SSS.SavesetIdentity LEFT
OUTER JOIN Collection COL ON SS.CollectionIdentity = COL.CollectionIdentity
where
OUTER JOIN Collection COL ON SS.CollectionIdentity = COL.CollectionIdentity
(SS.ArchivePointIdentity = 2) and ((IdDateTime = '20151130 00:34:07:000'
and IndexSeqNo > 121400000) or (IdDateTime > '20151130 00:34:07:000' and
IdDateTime <= '20161130 23:59:59:000')) order by IdDateTime asc, IndexSeqNo asc
and IndexSeqNo > 121400000) or (IdDateTime > '20151130 00:34:07:000' and
IdDateTime <= '20161130 23:59:59:000')) order by IdDateTime asc, IndexSeqNo asc
Additional Information
ETrack: 3906736
Was this article helpful?
Yes
No
Powered by
