I our case, changing MAXUSERTASKS does not effect the number of threads (all other parameters remaining the same).
With MAXUSERTASKS = 16, (not counting vserver) I get 25 threads when I come up to cold state, 51 up to warm state : $ /opt/sapdb/depend/bin/dbmcli -d DBT2 -u dbm,dbm db_cold OK $ ps -aef |grep sapdb |grep kernel| grep -v grep |wc -l 25 $ /opt/sapdb/depend/bin/dbmcli -d DBT2 -u dbm,dbm db_warm OK $ ps -aef |grep sapdb |grep kernel| grep -v grep |wc -l 51 Then, I set (via dbmcli) MAXUSERTASKS to 32 (check and commit the parameter), offline the database. Counting the number of threads at db_cold and db_warm state, I get exactly the same number of threads as the MAXUSERTASKS 16 case. I repeated this twice and checked the MAXUSERTASKS setting each time to make sure it changed. On Wed, 2003-02-05 at 08:08, Zabach, Elke wrote: > Holland, John wrote: > > > how can i limit the number of started kernel tasks for one database... > > or where can find information on this subject? > > for one database instance you have specified > MAXUSERTASKS > during the installation of the database. > > MAXUSERTASKS is the > Maximum number of simultaneously active users (database sessions) > default is 50. > > You should check this parameter. You can change this parameter > even for existing databases. The new value will be used when kernel > is started again (offline-mode --> online/warm-mode) > > Elke > SAP Labs Berlin > _______________________________________________ > sapdb.general mailing list > [EMAIL PROTECTED] > http://listserv.sap.com/mailman/listinfo/sapdb.general -- Mary Edie Meredith <[EMAIL PROTECTED]> Open Source Development Lab _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
