database will not started

[Former Member]

After a server crash i will restart the database, but i become following error:

dbmcli -d sm1 -u control,control

ERR -11608 COMMUNIC sql03_request: wrong connection state, state is 'requested'

Error! Connection failed to node (local) for database sm1:

Reading header from pipe:closed by serve

output of the command sdbregview -l

sapsm1:sm1adm 53> sdbregview -l

DB Analyzer         /sapdb/programs    7.7.07.41     64 bit    valid

Server Utilities    /sapdb/programs    7.7.07.41     64 bit    valid

PCR 7300            /sapdb/programs    7.3.00.60               valid

PCR 7301            /sapdb/programs    7.3.01.22               valid

PCR 7500            /sapdb/programs    7.5.00.52     64 bit    valid

SAP Utilities       /sapdb/programs    7.7.07.41     64 bit    valid

Base                /sapdb/programs    7.7.07.41     64 bit    valid

Redist Python       /sapdb/programs    7.7.07.41     64 bit    valid

JDBC                /sapdb/programs    7.6.06.05               valid

Messages            /sapdb/programs    MSG 0.8507              valid

ODBC                /sapdb/programs    7.7.07.41     64 bit    valid

SQLDBC 77           /sapdb/programs    7.7.07.41     64 bit    valid

Database Kernel     /sapdb/SM1/db      7.7.07.41     64 bit    valid

Loader              /sapdb/programs    7.7.07.41     64 bit    valid

SQLDBC              /sapdb/programs    7.7.07.41     64 bit    valid

Fastload API        /sapdb/programs    7.7.07.41     64 bit    valid

SQLDBC 76           /sapdb/programs    7.6.06.22     64 bit    valid

sapsm1:sm1adm 54>

What can i do ?

[Former Member · Accepted solution]

Hi Yashwanth,

thanks for your great help. After rename the both files dbm.shi and dbm.shi the

database worked again. The problem is solved.

Regards

Volker

[yashwanthkumar_kethineed · Accepted solution]

Hi Volker,

Glad, that your problem is solved. If you have no further questions, change the status of this question to answerd. Have a nice day.

Regards,

Yashwanth

[yashwanthkumar_kethineed]

Hello Voker,

Most likely this issue happens when the system is abnormally shutdown/restarted or after a Crash(due to power outage, for example) while the database is running.

MaxDB uses the OS file system to keep some shared files for the MaxDB internal communications. If the database is in ONLINE state and a OS restart is not properly done, the MaxDB cannot perform a 'clean' shutdown so these runtime files are not removed from the OS file system, causing the old runtime to be present at the new database startup.

Please do the following and let me know if the issue is resolved.

1. At OS level(process list), check whether there are any MaxDB/LiveCache (dbmsrv) processes still running. If any process is found, terminate it.
2. Locate the Runtime files at the File system. These files are named as <name of instance>*.dbm.shi & <name of instance>*.dbm.shm and are located under '/sapdb', /sapdb/data/wrk folders and '/var/lib/sdb/dbm/ipc(this last folder are only valid for UNIX and Linux systems
3. Rename(do not remove) the files. I.e: <SID>.dbm.shi_old, <SID>.dbm.shm_old.
4. Try to start up the database: dbmcli -d <your_db_sid> -u <your_dbm_user>,<your_dbm_pwd> db_online.
5. If everything is ok at the startup the previous command should return an OK as result.
6. You can confirm whether the database is ONLINE by issuing the command: dbmcli -d <your_db_sid> -u <your_dbm_user>,<your_dbm_pwd> db_state.

This should return ONLINE then.

Regards,

Yashwanth

[Former Member]

Dear Yashwanth,

Please tell me path for windows 7, i am not able to find these files, I have same issue. Please help me.

Thanks & Regards,

Manish Sharma

[yashwanthkumar_kethineed]

Hello Manish,

In windows envronment these files are under /sapdb/data/wrk for maxdb 7.7 or lower. For maxdb 7.8 or higher you can find them under /sapdb/<sid>/data/wrk.

[Former Member]

Hi Ratnajit,

thanks for your answer. The x_server was started.
but when i started the dbmcli command, i become the same error.


Best regards
  Volker

[former_member189725]

Did you check if the x_server is started properly ?

If required , restart the x_server

x_server stop

x_server start

Regards

Ratnajit