on 05-31-2006 6:43 PM
Hello,
We have installed SCM 4.1 on Solaris on one box and LC 7.5 on another solaris box.
For kernel upgrade, we shut down Live Cache using LC10>administration on SCM server. After kernel patch, other patches for ABAP stack, we upgraded LC to SP11 build 35.
Since then, we get following error in LC10.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Name and Server : LCA - gva1073
DBMRFC Function : DBM_EXECUTE
Command : dbm_version
Error : DBM Error
Return Code : -11
Error Message : tp error: Terminating. [nlsui0.c 1934] pid
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Also, in DB59, when we try to check connection, we get following error -
General Connection Data
Connection Name....: LCA
Database Name......: LCA
Database Server....: gva1073
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: gva1075_SCD_03 (
SunOS )
1. Connect. test with "dbmcli db_state"
Successful
2. Connect. test with command mode "dbmrfc db_state"
Unsuccessful
dbm_system_error
Name and Server : LCA - gva1073
DBMRFC Function : DBM_EXECUTE
Command : db_state
Error : DBM Error
Return Code : -11
Error Message : tp error: Terminating. [nlsui0.c 1934] pid
3. Connect. test with session mode "dbmrfc db_state"
Unsuccessful
dbm_system_error
Name and Server : LCA - gva1073
DBMRFC Function : DBM_CONNECT
Error : DBM Error
Return Code : -11
Error Message : tp error: Terminating. [nlsui0.c 1934] pid
4. Connect. test with "native SQL" ( LCA )
Successful
++++++++++++++++++++++++++++++++++++++++++++++++++++
Can anybody please help?
Thanks and regards,
Vaibhav
Hello Vaibhav,
while using transaction LC10, the error 11 "tp error: Terminating. [nlsui0.c ...]" occurs. The user authorization with tp fails and the application server cannot connect to the liveCache.
I assumed, that it's due to a library version mismatch, tp cannot use the liveCahe UNICODE libraries.
Please check, that the tp call at the command line works properly. And a dbmcli call in the transaction SM49 with the tp options
(dbmcli ::
-d <LC-SID> -n <LC-servername> -tpp <profile> -tpi <system-SID>
-tpc <connection - LCA/LDA> dbm_version)
works also properly.
I recommend you to update the liveCache client software on the Application server.
If you've got access to OSS/Service Market Place, then please take a look at note
649814 how to update the liveCache client software on the application server.
< Please also review the SAP notes 847736 & 831108 >
Before the liveCache client version will be upgraded on the application
server you can use the workaround by switching off the central authorization for the liveCache LCA/LDA connections:
In transaction LC10, choose Integration and deactivate the option Central authorization, then save.
If you are the official SAP customer, I recommend you to create the ticket to SAP on 'BC-DB-LVC' queue.
Thank you and best regards, Natalia Khlopina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.