| Bug #50329 | Error executing DELETE | ||
|---|---|---|---|
| Submitted: | 14 Jan 2010 13:47 | Modified: | 17 Feb 2010 6:00 |
| Reporter: | Junior Gaucho | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Server: Errors | Severity: | S1 (Critical) |
| Version: | 5.1.35 | OS: | Windows |
| Assigned to: | CPU Architecture: | Any | |
[15 Jan 2010 11:10]
Sveta Smirnova
Thank you for the report. But version 5.1.35 is old and probably this error fixed already. Please upgrade to current version 5.1.42, try with it and if problem still exists provide output of SHOW CREATE TABLE tab_0005_gru_rel, SHOW TABLE STATUS LIKE 'tab_0005_gru_rel' and your configuration file. If you could provide dump of this table this would be good also.
[15 Jan 2010 12:48]
Junior Gaucho
How could I do the upgrade with the minimum of time with the database stopped? I have to reinstall or just copy a file?
[17 Jan 2010 6:00]
Sveta Smirnova
Thank you for the feedback. Yes, you need to reinstall, then run mysql_upgrade command.
[18 Feb 2010 0: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".
Description: Please someone help me? Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 000000001DC0CE20=DELETE FROM tab_0005_gru_rel WHERE IdCodUsu_tu IN (1522,4021) thd->thread_id=392 thd->killed=NOT_KILLED The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. InnoDB: Log scan progressed past the checkpoint lsn 1 3264233087 100114 10:06:41 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... InnoDB: Doing recovery: scanned up to log sequence number 1 3264244582 100114 10:07:01 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed 100114 10:07:02 InnoDB: Started; log sequence number 1 3264244582 100114 10:07:03 [Note] Event Scheduler: Loaded 0 events 100114 10:07:03 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: ready for connections. Version: '5.1.35-community' socket: '' port: 3306 MySQL Community Server (GPL) How to repeat: Running a query delete