Hello Martin,

thanks alot for this advice. I restored some backups on the 11th after having messed sth. up (Full, inc, inc, log). Hardware is ok, no crash or sth., harddisks are okay too.
I've just set Logmode to autooverwrite for having the db back online.
i'll give it a try with clearing the logs. just one question :
if something goes badly wrong, i still can recover any full databackup after 
having the log cleared?


Thanks alot,

Flo

Florian Schmitz

______________________
acardo technologies AG
K�nigswall 18a
44137 Dortmund

fon: +49 (0) 2 31 / 58 44 97 - 0
fax: +49 (0) 2 31 / 58 44 97 - 21
mail: [EMAIL PROTECTED]
web: www.acardo.com


Brunzema, Martin schrieb:
Hi Florian,

the logpage at the offset 1442 on your logvolume is defect. Because your system is able to restart into online
mode, this page is not necessary for the restart.
When you initiate the logbackup, then the logpages are
checked for consistency. Because this page is not consistent,
the logbackup terminates the kernel. I can see that the logpage
is defect because there are values shown in the kerneltrace
 which are inconsistent and should never occur in that
combination.
First of all please check the logfiles of your system for
hardware errors. The page had been written (if the header is correct)
on Jun 11th at 8:25. Also I'd like to know if there had been
any administration taken place at this time.


To resolve the error, it is neccessary to reinitialize the logvolume.
You can do this with the following steps:
1) ensure that a db_online will work
2) enter admin mode
3) complete databackup for security reasons
4) issue the command "util_execute clear log" which will reinitialize
   the logvolume (and delete everything on it!!)
5) start the database
6) create a complete databackup in order to start the backup-history again
7) if necessary switch on autosave-log

kind regards, Martin



This page has been written
-----Original Message-----
From: Florian Schmitz [mailto:[EMAIL PROTECTED] Sent: Monday, June 13, 2005 12:33 PM
To: Brunzema, Martin
Subject: Re: SAPDBErr Assertion of state Log_SaveIterator::CheckPageBuffer 
pagebuffer is not inconsistent failed!

Hi Martin,

see the .prt.
The error happens explicitly when writing logbackups.
I restored a full backup, the db went online, then i tried a log-backup ...

Any Idea?

Flo

Florian Schmitz

______________________
acardo technologies AG
K�nigswall 18a
44137 Dortmund

fon: +49 (0) 2 31 / 58 44 97 - 0
fax: +49 (0) 2 31 / 58 44 97 - 21
mail: [EMAIL PROTECTED]
web: www.acardo.com


Brunzema, Martin schrieb:

Hi Florian,

which release and build do you use?
Could you please generate and send the readable kerneltrace either by issuing the dbmcli command
        trace_prot abkx
or clicking the corresonding actions in the dbmgui (check -> database
trace).

There should be some information about the error in the generated
file, which has the filename <your databasename>.prt and is located
in the rundirectory.
kind regards, Martin

-----Original Message-----
From: Florian Schmitz [mailto:[EMAIL PROTECTED] Sent: Monday, June 13, 2005 11:42 AM
To: [email protected]
Subject: SAPDBErr Assertion of state Log_SaveIterator::CheckPageBuffer
pagebuffer is not inconsistent failed!

Hello List,

somebody already came accross this one?
After doing an full cold-backup and restarting the DB, knldiag.err shows
the following :

2005-06-13 11:21:51  3555 ERR     0 SAPDBErr Assertion of state
Log_SaveIterator::CheckPageBuffer pagebuffer is not inconsistent failed!
2005-06-13 11:21:51  3555 ERR 11196 DBCRASH  vabort:Emergency Shutdown,
Log_SaveIterator.cpp: 215
2005-06-13 11:21:51  3555 ERR 11599 BTRACE   ----> Emergency Stack Back
Trace <----
..........
2005-06-13 11:21:51  3555 ERR 11599 BTRACE   ----> Symbolic Stack Back
Trace <----
2005-06-13 11:21:51  3555 ERR 11599 BTRACE      0: 0x0878b2ca
eo670_CTraceStack +0x001e
2005-06-13 11:21:51  3555 ERR 11599 BTRACE
/usr/sapdb/depend/pgm/kernel
2005-06-13 11:21:51  3555 ERR 11599 BTRACE         Frameinfo
[0xb542b7ac] (0x0,0x0,0x1,0x878b2b8)
2005-06-13 11:21:51  3555 ERR 11599 BTRACE      1: 0x087a97bd vabort
+0x0039
2005-06-13 11:21:51  3555 ERR 11599 BTRACE
/usr/sapdb/depend/pgm/kernel
2005-06-13 11:21:51  3555 ERR 11599 BTRACE         Frameinfo
[0xb542b7dc] (0x8af21dc,0x8938160,0x8938182,0xb542b804)
2005-06-13 11:21:51  3555 ERR 11599 BTRACE      2: 0x087153c3
RTE_Crash__FRC20SAPDBErr_MessageList +0x010f
2005-06-13 11:21:51  3555 ERR 11599 BTRACE
/usr/sapdb/depend/pgm/kernel
2005-06-13 11:21:51  3555 ERR 11599 BTRACE         Frameinfo
[0xb542b80c] (0x40250001,0xd7,0xb542b84c,0x8715346)
2005-06-13 11:21:51  3555 ERR 11599 BTRACE      3: 0x0861c4a5
CheckPageBuffer__16Log_SaveIterator +0x0199
2005-06-13 11:21:51  3555 ERR 11599 BTRACE
/usr/sapdb/depend/pgm/kernel
2005-06-13 11:21:51  3555 ERR 11599 BTRACE         Frameinfo
[0xb542b84c] (0xb542b890,0x0,0x0,0x861c31a)
2005-06-13 11:21:51 3555 ERR 11599 BTRACE 4: 0x0861c2cd GetNextLogPages__16Log_SaveIteratoriPt11tsp00_Array3Z9tkb3_pagei1000i100
0RUi +0x0791
2005-06-13 11:21:51  3555 ERR 11599 BTRACE
/usr/sapdb/depend/pgm/kernel
2005-06-13 11:21:51  3555 ERR 11599 BTRACE         Frameinfo
[0xb542b8bc] (0x8b5a19c,0x8,0xb542ba0c,0x861c2c1)
2005-06-13 11:21:51  3555 ERR 11599 BTRACE      5: 0x083a454e
kb391_ReadNextLogpages +0x0042
2005-06-13 11:21:51  3555 ERR 11599 BTRACE
/usr/sapdb/depend/pgm/kernel
2005-06-13 11:21:51  3555 ERR 11599 BTRACE         Frameinfo
[0xb542ba0c] (0x8b5a19c,0x4c,0x2a86a000,0xb542ba38)
2005-06-13 11:21:51  3555 ERR 11599 BTRACE      6: 0x0839eb03
kb39drt_devsp_read_task +0x0367
2005-06-13 11:21:51  3555 ERR 11599 BTRACE
/usr/sapdb/depend/pgm/kernel
2005-06-13 11:21:51  3555 ERR 11599 BTRACE         Frameinfo
[0xb542ba3c] (0xb542bde0,0x2a86a000,0xb897dbca,0x839eae5)






--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to