Miguel,

the failing assertion is in dict_load_table():

        ut_a(DB_SUCCESS == dict_load_foreigns(table->name));

Are you sure you do not have foreign keys which REFERENCE those tables?

4.0.13 has better diagnostics. Please upgrade to it if you are not using
MySQL replication.

"
Fixed a bug: if you dropped a table to which there was a FOREIGN KEY
reference, and later created the same table with non-matching
column types, InnoDB could assert in dict0load.c, in function
dict_load_table.
"
Regards,

Heikki

----- Original Message ----- 
From: "Miguel Perez" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, July 02, 2003 12:47 AM
Subject: Re: ERROR 2013:Lost connection to MySQL server


> I am running  the 4.0.12 version
> For those tables I don't have FOREIGN KEYS here is the table desc.
>
> CREATE TABLE CLIENTE (
>   FINGCIOID smallint(6) NOT NULL default '0',
>   FINOTIENDA smallint(6) NOT NULL default '0',
>   FICTEID int(11) NOT NULL default '0',
>   FIDIGITOVER smallint(6) NOT NULL default '0',
>   FIOCUID smallint(6) NOT NULL default '0',
>   FCCTENOMBRE char(18) NOT NULL default '',
>   FCCTEAPATERNO char(18) NOT NULL default '',
>   FCCTEAMATERNO char(18) NOT NULL default '',
>   FCCTEDIRCALLE char(25) NOT NULL default '',
>   FCCTEDIRNOEXT char(5) NOT NULL default '',
>   FCCTEDIRNOINT char(5) NOT NULL default '',
>   FCCTECP char(5) NOT NULL default '',
>   FCCTECOLONIA char(65) NOT NULL default '',
>   FCCTESEXO char(1) NOT NULL default '',
>   FCCTETEL char(15) NOT NULL default '',
>   FCCTERFC char(14) NOT NULL default '',
>   FCCTEFISMOR char(2) NOT NULL default '',
>   FITDAATIENDE smallint(6) NOT NULL default '0',
>   FDCTEFECALT datetime NOT NULL default '0000-00-00 00:00:00',
>   FLCTEECO smallint(6) NOT NULL default '0',
>   FIEDOCIVIL smallint(6) NOT NULL default '0',
>   FNLINEACRED decimal(8,2) NOT NULL default '0.00',
>   FDCTEFECNAC datetime NOT NULL default '0000-00-00 00:00:00',
>   FCNOCOBRADOR char(6) NOT NULL default '',
>   FITRANNO int(11) NOT NULL default '0',
>   KEY cliente (FCCTENOMBRE,FCCTEAPATERNO,FCCTEAMATERNO,FINOTIENDA)
> ) TYPE=InnoDB;
>
> CREATE TABLE PEDIDO (
>   FISUCURSAL int(11) NOT NULL default '0',
>   FINOPEDIDO int(11) NOT NULL default '0',
>   FINGCIOID smallint(6) NOT NULL default '0',
>   FICTEID int(11) NOT NULL default '0',
>   FINOTIENDA smallint(6) NOT NULL default '0',
>   FIDIGITOVER smallint(6) NOT NULL default '0',
>   FCEMPNO char(6) NOT NULL default '',
>   FITIPOVENTA smallint(6) NOT NULL default '0',
>   FDPEDFEC datetime NOT NULL default '0000-00-00 00:00:00',
>   FNPEDTOTAL decimal(12,2) NOT NULL default '0.00',
>   FIPEDFACT int(11) NOT NULL default '0',
>   FDFECFACT datetime NOT NULL default '0000-00-00 00:00:00',
>   FIPEDSTAT smallint(6) NOT NULL default '0',
>   FCUSERID char(10) NOT NULL default '',
>   FCWS char(10) NOT NULL default '',
>   FDFECSURT datetime NOT NULL default '0000-00-00 00:00:00',
>   FNPEDSALDO decimal(12,2) NOT NULL default '0.00',
>   FCFOLIOPARAM int(11) NOT NULL default '0',
>   FDFECIMPFACTURA datetime NOT NULL default '0000-00-00 00:00:00',
>   FIDIASSERV smallint(6) NOT NULL default '0'
> ) TYPE=InnoDB;
>
> And I haven't tried to downgrade my version.
>
> Greetings
>
>
>
> >From: "Heikki Tuuri" <[EMAIL PROTECTED]>
> >To: <[EMAIL PROTECTED]>
> >Subject: Re: ERROR 2013:Lost connection to MySQL server
> >Date: Wed, 2 Jul 2003 00:35:09 +0300
> >
> >Miguel,
> >
> >what exact MySQL version you are running?
> >
> >Have you created FOREIGN KEY constraints to those tables?
> >
> >Have you downgraded to a lower MySQL version?
> >
> >Regards,
> >
> >Heikki
> >
> >----- Original Message -----
> >From: ""Miguel Perez"" <[EMAIL PROTECTED]>
> >Newsgroups: mailing.database.mysql
> >Sent: Wednesday, July 02, 2003 12:11 AM
> >Subject: Re: ERROR 2013:Lost connection to MySQL server
> >
> >
> > > The OS I'm using is Red Hat 7.3, and the mysql version is 4.0
> > >
> > > The wierd thing is that I could access those tables but just after I
> > > rebooted my PC
> > > I couldn't access the 2 tables.
> > > The log files has the following:
> > >
> > > "030701 14:27:38  InnoDB: Assertion failure in thread 36874 in file
> > > dict0load.c line 677
> > > InnoDB: We intentionally generate a memory trap.
> > > InnoDB: Send a detailed bug report to [EMAIL PROTECTED]
> > > mysqld got signal 11;
> > > This could be because you hit a bug. It is also possible that this
> >binary
> > > or one of the libraries it was linked against is corrupt, improperly
> >built,
> > > or misconfigured. This error can also be caused by malfunctioning
> >hardware.
> > > We will try our best to scrape up some info that will hopefully help
> > > diagnose
> > > the problem, but since we have already crashed, something is
definitely
> > > wrong
> > > and this may fail. thd=0x8711eb8
> > > Attempting backtrace. You can use the following information to find
out
> > > where mysqld died. If you see no messages after this, something went
> > > terribly wrong...
> > > Cannot determine thread, fp=0xbfe7e0c8, backtrace may not be correct.
> > > Stack range sanity check OK, backtrace follows:
> > > 0x80741ea
> > > 0x8286058
> > > 0x81193b5
> > > 0x8108df8
> > > 0x80cf9c9
> > > 0x80c9bf4
> > > 0x8096a76
> > > 0x809262b
> > > 0x8091ccf
> > > 0x8092989
> > > 0x80e1d18
> > > 0x807fdd6
> > > 0x8082638
> > > 0x807dd5d
> > > 0x8083b6e
> > > 0x807cf0f
> > > 0x828380c 0x82b6f1a
> > > New value of fp=(nil) failed sanity check, terminating stack trace!
> > > Please read http://www.mysql.com/doc/en/Using_stack_trace.html and
> >follow
> > > instructions on how to resolve the stack trace. Resolved
> > > stack trace is much more helpful in diagnosing the problem, so please
do
> > > resolve it
> > > Trying to get some variables.
> > > Some pointers may be invalid and cause the dump to abort...
> > > thd->query at 0x87170a8 = show create table PEDIDOS
> > > thd->thread_id=1
> > > "
> > >
> > > I have 500MB in ram.
> > >
> > > Greetings
> > >
> > > >From: Fred van Engen <[EMAIL PROTECTED]>
> > > >To: Miguel Perez <[EMAIL PROTECTED]>
> > > >CC: [EMAIL PROTECTED]
> > > >Subject: Re: ERROR 2013:Lost connection to MySQL server
> > > >Date: Tue, 1 Jul 2003 21:23:41 +0200
> > > >
> > > >Hi,
> > > >
> > > >On Tue, Jul 01, 2003 at 02:13:23PM -0500, Miguel Perez wrote:
> > > > > I have the following problem, when I try to connect to my DB
> >servicios
> > > > > I get connected succesfully, but when I try to access certain
tables
> >I
> > > >get
> > > > > the error
> > > > > "ERROR 2013: Lost connection to MySQL server during query" but
only
> >with
> > > > > those certain tables, to be more specific there's only 2 tables
that
> >i
> > > > > can't access, I get that error,
> > > > > the other ones works fine.
> > > > >
> > > >
> > > >Which version, which OS?
> > > >
> > > >
> > > > > Any ideas or suggestions.
> > > > >
> > > >
> > > >Maybe mysqld crashes? It restarts automatically, on unices at least.
> > > >
> > > >Check the mysql error log to find out if it crashed.
> > > >
> > > >
> > > >Regards,
> > > >
> > > >Fred.
> > > >
> > > >--
> > > >Fred van Engen                              XB Networks B.V.
> > > >email: [EMAIL PROTECTED]                Televisieweg 2
> > > >tel: +31 36 5462400                         1322 AC  Almere
> > > >fax: +31 36 5462424                         The Netherlands
> > >
> > > _________________________________________________________________
> > > Charla con tus amigos en línea mediante MSN Messenger:
> > > http://messenger.microsoft.com/es
> > >
> > >
> > > --
> > > MySQL General Mailing List
> > > For list archives: http://lists.mysql.com/mysql
> > > To unsubscribe:
> >http://lists.mysql.com/[EMAIL PROTECTED]
> > >
> >
> >
> >
> >--
> >MySQL General Mailing List
> >For list archives: http://lists.mysql.com/mysql
> >To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]
> >
>
> _________________________________________________________________
> MSN Fotos: la forma más fácil de compartir e imprimir fotos.
> http://photos.msn.es/support/worldwide.aspx
>



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to