on 04-28-2015 12:51 AM
During the prep for migration I'm getting an error stating that the system seems to be in an unsound state.
This can be tested for by running sapcontrol as follows:
sapcontrol -nr 03 -function GetProcessList
28.04.2015 00:38:10
GetProcessList
OK
name, description, dispstatus, textstatus, starttime, elapsedtime, pid
disp+work, Dispatcher, YELLOW, Running but Dialog Queue info unavailable, 2015 04 27 16:05:38, 8:32:32, 1273
igswd_mt, IGS Watchdog, GREEN, Running, 2015 04 27 16:05:38, 8:32:32, 1274
I have not seen any system issues, yet the sapcontrol program clearly is having issues.
I have tested this with both the source kernel (721_REL patch 400) and the target kernel from the SUM directory (742 kernel).
Both give the same error.
(NB I've tried the EXT version on the source level too - 721_REL_EXT)
There is some advise that you can just skip this warning (see 1957443 - Check for system status at upgrade preparation (phase CHECKSYSSTATUS)) - however I would prefer to know what is going on here.
I've also found a note suggesting that this could be something that happens when you remove a Java stack from a system (we just have); however it refers to J2EE status as opposed to Dialog queue info.. 1855360 - *ERROR:* Your system appears to be in an unsound state. Correct the following issues befor...
I'd be very keen to see if anyone else has seen similar issues with SUM during an upgrade.
Additionally all.
Please note I've seen for some people this can be a problem when sapstartsrv isn't up to date with the rest of the kernel (easily possible esp. if you didn't manually kill all SAP processes during kernel updates).
However I did kill these processes and the binaries all look aligned:
sapcontrol -nr 03 -function GetVersionInfo
28.04.2015 09:48:31
GetVersionInfo
OK
Filename, VersionInfo, Time
/usr/sap/<SID>/DVEBMGS03/exe/sapstartsrv, 721, patch 400, changelist 1542873, opt (Dec 6 2014, 04:14:47), linuxx86_64, 2014 12 11 18:36:31
/usr/sap/<SID>/DVEBMGS03/exe/disp+work, 721, patch 400, changelist 1542873, opt (Dec 6 2014, 00:03:44), linuxx86_64, 2014 12 11 18:26:54
/usr/sap/<SID>/DVEBMGS03/exe/gwrd, 721, patch 400, changelist 1542873, opt (Dec 6 2014, 00:03:44), linuxx86_64, 2014 12 06 04:00:56
/usr/sap/<SID>/DVEBMGS03/exe/msg_server, 721, patch 400, changelist 1542873, opt (Dec 6 2014, 04:14:47), linuxx86_64, 2014 12 06 05:08:17
/usr/sap/<SID>/DVEBMGS03/exe/dboraslib.so, 721, patch 400, changelist 1542873, opt (Dec 6 2014, 00:03:44), linuxx86_64, 2014 12 05 23:32:49
/usr/sap/<SID>/DVEBMGS03/exe/dbmssslib.so, 721, patch 400, changelist 1542873, opt (Dec 6 2014, 00:03:44), linuxx86_64, 2014 12 05 23:55:44
/usr/sap/<SID>/DVEBMGS03/exe/dbdb2slib.so, 721, patch 400, changelist 1542873, opt (Dec 6 2014, 00:03:44), linuxx86_64, 2014 12 05 23:29:38
/usr/sap/<SID>/DVEBMGS03/exe/dbdb4slib.so, 721, patch 400, changelist 1542873, opt (Dec 6 2014, 00:03:44), linuxx86_64, 2014 12 05 23:31:50
/usr/sap/<SID>/DVEBMGS03/exe/dbdb6slib.so, 721, patch 400, changelist 1542873, opt (Dec 6 2014, 00:03:44), linuxx86_64, 2014 12 11 18:08:43
/usr/sap/<SID>/DVEBMGS03/exe/enserver, 721, patch 400, changelist 1542873, opt (Dec 6 2014, 04:14:47), linuxx86_64, 2014 12 06 05:11:52
/usr/sap/<SID>/DVEBMGS03/exe/icman, 721, patch 400, changelist 1542873, opt (Dec 6 2014, 04:14:47), linuxx86_64, 2014 12 06 05:05:12
/usr/sap/<SID>/DVEBMGS03/exe/sapwebdisp, 721, patch 400, changelist 1542873, opt (Dec 6 2014, 04:14:47), linuxx86_64, 2014 12 06 05:05:52
/usr/sap/<SID>/DVEBMGS03/exe/jcontrol, 721, patch 400, changelist 1542873, opt (Dec 6 2014, 04:14:47), linuxx86_64, 2014 12 06 05:27:04
/usr/sap/<SID>/DVEBMGS03/exe/jlaunch, 721, patch 400, changelist 1542873, opt (Dec 6 2014, 04:14:47), linuxx86_64, 2014 12 06 05:27:13
/usr/sap/<SID>/DVEBMGS03/exe/jstart, 721, patch 400, changelist 1542873, opt (Dec 6 2014, 04:14:47), linuxx86_64, 2014 12 06 05:25:50
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Jamie,
From the error you mentioned "J2EE status info unavailable".
Is it a dual stack system ? From the output of sapcontrol -nr <XX> -function GetProcessInfo
it do not seem to be dual stack .
So question are : Was this splitted using dual-stack split tool ?
From my experience , I have seen this issue due to following reasons.
1. sapstartsrv was not restarted and was still having status info for j2ee after the split.
in this case try restarting sapstartsrv using below command :
sapcontrol -nr <instance number > -function RestartService
once done, check the status agaib with command :
sapcontrol -nr <instance number> -function GetProcessList
2. There are still j2ee parameters in profiles or j2ee related directories on file system.
### Please note that above is application if this there is no java stack.
Thank you.
BR,
Gaurav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Gaurav,
Yes this was a dual stack system and it has been split using SWPM standard process to delete the Java stack.
However in fact what you state is incorrect. If you re-read my post, I did not mention that "J2EE status info unavailable" at all in the error message. In fact the error doesn't refer to J2EE at all. I have also mentioned that while SAP note 1855360 does seem a partial fit, it doesn't seem to match 100% (though I am anyway checking all traces of the Java stack are gone).
This error can be skipped if the system seems healthy but I'm trying to bottom it out and understand it first.
Regards, Jamie
Hi Jamie
Could you check this SAP KBA
1973276 - System not starting - Process List / GetProcessList does not display the list of processes
BR
SS
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.