Number of DIA work processes

Hello,
How do we decide the maximum number of DIA work processes (or total number of work processes including others like BGD, SPO, etc) that our server/hardware will support?
Secondly, we found that in the instance profile for one app server, parameter value for number of DIA is set as 30. However, in the SM50 for that instance, we only found 25 DIA work processes (no changes were made after system start in RZ03/RZ04). Any inputs?
Regards,
NK

When the instance is started, as many work processes as the sum of the following parameters are started:
rdisp/wp_no_dia
rdisp/wp_no_vb
rdisp/wp_no_vb2
rdisp/wp_no_enq
rdisp/wp_no_bt
rdisp/wp_no_spo
rdisp/wp_no_restricted
The sum of the parameters must be smaller or equal to the value of parameter rdisp/wp_max_no
From <http://help.sap.com/saphelp_nwpi71/helpdata/en/46/c24a5fb8db0e5be10000000a1553f7/frameset.htm>
Please let me know if your sum> rdsip/wp_max_no ?

Similar Messages

  • Maximum number of dialog work process

    Hello gurus,
    Could you please let me know what is the maximum number of dialog work process that you can configure in an Netweaver system with ABAP 7.0 before considering to install a new application server to distribute the load?
    Thaks for your help,
    Best regards

    > Just one question, according to the following statement, can I think that I should estimate a usage of 1/4 CPU core by every dialog WP?
    No, this was just an example to make clear what I mean.
    > Do you know any SAP note that could help me to estimate the number of WP according to the load of the system?
    There is no such note and there can't be.
    You could have a system with e. g. 100 users where 10 of them do really produce load, the other 90 may just run a few transactions or do just nothing - so 50 WPs is too much. You could also have a system with 20 users where ALL are entering data all data and doing reporting and stuff so 20 WPs is too less. There may also be processes like ATP that use one background worprocess and spawn a number of dialog WPs you configure in the application. If you configure too few of them, the ATP run will run very log, if you configure too much, the system will be overloaded and slowing down. I can imagine dozens of other examples what may cause load or not.
    Because of that it's not possible to give a formular how many WPs to be configured for how many users.
    This is a tuning thing and needs to be estimated in the first weeks after a GoLive; watch the system, reconfigure, watch. Check ST03N and SM50/SM66 or book an early watch after some time, they have rough estimates and give usually good advises. Out of theory it's almost impossible to predict something.
    Markus

  • What is the Max Number of Total Work Process that we can Have on  One C.I

    Hi,
    What is the Max Number of Total Work Process that we can have on a Single C.I
    Is there any Limit that We can only have Perticular Number of Total work process ?
    Or it is just Unlimited number of total work process
    Thanks & Regards
    Dan.

    from the system throughput point of view a rule of a thumb is:
    1 up to 4 sometimes 5 workprocesses per CPU.
    (one is used in Benchmarks where you have a very small number of transactions running with a small amount of database accesses)
    you can easily find it out:
    configure 4 WPs per CPU. If you have a number of WP's consuming nearly no CPU time you can reduce the number of WPs.
    regards
    Peter

  • Stop DIA work process with PRIV mode.

    Hi,
    How to stop DIA workprocess with PRIV mode. by searching notes, I find it is possible to setl the max time and max number of the private memory.
    Kind regards,
    Masaaki

    Hello Masaaki,
    Before deciding whether to wait for the process to finish by itself or not, i would suggest that you find out the program which is causing the work process to go into PRIV mode. Once this is done, as your technical guys (ABAP) to analyse why this is happening (is the program logic inefficient and hence using so much memory etc).
    You have to note that (Dialog) work processes going into PRIV mode is not a healthy sign for the SAP application server.
    This is beacuse once the WP goes into PRIV mode it is not available to any other transactions, and we only have a limited number of work processes.
    Please make sure the parameters below are defined in RZ10 instance profile:
    rdisp/max_priv_time - used to define the maximum time that a work process can remain in PRIV mode. (After this the work processes is terminated and restarted). This is reasonable because beyond the time limit set, it is imperative to assume that the program using the work process is in efficient. (in case a program really needs that much time, it needs to be scheduled as a background job).
    rdisp/wppriv_max_no- this parameter defines the maximum number of work processes that can be in PRIV mode. Very useful.
    Also, make sure that a parameter ABAP/heaplimit is defined. This ensures that if a program eats up a certain amount of heap memory, the work process being used can be terminated.
    And finally please do check if your extended memory allocation is not big enough. the parameter em/initial_size_mb defines the fixed size of extended memory. Increasing this size only if you find that a lot of processes are frequently going into PRIV mode.
    Hope this helps.
    Regards,
    Prashant

  • Increase the number of background work processes for data load performance

    Hi all,
    There are 10 available background work processes in the BW system. We're doing some mass load to multiple ODS.But system uses only 3 background processes. How can i
    increase the number of used background work processes for new data load.
    I tried to change number of prosesses with RSODSO_SETTINGS. But no successes. Are there any other settings need to change?
    thanks,
    Yigit

    Hi sankar,
    I entered the max proc. number into ROIDOCPRMS. But it doesn't make difference. System still uses only 3 of background processes. RSCUSTA2 is replaced with
    RSODSO_SETTINGS in BI 7.0 and this trans. can only change the processes for data activation, SID generation and rollback. I need to change the process numbers for data extraction.

  • How to find out number of background work processe available in the system?

    Hi All,
    I have a FM that triggers a background job using JOB_OPEN, ABAP_SUBMIT and JOB_CLOSE. But the problem is if there are no background work processes available at that moment, it does not return error. Not sure whether the job is even scheduled!
    Is there a way to find out if there are any background work processes available in the system? I know a FM SPBT_INITIALIZE which gives info about dialog work processes. Is there any other FM similar to this which gives info about background wp??
    Regards,
    Shailesh

    your Job will remain in a queue by message handler. once workprocess is free, your job gets scheduled
    by the way, you can use the functionality used in FM TH_DISPLAY_WORKPROCESS_LIST to read the workprocesses
    the command which gets you the workprocess is:
    CALL 'ThWpInfo' ID 'OPCODE' FIELD OPCODE_WP_LIST
                      ID 'TAB' FIELD LIST_STATE_WPLST-TABL
                      ID 'CPU' FIELD LIST_STATE_WPLST-CPU.
    check how its written in include LSDEBF01, form SET_LIST_WPLST
    Edited by: Soumyaprakash Mishra on Dec 12, 2011 12:17 PM

  • Stop DIA work process with PRIV mode in my program

    Hello,
    I  write Program that display in the end an alv report and when i display it after same time my dia wp get in PRIV mode
    I search about it and I didn't find the solution but it happend only with my program this reject the memory parameter that cause the problem
    Thanks for your help

    Hi,
    >I think this not the problem because in the dev and the qa system it won't get in priv thanks
    >mode and the have the same value in the parameter ztta/roll_extension and the qa is the copy of the prod but 3 month old
    And these 3 months difference can perfectly explain why you have the problemn on production and not on QA.
    Private modes are generated usually because of badly designed programs (including standard ones...).
    ALV is not designed to display a huge amoiunt of data.
    Beware also of internal tables : Abap programmer usually abuse internal tables thinking memory is an unlmimited ressource...
    Just a few ideas.
    Regards,
    Olivier

  • Function called IN BACKGROUND TASK goes to work process DIA, not BGD

    I'm calling a function IN BACKGROUND TASK
    In SM50, I see it running in a DIA work process.
    I want it to run in a BGD work process.
    Can this be done?  If so, how?  If not, why not?

    Hi...
    It looks like, it will always run in DIA process and not Background process...I am not sure that we can change the work process
    Check the below link..
    http://help.sap.com/saphelp_40b/helpdata/pt/69/c24f864ba111d189750000e8322d00/content.htm
    What is written in the link is...
    "Background updates (CALL FUNCTION IN BACKGROUND TASK) represent a variant of remote function call that is synchronous with the end of a transaction (COMMIT WORK). In background updating, an update is run in another dialog work process that may be in the same or in another application server and R/3 System. Because such updates run in their own LUWs, they may start only after all critical updates have been completed. Otherwise, it would not be possible to roll back background changes in the event of an error in another update component. "
    IF you get the answer of whether we can change the work process then please let us know...

  • "disp+work" process in not getting started after kernel upgradation

    Hello Experts,
    Good day…..,
    I am new to SAP. I installed SAP ECC6 EHP4 with default kernel version 701 and it was working fine.
    I have upgraded kernel version from 701 to 741, but the “disp+work” process is not getting started after kernel upgrade.
    I have posted “dev_W0” log &
    “disp+work” command result obtained in CMD prompt of respective server.
    Please help me out in this. Thanks all in advance.
    “dev_w0” Log”
    trc file: "dev_w0", trc level: 1, release: "741"
    *  ACTIVE TRACE LEVEL           1
    *  ACTIVE TRACE COMPONENTS      all, MJ
    M sysno      55
    M sid        TNG
    M systemid   562 (PC with Windows NT)
    M relno      7410
    M patchlevel 0
    M patchno    42
    M intno      20020600
    M make multithreaded, Unicode, 64 bit, optimized
    M profile D:\usr\sap\TNG\SYS\profile\TNG_DVEBMGS55_ABTHMSSB01
    M pid        2392
    M

    M Wed Jul 23 02:04:35 2014
    M  kernel runs with dp version 208000(ext=117000) (@(#) DPLIB-INT-VERSION-208000-UC)
    M  length of sys_adm_ext is 500 bytes
    M  ***LOG Q0Q=> tskh_init, WPStart (Workp. 0 2392) [dpInit.c 731]
    M  DpCommonParamInit: rdisp/core_file_size = default --> no change
    I  MtxInit: 30000 0 0

    M Wed Jul 23 02:04:36 2014
    M  DpIPCInit2: read dp-profile-values from sys_adm_ext
    M  DpShMCreate: alloate/attach shared memory (mode=ATTACH)
    M  DpShMCreate: sizeof(wp_adm)                         24288    (1104)
    M  DpShMCreate: sizeof(tm_adm)                          51472080             (256080)
    M  DpShMCreate: sizeof(ca_adm)                           432000  (72)
    M  DpCommTableSize: max/headSize/ftSize/tableSize=500/16/7464064/7583152
    M  DpShMCreate: sizeof(comm_adm)                   7583152                (14904)
    M  DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
    M  DpShMCreate: sizeof(slock_adm)                      0              (296)
    M  DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    M  DpShMCreate: sizeof(file_adm)                         0              (80)
    M  DpSockTableSize: max/headSize/ftSize/tableSize=500/16/520064/520080
    M  DpShMCreate: sizeof(sock_adm)                       520080  (1016)
    M  DpShMCreate: sizeof(vmc_adm)                       0              (3208)
    M  DpShMCreate: sizeof(wall_adm)                        (ft=41664/fi=67472/hd=64/rec=192)
    M  DpShMCreate: sizeof(amc_rec_adm)                              (ft=86464/fi=67472/hd=64/rec=416)
    M  DpShMCreate: sizeof(websocket_adm)                         (ft=28864/hd=64/rec=272)
    M  DpShMCreate: sizeof(gw_adm)          64
    M  DpShMCreate: sizeof(j2ee_adm)       3936
    M  DpShMCreate: SHM_DP_ADM_KEY                  (addr: 00000000103D0050, size: 60433936
    M  DpShMCreate: allocated sys_adm at 00000000103D0250
    M  DpShMCreate: allocated wp_adm_list at 00000000103E20F0
    M  DpShMCreate: allocated wp_adm at 00000000103E2410
    M  DpShMCreate: allocated tm_adm_list at 00000000103E84F0
    M  DpShMCreate: allocated tm_adm at 00000000103E8730
    M  DpShMCreate: allocated ca_adm at 00000000134FF000
    M  DpShMCreate: allocated comm_adm at 0000000013568980
    M  DpShMCreate: system runs without slock table
    M  DpShMCreate: allocated sock_adm at  0000000013CA4130
    M  DpShMCreate: allocated vmc_adm_list at 0000000013D232C0
    M  DpShMCreate: system runs without VMC
    M  DpShMCreate: allocated gw_adm at 0000000013D23560
    M  DpShMCreate: allocated j2ee_adm at 0000000013D237A0
    M  DpShMCreate: allocated ca_info at 0000000013D24900
    M  DpShMCreate: allocated wall_adm (ft) at 0000000013D24B40
    M  DpShMCreate: allocated wall_adm (fi) at 0000000013D2F000
    M  DpShMCreate: allocated wall_adm (head) at 0000000013D3F990
    M  DpShMCreate: allocated amc_rec_adm (ft) at 0000000013D3FBD0
    M  DpShMCreate: allocated amc_rec_adm (fi) at 0000000013D54F90
    M  DpShMCreate: allocated amc_rec_adm (head) at 0000000013D65920
    M  DpShMCreate: allocated websocket_adm (ft) at 0000000013D65B60
    M  DpShMCreate: allocated websocket_adm (head) at 0000000013D6CE20
    M  DpShMCreate: initialized 21 eyes
    M  DpCommAttachTable: attached comm table (header=0000000013568980/ft=0000000013568990/fi=0000000013C86E10)
    M  DpSockAttachTable: attached sock table (header=0000000013CA4130/ft=0000000013CA4140)
    X  EmInit: MmSetImplementation( 2 ).
    X  MM global diagnostic options set: 0
    X  <ES> client 0 initializing ....
    X  <ES> EsILock: use Semphore 33 for locking
    X  Using implementation view
    X  <EsNT> Using memory model view.
    M  <EsNT> Memory Reset disabled as NT default
    X  ES initialized.

    X Wed Jul 23 02:04:37 2014
    X  mm.dump: set maximum dump mem to 96 MB
    M  ThStart: taskhandler started
    M  ThInit: initializing DIA work process W0

    M Wed Jul 23 02:04:44 2014
    M  ThInit: running on host ABTHMSSB01
    I  MtxInit: 0 0 0

    M Wed Jul 23 02:04:45 2014
    M  calling db_connect ...
    B  Loading DB library 'D:\usr\sap\TNG\DVEBMGS55\exe\dboraslib.dll' ...
    B  Library 'D:\usr\sap\TNG\DVEBMGS55\exe\dboraslib.dll' loaded
    B  Version of 'D:\usr\sap\TNG\DVEBMGS55\exe\dboraslib.dll' is "741.10", patchlevel (0.42)
    C  Prepending D:\usr\sap\TNG\DVEBMGS55\exe to Path.
    C  Register application info.

    C Wed Jul 23 02:04:47 2014
    C  Oracle client version: 10.2.0.4.0, (dbsl 741 040714, UNICODE[2])
    C  Detailed Oracle client (patch) info not available.
    C  *** ERROR => Connect via SAPUSER not supported for kernel >= 740.
    [dbsloci.c    2406]
    C     Only Secure Connect method possible.
    M  ***LOG R19=> ThDbConnect, db_connect ( DB-Connect 000256) [thDatabase.c 76]
    M  in_ThErrHandle: 1
    M  *** ERROR => ThInit: db_connect (step TH_INIT, thRc ERROR-DB-CONNECT_ERROR, action STOP_WP, level 1) [thxxhead.c   2281]
    M Wed Jul 23 02:04:48 2014

    M  Info for wp 0

    M    pid = 2392
    M    severity = 0
    M    status = 0
    M    stat = WP_NEW
    M    waiting_for = NO_WAITING
    M    workerType = DP_WORKER_DIAWP
    M    act_cs_count = 0
    M    csTrack = 0
    M    csTrackRwExcl = 0
    M    csTrackRwShrd = 0
    M mode_cleaned_counter = 0
    M    control_flag = 0
    M    report = > <
    M    action = 0
    M    tab_name = >                              <

    M  ThIErrHandle: no current incoming request


    M *****************************************************************************
    M  *
    M  *  LOCATION SAP-Server ABTHMSSB01_TNG_55 on host ABTHMSSB01 (wp 0)
    M  *  ERROR ThInit: db_connect
    M  *
    M  *  TIME Wed Jul 23 02:04:48 2014
    M  *  RELEASE 741
    M  *  COMPONENT Taskhandler
    M  *  VERSION 1
    M  *  RC 16797709
    M  *  MODULE D:/depot/bas/741_REL/src/krn/si/th/thxxhead.c
    M  *  LINE 2470
    M  *  COUNTER 1
    M  *
    M  *****************************************************************************

    M  PfRejectStatistic: clear statistic record
    M  PfClearAllRec: clear statistic area
    M  PfClearAllRec: statRecordAction = STAT_RECORD_ACTION_REJECT
    M  Entering TH_CALLHOOKS
    M  ThCallHooks: call hooks for event BEFORE_DUMP
    M  ThIErrHandle: entering ThSetStatError
    M  ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
    M  call ThrShutDown (1)...
    M  ***LOG Q02=> wp_halt, WPStop (Workp. 0 2392) [dpnttool.c 335]
    “Desp+Work” Command result:
    C:\Users\tngadm>disp+work
    disp+work information
    kernel release 741
    kernel make variant 741_REL
    compiled on NT 6.0 6002 x86 MS VC++ 16.00 for NTAMD64
    compiled for                  64 BIT
    compilation mode UNICODE
    compile time Jul  9 2014 16:39:46
    update level 0
    patch number 42
    source id 0.042
    RKS compatibility level 0
    supported environment
    database (SAP, table SVERS) 700
    710
    701
    702
    703
                                  711
    720
    730
    731
    732
    738
    740
    operating system
    Windows NT 5.1
    Windows NT 5.2
    Windows NT 6.0
    Windows NT 6.1
    Windows NT 6.2
    Windows NT 6.3
    C:\Users\tng

    C  *** ERROR => Connect via SAPUSER not supported for kernel >= 740.
    [dbsloci.c    2406]
    C     Only Secure Connect method possible.
    For this issue you need to set up SSFS.
    1639578 - SSFS as password storage for primary database connect
    I am new to SAP. I installed SAP ECC6 EHP4 with default kernel version 701 and it was working fine.
    I have upgraded kernel version from 701 to 741
    Are you sure kernel 741 is compatible with an EHP 4 system ?
    Read this SAP note
    1969546 - Release Roadmap Kernel 740
    Regards
    RB

  • Dispatcher Not Running work process stop.

    HI,
    I am facing this problem while installing SAP PI 7.3 on RHEL6 with Oracle. During installation it stops at when it will start instance and when I check found having some issue with dispatcher. Below are the few logs which I found during installation no issue with oracle starting properly and not having any issue with R3trans -d.
    Dev_dpmon
    trc file: "dev_dpmon", trc level: 1, release: "720"
    sysno      00
    sid       
    systemid   390 (AMD/Intel x86_64 with Linux)
    relno      7200
    patchlevel 0
    patchno    90
    intno      20020600
    make       single threaded, Unicode, 64 bit, optimized
    profile   
    pid        14944
    Sun May 29 20:46:43 2011
    kernel runs with dp version 130000(ext=118000) (@(#) DPLIB-INT-VERSION-129000-UC)
    length of sys_adm_ext is 588 bytes
    ERROR => DpSysAdmExtCreate: ShmCreate (ATTACH) failed (3) [dpxxtool2.c  691]
    ERROR => DpIPCInit2: DpSysAdmExtCreate [dpxxtool2.c  408]
    ERROR => DpMonInit: DpExtProcAttach [dpxxmon.c    1081]
    ERROR => main: DpMonInit [dpxxmon.c    579]
    And Dev_w0
    trc file: "dev_w0", trc level: 2, release: "720"
    ACTIVE TRACE LEVEL           2
    ACTIVE TRACE COMPONENTS      all, MJ
    M Sun May 29 22:43:59 2011

    M  command line arg 0:     dw.sapAX2_DVEBMGS50
    M  command line arg 1:     pf=/usr/sap/AX2/SYS/profile/AX2_DVEBMGS50_sachin

    M sysno      50
    M sid        AX2
    M systemid   390 (AMD/Intel x86_64 with Linux)
    M relno      7200
    M patchlevel 0
    M patchno    90
    M intno      20020600
    M make       single threaded, Unicode, 64 bit, optimized
    M profile    /usr/sap/AX2/SYS/profile/AX2_DVEBMGS50_sachin
    M pid        2661
    M
    M  kernel runs with dp version 130000(ext=118000) (@(#) DPLIB-INT-VERSION-129000-UC)
    M  length of sys_adm_ext is 588 bytes
    M  DpWpCreate: W0 started
    M  DpFreeResources(pid=2661)
    M  NiICloseHandle: shutdown and close hdl 1/sock 8
    M  DpDelSocketInfo: del info for nihdl 9 (pos/type=1/1)
    M  NiICloseHandle: shutdown and close hdl 9/sock 9 - sock 10
    M  clear adfunctable
    M  DpSlicFreeResources: free license server resources
    M  prctl(PR_SET_UNALIGN): generate SIGBUS on unaligned user access disabled.
    M  ThStart: th_step = TH_INIT
    M  ThStart: taskhandler started
    M  SemSetCb: set callbacks (tryLockCb/lockedCb/releasedCb/tryErrorCb=5b3773/5b37c9/5b37fd/5b3856)
    M  SigIRegisterExitRoutine: exithandler installed (ThSigHandler)
    M  SigIRegisterRoutine: handler for signal SIGQUIT installed (ThSigIgnoreHandler)
    M  SigIRegisterRoutine: handler for signal SIGCHLD installed (SIG_DFL)
    M  ThrRegisterHooks: register basic hooks
    M  SosRegisterHook: add hook >ThrBtcStartUp(6bb2c2)< (condition/order=0xf/1) for event AFTER_MSG_UP
    M  SosRegisterHook: add hook >ThrBtcStartUp(6bb2c2)< (condition/order=0xf/1) for event AFTER_OPMODE_SWITCH
    M  SosRegisterHook: add hook >ThrtRaiseStopEvent(6b8efa)< (condition/order=0xf/1) for event SOFT_SHUTDOWN
    M  SosRegisterHook: add hook >ThrtFinishSoftShutdownTest(6b8ea4)< (condition/order=0xf/1) for event FINISH_SOFT_SHUTDOWN_TEST
    M  SosRegisterHook: add hook >ThrSaveSPAFields(6bad2c)< (condition/order=0xf/1) for event BEFORE_DUMP
    M  SosRegisterHook: add hook >db_init(16d17f0)< (condition/order=0xf/1) for event CREATE_SHM
    M  SosRegisterHook: add hook >ThVBDbaRequired(62d600)< (condition/order=IF_ROLLED_IN/1) for event DB_ADMIN_REQUIRED
    M  SosRegisterHook: add hook >ThrRegisterSem(64b3e0)< (condition/order=0xf/1) for event BEFORE_DB_CONNECT
    M  SosRegisterHook: add hook >ThrBtcCallLgCl(6bb258)< (condition/order=0xf/1) for event BEFORE_DUMP
    M  ThrRegisterHooks o.k.
    M  ThInit: initializing DIA work process W0
    M  eppSetEnvironment: set component = 1, version = 3, allocFunc = 54de70, freeFunc = 6077d7, traceFunc = 6077f9, traceLevel = 2
    M  ThInit: ThEppInit o.k.
    M  
    M  ***LOG Q01=> ThInit, WPStart (Workp. 0 1 2661) [thxxhead.c   1318]
    M  
    M  ThSetTraceLevel: save trace level
    M  iRng_InitHighResTimer() : Use default timer = 0;   Resolution of timer: 1000000000
    M  -
    M Sun May 29 22:44:05 2011
    M  -
    M  Rng_PseudoRandomInit() : Initialization of the Pseudo-RNG  (128/128/256)
    M  -
    M  NiHLFlush: cache flushed
    M  NiSrvLFlush: service cache flushed
    M  ThInit: dummy spa pointer = 631dca0
    M  ThInit: save spa pointer 7f9c7b18e1a0
    M  ThInitCpicStack: init cpic stack
    M  ThInit: running on host sachin
    M  ThPrivInit o.k.
    M  ThSysUsrCheck (1,1): check system user T0/U1/M0
    M  ThIEmFree: em state of T0/M0 (em_hdl=-1) is DP_EM_NO_CONTEXT
    M  ThSysUsrCheck: clear T0
    M  DpITmSlotClear: clear slot T0
    M  ThCallHooks: call hook >ThrRegisterSem< for event BEFORE_DB_CONNECT
    M  SosRegisterSem: malloc/realloc table
    M  SosRegisterSem: add sem >SEM_TM_ADM_KEY< for wptype 0x77
    M  SosRegisterSem: add sem >SEM_COMM_ADM_KEY< for wptype 0x77
    M  SosRegisterSem: add sem >SEM_STAT_KEY< for wptype 0x73
    M  SosRegisterSem: add sem >SEM_SHM_ADM_AREA_KEY< for wptype 0x73
    M  SosRegisterSem: add sem >SEM_REQ_QUEUE_KEY< for wptype 0x77
    M  SosRegisterSem: add sem >SEM_REQ_QUEUE_DIA_KEY< for wptype 0x77
    M  SosRegisterSem: add sem >SEM_REQ_QUEUE_NOWP_KEY< for wptype 0x77
    M  SosRegisterSem: add sem >SEM_MSBUF< for wptype 0x73
    M  SosRegisterSem: add sem >SEM_ASTAT_KEY< for wptype 0x73
    M  SosRegisterSem: add sem >SEM_PROFILE< for wptype 0x73
    M  SosRegisterSem: malloc/realloc table
    M  SosRegisterSem: add sem >SEM_THRUN_ADM< for wptype 0x73
    M  SosRegisterSem: add sem >SEM_VMC_ADM< for wptype 0x73
    M  SosRegisterSem: add sem >SEM_PXA_KEY< for wptype 0x73
    M  ThrRegisterSem: init SEM_PXA_KEY o.k.
    M  SosRegisterSem: add sem >SEM_ROLL_ADM_KEY< for wptype 0x73
    M  ThrRegisterSem: init SEM_ROLL_ADM_KEY o.k.
    M  SosRegisterSem: add sem >SEM_PAGING_KEY< for wptype 0x73
    M  ThrRegisterSem: init SEM_PAGING_KEY o.k.
    M  SosRegisterSem: add sem >SEM_CALI_BUFFER< for wptype 0x73
    M  ThrRegisterSem: init SEM_CALI_BUFFER o.k.
    M  SosRegisterSem: add sem >SEM_CCC_KEY< for wptype 0x73
    M  ThrRegisterSem: init SEM_CCC_KEY o.k.
    M  SosRegisterSem: add sem >SEM_VB_KEY< for wptype 0x73
    M  ThrRegisterSem: init SEM_VB_KEY o.k.
    M  SosRegisterSem: add sem >SEM_PRES_BUF< for wptype 0x73
    M  ThrRegisterSem: init SEM_PRES_BUF o.k.
    M  SosRegisterSem: add sem >SEM_DB_TBUFF< for wptype 0x73
    M  ThrRegisterSem: init SEM_DB_TBUFF o.k.
    M  SosRegisterSem: malloc/realloc table
    M  SosRegisterSem: add sem >SEM_DB_SYNC< for wptype 0x73
    M  ThrRegisterSem: init SEM_DB_SYNC o.k.
    M  SosRegisterSem: add sem >SEM_DB_TTAB< for wptype 0x73
    M  ThrRegisterSem: init SEM_DB_TTAB o.k.
    M  SosRegisterSem: add sem >SEM_DB_SNTAB< for wptype 0x73
    M  ThrRegisterSem: init SEM_DB_SNTAB o.k.
    M  SosRegisterSem: add sem >SEM_DB_IREC< for wptype 0x73
    M  ThrRegisterSem: init SEM_DB_IREC o.k.
    M  SosRegisterSem: add sem >SEM_DB_FTAB< for wptype 0x73
    M  ThrRegisterSem: init SEM_DB_FTAB o.k.
    M  SosRegisterSem: add sem >SEM_LOGFILE_KEY< for wptype 0x77
    M  ThrRegisterSem: init SEM_LOGFILE_KEY o.k.
    M  SosRegisterSem: add sem >SEM_DB_TBUFF_P< for wptype 0x73
    M  ThrRegisterSem: init SEM_DB_TBUFF_P o.k.
    M  SosRegisterSem: add sem >SEM_ENQ_REQ_KEY< for wptype 0x77
    M  ThrRegisterSem: init SEM_ENQ_REQ_KEY o.k.
    M  SosRegisterSem: add sem >SEM_ENQ_TABLE_KEY< for wptype 0x77
    M  ThrRegisterSem: init SEM_ENQ_TABLE_KEY o.k.
    M  SosRegisterSem: add sem >SEM_SAPCOM_1< for wptype 0x73
    M  ThrRegisterSem: init SEM_SAPCOM_1 o.k.
    M  SosRegisterSem: malloc/realloc table
    M  SosRegisterSem: add sem >SEM_SAPCOM_2< for wptype 0x73
    M  ThrRegisterSem: init SEM_SAPCOM_2 o.k.
    M  SosRegisterSem: add sem >SEM_VMS_FIXADR_KEY< for wptype 0x73
    M  ThrRegisterSem: init SEM_VMS_FIXADR_KEY o.k.
    M  SosRegisterSem: add sem >SEM_DB_CUA_BUFFER< for wptype 0x73
    M  ThrRegisterSem: init SEM_DB_CUA_BUFFER o.k.
    M  SosRegisterSem: add sem >SEM_RSPO_ADMIN< for wptype 0x73
    M  ThrRegisterSem: init SEM_RSPO_ADMIN o.k.
    M  SosRegisterSem: add sem >SEM_DB_OBJ_BUFFER< for wptype 0x73
    M  ThrRegisterSem: init SEM_DB_OBJ_BUFFER o.k.
    M  SosRegisterSem: add sem >SEM_CCMS_AS_MONI_KEY< for wptype 0x77
    M  ThrRegisterSem: init SEM_CCMS_AS_MONI_KEY o.k.
    M  SosRegisterSem: add sem >SEM_EG_ADM< for wptype 0x77
    M  ThrRegisterSem: init SEM_EG_ADM o.k.
    M  SosRegisterSem: add sem >SEM_STAT_BUF< for wptype 0x73
    M  ThrRegisterSem: init SEM_STAT_BUF o.k.
    M  SosRegisterSem: add sem >SEM_WP_ADM_KEY< for wptype 0x73
    M  ThrRegisterSem: init SEM_WP_ADM_KEY o.k.
    M  SosRegisterSem: add sem >SEM_RSPO_CACHE< for wptype 0x73
    M  ThrRegisterSem: init SEM_RSPO_CACHE o.k.
    M  SosRegisterSem: malloc/realloc table
    M  SosRegisterSem: add sem >SEM_AUDIT_SHM< for wptype 0x73
    M  ThrRegisterSem: init SEM_AUDIT_SHM o.k.
    M  SosRegisterSem: add sem >SEM_RSPO_RFC< for wptype 0x73
    M  ThrRegisterSem: init SEM_RSPO_RFC o.k.
    M  SosRegisterSem: add sem >SEM_AB_VMIT< for wptype 0x73
    M  ThrRegisterSem: init SEM_AB_VMIT o.k.
    M  SosRegisterSem: add sem >SEM_ENQID_KEY< for wptype 0x73
    M  ThrRegisterSem: init SEM_ENQID_KEY o.k.
    M  SosRegisterSem: add sem >SEM_ATRA_KEY< for wptype 0x73
    M  ThrRegisterSem: init SEM_ATRA_KEY o.k.
    M  SosRegisterSem: add sem >SEM_COV_KEY< for wptype 0x73
    M  ThrRegisterSem: init SEM_COV_KEY o.k.
    M  SosRegisterSem: add sem >SEM_ZDATE_TIMEINFO< for wptype 0x73
    M  ThrRegisterSem: init SEM_ZDATE_TIMEINFO o.k.
    M  SosRegisterSem: add sem >SEM_DB_OTR_BUFFER< for wptype 0x73
    M  ThrRegisterSem: init SEM_DB_OTR_BUFFER o.k.
    M  SosRegisterSem: add sem >SEM_DB_ESM_BUFFER< for wptype 0x73
    M  ThrRegisterSem: init SEM_DB_ESM_BUFFER o.k.
    M  SosRegisterSem: add sem >SEM_RTM_KEY< for wptype 0x73
    M  ThrRegisterSem: init SEM_RTM_KEY o.k.
    M  SosRegisterSem: malloc/realloc table
    M  SosRegisterSem: add sem >SEM_JAVA_1< for wptype 0x1
    M  ThrRegisterSem: init SEM_JAVA_1 o.k.
    M  SosRegisterSem: add sem >SEM_DBG_SESSION_BPS< for wptype 0x73
    M  ThrRegisterSem: init SEM_DBG_SESSION_BPS o.k.
    M  SosRegisterSem: add sem >SEM_HST_KEY< for wptype 0x73
    M  ThrRegisterSem: init SEM_HST_KEY o.k.
    M  ThCallHooks: hook >ThrRegisterSem< o.k.
    M  calling db_connect ...
    B  Loading DB library '/usr/sap/AX2/DVEBMGS50/exe/dboraslib.so' ...
    M  DlLoadLib() success: dlopen("/usr/sap/AX2/DVEBMGS50/exe/dboraslib.so"), hdl 0
    B  Library '/usr/sap/AX2/DVEBMGS50/exe/dboraslib.so' loaded
    B  Version of '/usr/sap/AX2/DVEBMGS50/exe/dboraslib.so' is "720.00", patchlevel (0.81)
    C  Register application info.
    C  Oracle client version: 10.2.0.4.0, V5, default build, (dbsl 720 170211, UNICODE[2])
    C  Installed Oracle client patches:
    C  #  Unique Patch ID:  12114073Created on 15 Jan 2010, 09:30:31 hrs PST8PDT
    C  #  Patch  8732366      : Created on 27 Jul 2009, 15:49:18 hrs CEST
    C  #  Patch  6944036      : Created on  3 Jun 2008, 23:35:37 hrs PST8PDT
    C  #  Patch  6826661      : Created on 20 May 2008, 00:23:58 hrs PST8PDT
    C  #  Patch  6775231      : Created on  2 Dec 2008, 21:45:40 hrs PST8PDT
    C  #  Unique Patch ID:  12924916Created on 13 Sep 2010, 23:47:52 hrs PST8PDT
    C  Client NLS setting (by OCINlsGetInfo(con=0)): 'AMERICAN_AMERICA.UTF16'
    C  Logon as OPS$-user to get SAPSR3's password
    C  Connecting as /@AX2 on connection 0 (nls 0) ... (dbsl 720 170211, UNICODE[2])
    C  Attaching to database server AX2 (con=0, svchp=6aae3d8, srvhp=6ab20b8)
    C  Starting user session: OCISessionBegin(con=0, usr='/',svc=6aae3d8, srv=6ab20b8, usr=6af1ba0)
    C  Connected to session 23.
    C  Now '/@AX2' is connected: con=0, nls=0, session_id=23.
    C  Got SAPSR3's password from OPS$-user
    C  Disconnecting from connection 0 ...
    C  Closing user session (con=0, svc=6aae3d8, usr=6af1ba0)
    C  Now I'm disconnected from ORACLE
    C  Connecting as SAPSR3/<pwd>@AX2 on connection 0 (nls 0) ... (dbsl 720 170211, UNICODE[2])
    C  Starting user session: OCISessionBegin(con=0, usr='SAPSR3', svc=6aae3d8, srv=6ab20b8, usr=6af1ba0)
    C  Connected to session 23.
    C  Now 'SAPSR3/<pwd>@AX2' is connected: con=0, nls=0, session_id=23.
    C  con=0, V$NLS_PARAMETERS: NLS_LANG=AMERICAN_AMERICA.UTF8, NLS_NCHAR_CHARACTERSET=UTF8, UNI_NON=FALSE
    C  Nls CharacterSet   (V$NLS)            NatioCharSet   (V$NLS)                 EnvHp      ErrHp      ErrBt
    C    0 (UTF16)          UTF8             (AL16UTF16)      UTF8                6a95d10    6a9d810    6aae4a8
    C  DB instance AX2 is running on sachin with ORACLE version 11.2.0.2.0 since MAY 29, 2011, 22:43:07.
    B  Connection 0 opened (DBSL handle 0)
    B  Wp  Hdl ConName          ConId     ConState     TX  BC  HC  PRM RCT FRC TIM MAX OPT Date     Time   DBHost           Program                                
    B  000 000 R/3              000000000 ACTIVE       NO  NO  NO  YES NO  NO  000 255 255 20110529 224405 sachin                                                  
    M  ThInit: db_connect o.k.
    M  ICT: ict/odata_compatible_urls=0
    M  ICT: HTTP compression only above 1024 bytes
    M  ICT: maximum size of HTTP messages: 101 MB
    M  ICT: exclude compression: .zip,.rar,.arj,.z,.gz,.tar,.lzh,.cab,.hqx,.ace,.jar,.ear,.war,.css,.pdf,.gzip,.uue,.bz2,.iso,.sda,.sar,.gif,.png,.swc,*.swf
    M  ICT: exclude_compression: *.zip
    M  ICT: exclude_compression: *.rar
    M  ICT: exclude_compression: *.arj
    M  ICT: exclude_compression: *.z
    M  ICT: exclude_compression: *.gz
    M  ICT: exclude_compression: *.tar
    M  ICT: exclude_compression: *.lzh
    M  ICT: exclude_compression: *.cab
    M  ICT: exclude_compression: *.hqx
    M  ICT: exclude_compression: *.ace
    M  ICT: exclude_compression: *.jar
    M  ICT: exclude_compression: *.ear
    M  ICT: exclude_compression: *.war
    M  ICT: exclude_compression: *.css
    M  ICT: exclude_compression: *.pdf
    M  ICT: exclude_compression: *.gzip
    M  ICT: exclude_compression: *.uue
    M  ICT: exclude_compression: *.bz2
    M  ICT: exclude_compression: *.iso
    M  ICT: exclude_compression: *.sda
    M  ICT: exclude_compression: *.sar
    M  ICT: exclude_compression: *.gif
    M  ICT: exclude_compression: *.png
    M  ICT: exclude_compression: *.swc
    M  ICT: exclude_compression: *.swf
    M  ThJInit: init java layer
    M  ThPlgRegister: register handler for protocol 17 (HTTP(JAVA))
    M  ThJInit: java not active
    M Sun May 29 22:44:10 2011

    M  read th-profile-values from sys_adm

    I  MtxInit: 0 0 0
    M  SHM_PRES_BUF               (addr: 7f9c80b56000, size: 4400000)
    M  SHM_ROLL_AREA          (addr: 7f9c23573000, size: 268435456)
    M  SHM_PAGING_AREA          (addr: 7f9c13573000, size: 268435456)
    M  SHM_ROLL_ADM               (addr: 7f9c80f8a000, size: 11142696)
    M  SHM_PAGING_ADM          (addr: 7f9c132f2000, size: 2622496)
    M  ThCreateNoBuffer          allocated 564152 bytes for 1000 entries at 7f9c0c824000
    M  ThCreateNoBuffer          index size: 3000 elems
    Thanks
    Sachin

    I am using below java version.
    Java version 1.4.2
    java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
    IBM J9 VM ( build 2.3, J2RE 1.4.2 IBM J9 2.3 Linux amd64-64 j9vmxa64142ifx-20101119 (JIT Enable)
    j9VM - 20101118_68931_LHdSMr
    JIT  - 20090210_1447ifx2_r8
    GC   - 200902_24
    Br,
    Sachin

  • How to moniter the max quantity of used dialog work process in SAP system

    Dear Gurus,
    The quantity of Dia Work Process(DWP) of APP1 is: 16 (rdisp/wp_no_dia=16)
    The quantity of Dia Work Process(DWP) of APP2 is: 16 (rdisp/wp_no_dia=16)
    The quantity of Dia Work Process(DWP) of APP3 is: 20 (rdisp/wp_no_dia=20)
    The quantity of Dia Work Process(DWP) of APP4 is: 20 (rdisp/wp_no_dia=20)
    So the quantity of DWP in our SAP system is: 72 (=161620+20).
    We have 75 dialog users and many RFC callings via JCO method from J2EE system.
    I'm afriad the 72 DWPs will be run out of use someday.
    So I want to moniter the max quantity of used DWP every per hour to prevent the situation I mentioned above.
    Could you give me some suggestions?
    Thank you very much..
    Jason

    Hi Olivier,
      I really appreciate your help. You told me a very useful clew!
      As the method you told me, I have some questions:
      (a3) Do you restart your 'CI + 6 DIA' separately every week? Why did you do that?
      (a4) How to calculate 'CPU intensive time'?  For example, App server 'APS' was restarted on 8-10-2011 and stopped on 8-20-2011.
    There was a DWP(PID 557550) was created and activated on APS during this period(10 days). So If I add up each 'cpu time' of the task
    which 557550 executed, I can get the 'CPU intensive time' of 557550 (dispalyed in SM50). Right?
        In other words:
           DWP(PID 557550) finished task1: cpu time = 5ms  8-10-2011
           DWP(PID 557550) finished task2: cpu time = 4ms 
           DWP(PID 557550) finished task3: cpu time = 6ms  8-20-2011
         So the 'CPU intensive time'(Between 8-10-2011 and 8-20-2011) of DWP(PID 557550) is: 15ms (5ms4ms6ms). Right?
      (a5)Can we moniter the 'CPU intensive time' of DWPs in CCMS automatically? (I want to prevent the situation: The DWPs in our entire ECC are occupied.)
    Thank you!
                                                                                    Jason

  • How to moniter the max quantity of used dialog work process in our SAP syst

    Dear Gurus,
    The quantity of Dia Work Process(DWP) of APP1 is: 16 (rdisp/wp_no_dia=16)
    The quantity of Dia Work Process(DWP) of APP2 is: 16 (rdisp/wp_no_dia=16)
    The quantity of Dia Work Process(DWP) of APP3 is: 20 (rdisp/wp_no_dia=20)
    The quantity of Dia Work Process(DWP) of APP4 is: 20 (rdisp/wp_no_dia=20)
    So the quantity of DWP in our SAP system is: 72 (=161620+20).
    We have 75 dialog users and many RFC callings via JCO method from J2EE system.
    I'm afriad the 72 DWPs will be run out of use someday.
    So I want to moniter the max quantity of used DWP every per hour to prevent the situation I mentioned above.
    Could you give me some suggestions?
    Thank you very much..
    Jason
    Edited by: jason xu on Aug 22, 2011 6:20 PM

    duplicate thread !!

  • How to statistic the rest dialog work process?

    Dear Gurus,
       Is there some method we can statistic the rest dialog work process in every ten minutes in our sap ECC prd system(ECC 6.0)?(I want to use the number to evaluate our SAP system's performance. Esp, at the business peak period.)
    Thank you!
    Jason

    Hi Jason,
    If I understand correct, you want to find out number of required work processes.
    You can find it, by using "ST02 -> Go to -> Current Local Data -> SAP cursor cache -> ID cache" path. On this table, you can analyze how many work processes are really running and how many work processes are waiting at the idle state.
    There is no time based values, about these statistics. These values indicate current stats.
    Best regards,
    Orkun Gedik

  • The worker process for application pool 'MSExchangeAutodiscoverAppPool' encountered an error

    Hello Guys,
    I am getting an event ID 2297 with the description given below.
    The worker process for application pool 'MSExchangeAutodiscoverAppPool' encountered an error 'Cannot add duplicate collection entry of type 'add' with unique key attribute 'name' set to 'WSMan'
    ' trying to read global module configuration data from file '\\?\C:\inetpub\temp\apppools\MSExchangeAutodiscoverAppPool\MSExchangeAutodiscoverAppPool.config', line number '275'.  Worker process startup aborted.
    Could someone help me please to resolve this.
    Thanks in Advance. :)
    Regards Rishi Aggarwal

    Hi,
    Based on the error message, it seems the issue is related to that there is a duplicate entry in the file it mentioned.
    I recommend you follow Amit’s suggestions to check result.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • How many work processes are recommended by SAP for 16 GB RAM

    How many work processes are recommended by SAP for 16 GB RAM ?

    This is the calculation for determining the number of work process according to the available memory  for the system.
    - Number of dialog work processes = RAM/256 (min 2, max 18)
    - Number of update work processes = RAM/768 (min 1, max 6)
    - Number of update2 work processes = RAM/1024 (min 1, max 3)
    - Number of batch work processes = RAM/1024 (min 2, max 3)
    - Number of enqueue work processes = 1
    - Number of spool work processes = 1
    You can also refer the following link regarding memory management in SAP .
    http://help.sap.com/saphelp_nw70/helpdata/EN/02/962817538111d1891b0000e8322f96/frameset.htm
    It explains the calculation based on number of processors for the server.
    Regards,
    Jazz

Maybe you are looking for

  • PSCS3 Extended - a let down

    I purchased PSCS3 Extended because it looked like it would really be great. I'm an architect and I was really looking forward to the measurement tool... I have to measure things off of job site pics all the time. I have to say the measurement tool in

  • The Horizontal & vertical scroll is not visible or not working when i run the form in Forms 6i.

    Hi all, The Horizontal & vertical scroll is not visible or not working when i run the form. In this form , there are 5 canvas namely CANVAS2 - Stacked Canvas PASS - Content Canvas MAT_RATES - Content Canvas DATE - Content Canvas PREVIOUS - Content Ca

  • Subcontracting Using Scheduling agreement

    I am trying to carry out subcontracting using Scheduling Agreement, but not able to achieve the same. Please let me know stepwise porocedure to carry out the same.

  • Mac Mail Smart Folders triplicate messages (Gmail-based mail server)

    I can't get Mail Smart Folders to work well with my Virginmedia mail server, which seems to use a Gmail type of system. (I'm using IMAP). It is easy to set up an instruction to select mail e.g. from defined individuals only, or any other qualifier. H

  • IPhoto - Backup failure after transfer to new Mac

    I just migrated everything over from my iMac to the new Mac Pro and plugged in the external hard drive I'd been using to back files up using the .Mac utility "Backup." I made no changes to the schedules I'd set up previously. All backup schedules are