Hello Frank, There was a new feature introduced with MaxDB 7.5.00.40 and 7.6.02.01 that allows, to specify an interval after which new log entries are startet to be backed up (even if the log segement size is not reached yet). Would this fulfill your customers requirements? If not, you could also use the DBM command 'info log' to check whether there are log pages to be backed up or not. This would be a way to prevent the nasty error messages in the log files.
Best regards, Tilo Heinrich Senior Developer MaxDB&liveCache SAP AG http://www.sap.com <http://www.sap.com/> Sitz der Gesellschaft/Registered Office: Walldorf, Germany Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), Shai Agassi, Léo Apotheker, Werner Brandt, Claus Heinrich, Gerhard Oswald, Peter Zencke Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: Hasso Plattner Registergericht/Commercial Register Mannheim No HRB 350269 Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. -----Original Message----- From: Frank Sent: Dienstag, 3. Juli 2007 16:15 To: maxdb@lists.mysql.com Subject: Re: using archive_stage und archive_stage_repeat in scripts Hello Tilo, thanks for your answer. We do use automatic log backup, but we want write a versionfile in a regular-time-cycle if log_pages are available. Maybe another way would be to reduce the LOG_SEGMENT_SIZE, but one goal of all is to keep the log/backup-stuff as simple as possible and usable for rollout. Yes the script can ignore error-messages, but the logfile don't look "nice": *** DBA Action ends: Timestamp: 20070703141500 State: Failure Returncode: 0002 Perhaps the customer want some kind of supervision, so it's easier to handle the logs. I think there is a new feature in 7.6 to do this easier. I use the script below. The idea with info+log I got in the forum. ------------------------------ not_saved=`$DBMCLI_PATH/dbmcli -d $SID -u $CNTRL_USR,$CNTRL_PWD info log \ | grep "Not Saved (KB)" \ | awk -F= '{print $2}'` if [ $not_saved == "0" ] then echo "no log_page" else echo "write versionfile" $DBMCLI_PATH/dbmcli -d $SID -u $CNTRL_USR,$CNTRL_PWD autolog_off $DBMCLI_PATH/dbmcli -d $SID -u $CNTRL_USR,$CNTRL_PWD -uUTL \ -c backup_start $LOG_MEDIUM LOG $DBMCLI_PATH/dbmcli -d $SID -u $CNTRL_USR,$CNTRL_PWD autolog_on $LOG_MEDIUM fi ------------------------------ Maybe someone has some (shell)-improvments. best regards Frank On Fri, 29 Jun 2007 19:33:25 +0200, [EMAIL PROTECTED] ("Heinrich, Tilo") wrote: >Hello Frank, > >This error message can not be avoided, but it can be ignored by your script. > >What is the rason for this non-automatic log backup? > >Best regards, >Tilo Heinrich >Senior Developer >MaxDB&liveCache >SAP AG >http://www.sap.com <http://www.sap.com/> > >Sitz der Gesellschaft/Registered Office: Walldorf, Germany >Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), Shai Agassi, >Léo Apotheker, Werner Brandt, Claus Heinrich, Gerhard Oswald, Peter Zencke >Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: Hasso >Plattner >Registergericht/Commercial Register Mannheim No HRB 350269 > >Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige >vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich >erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine >Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte >benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. > >This e-mail may contain trade secrets or privileged, undisclosed, or otherwise >confidential information. If you have received this e-mail in error, you are >hereby notified that any review, copying, or distribution of it is strictly >prohibited. Please inform us immediately and destroy the original transmittal. >Thank you for your cooperation. > > >-----Original Message----- >From: Frank >Sent: Freitag, 29. Juni 2007 18:26 >To: maxdb@lists.mysql.com >Subject: Re: using archive_stage und archive_stage_repeat in scripts > >Hello Tilo, > >I have another question regarding backup. > >if I do a logbackup in the following way, I get an error if no >log-pages available for backup. How can I avoid an Error-Message. > > >Skript: >-------- >dbmcli -d $SID -u control,control autolog_off >dbmcli -d $SID -u control,control -uUTL -c backup_start $LOG_MEDIUM >LOG >dbmcli -d $SID -u control,control autolog_on $LOG_MEDIUM > >Error: >-------- >ERR >-24988,ERR_SQL: sql error >-123,No more log to save > > >best regards Frank > > > > > >On Mon, 11 Jun 2007 13:44:41 +0200, [EMAIL PROTECTED] ("Heinrich, >Tilo") wrote: > >>Hello Frank, >> >>Of course you are right, the second archive_stage should have been an >>archive_stage_repeat. >> >>Best regards, >>Tilo Heinrich >>Senior Developer >>MaxDB&liveCache >>SAP AG >>http://www.sap.com <http://www.sap.com/> >> >>Sitz der Gesellschaft/Registered Office: Walldorf, Germany >>Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), Shai Agassi, >>Léo Apotheker, Werner Brandt, Claus Heinrich, Gerhard Oswald, Peter Zencke >>Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: >>Hasso Plattner >>Registergericht/Commercial Register Mannheim No HRB 350269 >> >>Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige >>vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich >>erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine >>Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte >>benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. >> >>This e-mail may contain trade secrets or privileged, undisclosed, or >>otherwise confidential information. If you have received this e-mail in >>error, you are hereby notified that any review, copying, or distribution of >>it is strictly prohibited. Please inform us immediately and destroy the >>original transmittal. Thank you for your cooperation. >> >> >>-----Original Message----- >>From: Frank >>Sent: Freitag, 8. Juni 2007 22:36 >>To: maxdb@lists.mysql.com >>Subject: Re: using archive_stage und archive_stage_repeat in scripts >> >>Hi Tilo, >> >>thanks for the support. Just for my information: Shouldn't be the >>second archive_stage-call a archive_stage_repeat. Maybe I missed >>something. >> >>Thanks in advance. >>Frank >> >> >>On Tue, 5 Jun 2007 13:48:53 +0200, [EMAIL PROTECTED] ("Heinrich, >>Tilo") wrote: >> >>>Hello Frank, >>> >>>You can A) write the archive_stage command and the archive_stage_repeat >>>command to an input file for the dbmcli call ("dbmcli ... <inputfile") or >>>use the inline input data facility of your shell: >>> >>>dbmcli -u control,control -d $SID -uUTL -c <<EOF >>>archive_stage $ARCHIVE_MEDIUM $LOG_MEDIUM NOVERIFY KEEP >>>archive_stage $ARCHIVE_MEDIUM2 $LOG_MEDIUM VERIFY >>>EOF >>> >>>Best regards, >>>Tilo Heinrich >>>Senior Developer >>>MaxDB&liveCache >>>SAP AG >>>http://www.sap.com <http://www.sap.com/> >>> >>>Sitz der Gesellschaft/Registered Office: Walldorf, Germany >>>Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), Shai Agassi, >>>Léo Apotheker, Werner Brandt, Claus Heinrich, Gerhard Oswald, Peter Zencke >>>Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: >>>Hasso Plattner >>>Registergericht/Commercial Register Mannheim No HRB 350269 >>> >>>Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige >>>vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich >>>erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine >>>Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte >>>benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen >>>Dank. >>> >>>This e-mail may contain trade secrets or privileged, undisclosed, or >>>otherwise confidential information. If you have received this e-mail in >>>error, you are hereby notified that any review, copying, or distribution of >>>it is strictly prohibited. Please inform us immediately and destroy the >>>original transmittal. Thank you for your cooperation. >>> >>>-----Original Message----- >>>From: Frank >>>Sent: Freitag, 1. Juni 2007 14:34 >>>To: maxdb@lists.mysql.com >>>Subject: using archive_stage und archive_stage_repeat in scripts >>> >>>Hallo, >>> >>>regarding maxdb-documentation I have to use archive_stage und >>>archive_stage_repeat in one utility-session. >>> >>> In addition to that we want to use environmentvariables in the >>>archivingscript. >>>Our script looks like: >>> >>>#/bin/sh >>>export SID=ALT >>>export LOG_MEDIUM=$SID'_LOG' >>>export ARCHIVE_MEDIUM=BACKUP_LOG_PIPE >>> >>>dbmcli -u control,control -d $SID -uUTL -c archive_stage >>>$ARCHIVE_MEDIUM $LOG_MEDIUM NOVERIFY KEEP >>> >>>How can I add the archive_stage_repeat-step in the script and make >>>shure both steps run in the same utility-session >>> >>>with Regards Frank >>> >>> >>> -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
