Error During SolMan Installation

[Former Member]

Hi,

We are trying to Install SAP Solution Manager 7.1.

Operating System - Redhat Linux 5.6

Database - MaxDB 7.7

During the installation we get the following error at the step "Start Java Engine"

Instance xxx/DVEBMGS00 reached state SHUTDOWN after having state STARTING. Giving up.

we have checked the files dev_w0, dev_ms, dev_disp. Below are snippets of the log from these files:

dev_ms

-

---

[Thr 47754012325216] Thu Nov 17 10:08:06 2011

[Thr 47754012325216] *** ERROR => MsSCheckConnections: no response from client C1 (127.0.0.1) after 300 secs received [msxxserv_mt. 4085]

[Thr 47754012325216] *** ERROR => MsSCheckConnections: disconnect now [127.0.0.1] [msxxserv_mt. 4089]

dev_w0

-

---

C Thu Nov 17 09:57:04 2011

C SQLDBC Module : /sapdb/programs/lib/libSQLDBC77.so

C SQLDBC SDK : SQLDBC.H 7.7.4 BUILD 009-123-173-450

C SQLDBC Runtime : libSQLDBC 7.7.4 BUILD 028-123-194-355

C SQLDBC client runtime is MaxDB 7.7.4.028 CL 194355

C SQLDBC supports new DECIMAL interface : 1

C SQLDBC supports VARIABLE INPUT data : 1

C SQLDBC supports VARIABLE OUTPUT data : 0

C SQLDBC supports Multiple Streams : 1

C SQLDBC supports LOB LOCATOR KEEPALIVE : 1

C SQLDBC supports LOB LOCATOR COPY : 1

C SQLDBC supports BULK SELECT with LOBS : 0

C INFO : SQLOPT= -I 0 -t 0 -S SAPR3

C Try to connect (DEFAULT) on connection 0 ...

C *** ERROR => Connect to database failed, rc = -10709 (Connection failed (RTE:database not running: no request pipe))

[dbsdbsql.cpp 139]

B ***LOG BV3=> severe db error -10709 ; work process is stopped [dbsh 1241]

B ***LOG BY2=> sql error -10709 performing CON [dblink 540]

B ***LOG BY0=> Connection failed (RTE:database not running: no request pipe) [dblink 540]

M ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c 1461]

M in_ThErrHandle: 1

M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 11090]

M

M Info for wp 0

M

dev_disp

-

---

Thu Nov 17 09:57:08 2011

• ERROR => DpHdlDeadWp: W0 (pid 10410) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=10410) exited with exit code 255

• ERROR => DpHdlDeadWp: W1 (pid 10411) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=10411) exited with exit code 255

• ERROR => DpHdlDeadWp: W2 (pid 10413) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=10413) exited with exit code 255

• ERROR => DpHdlDeadWp: W3 (pid 10417) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=10417) exited with exit code 255

• ERROR => DpHdlDeadWp: W4 (pid 10418) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=10418) exited with exit code 255

• ERROR => DpHdlDeadWp: W5 (pid 10419) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=10419) exited with exit code 255

• ERROR => DpHdlDeadWp: W6 (pid 10420) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=10420) exited with exit code 255

• ERROR => DpHdlDeadWp: W7 (pid 10421) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=10421) exited with exit code 255

• ERROR => DpHdlDeadWp: W8 (pid 10422) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=10422) exited with exit code 255

• ERROR => DpHdlDeadWp: W9 (pid 10423) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=10423) exited with exit code 255

• ERROR => DpHdlDeadWp: W10 (pid 10430) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=10430) exited with exit code 255

• ERROR => DpHdlDeadWp: W11 (pid 10431) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=10431) exited with exit code 255

• ERROR => DpHdlDeadWp: W12 (pid 10432) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=10432) exited with exit code 255

• ERROR => DpHdlDeadWp: W13 (pid 10433) died (severity=0, status=65280) [dpxxwp.c 1507]

We have checked the SAP MMC and see that message server and enq servers are green. disp+work is grey -> shutdown. Any idea how to solve the above error and continue with Installation?

Regards,

Reena

[Former Member]

Hi,

please try with the latest maxdb DBSL library and latest MaxDB clinet

regards, Javier

[Former Member]

Thanks for your reply.

Do you mean upgrade MaxDB to version 7.8?

Also, we came across SAP Note: 1393687. The error mentioned in this note is exactly the same as the error we have in our dev_w0 file. But the note is applicable for MaxDB 7.8 and not for 7.7.

Should be implement it anyhow as the problem is the same?

Regards,

Reena

[Former Member]

Hello,

The note mentioned by you is I think the same as upgrading the kernel to latest patch level.

You can try that for sure.

dbsl is also contained in the kernel.

Thanks