on 05-17-2013 7:44 AM
Hi,
Facing a situation where user session of a SAP user is not getting terminated. I tried it terminating through sm04, sm50 and Sm66.
But still the session exists, and everytime user make a login from SAP Logon pad, it shows that SAP-ID is already being executed from its own system.
I went through few threads on this and seen that restarting CI instance is final solution to this.
But I would like to explore an alternative solution so that we do not need to restart CI.
Please suggest.
Regards,
Kris
Hi Kris,
Depending on your OS if you have linux/aix what you can do is verify the user process which DIA process is it using in sm66/sm50 then logon to OS level and cancel the process.
example:
in sm50:
1 | DIA | 15068 | Running | Yes | SAPLTHFB | 000 | DDIC |
On os:
hostname:sidadm 51> ps -ef |grep 1506
sidadm 15068 14591 0 10:06 ? 00:00:05 dw.sapSID_DVEBMGS20 pf=/usr/sap/SID/SYS/profile/SID_DVEBMGSxx_dsidci20
sidadm 19906 19515 0 10:24 pts/0 00:00:00 grep 15068
hostname:sidadm 52> kill 15068
hostname:sidadm 53> ps -ef | grep 15068
sidadm 19918 19515 0 10:24 pts/0 00:00:00 grep 15068
After kill in SM50 work process 1 now has a different PID:
1 | DIA | 19924 | started | Yes | 1 |
For a windows environment it would be similar action.
VERY IMPORTANT:
Kill only the process and not the parent process PPID example:
hostname:sidadm 51> ps -ef |grep 15068
sidadm 15068 14591 0 10:06 ? 00:00:05 dw.sapSID_DVEBMGSxx
15068 - work process ID in use on SAP
14591 - Is sap dispatcher process (if you kill this sap will crash)
hostname:dbwadm 54> ps -ef |grep dw.sap
sidadm 4831 14591 0 09:23 ? 00:00:06 dw.sapSID_DVEBMGS20 pf=/usr/sap/SID/SYS/profile/SID_DVEBMGS20_sidwci20
sidadm 5638 14591 0 09:29 ? 00:00:02 dw.sapSID_DVEBMGS20 pf=/usr/sap/SID/SYS/profile/SID_DVEBMGS20_sidwci20
If you cannot kill process from OS level then you have to restart the instance this is an old and well known bug.
Good luck
Johan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kris,
Killing the process from OS level should help you in this case. If this is a recurring issue then probably you may need to evaluate whether it is some known OS bug or SAP kernel bug and react accordingly.
Hope this helps.
Regards,
Deepak Kori
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
11 | |
10 | |
9 | |
7 | |
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.