Hosting Provided By

RE: more AUTOLOG

From: Cappellano, John J <john.cappellano(at)tycoelectronics.com>
Date: Tue Jul 24 2007 - 13:14:11 EDT

I am running 7.6.00.25. My mistake. I'll keep it in mind for when I get their.

Thanks

-----Original Message-----

From: Heinrich, Tilo [mailto:tilo.heinrich@sap.com] Sent: Tuesday, July 24, 2007 11:48 AM
To: maxdb@lists.mysql.com
Subject: RE: more AUTOLOG

Hello John,

What version of MaxDB are you using? As stated below, you need MaxDB 7.5.00.40, 7.6.02.00 or newer versions of 7.5 and 7.6.

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), 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

Do you need help?

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: Cappellano, John J
Sent: Dienstag, 24. Juli 2007 17:34
To: Heinrich, Tilo; maxdb@lists.mysql.com Subject: RE: more AUTOLOG

Hi Tilo,
If I understand your reply the INTERVAL option can force logs to be created (cut) without the LOG_SEGMENT_SIZE being reached. This is what I am after. We want to try to push log activity out on a more frequent basis.

When I execute the command you specified: dbmcli -d ... -u ...,... -uUTL -c autolog_on <medium_name> INTERVAL 3600

I get:
-24946,ERR_TOOMANYPARAM: too many parameters

Any suggestions. I also tried it without the -uUTL -c syntax and get the same error returned.

Thanks

Do you need more help?

-----Original Message-----

From: Heinrich, Tilo
Sent: Tuesday, July 24, 2007 10:08 AM
To: maxdb@lists.mysql.com
Subject: RE: more AUTOLOG

Hello John,

I'm not sure what you understand by cutting a log backup. The INTERVAL option is in effect forcing a log backup, if there exist log entries, that were written to the log volume before the length of the INTERVAL but not backed up since. In other words, if your database has not created LOG_SEGMENT_SIZE many log entries for the length of the INTERVAL option after the last automatic log backup, the backup of the partial "log segment" is started at the end of the interval. No running log backup is cut.

In times with high activity on the log the automatic log backup creates log backups in the size of LOG_SEGMENT_SIZE as in previous versions. In times with low activity on the log the INTERVAL option ensures the backup of log entries after a certain amount of time.

Best regards,
Tilo Heinrich
Senior Developer
MaxDB&liveCache
SAP AG
http://www.sap.com <http://www.sap.com/>

Can we help you?

-----Original Message-----

From: Cappellano, John J
Sent: Dienstag, 24. Juli 2007 14:38
To: Heinrich, Tilo
Subject: RE: more AUTOLOG

Tilo,
Are you stating that every 3600 seconds a log backup will be cut and written to the backup medium location?

Thanks

-----Original Message-----

From: Heinrich, Tilo
Sent: Monday, July 23, 2007 10:58 AM
To: maxdb@lists.mysql.com
Subject: RE: more AUTOLOG

Hello Joerg,

If you use MaxDB 7.5.00.40, 7.6.02.00 or newer versions of 7.5 and 7.6 you can specify an interval while starting the automatic log backup, e.g.:

dbmcli -d ... -u ...,... -uUTL -c autolog_on <medium_name> INTERVAL 3600

This would ensure, that the backup of a log entry is started at least 3600 seconds after the log entry was written onto the log volumes. The interval option does not ensure log backups to fixed points in time but sets a time limit to the log entries lost, if the log volume is lost.

Can't find what you're looking for?

Best regards,
Tilo Heinrich
Senior Developer
MaxDB&liveCache
SAP AG
http://www.sap.com <http://www.sap.com/>

-----Original Message-----

Sent: Dienstag, 17. Juli 2007 14:18
To: maxdb@lists.mysql.com
Subject: more AUTOLOG

Hello,

how can i have AUTOLOG every hour, without AUTOLOG OFF and backup? Sorry but will not resize the LOG area. The LOG area will be a standard on our systems. :-(

Kind regard
Joerg

Don't know where to look next?

--

MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/maxdb?unsub=lists@pantek.com Received on Tue Jul 24 13:14:36 2007

This message: [ Message body ]
Next message: Frank: "Re: using archive_stage und archive_stage_repeat in scripts"
Previous message: Heinrich, Tilo: "RE: more AUTOLOG"
In reply to: Heinrich, Tilo: "RE: more AUTOLOG"

Contemporary messages sorted: [ By Date ] [ By Thread ] [ By Subject ] [ By Author ] [ By messages with attachments ]

This archive was generated by hypermail 2.1.8 : Thu Aug 09 2007 - 19:30:27 EDT