and how have you created those databases? From phpMyAdmin, command line? Which options/sql have you selected or typed?

TIA and ciao

TIA and ciao

can you execute this in your server:

SHOW VARIABLES LIKE 'character_set%';

SHOW LOCAL VARIABLES LIKE 'character_set%';

and post results here. Those are the checks performed by Moodle, just seeing what are them returning in your server. TIA!

I'm having the same problem. I am trying to upgrade from v 1.9 to v 1.9.1 and receiving this message: "Sorry, but your database is not already in Unicode, and this version of Moodle is not able to migrate your database to Unicode. Please upgrade to Moodle 1.7.x first and perform the Unicode migration from the Admin page. After that is done you should be able to migrate to Moodle 2007101512"

Background: Very experienced Moodler (using since 1.3); never had an upgrade problem until now.

Environment: Ubuntu 8.04; MySQL 5.0.51; PHP 5.2.4

If I revert to v1.9, the environment check is perfect (see attached).

In answer to Eloy's server questions, both queries return the following results:

SHOW LOCAL VARIABLES LIKE 'character_set%';
Variable_name Value
character_set_client utf8
character_set_connection utf8
character_set_database utf8
character_set_filesystem binary
character_set_results utf8
character_set_server latin1
character_set_system utf8
character_sets_dir /usr/share/mysql/charsets/

Anything more to check?

Thanks,

Jim

I intended to add this info:

When I initially received this error I did a db table check. All my Moodle tables were utf8_general_ci, but those tables that were added with phpMyAdmin were utf8_bin.

I altered the mdl_pma_* tables to utf8_general_ci and restarted both the DB server and the Ubuntu server. No good.

I then dropped all the mdl_pma_* tables, but to no avail: the upgrade to v 1.9.1 still results in the Unicode error.

Thanks,

Jim

One more detail to add: I removed phpMyAdmin, so that's not the problem.

Jim

I used the settings you recommended via the link above, adding them to the /etc/mysql/my.cnf file but with the same no-go results. A follow-up question:

Is there a command to ask MySQL which settings file it is drawing from? Even though I've got the settings correct in the my.cnf file (and I've restarted both Apache and MySQL), when I run "mysqladmin variables" I see the following mix of utf8 and latin1 settings, which may hint to the problem:

------------------------------------------------------------+

------------------------------------------------------------+

Any other hints would be appreciated. As I noted, I've been running Moodle since v1.3.x and have never had a problem with upgrading until now. (And why would it work from all dot releases > v1.7 to v1.9 and now get stuck on v1.9.1? It's a mystery.) Does anyone know if another application using the same MySQL server (but obviously not the same tables) could cause a problem. I installed WordPress on the same box, but can't remember the chronology so don't know if that could be a cause.

Thanks, Jim

I've got a resolution. A far more experienced programmer helped navigate through the Moodle codebase to discover that a value was missing from my mdl_config table. By inserting the value, we were able to proceed with the upgrade:

insert into mdl_config set `name`="unicodedb", value=1;

The mystery remains, though, as to why this value disappeared or why I was able to consistently upgrade thus far without it. But it's fixed now.

Jim

I had the same Problem as you, after inserting the value, the update from v1.8 to v1.91 works fine. Thanks for your hint!

Stefan