Hello Werner, your database at least contains one permanent corrupted table(no index!) identified by the root page 652499.
Make sure that you are connected as SystemDBA when executing "select * from roots where root = 652499" to get more information about the table. The error message "BD53: predsep.k > sep.k: 0" means that the calculation of a new separator in a b*tree is not possible, because one of the given keys probably from a leaf page is corrupted! If you have same time you may try to recreate the table by using a "create table/insert select" statement. This may work if only the order of the records in the corrupted table is interchanged. >From my point of view you should recover your database with the last data backup made before the first crash occur! After a successful database recovery you should execute a "check data extended" formerly known as "verify" via DBMGUI to be sure that no more defects exist. Regards, Torsten SAP Labs Berlin Sitz der Gesellschaft/Registered Office: Walldorf, Germany Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), Shai Agassi, Léo Apotheker, Werner Brandt, Claus Heinrich, Gerhard Oswald, Peter Zencke Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: Hasso Plattner Registergericht/Commercial Register Mannheim No HRB 350269 Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -----Original Message----- From: Werner Jörling [mailto:[EMAIL PROTECTED] Sent: Thursday, May 17, 2007 11:46 AM To: maxdb@lists.mysql.com Subject: DB crashes each day, cannot detect the table or index Hi, my database-server crashes each day at the same time (from about 01:40 to 01:50). The knldiag contains each time the messages: ----------------------------------------- 2007-05-16 01:48:04 22 ERR 53187 B*TREE BD53: predsep.k > sep.k: 0 2007-05-16 01:48:04 22 ERR 53000 B*TREE 0D0000000000000197FA000000000000 2007-05-16 01:48:04 22 ERR 53000 B*TREE Table Root 652499 2007-05-16 01:48:04 22 ERR 53372 B*TREE Base error: invalid_leaves_str 2007-05-16 01:48:04 22 ERR 53372 B*TREE Corrupted b*tree index; 0 2007-05-16 01:48:04 22 40 Admin Kernel state: 'OFFLINE' reached 2007-05-16 01:48:04 22 40 Admin + 2007-05-16 01:48:04 Admin Error 2 2007-05-16 01:48:04 22 40 Admin - A fatal error caused EMERGENCY SHUTDOWN. core is written 2007-05-16 01:48:04 22 ERR 11196 DBCRASH vabort:Emergency Shutdown, Kernel_Administration.cpp: 602 2007-05-16 01:48:04 22 ERR 11599 BTRACE ----> Emergency Stack Back Trace ------------------------------------------ The query SELECT * FROM roots WHERE root = 652499 does not find a result. Any idea what I can do? Regards Werner Jörling -- E-Mail [EMAIL PROTECTED] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
