Internal errorcode, Error code 9050 "disk_not_accessible"

[Former Member]

Hello ,

after a problem with the data voloume expansion, the MaxDB 7.8 would not start.
The following error message apperas:
"cat /sapdb/SM4/data/wrk/SM4/dbm.prt"

2012-11-29 17:28:20	456 ERR	-24580 DBMSrv   ERR_COMMAND_FAILED: Command 'db_online' has ended and failed with return code -24988.
	456 ERR	-24988 DBMSrv   ERR_SQL: SQL error
	456 ERR	-24778 DBMSrv   -902,I/O error
	456 ERR	-24778 DBMSrv   3,Database state: OFFLINE
	456 ERR	-24778 DBMSrv   Internal errorcode, Error code 9050 "disk_not_accessible"
	456 ERR	-24778 DBMSrv   20017,RestartFilesystem failed with 'I/O error'
	456 ERR	-24778 DBMSrv   20043,data volume configuration corrupted: Successor of volume 21 should be 22

Could you please help me

Best regrads
A. Wenning

[former_member229109]

Hello A. Wenning,

according posted information the successor of volume 21 should be 22.

Please update the message withh additional information:

-> post output of "param_getvolsall" dbm command.

-> Did you try to add datavolume 22 or did you have a problem with the data voloume expansion by datavolume 22 ?

What was the RC in both cases?

-> Was datavolume 22 created by database kernel at OS level?

-> Are you SAP customer?

Regards, Natalia Khlopina

[Former Member]

Hello Natalia,

param_getvolsall show the folling values:

/sapdb/programs/bin/dbmcli on SM4>param_getvolsall

OK

UseMirroredLog                   NO

MaxLogVolumes                    3

MaxDataVolumes                   36

LogVolumeName001                 512000     F  /saplog1/DISKL001  1

LogVolumeName002                 512000     F  /saplog1/DISKL002  1

DataVolumeName0001               1011200    F  /sapdata1/DISKD0001

DataVolumeName0002               1011200    F  /sapdata1/DISKD0002

DataVolumeName0003               1011200    F  /sapdata1/DISKD0003

DataVolumeName0004               1011200    F  /sapdata1/DISKD0004

DataVolumeName0005               1011200    F  /sapdata1/DISKD0005

DataVolumeName0006               1011200    F  /sapdata1/DISKD0006

DataVolumeName0007               1011200    F  /sapdata1/DISKD0007

DataVolumeName0008               1011200    F  /sapdata1/DISKD0008

DataVolumeName0009               1011200    F  /sapdata1/DISKD0009

DataVolumeName0010               1011200    F  /sapdata2/DISKD0010

DataVolumeName0011               1011200    F  /sapdata2/DISKD0011

DataVolumeName0012               1011200    F  /sapdata2/DISKD0012

DataVolumeName0013               1011200    F  /sapdata2/DISKD0013

DataVolumeName0014               1011200    F  /sapdata2/DISKD0014

DataVolumeName0015               1011200    F  /sapdata2/DISKD0015

DataVolumeName0016               1011200    F  /sapdata2/DISKD0016

DataVolumeName0017               1011200    F  /sapdata2/DISKD0017

DataVolumeName0018               1011200    F  /sapdata2/DISKD0018

DataVolumeName0019               1011200    F  /sapdata2/DISKD0019

DataVolumeName0020               1011200    F  /sapdata3/DISKD0020

DataVolumeName0021               1011200    F  /sapdata3/DISKD0021

#########################################################################

When I try to add a new vloume by command line, the follwing error message apperas:

/sapdb/programs/bin/dbmcli on SM4>param_addvolume 22 DATA /sapdata3/DISKD0022 F

8283750400

    ERR

    -24973,ERR_XPCHECK: param check failure/request

    DataVolumeSize0022      Constraint

    8283750400

####

Log file output:

"cat /sapdb/SM4/data/wrk/SM4/dbm.prt"

    2012-12-05 09:23:12       9217 INF          1 DBMSrvCo A DBM Server client connection was established at 2012-12-05 09:22:07 (client process has process ID 9215 on computer wdf-alm14.de.realtech.net).

    2012-12-05 09:23:12       9217 INF        283 DBMSrv   Command 'param_addvolume 22 DATA /sapdata3/DISKD0022 F 8283750400' is being executed.

    2012-12-05 09:23:12       9217 ERR     -24580 DBMSrv   ERR_COMMAND_FAILED: Command 'param_addvolume' has ended and failed with return code -24973.

                              9217 ERR     -24973 DBMSrv   ERR_XPCHECK: param check failure/request

                              9217 ERR     -24778 DBMSrv   DataVolumeSize0022       Constraint

                              9217 ERR     -24778 DBMSrv   8283750400

                              9217 ERR     -24778 DBMSrv  

######################

By adding an new vloume with the MaxDB Studio:

2012-12-05 09:26:33       9228 INF        283 DBMSrv   Command 'db_addvolume DATA "/sapdata3/DISKD0022" F 1011200' is being executed.

2012-12-05 09:26:33       9228 INF          1 DBMKnl   Sending an administrative statement to the database

                          9228 INF          8 DBMKnl   Statement:  ADD DATA VOLUME '/sapdata3/DISKD0022' PAGES 1011200 DEVICE 22

2012-12-05 09:26:34       9228 ERR          3 DBMKnl   Received the result of an administrative statement from the database

                          9228 ERR          9 DBMKnl   Statement:  ADD DATA VOLUME '/sapdata3/DISKD0022' PAGES 1011200 DEVICE 22

                          9228 ERR         10 DBMKnl   Returncode: -914

                          9228 ERR          5 DBMKnl   Errortext:  New volume not accessible

2012-12-05 09:26:34       9228 ERR     -24580 DBMSrv   ERR_COMMAND_FAILED: Command 'db_addvolume' has ended and failed with return code -24988.

                          9228 ERR     -24988 DBMSrv   ERR_SQL: SQL error

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

                          9228 ERR     -24778 DBMSrv   20043,data volume configuration corrupted: Successor of volume 21 should be 22

The data volume file was not being created

wdf-alm14:/sapdata3 # ls -al

total 16195032

drwxr-xr-x  2 sdb  sdba       4096 Nov 28 17:19 .

drwxr-xr-x 30 root root       4096 Nov 28 14:39 ..

-rw-rw----  1 sdb  sdba 8283750400 Nov 28 14:03 DISKD0020

-rw-rw----  1 sdb  sdba 8283750400 Nov 28 14:10 DISKD0021

Do you have any suggestions ?                         

Best regards

Alex

[yashwanthkumar_kethineed]

Hello Alex,

wdf-alm14:/sapdata3 # ls -al

total 16195032

drwxr-xr-x  2 sdb  sdba       4096 Nov 28 17:19 .

drwxr-xr-x 30 root root       4096 Nov 28 14:39 ..

-rw-rw----  1 sdb  sdba 8283750400 Nov 28 14:03 DISKD0020

-rw-rw----  1 sdb  sdba 8283750400 Nov 28 14:10 DISKD0021

The size of each volume in your case is "8283750400" (bytes) - when converted into pages (8283750400 / 1024) / 8 = 1011200

You need to specify the <size> for this dbm command in <pages>

You must use this DBM command param_addvolume only when creating a database instance, when changing the log mode of the database instance from SINGLE to DUAL, or in consultation with Support.

Refer to the MaxDB documentation for more details:

http://maxdb.sap.com/doc/7_7/9e/bf06a0e4ae49a4b16882d4083ab119/content.htm

/sapdb/programs/bin/dbmcli on SM4>param_addvolume 22 DATA /sapdata3/DISKD0022 F 8283750400

You are trying to add a configuration to datavolume 22 of size (61.7 TeraByte) - Which is why the error below -

ERR 

    -24973,ERR_XPCHECK: param check failure/request

    DataVolumeSize0022      Constraint

    8283750400

Regards,Yashwanth

[former_member229109]

Hello Alex,

If the datavolume 22 was not added by the database kernel < you didn’t see the successful output of Command 'db_addvolume in dbm.prt and KnlMsgArchive for 22 datavolume >, you should not run the dbm command:

param_addvolume 22 DATA /sapdata3/DISKD0022 F 1011200

This dbm command will add the configuration for datavolume 22 to param file, but according the posted information you have not in /sapdata3 the /sapdata3/DISKD0022 file created by database kernel.

1. Are you SAP customer?
2. Please post the post the entries from the param history file /sapdb/SM4/data/config/SM4.pah since the auto_extend failed time.

          Please post output of the command “ls –l /sapdb/SM4/data/config”

  3. As workaround please run following commands:

cp /sapdb/SM4/data/config /sapdb/SM4/data/config.old

dbmcli -d SM4 -u control,<pwd>

db_offline

auto_extend OFF

param_restore 1

db_online

And update the thread with results.

Regards, Natalia Khlopina