Bug #61531 | trying to load a 93M script (big table) created by dumping a table | ||
---|---|---|---|
Submitted: | 16 Jun 2011 0:44 | Modified: | 20 Jun 2011 9:35 |
Reporter: | Alex Wielhouwer | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S2 (Serious) |
Version: | 5.2.34CE.7780 | OS: | Windows |
Assigned to: | CPU Architecture: | Any |
[16 Jun 2011 0:44]
Alex Wielhouwer
[16 Jun 2011 1:48]
MySQL Verification Team
Which exactly version 5.2.XX are you using?. Thanks.
[16 Jun 2011 1:57]
Alex Wielhouwer
version updated above
[16 Jun 2011 6:44]
Valeriy Kravchuk
How exactly you tried to load that script? In SQL Editor or in Administration part?
[16 Jun 2011 12:08]
Alex Wielhouwer
Tried first from the administrator section. When that failed, I tried manually from the sql query tools
[16 Jun 2011 12:37]
Valeriy Kravchuk
Please, send the output of Help > System Info menu item.
[16 Jun 2011 12:46]
Alex Wielhouwer
MySQL Workbench CE for Windows version 5.2.34 Configuration Directory: C:\Users\win7sql\AppData\Roaming\MySQL\Workbench Data Directory: C:\Program Files\MySQL\MySQL Workbench 5.2 CE Cairo Version: 1.8.8 Rendering Mode: OpenGL is not available on this system, so GDI is used for rendering. OS: Microsoft Windows 7 Service Pack 1 (build 7601), 32-bit CPU: AMD Athlon(tm) II X4 630 Processor, 2.0 GiB RAM Current user language: English (Canada) Note: shouldn't make a difference but this is a virtual machine running on a Hyper-V server.
[17 Jun 2011 3:23]
Valeriy Kravchuk
Please, try to load using the "Import from Self-contained file" option in: Server Administration -> Data export and restore -> Import from Disk.
[17 Jun 2011 14:43]
Alex Wielhouwer
Unfortunately, I have had to trash the system and start over to at least try to keep the project on track. Reloading the data again from its original source. All this because of some index corruption that (innodb) that could not be solved by a simple drop index, create index. (wouldn't let me drop it after I had to set the innodb_force_recovery = 4 to actually start the system) seemed a bit chicken and egg in terms of corruption recovery.
[20 Jun 2011 9:35]
Alfredo Kojima
This is a duplicate of bug #55312