unable to continue upgrade from SUM tool

[Former Member]

Hi,

We are using NW 2004 s (dual stack) and upgrade it with NW 7.3 through SUM tool SP05. OS is server 2003 and DB ms-sql 2008 R2

I uninstall scs instance from installation master. Now when I run sum tool, at the phase Specify credentials, error prompting as SCS instance is not detected.

Below is the logfile status:

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

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

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

<!--NAME[F:\SUM\sdt\log\SUM\INPUT-OS-USER-PASSWORDS_01.LOG]/-->

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

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

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

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

Oct 18, 2012 9:21:36 PM [Info  ]: Connecting to the instance with address http://piserver:50013 using the SAPControl web service API.

Oct 18, 2012 9:21:39 PM [Info  ]: Setting the credentials for user pi1adm and a password.

Oct 18, 2012 9:21:39 PM [Info  ]: Setting the service timeout to 300 s.

Oct 18, 2012 9:21:39 PM [Info  ]: Connecting to the instance with address http://piserver:50013 using the SAPControl web service API.

Oct 18, 2012 9:21:41 PM [Info  ]: Setting the credentials for user pi1adm and a password.

Oct 18, 2012 9:21:41 PM [Info  ]: Setting the service timeout to 300 s.

Oct 18, 2012 9:21:41 PM [Info  ]: Connecting to the instance with address http://piserver:50013 using the SAPControl web service API.

Oct 18, 2012 9:21:43 PM [Info  ]: Setting the credentials for user pi1adm and a password.

Oct 18, 2012 9:21:43 PM [Info  ]: Setting the service timeout to 300 s.

Oct 18, 2012 9:21:43 PM [Info  ]: Instance: hostName: piserver|instanceNumber: 0|featuresList: ABAP|J2EE|GATEWAY|MESSAGESERVER|ENQUE|ICMAN|IGS|instanceName: null|profilePath: null|sapLocalHost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false

has been detected.

Oct 18, 2012 9:21:43 PM [Error ]: The following problem has occurred during step execution: com.sap.sdt.tools.sysinfo.InstanceDetectorException: The update tool is unable to detect the instances information. Check that the SAP Start Services are running for all instances in the cluster. See SAP Note 1401712 for further information.

SCS instance is not detected.

.

How can I resolve this issue.... help me!

Regards,

Devendra

[tomas_black · Accepted solution]

Hello Davendra,

note #1401712 won't help you as there is no SCS!

Since SCS was uninstsalled, your dual-stack system has become a single ABAP system, correct? On this case you won't be able to perform a dual-stack system upgrade as SUM will never find the Java stack.

You'll have to reset the current one and restart the ugprade procedure for a single ABAP stack only.

Best regards,

Tomas Black

[Former Member · Accepted solution]

Hi Tomas

THanks for your reply.

Yes i have uninstalled SCS but when i am resetting tool and restrting the upgrade then it is still showing system as Dual Stack in SUM.

So is there any specific procedure that we need to perform after uninstallation of Java stack.

Thanks in adcance.

[former_member209809]

Hi Devendra,

Since you have uninstalled Java instance then you might need to perform some post uninstallation process.

Follow below link http://scn.sap.com/thread/776757

after that reset your upgrade process and then restart the upgrade.

Regards,

Sumit Jha

[Former Member]

Hi Devendra,

Here is the solution for your issue from note 1401712 -

Reason and Prerequisites

The following upgrade/update tools:

• JSPM 702 SP3 and higher

• SAPJup for SAP NetWeaver 7.0 EHP2

• SAPJup for BS7i2010

• SAPehpi 702

• SUM

have a new instance detection mechanism which uses SAPControl Web Service API to retrieve the instances information in the cluster.
Therefore, it is very important that the SAP start services of all instances in the SAP system are running. If a service associated with a given instance is not running, the upgrade/update tool will not detect this instance and will not manage it.

Additionally, the new instance detection mechanism is not supported by all kernel versions. If you have an old kernel which does not support the new functionality, the old detection mechanism will be used.

- SAP KERNEL release 7.10: supported by all PATCH levels
- SAP KERNEL release 7.20: supported by all PATCH levels
- SAP KERNEL release 7.30: supported by all PATCH levels
- SAP KERNEL release 7.00: supported by PATCH 96 and higher
- SAP KERNEL release 6.40: supported by PATCH 169 and higher
Solution

If you face problems during the instance detection of the SAP system, check the following:

• Make sure that the SAP start service is running on each of the instances on each host in your SAP system.
• If you have a kernel with version lower than the listed versions and the update/upgrade tool was unable to detect all your instances, get a newer SAP KERNEL archive for your release and apply it manually as described in SAP Note 1122058.

This will solve the issue you are facing.

Regards,

Ashutosh Shukla