Hi Uwe, Yep, that's exactly what I'm seeing! It is fixed by using set log auto overwrite on.
The kernal diag is below. by the way, what does the WRN 19425 DBSTATE Shared exceeds available memory message mean? Thanks, David Starting SERVERDB: 'KIOSK' 2003-06-10 08:31:19 0x7D8 19770 INFO SERVERNODE: 'buckthorn.mw.prtdev.lexmark.com' 2003-06-10 08:31:19 0x7D8 19771 INFO Process ID: 964 2003-06-10 08:31:19 0x7D8 19773 INFO Date: 2003-06-10 2003-06-10 08:31:19 0x7D8 19772 INFO Owner: 'SYSTEM' 2003-06-10 08:31:19 0x7D8 19775 INFO Processors: 1 2003-06-10 08:31:19 0x7D8 19782 INFO Fiber: 'YES' 2003-06-10 08:31:19 0x7D8 19776 INFO Max virtual memory: 2047 MB 2003-06-10 08:31:19 0x7D8 19777 INFO Total physical memory: 127 MB 2003-06-10 08:31:19 0x7D8 19778 INFO Available physical memory: 37 MB 2003-06-10 08:31:19 0x7D8 19779 INFO Kernel shared data size: 126 MB 2003-06-10 08:31:19 0x7D8 WRN 19425 DBSTATE Shared exceeds available memory ------- more good stuff --------at the end of the log 2003-06-10 08:32:05 0x6C 19651 CONNECT Connection released, T69 2003-06-10 08:32:05 0x6C 19633 CONNECT Connect req. (T69, Node:'', PID:1716) 2003-06-10 08:32:05 0x6C 19651 CONNECT Connection released, T69 2003-06-10 08:43:03 0x7D8 ERR 18431 MESSAGES Could not write to event log, rc = 31 2003-06-10 08:43:03 0x7D8 WRN 19406 DBSTATE SERVERDB is being stopped in ONLINE state 2003-06-10 08:43:04 0x7D8 19684 TASKING Tracewriter termination timeout: 1200 sec 2003-06-10 08:43:05 0x288 19617 VOLUMEIO Single I/O attach, 'knltrace', UKT:1 ----- nothing more After restarting the SAPDB: KIOSK ser vice again will get this consistantly ---- the two questionable statements WRN 19425 DBSTATE Shared exceeds available memory ERR 18431 MESSAGES Could not write to event log, rc = 31 Cheers, David "Hahn, Uwe" <[EMAIL PROTECTED]> on 10/06/2003 02:30:41 AM To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> cc: [EMAIL PROTECTED] Subject: RE: How to turn off logging in sapdb ? Do you mean with switched off log writing the database could not become online ? This is not what should happen. Do you have any details describing that behaviour (knldiag,...) ? Yes, I can confirm that the log size only can be increased with db_addvolume. Kind regards, Uwe > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Dienstag, 10. Juni 2003 00:16 > To: Hahn, Uwe > Cc: [EMAIL PROTECTED] > Subject: RE: How to turn off logging in sapdb ? > > > > Hi Uwe, > > I tried just using "set log writer off"...until I discovered > the database > won't restart under Windows 2000, XP SP1 etc!!!!!!! Ouch! > > Can you confirm that the "set log auto overwrite on" will NOT > increase the > log size - ie will just keep writing over it? > > many thanks, > > David > > > > > "Hahn, Uwe" <[EMAIL PROTECTED]> on 06/06/2003 02:57:38 AM > > To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> > cc: [EMAIL PROTECTED] > Subject: RE: How to turn off logging in sapdb ? > > > Yes, you always have to define a log volume. > > If you used the command "set log writer off" the state is > stored in the > database. > So you don't need to execute this at every restart. > Please use additionally the command "set log auto overwrite on" > (util_execute in admin mode). > This is needed because switching of log writing does not > prevent savepoint > to write an entry into the log and if you want to run the > database in this > mode for a long time it can happen that > the log becomes full with switched off log writing which > would be amazing > for. > > But perhaps you only need to use the auto overwrite feature ?! > > Regards, > Uwe > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: Mittwoch, 4. Juni 2003 19:10 > > To: Hahn, Uwe > > Cc: [EMAIL PROTECTED] > > Subject: RE: How to turn off logging in sapdb ? > > > > > > > > We want to turn logging off permanently. > > > > Believe I have successfully done this with util_execute SET > > LOG WRITER OFF > > in my init script. > > > > Apart from backups etc. are there any other repercussions to > > doing this? > > We will move to transaction based stuff later, but for now > > don't need it. > > > > Also, apparently I ***have*** to create a log volume of > > atleast 2001 8K > > pages? > > > > Many thanks, > > > > David > > > > > > > > > > > > "Hahn, Uwe" <[EMAIL PROTECTED]>@listserv.sap.com on 15/05/2003 > > 02:34:38 AM > > > > Sent by: [EMAIL PROTECTED] > > > > > > To: "'Sourabh Ahuja'" <[EMAIL PROTECTED]>, > > [EMAIL PROTECTED] > > cc: > > Subject: RE: How to turn off logging in sapdb ? > > > > > > Please have a look into > http://www.sapdb.org/7.4/pdf/logsettings_eng.pdf < > http://www.sapdb.org/7.4/pdf/logsettings_eng.pdf> > If you have questions with this I will try to help you. > > kind regards > Uwe > > -----Original Message----- > From: Sourabh Ahuja [mailto:[EMAIL PROTECTED] > Sent: Mittwoch, 14. Mai 2003 22:40 > To: [EMAIL PROTECTED] > Subject: How to turn off logging in sapdb ? > > > Hi, > > I want to turn off logging in sapdb for testing purposes. Can > anybody tell me how to do that ? > > > Here is my param file:: > > param_rmfile > param_startsession > param_init OLTP > param_put LOG_MODE SINGLE > param_put CAT_CACHE_SUPPLY 3000 > param_put CACHE_SIZE 32768 > param_put MAXDATADEVSPACES 5 > param_checkall > param_commitsession > param_addvolume 1 DATA $HOME/$SID/DISKD0001 F 262144 > param_addvolume 1 LOG /export/$SID/DISKL001 F 65536 > quit > > > Any kind of help will be appreciated. > > Thanks, > > Sourabh. > > > > > > _____ > > Do you Yahoo!? > The New > <http://us.rd.yahoo.com/search/mailsig/*http://search.yahoo.com> > Yahoo! Search - Faster. Easier. Bingo. > > > (See attached file: C.htm) > > > > > > > > _______________________________________________ > sapdb.general mailing list > [EMAIL PROTECTED] > http://listserv.sap.com/mailman/listinfo/sapdb.general > _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
