Bug #69877 perror
Submitted: 31 Jul 2013 9:47 Modified: 31 Aug 2013 10:22
Reporter: Varun Surekha Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Errors Severity:S1 (Critical)
Version: OS:Linux
Assigned to: CPU Architecture:Any

[31 Jul 2013 9:47] Varun Surekha 
Description:
Perror utility does not know anything about the mysql error code. As i have tried on Centos 6.4 64 bit machine. The command is written as perror 1064 but always getting illegal error code till mysql 5 also.I have seen that oracle has mentioned in their documentation about the perror utility for training but the command is not working.

How to repeat:
Perror utility does not know anything about the mysql error code. As i have tried on Centos 6.4 64 bit machine. The command is written as perror 1064 but always getting illegal error code till mysql 5 also.I have seen that oracle has mentioned in their documentation about the perror utility for training but the command is not working.
[31 Jul 2013 10:22] MySQL Verification Team 
On recent version it works okay.

[x@x mysql-advanced-5.6.12-linux-glibc2.5-x86_64]$ ./bin/perror 1064
MySQL error code 1064 (ER_PARSE_ERROR): %s near '%-.80s' at line %d

[x@x mysql-5.5.32-linux2.6-x86_64]$ ./bin/perror 1064
MySQL error code 1064 (ER_PARSE_ERROR): %s near '%-.80s' at line %d

Perhaps fixed by:
http://bugs.mysql.com/bug.php?id=10143
[31 Jul 2013 10:22] MySQL Verification Team 
Hello Varun,

Thank you for the report.
I can not repeat described behavior on 5.5/5.6/5.7.
Could you tell us which MySQL version you are using?

//
[ushastry@cluster-repo mysql-5.5.32]$ bin/perror 1064
MySQL error code 1064 (ER_PARSE_ERROR): %s near '%-.80s' at line %d

[ushastry@cluster-repo mysql-5.6.13]$ bin/perror 1064
MySQL error code 1064 (ER_PARSE_ERROR): %s near '%-.80s' at line %d

[ushastry@cluster-repo mysql-5.7.2-m12]$ bin/perror 1064
MySQL error code 1064 (ER_PARSE_ERROR): %s near '%-.80s' at line %d

Thanks,
Umesh
[1 Sep 2013 1:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".