Hi
When i try to upgrade to tha latest moodle version it gives me this error
Your database has tables using Antelope as file format. You are recommended to convert the tables to Barracuda file format.
if i run this script
php admin/cli/mysql_compressed_rows.php
tables are converted to barracuda.
My question is
Does the server needs to support barracuda, or if it only supports antelope everything is going to work anyway?
Thanks
Hi All,
the reasons behind the choice of warning for Antelope can be found here: MDL-46235 and MDL-46963.
The conversion offered by Moodle runs on CLI but is is able to generate the SQL code required to update your DB: if you're on a shared hosting with no CLI access you can ask your Provider to launch that command on behalf of you but they need to re-configure the MySQL server too.
HTH,
Matteo
I've looked at the documentation here:
This documentation seems very light considering we are talking about a change to the actual database.
I remember we had a script that could be run from /admin/ to migrate from ISAM to InnoDB, and wonder if we should have something similar for this change ?
Matteo, you mention that the MySQL server requires reconfiguring (presumably to ensure any new db tables are created with Barracuda and not Antelope) - but I think we need to clearly document this too ?
There is some good information here that we could adapt and summarise:
https://dev.mysql.com/doc/refman/5.6/en/innodb-file-format.html
Hi Stuart,
I suppose you're right: I was thinking that having the option (-s, --showsql Print SQL statements for fixing of tables) to see what are the SQL commands Moodle wants to run on its database was enough - at least for me - to understand what are the actual impact of that CLI command.
Would you mind to add some lines in the Wiki or to create a dedicated page and not a simply redirect for https://docs.moodle.org/29/en/admin/environment/custom_check/unsupported_db_table_row_format?redirect=no (and for the other versions too)?
TIA,
Matteo
I wanted to second the suggestion of having a script that we can run to update these tables.
I have a client running moodle on a shared BlueHost server. We do not have access to run the modification scripts as outlined in the instructions. When I contacted BlueHost to ask for help, they said no.
I did download the database to a local install and perform the conversion there, but when I uploaded the database back to the server, I still get the error. I'm guessing I'm doing something wrong there.
After many hours spend researching and converting individual tables (only to have them revert back...presumably because the server changes were not made???) I'm forced to hope that we never have a course that is so large this becomes a problem.
And yes, we're looking at a new hosting company...
I'd appreciate any suggestions anyone has on this.
The message that you see is a suggestion. I think that you will still be fine with antelope as far as I know.
What version of Moodle are you running?
hi,
i have the same problem but i don't know how i'll resolve it,please if you have any solution that you can need me.
convert moodle to moodle 2.9.4
thank's
Hi
I have the same warning, but as I am not a coder and could not work out how to make the change to the file type, I just upgraded anyway.
From tests so far, it seems to work without the change.
Can anyone tell me if this will cause problems later on, or can elaborate on the instructions fr fixing for those of us who are not coders?
Many thanks in advance!
Debbie, what platform are you on? Linux or Windows?
No it is not required to convert yet, but is recommended, for if your course size is HUGE, then backing up or restoring may show issues, if your courses are under the range of say 500MB, then shouldn't be a problem.
Hi Usman
Thanks for your reply, that is good to know
I am on Linux and when you say under 500MB, are you referring to the database size or something else?
NO NO, not database size, but course size, as a course backup is made up of media embedded into course like Videos, Images and files, that can as big as 1GB+ in some cases, so restoring large courses like that sometimes showed issues in production environments and therefore conversion of database into Barracuda is recommended.
Database sizes had been way above 100GB or more even in time when conversion wasn't recommended.
Hello, guys! I just read this message (I'm running moodle 3.2.2) and I was wondering if there's already a fix for shared hostings, since I don't have CLI access :\
Thanks for any suggestion you can provide!
Hey Miguel,
I had the same problem and I`ve found a way around. The problem is not converting from antelope to barracuda but instead is setting your database in utf8_(whatever language)_ci (It looks like the default language is latin1_swedish_ci)
So, to fix this:
1- Go to your bluehost cPanel / Database Tools / phpMyAdmin
2- Select your database in the left panel.
3- Go to Operations menu (the one with the wrench icon). and set the correct database setting utf8_(whatever language)_ci. I`ve tried with English and Spanish and works fine anyway.
Good luck.
Am new here thank u
Moodle works fine without the conversion. The conversion is a precaution for plugins that may need a large number of fields. I converted mine because of the PayPal plugin, but there may be others that may require you to make the change. This suggestion is also to help with the overall speed of the website. Over time, antelope formatting will result in a significantly larger database file size. Good luck out there...
Moodle is not working fine in my case. It hangs up on the on the error screen and I cannot proceed with install? I have tried all the fixes but cannot get past this point. I am trying to install version 3.3.1 using data from installed version 3.1.1. I have uninstalled, re-installed again and again. Tried running the script, at one point it cleared the errors but upon restart reverted back to the same point! So much for the adrenaline rush. Any suggested fixes please, We host on our own servers. I have attached a screen shot of the errors
On my version 3.1.1 that is up and running this error appears but does not affect the functionality of the site?
unsupported_db_table_row_format if this test fails, it indicates a potential problem
Your database has tables using Antelope as the file format. You are recommended to convert the tables to the Barracuda file format. See the documentation Administration via command line for details of a tool for converting InnoDB tables to Barracuda.
Checkthis message is colored in yellow not critical red
Hi Sonny
You need to put below code in your my.cnf file.
[client] default-character-set = utf8mb4 [mysqld] innodb_file_format = Barracuda innodb_file_per_table = 1 innodb_large_prefix character-set-server = utf8mb4 collation-server = utf8mb4_unicode_ci skip-character-set-client-handshake [mysql] default-character-set = utf8mb4
For Community reference: https://docs.moodle.org/31/en/MySQL_full_unicode_support#Steps_to_upgrade .
HTH,
Matteo
Thanks but I am running on windows 12 server? I have attached a file from the mysql server 5 directory. Is this where the code needs to be added in a window installation. If not where is the my.cnf file located?
If this is the correct file where does one add the code?
Thanks Rahul
Yes, on Windows, my.ini is the correct file. You'll see section headings like [client] as in the sample code posted. Check to see if the setting already exists and then change the value to what was posted above. For settings that don't exist, add them to the appropriate section.
Thanks Rahul, this worked for getting out of the "antelope loop" when installing fresh 3.3.2
Hi guys,
I see this notification whenever I upgrade. Is possible to convert from antelope to barracuda for shared host?
