Running a repair on a data file should be reserved as a last resort and should typically only be carried out if no backups exist to recover from -- however, sometimes a repair is the only option. In these situations it is important to remember that sometimes the first pass of a repair does not fix everything, and that if after finishing a repair if issues are still reported within the database then it can be beneficial to run a subsequent repair immediately following the last repair. Pay attention to the number of records and or errors being reported because sometimes it can take a couple repairs to get a data file back to a clean bill of health.

At this same time -- it is a good idea to take a moment to re-evaluate the backup stratgey and re-enable it so that if another issue occurs in the future you will be able to recover using the backup files instead of relying on the repair feature.