maxdb won't start, bad converter page

[markus_nospers2]

Hello,

during startup of a maxdb, I get the following error message.

Is there any way to recover the database without restoring from backup? Or do we have to do a complete restore?

Thanky

Markus

Thread      - Task      -  2011-07-20 10:33:02     MsgOutput     27:  --- Starting GMT 2011-07-20 08:33:02           7.7.07   Build 019-123-235-079
Thread  0x9E8 Task    119  2011-07-20 10:33:05     AdminMsg       0:  4E2692C10004 0000   RST RESTART
Thread  0x9E8 Task    119  2011-07-20 10:33:10 ERR DBCRASH    18196:  vabort:Emergency Shutdown, IOMan_DataFileSystem.cpp: 2611
Thread  0x9E8 Task    119  2011-07-20 10:33:10 ERR IOMan      20032:  Bad converter page,_FILE=IOMan_DataFileSystem.cpp,_LINE=2611
                           2011-07-20 10:33:10 ERR IOMan          5:  Failed consistency check on read page,BLOCK_NO=1778176,VOLUME_ID=5,VOLUME_TYPE=data,_FILE=IOMan_Volume.cpp,_LINE=418
                                                                      DESCRIPTION:
                                                                      The post-read consistency check found an error on the page. The bad page was read from the 'data'  volume with the ID '5' from position  '1778176'.
                                                                      As it may be necessary for development support to do an in-depth analysis of the page, the defective data page has been stored in the database run directory.
                           2011-07-20 10:33:08 ERR Kernel     20004:  Bad page - page check algorithm is invalid,_FILE=Kernel_Page74.cpp,_LINE=62
                           2011-07-20 10:33:06 ERR Kernel     20004:  Bad page - page check algorithm is invalid,_FILE=Kernel_Page74.cpp,_LINE=62
                           2011-07-20 10:33:05 ERR Kernel     20004:  Bad page - page check algorithm is invalid,_FILE=Kernel_Page74.cpp,_LINE=62

[lbreddemann · Accepted solution]

Well, the error message says it all:

There is a corruption on a page in which one of the most important management structures for MaxDB is stored - the converter.

This cannot be repaired, it cannot be avoided, by-passed or overruled.

You're going to have to restore and recover your database to get back to the latest state.

regards,

Lars

[Former Member · Accepted solution]

Dear Markus,

Can you please share the exact scenario how the page got corrupted in the DB. Will help to increase our knowledge.

Means When you taken DB startup before that DB was properly or unproperly shutdown.

Regards,

Sahil

[lbreddemann · Accepted solution]

Sahil,

this is not something you could actually make.

The checksum on the page did not match to its contents. Usually this is due to hardware/system failures.

E.g. some bits switched on the way from the data cache to the disk or on the way vice versa.

If you only have one corrupt page and only a checksum error, then there's no way to figure out a pattern from that.

So usually - if you don't have any other evidence - it won't be possible to determine the root cause of this corruption.

This is exactly the reason why we recommend regular backups, consistency checks and recovery drills so much.

regards,

Lars

[markus_nospers2]

@Lars: Thank you. This wasn't exactly what I hoped to hear, but I already suspected it.

@Sahil: the DB got corrupted because of a complete system crash, so no wonder at all

bye

Markus