mysql 5.1.46

I am having the same issue when upgrading from 1.8.9 to 1.9.9. The solution found does not work in my situation.

5482:20120228:113543.823 [Z3005] query failed: [1267] Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_unicode_ci,IMPLICIT) for operation '=' [select distinct h.hostid,h.proxy_hostid from hosts h,interface i,dservices ds where h.hostid=i.hostid and i.ip=ds.ip and ds.dhostid=277 and h.hostid between 0 and 99999999999999 order by h.hostid]
5482:20120228:113629.877 [Z3005] query failed: [1267] Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_unicode_ci,IMPLICIT) for operation '=' [select distinct h.hostid,h.proxy_hostid from hosts h,interface i,dservices ds where h.hostid=i.hostid and i.ip=ds.ip and ds.dhostid=278 and h.hostid between 0 and 99999999999999 order by h.hostid]
5482:20120228:113630.017 [Z3005] query failed: [1267] Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_unicode_ci,IMPLICIT) for operation '=' [select distinct h.hostid,h.proxy_hostid from hosts h,interface i,dservices ds where h.hostid=i.hostid and i.ip=ds.ip and ds.dhostid=498 and h.hostid between 0 and 99999999999999 order by h.hostid]
5482:20120228:113630.116 [Z3005] query failed: [1267] Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_unicode_ci,IMPLICIT) for operation '=' [select distinct h.hostid,h.proxy_hostid from hosts h,interface i,dservices ds where h.hostid=i.hostid and i.ip=ds.ip and ds.dhostid=499 and h.hostid between 0 and 99999999999999 order by h.hostid]
5482:20120228:113630.233 [Z3005] query failed: [1267] Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_unicode_ci,IMPLICIT) for operation '=' [select distinct h.hostid,h.proxy_hostid from hosts h,interface i,dservices ds where h.hostid=i.hostid and i.ip=ds.ip and ds.dhostid=500 and h.hostid between 0 and 99999999999999 order by h.hostid]

If you need any information, don't hestitate to request...

Correcting the query executed by the Zabbix server from:

mysql> select distinct h.hostid,h.proxy_hostid from hosts h,interface i,dservices ds where h.hostid=i.hostid and i.ip=ds.ip and ds.dhostid=390 and h.hostid between 0 and 99999999999999 order by h.hostid;
ERROR 1267 (HY000): Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_unicode_ci,IMPLICIT) for operation '='

To:

mysql> select distinct h.hostid,h.proxy_hostid from hosts h,interface i,dservices ds where h.hostid="i.hostid" and i.ip="ds.ip" and ds.dhostid="390" and h.hostid between 0 and 99999999999999 order by h.hostid;
Empty set (0.00 sec)

Returns nothing, but seem to work. Perhaps this needs changing somewhere in de code?

This also happens in 'Administration/Discovery' (discovery.php)

Error in query [SELECT DISTINCT h.hostid,h.name,h.status,ds.dserviceid FROM hosts h,dservices ds,interface i WHERE 1=0 AND ds.ip=i.ip AND h.hostid=i.hostid AND h.hostid BETWEEN 000000000000000 AND 099999999999999 AND h.status IN (0,1) ORDER BY h.status] [Illegal mix of collations (utf8_unicode_ci,IMPLICIT) and (utf8_general_ci,IMPLICIT) for operation '=']
mysql_fetch_assoc() expects parameter 1 to be resource, boolean given [include/db.inc.php:560]
mysql_free_result() expects parameter 1 to be resource, boolean given [include/db.inc.php:561]

If the character set and collation's are all the same the issue is fixed.

This is not caused by the upgrade SQL scripts, but caused by configuration differences in old and new setups.
So, make sure the existing and default charset/collation in old and new environments are exactly the same.

I think this call can be closed.

the last issue you listed is coming from the frontend, so that's indeed a different thing. the original problem with the patch seems to remain

this didn't affect too many users, so closing it