[horde] db migrate maximum row size error

[Luis Felipe Marzagao]

Hello:

I´d appreciate some help here.

DB version: mariadb  Ver 15.1 Distrib 10.3.32-MariaDB, for 
debian-linux-gnu (x86_64) using readline 5.2

I´m getting this error when running horde-db-migrate:

[  INFO  ] Migrating DB up.
[  INFO  ] Current imp schema version: 3
[  INFO  ] Ending imp schema version: 3
[  INFO  ] Current ingo schema version: 7
[  INFO  ] Ending ingo schema version: 7
[  INFO  ] Current kronolith schema version: 23
[  INFO  ] Ending kronolith schema version: 23
[  INFO  ] Current turba schema version: 6
Migrating to TurbaUpgradeActiveSyncSchema (7)
== 7 TurbaUpgradeActiveSyncSchema: migrating 
==================================
-- addColumn('turba_objects', 'object_otherprovince', 'string', 
array('limit' => 255))
SQLSTATE[42000]: Syntax error or access violation: 1118 Row size too 
large. The maximum row size for the used table type, not counting BLOBs, 
is 8126. This includes storage overhead, check the manual. You have to 
change some columns to TEXT or BLOBs
[  INFO  ] Current nag schema version: 14
[  INFO  ] Ending nag schema version: 14
[  INFO  ] Current mnemo schema version: 8
[  INFO  ] Ending mnemo schema version: 8
[  INFO  ] Current wicked schema version: 6
[  INFO  ] Ending wicked schema version: 6
[  INFO  ] Current gollem schema version: 3
[  INFO  ] Ending gollem schema version: 3
[  INFO  ] Current content schema version: 2
[  INFO  ] Ending content schema version: 2
[  INFO  ] Current Horde_Alarm schema version: 2
[  INFO  ] Ending Horde_Alarm schema version: 2
[  INFO  ] Current Horde_Auth schema version: 1
[  INFO  ] Ending Horde_Auth schema version: 1
[  INFO  ] Current Horde_Cache schema version: 2
[  INFO  ] Ending Horde_Cache schema version: 2
[  INFO  ] Current Horde_Core schema version: 1
[  INFO  ] Ending Horde_Core schema version: 1
[  INFO  ] Current Horde_Dav schema version: 2
[  INFO  ] Ending Horde_Dav schema version: 2
[  INFO  ] Current Horde_Group schema version: 3
[  INFO  ] Ending Horde_Group schema version: 3
[  INFO  ] Current Horde_History schema version: 6
[  INFO  ] Ending Horde_History schema version: 6
[  INFO  ] Current Horde_Imap_Client schema version: 2
[  INFO  ] Ending Horde_Imap_Client schema version: 2
[  INFO  ] Current Horde_Lock schema version: 3
[  INFO  ] Ending Horde_Lock schema version: 3
[  INFO  ] Current Horde_Perms schema version: 3
[  INFO  ] Ending Horde_Perms schema version: 3
[  INFO  ] Current Horde_Prefs schema version: 3
[  INFO  ] Ending Horde_Prefs schema version: 3
[  INFO  ] Current Horde_SessionHandler schema version: 2
[  INFO  ] Ending Horde_SessionHandler schema version: 2
[  INFO  ] Current Horde_Token schema version: 1
[  INFO  ] Ending Horde_Token schema version: 1
[  INFO  ] Current Horde_Vfs schema version: 4
[  INFO  ] Ending Horde_Vfs schema version: 4

If I set innodb_strict_mode = 0 then it works. But it seems to be an 
unsafe workaround.

 From this text it seems that increasing innodb_page_size would solve 
the problem:

https://mariadb.com/kb/en/troubleshooting-row-size-too-large-errors-with-innodb/

But id doesn´t. If I set innodb_page_size than mariadb will not start.

Any pointers?

Thanks a lot!

Luis Felipe