MySQL server stopps after "select" command from client
am 23.06.2005 18:04:36 von O.Strobel--=_alternative 00582737C1257029_=
Content-Type: text/plain; charset="us-ascii"
Hi all,
I'm using MySQL Server 4.1.11 on a WindowsXP SP2 PC.
The client application is written in VB6 using the MyODBC-3.51.11-2
connector.
Following SQL command, started from a client pc, hits the MySQL server so
hard, that it stopps:
SELECT t1.*, t2.*, t3.Cus_Art_Name FROM Customer_Order t1,
Production_Order t2, Customer_Article t3 WHERE (t1.Sel_Sta_Ord_ID = 2 OR
t1.Sel_Sta_Ord_ID = 3) AND t1.Cus_Ord_No = t2.Cus_Ord_No AND t1.Cus_Art_ID
= t3.Cus_Art_ID ORDER BY t1.Cus_Ord_No;
The error occure suddenly, the last few days it works well. Even if i try
to commit the command with the QueryBrowser that stopps the server.
Following error is displayed in the QueryBrowser: "lost connection to
MySQL server during query" error no : 2013
The errolog-file from the MySQL server tells the following:
050623 17:43:11 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
050623 17:43:11 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 82784476.
InnoDB: Doing recovery: scanned up to log sequence number 0 82784476
InnoDB: Last MySQL binlog file position 0 79, file name
C:\Programme\MySQL\MySQL_V41\logs\Log_Bin.000037
050623 17:43:12 InnoDB: Flushing modified pages from the buffer pool...
050623 17:43:12 InnoDB: Started; log sequence number 0 82784476
050623 17:43:12 [Warning] 'db' entry 'mysql application@%' had database in
mixed case that has been forced to lowercase because
lower_case_table_names is set. It will not be possible to remove this
privilege using REVOKE.
050623 17:43:12 [Warning] 'db' entry 'em_cam application@%' had database
in mixed case that has been forced to lowercase because
lower_case_table_names is set. It will not be possible to remove this
privilege using REVOKE.
anyone with any ideas?
best regards
Oliver Strobel
--=_alternative 00582737C1257029_=--