Problem in connection between SCM 5.0 and LiveCache(Both on different Host)

[Former Member]

Hi,

I am facing a problem while establishing connection between Live Cache and SCM server.

Landscape:

HOST A:

SCM 5.0 IDES

Windows 2003 32 BIT (AMD architecture)

HOST B:

LiveCache 7.6.03.08

Windows 2003 64 BIT. (Intel architecture)

As livecache is not supported on 32 bit platform (SCM 5.0 Host A) I had to install, Livecache on other 64 Bit Server. (Host B)

After, Livecache Installation I have maintained setting in LC10 à Integration.

When I click LC10 à Livecache Monitoring, it takes lot of time and then error occurs in establishing RFC connection.

Also, connection test in DB59 is not successful.

In SM59,for TCP connection SAPDB_DBM connection test gives following error,

Logon Cancel

Error Details timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456 Timeout dur

Error Details ERROR: timeout during allocate

Error Details LOCATION: SAP-Gateway on host sapserver / sapgw02

Error Details DETAIL: no connect of TP sapdbmrfc from host sapserver after 20 sec

Error Details COMPONENT: SAP-Gateway

Error Details COUNTER: 153

Error Details MODULE: gwr3cpic.c

Error Details LINE: 5873

Error Details RETURN CODE: 242

Error Details SUBRC: 0

Error Details RELEASE: 700

Error Details TIME: Wed Jun 18 20:13:10 2008

Error Details VERSION: 2

Please reply at earliest.

Thanks,

Nirav Shah

Edited by: Nirav Shah on Jun 18, 2008 4:50 PM

[markus_doehr2]

> In SM59,for TCP connection SAPDB_DBM connection test gives following error,

> Logon Cancel

> Error Details timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456 Timeout dur

> Error Details ERROR: timeout during allocate

> Error Details LOCATION: SAP-Gateway on host sapserver / sapgw02

> Error Details DETAIL: no connect of TP sapdbmrfc from host sapserver after 20 sec

> Error Details COMPONENT: SAP-Gateway

> Error Details COUNTER: 153

> Error Details MODULE: gwr3cpic.c

> Error Details LINE: 5873

> Error Details RETURN CODE: 242

> Error Details SUBRC: 0

> Error Details RELEASE: 700

> Error Details TIME: Wed Jun 18 20:13:10 2008

> Error Details VERSION: 2

Is the host "sapserver" the machine running the LiveCache? If yes, can ping the machine from the SCM server by name?

You may also check

Note 1128989 - "command timeout exceeded" bei DBMRFC Session Mode

Markus

[Former Member]

Thanks for your reply.

sapserver is not Livecache server. It is SCM server.

Livecache is on different host.

I have checked note 1128989.

Livecache client version is 7.6.3.0. Also, workaround mentioned in note is not working.

Also, I can ping SCM server from Livecache server both by hostname and IP. Same is possible from SCM server to Livecache

Still same error persists.

Please share your views.

- Nirav

Edited by: Nirav Shah on Jun 18, 2008 5:48 PM

[markus_doehr2]

Please check DB59 and execute the test there - what's the output?

Markus

[former_member229109]

Hello Nirav,

-> Please review the SAP notes ::

822239 FAQ: MaxDB Interfaces

649814 Updating MaxDB/SAP DB/liveCache client software

-> From the given information it's looking that the liveCache client software was not installed or was not updated on the host A.

-> Please provide additional information ::

HOST A: SCM 5.0 IDES

Windows 2003 32 BIT (AMD architecture)

a) What is the version of the SAP kernel on your system?

b) What is the version of the liveCache client installed on the host A?

Run transaction /nsm49 -> using the dbmcli tool run '-s dbm_version' -> update with results.

Run transaction /nsm49 -> using the dbmrfc -> execute -> update with results.

Logon to the host A as <SCM-SID>adm user & run the following commands :

sdbregview -l

xinstinfo

dbmcli -s dbm_getpath IndepProgPath

-> As SAP customer you have option to create the SAP ticket,

we could logon to your system , check the issue & help you with the solution.

Thank you and best regards, Natalia Khlopina

Edited by: Natalia Khlopina on Jun 18, 2008 2:34 PM

[Former Member]

Hello,

Thanks for your reply. Below are the output of your mentioned commands :

======================================================

a) What is the version of the SAP kernel on your system?

SAP Kernel : 700_REL

Kernel Patch number : 111

Unicode System

======================================================

b) What is the version of the liveCache client installed on the host A?

7.6.3.0 (I have installed Livecache client using ERP 2007 SR3 master CD)

======================================================

c)Run transaction /nsm49 -> using the dbmcli tool run '-s dbm_version' -> update with results.

Can't find Installation! (use "dbmcli -s -R <instroot> inst_reg [-c]" to avoid this message) OK VERSION = 7.6.03 BUILD = DBMServer 7.6.03 Build 008-123-159-187 OS = WIN32 INSTROOT = LOGON = True CODE = ASCII SWAP = full UNICODE = (unknown) INSTANCE = (unknown) SYSNAME = Windows Server 2003 family

======================================================

Run transaction /nsm49 -> using the dbmrfc -> execute -> update with results.

Gives no output.

======================================================

Logon to the host A as <SCM-SID>adm user & run the following commands :

sdbregview u2013l

C:\Documents and Settings\scmadm>sdbregview -l

SAP Utilities d:/sapdb/programs 7.6.03.08 32 bit valid

PCR 7300 d:/sapdb/programs 7.3.00.59 valid

Redist Python d:/sapdb/programs 7.6.03.08 32 bit valid

Base d:/sapdb/programs 7.6.03.08 32 bit valid

PCR 7301 d:/sapdb/programs 7.3.01.21 valid

JDBC d:/sapdb/programs 7.6.03.03 valid

Messages d:/sapdb/programs MSG 0.5603 valid

PCR 7500 d:/sapdb/programs 7.5.00.46 32 bit valid

ODBC d:/sapdb/programs 7.6.03.08 32 bit valid

Loader d:/sapdb/programs 7.6.03.08 32 bit valid

PCR 7104 d:/sapdb/programs 7.1.04.45 valid

SQLDBC d:/sapdb/programs 7.6.03.08 32 bit valid

SQLDBC 76 d:/sapdb/programs 7.6.03.08 32 bit valid

Fastload API d:/sapdb/programs 7.6.03.08 32 bit valid

PCR 7403 d:/sapdb/programs 7.4.03.49 32 bit valid

======================================================

dbmcli -s dbm_getpath IndepProgPath

Warning! Can't find Installation!

(use "dbmcli -s -R <instroot> inst_reg [-c]" to avoid this message)

OK

D:\sapdb\programs

======================================================

Also, Below is output of LCA connection test using DB59

General Connection Data

Connection Name....: LCA

Database Name......: LCA

Database Server....: 192.168.10.8

tp Profiles........: no_longer_used

DBM User...........: CONTROL

-

---

Test Scope

1. Execute an external operating system command (DBMCLI)

2. Determine status using TCP/IP connection SAPDB_DBM (DBMRFC command mode)

3. Determine status using TCP/IP connection SAPDB_DBM_DAEMON (DBMRFC session mode)

4. Test the SQL connection (Native SQL at CON_NAME)

-

---

Application Server: sapserver_SCM_02 ( Windows NT )

1. Connect. test with "dbmcli db_state" Successful

2. Connect. test with command mode "dbmrfc db_state" Unsuccessful

system_failure

Name and Server : LCA - 192.168.10.8

DBMRFC Function : DBM_EXECUTE

Command : db_state

Error : System Error

Error Message : timeout during allocate / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456

Timeout during connection setup

3. Connect. test with session mode "dbmrfc db_state" Unsuccessful

communication_failure

Name and Server : LCA - 192.168.10.8

DBMRFC Function : DBM_CONNECT

Error : Communication Error

Error Message : Error when opening an RFC connection

4. Connect. test with "native SQL" ( LCA ) Successful

======================================================

Please have a look and suggest.

Regards,

Nirav

[former_member229109]

Hello Nirav,

1) Did you already created the SAP ticket, there this problem was reported?

2)

A) Please delete the SAPDB_DBM & SAPDB_DBM_DAEMON connections in /ndb59.

Run the /nlc10 transaction, those connections will be recreated. Test the

SAPDB_DBM & SAPDB_DBM_DAEMON connections in /ndb59 after that.

B) If the test is failed, please check the errors in the logs in /nst11.

C) Activate the "set RFC Trace" checkbox at the "Special Options" in

/nsm59, destination SAPDB_DBM. Save. After that run "Connection Test".

And deactivate the "set RFC Trace" checkbox for destination SAPDB_DBM. Save.

Run /nst11 & sort descending by date and time; check the dbmrfc.trc, dev_sapdbmrfc and

another files created/changed during your test.

If you already created the ticket, I would like to logon and check those files.

Thank you and best regards, Natalia Khlopina

[Former Member]

Hi,

upgrade kernel patch on SCM system.

regards,

kaushal

[Former Member]

Hi Natalia,

Thanks for your suggestions.

I have deleted RFC destination from SM59 and then recreated them executing LC10.

Still same error persists. Below are files you suggested,

1) dev_sapdbmrfc

=============================================================

20.06.2008 RSTR0006: Display Developer Traces 1

-

---

--- sapdbmrfc (pid: 9808) : sapdbmrfc parameters:

sapdbmrfc -adbmrfc@sapdb -gsapserver -xsapgw02 -t

--- sapdbmrfc (pid: 9808) : environment:

--- sapdbmrfc (pid: 9808) : ComSpec=C:\WINDOWS\system32\cmd.exe

--- sapdbmrfc (pid: 9808) : DBMS_TYPE=ora

--- sapdbmrfc (pid: 9808) : dbs_ora_schema=SAPSR3

--- sapdbmrfc (pid: 9808) : dbs_ora_tnsname=SCM

--- sapdbmrfc (pid: 9808) : NLS_LANG=AMERICAN_AMERICA.UTF8

--- sapdbmrfc (pid: 9808) : NUMBER_OF_PROCESSORS=1

--- sapdbmrfc (pid: 9808) : ORACLE_HOME=D:\oracle\product\10.2.0\db_1

--- sapdbmrfc (pid: 9808) : ORACLE_SID=SCM

--- sapdbmrfc (pid: 9808) : OS=Windows_NT

--- sapdbmrfc (pid: 9808) : Path=D:\usr\sap\SCM\DVEBMGS02\exe;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32\wbem;C:\j2sdk1.4.2

--- sapdbmrfc (pid: 9808) : PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH

--- sapdbmrfc (pid: 9808) : PERL5LIB=D:\oracle\product\10.2.0\db_1\perl\5.8.3\lib\MSWin32-x86;D:\oracle\product\10.2.0\db_1\perl\5.8.3\lib;D:\oracle\product\10.2.0\db_1\perl\5.8.

--- sapdbmrfc (pid: 9808) : PPID=2852

--- sapdbmrfc (pid: 9808) : PROCESSOR_ARCHITECTURE=x86

--- sapdbmrfc (pid: 9808) : PROCESSOR_IDENTIFIER=x86 Family 15 Model 95 Stepping 2, AuthenticAMD

--- sapdbmrfc (pid: 9808) : PROCESSOR_LEVEL=15

--- sapdbmrfc (pid: 9808) : PROCESSOR_REVISION=5f02

--- sapdbmrfc (pid: 9808) : SAPDATA_HOME=D:\oracle\SCM

--- sapdbmrfc (pid: 9808) : SAPEXE=D:\usr\sap\SCM\SYS\exe\uc\NTI386

--- sapdbmrfc (pid: 9808) : SAPLOCALHOST=sapserver

--- sapdbmrfc (pid: 9808) : SAPSYSTEMNAME=SCM

--- sapdbmrfc (pid: 9808) : SECUDIR=D:\usr\sap\SCM\DVEBMGS02\sec

--- sapdbmrfc (pid: 9808) : SystemDrive=C:

--- sapdbmrfc (pid: 9808) : SystemRoot=C:\WINDOWS

--- sapdbmrfc (pid: 9808) : TEMP=C:\WINDOWS\TEMP

--- sapdbmrfc (pid: 9808) : TMP=C:\WINDOWS\TEMP

--- sapdbmrfc (pid: 9808) : TNS_ADMIN=D:\usr\sap\SCM\SYS\profile\oracle

--- sapdbmrfc (pid: 9808) : windir=C:\WINDOWS

--- sapdbmrfc (pid: 9808) : end environment:

--- sapdbmrfc (pid: 9808) : getenv (PATH) = D:\usr\sap\SCM\DVEBMGS02\exe;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32\wbem;C:

--- sapdbmrfc (pid: 9808) : dbmcli -s dbm_getpath IndepProgPath)

--- sapdbmrfc (pid: 9808) : DBMCLI OUTPUT

--- sapdbmrfc (pid: 9808) : Warning! Can't find Installation!

--- sapdbmrfc (pid: 9808) : (use "dbmcli -s -R <instroot> inst_reg [-c]" to avoid this message)

--- sapdbmrfc (pid: 9808) : OK

--- sapdbmrfc (pid: 9808) : d:\sapdb\programs

--- sapdbmrfc (pid: 9808) : putenv (PATH) = PATH=d:\sapdb\programs\lib;D:\usr\sap\SCM\DVEBMGS02\exe;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;D:\oracle\product\10.2.0\db_1\bin;

--- sapdbmrfc (pid: 9808) : dbmrfc call parameters:

d:\sapdb\programs\bin\dbmrfc.exe -adbmrfc@sapdb -gsapserver -xsapgw02 -t

--- sapdbmrfc (pid: 6344) : sapdbmrfc parameters:

D:\usr\sap\SCM\DVEBMGS02\exe/sapdbmrfc sapserver sapgw02 94925328 CPIC_TRACE=2 IDX=0

--- sapdbmrfc (pid: 6344) : environment:

--- sapdbmrfc (pid: 6344) : ClusterLog=C:\WINDOWS\Cluster\cluster.log

--- sapdbmrfc (pid: 6344) : ComSpec=C:\WINDOWS\system32\cmd.exe

--- sapdbmrfc (pid: 6344) : DBMS_TYPE=ora

--- sapdbmrfc (pid: 6344) : dbs_ora_schema=SAPSR3

--- sapdbmrfc (pid: 6344) : dbs_ora_tnsname=SCM

--- sapdbmrfc (pid: 6344) : NLS_LANG=AMERICAN_AMERICA.UTF8

--- sapdbmrfc (pid: 6344) : NUMBER_OF_PROCESSORS=1

--- sapdbmrfc (pid: 6344) : ORACLE_HOME=D:\oracle\product\10.2.0\db_1

--- sapdbmrfc (pid: 6344) : ORACLE_SID=SCM

--- sapdbmrfc (pid: 6344) : OS=Windows_NT

--- sapdbmrfc (pid: 6344) : Path=D:\usr\sap\SCM\DVEBMGS02\exe;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32\wbem;C:\j2sdk1.4.2

--- sapdbmrfc (pid: 6344) : PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH

--- sapdbmrfc (pid: 6344) : PERL5LIB=D:\oracle\product\10.2.0\db_1\perl\5.8.3\lib\MSWin32-x86;D:\oracle\product\10.2.0\db_1\perl\5.8.3\lib;D:\oracle\product\10.2.0\db_1\perl\5.8.

--- sapdbmrfc (pid: 6344) : PPID=2832

--- sapdbmrfc (pid: 6344) : PROCESSOR_ARCHITECTURE=x86

--- sapdbmrfc (pid: 6344) : PROCESSOR_IDENTIFIER=x86 Family 15 Model 95 Stepping 2, AuthenticAMD

--- sapdbmrfc (pid: 6344) : PROCESSOR_LEVEL=15

--- sapdbmrfc (pid: 6344) : PROCESSOR_REVISION=5f02

--- sapdbmrfc (pid: 6344) : SAPDATA_HOME=D:\oracle\SCM

--- sapdbmrfc (pid: 6344) : SAPEXE=D:\usr\sap\SCM\SYS\exe\uc\NTI386

--- sapdbmrfc (pid: 6344) : SAPLOCALHOST=sapserver

--- sapdbmrfc (pid: 6344) : SAPSYSTEMNAME=SCM

--- sapdbmrfc (pid: 6344) : SECUDIR=D:\usr\sap\SCM\DVEBMGS02\sec

--- sapdbmrfc (pid: 6344) : SystemDrive=C:

--- sapdbmrfc (pid: 6344) : SystemRoot=C:\WINDOWS

--- sapdbmrfc (pid: 6344) : TEMP=C:\WINDOWS\TEMP

--- sapdbmrfc (pid: 6344) : TMP=C:\WINDOWS\TEMP

--- sapdbmrfc (pid: 6344) : TNS_ADMIN=D:\usr\sap\SCM\SYS\profile\oracle

--- sapdbmrfc (pid: 6344) : windir=C:\WINDOWS

--- sapdbmrfc (pid: 6344) : end environment:

--- sapdbmrfc (pid: 6344) : getenv (PATH) = D:\usr\sap\SCM\DVEBMGS02\exe;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;D:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32\wbem;C:

--- sapdbmrfc (pid: 6344) : dbmcli -s dbm_getpath IndepProgPath)

--- sapdbmrfc (pid: 6344) : DBMCLI OUTPUT

--- sapdbmrfc (pid: 6344) : Warning! Can't find Installation!

--- sapdbmrfc (pid: 6344) : (use "dbmcli -s -R <instroot> inst_reg [-c]" to avoid this message)

--- sapdbmrfc (pid: 6344) : OK

--- sapdbmrfc (pid: 6344) : D:\sapdb\programs

--- sapdbmrfc (pid: 6344) : putenv (PATH) = PATH=D:\sapdb\programs\lib;D:\usr\sap\SCM\DVEBMGS02\exe;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;D:\oracle\product\10.2.0\db_1\bin;

--- sapdbmrfc (pid: 6344) : dbmrfc call parameters:

D:\sapdb\programs\bin\dbmrfc.exe sapserver sapgw02 94925328 CPIC_TRACE=2 IDX=0

=============================================================

2) dbmrfc.trc

=============================================================

Directory: D:\usr\sap\SCM\DVEBMGS02\work

Name: dbmrfc.trc

-

---

-

---

Date Time TID(hex) Typ MsgID Label Message

-

---

2008-05-24 05:48:46 0x000018f0 INF 0 DBMRFC dbmrfc :: main

2008-05-24 05:48:46 0x000018f0 INF 0 DBMRFC d:\sapdb\programs\bin\dbmrfc.exe

2008-05-24 05:48:46 0x000018f0 INF 0 DBMRFC -adbmrfc@sapdb

2008-05-24 05:48:46 0x000018f0 INF 0 DBMRFC -gsapserver

2008-05-24 05:48:46 0x000018f0 INF 0 DBMRFC -xsapgw02

2008-05-24 05:48:46 0x000018f0 INF 0 DBMRFC -t

2008-05-24 05:48:47 0x000018f0 INF 0 DBMRFC cn901DBMRfcServer :: cn901DBMRfcServer

2008-05-24 05:48:47 0x000018f0 INF 0 DBMRFC EXIT cn901DBMRfcServer :: cn901DBMRfcServer

2008-05-24 05:53:20 0x000018f0 INF 0 DBMRFC cn901DBMRfcServer :: DBM_CONNECT

2008-05-24 05:53:20 0x000018f0 INF 0 DBMRFC Import Parameters

2008-05-24 05:53:20 0x000018f0 INF 0 DBMRFC DBNODE 192.168.10.1

2008-05-24 05:53:20 0x000018f0 INF 0 DBMRFC DBNAME LCA

2008-05-24 05:53:20 0x000018f0 INF 0 DBMRFC SYSID SCM

2008-05-24 05:53:20 0x000018f0 INF 0 DBMRFC CONN LCA

2008-05-24 05:53:21 0x000018f0 INF 0 DBMRFC PROFILE no_longer_used

2008-05-24 05:53:21 0x000018f0 INF 0 DBMRFC DBNODE 192.168.10.1

2008-05-24 05:53:22 0x000018f0 INF 0 DBMRFC Export Parameters

2008-05-24 05:53:22 0x000018f0 INF 0 DBMRFC DBMID 0

2008-05-24 05:53:22 0x000018f0 INF 0 DBMRFC SYSRC -4

2008-05-24 05:53:22 0x000018f0 INF 0 DBMRFC ERRTXT XSERVER might be inactive

2008-05-24 05:53:23 0x000018f0 INF 0 DBMRFC End Method DBM_CONNECT

2008-05-24 05:54:27 0x000018f0 INF 0 DBMRFC cn901DBMRfcServer :: DBM_CONNECT

2008-05-24 05:54:27 0x000018f0 INF 0 DBMRFC Import Parameters

2008-05-24 05:54:27 0x000018f0 INF 0 DBMRFC DBNODE 192.168.10.1

2008-05-24 05:54:27 0x000018f0 INF 0 DBMRFC DBNAME LCA

2008-05-24 05:54:28 0x000018f0 INF 0 DBMRFC SYSID SCM

2008-05-24 05:54:28 0x000018f0 INF 0 DBMRFC CONN LCA

2008-05-24 05:54:28 0x000018f0 INF 0 DBMRFC PROFILE no_longer_used

2008-05-24 05:54:28 0x000018f0 INF 0 DBMRFC DBNODE 192.168.10.1

2008-05-24 05:54:30 0x000018f0 INF 0 DBMRFC Export Parameters

2008-05-24 05:54:30 0x000018f0 INF 0 DBMRFC DBMID 0

2008-05-24 05:54:30 0x000018f0 INF 0 DBMRFC SYSRC -4

2008-05-24 05:54:30 0x000018f0 INF 0 DBMRFC ERRTXT XSERVER might be inactive

2008-05-24 05:54:30 0x000018f0 INF 0 DBMRFC End Method DBM_CONNECT

2008-05-24 05:57:36 0x000018f0 INF 0 DBMRFC cn901DBMRfcServer :: DBM_CONNECT

2008-05-24 05:57:36 0x000018f0 INF 0 DBMRFC Import Parameters

2008-05-24 05:57:36 0x000018f0 INF 0 DBMRFC DBNODE 192.168.10.1

2008-05-24 05:57:36 0x000018f0 INF 0 DBMRFC DBNAME LCA

2008-05-24 05:57:36 0x000018f0 INF 0 DBMRFC SYSID SCM

2008-05-24 05:57:36 0x000018f0 INF 0 DBMRFC CONN LCA

2008-05-24 05:57:36 0x000018f0 INF 0 DBMRFC PROFILE no_longer_used

2008-05-24 05:57:36 0x000018f0 INF 0 DBMRFC DBNODE 192.168.10.1

2008-05-24 05:57:38 0x000018f0 INF 0 DBMRFC Export Parameters

2008-05-24 05:57:38 0x000018f0 INF 0 DBMRFC DBMID 0

2008-05-24 05:57:38 0x000018f0 INF 0 DBMRFC SYSRC -4

2008-05-24 05:57:38 0x000018f0 INF 0 DBMRFC ERRTXT XSERVER might be inactive

2008-05-24 05:57:38 0x000018f0 INF 0 DBMRFC End Method DBM_CONNECT

2008-05-24 05:57:49 0x000018f0 INF 0 DBMRFC cn901DBMRfcServer :: DBM_CONNECT

2008-05-24 05:57:49 0x000018f0 INF 0 DBMRFC Import Parameters

2008-05-24 05:57:49 0x000018f0 INF 0 DBMRFC DBNODE 192.168.10.1

2008-05-24 05:57:49 0x000018f0 INF 0 DBMRFC DBNAME LID

2008-05-24 05:57:49 0x000018f0 INF 0 DBMRFC SYSID SCM

2008-05-24 05:57:49 0x000018f0 INF 0 DBMRFC CONN LDA

2008-05-24 05:57:49 0x000018f0 INF 0 DBMRFC PROFILE no_longer_used

2008-05-24 05:57:49 0x000018f0 INF 0 DBMRFC DBNODE 192.168.10.1

2008-05-24 05:57:50 0x000018f0 INF 0 DBMRFC Export Parameters

2008-05-24 05:57:50 0x000018f0 INF 0 DBMRFC DBMID 0

2008-05-24 05:57:50 0x000018f0 INF 0 DBMRFC SYSRC -4

2008-05-24 05:57:50 0x000018f0 INF 0 DBMRFC ERRTXT XSERVER might be inactive

2008-05-24 05:57:50 0x000018f0 INF 0 DBMRFC End Method DBM_CONNECT

2008-05-24 05:58:04 0x000018f0 INF 0 DBMRFC cn901DBMRfcServer :: DBM_CONNECT

2008-05-24 05:58:04 0x000018f0 INF 0 DBMRFC Import Parameters

2008-05-24 05:58:04 0x000018f0 INF 0 DBMRFC DBNODE 192.168.10.1

2008-05-24 05:58:04 0x000018f0 INF 0 DBMRFC DBNAME LID

2008-05-24 05:58:04 0x000018f0 INF 0 DBMRFC SYSID SCM

2008-05-24 05:58:05 0x000018f0 INF 0 DBMRFC CONN LDA

2008-05-24 05:58:05 0x000018f0 INF 0 DBMRFC PROFILE no_longer_used

2008-05-24 05:58:05 0x000018f0 INF 0 DBMRFC DBNODE 192.168.10.1

2008-05-24 05:58:06 0x000018f0 INF 0 DBMRFC Export Parameters

2008-05-24 05:58:06 0x000018f0 INF 0 DBMRFC DBMID 0

2008-05-24 05:58:06 0x000018f0 INF 0 DBMRFC SYSRC -4

2008-05-24 05:58:06 0x000018f0 INF 0 DBMRFC ERRTXT XSERVER might be inactive

2008-05-24 05:58:06 0x000018f0 INF 0 DBMRFC End Method DBM_CONNECT

2008-05-24 06:01:10 0x000018f0 INF 0 DBMRFC cn901DBMRfcServer :: DBM_CONNECT

2008-05-24 06:01:10 0x000018f0 INF 0 DBMRFC Import Parameters

2008-05-24 06:01:10 0x000018f0 INF 0 DBMRFC DBNODE 192.168.10.1

2008-05-24 06:01:10 0x000018f0 INF 0 DBMRFC DBNAME LID

2008-05-24 06:01:10 0x000018f0 INF 0 DBMRFC SYSID SCM

2008-05-24 06:01:10 0x000018f0 INF 0 DBMRFC CONN LDA

2008-05-24 06:01:10 0x000018f0 INF 0 DBMRFC PROFILE no_longer_used

2008-05-24 06:01:10 0x000018f0 INF 0 DBMRFC DBNODE 192.168.10.1

2008-05-24 06:01:11 0x000018f0 INF 0 DBMRFC Export Parameters

2008-05-24 06:01:11 0x000018f0 INF 0 DBMRFC DBMID 0

2008-05-24 06:01:11 0x000018f0 INF 0 DBMRFC SYSRC -4

2008-05-24 06:01:11 0x000018f0 INF 0 DBMRFC ERRTXT XSERVER might be inactive

2008-05-24 06:01:11 0x000018f0 INF 0 DBMRFC End Method DBM_CONNECT

2008-05-24 06:03:26 0x000018f0 INF 0 DBMRFC cn901DBMRfcServer :: DBM_CONNECT

2008-05-24 06:03:26 0x000018f0 INF 0 DBMRFC Import Parameters

2008-05-24 06:03:26 0x000018f0 INF 0 DBMRFC DBNODE sapserver

2008-05-24 06:03:26 0x000018f0 INF 0 DBMRFC DBNAME LID

2008-05-24 06:03:26 0x000018f0 INF 0 DBMRFC SYSID SCM

2008-05-24 06:03:26 0x000018f0 INF 0 DBMRFC CONN LEA

2008-05-24 06:03:26 0x000018f0 INF 0 DBMRFC PROFILE no_longer_used

2008-05-24 06:03:26 0x000018f0 INF 0 DBMRFC DBNODE sapserver

2008-05-24 06:03:26 0x000018f0 INF 0 DBMRFC Export Parameters

2008-05-24 06:03:26 0x000018f0 INF 0 DBMRFC DBMID 0

2008-05-24 06:03:26 0x000018f0 INF 0 DBMRFC SYSRC -4

2008-05-24 06:03:26 0x000018f0 INF 0 DBMRFC ERRTXT database instance not found

2008-05-24 06:03:26 0x000018f0 INF 0 DBMRFC End Method DBM_CONNECT

2008-05-24 06:10:20 0x000018f0 INF 0 DBMRFC cn901DBMRfcServer :: DBM_CONNECT

2008-05-24 06:10:20 0x000018f0 INF 0 DBMRFC Import Parameters

2008-05-24 06:10:20 0x000018f0 INF 0 DBMRFC DBNODE 192.168.10.1

2008-05-24 06:10:20 0x000018f0 INF 0 DBMRFC DBNAME LCA

2008-05-24 06:10:20 0x000018f0 INF 0 DBMRFC SYSID SCM

2008-05-24 06:10:20 0x000018f0 INF 0 DBMRFC CONN LCA

2008-05-24 06:10:20 0x000018f0 INF 0 DBMRFC PROFILE no_longer_used

2008-05-24 06:10:20 0x000018f0 INF 0 DBMRFC DBNODE 192.168.10.1

2008-05-24 06:10:22 0x000018f0 INF 0 DBMRFC Export Parameters

2008-05-24 06:10:22 0x000018f0 INF 0 DBMRFC DBMID 0

2008-05-24 06:10:22 0x000018f0 INF 0 DBMRFC SYSRC -4

2008-05-24 06:10:22 0x000018f0 INF 0 DBMRFC ERRTXT XSERVER might be inactive

2008-05-24 06:10:22 0x000018f0 INF 0 DBMRFC End Method DBM_CONNECT

2008-05-24 06:10:34 0x000018f0 INF 0 DBMRFC cn901DBMRfcServer :: DBM_CONNECT

2008-05-24 06:10:34 0x000018f0 INF 0 DBMRFC Import Parameters

2008-05-24 06:10:34 0x000018f0 INF 0 DBMRFC DBNODE 192.168.10.1

2008-05-24 06:10:34 0x000018f0 INF 0 DBMRFC DBNAME LCA

2008-05-24 06:10:34 0x000018f0 INF 0 DBMRFC SYSID SCM

2008-05-24 06:10:34 0x000018f0 INF 0 DBMRFC CONN LCA

2008-05-24 06:10:34 0x000018f0 INF 0 DBMRFC PROFILE no_longer_used

2008-05-24 06:10:34 0x000018f0 INF 0 DBMRFC DBNODE 192.168.10.1

2008-05-24 06:10:35 0x000018f0 INF 0 DBMRFC Export Parameters

2008-05-24 06:10:35 0x000018f0 INF 0 DBMRFC DBMID 0

2008-05-24 06:10:35 0x000018f0 INF 0 DBMRFC SYSRC -4

2008-05-24 06:10:35 0x000018f0 INF 0 DBMRFC ERRTXT XSERVER might be inactive

2008-05-24 06:10:35 0x000018f0 INF 0 DBMRFC End Method DBM_CONNECT

2008-05-24 06:55:38 0x000018f0 INF 0 DBMRFC cn901DBMRfcServer :: ~cn901DBMRfcServer

2008-05-24 06:55:38 0x000018f0 INF 0 DBMRFC EXIT cn901DBMRfcServer :: ~cn901DBMRfcServer

2008-05-24 06:55:38 0x000018f0 INF 0 DBMRFC EXIT dbmrfc :: main

2008-06-20 11:25:43 0x0000186c INF 0 DBMRFC dbmrfc :: main

2008-06-20 11:25:43 0x0000186c INF 0 DBMRFC D:\sapdb\programs\bin\dbmrfc.exe

2008-06-20 11:25:43 0x0000186c INF 0 DBMRFC sapserver

2008-06-20 11:25:43 0x0000186c INF 0 DBMRFC sapgw02

2008-06-20 11:25:43 0x0000186c INF 0 DBMRFC 94925328

2008-06-20 11:25:43 0x0000186c INF 0 DBMRFC CPIC_TRACE=2

2008-06-20 11:25:43 0x0000186c INF 0 DBMRFC IDX=0

2008-06-20 11:25:44 0x0000186c INF 0 DBMRFC DBMCliRfc_DBMRfc :: DBMCliRfc_DBMRfc

2008-06-20 11:25:44 0x0000186c INF 0 DBMRFC EXIT DBMCliRfc_DBMRfc :: DBMCliRfc_DBMRfc

2008-06-20 11:25:44 0x0000186c INF 0 DBMRFC DBMCliRfc_DBMRfc :: ~DBMCliRfc_DBMRfc

2008-06-20 11:25:44 0x0000186c INF 0 DBMRFC EXIT DBMCliRfc_DBMRfc :: ~DBMCliRfc_DBMRfc

2008-06-20 11:25:44 0x0000186c INF 0 DBMRFC EXIT dbmrfc :: main

=============================================================

Please suggest.

Thanks and Regards,

Nirav Shah.

[Former Member]

Hello Experts,

Please let me know your views.

- Nirav Shah.

[Former Member]

Hello Experts,

Please share some pointers towards resolution of problem.

Thanks in advance.

- Nirav.

[Melanie]

Hello Nirav,

I think you shouldn't urge people to answer your questions in the forum. Nobody is working full time on the forum - it's just people who try to help others, whenever time allows it. So please be patient - or open a customer message as this is obviously a problem with an SAP system.

However, in file dbmrfc.trc you can see the message 'XSERVER might be inactive'. Did you start the x_server on the liveCache server? This is the TCP/IP listener and it is necessary for remote connections to the liveCache.

Try to start it with 'x_server start'. If it is already started, SAP support should have a look at the system and it would be very helpful to get a remote connection to your server. So please open a customer message to get your problem solved!

Regards,

Melanie

[Former Member]

Hi Melanie,

Thanks for your suggestion. I agree to what you have said.

Xserver service is running fine on Livecache server. Hence, I guess that messages can be ignored.

- Nirav.

[former_member229109]

Hello Nirav,

Did you create the SAP ticket as it was recommended?

We could logon to your system via OSS & take a look closer on the

reported issue.

Thank you and best regards, Natalia Khlopina

[Former Member]

Hi ,

Was this problem resolved? if yes can you share the resolution please.

We are facing same issue with our server.

Regards,

Ravi.

[markus_doehr2]

Check the connections in DB59, execute the connection check an post the results.

Markus

[Former Member]

Hi Ravi,

Sorry to say that problem was not solved.

- Nirav.

[Former Member]

Hi Nirav,

Have you found solution?

I have the same error but in different circumstances (during connecting Crystal Reports with IDES).

Regards

Jacek

[Former Member]

Hi Nirav,

Can you please tell me what was the solution for the problem?

Regards

Prakash