Check and repair all indexes. I believe there is even an option to make MaxDB automatically repair indexes on startup.
robert 2007/5/17, Werner Jörling <[EMAIL PROTECTED]>:
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]
-- Have a look: http://www.flickr.com/photos/fussel-foto/ -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
