Max DB Startup Failed

[former_member673162]

Hi Gurus,

When i tried to start up the data base i'm getting an Error -24988 SQL error [db_online -f]; -902, I/O error.

Windows Server 2003 R2 X64 Bit;

Max Database Manager 7.5.00.18

The following is the data base error log file.. Please let me know if there are any other logfiles and specific error messages that I need to check, to resolve the MaxDB startup issue error. Any help would really appreciated.

-

---

Date Time TID(hex) Typ MsgID Label Message-Text

-

---

2009-06-04 19:00:44 0xD98 ERR 6 KernelCo + Internal errorcode, Errorcode 9050 "disk_not_accessible"

2009-06-04 19:00:44 0xD98 ERR 20017 Admin + RestartFilesystem failed with 'I/O error'

2009-06-04 19:00:44 0xD44 ERR 7 Messages Begin of dump of registered messages

2009-06-04 19:00:44 0xD44 ERR 10 Messages abort dump of registered messages

2009-06-04 19:00:44 0xD44 ERR 8 Messages End of the message list registry dump

2009-06-04 19:00:46 ___ Stopping GMT 2009-06-04 23:00:46 7.6.00 Build 035-123-139-084

2009-06-04 19:02:27 --- Starting GMT 2009-06-04 23:02:27 7.6.00 Build 035-123-139-084

2009-06-04 19:02:34 0xC10 ERR 18159 VOLUMEIO Could not open volume 'C:\sapdb\SRD\saplog\DISKL001', rc = 2

2009-06-04 19:02:34 0xFA8 ERR 20027 IOMan Attach error on log volume 1: could not open volume

2009-06-04 19:02:34 0xFA8 ERR 3 Admin Database state: OFFLINE

2009-06-04 19:02:34 0xFA8 ERR 6 KernelCo + Internal errorcode, Errorcode 9050 "disk_not_accessible"

2009-06-04 19:02:34 0xFA8 ERR 20017 Admin + RestartFilesystem failed with 'I/O error'

2009-06-04 19:02:34 0xF48 ERR 7 Messages Begin of dump of registered messages

2009-06-04 19:02:34 0xF48 ERR 10 Messages abort dump of registered messages

2009-06-04 19:02:34 0xF48 ERR 8 Messages End of the message list registry dump

2009-06-04 19:02:35 ___ Stopping GMT 2009-06-04 23:02:35 7.6.00 Build 035-123-139-084

2009-06-04 19:03:22 --- Starting GMT 2009-06-04 23:03:22 7.6.00 Build 035-123-139-084

2009-06-04 19:03:27 0x838 ERR 18159 VOLUMEIO Could not open volume 'C:\sapdb\SRD\saplog\DISKL001', rc = 2

2009-06-04 19:03:27 0x810 ERR 20027 IOMan Attach error on log volume 1: could not open volume

2009-06-04 19:03:27 0x810 ERR 3 Admin Database state: OFFLINE

2009-06-04 19:03:27 0x810 ERR 6 KernelCo + Internal errorcode, Errorcode 9050 "disk_not_accessible"

2009-06-04 19:03:27 0x810 ERR 20017 Admin + RestartFilesystem failed with 'I/O error'

2009-06-04 19:03:27 0x644 ERR 7 Messages Begin of dump of registered messages

2009-06-04 19:03:27 0x644 ERR 10 Messages abort dump of registered messages

2009-06-04 19:03:27 0x644 ERR 8 Messages End of the message list registry dump

2009-06-04 19:03:29 ___ Stopping GMT 2009-06-04 23:03:29 7.6.00 Build 035-123-139-084

2009-06-04 19:03:41 --- Starting GMT 2009-06-04 23:03:41 7.6.00 Build 035-123-139-084

2009-06-04 19:03:49 0xCC0 ERR 18159 VOLUMEIO Could not open volume 'C:\sapdb\SRD\saplog\DISKL001', rc = 2

2009-06-04 19:03:49 0xAEC ERR 20027 IOMan Attach error on log volume 1: could not open volume

2009-06-04 19:03:49 0xAEC ERR 3 Admin Database state: OFFLINE

2009-06-04 19:03:49 0xAEC ERR 6 KernelCo + Internal errorcode, Errorcode 9050 "disk_not_accessible"

2009-06-04 19:03:49 0xAEC ERR 20017 Admin + RestartFilesystem failed with 'I/O error'

2009-06-04 19:03:49 0x82C ERR 7 Messages Begin of dump of registered messages

2009-06-04 19:03:49 0x82C ERR 10 Messages abort dump of registered messages

2009-06-04 19:03:49 0x82C ERR 8 Messages End of the message list registry dump

2009-06-04 19:03:50 ___ Stopping GMT 2009-06-04 23:03:50 7.6.00 Build 035-123-139-084

2009-06-14 21:08:11 --- Starting GMT 2009-06-15 01:08:11 7.6.00 Build 035-123-139-084

2009-06-14 21:08:17 0x9C4 ERR 18159 VOLUMEIO Could not open volume 'C:\sapdb\SRD\saplog\DISKL001', rc = 2

2009-06-14 21:08:17 0xBBC ERR 20027 IOMan Attach error on log volume 1: could not open volume

2009-06-14 21:08:17 0xBBC ERR 3 Admin Database state: OFFLINE

2009-06-14 21:08:17 0xBBC ERR 6 KernelCo + Internal errorcode, Errorcode 9050 "disk_not_accessible"

2009-06-14 21:08:17 0xBBC ERR 20017 Admin + RestartFilesystem failed with 'I/O error'

2009-06-14 21:08:17 0x950 ERR 7 Messages Begin of dump of registered messages

2009-06-14 21:08:17 0x950 ERR 10 Messages abort dump of registered messages

2009-06-14 21:08:17 0x950 ERR 8 Messages End of the message list registry dump

2009-06-14 21:08:18 ___ Stopping GMT 2009-06-15 01:08:18 7.6.00 Build 035-123-139-084

2009-06-14 21:08:26 --- Starting GMT 2009-06-15 01:08:26 7.6.00 Build 035-123-139-084

2009-06-14 21:08:33 0xAE4 ERR 18159 VOLUMEIO Could not open volume 'C:\sapdb\SRD\saplog\DISKL001', rc = 2

2009-06-14 21:08:33 0xADC ERR 20027 IOMan Attach error on log volume 1: could not open volume

2009-06-14 21:08:33 0xADC ERR 3 Admin Database state: OFFLINE

2009-06-14 21:08:33 0xADC ERR 6 KernelCo + Internal errorcode, Errorcode 9050 "disk_not_accessible"

2009-06-14 21:08:33 0xADC ERR 20017 Admin + RestartFilesystem failed with 'I/O error'

2009-06-14 21:08:33 0xAD0 ERR 7 Messages Begin of dump of registered messages

2009-06-14 21:08:33 0xAD0 ERR 10 Messages abort dump of registered messages

2009-06-14 21:08:33 0xAD0 ERR 8 Messages End of the message list registry dump

2009-06-14 21:08:35 ___ Stopping GMT 2009-06-15 01:08:35 7.6.00 Build 035-123-139-084

2009-06-14 21:08:52 --- Starting GMT 2009-06-15 01:08:52 7.6.00 Build 035-123-139-084

2009-06-14 21:08:58 0x934 ERR 18159 VOLUMEIO Could not open volume 'C:\sapdb\SRD\saplog\DISKL001', rc = 2

2009-06-14 21:08:58 0x59C ERR 20027 IOMan Attach error on log volume 1: could not open volume

2009-06-14 21:08:58 0x59C ERR 3 Admin Database state: OFFLINE

2009-06-14 21:08:58 0x59C ERR 6 KernelCo + Internal errorcode, Errorcode 9050 "disk_not_accessible"

2009-06-14 21:08:58 0x59C ERR 20017 Admin + RestartFilesystem failed with 'I/O error'

2009-06-14 21:08:58 0x870 ERR 7 Messages Begin of dump of registered messages

2009-06-14 21:08:58 0x870 ERR 10 Messages abort dump of registered messages

2009-06-14 21:08:58 0x870 ERR 8 Messages End of the message list registry dump

2009-06-14 21:09:00 ___ Stopping GMT 2009-06-15 01:09:00 7.6.00 Build 035-123-139-084

2009-06-14 21:11:30 --- Starting GMT 2009-06-15 01:11:30 7.6.00 Build 035-123-139-084

2009-06-14 21:11:36 0x958 ERR 18159 VOLUMEIO Could not open volume 'C:\sapdb\SRD\saplog\DISKL001', rc = 2

2009-06-14 21:11:36 0x360 ERR 20027 IOMan Attach error on log volume 1: could not open volume

2009-06-14 21:11:36 0x360 ERR 3 Admin Database state: OFFLINE

2009-06-14 21:11:36 0x360 ERR 6 KernelCo + Internal errorcode, Errorcode 9050 "disk_not_accessible"

2009-06-14 21:11:36 0x360 ERR 20017 Admin + RestartFilesystem failed with 'I/O error'

2009-06-14 21:11:36 0x664 ERR 7 Messages Begin of dump of registered messages

2009-06-14 21:11:36 0x664 ERR 10 Messages abort dump of registered messages

2009-06-14 21:11:36 0x664 ERR 8 Messages End of the message list registry dump

2009-06-14 21:11:37 ___ Stopping GMT 2009-06-15 01:11:37 7.6.00 Build 035-123-139-084

2009-06-14 21:21:13 --- Starting GMT 2009-06-15 01:21:13 7.6.00 Build 035-123-139-084

2009-06-14 21:21:19 0xA88 ERR 18159 VOLUMEIO Could not open volume 'C:\sapdb\SRD\saplog\DISKL001', rc = 2

2009-06-14 21:21:19 0x954 ERR 20027 IOMan Attach error on log volume 1: could not open volume

2009-06-14 21:21:19 0x954 ERR 3 Admin Database state: OFFLINE

2009-06-14 21:21:19 0x954 ERR 6 KernelCo + Internal errorcode, Errorcode 9050 "disk_not_accessible"

2009-06-14 21:21:19 0x954 ERR 20017 Admin + RestartFilesystem failed with 'I/O error'

2009-06-14 21:21:19 0xBFC ERR 7 Messages Begin of dump of registered messages

2009-06-14 21:21:19 0xBFC ERR 10 Messages abort dump of registered messages

2009-06-14 21:21:19 0xBFC ERR 8 Messages End of the message list registry dump

2009-06-14 21:21:20 ___ Stopping GMT 2009-06-15 01:21:20 7.6.00 Build 035-123-139-084

2009-06-14 21:29:06 --- Starting GMT 2009-06-15 01:29:06 7.6.00 Build 035-123-139-084

2009-06-14 21:29:12 0x9F0 ERR 18159 VOLUMEIO Could not open volume 'C:\sapdb\SRD\saplog\DISKL001', rc = 2

2009-06-14 21:29:12 0x3B0 ERR 20027 IOMan Attach error on log volume 1: could not open volume

2009-06-14 21:29:12 0x3B0 ERR 3 Admin Database state: OFFLINE

2009-06-14 21:29:12 0x3B0 ERR 6 KernelCo + Internal errorcode, Errorcode 9050 "disk_not_accessible"

2009-06-14 21:29:12 0x3B0 ERR 20017 Admin + RestartFilesystem failed with 'I/O error'

2009-06-14 21:29:12 0x244 ERR 7 Messages Begin of dump of registered messages

2009-06-14 21:29:12 0x244 ERR 10 Messages abort dump of registered messages

2009-06-14 21:29:12 0x244 ERR 8 Messages End of the message list registry dump

2009-06-14 21:29:14 ___ Stopping GMT 2009-06-15 01:29:14 7.6.00 Build 035-123-139-084

2009-06-14 21:38:21 --- Starting GMT 2009-06-15 01:38:21 7.6.00 Build 035-123-139-084

2009-06-14 21:38:27 0x180 ERR 18159 VOLUMEIO Could not open volume 'C:\sapdb\SRD\saplog\DISKL001', rc = 2

2009-06-14 21:38:27 0xA14 ERR 20027 IOMan Attach error on log volume 1: could not open volume

2009-06-14 21:38:27 0xA14 ERR 3 Admin Database state: OFFLINE

2009-06-14 21:38:27 0xA14 ERR 6 KernelCo + Internal errorcode, Errorcode 9050 "disk_not_accessible"

2009-06-14 21:38:27 0xA14 ERR 20017 Admin + RestartFilesystem failed with 'I/O error'

2009-06-14 21:38:27 0xBC ERR 7 Messages Begin of dump of registered messages

2009-06-14 21:38:27 0xBC ERR 10 Messages abort dump of registered messages

2009-06-14 21:38:27 0xBC ERR 8 Messages End of the message list registry dump

2009-06-14 21:38:29 ___ Stopping GMT 2009-06-15 01:38:29 7.6.00 Build 035-123-139-084

Regards,

BI Learner.

[JPReyes · Accepted solution]

could not open volume 'C:\sapdb\SRD\saplog\DISKL00

Seems like one of the logs volumes is not available?... have you check if its there?...

I/O errors mean that either the file is not there or is corrupted.

Regards

Juan

[former_member673162 · Accepted solution]

Juan,

you are correct the log DISKL00 doesnt exist. DISKL001 exists. Please help me with the next steps to get the file back.

Regards,

BI Learner.

[JPReyes · Accepted solution]

That was a typo on my side... DB is looking for DISKL001

The log file might be corrupt... you might have to do a restore from backup

Regards

Juan

[former_member673162 · Accepted solution]

I was successfully able to back up using backup wizard. I tried turn SRD db to Online but the same error pops up. Please advice.

[former_member229109 · Accepted solution]

Hello Juan,

-> As you know the error occurred during the database restart:

2009-06-14 21:38:27 0x180 ERR 18159 VOLUMEIO

Could not open volume 'C:\sapdb\SRD\saplog\DISKL001', rc = 2

2009-06-14 21:38:27 0xA14 ERR 20027 IOMan Attach error on log volume 1: could not open volume

->Please check & post the entries from knldiag file before the error occurred.

-> You are running the database version u201C7.6.00 Build 035-123-139-084u201D, please update the DBMGUI to 7.6 version.

-> Could you login to the database server & try to restart the database using dbmcli tool:

dbmcli u2013d SRD u2013u <dbm-user>,<pwd> db_online

When the database was restarted successfully before the problem occurred?

Thank you and best regards, Natalia Khlopina

[former_member673162 · Accepted solution]

Thank you very much guys for trying to help me out. DISKL001 file exists in C:\sapdb\SRD\saplog\DISKL001

Fyi.. we were able to login to this system earlier may be 6 months back. Not sure what happened... To me i think updating to 7.6 version GUI doesn't resolve the issue as the 7.6 build worked with 7.5 GUI version.

Need help in executing the command: i have typed dbmcli -d and it asked me to enter data base name which i have entered as SRD. i'm now in dbmcli on SRD>. when i try to enter -u < control >,< control > db_online

I'm getting err-24977,err_command: unknown DBM command "-u". Can you guys please guide me.

Below is the Knldiag log file details.

-

---

Date Time TID(hex) Typ MsgID Label Message-Text

-

---

2010-06-15 13:40:30 0x6E8 19707 CONNECT WINSOCK: 2.0, SQLTCP-DLL: 7.6.0

2010-06-15 13:40:30 0x6E8 20233 RTE Dump of all kernel parameters start

2010-06-15 13:40:30 0x6E8 20206 RTE Using mode NORMAL for data volume 1

2010-06-15 13:40:30 0x6E8 20206 RTE Using mode NORMAL for data volume 2

2010-06-15 13:40:30 0x6E8 20206 RTE Using mode NORMAL for data volume 3

2010-06-15 13:40:30 0x6E8 20206 RTE Using mode NORMAL for data volume 4

2010-06-15 13:40:30 0x6E8 20206 RTE Using mode NORMAL for data volume 5

2010-06-15 13:40:30 0x6E8 20234 RTE ADMIN=1

2010-06-15 13:40:30 0x6E8 20234 RTE AKDUMP_ALLOWED=YES

2010-06-15 13:40:30 0x6E8 20234 RTE ALLOW_MULTIPLE_SERVERTASK_UKTS=NO

2010-06-15 13:40:30 0x6E8 20234 RTE AUTHENTICATION_ALLOW=

2010-06-15 13:40:30 0x6E8 20234 RTE AUTHENTICATION_DENY=

2010-06-15 13:40:30 0x6E8 20234 RTE AUTOSAVE=1

2010-06-15 13:40:30 0x6E8 20234 RTE AUTO_RECREATE_BAD_INDEXES=NO

2010-06-15 13:40:30 0x6E8 20234 RTE BACKUPRESULT=1

2010-06-15 13:40:30 0x6E8 20234 RTE BACKUP_BLOCK_CNT=64

2010-06-15 13:40:30 0x6E8 20234 RTE BACKUPHISTFILE=dbm.knl

2010-06-15 13:40:30 0x6E8 20234 RTE BACKUPMED_DEF=dbm.mdf

2010-06-15 13:40:30 0x6E8 20234 RTE CACHE_SIZE=174720

2010-06-15 13:40:30 0x6E8 20234 RTE CALLSTACKLEVEL=0

2010-06-15 13:40:30 0x6E8 20234 RTE CATCACHE_MINSIZE=262144

2010-06-15 13:40:30 0x6E8 20234 RTE CAT_CACHE_SUPPLY=10000

2010-06-15 13:40:30 0x6E8 20234 RTE CHECKDATA=1

2010-06-15 13:40:30 0x6E8 20234 RTE CHECK_BACKUP=NO

2010-06-15 13:40:30 0x6E8 20234 RTE CHECK_COMMON=0

2010-06-15 13:40:30 0x6E8 20234 RTE CHECK_CONVERTER=0

2010-06-15 13:40:30 0x6E8 20234 RTE CHECK_DATACACHE=NO

2010-06-15 13:40:30 0x6E8 20234 RTE CHECK_DATAINDEX=0

2010-06-15 13:40:30 0x6E8 20234 RTE CHECK_DATAPAGELOG=0

2010-06-15 13:40:30 0x6E8 20234 RTE CHECK_FBM=0

2010-06-15 13:40:30 0x6E8 20234 RTE CHECK_HASHED_RESULTSET=0

2010-06-15 13:40:30 0x6E8 20234 RTE CHECK_IOMAN=0

2010-06-15 13:40:30 0x6E8 20234 RTE CHECK_KB_REGIONS=NO

2010-06-15 13:40:30 0x6E8 20234 RTE CHECK_LOCK_SUPPLY=NO

2010-06-15 13:40:30 0x6E8 20234 RTE CHECK_LOCK=NO

2010-06-15 13:40:30 0x6E8 20234 RTE CHECK_LOGHISTORY=0

2010-06-15 13:40:30 0x6E8 20234 RTE CHECK_LOGPAGE=0

2010-06-15 13:40:30 0x6E8 20234 RTE CHECK_LOGTRANS=0

2010-06-15 13:40:30 0x6E8 20234 RTE CHECK_LOGVOLUME=0

2010-06-15 13:40:30 0x6E8 20234 RTE CHECK_REGIONS=NO

2010-06-15 13:40:30 0x6E8 20234 RTE CHECK_SRVTASKS=0

2010-06-15 13:40:30 0x6E8 20234 RTE CHECK_TABLE_WIDTH=NO

2010-06-15 13:40:30 0x6E8 20234 RTE CHECK_TASK_SPECIFIC_CATALOGCACHE=NO

2010-06-15 13:40:30 0x6E8 20234 RTE CHECK_TRANSLIST=NO

2010-06-15 13:40:30 0x6E8 20234 RTE CHECK_TREE_LOCKS=NO

2010-06-15 13:40:30 0x6E8 20234 RTE CHECK_TREE=NO

2010-06-15 13:40:30 0x6E8 20234 RTE CLUSTERED_LOBS=NO

2010-06-15 13:40:30 0x6E8 20234 RTE CLUSTER_WRITE_THRESHOLD=80

2010-06-15 13:40:30 0x6E8 20234 RTE COLUMNCOMPRESSION=YES

2010-06-15 13:40:30 0x6E8 20234 RTE _COMMENT=

2010-06-15 13:40:30 0x6E8 20234 RTE CONTROLPASSWORD=***

2010-06-15 13:40:30 0x6E8 20234 RTE CONTROLUSERID=CONTROL

2010-06-15 13:40:30 0x6E8 20234 RTE CONVERTER_REGIONS=8

2010-06-15 13:40:30 0x6E8 20234 RTE DATABASEFULL=1

2010-06-15 13:40:30 0x6E8 20234 RTE DATACACHE_RGNS=64

2010-06-15 13:40:30 0x6E8 20234 RTE DATA_IO_BLOCK_COUNT=64

2010-06-15 13:40:30 0x6E8 20234 RTE DATA_VOLUME_GROUPS=1

2010-06-15 13:40:30 0x6E8 20234 RTE DATA_VOLUME_MODE_0001=NORMAL

2010-06-15 13:40:30 0x6E8 20234 RTE DATA_VOLUME_MODE_0002=NORMAL

2010-06-15 13:40:30 0x6E8 20234 RTE DATA_VOLUME_MODE_0003=NORMAL

2010-06-15 13:40:30 0x6E8 20234 RTE DATA_VOLUME_MODE_0004=NORMAL

2010-06-15 13:40:30 0x6E8 20234 RTE DATA_VOLUME_MODE_0005=NORMAL

2010-06-15 13:40:30 0x6E8 20234 RTE DATA_VOLUME_NAME_0001=C:\sapdb\SRD\sapdata\DISKD0001

2010-06-15 13:40:30 0x6E8 20234 RTE DATA_VOLUME_NAME_0002=C:\sapdb\SRD\sapdata\DISKD0002

2010-06-15 13:40:30 0x6E8 20234 RTE DATA_VOLUME_NAME_0003=C:\sapdb\SRD\sapdata\DISKD0003

2010-06-15 13:40:30 0x6E8 20234 RTE DATA_VOLUME_NAME_0004=C:\sapdb\SRD\sapdata\DISKD0004

2010-06-15 13:40:30 0x6E8 20234 RTE DATA_VOLUME_NAME_0005=C:\sapdb\SRD\sapdata\DISKD0005

2010-06-15 13:40:30 0x6E8 20234 RTE DATA_VOLUME_SIZE_0001=640000

2010-06-15 13:40:30 0x6E8 20234 RTE DATA_VOLUME_SIZE_0002=640000

2010-06-15 13:40:30 0x6E8 20234 RTE DATA_VOLUME_SIZE_0003=640000

2010-06-15 13:40:30 0x6E8 20234 RTE DATA_VOLUME_SIZE_0004=640000

2010-06-15 13:40:30 0x6E8 20234 RTE DATA_VOLUME_SIZE_0005=640000

2010-06-15 13:40:30 0x6E8 20234 RTE DATA_VOLUME_TYPE_0001=F

2010-06-15 13:40:30 0x6E8 20234 RTE DATA_VOLUME_TYPE_0002=F

2010-06-15 13:40:30 0x6E8 20234 RTE DATA_VOLUME_TYPE_0003=F

2010-06-15 13:40:30 0x6E8 20234 RTE DATA_VOLUME_TYPE_0004=F

2010-06-15 13:40:30 0x6E8 20234 RTE DATA_VOLUME_TYPE_0005=F

2010-06-15 13:40:30 0x6E8 20234 RTE DATE_TIME_FORMAT=INTERNAL

2010-06-15 13:40:30 0x6E8 20234 RTE DBFILLINGABOVELIMIT=70L80M85M90H95H96H97H98H99H

2010-06-15 13:40:30 0x6E8 20234 RTE DBFILLINGBELOWLIMIT=70L80L85L90L95L

2010-06-15 13:40:30 0x6E8 20234 RTE DDLTRIGGER=YES

2010-06-15 13:40:30 0x6E8 20234 RTE DEADLOCK_DETECTION=4

2010-06-15 13:40:30 0x6E8 20234 RTE DEFAULT_CODE=ASCII

2010-06-15 13:40:30 0x6E8 20234 RTE DELAYCOMMIT=NO

2010-06-15 13:40:30 0x6E8 20234 RTE DELAYLOGWRITER=0

2010-06-15 13:40:30 0x6E8 20234 RTE DIAG_HISTORY_NUM=2

2010-06-15 13:40:30 0x6E8 20234 RTE DIAG_HISTORY_PATH=c:\sapdb\data\wrk\SRD\DIAGHISTORY

2010-06-15 13:40:30 0x6E8 20234 RTE DIAGSEM=0

2010-06-15 13:40:30 0x6E8 20234 RTE DWIO_AREA_FLUSH=50

2010-06-15 13:40:30 0x6E8 20234 RTE DWIO_AREA_SIZE=50

2010-06-15 13:40:30 0x6E8 20234 RTE DWLRU_TAIL_FLUSH=25

2010-06-15 13:40:30 0x6E8 20234 RTE ENABLE_CHECK_INSTANCE=YES

2010-06-15 13:40:30 0x6E8 20234 RTE ENABLE_SYSTEM_TRIGGERS=YES

2010-06-15 13:40:30 0x6E8 20234 RTE ERROR=3

2010-06-15 13:40:30 0x6E8 20234 RTE _EVENTFILE=knldiag.evt

2010-06-15 13:40:30 0x6E8 20234 RTE _EVENTSIZE=0

2010-06-15 13:40:30 0x6E8 20234 RTE EVENT=1

2010-06-15 13:40:30 0x6E8 20234 RTE EXPAND_COM_TRACE=NO

2010-06-15 13:40:30 0x6E8 20234 RTE EXTERNAL_DUMP_REQUEST=NO

2010-06-15 13:40:30 0x6E8 20234 RTE FBMLOW_IO_RATE=10

2010-06-15 13:40:30 0x6E8 20234 RTE FBM_VOLUME_BALANCE=10

2010-06-15 13:40:30 0x6E8 20234 RTE FBM_VOLUME_COMPRESSION=50

2010-06-15 13:40:30 0x6E8 20234 RTE FILEDIR_SPINLOCKPOOL_SIZE=10

2010-06-15 13:40:30 0x6E8 20234 RTE FORBID_LOAD_BALANCING=NO

2010-06-15 13:40:30 0x6E8 20234 RTE FORMATTING_MODE=PARALLEL

2010-06-15 13:40:30 0x6E8 20234 RTE FORMAT_DATAVOLUME=YES

2010-06-15 13:40:30 0x6E8 20234 RTE HASHED_RESULTSET_CACHESIZE=262144

2010-06-15 13:40:30 0x6E8 20234 RTE HASHED_RESULTSET=YES

2010-06-15 13:40:30 0x6E8 20234 RTE HEAP_CHECK_LEVEL=0

2010-06-15 13:40:30 0x6E8 20234 RTE HIRES_TIMER_TYPE=CPU

2010-06-15 13:40:30 0x6E8 20234 RTE HS_STORAGE_DLL=libhsscopy

2010-06-15 13:40:30 0x6E8 20234 RTE HS_SYNC_INTERVAL=50

2010-06-15 13:40:30 0x6E8 20234 RTE IDXFILELIST_SIZE=2048

2010-06-15 13:40:30 0x6E8 20234 RTE INDEX_LEAF_CACHING=2

2010-06-15 13:40:30 0x6E8 20234 RTE INIT_ALLOCATORSIZE=258048

2010-06-15 13:40:30 0x6E8 20234 RTE INSTANCE_TYPE=OLTP

2010-06-15 13:40:30 0x6E8 20234 RTE IOPROCSFOR_PRIO=0

2010-06-15 13:40:30 0x6E8 20234 RTE IOPROCSFOR_READER=0

2010-06-15 13:40:30 0x6E8 20234 RTE IOPROCSPER_DEV=1

2010-06-15 13:40:30 0x6E8 20234 RTE IOPROCSSWITCH=2

2010-06-15 13:40:30 0x6E8 20234 RTE JOIN_MAXTAB_LEVEL4=64

2010-06-15 13:40:30 0x6E8 20234 RTE JOIN_MAXTAB_LEVEL9=5

2010-06-15 13:40:30 0x6E8 20234 RTE JOIN_SEARCH_LEVEL=0

2010-06-15 13:40:30 0x6E8 20234 RTE JOIN_TABLEBUFFER=128

2010-06-15 13:40:30 0x6E8 20234 RTE _KERNELDIAGFILE=knldiag

2010-06-15 13:40:30 0x6E8 20234 RTE KERNELDIAGSIZE=800

2010-06-15 13:40:30 0x6E8 20234 RTE _KERNELDUMPFILE=knldump

2010-06-15 13:40:30 0x6E8 20234 RTE _KERNELTRACEFILE=knltrace

2010-06-15 13:40:30 0x6E8 20234 RTE KERNELTRACESIZE=869

2010-06-15 13:40:30 0x6E8 20234 RTE KERNELVERSION=KERNEL 7.6.00 BUILD 035-123-139-084

2010-06-15 13:40:30 0x6E8 20234 RTE LOAD_BALANCING_CHK=0

2010-06-15 13:40:30 0x6E8 20234 RTE LOAD_BALANCING_DIF=10

2010-06-15 13:40:30 0x6E8 20234 RTE LOAD_BALANCING_EQ=5

2010-06-15 13:40:30 0x6E8 20234 RTE LOCAL_REDO_LOG_BUFFER_SIZE=0

2010-06-15 13:40:30 0x6E8 20234 RTE LOCKSUPPLY_BLOCK=100

2010-06-15 13:40:30 0x6E8 20234 RTE LOGABOVELIMIT=50L75L90M95M96H97H98H99H

2010-06-15 13:40:30 0x6E8 20234 RTE LOGFULL=1

2010-06-15 13:40:30 0x6E8 20234 RTE LOGSEGMENTFULL=1

2010-06-15 13:40:30 0x6E8 20234 RTE LOG_BACKUP_TO_PIPE=NO

2010-06-15 13:40:30 0x6E8 20234 RTE LOG_IO_BLOCK_COUNT=4

2010-06-15 13:40:30 0x6E8 20234 RTE LOG_IO_QUEUE=200

2010-06-15 13:40:30 0x6E8 20234 RTE LOG_MIRRORED=NO

2010-06-15 13:40:30 0x6E8 20234 RTE LOG_QUEUE_COUNT=1

2010-06-15 13:40:30 0x6E8 20234 RTE LOG_SEGMENT_SIZE=273066

2010-06-15 13:40:30 0x6E8 20234 RTE LOG_VOLUME_NAME_001=C:\sapdb\SRD\saplog\DISKL001

2010-06-15 13:40:30 0x6E8 20234 RTE LOG_VOLUME_SIZE_001=819200

2010-06-15 13:40:30 0x6E8 20234 RTE LOG_VOLUME_TYPE_001=F

2010-06-15 13:40:30 0x6E8 20234 RTE LRU_FOR_SCAN=NO

2010-06-15 13:40:30 0x6E8 20234 RTE MAXBACKUPDEVS=2

2010-06-15 13:40:30 0x6E8 20234 RTE MAXCPU=2

2010-06-15 13:40:30 0x6E8 20234 RTE MAXDATAVOLUMES=11

2010-06-15 13:40:30 0x6E8 20234 RTE _MAXEVENTS=100

2010-06-15 13:40:30 0x6E8 20234 RTE _MAXEVENTTASKS=2

2010-06-15 13:40:30 0x6E8 20234 RTE MAXGARBAGECOLL=1

2010-06-15 13:40:30 0x6E8 20234 RTE MAXLOCKS=300000

2010-06-15 13:40:30 0x6E8 20234 RTE MAXLOGVOLUMES=2

2010-06-15 13:40:30 0x6E8 20234 RTE MAXPAGER=64

2010-06-15 13:40:30 0x6E8 20234 RTE MAXRGN_REQUEST=-1

2010-06-15 13:40:30 0x6E8 20234 RTE MAXSERVERTASKS=28

2010-06-15 13:40:30 0x6E8 20234 RTE MAXTASKSTACK=1024

2010-06-15 13:40:30 0x6E8 20234 RTE _MAXTRANS=408

2010-06-15 13:40:30 0x6E8 20234 RTE MAXUSERTASKS=50

2010-06-15 13:40:30 0x6E8 20234 RTE MAXVOLUMES=14

2010-06-15 13:40:30 0x6E8 20234 RTE MAX_HASHTABLE_MEMORY=5120

2010-06-15 13:40:30 0x6E8 20234 RTE MAX_LOG_QUEUE_COUNT=0

2010-06-15 13:40:30 0x6E8 20234 RTE MAXMESSAGE_FILES=0

2010-06-15 13:40:30 0x6E8 20234 RTE MAX_MESSAGE_LIST_LENGTH=100

2010-06-15 13:40:30 0x6E8 20234 RTE MAX_RETENTION_TIME=480

2010-06-15 13:40:30 0x6E8 20234 RTE MAX_SERVERTASK_STACK=500

2010-06-15 13:40:30 0x6E8 20234 RTE MAX_SINGLE_HASHTABLE_SIZE=512

2010-06-15 13:40:30 0x6E8 20234 RTE MAX_SPECIALTASK_STACK=500

( chopped because it is exceeding the maximum length of 15000 characters Part 1... will send the second part if needed.

Edited by: BI Learner on Jun 16, 2010 8:33 PM

Edited by: BI Learner on Jun 16, 2010 8:33 PM

[former_member673162 · Accepted solution]

Let me know if you need more details of knldiag file

============================================ begin of write cycle ==================

2010-06-15 13:40:36 0x6D4 19633 CONNECT Connect req. (T69, Node:'', PID:3068)

2010-06-15 13:40:36 0x6D4 19615 VOLUMEIO Attaching volume 'C:\sapdb\SRD\sapdata\DISKD0001'

2010-06-15 13:40:36 0x508 19613 DBSTATE I/O thread for 'C:\sapdb\SRD\sapdata\DISKD0001' started

2010-06-15 13:40:36 0x6D4 19617 VOLUMEIO Single I/O attach, 'C:\sapdb\SRD\sapdata\DISKD0001', UKT:7

2010-06-15 13:40:36 0x6D4 19615 VOLUMEIO Attaching volume 'C:\sapdb\SRD\sapdata\DISKD0002'

2010-06-15 13:40:36 0x95C 19613 DBSTATE I/O thread for 'C:\sapdb\SRD\sapdata\DISKD0002' started

2010-06-15 13:40:37 0x6D4 19617 VOLUMEIO Single I/O attach, 'C:\sapdb\SRD\sapdata\DISKD0002', UKT:7

2010-06-15 13:40:37 0x6D4 19615 VOLUMEIO Attaching volume 'C:\sapdb\SRD\sapdata\DISKD0003'

2010-06-15 13:40:37 0xAC4 19613 DBSTATE I/O thread for 'C:\sapdb\SRD\sapdata\DISKD0003' started

2010-06-15 13:40:37 0x6D4 19617 VOLUMEIO Single I/O attach, 'C:\sapdb\SRD\sapdata\DISKD0003', UKT:7

2010-06-15 13:40:37 0x6D4 19615 VOLUMEIO Attaching volume 'C:\sapdb\SRD\sapdata\DISKD0004'

2010-06-15 13:40:37 0x86C 19613 DBSTATE I/O thread for 'C:\sapdb\SRD\sapdata\DISKD0004' started

2010-06-15 13:40:37 0x6D4 19617 VOLUMEIO Single I/O attach, 'C:\sapdb\SRD\sapdata\DISKD0004', UKT:7

2010-06-15 13:40:37 0x6D4 19615 VOLUMEIO Attaching volume 'C:\sapdb\SRD\sapdata\DISKD0005'

2010-06-15 13:40:37 0x430 19613 DBSTATE I/O thread for 'C:\sapdb\SRD\sapdata\DISKD0005' started

2010-06-15 13:40:37 0x6D4 19617 VOLUMEIO Single I/O attach, 'C:\sapdb\SRD\sapdata\DISKD0005', UKT:7

2010-06-15 13:40:37 0x6D4 19615 VOLUMEIO Attaching volume 'C:\sapdb\SRD\saplog\DISKL001'

2010-06-15 13:40:37 0x6B8 ERR 18156 VOLUMEIO It's not a valid volume: 'C:\sapdb\SRD\saplog\DISKL001'

2010-06-15 13:40:37 0x6D4 ERR 20027 IOMan Attach error on log volume 1: error evaluating volume

2010-06-15 13:40:37 0x6D4 19616 VOLUMEIO Detaching volume 'C:\sapdb\SRD\sapdata\DISKD0001'

2010-06-15 13:40:37 0x6B8 19618 VOLUMEIO Single I/O detach, 'C:\sapdb\SRD\sapdata\DISKD0001', UKT:7

2010-06-15 13:40:37 0x508 19614 DBSTATE I/O thread for 'C:\sapdb\SRD\sapdata\DISKD0001' stopped

2010-06-15 13:40:37 0x6D4 19616 VOLUMEIO Detaching volume 'C:\sapdb\SRD\sapdata\DISKD0002'

2010-06-15 13:40:37 0x6B8 19618 VOLUMEIO Single I/O detach, 'C:\sapdb\SRD\sapdata\DISKD0002', UKT:7

2010-06-15 13:40:37 0x95C 19614 DBSTATE I/O thread for 'C:\sapdb\SRD\sapdata\DISKD0002' stopped

2010-06-15 13:40:37 0x6D4 19616 VOLUMEIO Detaching volume 'C:\sapdb\SRD\sapdata\DISKD0003'

2010-06-15 13:40:37 0x6B8 19618 VOLUMEIO Single I/O detach, 'C:\sapdb\SRD\sapdata\DISKD0003', UKT:7

2010-06-15 13:40:37 0xAC4 19614 DBSTATE I/O thread for 'C:\sapdb\SRD\sapdata\DISKD0003' stopped

2010-06-15 13:40:37 0x6D4 19616 VOLUMEIO Detaching volume 'C:\sapdb\SRD\sapdata\DISKD0004'

2010-06-15 13:40:37 0x6B8 19618 VOLUMEIO Single I/O detach, 'C:\sapdb\SRD\sapdata\DISKD0004', UKT:7

2010-06-15 13:40:37 0x86C 19614 DBSTATE I/O thread for 'C:\sapdb\SRD\sapdata\DISKD0004' stopped

2010-06-15 13:40:37 0x6D4 19616 VOLUMEIO Detaching volume 'C:\sapdb\SRD\sapdata\DISKD0005'

2010-06-15 13:40:37 0x6B8 19618 VOLUMEIO Single I/O detach, 'C:\sapdb\SRD\sapdata\DISKD0005', UKT:7

2010-06-15 13:40:37 0x430 19614 DBSTATE I/O thread for 'C:\sapdb\SRD\sapdata\DISKD0005' stopped

2010-06-15 13:40:37 0x6D4 ERR 3 Admin Database state: OFFLINE

2010-06-15 13:40:37 0x6D4 ERR 6 KernelCo + Internal errorcode, Errorcode 9050 "disk_not_accessible"

2010-06-15 13:40:37 0x6D4 ERR 20017 Admin + RestartFilesystem failed with 'I/O error'

2010-06-15 13:40:37 0x6D4 19651 CONNECT Connection released, T69

2010-06-15 13:40:37 0x6D4 19621 DBSTATE Shutdown kill requested

2010-06-15 13:40:37 0x6E8 ERR 7 Messages Begin of dump of registered messages

2010-06-15 13:40:37 0x6E8 ERR 10 Messages abort dump of registered messages

2010-06-15 13:40:37 0x6E8 ERR 8 Messages End of the message list registry dump

2010-06-15 13:40:37 0x6E8 19684 TASKING Tracewriter termination timeout: 1200 sec

2010-06-15 13:40:37 0x4FC 20000 Trace Start flush kernel trace

2010-06-15 13:40:37 0x4FC 19617 VOLUMEIO Single I/O attach, 'knltrace', UKT:1

2010-06-15 13:40:37 0x4FC 20001 Trace Stop flush kernel trace

2010-06-15 13:40:37 0x4FC 20002 Trace Start flush kernel dump

2010-06-15 13:40:37 0x4FC 20003 Trace Stop flush kernel dump

2010-06-15 13:40:37 0x4FC 19619 TASKING Releasing tracewriter

2010-06-15 13:40:37 0x6E8 19890 DIAGHIST Backup of diagnostic files will be forced at next restart

2010-06-15 13:40:37 0x6E8 19600 VERSION 'Kernel 7.6.00 Build 035-123-139-084'

2010-06-15 13:40:37 0x6E8 19654 DBSTATE SERVERDB 'SRD' has stopped

-

---

current write position -

---

[former_member229109 · Accepted solution]

Hello,

-> From the last post of knldiag log::

2010-06-15 13:40:37 0x6B8 ERR 18156 VOLUMEIO It's not a valid volume: 'C:\sapdb\SRD\saplog\DISKL001'

Check the properties of this file. Was this file compressed or changed?

-> As you was able to create the databackup of the database in admin status, you could run the recovery with initialization as one of the option to solve this issue.

-> Are you SAP customer?

Do you know how the database was stopped?

-> To start the database using dbmcli tool:

A) dbmcli u2013d SRD u2013u control,control db_online

or

B) dbmcli u2013d SRD u2013u control,control

<enter>

dbmcli on SRD>db_online

<enter>

dbmcli on SRD>exit

Thank you and best regards, Natalia Khlopina

[former_member673162 · Accepted solution]

-> From the last post of knldiag log::

2010-06-15 13:40:37 0x6B8 ERR 18156 VOLUMEIO It's not a valid volume: 'C:\sapdb\SRD\saplog\DISKL001'

Check the properties of this file. Was this file compressed or changed?

+The file size is 6.25 GB and was not compressed. This file has full access on the security tab.+

-> As you was able to create the databackup of the database in admin status, you could run the recovery with initialization as one of the option to solve this issue.

+Tried restore database instance with Initilization was getting -24988 SQL error [ db_activate RECOVER "new" DATA ];-902, I/O ERROR.+

-> Are you SAP customer? +Yes this system was order for learning.+

Do you know how the database was stopped? T+his is a learning environment and i'm not sure.+

-> To start the database using dbmcli tool:

A) dbmcli u2013d SRD u2013u control,control db_online

or

B) dbmcli u2013d SRD u2013u control,control

<enter>

dbmcli on SRD>db_online

<enter>

dbmcli on SRD>exit

_got the same error message -24988 error sql -902 i/o error 3, database state offline 6, Internal errorcode, errorcode 9050 "disk not accessible" 20017, restart File system failed with ' I/O error'_

Thanks !

[former_member229109 · Accepted solution]

Hello,

-> Please review the SAP notes::

1377148 FAQ: SAP MaxDB backup/recovery

869267 FAQ: SAP MaxDB LOG area

-> If the log volume was not compressed, then may be it's changed or corrupted.

Database kernel could not read it.

As the database kernel could not read the log file, could you rename it to corrupted <then delete later, if you don't need it >, then restart the recovery with initialization.

-> To run the database administration and learning =>

I recommend to update the DBMGUI.

See the SAP note:

386714 SQL Studio and Database Manager GUI installation

For SAP liveCache documentation please see the SAP note 767598.

-> You could start the database using dbmcli tool if you solve the issue with the log file,

please post the following outputs:

dbmcli u2013d SRD u2013u control,control

<enter>

dbmcli on SRD>param_getvolsall

<enter>

dbmcli on SRD>medium_getall

<enter>

What errors did you see in the knldiag file after you started the recovery with initialization?

Thank you and best regards, Natalia Khlopina

Edited by: Natalia Khlopina on Jun 16, 2010 7:35 PM

[Former Member]

somehow I saw this post as new one , I did not saw other replys

Edited by: Ivan Levrinc on Jun 16, 2010 7:35 PM

[former_member673162]

Please ignore

Edited by: BI Learner on Jun 16, 2010 8:36 PM

[former_member673162]

Please ignore my mistake

Edited by: BI Learner on Jun 16, 2010 8:36 PM