Hello Martin, thanks for this information! "info log" that's what I need.
Will the new timetriggered logbackups take in account if there are no new log entries written? Kind regards, Stephan On 1/5/07, Brunzema, Martin <[EMAIL PROTECTED]> wrote:
Hello Stephan, the dbmcli-command "info log" returns the size of the unsaved log in kilobytes in the row "Not Saved (KB)". If this value is greater than 0 there is log to be saved. Also there will be support for a timetriggered logbackup which starts a logbackup periodically. But this feature isn't yet supported by the dbmcli in build 7.6.01. It will be completely available with 7.6.02.01. Kind regards, Martin > -----Original Message----- > From: Stephan Baehr [mailto:[EMAIL PROTECTED] > Sent: Friday, January 05, 2007 11:20 AM > To: maxdb@lists.mysql.com > Subject: -123, No more log to save > > Dear all, > > we are using SAP Livecache with MaxDB 7.6.01 and I would like to run a > Logbackup every 60 minutes. > > If there are no new entries in the log the backup ends with > an error "-123, > No more log to save". > > Is there any possibility to check before the backup if there > are enough new > entries in the log? > > Thanks in advance! > > > > Kind regards, > > Stephan Bähr >
