[ZBX-5509] Errors in zabbix-2.0.2/upgrades/dbpatches/2.0/mysql/patch.sql Created: 2012 Aug 29  Updated: 2017 May 30  Resolved: 2012 Sep 03

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 2.0.2
Fix Version/s: 2.0.3rc1, 2.1.0

Type: Incident report Priority: Minor
Reporter: Unix Beheer Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: database, mysql
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Suse Linux Enterprise Server 10 SP 4 with mysql 5.0.26


 Description   

During run of patch script I get the following error:
ERROR 1064 (42000) at line 1535: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1
Failed to patch Zabbix database. Restore from backup
I've fixed this as follows:
fdl117:/home/zabbix/zabbix-2.0.2/upgrades/dbpatches/2.0/mysql # diff patch.sql patch.sql.wk
1535c1535
< CALL zbx_convert_operations();
—
> CALL zbx_convert_operations;

I've also noticed that this typo is not present in de v2.0.1 patch.sql script.

 Comments   
Comment by Oleksii Zagorskyi [ 2012 Sep 02 ]

I cannot find the "CALL zbx_convert_operations();" in any version of zabbix sources.

I mean there always just "CALL zbx_convert_operations;" - without brackets.

Please check and clarify where did you get those brackets ?

Comment by Oleksii Zagorskyi [ 2012 Sep 02 ]

ZBXNEXT-1391 can clarify a bit

Comment by Alexander Vladishev [ 2012 Sep 03 ]

Thanks for your report. The problem will be fixed in 2.0.3.

Only from MySQL 5.0.30 the stored procedures that take no arguments can be invoked without parentheses.

http://dev.mysql.com/doc/refman/5.0/en/call.html

Comment by Alexander Vladishev [ 2012 Sep 03 ]

Fixed in pre-2.0.3 r30060 and pre-2.1.0 (trunk) r30061.

Comment by Oleksii Zagorskyi [ 2012 Sep 03 ]

OMG, I mixed meaning of:
< CALL zbx_convert_operations();
and
> CALL zbx_convert_operations;

probably because the diff generated incorrectly.
So, I supposed opposite meaning

Generated at Thu Apr 18 22:15:02 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.