Hella John,
you're right that the error -8033 occurs only if autosave log
is enabled.
You can check the structure of the logbackups by using the command
recover_check <medium> <type> <number>
Additionally you can check for several logbackups, whether the
values of "First LOG Page" and "Last LOG Page" - that you get as
a part of the result from recover_check - are ascending without any
gap between the logbackups.
Kind regards, Martin
> -----Original Message-----
> From: Cappellano, John J [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 17, 2007 3:44 PM
> To: Brunzema, Martin
> Subject: RE: Error: (-8033) on Log Backups
>
> Martin,
> If I turn off the auto log function and take log backup manually I do
> not see the 8033 error. How can I be certain the log backups
> are okay if
> I keep auto log on? I would like to keep auto log set to on
> for obvious
> reasons.
>
> Please Advise
>
> -----Original Message-----
> From: Brunzema, Martin [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 16, 2007 4:57 AM
> To: [email protected]
> Cc: Cappellano, John J
> Subject: RE: Error: (-8033) on Log Backups
>
>
> From: Cappellano, John J
> [mailto:[EMAIL PROTECTED]
> Sent: Monday, January 15, 2007 9:03 PM
> To: [email protected]
> Subject: Error: (-8033) on Log Backups
>
>
> Hello All,
> I am getting the error -8033 every time a log backup (auto log
> on) executes. I looked up the error and it says:
>
>
> -8033: Incomplete log segment Locate the document in the library
> structure
> <http://dev.mysql.com/doc/maxdb/en/bb/549e3dcf9a4c64e10000000a
> 114084/fra
> meset.htm>
>
>
> Explanation:
>
> You tried to save the log area. However, there are fewer log
> entries to be saved than defined in the general database parameter
> <http://dev.mysql.com/doc/maxdb/en/ef/eb3d408ae01e24e10000000a
> 1550b0/con
> tent.htm> LOG_SEGMENT_SIZE.
>
> User Action:
>
> No action required
>
>
>
> This has just recently started to happen. It does not appear to
> be an issue but I am not sure what is really happening. Any guidance
> would be appreciated.
>
> Hello John,
>
> this seems to be an error in writing the protocol. If you
> look into the
> backuphistory and find
> directly above of the line which contains the error another
> line with en
> errorcode 0 (say ok)
> and these two lines have the same data - then this error is fixed with
> newer builds:
> 7.5.00.39
> 7.6.01.09
> 7.6.02.00
>
> In this case the lines containing the errorcode -8033 does
> not mean that
> there occured an error
> during autosave log.
>
> Kind re
>
>
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
