The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2024-11-16. For the latest, interactive version please visit https://mariadb.com/kb/.

MariaDB issue while upgradin Trac from V 1.0 to 1.2

Running MariaDB 10.1.48 and an upgrade of Trac from V 1.0 to 1.2 I get

[...]
2023-05-08 11:48:57,032 Trac[api] INFO: Need to upgrade database_version from 36 to 41
2023-05-08 11:49:03,516 Trac[env] INFO: trac.env.EnvironmentSetup upgrading...
2023-05-08 11:49:03,734 Trac[console] ERROR: Exception in trac-admin command: u'upgrade'
Traceback (most recent call last):
  File "build/bdist.linux-x86_64/egg/trac/admin/console.py", line 112, in onecmd
    rv = cmd.Cmd.onecmd(self, line) or 0
[...]
  File "build/bdist.linux-x86_64/egg/trac/upgrades/db37.py", line 40, in do_upgrade
    cursor.execute('ALTER TABLE %s %s' % (db.quote(tab), mods))
[...]
OperationalError: (1025, 'Error on rename of \'./trac/#sql-452_1f\' to \'./trac/session_attribute\' (errno: 184 "Tablespace already exists")')

Someone from the Trac community told me this is due to

The db37.py failed in your environment. The upgrade step alters tables
to modify columns which is TEXT type with MEDIUMTEXT type.

Any experiences, ideas, suggestions? I am stuck...

Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.