Upgrade to Nextcloud Hub 10 (31.0.0) Incorrect row format found in your database

[SckyzO]

After upgrading to Nextcloud 31.0.0, I got the following message:

✅ Solution
I fixed the issue by applying the following procedure:

source .env # assumed: contains MYSQL_ROOT_PASSWORD
DBCONTAINER=nextcloud-db #based on your compose.yaml
DBNAME=nextcloud #based on your compose.yaml

docker exec -i $DBCONTAINER mariadb -u root -p$MYSQL_ROOT_PASSWORD -N -e "
  SELECT CONCAT('ALTER TABLE ', TABLE_NAME, ' ROW_FORMAT=DYNAMIC;')
  FROM information_schema.tables
  WHERE table_schema = '$DBNAME' AND ROW_FORMAT != 'Dynamic';" \
| docker exec -i $DBCONTAINER mariadb -u root -p$MYSQL_ROOT_PASSWORD $DBNAME

This worked for me. Hope it helps someone else facing the same issue! 🙌

[waja]

This is indeed not a specific problem to this container image but in general for Nextcloud. It was noted already at https://help.nextcloud.com/t/upgrade-to-nextcloud-hub-10-31-0-0-incorrect-row-format-found-in-your-database/218366 and should be applied for every affected Nextcloud system.

Thanks for heads up.

[SckyzO]

This is indeed not a specific problem to this container image but in general for Nextcloud. It was noted already at https://help.nextcloud.com/t/upgrade-to-nextcloud-hub-10-31-0-0-incorrect-row-format-found-in-your-database/218366 and should be applied for every affected Nextcloud system.

Thanks for heads up.

Yes, I know, it's just to help people who have this problem 😁
I'll let you close the issue if you want, it's only to trace the correction of the database

[Nightwatch2359]

Thanks a lot SckyzO, you saved my day after slipping into an unexpected an unconveniant error situation after updating nextcloud to 31.x on a lazy sunday afternoon.

[BloodyIron]

So just upgraded to NC 31.0.12 today.. Why is this still an issue? Why hasn't this been fixed yet? This needs to be properly solved and issue closed. I now need to cobble together manually correcting this, as the script posted above seems to somehow not actually make the change... :/

[hoellen]

This issue falls outside the scope of what we will address within the Dockerfile itself. The project is focused on providing the Docker setup for Nextcloud and issues related to external configurations or database fixes should be handled separately.

There is also an open feature request to provide a repair step in the Nextcloud repository: nextcloud/server#53702

The issue here is still open so that other people who upgrade to version 31 can find the solution.

[BloodyIron]

This issue falls outside the scope of what we will address within the Dockerfile itself. The project is focused on providing the Docker setup for Nextcloud and issues related to external configurations or database fixes should be handled separately.

There is also an open feature request to provide a repair step in the Nextcloud repository: nextcloud/server#53702

The issue here is still open so that other people who upgrade to version 31 can find the solution.

Oops sorry I misread the scope of this repo/issue.

[SckyzO]

The bottom line is that we're really happy to find the solution quickly 😁🥳