MariaDB partial Antelope to Barracuda conversion

Hello!

The current result is this:

MariaDB [INFORMATION_SCHEMA]> SELECT NAME, SPACE, FILE_FORMAT FROM INFORMATION_SCHEMA.INNODB_SYS_TABLES WHERE NAME like "nextcloud%";
+---------------------------------------+-------+-------------+
| NAME                                  | SPACE | FILE_FORMAT |
+---------------------------------------+-------+-------------+
| nextcloud/oc_accounts                 |   199 | Antelope    |
| nextcloud/oc_activity                 |   202 | Antelope    |
| nextcloud/oc_activity_mq              |   205 | Antelope    |
| nextcloud/oc_addressbookchanges       |   208 | Antelope    |
| nextcloud/oc_addressbooks             |   213 | Barracuda   |
....

It was caused by myself following MYSQL instruction straightforward without care about MariaDB version :frowning:

I run

sudo -u www-data php occ maintenance:repair

BEFORE running

MariaDB> USE INFORMATION_SCHEMA;
MariaDB> SELECT CONCAT("ALTER TABLE `", TABLE_SCHEMA,"`.`", TABLE_NAME, "` ROW_FORMAT=DYNAMIC;") AS MySQLCMD FROM TABLES WHERE TABLE_SCHEMA = "nextcloud";

the wrong repair has stopped with an error exactly on oc_addressbooks

Then I discovered the right process :frowning:
And restarted the whole migration considering MariaDB procedure.
It is like the occ repair has marked the first tables as converted. There is a way to repeat the conversion over these few tables?

What to do now?
I’m sticking in maintenance mode.

Thanks

Nextcloud version 17
Operating system and version ubuntu 18.04
PHP version 7.3
Mariadb 10.1.43

Thanks to another post, I did not catch the meaning of this sentence:

Copy the output to the editor, remove the | and execute the resulting sql commands in the shell.

This link was much more clear:
https://www.allerstorfer.at/enabling-mysql-4-byte-support-for-nextcloud-on-ubuntu-18-04/

Well, finally this does the job!

In your opinion, could this fuzzy way to proceed cause some mess up?