How to fix ERROR 1305: Stored routine does not exist in MySQL

First, confirm you are using the right database:

SELECT DATABASE();
USE your_database_name;

If you are connected to the wrong database, MySQL will search for the routine in that schema and not find it. Always ensure your session is in the correct database before calling a procedure.

Query the information_schema to verify the routine exists:

SELECT ROUTINE_NAME, ROUTINE_TYPE, ROUTINE_SCHEMA
FROM INFORMATION_SCHEMA.ROUTINES
WHERE ROUTINE_SCHEMA = DATABASE();

Alternatively, use SHOW commands:

SHOW PROCEDURE STATUS WHERE db = DATABASE();
SHOW FUNCTION STATUS WHERE db = DATABASE();

If the routine does not appear in the output, it either does not exist or is in a different database.

Ensure your CALL statement matches the exact name (including case) and syntax:

-- Correct (assuming proc_name exists)
CALL proc_name();
CALL proc_name(arg1, arg2);

-- Incorrect (spaces before parentheses)
CALL proc_name ();
CALL my_function (arg);  -- Functions should use SELECT, not CALL

Remember:
- Stored procedures are invoked with CALL
- Stored functions are used in SELECT statements or expressions

Using CALL on a function will fail with error 1305. Use: SELECT my_function(arg);

If the routine exists in a schema other than the current one, prefix the call with the database name:

CALL reporting.generate_report();
CALL analytics.process_data();

This is especially useful in distributed environments or when working with multiple databases.

If the routine exists but you cannot execute it, verify your privileges:

-- Check what procedures a user can execute
SHOW GRANTS FOR 'username'@'hostname';

-- Grant EXECUTE privilege
GRANT EXECUTE ON PROCEDURE database_name.procedure_name TO 'username'@'hostname';
GRANT EXECUTE ON FUNCTION database_name.function_name TO 'username'@'hostname';
FLUSH PRIVILEGES;

Without EXECUTE privilege, MySQL will report the routine as not existing (for security, it does not reveal whether the routine exists or if you simply lack permissions).

If the routine does not exist, you must recreate it. Retrieve the routine definition from source control or a backup:

DELIMITER //
CREATE PROCEDURE my_procedure(IN param1 INT, OUT result INT)
BEGIN
  SELECT COUNT(*) INTO result FROM users WHERE id = param1;
END //
DELIMITER ;

Then call it:

CALL my_procedure(1, @result);
SELECT @result;

For deployments, ensure your SQL migration scripts include all CREATE PROCEDURE and CREATE FUNCTION statements.

On Unix-like systems, stored routine names are case-sensitive if lower_case_table_names=0. On Windows, they are case-insensitive.

-- Check the setting
SHOW VARIABLES LIKE 'lower_case_table_names';

If lower_case_table_names=0, ensure your CALL statements match the routine name exactly:

-- If created as MyProcedure, must call as MyProcedure
CALL MyProcedure();  -- Correct
CALL myprocedure();  -- Error 1305 on Unix

To avoid this issue, always use lowercase for routine names across all platforms.