In rare circumstances the Index Rebuild could fail with 'Failed to Switch Index Volumes For Rebuild'
Article ID: 100048918
Updated On:
Description
Error Message
Index rebuild fails with
The rebuild subtask has failed.
Error Code: 62
Description: Failed to Switch Index Volumes For Rebuild. Archive Id: [189058665ED031144968A691B1A6F92481110000evserver] - StartSequenceNumber: [97210379] - EndSequenceNumber: [106814279] - ignore64bitVolumes: [False]. Exception from HRESULT: 0x80040E2F
Enterprise Vault Event log contains the Event ID 13405
Event: 13405
Source: Enterprise Vault
Category: Directory Service
Description:
A constraint violation error was detected while accessing the Vault Database 'EnterpriseVaultDirectory' (Internal reference: {CADODataAccess::ExecuteSQLCommand} [d:\builds\16_\ev\v-m-s\sources\source\common\adointerface\adodataaccess.cpp, lines {1326,1328,1347,1370}, built Oct 9 11:34:22 2019]):
Description:
The DELETE statement conflicted with the REFERENCE constraint "FK_IndexingSubTask_IndexVolume". The conflict occurred in database "EnterpriseVaultDirectory", table "dbo.IndexingSubTask", column 'IndexVolumeIdentity'.
SQL Command:
dbo.uspsu_SwitchIndexVolumesForRebuild
Additional Microsoft supplied information:
Source: Microsoft OLE DB Driver for SQL Server
Number: 0x80040e2f
SQL State: 23000
Native Error: 00000547
HRESULT 0x80040e2f
Cause
There could be different Index Volumes with overlapping ranges associated to the same archive as for example:
IndexVolumeIdentity |
FirstItemSequenceNumber |
HighestItemSequenceNumber |
1000 |
87394680 |
97216509 |
1001 |
97210379 |
97230378 |
1002 |
97216510 |
106814279 |
The Index Volume '1001' range does overlap with either Index Volume '1000' and '1002', executing an index rebuild for '1001' would automatically include '1002' and '1000'.
Resolution
In case of the aforementioned an Index Rebuild for the entire archive rather than individual index volumes is recommended, however index volumes with overlapping ranges should not exist and its root cause and it's under investigation.
This issue is currently under investigation by Veritas Technologies LLC. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently 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.
Note: Customers experiencing this issue are encouraged to contact Veritas Technical Support as data is still being collected to assist in resolving this issue.
Issue/Introduction
Additional Information
