Changing rdisp/max_wprun_time

I have a third party program which uses a back ground account to connect to SAP and run ABAP.  This ABAP program is taking longer than 5 minutes and it is timing out with error:
SR_17009 Error in CPIC: [CMRCV: 18 Time limit exceeded
Current I am using SAP R3 4.x and will be moving to SAP ECC 6.x in future.
I have read that one can change following parameter
rdsip/rdisp/max_wprun_time   to change the default time.
I have  following questions, some of them are naive:
1. Does a background account(my third party cannot login interactively) still use Dialog Processes.
2. I am assuming I have to create s special profile for setting this parameter so it does not affect other accounts. What command do you use to create this profile.
3. What command do I use to assign my third party account to this profile.
4. How do I found which account has which profile.
THANSK A LOT.

Zigzagdna,
The parameter rdisp/max_wprun_time is not user or profile specific. It affects the entire system. Simply defined, it defines the amount of time a dialog work process can be occupied by one step (can be seen in SM50). Which user you use to run/call the ABAP program, does not change or decide the time.
1. Does a background account(my third party cannot login interactively) still use Dialog Processes.
Yes, it can. Most program need both dialog work processes and background.
2. I am assuming I have to create s special profile for setting this parameter so it does not affect other accounts. What command do you use to create this profile.
No, you dont need a profile.You can change this value from the Tcode RZ11.It can be changed and the new value is taken into effect without restarting the SAP system (dynamically switchable).
3. What command do I use to assign my third party account to this profile.
Not applicable
4. How do I found which account has which profile.
Not applicable
I dont have the exact info of your program, but from what it sound like, it could be timing out because of RFC timeout. If it is not running from the SAP Gui, it must make RFC calls to the server.
Kunal

Similar Messages

  • Determine/read the value of parameter rdisp/max_wprun_time within ABAP

    Hi,
    I need to avoid program breaks caused by exceeding run time longer than defined in parameter rdisp/max_wprun_time.
    I will check the time since start of report in the critcal loop to bring the current data changes to a controlled end before getting a program break. I won't put a constant to the report, I will have a dynamical routine to avoid changes of report if the value of parameter rdisp/max_wprun_time will be changed.
    But how can I get the value of this parameter within my ABAP report? Is there a table where this value has been stored? Is there an existing function module or a method to read the value?
    Thank's a lot in advance!
    Georg

    The runtime   parameter (GET RUN TIME ) can be used to dynamically get the program run time
    DATA T TYPE I.
    GET RUN TIME FIELD T.
    WRITE: / 'Runtime', T.
    or
    U probably can store the start date and time in TVARV with some variable ( line concatenate program name + START Date + Time)
    and then use
    SD_DATETIME_DIFFERENCE
    or
    SD_CALC_DURATION_FROM_DATETIME
    Regards,
    Mithun Shetty

  • The system profile parameter rdisp/max_wprun_time  how to cinfigure this in ecc system

    Hi,
    Can any body tell me the procedure how can we configure the the system profile
    parameter rdisp/max_wprun_time  in ecc system step by step procedure
    Regards
    Madhu

    Hi Madhu,
    If we change the max parametere here my be our problem will solved right.
    See this link is usefully
    http://scn.sap.com/thread/2045008
    Adding some comment to that rz-10 is different than RZ10?
    There is no t-code like rz-10.
    rz10 is the t-code for profile parameters
    Regards,
    Deva

  • BASIS Parameter rdisp/max_wprun_time

    Hi,
       Does anybody knows how the time limit given in the profile parameter rdisp/max_wprun_time work?
    I mean our parameter is set to 3600.  What does that mean? Does it mean that it will kill dialog process at 3600 secs or 7200 secs?
    Today our system almost came down as there were bex users (mostly with killed excel programs) which still had a process in SAP running for more than 40000 secs.  Any idea why the parameter didnt work?
    Also if the parameter gives two times its value before the dialog work process is killed why today I saw one dialog process getting killed at 3600 secs in sm66 shouldnt it get killed after 7200 seconds.
    I though the parameter is defined such that if rdisp/max_wprun_time=n then maximum dialog process runtime would be 2n and after n seconds smm66/sm51 would show up as red and after 2n it would be cancelled altogether...
    please help

    Hallo BWNovice
    The parameter is giving you maximum time for Dialog Process - for example when you run a bex query. The default is 600 sec but yo0u can extend as much as you want I suppose. But be carefully because then you can have process which run for 6000-7000 thousand seconds which can affect macvhine performance (depend on your machine). Usually 3600 is a good time, thinking also for the loading during the night where you can have some dialog processes which takes some time.
    Regarding your question: if you have it set-up 3600 and you run a bex report which takes more than 3600 at 3600 then the process will be killed by the system.
    But a suggestion: you should avoid to have process which run so long time in your machine, specially bex report.
    I hope this can help you.
    Mike

  • Runtime parameter rdisp/max_wprun_time is set to 1700

    u201CCaller 70u201D missing error. This is happening because the runtime parameter rdisp/max_wprun_time is set to 1700. If I edit it to 15000 temporarily and re run the load, the load is successful.
    this is popping up at the point of updating data targets, in the 1st set of data package while the second loads successfully.
    Krishna.

    The runtime parameter rdisp/max_wprun_time defines the time limit for a foreground process. While backgound processes are permitted to run with out any limit. With this parameter the foreground/dialog processes are permitted to run for the defined amount of time, beyond this the system will cancel them terming it as time limit exceeded error.
    The standard defined by SAP for this parameter is 3600, but depending on our business need we can increase or decrease this value. Usually taken care by Basis Administrators.
    Regards,
    Habeeb

  • Are there any troubles with high rdisp/max_wprun_time?

    Are there any unpredictable negative effects while setting this parameter large values (for example, 1000 or 2000 seconds?)

    Hi Pavel Danilov,
    You can increase the value but this increases the chance of work processes being blocked (eventual system standstill situations possible). I assume you have reviewed note <a href="http://service.sap.com/sap/support/notes/25528">25528</a> and other documentation about this parameter. There can be some reasons why 600 is not high enough also for current needs..
    Normally if you have very long running database accesses, than this indicates that the program is in a loop or no suitable index exist for this access so that a full table scan is performed or the optimizer has a problem with the statement.                                                                               
    You can check as well if the reason for the long running task is:                                                                               
    - Overload of the SAP System and/or of the database                                     
    - Waiting for locks in the DB         
    Regards, Mark

  • Long time to open tab "change history" of  business partner in Web_ui.

    Dear experts!
    Long time to open tab "change history" of  business partner in Web_ui.
    4 records were opened for 10-20 seconds
    http://imglink.ru/show-image.php?id=22083a6a576f78c66c86863bf6b0573b
    1. In what may be the reason?
    If the records are many, the discovery may be more than a minute.
    2. Is There a report for the purification of the " Сhange history" over a period?

    Hello Dilip,
    One more alternative would be to increase the time out parameter in ABAP environment.
    The steps to change this parameter:                                                                               
    1) txn: RZ11 -> enter the variable name rdisp/max_wprun_time                      
    2) Display -> Change value -> Then input the value you would like        (ideally 3600)                                                                               
    PS:                                                                          
    1) Don't set this value too big, otherwise general performance will be       
    influenced, since lots of dialogue process will be occupied for a long       
    time                                                                         
    2) This parameter can be changed dynamically                                                                               
    Once the parameter is set please test again. You can try incremental         
    values and test which one does not give timeout error.                                                                               
    please refer to the note 25528 for more details about RZ11.   
    Hope this helps!
    Thanks and Best Regards,
    Shanthala Kudva.

  • Program terminated: Time limit exceeded, ABAP performance, max_wprun_time

    Hi,
    I am running an ABAP program, and I get the following short dump:
    Time limit exceeded. The program has exceeded the maximum permitted runtime and has therefore been terminated. After a certain time, the program terminates to free the work processfor other users who are waiting. This is to stop work processes being blocked for too long by
    - Endless loops (DO, WHILE, ...),
    - Database acceses with large result sets,
    - Database accesses without an apporpriate index (full table scan)
    - database accesses producing an excessively large result set,
    The maximum runtime of a program is set by the profile parameter "rdisp/max_wprun_time". The current setting is 10000 seconds. After this, the system gives the program a second chance. During the first half (>= 10000 seconds), a call that is blocking the work process (such as a long-running SQLstatement) can occur. While the statement is being processed, the database layer will not allow it to be interrupted. However, to stop the program terminating immediately after the statement has been successfully processed, the system gives it another 10000 seconds. Hence the maximum runtime of a program is at least twice the value of the system profile parameter "rdisp/max_wprun_time".
    Last error logged in SAP kernel
    Component............ "NI (network interface)"
    Place................ "SAP-Dispatcher ok1a11cs_P06_00 on host ok1a11e0"
    Version.............. 34
    Error code........... "-6"
    Error text........... "connection to partner broken"
    Description.......... "NiPRead"
    System call.......... "recv"
    Module............... "niuxi.c"
    Line................. 1186
    Long-running programs should be started as background jobs. If this is not possible, you can increase the value of the system profile parameter "rdisp/max_wprun_time".
    Program cannot be started as a background job. We have now identified two options to solve the problem:
    - Increase the value of the system profile parameter "rdisp/max_wprun_time"
    - Improve the performance of the following SELECT statement in the program:
    SELECT ps_psp_pnr ebeln ebelp zekkn sakto FROM ekkn
    INTO CORRESPONDING FIELDS OF TABLE i_ekkn
    FOR ALL ENTRIES IN p_lt_proj
    WHERE ps_psp_pnr = p_lt_proj-pspnr
    AND ps_psp_pnr > 0.
    In EKKN we have 200 000 entries.
    Is there any other options we could try?
    Regards,
    Jarmo

    Thanks for your help, this problem seems to be quite challenging...
    In EKKN we have 200 000 entries. 199 999 entries have value of 00000000 in column ps_psp_pnr, and only one has a value which identifies a WBS element.
    I believe the problem is that there isn't any WBS element in PRPS which has the value of 00000000. I guess that is the reason why EKKN is read sequantially.
    I also tried this one, but it doesn't help at all. Before the SELECT statement is executed, there are 594 entries in internal table p_lt_proj_sel:
      DATA p_lt_proj_sel LIKE p_lt_proj OCCURS 0 WITH HEADER LINE.
      p_lt_proj_sel[] = p_lt_proj[].
      DELETE p_lt_proj_sel WHERE pspnr = 0.
      SORT p_lt_proj_sel by pspnr.
      SELECT ps_psp_pnr ebeln ebelp zekkn sakto FROM ekkn
      INTO CORRESPONDING FIELDS OF TABLE i_ekkn
      FOR ALL ENTRIES IN p_lt_proj_sel
      WHERE ps_psp_pnr = p_lt_proj_sel-pspnr.
    I also checked that the index P in EKKN is active.
    Can I somehow force the optimizer to use the index?
    Regards,
    Jarmo

  • Dialog WP runtime exceeds value set in rdisp/wp_max_runtime

    Dialog wp runtime exceeds the value set in parameter rdisp/wp_max_runtime
    Value set for rdisp/wp_max_runtime is 1500 but wp runtime exceeds more than 10,000. we are using 4.5B system on Oracle/AIX.
    Please suggest how to avoid such wp running for more than value set in parameter rdisp/wp_max_runtime.

    Hi Rudra,
    rdisp/max_wprun_time essentially may not stop the process all th time especially if your work process is waiting for some information or waiting for some query to execute.
    Read the following note which describes the behaviour of this parameter
    Note 25528 - Parameter rdisp/max_wprun_time
    Hope that helps.
    Regards,
    Siddhesh

  • Msprot: cant read profile parameter rdisp/mshost

    Hi
    When I run : msprot -name <SID> -l it returns:
    cant read profile parameter rdisp/mshost
    rdisp/mshost is set in the default profile to : sapms<SID>
    in etc/services  sapms<SID> is assigined to   <port_number>/tcp
    If you change rdisp/mshost to the port number rather than sapms<SID> it works....but we don't want to change the parameter to the port number.
    Thanks
    Jim

    Thanks.....i've being testing the command....it's like it can't read the default profile...
    if i use mshost switch it complain it can't read msserv.....once I use both switch it runs ok....
    I changed default profile to 777 just to test if it was a permissions issue but that didn't make a difference.
    Thanks for the note but that seems to be dealing with windows...i'm working on sun...tried it on linux also and get
    the same problem....
    Cheers
    Jim

  • Sap Message Service Name change

    hello guys,
    i need you help with something.
    I would like to change the sap Message Service Name from sapms<SID> to sapms<SID>_new.
    Is this possible?
    i am thinking to do this in RZ11 and change rdisp/msserv value... am i on the right path?
    Are there some limitations in message server service name?
    Thank you for answer.

    Hi Oliver,
    Does those same SID SAP systems , carries same instance number?
    As per SAP Note # 99435 , you should not edit SAPLOGON.ini file manually , instead carry out all changes via SAPLOGon PAD.
    Pls add both systems with different IP specifications and respective instance number details.
    Check if you are able to connect to correct instance
    Regards

  • When performing the LT03 for a delivery order

    The system runs forever; then ABAP dumps.  None of us here are experts in ABAP at all.  This is not happening in our QA client only in the production client so I am at a lsot as to why.  My initial though was due to changing serialization level from one to none but when I tried to duplicate the error in QA, it works,  Below is the message ...anyone with advice?
    Short text
    Time limit exceeded.
    What happened?
    The program "SAPLZAF_MM_SERIAL" has exceeded the maximum permitted runtime
    without
    interruption and has therefore been terminated.
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    After a specific time, the program is terminated to make the work area
    available to other users who may be waiting.
    This is to prevent a work area being blocked unnecessarily long by, for
    example:
    - Endless loops (DO, WHILE, ...),
    - Database accesses with a large result set
    - Database accesses without a suitable index (full table scan)
    The maximum runtime of a program is limited by the system profile
    parameter "rdisp/max_wprun_time". The current setting is 1800 seconds. If this
    time limit is
    exceeded, the system attempts to cancel any running SQL statement or
    signals the ABAP processor to stop the running program. Then the system
    waits another 60 seconds maximum. If the program is then still active,
    the work process is restarted.
    How to correct the error
    Programs with long runtime should generally be started as background
    jobs. If this is not possible, you can increase the system profile
    parameter "rdisp/max_wprun_time".
    Depending on the cause of the error, you may have to take one of the
    following measures:
    - Endless loop: Correct program;
    - Dataset resulting from database access is too large:
    Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table
    (for example);
    - Database has unsuitable index: Check index generation.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "TIME_OUT" " "
    "SAPLZAF_MM_SERIAL" or "LZAF_MM_SERIALU01"
    "ZAF_MM_SERIAL"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    System environment
    SAP-Release 700
    Application server... "WIC-PD-ECCSCS"
    Network address...... "10.200.1.245"
    Operating system..... "Linux"
    Release.............. "2.6.16.60-0.39.3-smp"
    Hardware type........ "x86_64"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "WIC-PD-ORC-01"
    Database type..... "ORACLE"
    Database name..... "ECP"
    Database user ID.. "SAPSR3"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Aug 23 2009 20:22:37"
    create on........ "Linux GNU SLES-9 x86_64 cc3.3.3"
    Database version. "OCI_102 (10.2.0.2.0) "
    Patch level. 221
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "Linux 2.6"
    Memory consumption
    Roll.... 16192
    EM...... 20949240
    Heap.... 0
    Page.... 57344
    MM Used. 10428296
    MM Free. 2138248
    User and Transaction
    Client.............. 400
    User................ "TNIDA"
    Language key........ "E"
    Transaction......... "LT03 "
    Transactions ID..... "4C7C27CEFAB745B2E10000000AC801F1"
    Program............. "SAPLZAF_MM_SERIAL"
    Screen.............. "SAPML03T 0102"
    Screen line......... 68
    Information on where terminated
    Termination occurred in the ABAP program "SAPLZAF_MM_SERIAL" - in
    "ZAF_MM_SERIAL".
    The main program was "SAPML03T ".
    In the source code you have the termination point in line 33
    of the (Include) program "LZAF_MM_SERIALU01".
    Source Code Extract
    Line SourceCde
    3 ""Local Interface:
    4 *" IMPORTING
    5 *" REFERENCE(LGORT) TYPE LGORT_D OPTIONAL
    6 *" REFERENCE(WERKS) TYPE WERKS_D OPTIONAL
    7 *" REFERENCE(MATNR) TYPE MATNR OPTIONAL
    8 *" REFERENCE(SERNR) TYPE GERNR OPTIONAL
    9 *" REFERENCE(LGNUM) TYPE LGNUM OPTIONAL
    10 *" EXPORTING
    11 *" REFERENCE(LGPLA) TYPE LGPLA
    12 *"----
    13
    14
    15 REFRESH: it_objk, it_ser03, it_lqua.
    16
    17 * Select serial number for all material documents
    18 SELECT * FROM objk
    19 INTO TABLE it_objk
    20 WHERE taser = 'SER03'
    21 AND sernr eq sernr
    22 AND matnr eq matnr.
    Select documents details for serial numbers.
    25 SELECT * FROM ser03
    26 INTO TABLE it_ser03
    27 FOR ALL ENTRIES IN it_objk
    28 WHERE obknr = it_objk-obknr
    29 AND werk = werks
    30 AND lagerort = lgort.
    31
    32 * Select storage bin details for all selected materials documents.
    >>>>> SELECT * FROM lqua
    34 INTO TABLE it_lqua
    35 FOR ALL ENTRIES IN it_ser03
    36 WHERE wenum = it_ser03-mblnr
    37 AND lgnum = lgnum.
    38 * AND lgpla = lgpla.
    39
    40
    41 * Populate the output table
    42 LOOP AT it_objk INTO wa_objk.
    43 READ TABLE it_ser03 INTO wa_ser03 WITH KEY obknr = wa_objk-obknr.
    44 IF sy-subrc = 0.
    45 READ TABLE it_lqua INTO wa_lqua WITH KEY wenum = wa_ser03-mblnr
    46 matnr = wa_objk-matnr.
    47 IF sy-subrc = 0.
    48 wa_ser-werks = wa_lqua-werks.
    49 wa_ser-lgort = wa_lqua-lgort.
    50 wa_ser-matnr = wa_lqua-matnr.
    51 wa_ser-sernr = wa_objk-sernr.
    52 wa_ser-lgnum = wa_lqua-lgnum.
    Contents of system fields
    Name Val.
    SY-SUBRC 0
    SY-INDEX 1
    SY-TABIX 10
    SY-DBCNT 33702
    SY-FDPOS 40
    SY-LSIND 0
    SY-PAGNO 0
    SY-LINNO 1
    SY-COLNO 1
    SY-PFKEY 31
    SY-UCOMM TATB
    SY-TITLE Create Transfer Order for Delivery: Generate TO Item
    SY-MSGTY E
    SY-MSGID L9
    SY-MSGNO 202
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO 0
    SY-DATUM 20100831
    SY-UZEIT 084745
    SY-XPROG SAPCNVE
    SY-XFORM CONVERSION_EXIT

    I managed to remove the serial numbers from the delivery and then tried LT03.  It ran for a long time however; I did manage to get it thru that way.  Added the serial numbers back in vlo02n and post goods issue just fine.
    Still curious as why the system is lagging so long and woul ABAP out if a serial numebr is in the LT03 when trying to create a TO...please any clues would be good.

  • Dispatcher getting stopped due to possible user/schema mismatch.Plz help

    Hello All,
    I have SAP Netweaver 7.01 ABAP AS installed on windows 2003. Was working fine but I had to have a bug fixed in win 2003 and restarted my SAP machine. Now, dispatcher is not running. Stops after a while. I have tried restarting SAP and the machine but dispatcher is not running. I looked at the dispatcher trace and dev_w0 but could not figure out the reason as I am new to SAP, please provide any pointers to solve this issue. Any general tips is also welcome. Timely help is greatly appreciated!
    I have pasted parts of dev_disp and dev_w0 below. If you require more details, please let me know. Thank you very much!
    -Arvind
    dev_disp:
    =========
    trc file: "dev_disp", trc level: 1, release: "701"
    sysno      00
    sid        NSP
    systemid   560 (PC with Windows NT)
    relno      7010
    patchlevel 0
    patchno    29
    intno      20020600
    make:      multithreaded, Unicode, optimized
    pid        3784
    Fri Jun 10 19:25:12 2011
    kernel runs with dp version 241000(ext=110000) (@(#) DPLIB-INT-VERSION-241000-UC)
    length of sys_adm_ext is 576 bytes
    *** SWITCH TRC-HIDE on ***
    ***LOG Q00=> DpSapEnvInit, DPStart (00 3784) [dpxxdisp.c   1261]
         shared lib "dw_xml.dll" version 29 successfully loaded
         shared lib "dw_xtc.dll" version 29 successfully loaded
         shared lib "dw_stl.dll" version 29 successfully loaded
         shared lib "dw_gui.dll" version 29 successfully loaded
         shared lib "dw_mdm.dll" version 29 successfully loaded
    rdisp/softcancel_sequence :  -> 0,5,-1
    use internal message server connection to port 3900
    Fri Jun 10 19:25:18 2011
    *** WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 5 seconds
    ***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c  5529]
    MtxInit: 30000 0 0
    DpSysAdmExtInit: ABAP is active
    DpSysAdmExtInit: VMC (JAVA VM in WP) is not active
    DpIPCInit2: start server >egsap701_NSP_00                         <
    DpShMCreate: sizeof(wp_adm)          13632     (1704)
    DpShMCreate: sizeof(tm_adm)          4415616     (21968)
    DpShMCreate: sizeof(wp_ca_adm)          1664     (80)
    DpShMCreate: sizeof(appc_ca_adm)     1600     (80)
    DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064
    DpShMCreate: sizeof(comm_adm)          528064     (1048)
    DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
    DpShMCreate: sizeof(slock_adm)          0     (96)
    DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    DpShMCreate: sizeof(file_adm)          0     (72)
    DpShMCreate: sizeof(vmc_adm)          0     (1544)
    DpShMCreate: sizeof(wall_adm)          (38456/34360/64/184)
    DpShMCreate: sizeof(gw_adm)     48
    DpShMCreate: SHM_DP_ADM_KEY          (addr: 07050040, size: 5042120)
    DpShMCreate: allocated sys_adm at 07050040
    DpShMCreate: allocated wp_adm at 07052170
    DpShMCreate: allocated tm_adm_list at 070556B0
    DpShMCreate: allocated tm_adm at 070556E0
    DpShMCreate: allocated wp_ca_adm at 0748B760
    DpShMCreate: allocated appc_ca_adm at 0748BDE0
    DpShMCreate: allocated comm_adm at 0748C420
    DpShMCreate: system runs without slock table
    DpShMCreate: system runs without file table
    DpShMCreate: allocated vmc_adm_list at 0750D2E0
    DpShMCreate: allocated gw_adm at 0750D320
    DpShMCreate: system runs without vmc_adm
    DpShMCreate: allocated ca_info at 0750D350
    DpShMCreate: allocated wall_adm at 0750D358
    MBUF state OFF
    DpCommInitTable: init table for 500 entries
    rdisp/queue_size_check_value :  -> off
    ThTaskStatus: rdisp/reset_online_during_debug 0
    *** ERROR => ztta/cua_area is 180000. [sapinit.c    975]
    *** ERROR => ztta/cua_area adjusted to 500000. [sapinit.c    979]
    EmInit: MmSetImplementation( 2 ).
    MM global diagnostic options set: 0
    <ES> client 0 initializing ....
    <ES> InitFreeList
    <ES> block size is 1024 kByte.
    Using implementation view
    <EsNT> Using memory model view.
    <EsNT> Memory Reset disabled as NT default
    <ES> 1023 blocks reserved for free list.
    ES initialized.
    rdisp/http_min_wait_dia_wp : 1 -> 1
    ***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c   1656]
    ***LOG Q0K=> DpMsAttach, mscon ( egsap701) [dpxxdisp.c   12362]
    DpStartStopMsg: send start message (myname is >egsap701_NSP_00                         <)
    DpStartStopMsg: start msg sent
    CCMS: alert/MONI_SEGM_SIZE = 0   monitoring and alerting switched off.
    DpMsgAdmin: Set release to 7010, patchlevel 0
    MBUF state PREPARED
    MBUF component UP
    DpMBufHwIdSet: set Hardware-ID
    ***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1048]
    DpMsgAdmin: Set patchno for this platform to 29
    Release check o.K.
    Fri Jun 10 19:25:58 2011
    my types changed after wp death/restart 0xbf --> 0xbe
    my types changed after wp death/restart 0xbe --> 0xbc
    my types changed after wp death/restart 0xbc --> 0xb8
    my types changed after wp death/restart 0xb8 --> 0xb0
    my types changed after wp death/restart 0xb0 --> 0xa0
    my types changed after wp death/restart 0xa0 --> 0x80
    *** DP_FATAL_ERROR => DpWPCheck: no more work processes
    *** DISPATCHER EMERGENCY SHUTDOWN ***
    increase tracelevel of WPs
    NiWait: sleep (10000ms) ...
    NiISelect: timeout 10000ms
    NiISelect: maximum fd=1565
    NiISelect: read-mask is NULL
    NiISelect: write-mask is NULL
    Fri Jun 10 19:26:08 2011
    NiISelect: TIMEOUT occured (10000ms)
    dump system status
    max_rq_id          11
    wake_evt_udp_now     0
    wake events           total     7,  udp     7 (100%),  shm     0 (  0%)
    since last update     total     7,  udp     7 (100%),  shm     0 (  0%)
    Workprocess Comm. Area Blocks               Fri Jun 10 13:56:08 2011
    =============================
    Slots: 20, Used: 1, Max: 0
    +------+--------------+----------+-------------+
    |   id | owner        |   pid    | eyecatcher  |
    +------+--------------+----------+-------------+
    |    0 | DISPATCHER   |       -1 | *WPCAAD000* |
    <SNIP>
    [DpProcDied] Process died  (PID:3492  HANDLE:1540)
    DpStartStopMsg: send stop message (myname is >egsap701_NSP_00                         <)
    DpStartStopMsg: Write AD_STARTSTOP message with type=  0, name=egsap701_NSP_00     , sapsysnr= 0, hostname=egsap701                                                       
    AdGetSelfIdentRecord: >                                                                           <
    AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
    AdCvtRecToExt: opcode 4 (AD_STARTSTOP), ser 0, ex 0, errno 0
    DpConvertRequest: net size = 189 bytes
    <SNIP>
    AdGetSelfIdentRecord: >                                                                           <
    AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0
    AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
    AdCvtRecToExt: opcode 40 (AD_MSBUF), ser 0, ex 0, errno 0
    blks_in_queue/wp_ca_blk_no/wp_max_no = 1/20/8
    LOCK WP ca_blk 1
    make DISP owner of wp_ca_blk 1
    DpRqPutIntoQueue: put request into queue (reqtype 1, prio LOW, rq_id 14)
    MBUF component DOWN
    NiICloseHandle: shutdown and close hdl 2 / sock 1496
    NiBufIClose: clear extension for hdl 2
    MsIDetach: detach MS-system
    cleanup EM
    EsCleanup ....
    EmCleanup() -> 0
    Es2Cleanup: Cleanup ES2
    ***LOG Q05=> DpHalt, DPStop ( 3784) [dpxxdisp.c   10924]
    Good Bye .....
    dev_w0
    ========
    trc file: "dev_w0", trc level: 1, release: "701"
    *  ACTIVE TRACE LEVEL           1
    *  ACTIVE TRACE COMPONENTS      all, MJ
    B 
    B Fri Jun 10 19:25:18 2011
    B  create_con (con_name=R/3)
    B  Loading DB library 'C:\usr\sap\NSP\DVEBMGS00\exe\dbsdbslib.dll' ...
    B  Library 'C:\usr\sap\NSP\DVEBMGS00\exe\dbsdbslib.dll' loaded
    B  Version of 'C:\usr\sap\NSP\DVEBMGS00\exe\dbsdbslib.dll' is "700.08", patchlevel (0.24)
    B  New connection 0 created
    M sysno      00
    M sid        NSP
    M systemid   560 (PC with Windows NT)
    M relno      7010
    M patchlevel 0
    M patchno    29
    M intno      20020600
    M make:      multithreaded, Unicode, optimized
    M pid        2768
    M
    M  kernel runs with dp version 241000(ext=110000) (@(#) DPLIB-INT-VERSION-241000-UC)
    M  length of sys_adm_ext is 576 bytes
    M  ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 2768) [dpxxdisp.c   1323]
    I  MtxInit: 30000 0 0
    M  DpSysAdmExtCreate: ABAP is active
    M  DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
    M  DpShMCreate: sizeof(wp_adm)          13632     (1704)
    M  DpShMCreate: sizeof(tm_adm)          4415616     (21968)
    M  DpShMCreate: sizeof(wp_ca_adm)          1664     (80)
    M  DpShMCreate: sizeof(appc_ca_adm)     1600     (80)
    M  DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064
    M  DpShMCreate: sizeof(comm_adm)          528064     (1048)
    M  DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
    M  DpShMCreate: sizeof(slock_adm)          0     (96)
    M  DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    M  DpShMCreate: sizeof(file_adm)          0     (72)
    M  DpShMCreate: sizeof(vmc_adm)          0     (1544)
    M  DpShMCreate: sizeof(wall_adm)          (38456/34360/64/184)
    M  DpShMCreate: sizeof(gw_adm)     48
    M  DpShMCreate: SHM_DP_ADM_KEY          (addr: 07050040, size: 5042120)
    M  DpShMCreate: allocated sys_adm at 07050040
    M  DpShMCreate: allocated wp_adm at 07052170
    M  DpShMCreate: allocated tm_adm_list at 070556B0
    M  DpShMCreate: allocated tm_adm at 070556E0
    M  DpShMCreate: allocated wp_ca_adm at 0748B760
    M  DpShMCreate: allocated appc_ca_adm at 0748BDE0
    M  DpShMCreate: allocated comm_adm at 0748C420
    M  DpShMCreate: system runs without slock table
    M  DpShMCreate: system runs without file table
    M  DpShMCreate: allocated vmc_adm_list at 0750D2E0
    M  DpShMCreate: allocated gw_adm at 0750D320
    M  DpShMCreate: system runs without vmc_adm
    M  DpShMCreate: allocated ca_info at 0750D350
    M  DpShMCreate: allocated wall_adm at 0750D358
    M  rdisp/queue_size_check_value :  -> off
    M  ThTaskStatus: rdisp/reset_online_during_debug 0
    Y  *** ERROR => ztta/cua_area is 180000. [sapinit.c    975]
    Y  *** ERROR => ztta/cua_area adjusted to 500000. [sapinit.c    979]
    X  EmInit: MmSetImplementation( 2 ).
    X  MM global diagnostic options set: 0
    X  <ES> client 0 initializing ....
    X  Using implementation view
    X  <EsNT> Using memory model view.
    M  <EsNT> Memory Reset disabled as NT default
    X  ES initialized.
    M  ThInit: running on host egsap701
    M 
    M Fri Jun 10 19:25:19 2011
    M  calling db_connect ...
    C 
    C  DBSDBSLIB : version 700.08, patch 0.024 (Make PL 0.29)
    C  MAXDB shared library (dbsdbslib) patchlevels (last 10)
    C    (0.024) Default value for max. input variables is 2000 (note 655018)
    C    (0.024) Profile parameter to define max. input variables (note 655018)
    C    (0.024) Switch SQLMODE after CREATE INDEX SERIAL (note 1267841)
    C    (0.024) Input parameters for SQL statements increased (note 655018)
    C    (0.018) Create index serial for MaxDB 7.6 (note 1267841)
    C    (0.018) More trace in case of packed to string conversion error (note 1262799)
    C    (0.016) R3trans export aborts with signal 6 (note 1262245)
    C    (0.009) IA64 alignment errors (note 1245982)
    C    (0.007) Support DB-Type 'SAP DB' by UPDSTAT (note 1225668)
    C 
    C 
    C  Loading SQLDBC client runtime ...
    C  SQLDBC SDK Version : SQLDBC.H  7.6.0    BUILD 002-121-083-965
    C  SQLDBC Library Version : libSQLDBC 7.6.5    BUILD 011-123-196-300
    C  SQLDBC client runtime is MaxDB 7.6.5.011 CL 196300
    C  SQLDBC supports new DECIMAL interface : 0
    C  SQLDBC supports VARIABLE INPUT data   : 1
    C  SQLDBC supports keepAlive indicator   : 0
    C  INFO : SQLOPT= -I 0 -t 0 -S SAPR3
    C  Try to connect (DEFAULT) on connection 0 ...
    C  Attach to SAP DB : Kernel    7.7.06   Build 007-123-197-046
    C  Database release is SAP DB 7.7.06.007
    C  INFO : Database 'NSP' instance is running on 'egsap701'
    C  DB max. input host variables  : 2000
    C  INFO : SAP DB Packet_Size = 131072
    C  INFO : SAP DB Min_Reply_Size = 4096
    C  INFO : SAP DB Comm_Size = 126976
    C  INFO : DBSL buffer size = 126976
    C  INFO : SAP DB MaxLocks = 300000
    C  INFO : Connect to DB as 'SAPNSP'
    C  *** ERROR => the connected user (SAPNSP) does not work with the right user/schema
    [dbslsdb.cpp  4818]
    C  *** ERROR => application has to work with schema SAPR3 (dbs/ada/schema)
    [dbslsdb.cpp  4820]
    M  ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c   1449]
    M  in_ThErrHandle: 1
    M  *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   10563]
    M 
    M  Info for wp 0
    M 
    M    pid = 2768
    M    severity = 0
    M    status = 0
    M    stat = WP_RUN
    M    waiting_for = NO_WAITING
    M    reqtype = DP_RQ_DIAWP
    M    act_reqtype = NO_REQTYPE
    M    rq_info = 0
    M    tid = -1
    M    mode = 255
    M    len = -1
    M    rq_id = 65535
    M    rq_source =
    M    last_tid = 0
    M    last_mode = 0
    M    semaphore = 0
    M    act_cs_count = 0
    M    csTrack = 0
    M    csTrackRwExcl = 0
    M    csTrackRwShrd = 0
    M    mode_cleaned_counter = 0
    M    control_flag = 0
    M    int_checked_resource(RFC) = 0
    M    ext_checked_resource(RFC) = 0
    M    int_checked_resource(HTTP) = 0
    M    ext_checked_resource(HTTP) = 0
    M    report = >                                        <
    M    action = 0
    M    tab_name = >                              <
    M    attachedVm = no VM
    M 
    M  *****************************************************************************
    M  *
    M  *  LOCATION    SAP-Server egsap701_NSP_00 on host egsap701 (wp 0)
    M  *  ERROR       ThInit: db_connect
    M  *
    M  *  TIME        Fri Jun 10 19:25:19 2011
    M  *  RELEASE     701
    M  *  COMPONENT   Taskhandler
    M  *  VERSION     1
    M  *  RC          13
    M  *  MODULE      thxxhead.c
    M  *  LINE        10783
    M  *  COUNTER     1
    M  *
    M  *****************************************************************************
    M 
    M  PfStatDisconnect: disconnect statistics
    M  Entering TH_CALLHOOKS
    M  ThCallHooks: call hook >BtcCallLgCl< for event BEFORE_DUMP
    M  ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
    M  *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c   723]
    M  *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c  261]
    M  Entering ThSetStatError
    M  ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
    M  Entering ThReadDetachMode
    M  call ThrShutDown (1)...
    M  ***LOG Q02=> wp_halt, WPStop (Workproc 0 2768) [dpnttool.c   334]

    Hello Rattandeep and Markus,
    Thanks for explaining the error to me. I'm still facing the issue though!
    My start profile is START_DVEBMGS00_egsap701 and instance profile is NSP_DVEBMGS00_egsap701 (they are included below).
    In both profiles, the dbs/ada/schema has been currently deactivated. I get the same errors even after deactivating the parameter in both profiles. I also tried your suggestions by setting parameter values to SAPNSP and then to SAPR3 in both profiles but I'm still getting the same errors.
    > the above log shows that you have to change the parameter with schema user SAPR3 instead of SAPNSP
    You mean that the SAP system is started by SAPNSP user and since the profile is executed by SAPNSP user, we are getting the error? I don't know about the SAPR3 user or the user's credential. I only use bcuser/ddic RFC user to logon to SAP.
    I don't know how to check the table space for SAPR3 database. As far as I know, BRTools is only for Oracle backends. So, I used Max DB database manager tool instead and found that the default NSP database has utilized about 50% data area (disk space). Overwrite mode is on and I have about 100% free log area (also determined through database manager tool). Still have not clue as to how to solve this. Please help. Thanks for your tips so far!
    The start profile is as follows :
    #.*       Start profile START_DVEBMGS00_EGSAP701                                                                               *
    #.*       Version                 = 000004                                                                                *
    #.*       Generated by user = DDIC                                                                                *
    #.*       Generated on = 27.04.2011 , 11:02:57                                                                                *
    SAPSYSTEMNAME = NSP
    SAPGLOBALHOST = egsap701
    SAPSYSTEM = 00
    INSTANCE_NAME = DVEBMGS00
    DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTI386
    DIR_EXECUTABLE = $(DIR_INSTANCE)\exe
    DIR_PROFILE = $(DIR_INSTALL)\profile
    _PF = $(DIR_PROFILE)\NSP_DVEBMGS00_egsap701
    # Copy SAP Executables
    Start_Program_00 = immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF)
    # Start ABAP database
    _DB = $(DIR_CT_RUN)\strdbs.cmd
    Start_Program_01 = immediate $(_DB) NSP
    # Start SAP message server
    _MS = $(DIR_EXECUTABLE)\msg_server$(FT_EXE)
    Start_Program_02 = local $(_MS) pf=$(_PF)
    # Start application server
    _DW = $(DIR_EXECUTABLE)\disp+work$(FT_EXE)
    Start_Program_03 = local $(_DW) pf=$(_PF)
    rsdb/dbid = NSP
    #dbs/ada/schema = SAPNSP
    Instance profile is as follows:
    #.*       Instance profile NSP_DVEBMGS00_EGSAP701                                                                              *
    #.*       Version                 = 000006                                                                                *
    #.*       Generated by user = DDIC                                                                                *
    #.*       Generated on = 27.05.2011 , 11:30:39                                                                                *
    SAPSYSTEMNAME = NSP
    SAPGLOBALHOST = egsap701
    SAPSYSTEM = 00
    INSTANCE_NAME = DVEBMGS00
    DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTI386
    DIR_EXECUTABLE = $(DIR_INSTANCE)\exe
    rdisp/wp_no_dia = 3
    rdisp/wp_no_btc = 1
    icm/server_port_0 = PROT=HTTP,PORT=80$$
    # SAP Message Server parameters are set in the DEFAULT.PFL
    ms/server_port_0 = PROT=HTTP,PORT=81$$
    rdisp/wp_no_enq = 1
    rdisp/wp_no_vb = 1
    rdisp/wp_no_vb2 = 1
    rdisp/wp_no_spo = 1
    PHYS_MEMSIZE = 128
    em/initial_size_MB = 10240
    em/max_size_MB = 1024
    abap/buffersize = 100000
    #old_value: 0                                                                                changed: DDIC 27.04.2011 11:04:52
    #old_value: 60000000                                                                           changed: DDIC 27.05.2011 11:29:55
    alert/MONI_SEGM_SIZE = 0
    enque/table_size = 2000
    #parameter deactivated                      by: DDIC         27.05.2011 11:11:00
    #rspo/local_print/method = 2
    rsdb/ntab/entrycount = 5000
    rsdb/ntab/ftabsize = 3000
    rsdb/ntab/sntabsize = 100
    rsdb/ntab/irbdsize = 1000
    rsdb/cua/buffersize = 500
    rsdb/obj/buffersize = 2048
    rsdb/obj/max_objects = 500
    rsdb/otr/buffersize_kb = 1000
    rsts/ccc/cachesize = 6000000
    rtbb/buffer_length = 500
    rtbb/max_tables = 50
    sap/bufdir_entries = 200
    zcsa/presentation_buffer_area = 350000
    zcsa/calendar_area = 300000
    zcsa/table_buffer_area = 3000000
    zcsa/db_max_buftab = 500
    ztta/roll_area = 1000000
    ztta/diag_area = 128000
    ztta/dynpro_area = 150000
    ztta/cua_area = 180000
    rdisp/PG_SHM = 100
    rdisp/PG_MAXFS = 256
    rdisp/ROLL_SHM = 100
    rdisp/ROLL_MAXFS = 2048
    #old_value: 0                                                                                changed: DDIC 27.04.2011 11:04:52
    #old_value: 300                                                                                changed: DDIC 27.05.2011 11:29:38
    rdisp/autoabaptime = 0
    rdisp/wp_ca_blk_no = 20
    rdisp/appc_ca_blk_no = 20
    rdisp/max_wprun_time = 30000
    icm/min_threads = 5
    icm/max_threads = 10
    icm/max_conn = 20
    mpi/total_size_MB = 10
    rsdb/dbid = NSP
    #parameter deactivated                      by: DDIC         27.05.2011 11:11:22
    #dbs/ada/schema = SAPNSP

  • Load from ODS into InfoCube gives TIME-OUT runtime error after 10 minutes ?

    Hi all,
       We have a full load from ODS into InfoCube and it was working fine till the last week upto with 50,000 records. Now, we have around 70,000+ records and started failing with TIME_OUT runtime error.
       The following is from the Short Dump (ST22):
       The system profile "rdisp/max_wprun_time" contains the maximum runtime of a
    program. The current setting is 600 seconds. Once this time limit has been exceeded, the system tries to terminate any SQL statements that are currently being executed and tells the ABAP processor to terminate the current program.
      The following are from ROIDOCPRMS table:
       MAXSIZE (in KB) : 20,000
       Frequency       :  10
       Max Processes : 3
      When I check the Data Packages under 'Details' tab in Monitor, there are four Data Packages and the first three are with 24,450 records.  I will right click on each Data Package and select 'Manual Update' to load from PSA. When this Manual Update takes more than 10 minutes it is failing with TIME_OUT again.
      How could I fix this problem, PLEASE ??
    Thanks,
    Venkat.

    Hello A.H.P,
    The following is the Start Routine:
    PROGRAM UPDATE_ROUTINE.
    $$ begin of global - insert your declaration only below this line  -
    TABLES: /BIC/AZCPR_O0400, /BIC/AZCPR_O0100, /BIC/AZCPR_O0200.
    DATA: material(18), plant(4).
    DATA: role_assignment like /BIC/AZCPR_O0100-CPR_ROLE, resource like
    /BIC/AZCPR_O0200-CPR_BPARTN.
    $$ end of global - insert your declaration only before this line   -
    The follow definition is new in the BW3.x
    TYPES:
      BEGIN OF DATA_PACKAGE_STRUCTURE.
         INCLUDE STRUCTURE /BIC/CS8ZCPR_O03.
    TYPES:
         RECNO   LIKE sy-tabix,
      END OF DATA_PACKAGE_STRUCTURE.
    DATA:
      DATA_PACKAGE TYPE STANDARD TABLE OF DATA_PACKAGE_STRUCTURE
           WITH HEADER LINE
           WITH NON-UNIQUE DEFAULT KEY INITIAL SIZE 0.
    FORM startup
      TABLES   MONITOR STRUCTURE RSMONITOR "user defined monitoring
               MONITOR_RECNO STRUCTURE RSMONITORS " monitoring with record n
               DATA_PACKAGE STRUCTURE DATA_PACKAGE
      USING    RECORD_ALL LIKE SY-TABIX
               SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
      CHANGING ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update
    $$ begin of routine - insert your code only below this line        -
    fill the internal tables "MONITOR" and/or "MONITOR_RECNO",
    to make monitor entries
       clear DATA_PACKAGE.
       loop at DATA_PACKAGE.
          select single /BIC/ZMATERIAL PLANT
             into (material, plant)
             from /BIC/AZCPR_O0400
             where CPR_EXT_ID = DATA_PACKAGE-CPR_EXT_ID
             and ( MATL_TYPE = 'ZKIT' OR MATL_TYPE = 'ZSVK' ).
           if sy-subrc = 0.
              DATA_PACKAGE-/BIC/ZMATERIAL = material.
              DATA_PACKAGE-plant = plant.
              modify DATA_PACKAGE.
              commit work.
           endif.
           select single CPR_ROLE into (role_assignment)
                         from /BIC/AZCPR_O0100
                         where CPR_GUID = DATA_PACKAGE-CPR_GUID.
            if sy-subrc = 0.
              select single CPR_BPARTN into (resource)
                         from /BIC/AZCPR_O0200
                         where CPR_ROLE = role_assignment
                         and CPR_EXT_ID = DATA_PACKAGE-CPR_EXT_ID.
                   if sy-subrc = 0.
                      DATA_PACKAGE-CPR_ROLE = role_assignment.
                      DATA_PACKAGE-/BIC/ZRESOURCE = resource.
                      modify DATA_PACKAGE.
                      commit work.
                   endif.
              endif.
           clear DATA_PACKAGE.
           endloop.
    if abort is not equal zero, the update process will be canceled
      ABORT = 0.
    $$ end of routine - insert your code only before this line         -
    Thanks,
    Venkat.

  • ABAP trail 7.00 timeouts and background process

    Does anyone knows if it's possible to change the number of dialog and background processes?
    And the transaction to change the timeouts of such processes?
    Thank you

    you can change the timeout in rz11.Parameter-name is rdisp/max_wprun_time. Backgound processes habe no timeout, so this value is only valid for dia-processes
    To change the number, you have to adjust your instance profile. In the forum  'Netweaver Administrator' should be some information about that. So just the short hint: you can adjust the profiles in RZ10, but have to do some steps for that. Just search in NW-Admin-forum above.
    Regards,
    ulf

Maybe you are looking for