Hi I have the same problem:
Picture of output below. I'm trying to upgrade from 3.9 to 3.10
Regards
Steve
Database error upgrading 3.9 to 3.10
Number of replies: 7
Re: Database error upgrading 3.9 to 3.10
I split this from the original discussion as it did not seem related (except that they were both db errors on upgrade).
Is there any more to this story? Is this what happens when you have a 'clean' working copy of 3.9 and try to upgrade? What I'm getting at is that there was no previous failed upgrade or similar?
Is there any more to this story? Is this what happens when you have a 'clean' working copy of 3.9 and try to upgrade? What I'm getting at is that there was no previous failed upgrade or similar?
Re: Database error upgrading 3.9 to 3.10
Hi Howard
It's a straight forward upgrade. Created new moodle folder and uploaded code, changed config.php to point to correct database, added theme KLASS (in theme folder) and CUSTOMCERT (in mod folder) opened the site, all goes great no problems until the final update screen and when pressed continue, this pops up.
It's a straight forward upgrade. Created new moodle folder and uploaded code, changed config.php to point to correct database, added theme KLASS (in theme folder) and CUSTOMCERT (in mod folder) opened the site, all goes great no problems until the final update screen and when pressed continue, this pops up.
I'm going to try the upgrade to 3.9.3 as in the other forum to see if the error still appears.
Steve
Re: Database error upgrading 3.9 to 3.10
I thought the error messages are self-explanatory. The DBMS is refusing to create a table which already exists.
The name of that table is odd: mdl_paygw_paypal. Moodle core doen't have such a table. The final line of the error message, "call to upgrade_noncore()" supports this.
The name of that table is odd: mdl_paygw_paypal. Moodle core doen't have such a table. The final line of the error message, "call to upgrade_noncore()" supports this.
Re: Database error upgrading 3.9 to 3.10
It's a new thing in 3.10. Payment gateways were abstracted out so that you have things other than PayPal. So, it's a legitimate, new database in 3.10
The only way it can already exist is if it's already been created (obviously) which would imply the upgrade script being run twice. The usual reason for that is restarting after failure.
The only way it can already exist is if it's already been created (obviously) which would imply the upgrade script being run twice. The usual reason for that is restarting after failure.
Re: Database error upgrading 3.9 to 3.10
Hi Howard
Well I updated to version 3.9.3, no problems at all. Then started the upgrade from 3.9.3 to 3.10+ and got the following again:
Steve
Well I updated to version 3.9.3, no problems at all. Then started the upgrade from 3.9.3 to 3.10+ and got the following again:
Steve
Re: Database error upgrading 3.9 to 3.10
To expand on what Howard said: payment gateways were introduced in Moodle 3.10 so the table mdl_paygw_paypal should not exist in the Moodle 3.9 site's database. You can check if it exists with the SQL query:
SHOW TABLES LIKE 'mdl_paygw_paypal';
Nothing should be returned. If this table does already exist you can remove it with DROP TABLE mdl_paygw_paypal (always make a backup of the database before making changes like this).
This kind of problem normally happens if an attempted upgrade has been rolled back to the previous version. The default behaviour when MySQL or MariaDB restores a database is to leave any new tables in place, resulting in this Moodle upgrade error because the table is unexpected.
Re: Database error upgrading 3.9 to 3.10
Hi All
Thank you for your assistance, I located mdl_paygw_paypal in the sql. I dropped the line, started again from 3.9.3 to 3.10+ and it worked perfectly. All good now.
Thanks once again.
Steve
Thank you for your assistance, I located mdl_paygw_paypal in the sql. I dropped the line, started again from 3.9.3 to 3.10+ and it worked perfectly. All good now.
Thanks once again.
Steve