All,
Forgive me for the length of this post, but I need a help resolving the root cause of a Full Text Catalog problem I recently had and hopefully finding an easier solution than the one I came up with. Here’s some background on the problem.
Our database as about 70 tables that are full text enabled. Our catalog stopped populating some time ago. Data that existed in the catalog could still be searched, but new records added to the DB were not searchable.
I tried numerous times to start full population but it simply refused to populate. I found this error in the Event Viewer: “Error: 80041201- The object was not found”.
I googled this error and found several suggestions, none of them resolved my problem though.
I tired rebuilding the catalog, but this made the problem worse. The rebuild drop the existing catalog, but still would not populate the new one. So now there was no search functionality at all.
I decide to rebuild the catalog this time using only one of the 70 tables. Each table I tried would not populate, and it would get the same error in the Event Viewer.
This went on until I finally came across a table that would populate without any errors. This particular table had been recently modified using the Enterprise Manager. I had increased the character length of one of the columns. This incidentally, was not an indexed column.
Once I realized this I decided to modify one of the other tables to see what would happen. After modification, the full text catalog was able to populate on that table.
I looked at the script for a table modification in EM. I thought maybe it was the index being dropped and recreated that was fixing the problem. I tried that on another table, but it didn’t fix the problem.
So the solution seems to be; to use EM to modify the tables. So I went through and did this for all 70 tables. After that I started full population on the catalog and it was able to populate (took 8 hours).
Our full text searching is working, and is better than ever now.
My question is, what caused this and why does using EM to modify the table fix the problem? Is there something else I could have done to fix this? Modifying the tables took about an hour and half. I have test databases that still have same problem; I need to fix those as well.
Any help or suggestions would be greatly appreciated.
Thanks in advance
Charles.
Forgive me for the length of this post, but I need a help resolving the root cause of a Full Text Catalog problem I recently had and hopefully finding an easier solution than the one I came up with. Here’s some background on the problem.
Our database as about 70 tables that are full text enabled. Our catalog stopped populating some time ago. Data that existed in the catalog could still be searched, but new records added to the DB were not searchable.
I tried numerous times to start full population but it simply refused to populate. I found this error in the Event Viewer: “Error: 80041201- The object was not found”.
I googled this error and found several suggestions, none of them resolved my problem though.
I tired rebuilding the catalog, but this made the problem worse. The rebuild drop the existing catalog, but still would not populate the new one. So now there was no search functionality at all.
I decide to rebuild the catalog this time using only one of the 70 tables. Each table I tried would not populate, and it would get the same error in the Event Viewer.
This went on until I finally came across a table that would populate without any errors. This particular table had been recently modified using the Enterprise Manager. I had increased the character length of one of the columns. This incidentally, was not an indexed column.
Once I realized this I decided to modify one of the other tables to see what would happen. After modification, the full text catalog was able to populate on that table.
I looked at the script for a table modification in EM. I thought maybe it was the index being dropped and recreated that was fixing the problem. I tried that on another table, but it didn’t fix the problem.
So the solution seems to be; to use EM to modify the tables. So I went through and did this for all 70 tables. After that I started full population on the catalog and it was able to populate (took 8 hours).
Our full text searching is working, and is better than ever now.
My question is, what caused this and why does using EM to modify the table fix the problem? Is there something else I could have done to fix this? Modifying the tables took about an hour and half. I have test databases that still have same problem; I need to fix those as well.
Any help or suggestions would be greatly appreciated.
Thanks in advance
Charles.
