cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to start MaxDB

Former Member
0 Kudos

Unable to Start MaxDB...

Here is the error lines from knldiag.

2009-10-26 22:25:04 0x169C ERR 19999 BTRACE Params: 01:00000000 02:00000000 03:00000000 04:00000000

2009-10-26 22:25:04 0xEF8 ERR 19999 BTRACE Mini dump file 'KnlMini.dmp' written!

2009-10-26 22:25:04 0xEF8 ERR 7 Messages Msg_List.cpp:3617

2009-10-26 22:25:04 0xEF8 ERR 7 Messages 2009-10-26 22:25:04 Messages Error 7

2009-10-26 22:25:04 0xEF8 ERR 7 Messages Begin of dump of registered messages

2009-10-26 22:25:04 0xEF8 ERR 8 Messages Msg_List.cpp:3636

2009-10-26 22:25:04 0xEF8 ERR 8 Messages 2009-10-26 22:25:04 Messages Error 8

2009-10-26 22:25:04 0xEF8 ERR 8 Messages End of the message list registry dump

2009-10-26 22:25:04 0xEF8 19684 TASKING Tracewriter termination timeout: 1200 sec

2009-10-26 22:25:04 0x1344 20000 Trace Trace_Writer.cpp:217

2009-10-26 22:25:04 0x1344 20000 Trace 2009-10-26 22:25:04 Trace Info 20000

2009-10-26 22:25:04 0x1344 20000 Trace Start flush kernel trace

2009-10-26 22:25:04 0x1344 19617 VOLUMEIO Single I/O attach, 'knltrace', UKT:1

2009-10-26 22:25:04 0x141C ERR 20125 RTE RTE_ExternalCall.cpp:877

2009-10-26 22:25:04 0x141C ERR 20125 RTE 2009-10-26 22:25:04 RTE Error 20125

2009-10-26 22:25:04 0x141C ERR 20125 RTE Database automatic restart failed

2009-10-26 22:25:04 0x1344 20001 Trace Trace_Writer.cpp:223

2009-10-26 22:25:04 0x1344 20001 Trace 2009-10-26 22:25:04 Trace Info 20001

2009-10-26 22:25:04 0x1344 20001 Trace Stop flush kernel trace

2009-10-26 22:25:04 0x1344 20002 Trace Trace_Writer.cpp:264

2009-10-26 22:25:04 0x1344 20002 Trace 2009-10-26 22:25:04 Trace Info 20002

2009-10-26 22:25:04 0x1344 20002 Trace Start flush kernel dump

2009-10-26 22:25:05 0x1344 20003 Trace Trace_Writer.cpp:392

2009-10-26 22:25:05 0x1344 20003 Trace 2009-10-26 22:25:05 Trace Info 20003

2009-10-26 22:25:05 0x1344 20003 Trace Stop flush kernel dump

2009-10-26 22:25:05 0x1344 19619 TASKING Releasing tracewriter

2009-10-26 22:25:05 0xEF8 19890 DIAGHIST Backup of diagnostic files will be forced at next restart

2009-10-26 22:25:05 0xEF8 19600 VERSION 'SlowKnl 7.6.00 Build 018-123-119-055'

2009-10-26 22:25:05 0xEF8 19654 DBSTATE SERVERDB 'MD8' has stopped

Any help is greatly appreciated.

Accepted Solutions (0)

Answers (1)

Answers (1)

lbreddemann
Active Contributor
0 Kudos

Hi there!

1) please post the symbolic stack back trace from the KNLDIAG file

2) DON'T use ancient MaxDB software versions like 7.6 Build 18 anymore.

There are reasons for why patches have been released. These reasons are called "fixed bugs" and "new/improved features"...

regards,

Lars

Former Member
0 Kudos

Fixed it by applying sap note 895992 .

Thanks for the quick response.