cancel
Showing results for 
Search instead for 
Did you mean: 

Error in DBMSERVER or DBMCLI

Former Member
0 Kudos

Hi Folks,

I am trying to navigate in LC10 and getting the error " Error in DBMSERVER or DBMCLI" during version determination this error is comming

We are getting "Communication error, CPIC return code 020, SAP return code 456" in the SM21.

in DB59 we are getting below mentioned error.

1. Connection Test Using "dbmcli db_state" Unsuccessful

dbmcli_command_execute_error

Can't exec external program (No such file or directory)

WaitForSingleObject failedwith %d (No such device or address)

2. Connection Test Using Command Mode "dbmrfc db_state" Unsuccessful

system_failure

Name and Server : LCI - dellesu

DBMRFC Function : DBM_EXECUTE

Command : db_state

Error : System Error

Error message :

3. Connection Test Using Session Mode "dbmrfc db_state" Unsuccessful

communication_failure

Name and Server : LCI - dellesu

DBMRFC Function : DBM_CONNECT

Error : Communication Error

Error message : program dbmrfc@sapdb not registered / CPIC-CALL: 'ThSAPECMINIT'#Transaction program not registered

4. Connection Test Using "native SQL" ( LCA ) Unsuccessful

For more detailed information, see the developer trace for the work process: 5

We are using SCM 4.0 . Apps server and livecache all are on single windows based box.

Answers wud be rewarded!!!!!!!!

Akshay Shail

Accepted Solutions (0)

Answers (2)

Answers (2)

roland_mallmann
Advisor
Advisor
0 Kudos

Hi,

if you're using liveCache (and thus SCM), then it's very likely you're an official SAP customer: I'd suggest to open an OSS message (if not already done).

Regarding your issue, please check if you can see the SAPDB_DBM and SAPDB_DBM_DAEMON are existant in transaction SM59 (under TCP/IP connections) and check to see if they work.

Additionally, is the liveCache Client software installed on the machine on which you're trying to connect to the liveCache? Can you issue DBMCLI commands (like 'dbmcli db_enum') on the commandline on that machine?

Regards,

Roland

Former Member
0 Kudos

HI,

Can you let me know where can we find DBM and KNLDIAG files.

I am unable to find can you specify the exact location.

Regards,

Mag.

Former Member
0 Kudos

HI Roland,

SAP runs on windows and MS-SQL.

Former Member
0 Kudos

HI,

I am facing with the same issue.

Can you let me know the solution.

Regards,

Mag.

Former Member
0 Kudos

Please fo to the SCM system and use the following reports through SE 38

RSLVCSTART To start

RSLVCSTOP to stop

Below links might Help:

http://help.sap.com/saphelp_nw70/helpdata/en/95/379f3cad1e3251e10000000a114084/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/72/65a93c35ce9e0ee10000000a11405a/content.htm

Former Member
0 Kudos

Hi Folks,

In my case as I was not able to run any DBMCLI command from OS level then I found that program file under the SAPDB folder was missing.

Check at OS level that Xserver service is running or not. If it's not running then try to restart it from the OS level by using " Xserver_start" command. To check all the DBMCLI command from command prompt check the DBMCLI help.

Please let me know in case of any issue.

Regards,

Akshay Shail

former_member229109
Active Contributor
0 Kudos

Hello Akshay,

-> Did you already open the OSS message, where this issue was reported?

-> If the liveCache & application running on the different servers, please

check/install the liveCache client software on the application server for

the livecache applications to be able to communicate to the liveCache on

your system.

Please follow the SAP note :: 649814 Updating MaxDB/liveCache client software

to install the liveCache software on the application server.

For additional information please review the SAP note::

822239 FAQ: MaxDB Interfaces

Thank you and best regards, Natalia Khlopina

PS to Mag:

The database log files & dbm* protocols are located in the database RUNDIRECTORY on the database server. The RUNDIRECTORY is the database parameter.

You could use the database tool xinstinfo, for example, to display the information::

xinstinfo <DB-name>

=> you will see in the output the settings for

IndepData : …

IndepPrograms : …

InstallationPath : ...

Rundirectory : …