cancel
Showing results for 
Search instead for 
Did you mean: 

Disappearing Logon Groups

0 Kudos

Hello experts,

We are facing problem with logon groups after implementation the lastest SPS 15 for NetWeaver 7.4 and updating the 742 64 bit kernel to PL 400.

It seems that the logon groups are not automaticaly updated by report SAPMSSY6. In tx. SMLG -> Load distribution the Sample fields are not automaticaly updated every 5 minutes (only manual update - click on all instances cause update).

We tried to update the kerenl to PL 401, but it don´t solve this problem.

Have anyone a similar experience with this situation?

Thank you very much for any advice

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

The problem is solved.

Solution is in this note https://launchpad.support.sap.com/#/notes/0002356238

Best regards,

Jakub

Answers (1)

Answers (1)

isaias_freitas
Advisor
Advisor
0 Kudos

Hello Jakub,

What is the value of the parameter "rdisp/autoabaptime"? Confirm that it has the default value in place (300).

If the value is correct, do you see any errors at the transaction SM21 or dumps at ST22 every 5 minutes or so?

Regards,

Isaías

0 Kudos

Hello Isaias,

Thank you for your reply.

The rdisp/autoabaptime is in default value = 300 and tx. SM21 and ST22 are clear.

Best regards, Jakub

isaias_freitas
Advisor
Advisor
0 Kudos

Hello Jakub,

You are welcome!

In this case, monitor the transaction SM5B and confirm that all the periodic tasks are being executed (switch to the "result" tab).

Best regards,

Isaías

0 Kudos

Hello Isaias,

Thanks a lot for the next advice .

I think that I have found some problems in this transaction. Some task (BTCSCHED, AUTOABAP, BGRFC_WATCHDOG, AUTOSECURITY) are not incremented ("Count." column) after time interval runs out. I compared this transaction with our others systems and there everything is incremented normaly.

Unfortunatelly I have no idea how to fix this problem 😞 . Do you have any ideas?

I really appreciate any help you can provide.

Best regards,

Jakub Skarke

isaias_freitas
Advisor
Advisor
0 Kudos

Hello Jakub,

You are welcome!

If AUTOABAP is not incrementing, this is the root cause for the logon group issue.

Can you attach the "dev_disp" trace to this thread?

(there is an option to attach a file, so you can attach a "zip" file instead of pasting the whole file at your reply)

If no, what is the SAP kernel release and patch level of the affected system?

Best regards,

Isaías

0 Kudos

´

Hello Isaias,

Thanks a lot again.

"dev_disp" is in attachment.

I think that the problem could be here:

    Tue Jul 26 14:00:48 2016

    DpUpdateStatusFileWith: state=YELLOW, reason=Length of high priority queue exceeds limit

    Tue Jul 26 14:00:50 2016

    DpWpDynCreate: created new work process W14-16580778

    Tue Jul 26 14:05:48 2016

    DpUpdateStatusFileWith: state=YELLOW, reason=Length of high priority queue exceeds limit

    Tue Jul 26 14:06:05 2016

    DpWpCheck: dyn W14, pid 16580778 no longer needed, terminate now

    DpHdlDeadWp: W14 (pid=16580778) terminated automatically

    Tue Jul 26 14:07:26 2016

    DpWpDynCreate: created new work process W12-27001020

    DpUpdateStatusFileWith: state=YELLOW, reason=Length of high priority queue exceeds limit

    DpUpdateStatusFileWith: state=YELLOW, reason=Length of high priority queue exceeds limit

SAP Kernel Information:

    SAP Kernel :  742

    Make Variant :  742_REL

    Database Client Library : OCI_112, 12.1.0.2.0, V2, default

    Created in  :  AIX 1 6 00F79A484C00 use-pr20160702

    Created on  :  Jul  3 2016 19:11:20

    Support Level  :  0

    Kernel Patch No. : 418

    RKS Compatibility Level : 0

    Source ID  :  0.418

    DBSL Patch No. : 401

    ICU Version : 50.1 Unicode Version 6.2

    libsapu16 Version : 1.0025  Jul  1 2016 20:29:31

    CommonCryptoLib Version : 8.4.49 Mar  4 2016

    Supported Environment

SAP Database Version

    740

    Database

    ORACLE 11.2.*.*.*

    ORACLE 12.*.*.*.*

Operating Sys.

    aix 1 6

    aix 1 7

Message server release:

    Release = 742

    Release no = 7420

    System name = SG1

    kernel information

    kernel release = 742

    database library =

    compiled on = AIX 1 6 00F79A484C00 use-pr20160702

    compiled time = Jul  3 2016 19:11:03

    update level = 0

    patch number = 400

    source id = 0.418

SAPKB level:

    SAP_BASIS    740    0015    SAPKB74015        SAP Basis Component

    SAP_ABA        740    0015    SAPKA74015        Cross-Application Component

    SAP_GWFND    740    0015    SAPK-74015INSAPGWFND    SAP Gateway Foundation 7.40

    SAP_UI        740    0016    SAPK-74016INSAPUI    User Interface Technology 7.40

    PI_BASIS    740    0015    SAPK-74015INPIBASIS    Basis Plug-In

    ST-PI        740    0003    SAPK-74003INSTPI    SAP Solution Tools Plug-In

    SAP_BW        740    0015    SAPKW74015        SAP Business Warehouse

    GRCFND_A    V1100    0012    SAPK-V1112INGRCFNDA    GRC Foundation ABAP

    GRCPINW        V1100_731    0013    SAPK-11513INGRCPINW    SAP GRC NetWeaver Plug-In

    ST-A/PI        01S_731    0000    -            Servicetools for SAP Basis 731

Thank you.

Best regards,

Jakub Skarke

isaias_freitas
Advisor
Advisor
0 Kudos

Hello Jakub,

The root cause is not very clear to me, yet.

However, it could be related to the trace entries you have found.

I have analyzed the Dispatcher trace, and I also see dynamic work processes being created frequently.

The Dispatcher creates them when there are no free processes to handle requests.

I believe that what you could do is to add more dialog work processes and then monitor the system to see whether the issue reoccurs.

Best regards,

Isaías

0 Kudos

Hello,

I tried to update disp+work package to newest PL422 and it seems, that the problem disappeared.

I will continue to monitor the logon groups.

Best regards,

Jakub