Hi again, is there no solution for this problem? Its now getting even worser. Shortly after rebuilding the primary key, we've got the same error again and data is not updated.
regards Michael Ruf Am Freitag, 1. April 2005 09:27 schrieb Michael Ruf: > Hi, > > we have occasionally problems with some of our MaxDB instances. If we try > to update a record we got the following error: > "[-9049] System error: BD Primkey from inv in primtree not found" > > DB Version is 7.5.00.23. > There is no message in krnldiag. > Here the message from krnldiagerror: > 2005-04-01 09:02:58 12953 ERR 51080 SYSERROR -9049 BD Primkey from inv in > primtree no > > After recreation of the primary key it works again for some time. > What is the reason and how can we prevent this error? > > regards > Michael Ruf -- ---------------------------------------------- Softwareentwicklung, Inxmail GmbH Tel. +49 (0)761/29 69 79-0 <http://www.inxmail.de> ---------------------------------------------- P.S.: Versenden personalisierter E-Mails - mit Inxmail ein Kinderspiel! http://www.inxmail.de -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
