Normally users want to backup the log for recovery purpose. This is supported by "autosave log" which must be enabled. This keeps the log volume(device) free for working.
If for any reason the log and revovery ability does not interest, you can set the database permanently to the log mode DEMO or you can use another variant with "dbmcli -d ... -u ... util_execute set log mode demo" After this you can reenable the "normal" log mode with a complete data backup in admin(cold) mode. regards Uwe > -----Original Message----- > From: Mohamed Koker [mailto:Mohamed.Koker@;mentatsolutions.com] > Sent: Montag, 4. November 2002 10:24 > To: [EMAIL PROTECTED] > Subject: Log_mode > > > I have a process which needs to be run each night and > essentially consists > of deleting a number of tables and then repopulating them > based on an number > of XML files. > > I found that unless I set the log_mode to demo, I end up > filling up my log > device. I sometimes get the same problem if I execute a query > with a lot of > outer joins. > > I would like to be able to change the log mode to demo just > before I execute > this process and then revert to single or dual after this > process executes. > Can I accomplish this via SQL or do I need to use dbmcli and > if so what is > the relevant command I need to use ? > > Is there any other way of preventing the log device from > being filled ? > > Cheers > > -Mohamed > > > > > _______________________________________________ > 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
