cancel
Showing results for 
Search instead for 
Did you mean: 

Index error

Ciaran_Kavanagh
Level 2
Hi Guys,

I got this error a few mins after submitting a rebuild index (Job Description: Rebuild index volume)

Event Type:Error
Event Source:Enterprise Vault
Event Category:Index Server
Event ID:7292
Date:2/1/2007
Time:3:48:58 PM
User:N/A
Computer:SERVER
Description:
The index volume has been marked as failed.
Index Volume: 1FCDC3C8EF5E9C0438C9794A522E39AF71110000vaultsite.XXX.XXXX.XXX/Volume:1 (journalarchive01)
Index Volume Path: Y:\index\SERVER\location03\1FCDC3C8EF5E9C0438C9794A522E39AF71110000vaultsite.XXX.XXXXX.XXX
Reference: Makestable


Due to errors accessing the index volume it has been marked as 'failed' to prevent further errors. The index volume will remain inaccessible until it has been repaired.

For more information, see Help and Support Center at http://evevent.veritas.com/rosetta/showevent.asp

any ideas.

Regards
Ciaran
5 REPLIES 5

Michael_Bilsbor
Level 6
Accredited
look at avtrace.log in the index location

is disk space connectivity ok to that drive?

Mojorsn
Level 5
We are seeing this same warning with a few failed Journal indexes.  The avtrace.log has the following:
 
Tue Feb 05 11:08:41.94 2008 (thread:4836) backtrace: backtrace starts:
Tue Feb 05 11:08:41.125 2008 (thread:4836) backtrace: ..\indexlib\dataset.c:344: (errno:22:Invalid argument) (result:0x00000008)
Tue Feb 05 11:08:41.125 2008 (thread:4836) backtrace: ..\indexlib\index.c:3718: (errno:22:Invalid argument) (result:0x00000008)
Tue Feb 05 11:08:41.125 2008 (thread:4836) backtrace: ..\indexlib\index.c:3785: (errno:22:Invalid argument) (result:0x00000008)
Tue Feb 05 11:08:41.125 2008 (thread:4836) backtrace: ..\api\avs_open.c:661: (errno:22:Invalid argument) (result:0x00000008) starting catch block
Tue Feb 05 11:08:41.125 2008 (thread:4836) backtrace: ..\api\avs_open.c:668: (errno:22:Invalid argument) (result:0x00000008) no specific catch clause caught
Tue Feb 05 11:08:41.141 2008 (thread:4836) backtrace: backtrace completed.
Tue Feb 05 11:08:41.141 2008 (thread:4836) avs_makestable: error: File I/O error (can't create output file or shared memory)
Tue Feb 05 11:08:41.141 2008 (thread:4836) avs_getindexversion: locked out
Tue Feb 05 11:08:41.829 2008 (thread:4836) avs_getindexversion: locked out
Tue Feb 05 11:08:41.829 2008 (thread:4836) avs_startdoc: locked out
Tue Feb 05 11:08:41.844 2008 (thread:4836) avs_getindexversion: locked out
Tue Feb 05 11:08:42.438 2008 (thread:4836) avs_getindexversion: locked out
Tue Feb 05 11:08:42.438 2008 (thread:4836) avs_startdoc: locked out
Tue Feb 05 11:08:42.438 2008 (thread:4836) avs_getindexversion: locked out
 
Has anyone seen this before or have any solutions to fix this?
 
Thank you!!

John_Chisari
Level 6
Partner Accredited
Tom
 
Have a look at this technote - http://support.veritas.com/docs/280922 - hopefully will help you out to solve the issue - just guessing but this looks like an anti-virus scanning Index location or OPlocks issue.

jimbo2
Level 6
Partner
Sounds like the /3GB in the boot.ini file.
 
 
 

Mojorsn
Level 5
We have implemented all of the index best practices, have excluded all the pertinent directories from virus scanning, and do not have the 3gb switch set on any of the servers.
 
We found the index corruption occurred weekly right around the time our servers came up after a reboot.  So we believe the problem is from not waiting long enough after we stop the EV services to reboot the server.  Symantec support told us that anytime we reboot the server we should stop all EV services, wait 5-10 minutes, then reboot.
 
The reason for this is if you just reboot the server then the indexing service may not have time to finish committing what it has in memory.  If the indexing service cannot finish its process then it cannot make the index stable and causes index corruption.
 
It seems like this is more of an issue with the newer versions of EV because we never had this problem before.  Hopefully this information makes its way to a technote soon.