For linux, check to make sure /proc/sys/shmmax is high enough. You should be able to verify that is the problem if there are shmget (or even malloc) errors in the knldiag file.
I can raise mine to 500 if I have shmmax set high enough. On Fri, 2002-07-26 at 16:41, Jenny Zhang wrote: > I am running SAPDB 7.3.0.23 on RedHat 7.2 > I have an 8-way system with 16G memory. > > I am trying to increase concurrent database connections. > MAXUSERTASKS is 100. > > But I can only get 70 connections. The knldiag says: > 2002-07-26 14:28:05 8413 WNG 11832 COMMUNIC rejecting request > 2002-07-26 14:28:08 8413 WNG 11837 COMMUNIC ALL are busy (in all UKTs) > > I can make the same number of database connections on a 2-way system > with 1G memory. So I guess the system limitation is not memory. > > Where can I check what system resources limits the database connection? > Any other parameter I can play with (either database or kernel)? > > Thanks in advance, > Jenny > -- > Jenny Zhang > Open Source Development Lab Inc > 15275 SW Koll Parkway - Suite H > Beaverton, OR 97006 > (503)626-2455 ext 31 > > _______________________________________________ > sapdb.general mailing list > [EMAIL PROTECTED] > http://listserv.sap.com/mailman/listinfo/sapdb.general -- Mark Wong - - [EMAIL PROTECTED] Open Source Development Lab Inc - A non-profit corporation 15275 SW Koll Parkway - Suite H - Beaverton OR, 97006 (503)-626-2455 x 32 (office) (503)-626-2436 (fax) http://www.osdl.org/archive/markw/ _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
