Running Searches after upgrading to Enterprise Vault 12.4 causes multiple Index Volume failures

Running Searches after upgrading to Enterprise Vault 12.4 causes multiple Index Volume failures

Article: 100045903
Last Published: 2019-07-11
Ratings: 0 0
Product(s): Enterprise Vault

Problem

After upgrading to Enterprise Vault (EV) 12.4, running Searches in EV Search (EVS) or Discovery Accelerator (DA) can cause random Index Volumes to fail. Error Event ID 41315 is logged in the Event Logs with the description below. In addition, a review of the Indexing system-reporting log for that day, usually found under \Program Files (x86)\Enterprise Vault\EVIndexing\data\indexmetadata\reporting\system-reporting, will display an error referencing a missing column, as listed below.

Note - In order to review this log, it must be viewed in a SQLite browser. Veritas does not recommend any specific SQLite browser; however, there are numerous browsers that may be found online that can be used.

 

Error Message

- In the Enterprise Vault Event Log on the EV Indexing Server:

Event ID 41315
Category : Index Query Server
Description: A search failed with error "The indexing engine could not load the index".
Archive: JournalArchive01
Archive ID: 1A23BC456DEF123456789ABCDEFGHI12A1110000EVSERVER1
Index volume ID: X
User: evlab\vsa
Maximum results: 10000
Timeout (seconds): 3600
Sort order: snum

- In the error table of the system-reporting logs:

SQL error code [1]: no such column: frozen

 

Cause

EV 12.4 introduced an updated version of the Indexing engine. An EV upgrade processes each Index to also update its internal schema to match the Indexing engine's schema. This schema update is performed during the first startup of the Indexing service after the EV 12.4 upgrade. An informational event is logged advising the successful schema update of all Indexes, however, the missing column is still not present.

This issue can be mitigated by Rebuilding the affected Index Volumes, as Rebuilding the affected Index Volumes creates the proper schema. Performing an Index Volume Verify | Basic is sufficient to return the Index Volume to a healthy status. Since the random Index Volume failures have only been observed during multiple simultaneous searches using a high number of keywords in EVS or DA, searches may be resubmitted one at a time until they complete successfully.

 

Solution

Veritas has acknowledged that the above-mentioned issue is present in the version(s) of the product(s) referenced in this article.

This issue is currently under investigation by Veritas. Pending the outcome of the investigation, this issue may be resolved by way of a cumulative hotfix or service pack in the current or future versions 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.  For information on how to contact Veritas Sales, please see http://www.veritas.com .

Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.

References

JIRA : CFT-2045

Was this content helpful?