Moss 2007 Migration [Part2] - Check errorlog file for the reason that full-text catalog became offline and bring it online
In my pervious post I mentioned a Moss 2007 64Bit Migration Experience , well here's the follow up : Ok , so we had an INDEX problem that was inherited from the Sharepoint 2003 Version. The Problem was that we got on our main 'spscontentdb' database:
"Object spscontentdb failed in event OnBackup. For more information, see the error log located in the backup directory. SqlException: The backup of full-text catalog 'ix_SPSPortal_SITE_db' is not permitted because it is not online. Check errorlog file for the reason that full-text catalog became offline and bring it online. Or 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."
Steps take to resolve the problem:
- SELECT * FROM sysfulltextcatalogs - which gave us the FCTATID , NAME , STATUS , PATH. I took a look if the path existed and - No , it didn't exist. so the Index is poiniting to a non exsiting File/Directory. Seeing that most of the Articles I came accross told me to remove the index I have decided to take this corse of action - drop the index.
- Ok, now I have to drop the index. Have it's name did the following: DROP FULLTEXT CATALOG ix_SPSPortal_SITE_db. Where "ix_SPSPortal_SITE_db" is the name of the catalog.
- Now try again to backup the Farm. Don't forget that the backup directory name should be a UNC path for example \\xmoss\backup\ , and that the User who runs the SqlServer Service has write permission
- don't forget the Complete reference of all STSADM operations (with parameters) in MOSS 2007