Mailing List
Home
Forum Home
MySQL General - General MySQL discussion
MaxDB - Everything about MaxDB, formerly known as SAP DB
MySQL++ - Programming with the C++ API to MySQL
ODBC - ODBC with the MySQL Connector/ODBC driver
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
Java Help - Mostly related to the MySQL Connector/J driver
Perl - Perl support for MySQL with DBI and DBD::mysql
GUI - MySQL GUI Tools
Announcement
Subjects
• mysql openssl Question
• mysql:it 's a db not a dbms how it 's possible?!
• Does the binary log enabling affect the MySQL performances?
• Strange behavior, Table Level Permission
• FULLTEXT query format question
• Preventing Duplicate Entries
• Comparing and writing out BLOBS
• Executing MySQL Commands From Within C Program
• Can 't access mysql after kernel upgrade
• Mysql 4 0 Oracle Stored Procedure Trigger Conversion
• Downgrade Mysql from 4 to 3 23
• MySQL Cluster Software
• mysql test 4 1 fails with the gis test
• ERROR 2002: Can 't connect to local MySQL server through socket
• Getting Identity after INSERT
• Update one field with more fields from another table
• ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
• mysql have same function mthod as Oracle decode()
 
-123, No more log to save

-123, No more log to save

2007-01-05       - By Stephan Baehr

 Back
Reply:     1     2     3     4  

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 <martin.brunzema@(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:baehrs@(protected)]
> > Sent: Friday, January 05, 2007 11:20 AM
> > To: maxdb@(protected)
> > 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
> >
>