Archived discussions are read-only. Learn more about SAP Q&A

SUM can't connect to Java instance

Sorry for bothering you with something that has to be a beginner's problem:

I started SUM on the java instance of an MCOD installation. But it fails when it tries to connect to the java instances with sapcontrol:

more /usr/sap/P1E/SUM/sdt/log/SUM/INPUT-OS-USER-PASSWORDS_10.LOG

<!--LOGHEADER[START]/-->

<!--HELP[Manual modification of the header may cause parsing problem!]/-->

<!--LOGGINGVERSION[2.0.7.1006]/-->

<!--NAME[/usr/sap/P1E/SUM/sdt/log/SUM/INPUT-OS-USER-PASSWORDS_10.LOG]/-->

<!--PATTERN[INPUT-OS-USER-PASSWORDS_10.LOG]/-->

<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%6s]: %m)]/-->

<!--ENCODING[UTF8]/-->

<!--LOGHEADER[END]/-->

Nov 5, 2013 11:17:20 AM [Info  ]: Connecting to the instance with address http://r9018i1:51013 using the SAPControl web service API.

Nov 5, 2013 11:17:27 AM [Info  ]: Setting the credentials for user p1eadm and a password.

Nov 5, 2013 11:17:27 AM [Info  ]: Setting the service timeout to 300 s.

Nov 5, 2013 11:17:34 AM [Info  ]: The detected sapstartsrv release is 720 and patch level is 401. The minimum supported patch level for this release is 54.

Nov 5, 2013 11:17:34 AM [Info  ]: Connecting to the instance with address http://r9018i1:51013 using the SAPControl web service API.

Nov 5, 2013 11:17:39 AM [Info  ]: Setting the credentials for user p1eadm and a password.

Nov 5, 2013 11:17:39 AM [Info  ]: Setting the service timeout to 300 s.

Nov 5, 2013 11:17:40 AM [Info  ]: Connecting to the instance with address http://r9018i1:51013 using the SAPControl web service API.

Nov 5, 2013 11:17:43 AM [Info  ]: Setting the credentials for user p1eadm and a password.

Nov 5, 2013 11:17:43 AM [Info  ]: Setting the service timeout to 300 s.

Nov 5, 2013 11:17:43 AM [Warning]: No instances were detected via sapcontrol. Most probably there is no local sapstartsrv process running.

Nov 5, 2013 11:17:43 AM [Error ]: The following problem has occurred during step execution: com.sap.sdt.tools.sysinfo.RequiredKernelFunctionNotSupportedException: No instances

were detected via sapcontrol. Most probably there is no local sapstartsrv process running.

.

but as you can see, sapstartsrv processes are up 'n running.

r9018:p1eadm 12> ps -ef | grep saps | grep P1E

  p1eadm 17760268        1   0 15:19:48      -  0:29 /usr/sap/P1E/SCS11/exe/sapstartsrv pf=/usr/sap/P1E/SYS/profile/P1E_SCS11_r9018i1 -D

  p1eadm 22610000        1   0 10:37:06      -  0:00 sapstart pf=/usr/sap/P1E/SYS/profile/P1E_SCS11_r9018i1

  p1eadm 26149094        1   0 15:01:59      -  1:59 /usr/sap/P1E/J10/exe/sapstartsrv pf=/usr/sap/P1E/SYS/profile/P1E_J10_r9018i1 -D

  p1eadm 30801988        1   0 10:37:23      -  0:00 sapstart pf=/usr/sap/P1E/SYS/profile/P1E_J10_r9018i1

privileges for sapuxuserchk:

-rwsr-xr-x    1 root     sapsys      1024159 Jan 16 2013  sapuxuserchk

and the provided password for p1eadm is correct, too.

So what may be the error?

replied

Hi guys,

now that a colleague has solved the riddle, I would like to pass the information to all of you. Looks like this is somehow typical for the way, SUM handles the upgrade and sometimes makes a mountain out of a molehill:

During some earlier upgrade from 7.x to 7.3 there was created a java central instance J10 out of the former JC10. I don't know whether this is usual behavior or just a fault from the guy who did the upgrade, but the old instance directory remained.

Switching traceleve higher, my colleague discovered that SUM still tried to connect to this old JC10.

So we just removed the old instance directory - and now it runs ...

Regards

Ralf

1 View this answer in context

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question