> However, I couldn't find any hints on the internet how to set > up these values. Does anyone know hot to set them up properly > for MaxDB? There are only resources available on the net for > Oracle or other DBs.
This depends on the box... Here on a Solaris 9/x86 (32bit!) I have the following settings: set rlim_fd_max = 65535 set rlim_fd_cur = 8192 set shmsys:shminfo_shmmin = 1 set shmsys:shminfo_shmmax = 4294967295 set semsys:seminfo_semmni = 512 set shmsys:shminfo_shmseg = 512 set semsys:seminfo_semmns = 1024 set semsys:seminfo_semmsl = 256 set semsys:seminfo_semopm = 256 Usually these entries only set the max. values so it shouldn't become a problem (in this case). Greetz, SIEGENIA-AUBI KG Informationswesen i.A. Markus D�hr SAP-CC/BC, SAPDB-DBA Tel.: +49 6503 917-152 Fax: +49 6503 917-7152 E-Mail: [EMAIL PROTECTED] Internet: http://www.siegenia-aubi.com > -----Original Message----- > From: Dominic Veit [mailto:[EMAIL PROTECTED] > Sent: Friday, April 15, 2005 11:56 AM > To: Brunzema, Martin; [email protected] > Subject: Re: AW: MaxDB not available for ca. 1 minute > > Hi Martin, > > in knldiag is no message. However, I forgot to look at > xserver_HOSTNAME.prt and I there I got a message: > > 2005-04-15 10:30:58 12735 ERR 11277 IPC create_sem: > semget error, > No space left on device > > I think we have to restart the machine with the following > /etc/system file settings: > > --- > (...) > set semsys:seminfo_semmap=691200 > set semsys:seminfo_semmni=9216 > set semsys:seminfo_semmns=691200 > set semsys:seminfo_semmnu=9216 > set semsys:seminfo_semume=160 > set semsys:seminfo_semmsl=75 > set semsys:seminfo_semopm=75 > --- > > > Best, > > Dominic > > Brunzema, Martin wrote: > > > >>-----Urspr�ngliche Nachricht----- > >>Von: Dominic Veit [mailto:[EMAIL PROTECTED] > >>Gesendet: Freitag, 15. April 2005 11:14 > >>An: [email protected] > >>Betreff: MaxDB not available for ca. 1 minute > >> > >> > >>Hi, > >> > >>we have a MaxDB running productive: > >> > >>X64/SUN 7.5.0 Build 015-123-074-675 (Application > startup program) > >>X64/SUN 7.5.0 Build 015-123-074-675 (vserver) > >> > >>OS (as stated above) is Solaris 9. > >> > >>Since a couple of days we encounter a strange problem. The Database > >>does not service for ca. 1 minute and is then completely back. > >>However, I cannot find anything in the log-files. The last > entries are > >>from mid march. No entries for april, neither anything that > states any > >>difficulties. > >> > >>Is there anybody who has encountered this problem, too? > >> > >>Since this is a productive system, this is extremely urgent. > > > > > > Hi Dominic, > > > > have a look into the file knldiag. Maybe you have autosave-log > > activated, but your logvolume is too small. Then your > application runs > > into a logfull- situation (i.e. they wait until log is freed) until > > the autosave starts again and saves log. If this is the case simply > > add another logvolume and eventually adjust the parameter > LOG_SEGEMENT_SIZE to your needs. > > > > kind regards, Martin > > > > -- > Dominic Veit M.A. > University Hospital Freiburg > CwebRD (Center for web-based Research and Patient Databases) > Breisacherstr. 60 > 79106 Freiburg > Tel.: +49 (0)761 270 37 84 > E-mail: [EMAIL PROTECTED] > > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
