Greetings Daniel. Ok, thats great. Now, does SAPDB have any kind of definitions/rules/guidlines for the correct semaphore/shared memory segment setup for Linux (and Solaris for that matter)? I have found this kind of guideline document for POSTGRES under Linux, but nothing for SAPDB.
The current settings in the /usr/include/linux/sem.h file is as follows: #define SEMMNI 128 /* <= IPCMNI max # of semaphore identifiers */ #define SEMMSL 250 /* <= 8 000 max num of semaphores per id */ #define SEMMNS (SEMMNI*SEMMSL) /* <= INT_MAX max # of semaphores in system */ #define SEMOPM 32 /* <= 1 000 max num of ops per semop call */ #define SEMVMX 32767 /* <= 32767 semaphore maximum value */ In addition I have added the following lines to the /etc/sysctl.conf file (increasing the SHMMAX and SHMALL values to 128MB from 32MB): kernel.shmall = 134217728 kernel.shmmax = 134217728 This has not fixed the problem though, and I don't want muck about too much without first finding out if you can assist here!? Many thanks in advance, Carl -----Original Message----- From: Dittmar, Daniel [mailto:[EMAIL PROTECTED]] Sent: 17 June 2002 12:28 To: '[EMAIL PROTECTED]'; Sapdb. General@Listserv. Sap. Com Subject: RE: Problems with multiple database instances > All is fine and my db instances are running smoothly UNTIL: > > I try and create/start my 6th instance (if 5 other instances are running)!! > > Is there some limit to the number of database instances you can run? There is no fixed limit about the number of running SAP DB instances. But a dabase instance uses limited global resources like semaphores and shared memory. You'll have to look into knldiag to see which resource was the limiting factor and then reconfigure the Linux kernel accordingly. Daniel Dittmar -- Daniel Dittmar SAP DB, SAP Labs Berlin [EMAIL PROTECTED] http://www.sapdb.org/ _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
