Hi,
last time i saw that error, it happened to me on a SuSE 9.1 system while starting a MaxDB 7.5 database instance, that was restored with a backup made by SAPDB 7.4. Now it happened to me on a Gentoo-Linux-System while upgrading a 7.5.0.15 installation to 7.5.0.16. The databse-instance doesn't want to start, and the knldiag shows this error:
2004-08-21 16:37:51 4929 34 Admin Kernel state: 'REDO LOG' finished
2004-08-21 16:37:51 4929 54003 dynpool DYNP_A42_PARSEID : 600
2004-08-21 16:37:51 4929 54000 OBJECT /opt/sapdb/7500/lib/liboms
2004-08-21 16:37:51 4929 51381 MIGRAT start of catalog migration : source is
2004-08-21 16:37:51 4929 51381 MIGRAT Kernel 7.5.0 Build 015-121-074-675
2004-08-21 16:37:52 4929 ERR 8 Admin ERROR 'illegal_filename' CAUSED EMERGENCY SHUTDOWN
2004-08-21 16:37:52 4929 12696 DBSTATE Change DbState to 'SHUTDOWN'(25)
I don't want this to happen to me all the time. How can i help to track the error? What does the catalog migration do? does it run external commands or such stuff? I really don't want this to happen to me each time i upgrade the kernel.
-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
