Hi Daniel,

the standard protocol-file is named knldiag. It will be
overwriten each time the database is restarted. A copy will
saved in the file knldiag.old. But also this copy is overwritten
at the second restart after a crash.

Another copy of the file knldiag may be saved into a subdirectoy of
DIAGHISTORY. Search there for the file knldiag and have a look
at the dates in the subdirectory-names.

The file knldiag.err contains also contains a history of the 
"most important" errors and is never overwritten.
Kind regards, Martin
  

-----Original Message-----
From: Daniel Castro [mailto:[EMAIL PROTECTED] 
Sent: Monday, February 13, 2006 2:05 PM
To: maxdb@lists.mysql.com
Subject: Log Analysis

Hi,

I am new to SAPDB. I am using SAPDB on Suse Linux 10.0
Everything is fine, but in the last 2 months the database crashed 1 time and
I couldn't see why...
How can I read the log files to discover the problem?
Can you help me or send me an article about it?

Attachment: smime.p7s
Description: S/MIME cryptographic signature

  • Log Analysis Daniel Castro
    • RE: Log Analysis Brunzema, Martin

Reply via email to