Support

 Hi. I have a Joomla site that the client has decided to move to another hosting service.
I made a backup, uploaded the file to the new hosting provider and now I am trying to setup the site in its new server using Kickstart.
In the Database Restoration phase, I enter the DB details and click next. Then I get a popup window with this text:
Database error processing line 0
Database server error reply:

ErrNo #0

SQL=CREATE TABLE `j4nye_admintools_acl` ( `user_id` bigint(20) unsigned NOT NULL, `permissions` mediumtext, PRIMARY KEY (`user_id`) ) ENGINE=Aria DEFAULT CHARSET=utf8 PAGE_CHECKSUM=1
Raw query text:

CREATE TABLE `#__admintools_acl` ( `user_id` bigint(20) unsigned NOT NULL, `permissions` mediumtext, PRIMARY KEY (`user_id`) ) ENGINE=Aria DEFAULT CHARSET=utf8 PAGE_CHECKSUM=1.

Attached a screenshot.

What is this and how can I repair it please?

Are you sure your database user has rights to create a table? Your database user generally should have all rights to the database.

Are you sure the Aria engine is installed on this database server?

Hi. Thanks for the quick replay.
As you can see in the attached screenshot, I do have all rights.
About Aria engine. I don't know...

It looks like the permissions are fine. The Aria engine is important, if it is not available on the target server, the database would not be able to restore. You will need to check with your host on that. If it is not available, I'll have to find out the easiest way to take the ENGINE commands out of the SQL dump file.

OK. Checked with the provider - no Aria engine.
What can we do now?

???

Worst case scenario, we search for "ENGINE=Aria" and replace with "". In most cases we don't need the ENGINE parameter. Let me see if there is an easier way.

This falls under using Akeeba Backup to transfer a site between different database technologies. As it says in the documentation, this can't be done. While MariaDB and MySQL are very close, they are not the same.

So what we're going to do is impossible. It will work on 9 out of 10 sites, but some components actually do require special database engines for their tables. CiviCRM comes to mind, it requires the InnoDB engine. I'm not sure what would happen if we tried this with a CiviCRM site, but it wouldn't be pretty.

Your SQL dump files are on your site in the /installation/sql folder. We need to FTP them to your local computer. There may be more than one SQL dump file there depending on the size of your database. We need to edit them with a text editor - not a word processor. We're going to search for "ENGINE=Aria " and replace with "" (empty string). Upload your changed SQL files and try your install again.

Hi.
First, I really don't understand if you expect it to work or not.
As I understand it, the files to be modified are the files in the new server. Is this correct?
In the /installation/sql folder in the new server I have 42 files with the name site.s01 - site.s42, and two more files: database.ini and site.sql.
Do I need to search for "ENGINE=Aria " in all of them?

I did all that and now I get this error:
SQL=CREATE DATABASE `kiahorg_db1` CHARACTER SET `utf8`
Attached a screeshot

I apologize if I was not specific enough. Yes you need to edit all 43 files to search for the ENGINE command. Yes I expect it to work, but there are circumstances where I know what we're doing will cause problems.

The error is in the CREATE DATABASE command. Generally the restore function can't CREATE a database, only create tables within an existing database. Is your database name, database user and password correct for the server you are restoring to? Did you manually create the database before you began the restore?

I did have a lowercase instead of uppercase letters in the user name. Now that I fixed it, I get this error:
ErrNo #0
SQL=CREATE TABLE `j4nye_admintools_acl` ( `user_id` bigint(20) unsigned NOT NULL, `permissions` mediumtext, PRIMARY KEY (`user_id`) ) DEFAULT CHARSET=utf8 PAGE_CHECKSUM=1
Raw query text:

CREATE TABLE `#__admintools_acl` ( `user_id` bigint(20) unsigned NOT NULL, `permissions` mediumtext, PRIMARY KEY (`user_id`) ) DEFAULT CHARSET=utf8 PAGE_CHECKSUM=1

It looks like the same error...

No, not the same error. We got rid of the ENGINE, now it doesn't like the PAGE_CHECKSUM.

OK, this time we're going to do a test before we edit all those SQL files. Just edit site.sql this time, search for "PAGE_CHECKSUM=1 " and replace with "". When you retry the install, it will error out, I know that. What I want to know is will it create the j4nye_admintools_acl table properly after this second fix, or is there another gremlin waiting for us?

If we get the same error on a different table, we know that j4nye_admintools_acl was created successfully and we can edit the other .s01-.s42 files and continue with the restore.