Problem with 1.8.4 SQL Patch

[scanch]

Hello,
The following error appear when I try to apply the 1.8.4 SQL patch to my current 1.8.3 Database under MySQL:

mysql> use zabbix;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
mysql> DROP INDEX node_cksum_cksum_1 ON node_cksum;
ERROR 1091 (42000): Can't DROP '[B]node_cksum_cksum_1[/B]'; check that column/key exists
mysql> CREATE INDEX node_cksum_1 on node_cksum (nodeid,cksumtype,tablename,recordid);
ERROR 1061 (42000): Duplicate key name '[B]node_cksum_1[/B]'

Is there an error in with the INDEX name on the first request ?
Regards,

[jonh]

There's an extra '_cksum' in the name of the index. Just rip one out and it should work.

[badener]

I thought the patch was only necessary when upgrading from a 1.6.x version ?
I upgraded my 1.8.3 to 1.8.4 without the patch and I get no errors.

[richlv]

database patching is not required for minor upgrades like 1.8.3->1.8.4 (or 1.8.0->1.8.4) - actually, it is more likely to break your db. to be completely sure, restore from the backup right before attempting to patch the db and don't try to patch it again

[scanch]

database patching is not required for minor upgrades like 1.8.3->1.8.4 (or 1.8.0->1.8.4) - actually, it is more likely to break your db. to be completely sure, restore from the backup right before attempting to patch the db and don't try to patch it again

Too late and don't have database backup

I will known it for the future, but I think you may change your sentence about the SQL patch:

If you are using Zabbix 1.8 with node-based distributed setup, please run the following SQL patch. It should improve performance of configuration syncing a lot.
MySQL:
DROP INDEX node_cksum_cksum_1 ON node_cksum;
CREATE INDEX node_cksum_1 on node_cksum (nodeid,cksumtype,tablename,recordid);

It's not very clear that we don't need to apply the patch

[richlv]

oh, that part only... i assumed you were trying to run the full db patch 1.6->1.8

that's a single index and executing those commands will cause no harm

edit : to clarify, it will actually do what the comment says - improve distributed setup performance a lot