Potential inconsistent search results may occur when using Discovery Accelerator or Compliance Accelerator against Enterprise Vault (tm) for Microsoft Exchange 5.0 SP4 with Engineering hotfix, through 6.0 SP2 - Overview
| Article:TECH48662 | | | Created: 2006-01-03 | | | Updated: 2006-01-11 | | | Article URL http://www.symantec.com/docs/TECH48662 |
Problem
Potential inconsistent search results may occur when using Discovery Accelerator or Compliance Accelerator against Enterprise Vault (tm) for Microsoft Exchange 5.0 SP4 with Engineering hotfix, through 6.0 SP2 - Overview
Solution
What is Affected
Search performance improvements in Enterprise Vault 5.0 SP5 introduced the potential for inconsistent search results may occur under ANY of the following conditions:
1. Abnormal load
2. The index server default parameters were changed
3. Running any version of Discovery Accelerator (DA) to perform searches against Enterprise Vault for Microsoft Exchange 5.0 SP4 + Engineering Hotfix through 6.0 SP2
4. Running any version of Compliance Accelerator (CA) to perform searches against Enterprise Vault for Microsoft Exchange 5.0 SP4 + Engineering Hotfix through 6.0 SP2
5. When an Enterprise Vault index server reached the maximum allowed index connections, default of 24 connections, an ongoing search request from a vault could be prematurely terminated without giving an error
6. During the testing of this issue, it was also determined that any single archive with more search results than the default 'chunk size' (50,000 for DA/CA 5.0 and 10,000 in prior versions) might have returned inconsistent results due to an issue with how those results were chunked and sorted. Note: Compliance Accelerator is less likely to be affected by this issue.
How to Determine if Affected
Because there are so many factors which could have created bursts of index connections, Symantec cannot guarantee that this issue did not impact your results. If you are running any searches from CA or DA against any of the versions listed above, of Enterprise Vault for Microsoft Exchange, the search results may be affected by this issue. However, the chance of being affected by this issue is significantly lower if you are running any version of Enterprise Vault 6.0.
Resolution
This issue is formally resolved with Enterprise Vault for Microsoft Exchange 6.0 SP3, which is available at the following link: http://support.veritas.com/docs/284461
For Enterprise Vault for Microsoft Exchange 6.0 SP2, a hotfix is available at the following link: http://support.veritas.com/docs/284451
For Enterprise Vault for Microsoft Exchange 5.0 SP6, a hotfix is available at the following link: http://support.veritas.com/docs/284439
Once any of these resolutions have been applied, you can re-run and review any previous searches with Discovery Accelerator or Compliance Accelerator against Enterprise Vault for Microsoft Exchange.
Further Information
For more detailed information, please refer to the following FAQ designed to assist Administrators with this issue:
http://support.veritas.com/docs/284543
Search performance improvements in Enterprise Vault 5.0 SP5 introduced the potential for inconsistent search results may occur under ANY of the following conditions:
1. Abnormal load
2. The index server default parameters were changed
3. Running any version of Discovery Accelerator (DA) to perform searches against Enterprise Vault for Microsoft Exchange 5.0 SP4 + Engineering Hotfix through 6.0 SP2
4. Running any version of Compliance Accelerator (CA) to perform searches against Enterprise Vault for Microsoft Exchange 5.0 SP4 + Engineering Hotfix through 6.0 SP2
5. When an Enterprise Vault index server reached the maximum allowed index connections, default of 24 connections, an ongoing search request from a vault could be prematurely terminated without giving an error
6. During the testing of this issue, it was also determined that any single archive with more search results than the default 'chunk size' (50,000 for DA/CA 5.0 and 10,000 in prior versions) might have returned inconsistent results due to an issue with how those results were chunked and sorted. Note: Compliance Accelerator is less likely to be affected by this issue.
How to Determine if Affected
Because there are so many factors which could have created bursts of index connections, Symantec cannot guarantee that this issue did not impact your results. If you are running any searches from CA or DA against any of the versions listed above, of Enterprise Vault for Microsoft Exchange, the search results may be affected by this issue. However, the chance of being affected by this issue is significantly lower if you are running any version of Enterprise Vault 6.0.
Resolution
This issue is formally resolved with Enterprise Vault for Microsoft Exchange 6.0 SP3, which is available at the following link: http://support.veritas.com/docs/284461
For Enterprise Vault for Microsoft Exchange 6.0 SP2, a hotfix is available at the following link: http://support.veritas.com/docs/284451
For Enterprise Vault for Microsoft Exchange 5.0 SP6, a hotfix is available at the following link: http://support.veritas.com/docs/284439
Once any of these resolutions have been applied, you can re-run and review any previous searches with Discovery Accelerator or Compliance Accelerator against Enterprise Vault for Microsoft Exchange.
Further Information
For more detailed information, please refer to the following FAQ designed to assist Administrators with this issue:
http://support.veritas.com/docs/284543
If you have not
received this as a Software Alert from the Symantec Email Notification Service,
please visit the following link to
subscribe: http://maillist.support.veritas.com/subscribe.asp
. To receive notifications of critical technical issues, like this one, select
"Software Alerts" for each product running in your environment. To receive
monthly updates on new or republished TechNotes, select "Digest" updates.
|
|
| Source | ETrack |
| Value | 623771 |
Related Articles
Legacy ID
284569
Article URL http://www.symantec.com/docs/TECH48662
Terms of use for this information are found in Legal Notices









Thank you.