You may get one of these errors in your Health Analyzer logs. I am getting it on a database called WSS_Search_SVR-WEB1. What happened was that I had two server in my farm, one of which I decommisioned to move to 64bit before moving to 2010.
The older SVR-WEB1 had the WSS Search database tied too it. But somehow when I decommisioned it, the entry in the objects heirarchy table remained (it became orphaned and the 2010 upgrade checker didn't say jack about them) and now I'm stuck with this weird database that is really OLD and SharePoint 2010 does NOT like. How do I remove it?
As always, I left with resorting to the objects table and doing a 'name like' and 'properties like' query to find anything that was related to the old server. Once I find those things i run the STSADM -o deleteconfigurationobject -id "<object id>" command to remove them.
After removing the orphaned objects, I re-run the Health Analyzer job and the error goes away! Whoot!
Chris