MaxDB does not start - dbmcli shows no reaction

[Former Member]

Hello,

Since two weeks I'm not able to start a NW7.3 System. After several checks I figured out that the database (MaxDB 7.8 on Windows) does not start. There were no changes in Hardware or OS, Kernel was not updated/upgraded. The System was running since installation in May 2012.

dbmcli db_enum does work:

But my problem is, that when I run dbmcli -u superdba,***** -d NWD db_online, there is no further reaction. Unfortunatelly the MaxDB logfiles (knlmessage etc.) were not updated, so I have no hint what I should check as nect.

Here you can find the whole discussion in Netweaver group: http://scn.sap.com/thread/3333896

So my question would be: is there any other MaxDB tool or log file, which can help me to solve this issue - or get at least a hint on the reason why the database can't start any more? Or maybe is an update to 7.9 a possible solution?

Thanks in advance

Václav

[Former Member · Accepted solution]

Hi,

what did you do so that the system does not start?

Did it crash?

Did you try to reboot the server already? Maybe some shared memory objects stayed after shutdown.

As I know an upgrade to MaxDB 7.9 would not be possible. Therefore you need a system which can reach state online.

Best regards

Christian

[Former Member · Accepted solution]

Hi Christian,

I'm not sure what happend, may be the VM (running on ESX) stopped suddenly. I restarted the server several times (including ESX) - without success. All other machines on the hardware (SAP ERP) are fine, it's just this one. Is there a way to check the consistency of the libraries, program files and parameters? Or do you have other suggestions?

Thanks & Regards

Václav

[Former Member · Accepted solution]

Hi Vaclav,

I have a one doubt here...

Have you installed maxdb database studio? if yes please connect and check your data volumes or log volumes full?

If studio not installed check at command level as below.

dbmcli -d <SID> -u control,<password of control user> show active

Please check and let me know result

Thanks,

Venkat

[former_member188883 · Accepted solution]

Hi Vaclav,

Please kill the existing x_server service from task manager (if any).

Then restart the x_server service . Check the results after this.

Regards,

Deepak Kori

[Former Member · Accepted solution]

Hello,

I restarted the x_server and tried the command show active (DB Studio is no installed locally). x_server is starting/stoping without any problem, just dbmcli does still not respond:

Regards

Václav

[Former Member · Accepted solution]

Hi Vaclav,

did you do as mentioned by Deepak?

What is the result?

Once I had a similar problem, dbmcli just did not come back after an upgrade ... SAP told me to stop the database and to kill the processes (dbmsrv).

Than they backed up (renamed) the *.shi / *.shm files from the maxdb rundirectory (sapdb\data\wrk) and every thing went fine ...

Maybe you could try this?

Best regards

Christian

[former_member188883 · Accepted solution]

Hi Vaclav,

As described by Christian, could you try this.

SAP told me to stop the database and to kill the processes (dbmsrv).
Than they backed up (renamed) the *.shi / *.shm files from the maxdb rundirectory 

Regards,

Deepak Kori

[Former Member · Accepted solution]

Hello Christian,

I tried today Deepaks suggestion. I renamed the mentioned files:

This is what happened in cmd: first I tried dbmcli db_state. Then I killed the process in task manager (this caused the error message below) and renamed the files. After that I tried dbmcli db_state again, the dbmserv process started again, but nothing further happens.

Are there maybe some config files which I can check?

Thanks & Regards

Václav

[former_member188883 · Accepted solution]

Hi Vaclav,

Can you replicate the issue once gain to get the error message

" Connecton failed to node (local) for database NWD"

Once you get this error , look into dbmcli.log and share details.

Regards,

Deepak Kori

[Former Member · Accepted solution]

Hi Vaclav,

there were no other *.shi or *.shm files when the database was shutdown? These are not the one I expected.

Please shutdown the database and search for NWD.dbm.shi and NWD.dbm.shm (hope they are named this way) on your disk to rename (should be in maxdb rundirectory, but how to get this parameter when you do not even get a db_state).

If these files does not exist anywhere, than the error must be an other...

Best regards

Christian

[Former Member · Accepted solution]

Hi Christian,

I have overlooked the files you mentioned. Now I made a backup of NWD.dbm.shi/shm and actually it worked! You are really great guys! Thanks a lot, after that the database works fine:

The Netweaver ist now starting without any trouble

Again, thanks a lot!

Regards,

Václav

[thorsten_zielke]

Hello,

let me give you some quick thoughts for trouble checking:

1. Make sure to use the 'dbmcli' from the database server and not remotely.

2. Since 7.8, always access MaxDB on Windows with 'Administrator' privilege from the command line.

3. Execute 'xinstinfo NWD' and navigate to the resulting 'InstallationPath' and from there to the 'pgm' subdirectory. In your example above you were using the dbmcli from the 'client-installation' directory.

4. Try a 'dbmcli db_state'

5. If the state is 'unknown', stop it with 'dbmcli db_offline'

6. Try to start the database to 'admin' only.

Thorsten

[Former Member]

Hello Thorsten,

thank you for your suggestions, this is what I tried today:

• Logged on to db server as Administrator
• started cmd with option "run as administrator" (just to make sure that it isn't a privilege issue)
• executed xinstinfo NWD in order to determine the right path
• tried dbmcli db_state:

After that nothing happens, no error message or any reaction. Then I checked the task manager, where a MaxDB task is running:

But even if I was waiting for at least half an hour - no reaction.

Do you have any idea what I can check as next?

Thanks a lot!

Václav

[former_member188883]

Hi Vaclav,

Please use following command

1) dbmcli -u control,control -d NWD db_state

2) Check the following logs dbm.prt and krnl.diag . Post relevant error messages.

Regards,

Deepak Kori

[Former Member]

Hi,

unfortunately dbmcli does not work with user control neither:

Logfiles (knl*) are unchanged 😞

Regards

Václav