well.... I don't know what the deal was exactly except that it appears to have been an incomplete or corrupted restore from the production db to the "migration" db.... tonight...