# Schema\_migrations table not created

**URL:** <https://www.ruby-forum.com/t/schema-migrations-table-not-created/176824>\
**Category:** Deployment\
**Created:** [October 6, 2009, 6:31pm UTC](https://www.ruby-forum.com/t/schema-migrations-table-not-created/176824 "2009-10-06T18:31:59Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![terrii](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/a587f6/32.png) [@terrii](https://www.ruby-forum.com/u/terrii)\
**Post date:** [October 6, 2009, 6:31pm UTC](https://www.ruby-forum.com/t/schema-migrations-table-not-created/176824/1 "2009-10-06T18:31:59Z")

</div>

Hi - We’ve got a Rails application/Oracle database that we just  
upgraded from Rails 1.2 to 2.3.2 We did not have any database  
structural modifications, and thus did not need to run any  
migrations. However, the deployment scripts by default include  
command cap deploy:migrations. Instead of recognizing that there  
were no new migrations, Rails wanted to start over and  
run all migrations. The schema\_info table was there, but no  
schema\_migrations table. When was the schema\_info table supposed  
to be replaced with a schema\_migrations table; shouldn’t it have  
happened automatically?

Should I now go in and delete the schema\_info table and manually  
create and populate a schema\_migrations table?