How to fix P3002: The attempted migration was rolled back: {database_error} in Prisma

Production migration strategies: In production environments, you may need to manually complete partially applied migrations. If a migration partially succeeded before rolling back, inspect the database state carefully. You might need to manually revert some changes before marking the migration as rolled back.

Shadow database and development: Prisma uses a shadow database during development to detect schema drift and validate migrations. If your shadow database lacks necessary permissions or resources, migrations may fail. Ensure the shadow database has the same capabilities as your main database.

Handling enum changes: PostgreSQL cannot alter enum types within a transaction. If you're adding or removing enum values, you may need to split the migration into multiple steps or use a workaround that creates a new enum type and migrates data outside the transaction.

Baseline migrations: If you're integrating Prisma Migrate into an existing database, use prisma migrate resolve --applied to mark initial migrations as already applied without running them. This prevents rollbacks due to already-existing schema elements.

Multi-instance deployments: In environments with multiple application instances, ensure only one instance runs migrations at a time. Use deployment orchestration tools to sequence migrations before scaling up instances, or implement migration locks to prevent concurrent execution.

Down migrations: While Prisma Migrate doesn't natively support down migrations, you can use prisma migrate diff to generate a rollback SQL script. Store these alongside your migrations for emergency rollback scenarios in production.