Hi, > -----Original Message----- > From: Renner Klaus [mailto:[EMAIL PROTECTED] > Sent: Dienstag, 17. Juni 2003 17:14 > To: [EMAIL PROTECTED] > Subject: -24994,ERR_RTE: runtime environment error on Solaris > 5.8 sun4us > s parc > > > Hello, > > I cannot find why create_sem fails with "No space left on device"
Because UNIX system error messages are sometimes misleading... > Are the resources listed below not enough for sapdb? Not nearly.... > > ... > start track001 failed: ERR > -24994,ERR_RTE: runtime environment error > 1,Check knldiag! Kernel died before reaching ADMIN state > ########################### > $ cat ./wrk/TRACK001/knldiag.err > -------------------------------------------------------------- > -------------- > ---- > Date Time TID Typ MsgID Label Message-Text > -------------------------------------------------------------- > -------------- > ---- > 2003-06-17 16:38:37 --- Starting GMT > 2003-06-17 > 14:38:3 > 7 7.4.3 Build 017-123-039-277 > 2003-06-17 16:38:40 1 ERR 11277 IPC create_sem: > semget error, No > space > left on device > 2003-06-17 16:38:40 --- Starting GMT > 2003-06-17 > 14:38:4 > 0 QUICK 7.4.3 Build 017-123-039-277 > 2003-06-17 16:38:42 1 ERR 11277 IPC create_sem: > semget error, No > space > left on device > 2003-06-17 16:38:42 --- Starting GMT > 2003-06-17 > 14:38:4 > 2 SLOW 7.4.3 Build 017-123-039-277 > 2003-06-17 16:38:44 1 ERR 11277 IPC create_sem: > semget error, No > space > left on device > ###########################solaris:prtconf says: > Memory size: 12288 Megabytes > ########################### > sysdef tells: > * > * IPC Messages > * > 2048 max message size (MSGMAX) > 4096 max bytes on queue (MSGMNB) > 50 message queue identifiers (MSGMNI) > 40 system message headers (MSGTQL) > * > * IPC Semaphores > * > 10 semaphore identifiers (SEMMNI) > 60 semaphores in system (SEMMNS) > 30 undo structures in system (SEMMNU) > 25 max semaphores per id (SEMMSL) > 10 max operations per semop call (SEMOPM) > 10 max undo entries per process (SEMUME) > 32767 semaphore maximum value (SEMVMX) > 16384 adjust on exit max value (SEMAEM) On our development server i found in /etc/system *--------------------------------------------------------------------------- * Semaphores parameters set for SAP & DB's: set semsys:seminfo_semmap=9218 set semsys:seminfo_semmni=9216 set semsys:seminfo_semmns=18432 set semsys:seminfo_semmnu=8192 set semsys:seminfo_semume=160 set semsys:seminfo_semmsl=75 set semsys:seminfo_semopm=50 The rearly needed amount depends on the number of connection you want to support. For each UKT a semaphore is needed to inform about incoming packets and each connection needs a semaphore to be informed about replys. > * > * IPC Shared Memory > * > 1048576 max shared memory segment size (SHMMAX) > 1 min shared memory segment size (SHMMIN) > 100 shared memory identifiers (SHMMNI) > 6 max attached shm segments per process (SHMSEG) > ########################### > This would limit your number of concurrent UKT to SHMSEG-1. I would rather suggest at least to increase SHMSEG to 256... On our development server i found in /etc/system *--------------------------------------------------------------------------- * Shared memory parameters set for SAP & DB's software: * 1638 MB shminfo_shmmax set shmsys:shminfo_shmmax=1717567488 set shmsys:shminfo_shmmni=1024 set shmsys:shminfo_shmseg=256 > I am using SAPDB 7.4 > > Thanks for your help > > Klaus Renner > _______________________________________________ > sapdb.general mailing list > [EMAIL PROTECTED] > http://listserv.sap.com/mailman/listinfo/sapdb.general CU jrg _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
