Bug #41633 Execution of Procedure delayed using ODBC-Connector
Submitted: 19 Dec 2008 12:01 Modified: 12 Feb 2009 13:52
Reporter: shehzad pankhawala Email Updates:
Status: Not a Bug Impact on me:
None 
Category:Connector / ODBC Severity:S2 (Serious)
Version:5.0.22 OS:Linux (Ubuntu 6.06.1 LTS)
Assigned to: CPU Architecture:Any
Tags: ODBC-connector, stored procedure

[19 Dec 2008 12:01] shehzad pankhawala
Description:
Mysql  Ver 14.12 Distrib 5.0.22.
ODBC connector version: mysql-connector-odbc-3.51.18-linux-x86-32bit.
OS version :Ubuntu 6.06.1 LTS.
RAM : 4151572 kB.
==============================================================================

We have created a Script that fetch the data from a PBX SERVER about call records. 

This script call some procedures via the above ODBC Connectors so as to perform insert/update/select transaction for our purpose.

Most of all procedure performs select transaction, and only one of them is performing Insert & Update transaction which is last procedure to be called by a script , this procedure perform one insert and two update transaction.

All the procedure should complete by the time. so script can continue performing all the desire transaction and after all the successful transaction last procedure should performs a insert/update operation to store the all 
the collected data.

Now this last insert/update procedure cause delay in performing its desire operation and so that script become idle and can't remain in execution and lead to delayed entry of data.

Related information:
=====================================================================================================================

-- Delay to complete procedure which performs one insert and two update operation: approx 4-5 hours
-- The above glitch happens one or two time in week.
-- During that no any further load on system, and only one instance of script  is running at a time so not exists any deadlock.
-- System is running 24 hour, and script is called average 25-50 times in an hour.

How to repeat:
Evenly generated itself as in description
[12 Feb 2009 13:52] Tonci Grgin
We're sorry, but the bug system is not the appropriate forum for asking help on using MySQL products. Your problem is not the result of a bug.

Support on using our products is available both free in our forums at http://forums.mysql.com/ and for a reasonable fee direct from our skilled support engineers at http://www.mysql.com/support/

Thank you for your interest in MySQL.

Explanation:
Hi Shehzad and thanks for your report.

Unfortunately, I don't have a crystal ball and can't tell anything from your description... There is no test case either.

What I can advise you is to look at server logs and see what is happening around the time error occurs.
If you can come about with compact but complete test case that exhibits this error every time it is run, feel free to attach it and reopen the report.