Skip to Content
0

SOLMAN UPGRADE - startsap error

Aug 28, 2017 at 10:32 PM

132

avatar image
Former Member

Hi experts,

When SUM was running in execution phase an error occurred. I noticed that sap instance 00 was down and instance 04 ABAP (shadow) was running. Then SUM stopped with error and I found note 2047880 - The upgrade stops due to sap.com/ui~five application issues when upgrade NW AS JAVA from version 7xx to 740 but it was not possible to connect via telnet hostname 50008 so I set parameter

icm/server_port_3 = PROT=TELNET,PORT=5$(SAPSYSTEM)08,HOST=localhost and restarted instance with no success.

scdadm 51> startsap Checking syb Database Database is not available via R3trans ------------------------------------------- starting database SCD ... Log file: /sybase/SCD/startdb.log parse level 0: identified message 'Database 'master' is now online.' parse level 1: identified message 'Database 'tempdb' is now online.' parse level 2: identified message 'Database 'sybsystemprocs' is now online.' parse level 3: identified message 'Recovery complete.' Recovery Complete startdb completed successfully Starting Startup Agent sapstartsrv /usr/sap/SCD/SYS/exe/uc/linuxx86_64/startsap: line 3171: 5205 Segmentation fault $_SAPSTARTSRV pf=$_PROFILE -D >> $LOGFILE 2>&1 FAIL: Timeout Startup of Instance Service failed See /home/scdadm/startsap_SCS02.log for details ------------------------------------------- solmandes:scdadm 52>

If I execute R3trans -x everything looks fine:

> R3trans -x This is R3trans version 6.26 (release 749 - 24.03.17 - 20:17:03). unicode enabled version R3trans finished (0000). Attached /home/scdadm directory (the only one with updated info)

Any clue?

10 |10000 characters needed characters left characters exceeded

...if the AS Java might not start it is better to have a look on the logs in the Java instance work folder.

(\usr\sap\<AS-JAVA-SystemID>\<central instance>\work)

Please examine the most recent ones (from the last failed startup attempt).

If you still face this issue please post them here to have a look.

0
Former Member

Hi,

None of the work directories were updated.

/usr/SAP/SID/DVEBMGS04/work (shadow)

/usr/SAP/SID/DVEBMGS00/work

/usr/SAP/SID/SCS02/work

/usr/SAP/SID/ASCS01/work

Any clue?

0

1. Would you please change this so that the element.resynch is set to FORCE and then restart the AS JAVA. Please check the below Note in order to check the bootstrap properties file:

710663 - AS Java Bootstrap Synchronization

2. move the entire AS Java work folder content to a different file location.

3. restart the AS Java. Then the AS Java work folder should have some log files. These needs to be analysed.

4. when the AS Java is down one might not access it neither through TELNET, nor P4 .

0
Former Member

Hi Milen,

startsap finally finished successfully.

This is what I did:

delete the exe-directories of all instances

root> cd /usr/sap/SID/DVEBMGS<Sy.Nr. of instance>/exe
root> rm -rf *

root> cd /usr/sap/SID/ASCS<Sy.Nr. of ASCS>/exe
root> rm -rf *

root> cd /usr/sap/SID/SCS<Sy.Nr. of SCS/exe
root> rm -rf *

execute SAPCPE

It is recommended by sap to start sapcpe for every instance. Be aware to use the scs.lst file for the central services and the ERS!

For the central instance:

sidadm> cd /usr/sap/SID/DVEBMGS<Sy.Nr. instance>/work
sidadm> sapcpe pf=/usr/sap/SID/SYS/profile/SID_DVEBMGS<Sy.Nr. instance>_

For the central services:

sidadm> cd /usr/sap/SID/SCS<Sy.Nr. SCS>/work
sidadm> sapcpe pf=/usr/sap/SID/SYS/profile/SID_SCS<Sy.Nr. SCS>_ list:/usr/sap/SID/SYS/exe/run/scs.lst

sidadm> cd /usr/sap/SID/ASCS<Sy.Nr. ASCS>/work
sidadm> sapcpe pf=/usr/sap/SID/SYS/profile/SID_ASCS<Sy.Nr. ASCS>_ list:/usr/sap/SID/SYS/exe/run/scs.lst

Now continuing with the note 2047880 to solve SUM error I am having problems connecting via telnet :

solmandes:scdadm 96> telnet solmandes 50008
Trying 10.254.252.107...
telnet: connect to address 10.254.252.107: Connection refused
solmandes:scdadm 97> telnet solmandes 50000
Trying 10.254.252.107...
telnet: connect to address 10.254.252.107: Connection refused
solmandes:scdadm 98> telnet solmandes 50400
Trying 10.254.252.107...
telnet: connect to address 10.254.252.107: Connection refused
solmandes:scdadm 99> telnet solmandes 50408
Trying 10.254.252.107...
telnet: connect to address 10.254.252.107: Connection refused

Any clue?

Only shadow ABAP (04) is running fine so I am able to connect there via SAPGUI. probably instance 00 is not able because of execution phase in SUM with shadow --->target

Regards.

0
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Asha Pillai
Sep 07, 2017 at 04:39 AM
1

Hello,

In addition to what Milen said, please read these notes to find out if your P4 port is accessible.

1842153 - Telnet console open problem

1925352 - Check access points (or ports) being used by a live SAP JAVA server

1158626 - P4 connection to ICM on machine with multiple IPs fails

Regards,

Asha

Share
10 |10000 characters needed characters left characters exceeded
Milen Dontcheff
Sep 02, 2017 at 11:32 AM
0

If I were you I would have examined which services are listening to which ports...

1.

Output display of these 2 commands:

netstat -ano

tasklist

2.

Match the process name >>> PID >>> IP:port

Again, if the AS Java is down nobody might access it through TELNET. Hence, please cross check whether it is up and running.

Share
10 |10000 characters needed characters left characters exceeded