The two records are the same; however, when looking at the created_at/updated_at fields, there is one from January 20 (which makes sense) and one from December 6.
This is probably the date you made the first attempt to upgrade, and I suspect the way you are restoring the backup is not removing the newly created measures table.
Can you try again, but make sure to truncate or drop the measures table before starting the upgrade?
I’m not an expert on that, but I believe you would have to drop the entire db before restoring. The --clean option will only drop and re-create the tables (or other objects) that are part of the dump. So in this case it didn’t touch the measures table which doesn’t exist in the dump.
Hello @HaNs_Neefs, @haugsrud and @AngelaMarie,
We are trying to identify why the migration is failing with an out of memory error. Are you using the community plugin dependency-check or any other custom plugin? Thanks.