SAP Knowledge Base Article - Preview

1684452 - Cannot start after a crash or system restart: UNKNOWN State

Symptom

After an OS restart or a System crash, the MaxDB/liveCache database does not start anymore. When you try to start it up, you receive an error similar to:

Error! Connection failed to node sap011 for database JDI:
-24700,ERR_DBMSRV_NOSTART: Could not start DBM server.
-24832,ERR_SHMNOTAVAILABLE: Shared memory not available
-24686,ERR_SHMNOCLEANUP: Could not cleanup the DBM server Shared Memory
-24606,ERR_SHMSO: Start address 0x349300010c1d01b8 for linetype 0 out

Or

-24576 DBMSrv   ERR_SHMNOHOUSEKEEPINGLYT: Could not create line layout for HouseKeeping
-24700 DBMSrv   ERR_DBMSRV_NOSTART: Could not start DBM server.
-24724 DBMSrv   ERR_RESLOCK_NO_LOCK: Resource ParamAccess not locked
-24726 DBMSrv   ERR_SHMLINESEXCEEDED: Too many lines of type 2
-24686 DBMSrv   ERR_SHMNOCLEANUP: Could not cleanup the DBM server Shared Memory

Or in log file 'dbmsrv_<server_name>.prt':

ERR     -24576 DBMSrv   ERR_SHMNOHOUSEKEEPINGLYT: Could not create line layout for HouseKeeping
ERR     -24700 DBMSrv   ERR_DBMSRV_NOSTART: Could not start DBM server.
ERR     -24724 DBMSrv   ERR_RESLOCK_NO_LOCK: Resource ParamAccess not locked
ERR     -24726 DBMSrv   ERR_SHMLINESEXCEEDED: Too many lines of type 2
ERR     -24686 DBMSrv   ERR_SHMNOCLEANUP: Could not cleanup the DBM server Shared Memory

Or

If you try to query database status with command:

  •    dbmcli -d <your_db_sid> -u <Your_dbm_usr>,<Your_dbm_pwd> db_state

Database status appears as 'UNKNOWN'.

Or it can't even connect to the database instance while it is still running:

Error! Connection failed to node (local) for database LCA:
Connection broken to PID 2336 (D)

 

Or the number of 'dbmsrv' processes is reported as invalid/corrupted when you try to stablish a 'dbmcli' session or execute a 'dbmcli' command:

DBM Server exits!
-24524,ERR_INVALID_NUMBER_OF_REGISTERED_DBMSERVERS: The number of registered dbm server processes is corrupt (-235012096)
Error! Connection failed to node (local) for database SDB:
Connection broken to PID 6068 (D)

 

 


Read more...

Environment

OS Platforms:

  • Windows Platforms (2003, 2008, etc..)
  • Unix (AIX, HP-UX, SOLARIS, etc..)
  • Linux(SuSe, RedHat, etc..)

Database Versions

  • 7.5(both 32 and 64bit)
  • 7.6(both 32 and 64bit)
  • 7.7(both 32 and 64bit)
  • 7.8(both 32 and 64bit)
  • 7.9(both 32 and 64bit)

Keywords

runtime, maxdb, livecache, startup, crash, restart, ERR_SHMNOTAVAILABLE, ERR_DBMSRV_NOSTART, ERR_SHMNOCLEANUP, ERR_SHMSO, dbm_server, connection_broken, operating_system, start, shared_memory, Live_Cache, server, hang, standstill, connection, , KBA , BC-DB-SDB , MaxDB , BC-DB-LVC , liveCache , BC-DB-LCA , liveCache Applications , BW-SYS-DB-SDB , BW MaxDB , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.