Support

Akeeba Backup for Joomla!

#15314 AEAbstractDump :: Database Error: Unknown storage engine 'InnoDB' SQL=SHOW CREATE TABLE `clho_xmap_items`

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by nicholas on Thursday, 07 March 2013 01:17 CST

vickiwatson

Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Troubleshooting guide
Joomla! version: 2.5.9
PHP version: 5.3.18
MySQL version: 5.5.30-cll
Host: Knownhost
Akeeba Backup version: 3.7.2

EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.

Description of my issue:

Not sure why this happened. I uninstalled xmap and the error disappeared. Everything is functional now, so I don't need a solution, but if there's an easy answer why that error appeared, that might be helpful in the future.

I got the error message when I tried to create a backup after doing several updates on the site.

AEAbstractDump :: Database Error: Unknown storage engine 'InnoDB' SQL=SHOW CREATE TABLE `clho_xmap_items`

The series of events leading up to this was:

Updated Admin Tools to 2.5.2

Updated Akeeba Backup to 3.7.2

Updated joomla from 2.5.8 to 2.5.9

The backups had always worked before with the xmap component installed.

 

 

 

nicholas
Akeeba Staff
Manager

This actually indicates a potential issue with the database. Please ask your host these questions:

  • Are they using MySQL or MariaDB?
  • Do they have InnoDB support compiled and turned on in their database server?

I think that somehow they have a MySQL or MariaDB server which doesn't support the InnoDB table storage engine. Most likely this happened during an update of the server which explains why a table existed with an unsupported table storage engine.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!