cancel
Showing results for 
Search instead for 
Did you mean: 

NW 7.01 -> 7.31 Upgrade System appears to be in an unsound state

Former Member
0 Kudos

Hi

We have a system which was previously a dual stack and since then it has been split. We are now trying to upgrade the abap system from NW 7.01 to 7.31. However, the dialog instances seems to be in an "unsound" state. However the central instance is fine. On the Dialog instances, when we run:

sapcontrol -format script -nr 36 -function GetProcessList

21.12.2013 12:34:03

GetProcessList

OK

0 name: disp+work

0 description: Dispatcher

0 dispstatus: YELLOW

0 textstatus: Running, Message Server connection ok, Dialog Queue time: 0.00 sec, J2EE status info unavailable

0 starttime: 2013 12 21 12:11:41

0 elapsedtime: 0:22:22

0 pid: 8912922

1 name: rslgsend

1 description: Central Syslog Sender

1 dispstatus: GREEN

1 textstatus: Running

1 starttime: 2013 12 21 12:11:41

1 elapsedtime: 0:22:22

1 pid: 7274644

2 name: igswd_mt

2 description:

2 dispstatus: GREEN

2 textstatus: Running

2 starttime: 2013 12 21 12:11:42

2 elapsedtime: 0:22:21

2 pid: 11796714

The issue is, the dialog instance is thinking that it still has J2EE. However, I have removed all j2ee and jstart parameters from the instance profile except for the following:

system/type = ABAP

exe/icmbnd = $(DIR_CT_RUN)/icmbnd

rdisp/j2ee_start_control = 0

rdisp/j2ee_start = 0

Can anyone help?

Cheers,

Thusjanthan Kubendranathan

Accepted Solutions (1)

Accepted Solutions (1)

Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos
Former Member
0 Kudos

I have already performed the steps outlined in the Note: 1229586 for removing the Java stack manually. However, no luck.

Reagan
Product and Topic Expert
Product and Topic Expert
0 Kudos

If you have already performed the steps mentioned under "Deleting the Java Stack (Java Add-In) of a Dual-Stack (ABAP+Java) System Manually" then the problem shouldn't be there.

Provide the output for this command for all the nodes

ls -la /usr/sap/SID/D*

ls -la /usr/sap/SID/D36

Also provide the contents of the profiles. (if possible)

Regards

RB

Former Member
0 Kudos

Hi,

As you have checked the note and the issue is still there.

1855360 - *ERROR:* Your system appears to be in an unsound state. Correct the following issues befor...

Can you please check the below section.(Know that you have Split it now)

Release Upgrade: Dual-Stack Additional Appl. Server Instances Must be Reinstalled

When upgrading a dual-stack system, SUM is not able to automatically upgrade additional application server instances.

You must uninstall them manually before entering downtime and reinstall them on the new release after the upgrade. To do this, use the Software Provisioning Manager 1.0 tool and the installation guide for your target release.

1732061 - Central Note - Software Update Manager 1.0 SP07 [lmt_008]

Thanks

Rishi Abrol

Former Member
0 Kudos

I had found the problem. There appeared to be an older stale version of sapstartsrv that was started that wasn't getting cleared on a stopsap. Manually killed it and restarted the dialog instance and that solved the issue.

Cheers,

Thusjanthan Kubendranathan

Answers (0)