Skip to end of metadata
Go to start of metadata

This page should help you to analyze connection problems from the SAP system to an SAP MaxDB database or SAP liveCache.

  1. What always needs to be checked first
  2. Carry out transaction DB59
  3. Carry out transaction SM59 and find all traces
  4. Carry out checks from the command line or using transaction SM49
  5. Check dbmrfc and sapdbmrfc manually
  6. Check/delete DBMRfc connection in transaction SMGW
  7. Check the content of the PATH and LD_LIBRARY_PATH variables
  8. Check the libraries
  9. Check the files

1. What always needs to be checked first

If you encounter connection problems in transaction DB59, DBACOCKPIT, DB50 or LC10 you should start with checking the following SAP notes:

  • 382312 CCMS für SAP-System mit SAP DB >= 7.2 (7.2,..., 7.8)
    This note describes the prerequisites to be fulfilled by SAP NetWeaver for operating the specified database version
  • 588515  Authorizations for database access iin the SAP MaxDB/liveCache CCMS
    This note describes how to define authorization data for a successful communication
  • See also: Connect ProblemsSAP MaxDB Network Guide

back to top

2. Carry out transaction DB59

Carry out transaction DB59 to check which kind of problem the system has: 
Select the affected SAP MaxDB connection, press the "Connection Test"  button, select the database computer for test, and press  "Connection Test" button again.
You can check the results using the "Log" button.

Typically, there are three possible sources of error:

1) DBM Error -24000 ... -24999 - There is a DBM Server error but no DBMRfc problem.

Name and Server     : WDF - SWBWFDDB                 
DBMRFC Function     : DBM_EXECUTE                        
Command                 :  sql_connect control,control     
Error                         : DBM Error                          
Return Code             :     -24988                         
Error Message          : ERR_SQL: SQL error  -4008,Unknown user name/password combination                                   

If you need to analyze such an error, please proceed with the command line check

2) DBM Error -1 ... -100 - There is a DBM Client error, it might also be a DBMRfc problem or a problem with other DBM Clients, like DBMCLI.

Name and Server   : UTT - wielap03
Command               : db_state
Error                      : DBM Error
Return Code          : -16
Error Message       : command timeout exceeded

If you need to analyze such an error, please proceed with the SM59 check and afterwards with the command line check

3) System/Communication Error - There is a DBMRfc communication problem.

Name and Server  : DXI - dbdxi13
Command              : db_state
Error                      : System Error
Error Message       : timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456#Timeout during connection setup

If you need to analyze such an error, please proceed with the SM59 check

back to top

3. Use transaction SM59 to create RFC trace and find another relevant traces

Check now the TCP/IP connections using transaction SM59. The destination SAPDB_DBM is used for DBMRfc in the "command mode" . SAPDB_DBM_DAEMON is used in the "session mode" DBMRfc. For SAPDB_DBM, activate the check box "Set RFC Trace" on the "Special Options"  tab.
Turn on the RFC Trace for SAPDB_DBM_DAEMON using transaction DB59.
Then check all trace files using transaction AL11 in the SAP working directory DIR_HOME.

Files of interest are:

  • dbmrfc.trc Trace of DBMRfc
  • dev_sapdbmrfc Trace of sapdbmrfc
  • dev_rd
  • dev_rfc<n>
  • rfc<pid>*.trc
  • CPICTRC<pid>
  • dev_* files of the corresponding work processes

(warning)   Please note:
<pid> is the DBMRfc process ID mentioned in the column TID in the dbmrfc.trc file.

Proceed with the dbmrfc manually check.

back to top

4. Carry out checks from the command line or using transaction SM49

Execute the following commands. They can be run from the command line or using transaction SM49.

Check Database Manager CLI (DBMCLI) manually from simple to more complex:

  • Can the DBM Server be reached?
    dbmcli [-n <database_computer>] dbm_version

If this fails, check the software installation as described in SAP note 546737, and check the DBM Server log files dbmsrv_*.prt in the <IndepDataPath>/wrk directory.

  • Can the database be reached?
    dbmcli [-n <database_computer>] -d <database_name> dbm_version

If this fails, check the database log files like KnlMsg and KnlMsgArchive.

  • Is there valid logon data?
    dbmcli [-n <database_computer>] -d <database_name> -u <DBM_operator>,<password> dbm_version

If this fails, find out the correct logon data and change the integration data as described in SAP note 588515

  • Does the "central authorization" ("tp feature") work?
    dbmcli -tpp dummy -tpi <sysid> -tpc <connid> -d <database_name> db_state
    e.g. dbmcli -tpp dummy -tpi P01 -tpc P01 -d P01 db_state

If this fails, check tp as described in SAP MaxDB CCMS - Background Information → Problems with TP. When the TP problem is fixed, please rerun this check.

(warning)   Please note:
Use the same operating system user as the application server process. On Windows, you cannot log on as the SAPService<SID> user. Therefore, use transaction SM49.

(warning)   Please note:
To display the independent data path for SAP MaxDB, use the DBMCLI command dbm_getpath IndepDataPath

Proceed with the variables check

back to top

5. Check dbmrfc and sapdbmrfc manually

Check dbmrfc and sapdbmrfc by starting "session mode" DBMRfc manually, possibly also activating trace:

dbmrfc -a dbmrfc@sapdb -g <node> -x sapgw<sysno> [-t]
sapdbmrfc -a dbmrfc@sapdb -g <node> -x sapgw<sysno> [-t]




<ID> Program ID, see the DM59 transaction destination SAPDB_DBM_DAEMON

-g <node>

node of the gateway service

-x sysgw<sysno>

name of the gateway service with system number


activates the DBMRfc trace

If the last sapdbmrfc call doesn't return successfully and the command line check and/or SM59 check fail, use transaction DB59 or SMGW to stop the daemon SAPDB_DBM_DAEMON.

Proceed with the SMGW check.

back to top

6. Check/delete DBMRfc connection using transaction SMGW

Check and possibly delete a DBMRfc connection using transaction SMGW Gateway Monitor.

Choose Goto -> Logged on Clients to see the clients, which are registered in the gateway. There must be:

  • only one "session mode" DBMRfc (tp Name: dbmrfc@sapdb, System Typ: Registered Server)
  • several "command mode" DBMRfc (tp Name: dbmrfc, System Typ: External Client).

Each connection can be deleted choosing Goto -> Logged on Clients -> Delete Client.

Proceed with the variables check

back to top

7. Check the content of the PATH and LD_LIBRARY_PATH variables

Check the content of the environment variables in the environment used by the application, DBMRfc, X Server or DBM Server

PATH must comprise the following directories:

  • <indepprogpath>/lib containing the SAP MaxDB libraries
  • containing the executable sapdbmrfc like /usr/sap/<SID>/SYS/exe/ru
  • <indepprogpath>/bin
  • <indepprogpath>/pgm

LD_LIBRARY_PATH must comprise the following directories:

  • <indepprogpath>/lib containing the SAP MaxDB libraries
  • containing the executable sapdbmrfc like /usr/sap/<SID>/SYS/exe/ru

(warning)   Please note:
To display he independent program path for SAP MaxDB, use the dbmcli command dbm_getpath IndepProgPath

Proceed with the libraries check.

back to top

8. Check the libraries

Check possible problems with libraries in the <indepprogpath>/lib directory:

  • wrong version of libraries
  • existence of an old librfc32u.dll in the Windows system32 directory
  • The following libraries are expected in the <indepprogpath>/lib directory:









    Proceed with the files check.

back to top

9. Check the files

Check the relevant files in the file system:

On Unix check whether the central SAP MaxDB configuration file /etc/opt/sdb exists.

If not, use SDBUPD to install the Base package of the same or a higher database version.

On Windows, check the entries in the following two files:

  • %WINDOWS%\system32\drives\etc\hosts
  • %WINDOWS%\system32\drives\etc\services

If entries are missing in one or both the files, install the higher database version.

back to top

  • No labels