After upgrading mariadb from 10.3.25 to 10.3.31 it fails to start like described in this bug report

I temporary fixed it by downgrading mariadb to 10.3.25 again like I described here.

To fix this completely, it seems I have to

1. mysqldump -p --all-databases>/tmp/all.sql
2. delete all tables
3. upgrade mariadb
4. reimport the dump

But that seems like a lot of work and dangerous. Also I get an error while exporting with mysqldump:

mysqldump: Couldn't execute 'SELECT `Vorname`, `Name`, `Stra?e` FROM `adresses`':
  Unknown column 'Stra?e' in 'field list' (1054)

(There seems to be a UTF-8 encoding problem. It should be "Straße" with a german sharp s)

I could wait a few months and see if a newer version will still produce that error. Is there any hope, they will fix this in a future version? Or is it something corrupt in my current database?

After upgrading mariadb from 10.3.25 to 10.3.31 it fails to start like described in this bug report

I temporary fixed it by downgrading mariadb to 10.3.25 again like I described here.

To fix this completely, it seems I have to

1. mysqldump -p --all-databases>/tmp/all.sql
2. delete all tables
3. upgrade mariadb
4. reimport the dump

But that seems like a lot of work and dangerous. Also I get an error while exporting with mysqldump:

mysqldump: Couldn't execute 'SELECT `Vorname`, `Name`, `Stra?e` FROM `adresses`':
  Unknown column 'Stra?e' in 'field list' (1054)

There seemed to be a UTF-8 encoding problem. It should be "Straße" with a german sharp "s" I deleted that very old table and the error is gone.

I could wait a few months and see if a newer version will still produce that error. Is there any hope, they will fix this in a future version? Or is it something corrupt in my current database? Maybe the UTF-8 problem was the cause already?

I will try upgrading again, when I have the time and see if the corrupted TRX_NO error is gone too.

I'll keep you updated...

My question:
Is there another way to fix the corrupted TRX_NO error than dumping the whole database?

After upgrading mariadb from 10.3.25 to 10.3.31 it fails to start like described in this bug report

I temporary fixed it by downgrading mariadb to 10.3.25 again like I described here.

To fix this completely, it seems I have to

1. mysqldump -p --all-databases>/tmp/all.sql
2. delete all tables
3. upgrade mariadb
4. reimport the dump

But that seems like a lot of work and dangerous. I could wait a few months and see if a newer version will still produce that error. Is there any hope, they will fix this in a future version? Or is it something corrupt in my current database?

After upgrading mariadb from 10.3.25 to 10.3.31 it fails to start like described in this bug report

I temporary fixed it by downgrading mariadb to 10.3.25 again like I described here.

To fix this completely, it seems I have to

1. mysqldump -p --all-databases>/tmp/all.sql
2. delete all tables
3. upgrade mariadb
4. reimport the dump

But that seems like a lot of work and dangerous. Also I get an error while exporting with mysqldump:

mysqldump: Couldn't execute 'SELECT `Vorname`, `Name`, `Stra?e` FROM `adresses`':
  Unknown column 'Stra?e' in 'field list' (1054)

(There seems to be a UTF-8 encoding problem. It should be "Straße" with a german sharp s)

I could wait a few months and see if a newer version will still produce that error. Is there any hope, they will fix this in a future version? Or is it something corrupt in my current database?