Mysql Error 1307 Failed To Create Function
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up MySQL: failed to create function {functionName} up vote 0 down vote favorite This works on MySQL 5.0.41, but on 5.1.31 it just says "failed to create function". I type this in the console: delimiter |
Community Podcasts MySQL.com Downloads Documentation Section Menu: MySQL Forums :: Stored Procedures :: Urgent + ERROR 1307 (HY000): FAILED TO CREATE PROCEDURE New Topic Advanced Search Urgent + ERROR 1307 (HY000): FAILED TO CREATE PROCEDURE Posted by: R Roberts () Date: July 03, 2008 06:31AM Hi I am in need of some help please urgently. I have installed SQLYog GUI community edition v6.16 and also MySQL Server 6.0 on my local machine. I have managed to restore my tables on there, but http://stackoverflow.com/questions/3047692/mysql-failed-to-create-function-functionname I am unable to create a function or stored procedure as I keep getting the error on the query analzyer and also on the command client as well. ERROR 1307 (HY000): FAILED TO CREATE PROCEDURE ERROR 1307 (HY000): FAILED TO CREATE FUNCTION Any ideas or suggestions would be helpful please??? Please help out as I cannot progress with http://forums.mysql.com/read.php?98,216897,216897 the work... Thanks Navigate:Previous Message•Next Message Options:Reply•Quote Subject Views Written By Posted Urgent + ERROR 1307 (HY000): FAILED TO CREATE PROCEDURE 14613 R Roberts 07/03/2008 06:31AM Re: Urgent + ERROR 1307 (HY000): FAILED TO CREATE PROCEDURE 6892 Peter Brawley 07/03/2008 09:05AM Re: Urgent + ERROR 1307 (HY000): FAILED TO CREATE PROCEDURE 6511 R Roberts 07/03/2008 09:19AM Re: Urgent + ERROR 1307 (HY000): FAILED TO CREATE PROCEDURE 6126 Peter Brawley 07/03/2008 08:54PM Re: Urgent + ERROR 1307 (HY000): FAILED TO CREATE PROCEDURE 5538 R Roberts 07/05/2008 06:20AM Re: Urgent + ERROR 1307 (HY000): FAILED TO CREATE PROCEDURE 5259 Peter Brawley 07/05/2008 08:52AM Re: Urgent + ERROR 1307 (HY000): FAILED TO CREATE PROCEDURE 8272 R Roberts 07/05/2008 09:48AM Re: Urgent + ERROR 1307 (HY000): FAILED TO CREATE PROCEDURE 5491 Peter Brawley 07/05/2008 10:43AM Re: Urgent + ERROR 1307 (HY000): FAILED TO CREATE PROCEDURE 4305 Igor B 10/13/2008 07:00PM Re: Urgent + ERROR 1307 (HY000): FAILED TO CREATE PROCEDURE 5115 Boyd Hemphill 11/11/2008 02:39PM Re: Urgent + ERROR 1307 (HY000): FAILED TO CREATE PROCEDURE
Email Updates: Status: Not a Bug Impact on me: None Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S1 (Critical) Version:5.1.30-ndb-6.3.20-cluster-gpl OS:Linux (FC6) Assigned to: Tags: ERROR 1307 (HY000): Failed to CREATE PROCEDURE on Mysql http://bugs.mysql.com/41973 Cluster View Add Comment Files Developer Edit Submission View Progress Log Contributions [8 Jan 2009 17:31] Suresh Shanmughom Description: Getting error while creating procedure: mysql> DELIMITER // mysql> CREATE PROCEDURE age_tests(out parm1 int) -> https://docs.oracle.com/cd/E17952_01/mysql-5.1-en/error-messages-server.html BEGIN -> select count(*)from status where -> StateChange < DATE_SUB(NOW(), INTERVAL 1 HOUR) and severity < 1; -> END // ERROR 1307 (HY000): Failed to CREATE PROCEDURE age_tests Version: 5.1.27-ndb-6.3.17-cluster-gpl How to repeat: Run mysql error the above create procedure for an existing table Suggested fix: Not aware of [8 Jan 2009 20:36] Tomas Ulin Did not try with 5.1.27-ndb-6.3.17 but it works with 5.1.30-ndb-6.3.20 can you please change to a newer version and verify. BR, Tomas [8 Jan 2009 20:46] Suresh Shanmughom Thanks for the info. I just wanted to see whether I am doing something wrong or it is a bug. If it mysql error 1307 is a bug then I am willing to go for 5.1.30-ndb-6.3.20. ? -Suresh [8 Jan 2009 20:58] Tomas Ulin error 1307 is a generic failure code if you hit 'show warnings' directly after the failed command there might be more info. in general there is no difference between stored procs in cluster vs. in the vanilla mysql server, so if you have a table which is a 'ndb' or a 'myisam' table should not matter. you have not supplied the table definition so it is hard to say if it is related to that. But I would move to 6.3.20 since a lot has happened since the version you are on. Especially since you seem to be interested in stored procs, there are lots of bugfixes in the server between 5.1.27 and 5.1.30. BR, T [8 Jan 2009 21:11] Suresh Shanmughom Thanks, Here is the create table statement: CREATE TABLE `status` ( `dedupid` varchar(255) NOT NULL, `evid` char(25) NOT NULL, `device` varchar(128) NOT NULL, `component` varchar(128) DEFAULT '', `eventClass` varchar(128) DEFAULT '/Unknown', `eventKey` varchar(128) DEFAULT '', `summary` varchar(128) NOT NULL, `message` varchar(4096) DEFAULT '', `severity` smallint(6) DEFAULT '-1', `eventState` smallint(6) DEFAULT '0', `eventClassKey` varchar(128) DEFAULT '', `eventGroup` varchar(64) DEFAULT '', `stateChange` timestamp NOT NULL DEFA
error. For example, the mysql client program displays errors using the following format: shell> ER_SLAVE_AMBIGOUS_EXEC_MODE7 ERROR 1146 (42S02): Table 'test.no_such_table' doesn't exist The message displayed contains three types of information: A numeric error code (ER_SLAVE_AMBIGOUS_EXEC_MODE6). This number is MySQL-specific and is not portable to other database systems. A five-character SQLSTATE value (ER_SLAVE_AMBIGOUS_EXEC_MODE5). The values are taken from ANSI SQL and ODBC and are more standardized. Not all MySQL error numbers have corresponding SQLSTATE values. In these cases, ER_SLAVE_AMBIGOUS_EXEC_MODE4 (general error) is used. A message string that provides a textual description of the error. For error checking, use error codes, not error messages. Error messages do not change often, but it is possible. Also if the database administrator changes the language setting, that affects the language of error messages. Error codes are stable across GA releases of a given MySQL series. Before a series reaches GA status, new codes may still be under development and subject to change. Server error information comes from the following source files. For details about the way that error information is defined, see the MySQL Internals Manual. Error message information is listed in the ER_SLAVE_AMBIGOUS_EXEC_MODE3 file. ER_SLAVE_AMBIGOUS_EXEC_MODE2 and ER_SLAVE_AMBIGOUS_EXEC_MODE1 represent numbers and strings, respectively, that are substituted into the Message values when they are displayed. The Error values listed in ER_SLAVE_AMBIGOUS_EXEC_MODE0 are used to generate the definitions in the ER_SLAVE_AMBIGOUS_EXEC_MODE9 and ER_SLAVE_AMBIGOUS_EXEC_MODE8 MySQL source files. The SQLSTATE values listed in ER_SLAVE_AMBIGOUS_EXEC_MODE7 are used to generate the definitions in the ER_SLAVE_AMBIGOUS_EXEC_MODE6 MySQL source file. Because updates are frequent, it is possible that those files will contain additional error information not listed here. Error: ER_SLAVE_AMBIGOUS_EXEC_MODE5 SQLSTATE: ER_SLAVE_AMBIGOUS_EXEC_MODE4 (ER_SLAVE_AMBIGOUS_EXEC_MODE3) Message: hashchk Unused. Error: ER_SLAVE_AMBIGOUS_EXEC_MODE2 SQLSTA