Hi,
as I said previously, the knldiag.err or knldiag both don't give any hint
about the problem. They don't even get touched (see the date). And I
confirmed that it's the right knldiag.err via slocate (its the only
knldiag.err).
1497-1 SAG_VIP # pwd
/var/opt/sdb/data/wrk/SAG_VIP
1497-1 SAG_VIP # date
Fri Feb 24 10:56:19 CET 2006
1497-1 SAG_VIP # ls -la knldiag*
-rw-rw---- 1 sdb sdba 834134 Feb 23 10:11 knldiag
-rw-rw---- 1 sdb sdba 344 Oct 18 17:20 knldiag.err
1497-1 SAG_VIP # cat
knldiag.err
--------------------------------------------------------------------------------
Date Time TID Typ MsgID Label
Message-Text
--------------------------------------------------------------------------------
2005-10-18 17:20:07 --- Starting GMT 2005-10-18
15:20:07 7.5.0 Build 030-121-100-791
So the only information I have, is that our disk ran full and now the DB is
somehow confused(?).
Still eagerly waiting for a solution, :-)
Daniel
> Hello Daniel,
>
> could you look up the knldiag file, and post the error found there to the
> list?
> The -24994 error simply means the database server ('kernel') terminated
> itself
> after start after detecting some eror (which is detailed in the knldiag
> file).
>
> Regards
> Alexander Schröder
> SAP DB, SAP Labs Berlin
--
DSL-Aktion wegen großer Nachfrage bis 28.2.2006 verlängert:
GMX DSL-Flatrate 1 Jahr kostenlos* http://www.gmx.net/de/go/dsl
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
