Heiko Giesselmann wrote:
Hi all,

our MaxDB server (based on build 7.5.0 Build 014-123-073-298) seems to
have crashed - see attached knldiag.err. The crash seems to be related
to a B-Tree corruption. Are any checks other than the database check
from Database Manager recommended to verify consistency of the database
after the crash?

Anybody any idea if this is a known bug and if/when it will be fixed?

2004-07-14 10:28:42      0x93C ERR 53133 DATACACH Illegal Req  PNO 17065 PTR 58207E7E
2004-07-14 10:28:42      0x93C ERR 53000 B*TREE   07010000000000000307000000000000
2004-07-14 10:28:42      0x93C ERR 53000 B*TREE   INDEX ROOT  15029
...
2004-07-14 10:28:45 0x93C ERR 19999 BTRACE kernel!bd20GetPage + 700 bytes
2004-07-14 10:28:45 0x93C ERR 19999 BTRACE SFrame: IP:00667a5c RA:00657127 FP:09248cf8 SP:09248d00 2004-07-14 10:28:45 0x93C ERR 19999 BTRACE Params: 01:0000003e 02:0925f9fc 03:0925f9be 04:0925f9da 2004-07-14 10:28:45 0x93C ERR 19999 BTRACE Source: vbd20.c ( Line: 2653 )

this looks like bug # http://www.sapdb.org/webpts?wptsdetail=yes&ErrorType=0&ErrorID=1130326 and is 'work in progress'

  Henrik

--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]



  • MaxDB crash Heiko Giesselmann
    • Re: MaxDB crash Henrik Hempelmann

Reply via email to