I have a full text index scheduled at every night in SQL server 2000.
Normally the status on the full-text catalog will either "Idle" or
"Incremental population in progress". But today I got "shut down". This
happened to one of our other server yesterday too. Since this happens
more often now, I want to find out why and what to do to prevent it
from happening again. I went to system Application event log. This is
the error description I got.
"The critical error 9 occurred in project <SQLServer SQL0000800007>.
Error: 8007054e - Unable to complete the requested operation because of
either a catastrophic media failure or a data structure corruption on
the disk. . The project has been shut down. The system is probably low
on the resources. Free up resources and restart the service.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp."
Event info:
Event Type: Error
Event Source: Microsoft Search
Event Category: Gatherer
We have almost 300G of free disk space. So the system can't be low on
resource. Anyone knows why this is happening? Any help will be greatly
appreciated.
Thanks in advance!
By default fulltext used a directory on your system drive - possibly
C:\WINDOWS\Temp\gthrsvc. Could there be enough space on your system drive as
well.
You could also be doing a master merge which requires at least twice the
size of your largest catalog to complete. How large is your largest catalog?

Signature
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
>I have a full text index scheduled at every night in SQL server 2000.
> Normally the status on the full-text catalog will either "Idle" or
[quoted text clipped - 24 lines]
>
> Thanks in advance!
discover - 08 Nov 2006 14:52 GMT
C drive has more than 17G free space. I don't know which extension is
for catalog itself. But the whole directory for that catalog is only
81M. I don't think the disk space is an issue here. I just have a
"Shutdown" status on that again from last run.
Hilary Cotter - 08 Nov 2006 15:02 GMT
Can you send me the gatherer logs or attach them here?

Signature
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
>C drive has more than 17G free space. I don't know which extension is
> for catalog itself. But the whole directory for that catalog is only
> 81M. I don't think the disk space is an issue here. I just have a
> "Shutdown" status on that again from last run.
discover - 14 Nov 2006 17:38 GMT
It seems that Veritas back up locks the file. We set it to not use the
lock on the file. It seems to went well last night.