Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
RE: AW: ERROR 'illegal_filename' CAUSED EMERGENCY SHUTDOWN
From: Hahn, Uwe (uwe.hahnsap.com)
Date: Fri May 28 2004 - 01:51:19 CDT
"filename" does not mean files in a filesystem
it means a database file in the data area.
Tables and indexes are examples for files.
The catalog maps the user.tablename to an internally used filename.
Please repeat the restart with enabled vtrace.
db_online => database goes offline
trace_prot akbx => this produces the trace file DJHDB01.prt
in the rundirectory.
Please compress the file and send it back.
Please append dbm.prt, dbm.utl as well.
From which db version was the backup taken ?
>From: Sven Köhler [mailto:skoehlerupb.de]
>Sent: Friday, May 28, 2004 2:36 AM
>To: Brunzema, Martin
>Subject: Re: AW: ERROR 'illegal_filename' CAUSED EMERGENCY SHUTDOWN
>>>what can i do if knldiag.err conatins the following?
>>>2004-05-27 03:46:14 --- Starting GMT
>>>01:46:14 7.5.0 Build 012-121-071-233
>>>2004-05-27 03:47:30 2577 ERR 8 Admin ERROR
>>>CAUSED EMERGENCY SHUTDOWN
>>>i can put the DB into Admin-Mode, but warming fails.
>>>The DB was restored from a complete backup. I was using Max
>> have a look into the file knldiag. You should find there the
>> same error message, but hopefully some more information about
>> the context of the error (e.g. a message about the attach of a
>> Also have a look at your parameters. Maybe you can find there
>> a strange looking filename.
>I don't see any abnormal or false path-names in the paramters. I can
>create a blank database. The moment i restore my complete backup from
>another machine that runs SAPDB 7.4, the kernel fails to start. I
>attached the knldiag etc.
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb