> DB geeks, > > we reinstalled our experimental server with SuSE 9.1 and SAPDB 7.3.0.25. > We have several customer databases running, about 20 database instances > I guess. Each db is about 500 to 2000 MB in size in only one devspace. > The server is an old Athlon 900 with 768 MB RAM (ok, maybe this is an > option...) > > After setting the LD_ASSUME_KERNEL=2.4.1 option all things are working > fine > now - with one exception:
IIRC I had LD_ASSUME_KERNEL=2.2.5 with SAPDB 7.4 on RedHat 9, maxbe you could try? Something else (just guessig), I have /sbin/sysctl -w kernel.shmmax=104857600 in my init script. Maybe SHM is the problem? > > When starting the 6th database we get the error > > -24994 runtime environment error [db_warm -f]; 1, Kernel died before > reaching COLD state > > The databases that have been started before are running properly. It seems > that > there is a problem with the sixth instance of the SAPDB kernel. We fizzled > around a little > with trying to start the databases in another order, but still the 6th > kernel does not > startup to warm state. > > OK, we know the environment is not very uptodate, but it was running fine > with installation > before (when we used SuSE 8.0). > > Are there some kernel parameters to set on the 9.1 environment? > Is there another limit that is memory related and handicaps the amount of > the kernel instances? > Is the SuSE kernel buggy in combination with the old 7.3.0.25 SAPDB? > > In advance: we cannot upgrade to other SAPDB/MaxDB version. Now that you told us, everybody is interested to hear why :) Simon > > Folks, any hint ist welcome. > > Tilmann Starke > > SOFTWORK GmbH > www.softwork.de > > Help to prevent global warming by writing cool software... > > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]