Ok, checking the running tasks I noticed that the "niserver" process was missing. "/opt/sapdb/indep_prog/bin/x_server start" should do the trick. Should ;)
The niserver isn't needed, so it's best to start x_server with the -Y option.
The same problem we had one week ago. Then we made the mistake to
shut down the database and didn't get it running again (kernel died
before reaching blablabla).
Have you tried a dbmcli ... db_clear after the shutdown? This should remove any IPC resources that refuse to leave voluntarily.
A look at the knldiag could be also helpful, both when something unusual happens and when an instance won't come up.
Daniel Dittmar
-- Daniel Dittmar SAP DB, SAP Labs Berlin [EMAIL PROTECTED] http://www.sapdb.org
-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
