sap upgrade stuck due to dialog instance not found

[Former Member]

Hi ALL,

I am middle to SAP Java upgrade from 7.01 release to EHP1 OF 7.30, I am having issue in initialization phase where SAP MMC detecting dialog instance which no longer exist, I can't delete this dialog instance since server itself not exist,

In solve this issue, I tried following step

I rename the instance folder J60 to old_J60, I removed the  dialog instance profile from /sapmnt<SID>/ profiles, I also followed the sap note      871523 - Removing dialog instance from database after uninstallation,  and restarted the instance, but somehow when I am still running the MMC, it is pointing to dialog instance which no longer exist,  and give error like The host  name could not be resolve,?

would anyone can help and tell me how can I removed instance so http://<hostname:5<sys no>13 does not point to dialog instance and I can continue upgrade

Dinesh

[Former Member]

Hi Dinesh,

Please go through below points if that helps...

Upgrade tool (SUM, SAPehpi,etc) 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.

Also, try fresh with extracting SUM files again instead of using existing SUM.

Regards,

Prithviraj.

[former_member185239]

Hi Dinesh,

Follow the below steps:

1. Remove the profiles of dialog instances from shadow system as well.

2. remove .saptream files from /tmp directory.

3. Kill the sapstartsrv process if it running for the dialog instance.

4. remove all the files from sapcontrol folder.

Then take a restart of the whole sap system.

Also do paste the output of

sapcontrol -nr <dialog instance number> -function GetProcessList

With Regards

Ashutosh Chaturvedi

[Former Member]

Hi Ashutosh,

I tried to above steps , but still no luck, I can see entry for effected server coming in sapcontrol folder, but  I cleaned up /tmp folder and also clear entries in sapcontrol and restarted the server and sapstartsrv, but somehow entry keep coming

nzlsvfnux406:bjqadm 149> sapcontrol -nr 60 -function GetProcessList 28.12.2014 13:08:54 GetProcessList FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen() nzlsvfnux406:bjqadm 150> sapcontrol -nr 56 -function GetProcesslist Unknown webmethod: GetProcesslist nzlsvfnux406:bjqadm 151> sapcontrol -nr 56 -function GetProcessList 28.12.2014 13:09:18 GetProcessList OK name, description, dispstatus, textstatus, starttime, elapsedtime, pid jcontrol, J2EE Server, YELLOW, Some processes running, 2014 12 28 13:05:55, 0:03:23, 22766 igswd_mt, IGS Watchdog, GREEN, Running, 2014 12 28 13:05:55, 0:03:23, 22767 nzlsvfnux406:bjqadm 152>

[Reagan]

Are there any entries under services.msc pointing to the AS?

Also if there are profiles of the deleted AS in the profile directory then remove them.

It would be easy to understand what the issue is if you supply the relevant logs from the upgrade directory.

[Former Member]

Thank for reply, but we are in Linux server and services.msc  not sure where I can found, I did following step till mow

1. remove profile from profile directory

2. rename java folder J60 to old_file

3. deleted dialog instance as per sap note 871523

put upgrade still stuck with

Dec 24, 2014 12:18:46 PM [Info  ]: getParameterValue SAPLOCALHOST from http://pasbjq:55613 Dec 24, 2014 12:18:46 PM [Info  ]: getParameterValue response: pasbjq Dec 24, 2014 12:18:46 PM [Info  ]: All retrieved instances : 3 Dec 24, 2014 12:18:46 PM [Info  ]: Correctly detected instance: 56 on host pasbjq Dec 24, 2014 12:18:46 PM [Info  ]: Correctly detected instance: 55 on host jscsbjq Dec 24, 2014 12:18:46 PM [Info  ]: Correctly detected instance: 60 on host aas4bjq Dec 24, 2014 12:18:46 PM [Info  ]: All retrieved instances from sapcontrol at http://pasbjq:55613: Dec 24, 2014 12:18:46 PM [Info  ]: Instance: hostName: pasbjq|instanceNumber: 56|state: IN_PROGRESS|featuresList: J2EE|IGS|instanceName: null|profilePath: null|sapLocalHost: nul l|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false Dec 24, 2014 12:18:46 PM [Info  ]: Instance: hostName: jscsbjq|instanceNumber: 55|state: RUNNING|featuresList: MESSAGESERVER|ENQUE|instanceName: null|profilePath: null|sapLocalH ost: null|startProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false Dec 24, 2014 12:18:46 PM [Info  ]: Instance: hostName: aas4bjq|instanceNumber: 60|state: STOPPED|featuresList: J2EE|IGS|instanceName: null|profilePath: null|sapLocalHost: null|s tartProfile: null|osUserName: null|isSCS: false|isInitiallyConnectedInstance: false|isCentralInstance: false Dec 24, 2014 12:18:46 PM [Info  ]: getParameterValue DIR_PROFILE from http://pasbjq:55613 Dec 24, 2014 12:18:46 PM [Info  ]: getParameterValue response: /usr/sap/BJQ/SYS/profile Dec 24, 2014 12:18:46 PM [Info  ]: getParameterValue INSTANCE_NAME from http://pasbjq:55613 Dec 24, 2014 12:18:46 PM [Info  ]: getParameterValue response: JC56 Dec 24, 2014 12:18:46 PM [Info  ]: getParameterValue SAPPROFILE from http://pasbjq:55613 Dec 24, 2014 12:18:46 PM [Info  ]: getParameterValue response: /sapmnt/BJQ/profile/BJQ_JC56_pasbjq Dec 24, 2014 12:18:46 PM [Info  ]: getParameterValue SAPLOCALHOST from http://pasbjq:55613 Dec 24, 2014 12:18:46 PM [Info  ]: getParameterValue response: pasbjq Dec 24, 2014 12:18:46 PM [Info  ]: getStartProfile response from http://pasbjq:55613: /usr/sap/BJQ/SYS/profile/START_JC56_pasbjq Dec 24, 2014 12:18:46 PM [Info  ]: Creating a proxy to the sapcontrol web service at http://jscsbjq:55513 Dec 24, 2014 12:18:47 PM [Info  ]: Setting the credentials for user bjqadm and a password. Dec 24, 2014 12:18:47 PM [Info  ]: Using user name bjqadm to authenticate against the SAPControl web service API. Dec 24, 2014 12:18:47 PM [Info  ]: Setting the service timeout to 300 s. Dec 24, 2014 12:18:47 PM [Info  ]: getParameterValue INSTANCE_NAME from http://jscsbjq:55513 Dec 24, 2014 12:18:47 PM [Info  ]: getParameterValue response: SCS55 Dec 24, 2014 12:18:47 PM [Info  ]: getParameterValue INSTANCE_NAME from http://jscsbjq:55513 Dec 24, 2014 12:18:47 PM [Info  ]: getParameterValue response: SCS55 Dec 24, 2014 12:18:47 PM [Info  ]: getParameterValue SAPPROFILE from http://jscsbjq:55513 Dec 24, 2014 12:18:47 PM [Info  ]: getParameterValue response: /usr/sap/BJQ/SYS/profile/BJQ_SCS55_jscsbjq Dec 24, 2014 12:18:47 PM [Info  ]: getParameterValue SAPLOCALHOST from http://jscsbjq:55513 Dec 24, 2014 12:18:47 PM [Info  ]: getParameterValue response: jscsbjq Dec 24, 2014 12:18:47 PM [Info  ]: getStartProfile response from http://jscsbjq:55513: /usr/sap/BJQ/SYS/profile/START_SCS55_jscsbjq Dec 24, 2014 12:18:47 PM [Info  ]: Creating a proxy to the sapcontrol web service at http://aas4bjq:56013 Dec 24, 2014 12:18:47 PM [Info  ]: Setting the credentials for user bjqadm and a password. Dec 24, 2014 12:18:47 PM [Info  ]: Using user name bjqadm to authenticate against the SAPControl web service API. Dec 24, 2014 12:18:47 PM [Info  ]: Setting the service timeout to 300 s. Dec 24, 2014 12:18:47 PM [Info  ]: getParameterValue INSTANCE_NAME from http://aas4bjq:56013 Dec 24, 2014 12:18:47 PM [Error ]: Error while obtaining the INSTANCE_NAME parameter value from the instance with number 60 on host aas4bjq using the SAPControl web service API. For more information, see SAP Note 1401712. Dec 24, 2014 12:18:47 PM [Error ]: HTTP transport error: java.net.UnknownHostException: aas4bjq Dec 24, 2014 12:18:47 PM [Info  ]: Could not establish a connection to instance 60 on host aas4bjq by using HTTP protocol. SUM will attempt to connect to the instance by using t he HTTPS protocol. Dec 24, 2014 12:18:47 PM [Info  ]: Creating a proxy to the sapcontrol web service at https://aas4bjq:56014 Dec 24, 2014 12:18:48 PM [Info  ]: Setting the credentials for user bjqadm and a password. Dec 24, 2014 12:18:48 PM [Info  ]: Using user name bjqadm to authenticate against the SAPControl web service API. Dec 24, 2014 12:18:48 PM [Info  ]: Setting the service timeout to 300 s. Dec 24, 2014 12:18:48 PM [Info  ]: getParameterValue INSTANCE_NAME from https://aas4bjq:56014 Dec 24, 2014 12:18:48 PM [Error ]: Error while obtaining the INSTANCE_NAME parameter value from the instance with number 60 on host aas4bjq using the SAPControl web service API. For more information, see SAP Note 1401712. Dec 24, 2014 12:18:48 PM [Error ]: HTTP transport error: java.net.SocketException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl) Dec 24, 2014 12:18:48 PM [Error ]: The following problem has occurred during step execution: com.sap.sdt.tools.sapcontrolws.SapControlWsException: Error while obtaining the INST ANCE_NAME parameter value from the instance with number 60 on host aas4bjq using the SAPControl web service API. For more information, see SAP Note 1401712. com.sun.xml.internal.ws.client.ClientTransportException: HTTP transport error: java.net.SocketException: java.security.NoSuchAlgorithmException: Error constructing implementatio n (algorithm: Default, provider: SunJSSE, class: com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl) java.net.SocketException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: com.sun.net.ssl.internal.ssl.D efaultSSLContextImpl) java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: com.sun.net.ssl.internal.ssl.DefaultSSLContextImpl) java.security.cert.CertificateException: java.security.InvalidKeyException: PublicKey algorithm not implemented: ECPublicK

[Reagan]

How about the files under /sapmnt/SID/global/sapcontrol directory?

If there are conflicting entries then move them to a different location and restart SUM.

[Former Member]

HI Reagan,

I did tried to move files from /sapmnt/SID>/global/sapcontrol directory, but they are again coming as soon as it hit http://<hostname>:5<syd no>13

[Sriram2009]

H Dinesh

Dialog instance uninstall steps are completed without any error message? could you check the uninstall log.

BR

SS

[Former Member]

Hi S,

in my case uninstall not possible, as server long gone, I have to rename folders, remove profile from profile directory , but somehow sap management console detect instance, I need option to clear system from SAP MC, it is stopping me in upgrade

Dinesh

[ashish_vikas]

Can you try to restart sapstartsrv process.

Regards,

Ashish

[Sriram2009]

Hi Dinesh

Better you can reinstall the OS and then do the DI installation

BR