cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

MaxDB 7.9 - Add Volume Error

former_member229542
Active Participant

on ‎08-17-2018 12:27 AM

0 Kudos

Hi!

When adding a new volume via Database Studio, the following messages are displayed on the Database Error output.

I'm trying to add Volume #31 but for some reason, Im unable to do it.

Process is quite straightforward same as documented in MaxDB guide, just click on Volumes List and adding a new one.

Any comments on messages below, would be highly appreciated.


Thanks!

 20:36:41     IOMan         47:  Data volume name is /sapdb/DES/sapdata1/DISKD0001
                               2018-08-16 20:36:39 ERR Kernel     20004:  Bad page - page check algorithm is invalid,_FILE=Kernel_Page74+noPIC.cpp,_LINE=62
                               2018-08-16 20:36:20 ERR Kernel     20004:  Bad page - page check algorithm is invalid,_FILE=Kernel_Page74+noPIC.cpp,_LINE=62
                               2018-08-16 20:36:14 ERR Kernel     20004:  Bad page - page check algorithm is invalid,_FILE=Kernel_Page74+noPIC.cpp,_LINE=62
Thread     0x4339 Task     59  2018-08-16 20:36:41     AdminMsg       0:  5B75E05900EE 0000   ADD RETURNCODE  -914;ADD DATA VOLUME '/sapdb/DES/sapdata1/DISKD0031' PAGES 8388608 DEVICE 31
Thread     0x4332 Task      4  2018-08-16 20:40:41     AdminMsg       0:  5B75E14900F4 0000   ADD ADD DATA VOLUME '/usr/sap/trans/DISKD0031' PAGES 16384000 DEVICE 31
Thread     0x4332 Task      4  2018-08-16 20:41:41 ERR IOMan      20040:  Bad volume info page,_FILE=IOMan_Volume+noPIC.cpp,_LINE=257
                               2018-08-16 20:41:41 ERR IOMan          5:  Failed consistency check on read page,BLOCK_NO=0,VOLUME_ID=1,VOLUME_TYPE=Data_Volume,_FILE=IOMan_Volume+noPIC.cpp,_LINE=450

                                                                           DESCRIPTION:

                                                                           The post-read consistency check found an error on the page. The bad page was read from the 'Data_Volume'  volume with the ID '1' from position  '0'.

                                                                           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.

                                                                           
                               2018-08-16 20:41:41     IOMan         47:  Data volume name is /sapdb/DES/sapdata1/DISKD0001
                               2018-08-16 20:41:39 ERR Kernel     20004:  Bad page - page check algorithm is invalid,_FILE=Kernel_Page74+noPIC.cpp,_LINE=62
                               2018-08-16 20:41:34 ERR Kernel     20004:  Bad page - page check algorithm is invalid,_FILE=Kernel_Page74+noPIC.cpp,_LINE=62
                               2018-08-16 20:41:26 ERR Kernel     20004:  Bad page - page check algorithm is invalid,_FILE=Kernel_Page74+noPIC.cpp,_LINE=62
Thread     0x4332 Task      4  2018-08-16 20:41:41     AdminMsg       0:  5B75E18500F5 0000   ADD RETURNCODE  -914;ADD DATA VOLUME '/usr/sap/trans/DISKD0031' PAGES 16384000 DEVICE 31

Show replies
Show replies
Answer

Accepted Solutions (0)

Answers (3)

Answers (3)

former_member229542
Active Participant
‎08-18-2018 3:33 AM
0 Kudos

Also this is shown in KnlMsgArchive

<MSGL _NO="266177" _PROCESS="6373" _THREAD="0x1907" _TASK="758" _TIME="2018-08-18 02:22:37.000">
  <MSG _NO="1" _TYPE="Error" _ID="12" _COMP="RTEIO" _TEXT="Attach volume $VOLUME_NAME$ failed during open">
   <MSG_ARGS
     _FILE="RTEIO_VolumeInfo-k+noPIC.cpp"
     _LINE="1708"
     _TIME="2018-08-18 02:22:37.000"
     _MESSAGEVERSION="2"
     VOLUME_NAME="LOG_VOLUME_001"
    />
  </MSG>
  <MSG _NO="2" _TYPE="Error" _ID="1" _COMP="RTEIO" _TEXT="Open file $PATHNAME$ failed, $DESCRIPTION$ returned '$ERRORTEXT$' ($RETURNCODE$)">
   <MSG_ARGS
     _FILE="RTEIO_VolumeInfo-k+noPIC.cpp"
     _LINE="2346"
     _TIME="2018-08-18 02:22:37.000"
     _MESSAGEVERSION="2"
     PATHNAME="/sapdb/DES/saplog/DISKL001"
     RETURNCODE="2"
     ERRORTEXT="No such file or directory"
     DESCRIPTION="open(READWRITE,OPEN_EXISTING)"
    />
  </MSG>
 </MSGL>
<MSGL _NO="266178" _PROCESS="6373" _THREAD="0x1907" _TASK="758" _TIME="2018-08-18 02:22:37.000">
  <MSG _NO="1" _TYPE="Error" _ID="61" _COMP="Log" _TEXT="The logarea could not be opened">
   <MSG_ARGS
     _FILE="Log_Area+noPIC.cpp"
     _LINE="653"
     _TIME="2018-08-18 02:22:37.000"
     _MESSAGEVERSION="1"
    />
Show replies
Show replies
former_member229542
Active Participant
‎08-18-2018 3:32 AM
0 Kudos

Hi James.

I have tried adding another path but still fails, even if i select the same path where a DataVolume Exists, it cannot add it

Also ran a Structure Check and LogArea is not accesible with message "disk_not_accesible" when the disk is accesible since it was created with SWPM and has proper permissions.

As you can see, there are kernel dumps when starting the DB, causing to shutdown

Thanks in advance!

Thread    0x1271A Task     83  2018-08-17 02:04:36 ERR IOMan      20038:  Bad restart page,_FILE=IOMan_DataFileSystem+noPIC.cpp,_LINE=529
                               2018-08-17 02:04:36 ERR IOMan          5:  Failed consistency check on read page,BLOCK_NO=1,VOLUME_ID=1,VOLUME_TYPE=Data_Volume,_FILE=IOMan_Volume+noPIC.cpp,_LINE=450


                                                                           DESCRIPTION:


                                                                           The post-read consistency check found an error on the page. The bad page was read from the 'Data_Volume'  volume with the ID '1' from position  '1'.


                                                                           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.


                                                                           
                               2018-08-17 02:04:36     IOMan         47:  Data volume name is /sapdb/DES/sapdata1/DISKD0001
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:  ----> Emergency stack backtrace <----
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:  Using 'backtrace' for stack tracing
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:  (0):0x00000000015d720f 
T
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:  ----> Symbolic stack backtrace <----
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:    0: RTEDiag_CallStack::TraceStackSymbolic(RTEDiag_RegisterSet const*) + 0x42
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Symbol: _ZN17RTEDiag_CallStack18TraceStackSymbolicEPK19RTEDiag_RegisterSet
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           SFrame: IP: 0x00000000015d74d2 (0x00000000015d7490+0x42)
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Module: /sapdb/DES/db/pgm/kernel
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:       -----------------------------------------
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:    1: RTEKernel_CrashHandler::AbortHandler(RTEDiag_FaultDescriptor*, void*) + 0x1b9
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Symbol: _ZN22RTEKernel_CrashHandler12AbortHandlerEP23RTEDiag_FaultDescriptorPv
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           SFrame: IP: 0x00000000014158e9 (0x0000000001415730+0x1b9)
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Module: /sapdb/DES/db/pgm/kernel
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:       -----------------------------------------
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:    2: RTE_Crash(Msg_List const&) + 0x3f
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Symbol: _Z9RTE_CrashRK8Msg_List
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           SFrame: IP: 0x0000000001646bdf (0x0000000001646ba0+0x3f)
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Module: /sapdb/DES/db/pgm/kernel
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:       -----------------------------------------
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:    3: IOMan_DataFileSystem::ReadRestartPageWithBlock(RTETask_ITask&, Kernel_RestartPage&, IOMan_BlockAddress const&, IOMan_IOPriority const&) + 0x327
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Symbol: _ZN20IOMan_DataFileSystem24ReadRestartPageWithBlockER13RTETask_ITaskR18Kernel_RestartPageRK18IOMan_BlockAddressRK16IOMan_IOPriority
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           SFrame: IP: 0x0000000000c38547 (0x0000000000c38220+0x327)
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Module: /sapdb/DES/db/pgm/kernel
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:       -----------------------------------------
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:    4: IOMan_DataFileSystem::ReadRestartPage(RTETask_ITask&) + 0x28
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Symbol: _ZN20IOMan_DataFileSystem15ReadRestartPageER13RTETask_ITask
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           SFrame: IP: 0x0000000000c33468 (0x0000000000c33440+0x28)
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Module: /sapdb/DES/db/pgm/kernel
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:       -----------------------------------------
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:    5: IOMan_DataFileSystem::OpenAll(RTETask_ITask&, Msg_List&, bool) + 0x318
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Symbol: _ZN20IOMan_DataFileSystem7OpenAllER13RTETask_ITaskR8Msg_Listb
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           SFrame: IP: 0x0000000000c39fe8 (0x0000000000c39cd0+0x318)
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Module: /sapdb/DES/db/pgm/kernel
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:       -----------------------------------------
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:    6: IOMan_DataArea::AddDataVolume(RTETask_ITask&, tsp00_OldPascalString<256>&, unsigned int, SAPDB_Invalidatable<unsigned short, (unsigned short)65535>, Msg_List&) + 0xbd
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Symbol: _ZN14IOMan_DataArea13AddDataVolumeER13RTETask_ITaskR21tsp00_OldPascalStringILi256EEj19SAPDB_InvalidatableItLt65535EER8Msg_List
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           SFrame: IP: 0x0000000000c542bd (0x0000000000c54200+0xbd)
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Module: /sapdb/DES/db/pgm/kernel
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:       -----------------------------------------
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:    7: Kernel_Administration::AddDataVolume(Trans_Context&, tsp00_OldPascalString<256>&, int, short) + 0x1e5
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Symbol: _ZN21Kernel_Administration13AddDataVolumeER13Trans_ContextR21tsp00_OldPascalStringILi256EEis
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           SFrame: IP: 0x000000000132ad75 (0x000000000132ab90+0x1e5)
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Module: /sapdb/DES/db/pgm/kernel
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:       -----------------------------------------
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:    8: a37_call_semantic(SQLMan_Context&, tgg00_UtilCmdId const&) + 0xb52
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Symbol: _Z17a37_call_semanticR14SQLMan_ContextRK15tgg00_UtilCmdId
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           SFrame: IP: 0x000000000054e7d2 (0x000000000054dc80+0xb52)
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Module: /sapdb/DES/db/pgm/kernel
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:       -----------------------------------------
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:    9: ak35call_semantik(SQLMan_Context&, SharedSQL_PrepareHandle*) + 0x6ca
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Symbol: _Z17ak35call_semantikR14SQLMan_ContextP23SharedSQL_PrepareHandle
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           SFrame: IP: 0x000000000050fffa (0x000000000050f930+0x6ca)
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Module: /sapdb/DES/db/pgm/kernel
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:       -----------------------------------------
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:   10: a35_asql_statement2(SQLMan_Context&, SharedSQL_PrepareHandle*, bool) + 0x9c7
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Symbol: _Z19a35_asql_statement2R14SQLMan_ContextP23SharedSQL_PrepareHandleb
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           SFrame: IP: 0x00000000005119d7 (0x0000000000511010+0x9c7)
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Module: /sapdb/DES/db/pgm/kernel
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:       -----------------------------------------
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:   11: ak92not_only_execute(SQLMan_Context&, int&, short&, tak_parskey&, tsp1_part*&, tak_ddl_descriptor_Enum, bool, int, bool&, SharedSQL_PrepareHandle*&, SharedSQL_ExecuteHandle&, int&, int&, bool&) + 0x418
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Symbol: _Z20ak92not_only_executeR14SQLMan_ContextRiRsR11tak_parskeyRP9tsp1_part23tak_ddl_descriptor_EnumbiRbRP23SharedSQL_PrepareHandleR23SharedSQL_ExecuteHandleS1_S1_S9_
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           SFrame: IP: 0x000000000069b5c8 (0x000000000069b1b0+0x418)
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Module: /sapdb/DES/db/pgm/kernel
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:       -----------------------------------------
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:   12: a92_mode_analyzer(SQLMan_Context&, tak_ddl_descriptor_Enum, bool) + 0xde4
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Symbol: _Z17a92_mode_analyzerR14SQLMan_Context23tak_ddl_descriptor_Enumb
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           SFrame: IP: 0x000000000069d794 (0x000000000069c9b0+0xde4)
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Module: /sapdb/DES/db/pgm/kernel
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:       -----------------------------------------
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:   13: ak93one_command(SQLMan_Context&, int, int&, bool, bool&) + 0x76c
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Symbol: _Z15ak93one_commandR14SQLMan_ContextiRibRb
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           SFrame: IP: 0x000000000069fc0c (0x000000000069f4a0+0x76c)
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Module: /sapdb/DES/db/pgm/kernel
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:       -----------------------------------------
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:   14: a93_user_commands(SQLMan_Context&, bool&, bool&) + 0x629
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Symbol: _Z17a93_user_commandsR14SQLMan_ContextRbS1_
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           SFrame: IP: 0x00000000006a1d09 (0x00000000006a16e0+0x629)
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Module: /sapdb/DES/db/pgm/kernel
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:       -----------------------------------------
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:   15: SQLTask(SQLMan_Context&, Kernel_DatabaseContext*, RTETask_ITask&, bool&, bool) + 0x71
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Symbol: _Z7SQLTaskR14SQLMan_ContextP22Kernel_DatabaseContextR13RTETask_ITaskRbb
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           SFrame: IP: 0x0000000001349cb1 (0x0000000001349c40+0x71)
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Module: /sapdb/DES/db/pgm/kernel
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:       -----------------------------------------
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:   16: Kernel_Main(RTETask_ITask&) + 0x218
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Symbol: _Z11Kernel_MainR13RTETask_ITask
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           SFrame: IP: 0x000000000134a198 (0x0000000001349f80+0x218)
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Module: /sapdb/DES/db/pgm/kernel
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:       -----------------------------------------
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:   17: RTETask_Task::KernelTaskMain() + 0x120
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Symbol: _ZN12RTETask_Task14KernelTaskMainEv
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           SFrame: IP: 0x00000000013d0150 (0x00000000013d0030+0x120)
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Module: /sapdb/DES/db/pgm/kernel
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:       -----------------------------------------
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:   18: RTEExec_Coroutine::StartCoroutine(RTEExec_Coroutine*, unsigned int) + 0x42c
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Symbol: _ZN17RTEExec_Coroutine14StartCoroutineEPS_j
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           SFrame: IP: 0x00000000015c9e0c (0x00000000015c99e0+0x42c)
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Module: /sapdb/DES/db/pgm/kernel
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:       -----------------------------------------
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:   19: __start_context + 0x0
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           SFrame: IP: 0x00007f8f503e9d40 (0x00007f8f503e9d40+0x0)
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR DIAG           0:           Module: /usr/lib64/libc-2.17.so
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR Messages       7:  Begin of dump of registered messages,_FILE=Msg_Registry+noPIC.cpp,_LINE=507
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR IOMan      20038:  Bad restart page,_FILE=IOMan_DataFileSystem+noPIC.cpp,_LINE=529
                               2018-08-17 02:04:36 ERR IOMan          5:  Failed consistency check on read page,BLOCK_NO=1,VOLUME_ID=1,VOLUME_TYPE=Data_Volume,_FILE=IOMan_Volume+noPIC.cpp,_LINE=450


                                                                           DESCRIPTION:


                                                                           The post-read consistency check found an error on the page. The bad page was read from the 'Data_Volume'  volume with the ID '1' from position  '1'.


                                                                           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.


                                                                           
                               2018-08-17 02:04:36     IOMan         47:  Data volume name is /sapdb/DES/sapdata1/DISKD0001
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR Messages       8:  End of the message list registry dump,_FILE=Msg_Registry+noPIC.cpp,_LINE=544
Thread    0x1271A Task      -  2018-08-17 02:04:36 ERR AK CACHE   51105:  DUMPING SESSION CATCACHE: 1
Thread    0x1271A Task      -  2018-08-17 02:04:37 ERR DIAG           0:  analysing LVCMem_Allocator_001
Thread    0x1271A Task      -  2018-08-17 02:04:37 ERR DIAG           0:  
Thread    0x1271A Task      -  2018-08-17 02:04:37 ERR DIAG           0:  no problems detected in LVCMem_Allocator_001
Thread    0x1271A Task      -  2018-08-17 02:04:37 ERR DIAG           0:  analysing LVCMem_Allocator_002
Thread    0x1271A Task      -  2018-08-17 02:04:37 ERR DIAG           0:  
Thread    0x1271A Task      -  2018-08-17 02:04:37 ERR DIAG           0:  no problems detected in LVCMem_Allocator_002
Thread    0x1271A Task      -  2018-08-17 02:04:37 ERR DIAG           0:  analysing LVCMem_Allocator_003
Thread    0x1271A Task      -  2018-08-17 02:04:37 ERR DIAG           0:  
Thread    0x1271A Task      -  2018-08-17 02:04:37 ERR DIAG           0:  no problems detected in LVCMem_Allocator_003
Thread    0x1271A Task      -  2018-08-17 02:04:37 ERR DIAG           0:  analysing LVCMem_Allocator_004
Thread    0x1271A Task      -  2018-08-17 02:04:37 ERR DIAG           0:  
Thread    0x1271A Task      -  2018-08-17 02:04:37 ERR DIAG           0:  no problems detected in LVCMem_Allocator_004
Thread    0x126F5 Task      -  2018-08-17 02:04:53 ERR RTEKernel    101:  Kernel exited with core and exit status 0x86,_FILE=RTEKernel_Termination+noPIC.cpp,_LINE=677
Thread    0x126F5 Task      -  2018-08-17 02:04:53 ERR RTEKernel     98:  Kernel exited due to signal 6 (SIGABRT),_FILE=RTEKernel_Termination+noPIC.cpp,_LINE=734
Thread    0x126F5 Task      -  2018-08-17 02:04:53     MsgOutput     28:  ___ Stopping GMT 2018-08-17 02:04:53           7.9.07   Build 010-123-243-190

So not sure if there is an issue at Filesystem Level in Linux

Show replies
Show replies
JamesZ
Advisor
Advisor
‎08-18-2018 3:44 AM
0 Kudos

It seems the existing data volume has inconsistency, then please attach diagpack.tgz after executing:

dbmcli -d <dbsid> -u superdba,<password> diag_pack

former_member229542
Active Participant
‎08-18-2018 4:37 AM
0 Kudos

Hi james, i have uploaded diagpack.tgz file to this location

http://s000.tinyupload.com/?file_id=00662454365875888407

Thanks again!

former_member229542
Active Participant
‎08-18-2018 3:41 PM
0 Kudos

Hi James.

Now, even when Try to put db in Admin mode, there is a kernel dump related to Log area.

It cannot create/attach LOG VOLUME, even when filesystem has all permissions.

So, really no clue if error is at OS level

Thread    0x19B77 Task      -  2018-08-18 14:08:09 ERR RTEKernel    101:  Kernel exited with core and exit status 0x86,_FILE=RTEKernel_Termination+noPIC.cpp,_LINE=677
Thread    0x19B77 Task      -  2018-08-18 14:08:09 ERR RTEKernel     98:  Kernel exited due to signal 6 (SIGABRT),_FILE=RTEKernel_Termination+noPIC.cpp,_LINE=734
Thread    0x19B77 Task      -  2018-08-18 14:08:09     MsgOutput     28:  ___ Stopping GMT 2018-08-18 14:08:09           7.9.07   Build 010-123-243-190
Thread          - Task      -  2018-08-18 14:19:48     MsgOutput     27:  --- Starting GMT 2018-08-18 14:19:48           7.9.07   Build 010-123-243-190
Thread    0x1A28D Task    258  2018-08-18 14:20:35 ERR RTEIO         12:  Attach volume LOG_VOLUME_001 failed during open,_FILE=RTEIO_VolumeInfo-k+noPIC.cpp,_LINE=1708
                               2018-08-18 14:20:35 ERR RTEIO          1:  Open file /sapdb/DES/saplog/DISKL001 failed, open(READWRITE,OPEN_EXISTING) returned 'No such file or directory' (2),_FILE=RTEIO_VolumeInfo-k+noPIC.cpp,_LINE=2346
Thread    0x1A28D Task    258  2018-08-18 14:20:35 ERR SYSERROR   51080:  -9209 redo_log_write_error
Thread    0x1A28D Task    258  2018-08-18 14:20:35 ERR Log           61:  The logarea could not be opened,_FILE=Log_Area+noPIC.cpp,_LINE=653
JamesZ
Advisor
Advisor
‎08-21-2018 2:14 AM
0 Kudos

Sorry, I am not able to download, because my laptop blocks the website, please change diagpack.tgz to diagpack.txt, then attach to this discussion, then I will donwload and change the name back

former_member229542
Active Participant
‎08-21-2018 2:39 AM
0 Kudos

Hi James.

I was able to overcome the issue.

Let me explain it how I do it.

First, I ran SWPM to define DataVolume and LogVolume

When SWPM asks me to manual recover database, i need to first initialize Database so LogVolume is created at OS Level.

After I notice LogVolume is created, I could start Recovery Process and finished without errors.

So, the lesson learnt is that I needed to make sure LogVolume is at OS Level, otherwise when Recovery is stated, it wouldn't be created.

Thanks for your help

JamesZ
Advisor
Advisor
‎08-17-2018 3:21 AM
0 Kudos

Please do database structure check from database studio see wehther there is any error. If there is no error, would you please specify another file path name for the to-be-added data volume?

Show replies
Show replies
Ask a Question