Same issue here. Upgraded via Docker to 35.x and getting the below error. Any assistance would be appreciated. Running on UgreenOS (Debian) and MariaDB.
root@xxxxxxxxxxxx:/var/www/html# php ./occ upgrade
Setting log level to debug
Updating database schema
Updated database
OCP\DB\Schema\SchemaException: The table with name "nextcloud.oc_sharing_classmap" already exists.
Update failed
Maintenance mode is kept active
Resetting log level
The database schema does not match what is expected for the installed version:
- missing table 'oc_federated_invites'
- unexpected table 'oc_ocm_token_map'
Run "occ db:schema:check -v" for details.
root@xxxxxxxxxxxx:/var/www/html# ./occ db:schema:check -v
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
missing table 'oc_federated_invites'
unexpected table 'oc_ocm_token_map'
I started this thread to report about a specific problem. Please stop this discussion that covers a much broader spectrum. You can start an own thread.
I am so sorry. Didn’t know you own it before I hijacked it. However if you read this thread, you’d not only find the cause, but also a solution to your problem and a warning to not become too eager. You are welcome.
The original post is about missing indexes. One of the early mentioned problems is about the oc_appconfig table that is missing indexes. In my installation, this is also the only error - no unwanted tables.
That is AFAIK a core table, not created by an extra app. I don’t see a sollotion for this problem in this (long) thread.
Yeah, the thread got a little out of hand, and I certainly played my part in that. I don’t really feel bad about it, though, because… well, a) OP didn’t fill out the support template, and then everyone who had some random issue related to their database started posting here.
But apparently that wasn’t enough, so of course someone also had to use the opportunity to turn it into a general discussion and bring the term “enshittification” into it. Sorry, but at that point, the thread was pretty much doomed anyway.