All Full-text Catalog Operations Hang

Hi!
I've got a database with one full-text index. Recently, it's started
to misbehave. The other day I was alerted to a problem where the
full-text population had stalled in the PAUSED state after only about
10% of the required rows had been indexed. The machine where this
is running has plenty of RAM and HD space, and CPU consumption
isn't high.
I tried to do a rebuild of the catalog, but this simply hung. In fact,
all
operations on this catalog hang. I've looked at the process
information,
and no locks are in the way. The processes handling the catalog
operations
just seem to get stuck in the runnable state. Killing these
hung processes doesn't make them go away.
It's a SQL Server 2000 installation. The machine has been rebooted
since the problem was originally discovered, but the hanging
problem remains.
I know this is a long shot, but a few weeks ago we had trouble
when a Windows Indexing Service catalog became corrupted. Could
this have any bearing on the SQL Server problem?
If you need any more information, I'm happy to supply it.
Any help appreciated!
richard
richardhagen
richardhagen's Profile: http://www.dbtalk.net/m100
View this thread: http://www.dbtalk.net/t296815
While there are some dependencies between indexing services and SQL Full
Text Search, the catalog corruption of an indexing services catalog should
not impact SQL FTS. Please review the gatherer log for reasons as to why the
population paused. Note that if you are running on a laptop your population
will pause if you go on battery power.
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
"richardhagen" <richardhagen.25oid0@.no-mx.forums.yourdomain.com.au> wrote in
message news:richardhagen.25oid0@.no-mx.forums.yourdomain.com.au...
> Hi!
> I've got a database with one full-text index. Recently, it's started
> to misbehave. The other day I was alerted to a problem where the
> full-text population had stalled in the PAUSED state after only about
> 10% of the required rows had been indexed. The machine where this
> is running has plenty of RAM and HD space, and CPU consumption
> isn't high.
> I tried to do a rebuild of the catalog, but this simply hung. In fact,
> all
> operations on this catalog hang. I've looked at the process
> information,
> and no locks are in the way. The processes handling the catalog
> operations
> just seem to get stuck in the runnable state. Killing these
> hung processes doesn't make them go away.
> It's a SQL Server 2000 installation. The machine has been rebooted
> since the problem was originally discovered, but the hanging
> problem remains.
> I know this is a long shot, but a few weeks ago we had trouble
> when a Windows Indexing Service catalog became corrupted. Could
> this have any bearing on the SQL Server problem?
> If you need any more information, I'm happy to supply it.
> Any help appreciated!
> richard
>
> --
> richardhagen
> richardhagen's Profile: http://www.dbtalk.net/m100
> View this thread: http://www.dbtalk.net/t296815
>
|||Hi!
Thanks for the reply (and sorry for my slowness in coming back).
I've looked at the gatherer logs, and they don't reveal anything
about why full-text indexing has gotten stuck in the paused state.
I'll attach the last two logs.
At the moment we're in the invidious position of simply not being able
to operate on full-text things at all in SQL Server.
Here's what's known:
In SQL Server:
* Attempting to operate on the full-text catalog or the full-text
indexes on
the our full-text indexed tables in any way causes things to hang. If
Enterprise Manager is being used, it hangs. If Query Analyser is being
used,
it hangs.
* The hanging processes aren't being blocked by locks on database
objects.
They seem to just sit in the runnable state, waiting.
* Killing the hung processes within Enterprise Manager doesn't clear
them.
* A hung instance of Enterprise Manager or Query Analyser needs to be
killed via the Windows Task Manager.
As always, any help appreciated!
richard
1
2
+---+
|Filename: gthrlog.4.txt |
|Download: http://www.dbtalk.net/a2 |
+---+
richardhagen
richardhagen's Profile: http://www.dbtalk.net/m100
View this thread: http://www.dbtalk.net/t296815