Hello Tilo,
below a part of dbm.ebl
The period from start Pipe2file till kill pipe2file seems always about
60 sec.
best Regards
Frank
---------------------------------------------------------------------------------------------------
Constructed pipe2file call 'pipe2file -d file2pipe -f
/sapdb/ALI/saparch/LCLOG.719 -p /sapdb/ALI/saparch/BACKINT_LOG_PIPE
-nowait'.
Starting pipe2file for stage file '/sapdb/ALI/saparch/LCLOG.719'.
Starting pipe2file process 'pipe2file -d file2pipe -f
/sapdb/ALI/saparch/LCLOG.719 -p /sapdb/ALI/saparch/BACKINT_LOG_PIPE
-nowait >>/tmp/temp1187627401-0 2>>/tmp/temp1187627401-1'.
Process was started successfully.
Pipe2file has been started successfully.
Starting Backint for MaxDB.
Starting Backint for MaxDB process '/sapmnt/AAI/exe/backint -u
ALI -f backup -t file -p /sapdb/ALI/sapbackup/backint/initALI.utl -i
/sapdb/ALI/sapbackup/backint/backint.inp -c
>>/sapdb/ALI/sapbackup/backint/backint.out
2>>/sapdb/ALI/sapbackup/backint/backint.err'.
Process was started successfully.
Backint for MaxDB has been started successfully.
Waiting for end of the backup operation.
2007-08-20 18:30:01 The backup tool is running.
2007-08-20 18:30:01 Pipe2file is running.
2007-08-20 18:30:02 The backup tool process has finished work
with return code 2.
2007-08-20 18:30:06 Pipe2file is running.
2007-08-20 18:30:16 Pipe2file is running.
2007-08-20 18:30:31 Pipe2file is running.
2007-08-20 18:30:51 Pipe2file is running.
Killing not reacting pipe2file process.
Pipe2file killed successfully.
2007-08-20 18:31:03 The pipe2file process has finished work
with return code -1.
The backup operation has ended.
------------------------------------------------------------------------------------------------------
On Mon, 20 Aug 2007 17:13:54 +0200, [EMAIL PROTECTED] ("Heinrich,
Tilo") wrote:
>Hello Frank,
>
>I do not remember pipe2file having any timeout. What do you see exactly in
>dbm.ebl?
>
>Best regards,
>Tilo
>
>Tilo Heinrich
>Senior Developer
>MaxDB&liveCache
>SAP AG
>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 [mailto:[EMAIL PROTECTED]
>Sent: Freitag, 17. August 2007 18:18
>To: maxdb@lists.mysql.com
>Subject: Re: using archive_stage und archive_stage_repeat in scripts
>
>Hello Tilo,
>
>As I see in dbm.ebl or *.ssa it seems that the pipe2file-cmd timed
>out. This happens only one or two times a day likely because highload
>of the backup-Server.
>
>Is there any way to avoid this situation or change the timeout-value
>for the pipe2file-cmd
>
>Best Regards Uwe
>
>
>On Fri, 27 Jul 2007 18:00:31 +0200, [EMAIL PROTECTED] ("Heinrich,
>Tilo") wrote:
>
>>Hello Frank,
>>
>>One option would be to put the archive_stage* commands into an additional
>>file and use the '-i <input_file>' option of dbmcli. In this case dbmcli
>>would not execute the archive_stage_repeat, if the archive_stage had already
>>failed (at least, this is stated by
>>http://maxdb.sap.com/currentdoc/84/5b0282467f11d4aa1100a0c9430730/frameset.htm
>>
>><http://maxdb.sap.com/currentdoc/84/5b0282467f11d4aa1100a0c9430730/frameset.htm>
>> ).
>>
>>Best regards,
>>Tilo
>>
>>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), Léo Apotheker
>>(stellvertretender Sprecher/Deputy CEO), 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, 27. Juli 2007 14:12
>>To: maxdb@lists.mysql.com
>>Subject: Re: using archive_stage und archive_stage_repeat in scripts
>>
>>Helle Tilo,
>>
>>sorry that I didn't explain the error-situation.
>>
>>if the backup-infrastructure (tape_changer,robots, Mediaserver etc)
>>has to work on a high load the responsetime of the external backup
>>program is higher then the TIMEOUT...-Parameter in bsi.env
>>So the first archive_step fails
>>Now the second archive_step can run ok and we have only 1 copy of the
>>logfile.
>>
>>I increased the TIMEOUT...-Parameter in bsi.env to 300 sec. Now we
>>have nearly no errors.
>>
>>The last error seems not covered from the timeout-Parameter because
>>" The pipe2file process has finished work with return
>>code -1." after 1 min 03 sec
>>
>>I will send you the dbm.ebl.
>>
>>Best Regards
>>Frank
>>
>>
>>
>>On Wed, 25 Jul 2007 14:51:08 +0200, [EMAIL PROTECTED] ("Heinrich,
>>Tilo") wrote:
>>
>>>Hello Frank,
>>>
>>>Does log file dbm.ebl contain any information about such an error situation,
>>>if so can you please send the log file dbm.ebl to the mailing list or to me?
>>>
>>>Best regards,
>>>Tilo
>>>
>>>Tilo Heinrich
>>>Senior Developer
>>>MaxDB&liveCache
>>>SAP AG
>>>http://www.sap.com <http://www.sap.com> <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, 24. Juli 2007 19:17
>>>To: maxdb@lists.mysql.com
>>>Subject: Re: using archive_stage und archive_stage_repeat in scripts
>>>
>>>Hello Tilo,
>>>
>>>I use the following skript for archiving (thanks for your support)
>>>
>>>dbmcli -u control,control -d $SID -uUTL -c <<EOF
>>>(step-1) archive_stage $ARCHIVE_MEDIUM $LOG_MEDIUM NOVERIFY KEEP
>>>(step-2) archive_stage_repeat $ARCHIVE_MEDIUM2 $LOG_MEDIUM VERIFY
>>>EOF
>>>
>>>If step_1 fails and step_2 succeed I get only 1 backup and afterwards
>>>the log wil be deleted.
>>>
>>>Is there any possibility to avoid this situation?
>>>
>>>best regards Frank
>>
>>
>>
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
