Skip to Content

MaxDB is not starting anymore - Error code 9050 "disk_not_accessible"

Hi,

we have the problem to start our MaxDB anymore. We get the following error message:

af4lm139:sm2adm 93> dbmcli -d SM2 -u control,tsyst001 db_warm

ERR

-24988,ERR_SQL: SQL error

-902,I/O error

3,Database state: OFFLINE

Internal errorcode, Error code 9050 "disk_not_accessible"

20017,RestartFilesystem failed with 'I/O error'

Content of the knldiag:

Thread - Task - 2012-01-19 14:33:31 MsgOutput 27: --- Starting GMT 2012-01-19 13:33:31 7.8.02 Build 026-121-243-456

Thread 0x61C Task 120 2012-01-19 14:34:11 AdminMsg 0: 4F181BD30004 0000 RST RESTART

Thread 0x61C Task 120 2012-01-19 14:34:11 ERR RTEIO 12: Attach volume DATA_VOLUME_0028 failed during open,_FILE=RTEIO_VolumeInfo-k+noPIC.cpp,_LINE=1766

2012-01-19 14:34:11 ERR RTEIO 1: Open file /sapdb/SM2/sapdata1/DISKD0028 failed, open(READWRITE,OPEN_EXISTING) returned 'No such file or directory' (2),_FILE=RTEIO_VolumeInfo-k+noPIC.cpp,_LINE=2404

Thread 0x61C Task 120 2012-01-19 14:34:11 ERR Admin 3: Database state: OFFLINE,_FILE=Kernel_Administration+noPIC.cpp,_LINE=815

2012-01-19 14:34:11 KernelComm 6: Internal errorcode, Error code 9050 "disk_not_accessible"

2012-01-19 14:34:11 ERR Admin 20017: RestartFilesystem failed with 'I/O error',_FILE=Kernel_Administration+noPIC.cpp,_LINE=435

Thread 0x5FC Task - 2012-01-19 14:34:11 ERR Messages 7: Begin of dump of registered messages,_FILE=Msg_Registry+noPIC.cpp,_LINE=507

Thread 0x5FC Task - 2012-01-19 14:34:11 KernelComm 6: Internal errorcode, Error code 9050 "disk_not_accessible"

Thread 0x5FC Task - 2012-01-19 14:34:11 ERR Admin 3: Database state: OFFLINE,_FILE=Kernel_Administration+noPIC.cpp,_LINE=815

2012-01-19 14:34:11 KernelComm 6: Internal errorcode, Error code 9050 "disk_not_accessible"

2012-01-19 14:34:11 ERR Admin 20017: RestartFilesystem failed with 'I/O error',_FILE=Kernel_Administration+noPIC.cpp,_LINE=435

Thread 0x5FC Task - 2012-01-19 14:34:11 ERR Messages 8: End of the message list registry dump,_FILE=Msg_Registry+noPIC.cpp,_LINE=544

Thread 0x5F5 Task - 2012-01-19 14:34:12 ERR RTEKernel 102: Kernel exited without core and exit status 0x200,_FILE=RTEKernel_Termination+noPIC.cpp,_LINE=683

Thread 0x5F5 Task - 2012-01-19 14:34:12 ERR RTEKernel 106: Kernel exited with exit code 0x2,_FILE=RTEKernel_Termination+noPIC.cpp,_LINE=761

Thread 0x5F5 Task - 2012-01-19 14:34:12 MsgOutput 28: ___ Stopping GMT 2012-01-19 13:34:12 7.8.02 Build 026-121-243-456

We tried to add a volume in offline mode of the database.

Has someone an idea how to solve this issue?

Thanks in advance for your help!

Kind regards,

Joern

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • Jan 19, 2012 at 02:32 PM

    Hi Joern,

    Looks like some serious problem with your system. Data volume seems to be corrupted or has some serious problem.

    Do you have a full backup of your system ?

    You can refer the following document for the recovery procedure

    MAXDB library at http://maxdb.sap.com/doc/7_7/default.htm -> Database Administration

    • -> Restoring Databases*

    Also share the output of following command

    dbmcli -d SM2 -u control,tsyst001 param_getvolsall

    Regards,

    Deepak Kori

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 19, 2012 at 02:38 PM

    Hi Deepak,

    the output is as follow:

    af4lm139:sm2adm 94> dbmcli -d SM2 -u control,tsyst001 param_getvolsall

    OK

    UseMirroredLog YES

    MaxLogVolumes 3

    MaxDataVolumes 38

    LogVolumeName001 819200 F /sapdb/SM2/saplog/DISKL001 1

    MirroredLogVolumeName001 F /sapdb/SM2/m_saplog/M_DISKL001

    LogVolumeName002 12800 F /sapdb/SM2/saplog/DISKL002 1

    MirroredLogVolumeName002 F /sapdb/SM2/m_saplog/M_DISKL002

    DataVolumeName0001 1024000 F /sapdb/SM2/sapdata1/DISKD0001

    DataVolumeName0002 1024000 F /sapdb/SM2/sapdata1/DISKD0002

    DataVolumeName0003 1024000 F /sapdb/SM2/sapdata1/DISKD0003

    DataVolumeName0004 1024000 F /sapdb/SM2/sapdata1/DISKD0004

    DataVolumeName0005 1024000 F /sapdb/SM2/sapdata1/DISKD0005

    DataVolumeName0006 1024000 F /sapdb/SM2/sapdata1/DISKD0006

    DataVolumeName0007 1024000 F /sapdb/SM2/sapdata1/DISKD0007

    DataVolumeName0008 1024000 F /sapdb/SM2/sapdata1/DISKD0008

    DataVolumeName0009 1024000 F /sapdb/SM2/sapdata1/DISKD0009

    DataVolumeName0010 1024000 F /sapdb/SM2/sapdata1/DISKD0010

    DataVolumeName0011 1024000 F /sapdb/SM2/sapdata1/DISKD0011

    DataVolumeName0012 1024000 F /sapdb/SM2/sapdata1/DISKD0012

    DataVolumeName0013 1024000 F /sapdb/SM2/sapdata1/DISKD0013

    DataVolumeName0014 1024000 F /sapdb/SM2/sapdata1/DISKD0014

    DataVolumeName0015 1024000 F /sapdb/SM2/sapdata1/DISKD0015

    DataVolumeName0016 1024000 F /sapdb/SM2/sapdata1/DISKD0016

    DataVolumeName0017 1024000 F /sapdb/SM2/sapdata1/DISKD0017

    DataVolumeName0018 1024000 F /sapdb/SM2/sapdata1/DISKD0018

    DataVolumeName0019 1024000 F /sapdb/SM2/sapdata1/DISKD0019

    DataVolumeName0020 1024000 F /sapdb/SM2/sapdata1/DISKD0020

    DataVolumeName0021 1024000 F /sapdb/SM2/sapdata1/DISKD0021

    DataVolumeName0022 1024000 F /sapdb/SM2/sapdata1/DISKD0022

    DataVolumeName0023 1024000 F /sapdb/SM2/sapdata1/DISKD0023

    DataVolumeName0024 1024000 F /sapdb/SM2/sapdata1/DISKD0024

    DataVolumeName0025 1024000 F /sapdb/SM2/sapdata1/DISKD0025

    DataVolumeName0026 1024000 F /sapdb/SM2/sapdata1/DISKD0026

    DataVolumeName0027 512000 F /sapdb/SM2/sapdata1/DISKD0027

    DataVolumeName0028 1024000 F /sapdb/SM2/sapdata1/DISKD0028

    BUT the last created files DISK0028 was not successfully created. We tried to add this file in offline mode of the database. On OS level is file not visible:

    af4lm139:sm2adm 97> cd ../../../sapdata1/

    af4lm139:sm2adm 98> ll

    total 217514544

    -rw-rw---- 1 sdb sdba 8388608000 2012-01-18 10:35 DISKD0001

    -rw-rw---- 1 sdb sdba 8388608000 2012-01-18 09:21 DISKD0002

    -rw-rw---- 1 sdb sdba 8388608000 2012-01-18 00:40 DISKD0003

    -rw-rw---- 1 sdb sdba 8388608000 2012-01-18 00:40 DISKD0004

    .....

    -rw-rw---- 1 sdb sdba 8388608000 2012-01-18 00:43 DISKD0026

    -rw-rw---- 1 sdb sdba 4194304000 2012-01-18 00:57 DISKD0027

    af4lm139:sm2adm 99>

    Kind regards,

    Joern

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Joern,

      You can make a copy of DISK0027 as DISK0028 on your system, Post that start your MaxDB database.

      Let us know the results.

      In case your database comes up, please do a complete recovery from your lastest backup.

      Regards,

      Deepak Kori

  • Jan 20, 2012 at 07:46 AM

    He Deepak,

    the copy operation was not successful, I got the following error:

    hread 0x1E5E Task 120 2012-01-20 08:25:18 ERR IOMan 20036: Volume id of a data volume in database configuration (28) does not match volume id in iomanager info page (26) ,_FILE=IOMan_Volume+noPIC.cpp,_LINE=991

    Thread 0x1E5E Task 120 2012-01-20 08:25:18 ERR Admin 3: Database state: OFFLINE,_FILE=Kernel_Administration+noPIC.cpp,_LINE=815

    2012-01-20 08:25:18 KernelComm 6: Internal errorcode, Error code 9050 "disk_not_accessible"

    2012-01-20 08:25:18 ERR Admin 20017: RestartFilesystem failed with 'I/O error',_FILE=Kernel_Administration+noPIC.cpp,_LINE=435

    Thread 0x1E12 Task - 2012-01-20 08:25:18 ERR Messages 7: Begin of dump of registered messages,_FILE=Msg_Registry+noPIC.cpp,_LINE=507

    Thread 0x1E12 Task - 2012-01-20 08:25:18 KernelComm 6: Internal errorcode, Error code 9050 "disk_not_accessible"

    Thread 0x1E12 Task - 2012-01-20 08:25:18 ERR Admin 3: Database state: OFFLINE,_FILE=Kernel_Administration+noPIC.cpp,_LINE=815

    2012-01-20 08:25:18 KernelComm 6: Internal errorcode, Error code 9050 "disk_not_accessible"

    2012-01-20 08:25:18 ERR Admin 20017: RestartFilesystem failed with 'I/O error',_FILE=Kernel_Administration+noPIC.cpp,_LINE=435

    Thread 0x1E12 Task - 2012-01-20 08:25:18 ERR Messages 8: End of the message list registry dump,_FILE=Msg_Registry+noPIC.cpp,_LINE=544

    Thread 0x1DE9 Task - 2012-01-20 08:25:19 ERR RTEKernel 102: Kernel exited without core and exit status 0x200,_FILE=RTEKernel_Termination+noPIC.cpp,_LINE=683

    Thread 0x1DE9 Task - 2012-01-20 08:25:19 ERR RTEKernel 106: Kernel exited with exit code 0x2,_FILE=RTEKernel_Termination+noPIC.cpp,_LINE=761

    Thread 0x1DE9 Task - 2012-01-20 08:25:19 MsgOutput 28: ___ Stopping GMT 2012-01-20 07:25:19 7.8.02 Build 026-121-243-456

    Do you have another idea to fix the problem?

    Thanks in advance,

    Joern

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Joern,

      In the file dbm.prt (and in dbm.utl in 7.6 if necessary), check whether the system was able to successfully execute db_addvolume for the volume 28 reported above.

      For example, if db_addvolume was completed successfully, the following messages exist:

      2009-03-31 09:12:04 Command 'db_addvolume Data 28' is being executed.

      2009-03-31 10:10:48 Command 'db_addvolume' has ended with return code 0.

      If the action is not reported as completed with return code 0 in dbm.prt (or dbm.utl) (for example, because the dbmserver terminated), use the knldiag or KnlMsg files to check whether the operation could be completed.

      Incase your MaxDB version is 7.6 use the following command to delete the entries

      dbmcli -d <SID> -u <dbmusr>,<pwd> param_directdel DATA_VOLUME_NAME_<number>

      dbmcli -d <SID> -u <dbmusr>,<pwd> param_directdel DATA_VOLUME_TYPE_<number>

      dbmcli -d <SID> -u <dbmusr>,<pwd> param_directdel DATA_VOLUME_SIZE_<number>

      Ensure that you use exactly the same values for <number> as those saved in dbm.prt or dbm.utl

      After this first check the database in OFFLINE mode and then restart it in ONLINE mode.

      Hope this helps.

      Regards,

      Deepak Kori

  • Jan 20, 2012 at 12:59 PM

    He Deepak,

    our version is: 7.8.02.26

    and log entries in the dbm.prt look not so good:

    2012-01-19 14:08:34 18432 INF 283 DBMSrv Command 'db_addvolume DATA /sapdb/SM2/sapdata1/DISKD0028 F 1011200' is being executed.

    2012-01-19 14:08:35 18432 INF 1 DBMKnl Sending an administrative statement to the database

    18432 INF 8 DBMKnl Statement: ADD DATA VOLUME '/sapdb/SM2/sapdata1/DISKD0028' PAGES 1011200 DEVICE 29

    2012-01-19 14:08:36 18432 ERR 3 DBMKnl Received the result of an administrative statement from the database

    18432 ERR 9 DBMKnl Statement: ADD DATA VOLUME '/sapdb/SM2/sapdata1/DISKD0028' PAGES 1011200 DEVICE 29

    18432 ERR 10 DBMKnl Returncode: -914

    18432 ERR 5 DBMKnl Errortext: New volume not accessible

    2012-01-19 14:08:36 18432 ERR -24580 DBMSrv ERR_COMMAND_FAILED: Command 'db_addvolume' has ended and failed with return code -24988.

    18432 ERR -24988 DBMSrv ERR_SQL: SQL error

    18432 ERR -24778 DBMSrv -914,New volume not accessible

    Should I run the mentioned delete commands anyway or should I do something else?

    Kind regards,

    Joern

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Joern,

      Since you are on MaxDB 7.8 use the below command

      dbmcli -d <SID> -u <dbmusr>,<pwd> param_directdel DataVolumeName_0028

      dbmcli -d <SID> -u <dbmusr>,<pwd> param_directdel DataVolumeType_0028

      dbmcli -d <SID> -u <dbmusr>,<pwd> param_directdel DataVolumeSize_0028

      There is not other option to get your database up and running.

      Regards,

      Deepak Kori

  • Jan 23, 2012 at 08:21 AM

    Hi Depaak,

    the command didn't work:

    af4lm139:sm2adm 51> dbmcli -d SM2 -u control,<pwd> param_directdel DataVolumeName_0028

    ERR

    -24979,ERR_XPNOTFOUND: parameter not found

    As you can see the version is 7.8:

    af4lm139:sm2adm 52> dbmcli -d SM2 -u control,<pwd> version

    OK

    version,os,dbroot,logon,code,swap

    "7.8.02","UNIX","/sapdb/SM2/db",True,ASCII,2

    Could you help me again?

    Kind regards,

    Joern

    Add comment
    10|10000 characters needed characters exceeded

    • Easy. You should have started with a query:

      dbmcli -d SID -U c param_directgetall | findstr "DataVolume"

      (for UNIX replace findstr with grep Syntax)

      Then you are half the way done.

      Just go ahead and delete the three entries relevant to the problematic Volume

      dbmcli -d SID -U c param_directdel DataVolumeName0028

      the same for size entry and type entry

      Use the parameter name from your first query

      All should be fine after.