Error Livecache

[Former Member]

Hi,

I´m getting this error when I try to connect the sap system with the instance of livecache.the error that I get in the LC10 is the next:

Name und Server : LAC - host

DBMRFC Funktion : DBM_CONNECT

Fehler : Fehler des DBM

Rückgabewert : -4

Fehlermeldung : Reading header from pipe:closed by serv

What can i do??

[former_member229109 · Accepted solution]

Hello Ruben Torres,

-> You have the option to open the SAP message and get SAP support.

-> Check on the host server if you could connect to LAC as DBM user.

< control, by default SAP installation>

Check the dbmsrv* protocol for additional information located in IndepDataPath/wrk on host server.

Check with sdbverify tool < run as root on Linux/Unix server > the liveCache software installation.

Thank you and best regards, Natalia Khlopina

[Former Member · Accepted solution]

Hi natalia,

Yes, I know that I´ve the option to open the SAP message, but for me is the last option.

Yes, I can connect whit the user control to the instance LAC with the user control.

Later, I´ll try to make the last indications

More thanks.

[former_member229109 · Accepted solution]

Hello,

1. The best answer on the posted question u201CWhat can i do??u201D

=> Create the SAP ticket & you know it. The problem will be solved faster.

In case you will go in the wrong direction, the new problems will be created

2. If you still try to solve it by yourself, please review the liveCache documentation & liveCache installation guids first.

u201CCheck with sdbverify tool < run as root on Linux/Unix server > the liveCache software installation.u201D

Please run as root user & post the results:

cd /sapdb/programs/bin

./sdbverify

Also post the outputs of the commands, as user in the sdba group:

sdbregview u2013l

dbmcli db_enum

dbmcli inst_enum

dbmcli u2013d LAC -n host u2013u <dbm-user>,<pwd> db_state

dbmcli u2013s dbm_version

xinstinfo LAC

df u2013k /sapdb

df u2013k /sapdb/programs

mount

Thank you and best regards, Natalia Khlopina

[Former Member · Accepted solution]

Hi Natalia,

sdbregview u2013l

avast:> sdbregview -l

SAP Utilities /sapdb/programs 7.7.04.29 64 bit valid

Server Utilities /sapdb/programs 7.7.04.29 64 bit valid

DB Analyzer /sapdb/programs 7.7.04.29 64 bit valid

APO LC APPS /sapdb/LCP/db/sap 7.00.006 64 bit valid

APO LC APPS /sapdb/LAC/db/sap 7.00.006 64 bit valid

APO LC APPS /sapdb/LCA/db/sap 7.00.006 64 bit valid

Redist Python /sapdb/programs 7.7.04.29 32 bit valid

Base /sapdb/programs 7.7.04.29 64 bit valid

JDBC /sapdb/programs 7.6.05.06 valid

Messages /sapdb/programs MSG 0.7113 valid

ODBC /sapdb/programs 7.7.04.29 64 bit valid

SQLDBC 77 /sapdb/programs 7.7.04.29 64 bit valid

Database Kernel /sapdb/LCP/db 7.7.04.29 64 bit valid

Database Kernel /sapdb/LAC/db 7.7.04.29 64 bit valid

Database Kernel /sapdb/LCA/db 7.7.04.29 64 bit valid

Loader /sapdb/programs 7.7.04.29 64 bit valid

SQLDBC /sapdb/programs 7.7.04.29 64 bit valid

SQLDBC 76 /sapdb/programs 7.6.05.11 64 bit valid

Fastload API /sapdb/programs 7.7.04.29 64 bit valid

dbmcli db_enum

The user lacadm is in the group sdba, but when I try to executed the different command I get this message:

RTE_CallSdbStarter(): Must be called by root or effective user 102 effective group 105

Error! Connection failed to node (local) for database (no dbname):

Reading header from pipe:closed by serv

If i executed como user root

root@avast# ./dbmcli db_enum

OK

LAC /sapdb/LAC/db 7.7.04.29 fast running

LAC /sapdb/LAC/db 7.7.04.29 quick offline

LAC /sapdb/LAC/db 7.7.04.29 slow offline

LAC /sapdb/LAC/db 7.7.04.29 test offline

dbmcli inst_enum

root@avast # ./dbmcli inst_enum

OK

7.7.04.29 /sapdb/LC1/db

7.7.04.29 /sapdb/LC2/db

7.7.04.29 /sapdb/LAC/db

dbmcli u2013d LAC -n host u2013u <dbm-user>,<pwd> db_state

root@avast # ./dbmcli -d LAC -n apo -u control,password db_state

OK

State

ADMIN

dbmcli u2013s dbm_version

root@avast# ./dbmcli -s dbm_version

OK

VERSION = 7.7.04

BUILD = DBMServer 7.7.04 Build 029-123-196-543

OS = UNIX

INSTROOT = /sapdb/LC1/db

LOGON = True

CODE = UTF8

SWAP = full

UNICODE = YES

INSTANCE = (unknown)

SYSNAME = SunOS

MASKING = YES

REPLYTREATMENT = none,zlib,auto

xinstinfo LAC

root@avast# ./xinstinfo LAC

IndepData : /sapdb/data

IndepPrograms : /sapdb/programs

InstallationPath : /sapdb/LAC/db

Kernelversion : KERNEL 7.7.04 BUILD 029-123-196-543

Rundirectory : /sapdb/data/wrk/LAC

df u2013k /sapdb

root@avast # df -k /sapdb/

Filesystem kbytes used avail capacity Mounted on

/dev/md/dsk/d0 14460933 9158778 5157546 64% /

df u2013k /sapdb/programs

root@avast# df -k /sapdb/programs/

Filesystem kbytes used avail capacity Mounted on

/dev/md/dsk/d0 14460933 9158778 5157546 64% /

This are the outputs of the listed commands.

Edited by: Ruben Torres on Jan 10, 2010 6:19 PM

Edited by: Ruben Torres on Jan 10, 2010 6:21 PM

[former_member229109 · Accepted solution]

Hello Ruben,

1. What is the user with ID 102 & what is effective group 105?

Please post output of the commands:

id sdb

id lacadm

more /etc/opt/sdb

ls u2013l /sapdb/LAC/db/pgm

ls u2013l /sapdb/LAC/db/pgm/starter

ls u2013l /sapdb/programs/pgm/starter

ls u2013l /sapdb/programs/pgm

2. Please run as root user & post the results:

cd /sapdb/programs/bin

./sdbverify

Thank you and best regards, Natalia Khlopina

[Former Member · Accepted solution]

Hi Natalia,

This is the output of each command:

id sdb

bash-3.00$ id sdb

uid=102(sdb) gid=105(sdba)

id lacadm

bash-3.00$ id lacadm

uid=104(lacadm) gid=100(sapsys)

more /etc/opt/sdb

[Globals]

IndepData=/sapdb/data

IndepPrograms=/sapdb/programs

SdbOwner=sdb

SdbGroup=sdba

ls u2013l /sapdb/LAC/db/pgm

bash-3.00$ ls -l /sapdb/LAC/db/pgm/

total 392322

-r-xr-xr-x 1 sdb sdba 2659056 Oct 30 2008 backup

-r-xr-xr-x 1 sdb sdba 3521736 Oct 29 2008 cons

-r-xr-xr-x 1 sdb sdba 2905432 Oct 30 2008 dbmdrop

-r-xr-xr-x 1 sdb sdba 2905400 Oct 30 2008 dbmreg

-r-xr-xr-x 1 sdb sdba 16402168 Oct 30 2008 dbmshm

-r-xr-xr-x 1 sdb sdba 16432248 Oct 30 2008 dbmsrv

-r-xr-xr-x 1 sdb sdba 2905480 Oct 30 2008 dbmstart

-r-xr-xr-x 1 sdb sdba 2905448 Oct 30 2008 dbmstop

-r-xr-xr-x 1 sdb sdba 2905488 Oct 30 2008 dbmunreg

-r-xr-xr-x 1 sdb sdba 5090320 Oct 29 2008 diagnose

-r-xr-xr-x 1 sdb sdba 46553488 Oct 30 2008 kernel

-r-xr-xr-x 1 sdb sdba 14031712 Oct 30 2008 lserver

-r-xr-xr-x 1 sdb sdba 8047104 Oct 30 2008 python

-r-xr-xr-x 1 sdb sdba 67309456 Oct 29 2008 slowknl

-r-xr-xr-x 1 sdb sdba 2963704 Oct 29 2008 start

dr-x------ 2 sdb sdba 512 Dec 31 12:11 starter

-r-xr-xr-x 1 sdb sdba 2958280 Oct 29 2008 stop

-r-xr-xr-x 1 sdb sdba 60456 Oct 29 2008 sysrc

-r-xr-xr-x 1 sdb sdba 60768 Oct 30 2008 tracesort

ls u2013l /sapdb/LAC/db/pgm/starter

bash-3.00$ ls -l /sapdb/LAC/db/pgm/starter

total 10176

-r-x------ 1 root sdba 2596688 Oct 30 2008 dbmverifypw

-r-xx- 1 root sdba 2596352 Oct 29 2008 sdbstarter

ls u2013l /sapdb/programs/pgm/starter

bash-3.00$ ls -l /sapdb/programs/pgm/starter/

total 5088

-rwxrwxrwx 1 root sdba 2596352 Oct 29 2008 sdbstarter

ls u2013l /sapdb/programs/pgm

bash-3.00$ ls -l /sapdb/programs/pgm/

total 75618

-rwxrwxrwx 1 sdb sdba 14031712 Oct 30 2008 lserver

-rwxrwxrwx 1 sdb sdba 2560056 Oct 29 2008 maketi

-rwxrwxrwx 1 sdb sdba 1614552 Oct 30 2008 niping

-rwxrwxrwx 1 sdb sdba 2353568 Oct 29 2008 niserver

-rwxrwxrwx 1 sdb sdba 2352896 Oct 29 2008 nisslserver

-rwxrwxrwx 1 sdb sdba 8047104 Oct 30 2008 python

-rwxrwxrwx 1 sdb sdba 2555992 Oct 30 2008 regupd

-rwxrwxrwx 1 sdb sdba 2504832 Oct 29 2008 sqlping

drwxrwxrwx 2 sdb sdba 512 Dec 31 12:11 starter

-rwxrwxrwx 1 sdb sdba 2572304 Oct 30 2008 vserver

Any suggestion?

More thanks

[former_member229109 · Accepted solution]

Hello Ruben Torres,

1. Did you change the permissions of the database software manually? Itu2019s NOT recommended.

The ownership and permissions of the database software has to be set by the MAXD installation or upgrade tools.

The u2018s-bitu2019 settings could be changed if you copied the software or has the restrictions for u2018s-bitu2019 for the FS where the software installed, for example.

Please run as root user:

cd /sapdb/programs/pgm/starter

chmod 4510 ./sdbstarter

ls -ltr

and update with output of the recommended commands.

2. Please run as root user & post the results:

cd /sapdb/programs/bin

./sdbverify

Thank you and best regards, Natalia Khlopina

[Former Member · Accepted solution]

Hi Natalia,

If the permissions are modified what solutions are there??

What do the command /sapdb/programs/bin/sdbverify --set_corrupted_invalid ??

More thanks.

Edited by: Ruben Torres on Jan 19, 2010 2:43 PM

[former_member229109 · Accepted solution]

Hello Ruben,

1. Please run as root user & post the results:

cd /sapdb/programs/bin

./sdbverify

At least please post the information about the database software files,

which have the modified ownership/permissions.

2. Please run as root user:

cd /sapdb/programs/pgm/starter

chmod 4510 ./sdbstarter

ls -ltr

and let me know if you could set the u2018s-bitu2019.

3. This command u2018/sapdb/programs/bin/sdbverify --set_corrupted_invalidu2019 should run with root user.

You could set the incorrectly installed database software package as invalid,

then you need to install those database software packages with SDBINST again.

Please post the answer on the 1. & 2. before to go with this option.

< Please review the SAP Note No. 767538, for example. >

Thank you and best regards, Natalia Khlopina