Hello Arne, I think it's not a hardware problem but finding the error will take longer. You should upgrade to build 32, which is the latest published build as I could see. With build 32 dropping the index should be safe.
Regards, Uwe >-----Original Message----- >From: Arne Gehlhaar [mailto:[EMAIL PROTECTED] >Sent: Tuesday, August 24, 2004 8:31 AM >To: Hahn, Uwe >Cc: [EMAIL PROTECTED] >Subject: Re: DB crash > > >Hello Uwe, > >thanks for the help. So is it save to drop the effected index, >or could >that crash the DB as well? > >Have you been able to determine the cause (hw / sw) by looking at the >dumped page? Does the fact that we use raw devices have any >significance? > >Regards, >Arne > > >Hahn, Uwe wrote: >> Thanks Arne, >> >> with "recovery" I meant log and data of course so that you >shouldn't have any data loss. >> Nevertheless with "select * from roots where root = 50956" >you will find the index and the table. >> The -9000 error does not cause such problems. This is a >different problem. >> Normally page errors come from hardware errors (disc or >controller) but I will have a look into the dumped page if it >could be a software bug. >> >> kind regards, >> Uwe > >-- >Institut fuer Seeverkehrswirtschaft und Logistik http://www.isl.org/ >Arne Gehlhaar mailto:[EMAIL PROTECTED] >Universitaetsallee GW1 Block A tel:+49 421 22096-49 >D-28359 Bremen fax:+49 421 22096-55 > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
