maxdb crashes once after every system start

[former_member793273]

Hi there.

We use maxdb in Version 7.9.10 but it also was a problem in previous 7.8er Versions.
I have installed maxdb on my local system (win 10) and every morning after system restart, the maxdb is crashed after the first time it is accessed.
Then after a manual restart of the instance with the database studio, maxdb is running without any problems the whole day. This szenario is repeating the next day.
A made some tests:
Afer a manual system "reboot", the problem seems not to be happend. But afer a "system shutdown and manual system start" the problem happens again.
Here is the KnlMsg log of two different crashes from the test from today. I must post it in pictures, beacuse in the textual way formatting is gone.
First Start: Data volume name is anonymized be me with "....."

Second Start (after shutdown and start system again): LOG_VOLUME_001 is renamed by me with "....."

This problem happens on differnt systems (also on systems of some of my colleagues); futhermore it was a problem in the past in older MAXDB versions.I can read the "The device is not ready" ih the first Log; but where can i start diagnose? Are there any known issues in combination with other system programs like bitlocker or some others?
Any ideas?
Thx and best reagrds
Marco

[former_member793273]

Together we have found the origin of this problem.
Thanks to Alexander and Birgit and the complete other team members of the SAP MaxDB-Team which were participated.

Simple reason, but not easy to find:

It's the fast startup mode of windows!

In our opinion:
This mode shutdown running programs; it logs of the current user but it don't turn off the windows kernal and also not running Services. After restart system then; something in the state of the old running services is incompatible or in a bad state.

Workaround (for us) is simple:

Just turn off windows fast startup mode

Regards, Marco

[former_member793273]

KnlMsg from today as attachment.

Regards, Marco

[former_member272632]

Hello Marco,

if you are SAP customer you can open a case in the ticketing system. Let me know the number. Otherwise you can generate diagpkg.tgz file and attach it here. (Enter in the Studio Admin View in the 'Command Line' tab the command: diag_pack. It will generate diagpkg.tgz in the running directory, which you will find with the command: param_getvalue RunDirectory)

Regards, Alexander

[former_member793273]

Hi Alexander.

Thanks for fast response!! Adding the answers to your questions:
-No; there are no hints about I/O errors on disk device in the eventlog. I looked through this morning and also several times in the past.
-D is a simple NTFS-Partition on a SSD hard disk. Nothing special except bitlocker crypted. Space enough with about 320GB.
-No I don't use a virtual device. Simple direct installed Win 10.

I reproduced the error again this morning:
Computer started at 7:40.
First; I did no activity on the DB.
Starting Database Studio at about 8:10.
Instance is running; everything looks good.
Then I opened "Schemas"-node of the user and in there also the node for the table list.
Still; everything looks good.
I pick a small table and select "Content". It shows me the Content of the table and still everything looks good.
Then I do it again (and I think also with the same table) Show "Content" -> Crash

-Yes; of cause I can give you the complete KnlMsg or other diagnosis files if you need them. I will send it to you.

Thanks a lot and best regards
Marco

[former_member272632]

Hello Marco,

I'm not sure it is MaxDB issue, as it is using usual OS functions to access the storage. You can check the windows events messages. There must be information regarding storage issues.

What is your drive 😧 ? is it a special storage? (External USB drive, etc)

Are you running virtual machine? If yes how the virtual machine disks are configured? You must allocate whole guest disk size on the VM server.

Would you provide complete KnlMsg file?

Thank you, regards, Alexander

[former_member793273]

Hi Birgit.
Thanks for your effort and the fast answer!
I've tried your solution. I played around with the settings of the windows maxdb instance service. But "Automatic (Delayed Start)" doesn't help for me.
Everytime I shutdown the computer and then start the system new, I'm getting the same the error again. That's not the same than reboot the system; after reboot the problem seems not to be happen!!!
I think it's not a problem that there are not all system resources available. Because with experience with this problem a made in the past, there are situations that after a fresh system start in morning and after a few hours with no process working on the db; everything seems to be running fine (also the service of the instance is running) and then the first accesses comes (seems to be write access?) than the db crashes consequently and the instance service has stopped. The first access f.e. can be easy made with the database studio and then klick on "Schemas" tree node of the instance of the sql user.
Seems to be a hard issue...

[birgit_malik]

Hi Marco,

I asked our SAP MaxDB developer team and got the following answer:

May be the user added the start of SAP MaxDB as AutoStart. So after reboot of Microsoft Windows system all services marked with AutoStart start automatically (no manual start of database is necessary).

It can happen that not all resources are available yet if MaxDB service starts automatically. The errors you mentioned can point to this.

In such case you can use AutoStart with delay: Automatic (Delayed Start).

Regards IMS SAP MaxDB