Skip to Content
Author's profile photo Former Member

failing upgrade because of a non running server node

Some weeks ago I upgraded an SAP netweaver system (double stack). During the deployment the whole upgrade stopped. In the corresponding log files I didn’t find any hint what might have caused this error. In SCN and the published SAP notes no information for this problem was available.

Later I restarted the upgrade. Parallel to this upgrade I checked the server node status using jcmon. When the deployment started again in SUM the infomation came up that the upgrade process started the server node. But in jcmon this wasn’t happening. This was the error that caused the problem during the earlier upgrade. Here I started the corresponding server node via jcmon. Shortly afterwards the deployment continued and finished successfully.

Please check the status of your server node during an upgrade using jcmon. I used the following procedure and commands to solve the error.

1. stopping the system with

stopsap R3

2. checking the corresponding sdm log for the instance to be started

3. start the corresponding instance with e. g.

startsap DVEBMGS00 <name of ci>

4. check the system using jcmon if the java server had been started with

jcmon pf=<profile>

5. if not restart it using jcmon

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.