Skip to Content
0
Jun 29 at 05:59 AM

MaxDB could not start after system failure

128 Views

Hello All.

After system filure we get the error during startup of MaxDB:

2021-06-16 15:14:20 RTEIO 8: Volume M_LOG_VOLUME_002 on /sapdb/CS3/saplog/DISKL_M_002 was attached

2021-06-16 15:14:24 ERR IOMan 20038: Bad converter page,_FILE=IOMan_CommonDataFileSystem+noPIC.cpp,_LINE=1366

2021-06-16 15:14:24 ERR IOMan 5: Failed consistency check on read page,BLOCK_NO=845260,VOLUME_ID=140,VOLUME_TYPE=Data_Volume,_FILE=IOMan_Volume+noPIC.cpp,_LINE=450

2021-06-16 15:14:24 IOMan 47: Data volume name is /sapdb/CS3_3/sapdata/DISKD0140

2021-06-16 15:14:23 ERR Kernel 20004: Bad page - page check algorithm is invalid,_FILE=Kernel_Page74+noPIC.cpp,_LINE=62

2021-06-16 15:14:22 ERR Kernel 20004: Bad page - page check algorithm is invalid,_FILE=Kernel_Page74+noPIC.cpp,_LINE=62

2021-06-16 15:14:21 ERR Kernel 20004: Bad page - page check algorithm is invalid,_FILE=Kernel_Page74+noPIC.cpp,_LINE=62

2021-06-16 15:14:26 RunTime 3: State changed from ADMIN to ABORT

2021-06-16 15:14:26 RTEKernel 60: Kernel aborts

Is it posible to recover DB without restoring of backup, even if we will lose of some data?

>Kernel version: Kernel 7.9.09 Build 009-123-262-191

>Runtime version: U64/LIX86 7.9.09 Build 009-123-262-191

>OS: Linux 2.6.32.59-0.7-default #1 SMP 2012-07-13 15:50:56 +0200

BR,

Evgeny.