Disk I/O Error after upgrade

[Former Member]

Hello, I am running NW2004s SP10 on a Windows XP 32 bit system w/ MAXDB ver 7.6.

I tried to apply an upgrade to SP 13 and now my database will not start nor can I connect. I get the following in the DB trace:

2007-12-20 11:23:45 0x968 31 SrvTask Permanently reserved 13 servertasks for 'Backup / Restore'.

2007-12-20 11:23:45 0xC68 67 RTEKERN Kernel state changed from STARTING to ADMIN

2007-12-20 11:23:45 0x968 31 SrvTask Permanently reserved 2 servertasks for 'Backup / Restore'.

2007-12-20 11:23:45 0xC68 19601 MsgOutp SERVERDB is ready

2007-12-20 11:23:45 0xC68 221 RTE Database tries automatic restart

2007-12-20 11:23:45 0x9C0 19821 MsgOutp Thread 2496 starting

2007-12-20 11:23:46 0xD90 19633 MsgOutp Connect req. (T53, Node:'', PID:2200)

2007-12-20 11:23:46 0xD90 19615 MsgOutp Attaching volume 'C:\sapdb\D01\sapdata\DISKD0001'

2007-12-20 11:23:46 0x17D4 ERR 18177 MsgOutp No volume on compressed file 'C:\sapdb\D01\sapdata\DISKD0001'

2007-12-20 11:23:46 0xD90 ERR 23 IOMan Attach error on Data volume 1: no volumes on compressed file

2007-12-20 11:23:46 0xD90 ERR 14 Admin RestartFilesystem failed with 'I/O error'

2007-12-20 11:23:46 0xD90 49 Kernel EMERGENCY SHUTDOWN, Error occured: -902, 'I/O error' (disk_not_accessible)

2007-12-20 11:23:46 0xD90 40 Admin Kernel state: 'OFFLINE' reached

2007-12-20 11:23:46 0xD90 19620 MsgOutp Shutdown normal requested

2007-12-20 11:23:46 0x324 19684 MsgOutp Tracewriter termination timeout: 1200 sec

2007-12-20 11:23:46 0xEC4 0 Trace Start flush kernel trace

2007-12-20 11:23:46 0xEC4 19617 MsgOutp Single I/O attach, 'knltrace', UKT:1

2007-12-20 11:23:46 0xEC4 1 Trace Stop flush kernel trace

2007-12-20 11:23:46 0xEC4 19619 MsgOutp Releasing tracewriter

2007-12-20 11:23:46 0x324 19600 MsgOutp 'Kernel 7.6.00 Build 009-123-105-149'

2007-12-20 11:23:46 0x324 19654 MsgOutp SERVERDB 'D01' has stopped

It looks like a disk error, but I am not sure. I was having no issues prior to upgrade. Could it be the upgrade corrupted the DB or could I actually have a bad disk?

[Former Member · Accepted solution]

Yes, it is (it was before). I will try uncompressing it. Is that the right way to go?

[markus_doehr2 · Accepted solution]

Yes. The database files must not be compressed

Markus

[Former Member]

Uncommpressed the data and log files and was able to start the DB. I believe the files got compressed when a disk cleanup was run prior to the upgrade to free up disk space.

Thanks for the help!! Points awarded!!

[Former Member]

No.

[markus_doehr2]

The error points to that... is the file itself maybe compressed (to save space)?

Markus

[markus_doehr2]

Did you compress your database files (using Windows' compress filesystem settings)?

Markus