User Tools

Site Tools


how_to_resume_a_failed_upgrade

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
how_to_resume_a_failed_upgrade [2020/07/28 17:27]
admin
how_to_resume_a_failed_upgrade [2020/07/28 17:28] (current)
admin
Line 5: Line 5:
 1. Make note of which version of the upgrade patches that halted. In this example, we will assume 2.0.sql was the patch that halted with an error during upgrade. 1. Make note of which version of the upgrade patches that halted. In this example, we will assume 2.0.sql was the patch that halted with an error during upgrade.
  
-2. Start by deleting all patches before the failing patch prior to (in this case) 2.0. All prior patches should have been successfully processed until this one, and should not be applied again. If it was the .php patch that failed, you can safely delete the .sql patch, as the SQL patch is always processed before the php patch.+2. Start by deleting all patches before the failing patch prior to e.g. 2.0. All prior patches should have been successfully processed until this one, and should not be applied again. If it was the .php patch that failed, you can safely delete the .sql patch, as the SQL patch is always processed before the php patch.
  
-3. Edit the failing patch 2.0.sql and remove all commands before the failing command that halted the process, as they are already applied. Once more, we do not want to apply the successful commands again.+3. Edit the failing patch and remove all commands before the failing command that halted the process, as they have already been applied.
  
 4. Solve the cause for why the command halted. Usually it's due to conflicting data in the database. 4. Solve the cause for why the command halted. Usually it's due to conflicting data in the database.
how_to_resume_a_failed_upgrade.txt ยท Last modified: 2020/07/28 17:28 by admin