Enterprise Vault may not remove all fingerprints or storage entries during a rollback operation (failed storage attempt)

  • Modified Date:
  • Article ID:000005851


Enterprise Vault 8.x introduced an advanced Single Instance Storage mechanism to further reduce the footprint of physical storage required for archived items by creating and storing a unique fingerprint within a new database.  Under certain conditions, a SQL deadlock can occur during the creation of these fingerprints, causing orphaned fingerprints (that cannot currently be removed) to exist within the database.  Changes have been made in Enterprise Vault 8.0 Service Pack 2 to reduce the likelihood of SQL deadlocks that could result in orphan records being created as well as code changes to mitigate any errors stemming from such deadlocks.

At no time could a data loss situation occur due to the orphaned fingerprints. 


Symantec Corporation 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 Symantec Sales representative or the Symantec Sales group to discuss these concerns.  For information on how to contact Symantec Sales, please see http://www.symantec.com.


Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)