How do I analyse knltrace and core dump after DB crash

[Former Member]

Hi there,

We are currently experience a db crash when I try to bring the DB online after a backup restore. I have performed a database structure check in admin mode and all appears to be fine.

I have posted an extract of knldiag file at the bottom of this post.

A comseg.dump file is also generated for the task (which is executing UKT7 which seems to be responsible for the data files).

I would like to analyse the knltrace and core dump files and followed instructions from Note 837385 - FAQ: SAP MaxDB database trace (VTRACE), no 13, but the generated .prt file contains only a header.

If anyone can advise how I can get more information on the cause of the kernal crash by reading the knltrace or core dump files that would be much appreciated.

kndldiag extract:

2009-12-03 03:04:18    24     53000 DATACACH Finish data cache restart
2009-12-03 03:04:18    24     53000 B*TREE   Blob file directory restart successful
2009-12-03 03:04:18    24         7 FileDir  File directory restarting
2009-12-03 03:04:18    24         8 FileDir  File directory restart completed
2009-12-03 03:04:18    24     20061 Log      History: 60 (60) files existing
2009-12-03 03:04:18    24     20064 Log      History: all history files registered, GC is ready
2009-12-03 03:04:18    24     54003 dynpool  DYNP_K51_LOCK_LIST     : 82783696
....
....
2009-12-03 03:04:18    24     54003 dynpool  LOCK TransHash size    :   3072
2009-12-03 03:04:18    24     54003 dynpool  LOCK SupplyPoolSegments:   9000
2009-12-03 03:04:18    24     54003 dynpool  LOCK SupplyPoolSize    : 79416000
2009-12-03 03:04:18    24     54003 dynpool  LOCK ObjColl_list size :  12288
2009-12-03 03:04:18    24     54003 dynpool  LOCK ObjReq_list size  :   7680
+++++++++++++++++++++++++++++++++++++++ Kernel Exit ++++++++++++++++++++++++++++
2009-12-03 03:04:22     0     11987 dump_rte rtedump written to file 'rtedump'
2009-12-03 03:04:22     0 ERR 12005 DBCRASH  Kernel exited with core and exit status 0x8b
2009-12-03 03:04:22     0 ERR 12012 DBCRASH  No stack backtrace since signal handler was suppressed by SUPPRESS_CORE=NO
2009-12-03 03:04:22     0 ERR 12009 DBCRASH  Kernel exited due to signal 11(SIGSEGV)
2009-12-03 03:04:22     0     12808 DBSTATE  Flushing knltrace pages
2009-12-03 03:04:22     0 WNG 11824 COMMUNIC Releasing  T149 kernel abort
2009-12-03 03:04:22     0     12696 DBSTATE  Change DbState to 'OFFLINE '(29)
--------------------------------------- current write position -----------------

[lbreddemann]

HI there,

nothing to be analyzed by a non-liveCache/MaxDB-developer here.

Sorry to tell you, but even if we tell you how to extract call stacks from the information, you won't be able to tell what happened without the access to the source code.

Open a support message for that and have the problem analysed by the support team.

regards,

Lars