Today I accidentally ran migrations on a production environment that shouldn't run. Luckily, the table wasn't critical, but it did cause a feature of an app to break.
There is not a straight forward way to "force" a previous migration that already ran via a simple Rake command or something.
Eventually, I found a solution inspired by this post on StackOverflow: http://stackoverflow.com/questions/753919/run-a-single-migration-file.
Here's what I did to bring back the table by re-running the previous migration.