Skip to Content
author's profile photo Former Member
Former Member

DBM_CONNECT error, return code -11, tp error

Hello

I have an SCM 5.0 ABAP-only system (sid=APC) not correctly communicating with a 7.6.0.3 liveCache. In transaction LC10, clicking the monitoring button for any DB connection results in:

Name and Server : LPC - dngdbs07

DBMRFC Function : DBM_CONNECT

Error : DBM Error

Return Code : -11

Error Message : tp error: sapparam: SAPSYSTEMNAME neithe

Notice how error message is cut off ...

1. LCA, LDA, and LEA connection tests in DB59 all fail with the same error.

2. From transaction SM49, dbmcli -d LPC -n dngdbs07 -tpp no_longer_used -tpi APC -tpc LCA <any command> fails with the same error.

3. From the command-line, dbmcli -d LPC -n dngdbs07 -tpp no_longer_used -tpi APC -tpc LCA <any command> succeeds for both apcadm and SAPserviceAPC users. (ABAP system is Windows, liveCache system is HP-UX.)

4. RFC destinations SAPDB_DBM, SAPDB_DBM_DAEMON, and SAPXPG_DBDEST_<HOSTNAME> are all successful.

5. I un-checked the Central Authorization checkbox in LC10 --> Integration and the error goes away, so I can then see the liveCache system status.

I tried debugging the ABAP and it appears sapxpg is having trouble calling the external command when Central Authorization is enabled. Does anyone have any ideas about what's wrong with this?

SAP_BASIS SP 14

NW 700 kernel patch 159

non-unicode

Thanks

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    Posted on Aug 12, 2008 at 06:24 AM

    > Name and Server : LPC - dngdbs07

    > DBMRFC Function : DBM_CONNECT

    > Error : DBM Error

    > Return Code : -11

    > Error Message : tp error: sapparam: SAPSYSTEMNAME neithe

    >

    > Notice how error message is cut off ...

    Ok, the cutoff is just due to the error handling routine - I believe the full error message would be "SAPSYSTMNAME neiter in environment or parameterfile specified" or something like this.

    > 1. LCA, LDA, and LEA connection tests in DB59 all fail with the same error.

    Of course they do - they are all the same connection setup, just for different purposes.

    > 2. From transaction SM49, dbmcli -d LPC -n dngdbs07 -tpp no_longer_used -tpi APC -tpc LCA <any command> fails with the same error.

    Of course it does. The TP is used to get logon data from the SCM database (central authorization) for the logon to the liveCache. with the -tpp -tpi -tpc arguments you tell dbmcli to use TP.

    > 3. From the command-line, dbmcli -d LPC -n dngdbs07 -tpp no_longer_used -tpi APC -tpc LCA <any command> succeeds for both apcadm and SAPserviceAPC users. (ABAP system is Windows, liveCache system is HP-UX.)

    Well, perhaps you've a different environment setup here? On Windows it's a quite common issue that everything works fine as <SID>adm but the SAP workprocesses run as SAPSERVICE<SID> ... so checking the environment variables for both might be a good idea.

    > 4. RFC destinations SAPDB_DBM, SAPDB_DBM_DAEMON, and SAPXPG_DBDEST_<HOSTNAME> are all successful.

    Sure - they've nothing to do with TP. Instead these are just calls to the dbmcli command. SAPDB_DBM is just running one command and returning the result, where SAPDB_DBM_DEAMON is used for multiple commands in one DBM session.

    > 5. I un-checked the Central Authorization checkbox in LC10 --> Integration and the error goes away, so I can then see the liveCache system status.

    Also quite clear - TP is only used with dbmcli when central authorization is used. If it's not used, then XUSER data is used to connect to the liveCache.

    > I tried debugging the ABAP and it appears sapxpg is having trouble calling the external command when Central Authorization is enabled. Does anyone have any ideas about what's wrong with this?

    As already said: check the environment variables. Also check the Transportprofile (TMS).

    If you don't succeed: open a support message.

    regards,

    Lars

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Lars, thank you for your response.

      It stands to reason that if I can successfully call dbmcli -d -n -tpp -tpc -tpi etc as SAPServiceAPC then the work processes (which also run as SAPServiceAPC) should then invoke sapxpg and call it successfully as well. Same user, same environment.

      However this is not the behavior I'm witnessing. From the command-line the dbmcli command succeeds, from LC10 the external call fails. This does not make sense! I've double-checked the environment variables, everything looks fine.

      Thanks anyway.

  • author's profile photo Former Member
    Former Member
    Posted on Aug 12, 2008 at 09:23 PM

    hello,

    it is worth to try following :

    in sm49 run command env(or set)

    and compare it with set/env result in command line for sidadm and sapserviceSID

    it is possible that you have changed enviroment but you have not restarted SAP since then ?

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Thanks Ivan for your response. It seems that my A.BAP system is only recognizing the system-wide environment variables, and not the user-specific ones. This is clearly the case after running "set" from SM49. This is quite bizarre but I've found a few Microsoft support notes indicating similar behavior. In particular this one: http://support.microsoft.com/kb/883662

      In any case, I've worked around the problem by setting all of my important environment variables as global system-wide ones. The ABAP system now communicates with liveCache correctly.

      Thanks

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.