prisma2 migrate Error: There are more migrations in the database than locally

This is due to a mismatch between the migrations that were executed against the database and the migrations in your prisma/migrations folder.

This happens under the following circumstances:

1. Create a migration with prisma2 migrate save --name “init” --experimental
2. Execute the migration with prisma2 migrate up --experimental
3. Delete the migration files in your prisma/migrations folder
4. Try to run prisma2 migrate save --name “new-migration” --experimental

At step 4 you will see that error.

Prisma keeps track of the executed migrations in the database in a table called _Migration.

To solve the problem try to delete the _Migration table in the database. With SQLite you can do it as follows:

sqlite3 prisma/dev.db "delete from _Migration"

If that doens't work, you need to recreate the database. If you’re using sqlite, delete the prisma/dev.db file (you will lose all data in the database).

To prevent this in the future, make sure that you start with a clean database and if you reuse the same database avoid deleting migration files (in prisma/migrations after they’ve been executed.

this happens when there are a conflict with the schema.Prisma file and the database which you have used migration you have used the old database and there is a table witch his name _Migration how to solve so please try to drop him by user interface or command line name_database delete from _Migration and try to exec yarn prisma migrate save --experimental or prisma2 migrate save --name “new-migration” --experimental it should be work