Posted April 6Apr 6 During the upgrade from 4.7.20 to 5.0.5, I was ask to manually ALTER the database. But when I ran the command, it said that the key already exist.I tried running the command automatically using the upgrader. It displayed the message:"Upgrading database (Core: Upgrade ID 500001-31). Please wait while we transfer you..."After about 30 minutes, the CPU usage on the server dropped to 0, so I assumed the process was stuck. I closed the tab and accessed the upgrader in a new tab.I was able to resume the upgrade, but it prompted me to run a new command manually again:I got the same error as before, but clicking "Try to run automatically" resolved it quickly. I continued using "Try to run automatically", and the upgrade completed successfully.Now I'm unsure whether I should manually run the command and ignore the duplicate key error, or run it automatically through the upgrader and risk a timeout.This was done on a test install.
April 6Apr 6 35 minutes ago, Donnie95 said:I continued using "Try to run automatically", and the upgrade completed successfully.If the upgrade is completed successfully and there are no errors further then all is fine imo.
April 6Apr 6 Author 8 minutes ago, Miss_B said:If the upgrade is completed successfully and there are no errors further then all is fine imo.Yeah, but it almost timed out when I ran the command automatically (Big table), and I'm getting duplicate errors when I run it manually.
April 6Apr 6 10 minutes ago, Donnie95 said:Yeah, but it almost timed out when I ran the command automatically (Big table), and I'm getting duplicate errors when I run it manually.Did you get more duplicate errors than the one you quoted in your previous post? Would it be possible to post the error messages and the queries that were recommended to be run in a text format rather than a screenshot? They make for a better read that way imo.
April 6Apr 6 Author 46 minutes ago, Miss_B said:Did you get more duplicate errors than the one you quoted in your previous post? Would it be possible to post the error messages and the queries that were recommended to be run in a text format rather than a screenshot? They make for a better read that way imo.Only two duplicate errors, but I also encountered another error. When it asked me to run an ALTER command, I ran it manually without any errors. I confirmed that I had executed it successfully, but the upgrade process got stuck. I had to click "Try to run automatically." to continue. I might wait until version 5.0.10+ before upgrading.
