Sqlyog 6.11 And 6.12rc Crash

[dany]

I'm trying to Restore a backup using “Restore from SQL DUMP”.

Dump file (4140 K:cool: was generated by SQLyog 6.1 Community Edition on MySQL 4.1.22.

I've tried to restore using SQLyog 6.11 and 6.12RC Enterprise on MySQL 4.1.22.

EVERY time i try I get an error message after 56 executed querys:

SQL dump import error:

“There was an error while executing a query…”

I open the error file and I get:

Error occured at:2007-11-07 13:23:19

Line no.:484

Error Code: 2006 – MySQL server has gone away

1) Then I click OK to close the SQL dump import error dialog.

2) I click Cancel to close the Execute Query From A File dialog.

3) The I press F5 (refresh) to see what appened

4) A new dialog: SQLyog crashed. Dump file saved.

I can restore other DUMPs but not this IMPORTANT file.

I'm using Windows Vista Ultimate 32bit.

PLEASE HELP !!!

[peterlaursen]

You have reported two issues.

1) your SQL DUMP won't import (server has 'gone away').

This may very well be because the max_allowed_packet setting in server configuration is too small compared to the size of an INSERT in this SQL DUMP.

If this is the situation, you should raise this setting. If you are not in control of the server configuration for this server you will probably be able to import to another (local) server and copy data (using 'copy to other' or 'data sync')

Also please read this FAQ:

http://webyog.com/faq/content/24/101/en/ab…-and-bulks.html

2) SQLyog crashes. We are looking into that now!

[peterlaursen]

Could you share that SQL DUMP with us? There is no usable stack trace in the crash dump file saved by SQLyog, so without it it will be difficult to do progress. You can create a ticket and attach here if you want privacy. And please zip before attaching!

BTW: I think you execute as an external file. What happens if you copy the file into the editor and executes from here?

[dany]

This is what the DUMP file looks like

I've skipped to the (let's say) 'aaa' table.

The problem arises when SQLyog is doing the INSERT INTO.

That INSERT INTO is very, very long.

I will do more tests this night.

Bye,

Daniele

/*

SQLyog Community Edition- MySQL GUI v6.1

MySQL – 4.1.22-community-nt : Database – az1001

*********************************************************************

*/

/*!40101 SET NAMES utf8 */;

/*!40101 SET SQL_MODE=''*/;

create database if not exists `az1001`;

USE `az1001`;

/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;

/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;

/*Table structure for table `aaa` */

DROP TABLE IF EXISTS `aaa`;

CREATE TABLE `aaa` (

`id` int(10) unsigned NOT NULL auto_increment,

`aaa1` smallint(6) NOT NULL default '0',

`aaa2` smallint(6) default NULL,

`aaa3` int(11) NOT NULL default '0',

`aaa4` int(11) default NULL,

`aaa5` int(11) default NULL,

`aaa6` int(11) default NULL,

`aaa7` char(18) default NULL,

`aaa8` char(18) default NULL,

`aaa9` char(80) default NULL,

`aaa10` int(11) default NULL,

`aaa11` decimal(12,3) default NULL,

`aaa12` decimal(12,5) default NULL,

`aaa13` decimal(4,2) default NULL,

PRIMARY KEY (`id`),

KEY `indexaaa6` (`aaa6`)

) ENGINE=InnoDB DEFAULT CHARSET=latin1 ROW_FORMAT=FIXED COMMENT='InnoDB free: 7168 kB';

/*Data for the table `aaa` */

insert into `aaa`(`id`,`aaa1`,`aaa2`,`aaa3`,`aaa4`,`aaa5`,`aaa6`,`aaa7`,`aaa8`,`aaa9`,`aaa10`,`aaa11`,`aaa12`,`aaa13`)

values (2,1,NULL,9,NULL,NULL,NULL,NULL,NULL,'',NULL,NULL,NULL,NULL)

/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;

/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;

[peterlaursen]

“That INSERT INTO is very, very long.”

And that is why raising the max_allowed_packet in server configuration may solve the import issue.

Also we will probably need to lose connection to the server/get the 'gone away' server error if we shall reproduce the program crash!

[dany]

Raising the max_allowed_packet value in server configuration solved the import issue.

Thanks 🙄

I think you should try to reproduce the program crash lowering the max_allowed_packet value.

Yesterday SQLyog crashed every single time i tried to import that DUMP file right after the “MySQL server has gone away” error.

Daniele

[peterlaursen]

we have now reproduced this — and most often that is more difficult than fixing!

[dany]

Just to let you know,

I did some little test on a Windows XP computer and I can confirm that

this bug was present also in SQLyog 6.07 enterprise.

Bye

[peterlaursen]

yes .. it is an old bug.

We have fixed the crash with this build:

http://www.webyog.com/downloads/betas/not_…QLyog612Ent.exe

You are welcome to confirm!

[dany]

Yes!

SQLyog 6.12 n3 works.

[Author]

Posts