
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
> SP1 is already applied on SQL Server 2005.
> Displayed version number is 9.0.2047.
[quoted text clipped - 30 lines]
>> > 'J:\BOL_PROD_DATA\MSSQL.4\MSSQL\FTData\Bihr_FullTextCatalog\SQL.HDR' at
>> > 'fulltext.cpp'(529).
Thank you for your replies!
There is another error message in the maintenance plan history I didn't see
before.
It seems that the fulltext catalog is offline sometimes which would explain
why the backup could not be done.
But what could turn off the fulltext catalog?
Executing the query "BACKUP DATABASE [BihrOnline2_commerce] TO DISK =
N'K:\\BOL_BACKUPS\\BihrOnline2_commerce\\BihrOnline2_commerce_backup_200609141600.bak'
WITH NOFORMAT, NOINIT, NAME = N'BihrOnline2_commerce_backup_20060914160012',
SKIP, REWIND, NOUNLOAD, STATS = 10 " failed with the following error: "The
backup of the file or filegroup "sysft_Bihr_FTC" is not permitted because it
is not online. BACKUP can be performed by using the FILEGROUP or FILE clauses
to restrict the selection to include only online data. BACKUP DATABASE is
terminating abnormally.". Possible failure reasons: Problems with the query,
"ResultSet" property not set correctly, parameters not set correctly, or
connection not established correctly.
> Actually I just realized we get this error message every time we do a
> transaction log dump. This error seems to be a warning message more than
[quoted text clipped - 34 lines]
> >> > 'J:\BOL_PROD_DATA\MSSQL.4\MSSQL\FTData\Bihr_FullTextCatalog\SQL.HDR' at
> >> > 'fulltext.cpp'(529).
Hilary Cotter - 14 Sep 2006 16:59 GMT
does this apply?
http://support.microsoft.com/kb/923355/en-us

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
> Thank you for your replies!
> There is another error message in the maintenance plan history I didn't
[quoted text clipped - 63 lines]
>> >> > at
>> >> > 'fulltext.cpp'(529).
Mickael Parisot - 14 Sep 2006 18:04 GMT
Not really. The fulltext catalog is working well and the maintenance plan is
working sometimes.
I think that a process is using the fulltext catalog while a rebuild occurs
for example.
In this case, the rebuild would fail and the catalog folder would be erased.
Thus, the backup cannot be done because the fulltext catalog filegroup is
now "OFFLINE".
Am I correct?
> does this apply?
>
[quoted text clipped - 67 lines]
> >> >> > at
> >> >> > 'fulltext.cpp'(529).
Hilary Cotter - 14 Sep 2006 20:45 GMT
I'm not sure. I opened a support incident on this case with Microsoft. We
were getting catalog corruption errors but these were due to something else.
Microsoft wanted us to run a debugger for them and send them the dump but we
were unable to do so. We also run filemon to figure out what was trying to
open the file and it was SQL Server. Microsoft did tell us it was fixed in
SP 1. We still get the errors.
I can reopen the case and get more info for you if you want.

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
> Not really. The fulltext catalog is working well and the maintenance plan
> is
[quoted text clipped - 85 lines]
>> >> >> > at
>> >> >> > 'fulltext.cpp'(529).
Mickael Parisot - 15 Sep 2006 07:52 GMT
Thanks a lot. You are really nice.
I tried something else:
1) Rebuild the fulltext catalog before backup database
2) Shift the backup log after backup database (it was starting at the same
time before)
3) Run filemon to check which process is accessing the fulltext catalog
Filemon indicates that only sqlservr.exe is accessing the fulltext catalog
when rebuild and backup occured.
Right now, the last backups are succesfull. I hope this will continue and it
may give some hints.
> I'm not sure. I opened a support incident on this case with Microsoft. We
> were getting catalog corruption errors but these were due to something else.
[quoted text clipped - 93 lines]
> >> >> >> > at
> >> >> >> > 'fulltext.cpp'(529).
Hilary Cotter - 15 Sep 2006 11:47 GMT
Thanks Mickael, keep us informed.

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
> Thanks a lot. You are really nice.
>
[quoted text clipped - 123 lines]
>> >> >> >> > at
>> >> >> >> > 'fulltext.cpp'(529).
Mickael Parisot - 20 Sep 2006 15:07 GMT
Everything is working fine now.
Rebuilding the fulltext catalog everytime, just before the "backup
database", seems to solve the problem.
> Thanks Mickael, keep us informed.
>
[quoted text clipped - 125 lines]
> >> >> >> >> > at
> >> >> >> >> > 'fulltext.cpp'(529).