| Groups | Blog | Home |
sql server full text search : Full-text indexing hangs on SQL 7
for one of the larger applications we have, but we're a small company. The main table for the database, which contains the most text fields, only has 10000 rows in it. All-in-all, the indexing is probably only scanning 50000 rows total. The incremental population hangs every few weeks, and I'm trying to find a solution to prevent this. Any suggestions? The server is not the strongest of servers. It's a dual-P3, 1.0 GHz, with a gig of RAM. Yeah yeah, it's weak, but it's what I was given. CPU usage soars when full population is running, but that's during off-hours once-a-week. I'm not sure how much of this is a hardware performance issue. Any suggestions on determining why it hangs? Thanks, Dan
Have you checked the gatherer logs to determine exactly why it is hanging
like this? There may be a message written there. Also are there any messages in the event log from MSSCi? -- Hilary Cotter Looking for a SQL Server replication book? Now available for purchase at: http://www.nwsu.com/0974973602.html [quoted text, click to view] "Dan Tan" <dan.tan@catapult.com> wrote in message news:eWDwvn82EHA.3336@TK2MSFTNGP11.phx.gbl... > We're running full-text indexing on SQL 7.00.1063 (SP4). The database is > for one of the larger applications we have, but we're a small company. > The > main table for the database, which contains the most text fields, only has > 10000 rows in it. All-in-all, the indexing is probably only scanning > 50000 > rows total. > > The incremental population hangs every few weeks, and I'm trying to find a > solution to prevent this. Any suggestions? > > The server is not the strongest of servers. It's a dual-P3, 1.0 GHz, with > a > gig of RAM. Yeah yeah, it's weak, but it's what I was given. CPU usage > soars when full population is running, but that's during off-hours > once-a-week. I'm not sure how much of this is a hardware performance > issue. > > Any suggestions on determining why it hangs? > > Thanks, > Dan > >
Hi Hillary,
Thanks for your reply! Hm, yes there are... I'm rebuilding right now, and two warnings or info messages have appeared. * Microsoft Search generates a warning, "One or more errors for Gatherer project <SQLServer SQL0006900006> logged to file <h:\MSSQL7\FTDATA\SQLServer\GatherLogs\SQL0006900006.2.gthr>." * Then, Mssci generates an info message in the event log, "Content index corruption detected in component ChangeLog5 in catalog d:\mssql7\ftdata\sql0006900006\build\indexer\cifiles\. Stack trace is... (etc etc.....)" * When I open the SQL0006900006.2.gthr file, it says, d1af8a5c 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/00002426 8000000c 0 8004111b d232abb2 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/00002427 8000000c 0 8004111b d23e9774 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/00002425 8000000c 0 8004111b d240f9ce 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/00002423 8000000c 0 8004111b d245be82 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/00002424 8000000c 0 8004111b d24820dc 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/00002428 8000000c 0 8004111b d24ce590 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/0000242A 8000000c 0 8004111b I don't know how to interpret the .gthr log file. Is that the right log file to look at? Dan [quoted text, click to view] "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message news:O0sClt82EHA.2876@TK2MSFTNGP12.phx.gbl... > Have you checked the gatherer logs to determine exactly why it is hanging > like this? There may be a message written there. > > Also are there any messages in the event log from MSSCi? > > -- > Hilary Cotter > Looking for a SQL Server replication book? > Now available for purchase at: > http://www.nwsu.com/0974973602.html > > "Dan Tan" <dan.tan@catapult.com> wrote in message > news:eWDwvn82EHA.3336@TK2MSFTNGP11.phx.gbl... > > We're running full-text indexing on SQL 7.00.1063 (SP4). The database is > > for one of the larger applications we have, but we're a small company. > > The > > main table for the database, which contains the most text fields, only has > > 10000 rows in it. All-in-all, the indexing is probably only scanning > > 50000 > > rows total. > > > > The incremental population hangs every few weeks, and I'm trying to find a > > solution to prevent this. Any suggestions? > > > > The server is not the strongest of servers. It's a dual-P3, 1.0 GHz, with > > a > > gig of RAM. Yeah yeah, it's weak, but it's what I was given. CPU usage > > soars when full population is running, but that's during off-hours > > once-a-week. I'm not sure how much of this is a hardware performance > > issue. > > > > Any suggestions on determining why it hangs? > > > > Thanks, > > Dan > > > > > >
The Stack trace error you are getting means an access violation. You might
want to contact Microsoft PSS on this one. -- Hilary Cotter Looking for a SQL Server replication book? Now available for purchase at: http://www.nwsu.com/0974973602.html [quoted text, click to view] "Dan Tan" <dan.tan@catapult.com> wrote in message news:%23o4a1A92EHA.3000@TK2MSFTNGP15.phx.gbl... > Hi Hillary, > Thanks for your reply! > Hm, yes there are... I'm rebuilding right now, and two warnings or info > messages have appeared. > > * Microsoft Search generates a warning, "One or more errors for Gatherer > project <SQLServer SQL0006900006> logged to file > <h:\MSSQL7\FTDATA\SQLServer\GatherLogs\SQL0006900006.2.gthr>." > > * Then, Mssci generates an info message in the event log, "Content index > corruption detected in component ChangeLog5 in catalog > d:\mssql7\ftdata\sql0006900006\build\indexer\cifiles\. Stack trace is... > (etc etc.....)" > > * When I open the SQL0006900006.2.gthr file, it says, > > d1af8a5c 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/00002426 8000000c 0 > 8004111b > d232abb2 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/00002427 8000000c 0 > 8004111b > d23e9774 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/00002425 8000000c 0 > 8004111b > d240f9ce 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/00002423 8000000c 0 > 8004111b > d245be82 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/00002424 8000000c 0 > 8004111b > d24820dc 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/00002428 8000000c 0 > 8004111b > d24ce590 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/0000242A 8000000c 0 > 8004111b > > I don't know how to interpret the .gthr log file. Is that the right log > file to look at? > > Dan > > > "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message > news:O0sClt82EHA.2876@TK2MSFTNGP12.phx.gbl... >> Have you checked the gatherer logs to determine exactly why it is hanging >> like this? There may be a message written there. >> >> Also are there any messages in the event log from MSSCi? >> >> -- >> Hilary Cotter >> Looking for a SQL Server replication book? >> Now available for purchase at: >> http://www.nwsu.com/0974973602.html >> >> "Dan Tan" <dan.tan@catapult.com> wrote in message >> news:eWDwvn82EHA.3336@TK2MSFTNGP11.phx.gbl... >> > We're running full-text indexing on SQL 7.00.1063 (SP4). The database > is >> > for one of the larger applications we have, but we're a small company. >> > The >> > main table for the database, which contains the most text fields, only > has >> > 10000 rows in it. All-in-all, the indexing is probably only scanning >> > 50000 >> > rows total. >> > >> > The incremental population hangs every few weeks, and I'm trying to >> > find > a >> > solution to prevent this. Any suggestions? >> > >> > The server is not the strongest of servers. It's a dual-P3, 1.0 GHz, > with >> > a >> > gig of RAM. Yeah yeah, it's weak, but it's what I was given. CPU >> > usage >> > soars when full population is running, but that's during off-hours >> > once-a-week. I'm not sure how much of this is a hardware performance >> > issue. >> > >> > Any suggestions on determining why it hangs? >> > >> > Thanks, >> > Dan >> > >> > >> >> > >
When I select "properties" for the "Full-Text Search" support service under
Enterprise Manager, it tells me that the temporary directory is pointing to the system drive, which doesn't have much space left on it. Could this be causing a problem during population? Regardless, I'd like to move the temp directory for the Full-Text Search to a drive that has plenty of free space. Is there a way to do this from within SQL management tools/stored procedures? I see where it's defined in the Registry, but would rather try doing it "nicely" first. I'm hoping to resolve this without a support call if necessary. I don't have authority to pay for a support call. And I doubt I'll be able to reach someone who can authorize it within a reasonable time period. :-( Dan [quoted text, click to view] "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message news:u7obfG92EHA.936@TK2MSFTNGP12.phx.gbl... > The Stack trace error you are getting means an access violation. You might > want to contact Microsoft PSS on this one. > > -- > Hilary Cotter > Looking for a SQL Server replication book? > Now available for purchase at: > http://www.nwsu.com/0974973602.html > > "Dan Tan" <dan.tan@catapult.com> wrote in message > news:%23o4a1A92EHA.3000@TK2MSFTNGP15.phx.gbl... > > Hi Hillary, > > Thanks for your reply! > > Hm, yes there are... I'm rebuilding right now, and two warnings or info > > messages have appeared. > > > > * Microsoft Search generates a warning, "One or more errors for Gatherer > > project <SQLServer SQL0006900006> logged to file > > <h:\MSSQL7\FTDATA\SQLServer\GatherLogs\SQL0006900006.2.gthr>." > > > > * Then, Mssci generates an info message in the event log, "Content index > > corruption detected in component ChangeLog5 in catalog > > d:\mssql7\ftdata\sql0006900006\build\indexer\cifiles\. Stack trace is... > > (etc etc.....)" > > > > * When I open the SQL0006900006.2.gthr file, it says, > > > > d1af8a5c 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/00002426 8000000c 0 > > 8004111b > > d232abb2 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/00002427 8000000c 0 > > 8004111b > > d23e9774 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/00002425 8000000c 0 > > 8004111b > > d240f9ce 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/00002423 8000000c 0 > > 8004111b > > d245be82 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/00002424 8000000c 0 > > 8004111b > > d24820dc 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/00002428 8000000c 0 > > 8004111b > > d24ce590 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/0000242A 8000000c 0 > > 8004111b > > > > I don't know how to interpret the .gthr log file. Is that the right log > > file to look at? > > > > Dan > > > > > > "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message > > news:O0sClt82EHA.2876@TK2MSFTNGP12.phx.gbl... > >> Have you checked the gatherer logs to determine exactly why it is hanging > >> like this? There may be a message written there. > >> > >> Also are there any messages in the event log from MSSCi? > >> > >> -- > >> Hilary Cotter > >> Looking for a SQL Server replication book? > >> Now available for purchase at: > >> http://www.nwsu.com/0974973602.html > >> > >> "Dan Tan" <dan.tan@catapult.com> wrote in message > >> news:eWDwvn82EHA.3336@TK2MSFTNGP11.phx.gbl... > >> > We're running full-text indexing on SQL 7.00.1063 (SP4). The database > > is > >> > for one of the larger applications we have, but we're a small company. > >> > The > >> > main table for the database, which contains the most text fields, only > > has > >> > 10000 rows in it. All-in-all, the indexing is probably only scanning > >> > 50000 > >> > rows total. > >> > > >> > The incremental population hangs every few weeks, and I'm trying to > >> > find > > a > >> > solution to prevent this. Any suggestions? > >> > > >> > The server is not the strongest of servers. It's a dual-P3, 1.0 GHz, > > with > >> > a > >> > gig of RAM. Yeah yeah, it's weak, but it's what I was given. CPU > >> > usage > >> > soars when full population is running, but that's during off-hours > >> > once-a-week. I'm not sure how much of this is a hardware performance > >> > issue. > >> > > >> > Any suggestions on determining why it hangs? > >> > > >> > Thanks, > >> > Dan > >> > > >> > > >> > >> > > > > > >
Dan,
Depending upon what is the content of the columns you are FT Indexing - plain text or MS Word documents in an IMAGE datatype as well as the size of the documents, this could be a factor. There is no *nice* way of changing this parameter, I'm sad to say, other than to make a change to the following Registry key and value change: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search\1.0\Gathering Manager TempPath = C:\WINNT\TEMP\gthrsvc You would need to change the TempPath value to your desired location and most likely stop & restart the MSSearch service. Hope that helps! John [quoted text, click to view] "Dan Tan" <dan.tan@catapult.com> wrote in message news:eGsNns92EHA.2608@TK2MSFTNGP10.phx.gbl... > When I select "properties" for the "Full-Text Search" support service under > Enterprise Manager, it tells me that the temporary directory is pointing to > the system drive, which doesn't have much space left on it. > > Could this be causing a problem during population? > > Regardless, I'd like to move the temp directory for the Full-Text Search to > a drive that has plenty of free space. Is there a way to do this from > within SQL management tools/stored procedures? I see where it's defined in > the Registry, but would rather try doing it "nicely" first. > > I'm hoping to resolve this without a support call if necessary. I don't > have authority to pay for a support call. And I doubt I'll be able to reach > someone who can authorize it within a reasonable time period. :-( > > Dan > > > "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message > news:u7obfG92EHA.936@TK2MSFTNGP12.phx.gbl... > > The Stack trace error you are getting means an access violation. You might > > want to contact Microsoft PSS on this one. > > > > -- > > Hilary Cotter > > Looking for a SQL Server replication book? > > Now available for purchase at: > > http://www.nwsu.com/0974973602.html > > > > "Dan Tan" <dan.tan@catapult.com> wrote in message > > news:%23o4a1A92EHA.3000@TK2MSFTNGP15.phx.gbl... > > > Hi Hillary, > > > Thanks for your reply! > > > Hm, yes there are... I'm rebuilding right now, and two warnings or info > > > messages have appeared. > > > > > > * Microsoft Search generates a warning, "One or more errors for Gatherer > > > project <SQLServer SQL0006900006> logged to file > > > <h:\MSSQL7\FTDATA\SQLServer\GatherLogs\SQL0006900006.2.gthr>." > > > > > > * Then, Mssci generates an info message in the event log, "Content index > > > corruption detected in component ChangeLog5 in catalog > > > d:\mssql7\ftdata\sql0006900006\build\indexer\cifiles\. Stack trace > is... > > > (etc etc.....)" > > > > > > * When I open the SQL0006900006.2.gthr file, it says, > > > > > > d1af8a5c 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/00002426 8000000c 0 > > > 8004111b > > > d232abb2 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/00002427 8000000c 0 > > > 8004111b > > > d23e9774 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/00002425 8000000c 0 > > > 8004111b > > > d240f9ce 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/00002423 8000000c 0 > > > 8004111b > > > d245be82 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/00002424 8000000c 0 > > > 8004111b > > > d24820dc 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/00002428 8000000c 0 > > > 8004111b > > > d24ce590 1c4dbcd MSSQL://LOCALHOST/69.843150049.304/0000242A 8000000c 0 > > > 8004111b > > > > > > I don't know how to interpret the .gthr log file. Is that the right > log > > > file to look at? > > > > > > Dan > > > > > > > > > "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message > > > news:O0sClt82EHA.2876@TK2MSFTNGP12.phx.gbl... > > >> Have you checked the gatherer logs to determine exactly why it is > hanging > > >> like this? There may be a message written there. > > >> > > >> Also are there any messages in the event log from MSSCi? > > >> > > >> -- > > >> Hilary Cotter > > >> Looking for a SQL Server replication book? > > >> Now available for purchase at: > > >> http://www.nwsu.com/0974973602.html > > >> > > >> "Dan Tan" <dan.tan@catapult.com> wrote in message > > >> news:eWDwvn82EHA.3336@TK2MSFTNGP11.phx.gbl... > > >> > We're running full-text indexing on SQL 7.00.1063 (SP4). The > database > > > is > > >> > for one of the larger applications we have, but we're a small > company. > > >> > The > > >> > main table for the database, which contains the most text fields, > only > > > has > > >> > 10000 rows in it. All-in-all, the indexing is probably only scanning > > >> > 50000 > > >> > rows total. > > >> > > > >> > The incremental population hangs every few weeks, and I'm trying to > > >> > find > > > a > > >> > solution to prevent this. Any suggestions? > > >> > > > >> > The server is not the strongest of servers. It's a dual-P3, 1.0 GHz, > > > with > > >> > a > > >> > gig of RAM. Yeah yeah, it's weak, but it's what I was given. CPU > > >> > usage > > >> > soars when full population is running, but that's during off-hours > > >> > once-a-week. I'm not sure how much of this is a hardware performance > > >> > issue. > > >> > > > >> > Any suggestions on determining why it hangs? > > >> > > > >> > Thanks, > > >> > Dan > > >> > > > >> > > > >> > > >> > > > > > > > > > > > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |