Hi Nirav,
Please let me know the version of the SUM tool that you are using . I can see this error in SUM tools 1 SP06 and SP07
Dual stack: Timeout after phase MAIN_UPTRANS/STARTSAP_PUPG due to longer start up of JAVA instance
In phase MAIN_UPTRANS/STARTSAP_PUPG, the Software Update Manager starts the ABAP and JAVA instance. If the starting up of the JAVA instance takes much time, the phase can fail, even though the ABAP instance might be started successfully and the JAVA instance might complete its succesful start up some minutes later.
In this case, the SAPup.ECO logfile in SUM/abap/log has at the end for example the following entry:
EXECUTING /usr/sap/<SID>/<instance>/exe/sapcontrol (sapcontrol) -p
NI_HTTP -host <hostname> -nr <instancenum> -function StartWait 1000
<date> <time>
Start
OK
<date> <time>
StartWait
FAIL: Timeout
The timeout can indicate that the start up just needs more time, such as 16,6 minutes based on the above-mentioned example entry in which the StartWait parameter is 1000, and the calculation is 1000/60.
As you usually know how long your systems needs for a starting up, you can use this calculation to get a hint if it's a timeout or a real start error.
In case it is just a timeout and the system starts, you can wait until the JAVA instance has started and then try the phase again using the Repeat-option.
(Windows only:) Phase MAIN_UPTRANS/STARTSAP_PUPG: Start of AAS instances failed
During an update or upgrade of distributed and high availability systems, the start of additional application server instances fails in phase MAIN_UPTRANS/STARTSAP_PUPG. The reason is that the SAPGLOBALHOST parameter in the instance profiles cannot be analyzed.
To solve the issue, proceed as follows:
- 3. Check the instance profiles of all additional application server instances for a line that starts with #SAPGLOBALHOST.
- 4. Remove the # at the beginning of the line, because this sign changes the line to a comment so that the value of the parameter cannot be analyzed.
- 5. Repeat phase MAIN_UPTRANS/STARTSAP_PUPG.
Additional checks:
Add parameter rdisp/ignore_gw_death = 1 it is useful when you have problems with your message server, in this way you can start SAP and troubleshout the system in an easier way.
Be sure to set sapms and listener in /etc/services:
sapmsSID 39NN/tcp #sap service for SID
lsnrSID 15NN/tcp #sap Oracle listener for SID
Please check that rdisp/msserv parameter is set or not, for some reason it is not set in the source system.
Thanks
Rishi Abrol