Not really, your only choice is to run DBCC CHECKDB with repair_allow_data_loss option. The optimum solution would have been to restore from a previous database backup prior to the corruption, and if there where t-log backups to restore those as well up until the corruption.