[EMAIL PROTECTED] wrote: > Hi, > > I'm currently experimenting with LONG columns. I've stored > some 2MB files in the database. But now the database seems > full (kernel message say that database is full). > > After trying to delete the table containing the files > (which made the process hang) and deleting some other > data to make space, i see core dump messages in the kernel > traces, which I have appended. > > The database seems so corrupt now, that I cannot find any way > to repair it. > > I'm using 7.3.0.25 on SuSE 8.0. > > Can you see why the database has crashed? How can I avoid this? > Or do you have a bug fix for the next release? > > > Greetings, > > Mathias Kettner
After some trouble with his mail (MIME-format, charset=X-UNKNOWN, even the last one) we could see this message in the knldiag: Server should not run as superuser The message seen above should be read as Server may not run as superuser The database was created by superuser. This is NOT allowed. It has to be a 'normal' user. With one of the next versions this restriction will not exist any more, but with 7.3.0.25 superuser is a really bad choice for creation of a database. This has nothing to do with LONGs or any other SQl-statement. Elke SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
