help.nextcloud.com is for home/non-enterprise users. If you’re running a business, paid support can be accessed via portal.nextcloud.com where we can ensure your business keeps running smoothly.
In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces:
example
Or for longer, use three backticks above and below the code snippet:
longer
example
here
Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can
Nextcloud version (eg, 29.0.5): Nextcloud Hub 8 (29.0.6)
Operating system and version (eg, Ubuntu 24.04): 24.04.1 LTS
Apache or nginx version (eg, Apache 2.4.25): Apache/2.4.58
PHP version (eg, 8.3): 8.3
The issue you are facing: Using Mariadb 10.11.8 as a database and facing frequent Database Table corruption with below error for random app tables.
Error : Got error 194 “Tablespace is missing for a table” from storage engine InnoDB
Looking for some recommendations on how to select and set up a stable database, presently with MariaDB it seems to be a WORK if there are so many frequent table corruptions.
Is this the first time you’ve seen this error? (Y/N): NO
I’m not a database expert, but I can say that I’ve been using MariaDB 10.11 for quite some time now and have never had any issues. Also, since Debian 12 and Ubuntu 22.04 both ship with MariaDB 10.11, there is probably a very large userbase using it with Nextcloud, despite the fact that 10.6 is still the recommended version, and if they were all having issues we would see a lot more posts like yours, which we don’t.
In short, I don’t think there are any general incompatibilities between Nextcloud and MariaDB 10.11, and the problem is more likely to be specific to your system, either a configuration issue or perhaps a hardware issue (RAM, storage…?).
That’s a relief that there are not many such incidents , I am trying for the second time on separate server using a hyperscalar with a 4 GB RAM. Amount of RAM should not be the reason for frequent tablespace corruption when there absolutely no load except photo upload from mobile device so am trying to narrow down possible reasons , might try with Ubuntu 22 later … am still scratching my head … any lead for DB parameter tuning which might help ?
Also when the yesterdays backup is restored to fix this issue , Disk utillization changes for the user … Not sure if maintenance:data-fingerprint helps to sync/link lost data reference which is already there on the server, am monitoring.
This really shouldn’t happen - and generally won’t as long as you stick to the GA/LTS releases of MariaDB (which you are from the looks of it).
Check your database error log. There may be some clues. Also there may be some hints in your server (OS) log, such as underlying storage problems.
If you use your favorite search engine you can find some details of the underlying things that can cause that error.
Maybe there’s a deeper issue with your infrastructure or something. There are also a lot of variations of restore scenarios that can cause it.
In short: While anything is possible, I doubt this is a problem with the specific version you’re running. There’s likely something else going on (which will also, in turn, follow you to any new version you moved to).
