Process chain Hang

Hi,
In general, the process chain when being put to schedule resets the old
runs and also removes any active run from schedule.
This is not happening, and the system gives the dump with message "MESSAGE_TYPE_X".
which says it is due the old job still in active run state.
This was not happening before since our go-live. we started getting the issue from the last two weeks.
We r in BI 7.0. Kindly suggest how to rectify this.
Regards,
Ahmed

I rescheduled the process chain , after removing it from the schedule. which deleted the old released jobs. This resolved my problem. but the process chain when being put to schedule should resets the old runs and also removes any active run from schedule. which was not happening.
My issue is resolved, hence i close it.

Similar Messages

  • Process chain hangs due to locks in SM12

    We are currently experiencing issues when executing the process chains. The process chain hangs at one or more DTP loads without executing the following step even though the DTP load is successfully complete (Green). Upon research found that the system locks in SM12 are not released for these DTP loads which is causing the process chain to hang.
    Once I delete the lock manually, the process chain continues with the subsequent steps. This is painful during night time loads and hence am wondering if you guyz are aware of a fix for this problem.
    FYI, we our system is BI 7.0 and SP 13. Any leads towards the solution are highly appreciated. Thanks!

    hi Chetan,
    Please enlight me, with your suggestion here you are asking to increase the BGD processes for that particular process chain or for system (SID) as whole?
    Please help to understand better.
    Thanks in advance
    Regards
    Sekhar

  • Process chain hangs when reaching AND process before Attribute Change Run

    Hi Experts,
    I have the following problem. For some reason my master data attribute process chain hangs when it reaches the AND process variant right before the Attribute Change Run. It does not go anywhere from that point.
    Thank you

    hi AG,
    if this is hanging daily at the same place without proceeding further, and with out giving the instance for the same. then the better way is to replace that AND process in the chain with the new AND process. and then check and activate ur chain. this wil solve ur problem.
    if this is the first time that happend to u, then check the previous load status, if any of the load has failed and u didnt turned the status of the process then also this can happen. So please do check it and act accordingly. If u cannt find the resolution then please run ur changerun manually.
    u can use RSPC_PRCESS_FINISH FM to convert the status of any process. for this u need to give instance and variant details. and then if u execute, then chain will continue further.
    Hope this will help you.
    thanks
    Vishnu

  • Process Chain hangs on AND process

    Help Super gurus!
    I've tried several versions of a chain that loads multiple InfoPackages serially then multiple DTP in parallel using filtering from the PSA to a DSO. All load successfully. Then I have the DTPs all meet at an 'AND' process before processing should continue to a cube.
    The 'AND' process also shows green but it does not continue to the next process step. It just stops there, no more jobs running, no yellow, nothing. It thinks it's all done, everything after that is still blue.
    Why does it hang there and what can I do to get it to continue?
    Thanks,
    Al
    Points available.

    Hi,
    Not sure what is the root cause in your case.
    Try this. It may work. Normally this is done after a step turns red and no repeat is available.
    Method 1 (when it fails in a step/request)
    /people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
    How is it possible to restart a process chain at a failed step/request?
    Sometimes, it doesn't help to just set a request to green status in order to run the process chain from that step on to the end.
    You need to set the failed request/step to green in the database as well as you need to raise the event that will force the process chain to run to the end from the next request/step on.
    Therefore you need to open the messages of a failed step by right clicking on it and selecting 'display messages'.
    In the opened popup click on the tab 'Chain'.
    In a parallel session goto transaction se16 for table rspcprocesslog and display the entries with the following selections:
    1. copy the variant from the popup to the variante of table rspcprocesslog
    2. copy the instance from the popup to the instance of table rspcprocesslog
    3. copy the start date from the popup to the batchdate of table rspcprocesslog
    Press F8 to display the entries of table rspcprocesslog.
    Now open another session and goto transaction se37. Enter RSPC_PROCESS_FINISH as the name of the function module and run the fm in test mode.
    Now copy the entries of table rspcprocesslog to the input parameters of the function module like described as follows:
    1. rspcprocesslog-log_id -> i_logid
    2. rspcprocesslog-type -> i_type
    3. rspcprocesslog-variante -> i_variant
    4. rspcprocesslog-instance -> i_instance
    5. enter 'G' for parameter i_state (sets the status to green).
    Now press F8 to run the fm.
    Now the actual process will be set to green and the following process in the chain will be started and the chain can run to the end.
    Of course you can also set the state of a specific step in the chain to any other possible value like 'R' = ended with errors, 'F' = finished, 'X' = cancelled ....
    Check out the value help on field rspcprocesslog-state in transaction se16 for the possible values.
    Thanks,
    JituK

  • Process Chain hangs -  BI_PROCESS_TRIGGER

    I kick off a process chaing and check SM37.
    Job BI_PROCESS_TRIGGER appears in active mode.
    The job log shows <b>"Job started" but that's it</b>.
    The job never ends and the data doesn't come in.
    Has anyone had this issue before?  BW 3.5 Highest support pack:  SAPKW35010

    Hi,
    We have encountered that problem before but an advance correction solved the problem. We are running BW 3.1 while you have BW 3.5 so I presume that the advance correction we applied is already in your system.
    You may find additional help from OSS. Search <b>BI_PROCESS_TRIGGER</b> or "<i>Process Chain</i>".
    It could be a program issue.
    Check also if you can run your infopackages separately (just to isolate if the problem is within the process chain or in your actual process steps such as Infopackage loading).
    --Jkyle

  • Process chain hangs on Yellow , no process no data load, nothing happens...

    Hi friends  ,
    I have a  problem on one of our Meta chain . We have a meta chain , and it have some sub chains .  It is a daily scheduled meta chain.
    One day some thing happened and one of the sub chain begun to hang on . One of the sub chain of meta Chain I see Yellow light, which means on process . But while I enter into this sub chain I see nothing processed .  Meta chain finish previous chain but besides nothing .
    I tried to remove this sub chain from schedule , I tried to reactivate , and to schedule again , but all of my attems didn't solve anything . All of them get an short dump because of maximum time
    I need your helps .
    Thanks

    hi  dear,
    I guess u already got so many solutions and none of them working try these out.....
    1.Try activating the chain ...is there some issue in that??
    2.Now go to the top...menu..execution tab...remove from schedule...Now schedule again...
    3.If you want to run the chain immediately...after doing remove from schedule go to the start variant and change the option as start immediately.
    Since the chain is not triggering ,moving forward after start variant then may be the load on the system is too much or else the chain has activation issues...
    Regards,
    rocks

  • Process chain taking long time

    Hi,
        I developed a Process chain. In developemnt for Completion of the Update rules(Start routine) its taking 60m( for around 50,000 records).
    After transporting the Process chain to Production for Start routine completion (For 1,70,000 records) its taking 7hrs and sometimes its failing as the "Process is Over due" and sometimes due to "Short dump".
    How to handle this.........
    Thanks

    Hi js,
    Check the ST22... Any dumps
    Check out for the short dump in source system and try loading the delta again
    then
    I have got the problem when u have posted...but little later.Even I was about to post the issue.. Actually my issue was...
    My PC is like this
    1) Start Process
    2) Delete index
    3) Load IP
    4) delete overlapping request
    5) create Index
    6) ABAP program
    Process chain hangs at Overlapping requests process type but the status was yellow. And the previous step (3) was success. From there its not moving to next further steps.. But the Job in SM37 was canceled.
    I saw Ur post and saw the note 833168 and which matches exactly our issue.
    Like we run the PCs thru the TIDAL where due to some problems PC got triggered twice... I can see the two logs in the PC. (Log view) and two requests at RSMO.
    Everything was recovered again thru manual steps. This is the first time we encountered... the note helped us ... We now are very cautious about the Tidal runs...
    Now PC is running perfectly
    we have instructed the Supported team to make the necessary changes or fix this issues in TIDAL...
    i hope this is helpful to u
    bye now
    suresh

  • How to stop/cancel Process Chain in BI 7.0

    Hi,
    Could you tell me how to stop/cancel a process chain that hangs with status yellow or green in BI 7.0? There was an easy option to do it in 3.x, but I cannot find a similar option in 7.0.
    What happens is that at random our process chains hang at a certain variant with either yellow or even green status and do not proceed further. What happens is that in a couple of hours another pchain run occurs and it executes fine. Then again at random (might be the same day or the next day) the process chain hangs again. I think that all those "hanged" pchains pile up in the queue, so that it cause other future pchains to hang as well at some point. So, is there anyway to stop/cancel these zombie process chains when it stops at a particular event RSPROCESS in BI 7?
    Thank you,
    AG
    Message was edited by:
            AG

    Hi Frank,
    Thanks for your reply. I have a few questions.
    1)SM37 -->Kill Job
    We cannot do that because the job has already finished.
    2)SM50/sm66- ->Kill process
    There are no hanged processes to kill
    3)RSPC>Job Log>Make the process RED forecefully
    How do you do that exactly?
    4)RSPC>Process chain> main Menu"Remove from Scheduling"  OR
    5)se37-->RSPC_API_CHAIN_INTERRUPT
    give RFC BW system name(technical) and process chain name(technical) - we can do this,  but what exactly would it accomplish. Would it remove the process chain from any runs in the future or also any hanged ones in the past? An how is this step different from #4?
    Thank you,
    AG

  • Process Chains - Incompletion Status

    Hi,
    I am having regular scheduled process chain. In the chain log, At the middle of the chain, chain was showing green, rest of the chain was showing gray color. But i can see rest of the data loads completed after checking the data targets manually.
    Can you please tell me the reason, why the rest of the process chain is not showing complete status (Green status) in log view?
    Best Regards,
    Venkata

    Hi
    The reason may be becose...
    The chain was ran twice....
    When the Chain PC ran twice .. the PC gets hang..  there is a note on this issue...
    Please serach the note witht he Key word : "Process chain hangs"..
    And there is a Big discussin which was raised by Pradep Patil.. please search once.. that thread .  u will get lot if info...
    hope it helps..
    regards
    AK
    HERE IS THE NOTE NO: 833168 please check it once...
    Message was edited by:
            A K

  • Process chain executed synchronously produces dump and hangs

    Process chain (RSPC) being executed synchronously hangs on a step (not first) with yellow status. Analysis of ST22 shows there is dump: RAISE_EXCEPTION
    The chain loads data from flat files on frontend to several characteristics (attributes and texts). All the steps are sequential.
    After the start first file is loaded successfully (info package), subsequent data transfer process has no errors too. But the second info package becomes yellow and hangs just after ( after some time timeout occurs and the step becomes red). In ST22 i see dump, text of the dump is below. Analysis of the dump reveals that 'GUI_UPLOAD' FM doesn't work during execution of the second info-package.
    The chain looks as follows:
    1. Info package 1
          V
    2. Data transfer process 1
          V
    3. Info package 2              <-------   hangs here because of dump
          V
    4. Data transfer process 2
         V
    Hangs on step 3 (infopackage 2).
    Text of the dump:
    Runtime Errors         RAISE_EXCEPTION
    Date and Time          10.10.2010 19:07:59
    |Short text                                                                                |
    |    Exception condition "NOT_SUPPORTED_BY_GUI" raised.                                            |
    |What happened?                                                                                |
    |    The current ABAP/4 program encountered an unexpected                                          |
    |    situation.                                                                                |
    |Error analysis                                                                                |
    |    A RAISE statement in the program "CL_GUI_FRONTEND_SERVICES======CP" raised the                |
    |     exception                                                                                |
    |    condition "NOT_SUPPORTED_BY_GUI".                                                             |
    |    Since the exception was not intercepted by a superior                                         |
    |    program, processing was terminated.                                                           |
    |                                                                                |
    |    Short description of exception condition:                                                     |
    |                                                                                |
    |                                                                                |
    |    For detailed documentation of the exception condition, use                                    |
    |    Transaction SE37 (Function Library). You can take the called                                  |
    |    function module from the display of active calls.                                             |
    |    -                                                                                |
    |How to correct the error                                                                          |
    |                                                                                |
    |    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:                                                                                |
    |                                                                                |
    |    "RAISE_EXCEPTION" " "                                                                         |
    |    "CL_GUI_FRONTEND_SERVICES======CP" or "CL_GUI_FRONTEND_SERVICES======CM00X"                   |
    |    "FILE_EXIST"                                                                                |
    |                                                                                |
    |    or                                                                                |
    |                                                                                |
    |    "CL_GUI_FRONTEND_SERVICES======CP" "NOT_SUPPORTED_BY_GUI"                                     |
    |                                                                                |
    |    or                                                                                |
    |                                                                                |
    |    "RSBATCH1 " "NOT_SUPPORTED_BY_GUI"                                                            |
    |    If you cannot solve the problem yourself and want to send an error                            |
    |    notification to SAP, include the following information:                                       |
    |                                                                                |
    |System environment                                                                                |
    |    SAP-Release 701                                                                               |
    |                                                                                |
    |                                                                                |
    |    SAP kernel....... 701                                                                         |
    |                                                                                |
    |    Patch level. 69                                                                               |
    |    Patch text.. " "                                                                              |
    |                                                                                |
    |User and Transaction                                                                              |
                                                                                    |
    |    Program............. "CL_GUI_FRONTEND_SERVICES======CP"                                       |
    |    Screen.............. "SAPMSSY0 1000"                                                          |
    |    Screen Line......... 6                                                                        |
    |                                                                                |
    |Information on where terminated                                                                   |
    |    Termination occurred in the ABAP program "CL_GUI_FRONTEND_SERVICES======CP" -                 |
    |     in "FILE_EXIST".                                                                             |
    |    The main program was "RSBATCH1 ".                                                             |
    |                                                                                |
    |    In the source code you have the termination point in line 8                                   |
    |    of the (Include) program "CL_GUI_FRONTEND_SERVICES======CM00X".                               |
    |Source Code Extract                                                                               |
    |Line |SourceCde                                                                                |
    |    1|method FILE_EXIST.                                                                          |
    |    2|* ...                                                                                |
    |    3|                                                                                |
    |    4|  CLASS CL_GUI_CONTROL DEFINITION LOAD .                                                    |
    |    5|                                                                                |
    |    6|*-check if valid GUI is available----
                             |
    |    7|  IF IS_VALID_HANDLE( ) NE 0 AND cl_gui_control=>www_active IS INITIAL.                     |
    |>>>>>|    RAISE NOT_SUPPORTED_BY_GUI.                                                             |
    |    9|  ENDIF.                                                                                |
    |   10|                                                                                |
    |   11|* check parameter, wild characters not allowed                                              |
    |   12|  IF FILE IS INITIAL OR FILE CA '*<>|"'.                                                    |
    |   13|  MESSAGE 'WRONG PARAMETER: FILE_NAME' TYPE 'I' RAISING WRONG_PARAMETER.                    |
    |   14|    EXIT.                                                                                |
    |   15|  ENDIF.                                                                                |
    |   16|                                                                                |
    |   17|* special handling for SAPGUI for HTML                                                      |
    |   18|  IF CL_GUI_CONTROL=>WWW_ACTIVE IS NOT INITIAL.                                             |
    |   19|                                                                                |
    |   20|    DATA: rc type i, filename(4096) type C.                                                 |
    |   21|    filename = file.                                                                        |
    |   22|    CALL FUNCTION 'ITS_QUERY'                                                               |
    |   23|      EXPORTING                                                                             |
    |   24|        filename = FILEname                                                                 |
    |   25|        query    = 'FE'                                                                     |
    |   26|      IMPORTING                                                                             |
    |   27|        return   = rc.                                                                      |
    |Active Calls/Events                                                                               |
    |No.   Ty.          Program                             Include                             Line   |
    |      Name                                                                                |
    |    8 METHOD       CL_GUI_FRONTEND_SERVICES======CP    CL_GUI_FRONTEND_SERVICES======CM00X     8  |
    |      CL_GUI_FRONTEND_SERVICES=>FILE_EXIST                                                        |
    |    7 FUNCTION     SAPLSFES                            LSFESU16                               96  |
    |      GUI_UPLOAD                                                                                |
    |    6 METHOD       CL_GUI_FRONTEND_SERVICES======CP    CL_GUI_FRONTEND_SERVICES======CM013     4  |
    |      CL_GUI_FRONTEND_SERVICES=>GUI_UPLOAD                                                        |
    |    5 METHOD       CL_RSDS_ACCESS_GUI_UPLOAD=====CP    CL_RSDS_ACCESS_GUI_UPLOAD=====CM001    74  |
    |      CL_RSDS_ACCESS_GUI_UPLOAD=>IF_RSDS_EXTRACT_DIRECT~EXTRACT                                   |
    |    4 FUNCTION     SAPLRSDS_BACKEND                    LRSDS_BACKENDU01                      304  |
    |      RSDS_DATA_PULL                                                                              |
    |    3 FUNCTION     SAPLRSSM                            LRSSMU17                             5422  |
    |      RSSM_CALL_RSAR_DATA_REQUEST_1                                                               |
    |    2 FORM         RSBATCH1                            RSBATCH1                             1327  |
    |      START                                                                                |
    |    1 EVENT        RSBATCH1                            RSBATCH1                              498  |
    |      START-OF-SELECTION                                                                          |

    If i load the step manually it works. The hung step is possible to re-execute after it gets red (with context menu) and it works then. After that it hangs on the 3rd info-package and so on.
    The file lays on a network drive, but i suspect it doesn't matter

  • Process Chains Always Hangs at the second step waiting for an event

    Gents;
    all BI process chains created in Production system are always hanging in the second step waiting for an event RSPROCESS with a certain parameter. This issue is happening for all process chains in Production system and it is not happening for the same in other systems in the landscape (development, Copy of porudction, quality and so on). I tried to trigger the event manually using SM62 but the job is always stick to status " released". the same thing was replicated in other systems and the job status has changed and the process was completed.
    Any idea what might cause this issue??
    Thanks.

    Hi,
    You said that this thing is happening only in production system.Try doing the following checks :
    1.Check SM21to see if there are any red entries.It can be possible that there is some data base RFC connection failure.While checking SM21, make sure you give proper selection condition.If there are any red entries, you may take the help of basis guys to understand the type of failure.May be file system has got some problems.
    2.Check St22 and try to analyse if any short dumps.
    3.Try to check Connection with the source system ( Goto RSA1->source system tab->right click on the source system and select check option to find if any errors in the connection.
    4.If possible, try to load manually in some other info provider.
    Thanks,
    Tarun Brijwani.

  • Process chains time outs and hangs with no error msg - in SP13

    Hi all,
    We are having all kind of weird problems after we patched our system with SP13. Our process chain time outs and hangs, but surprisingly we never get any error msg. And scarier part is, the problem seems to be intermittent. PC runs fine on some days and hangs on some.
    Further analysis into the dump – as below
    Termination occurred in the ABAP program "SAPLRSSM" -
    in "RSSM_SLEEP_DEBUG".
    The main program was "SAPMSSY1 ".
    In the source code the termination point is in (Include) program "LRSSMU39".
    This refers to an issue that appears to have been addressed by OSS Note
    934648(meant for SP8). This notes also indicates to populate RSADMIN table to
    exclude "RSSM_SLEEP_DEBUG". Not sure if this note is valid for SP13? However we went ahead and populated the RSADMIN table.
    So now we have no clue what’s going on and where to fix the issue.
    As per SAP suggestion we applied the following notes:
    0000653996  Analyzing lock situations
    0000893563  Correction: Deadlock on completion of a remote chain
    0000994007  Corrections: Deadlock with external status query
    0001005481  Correction: Process successful, but there is no instance
    0001047174  Correction: Incorrect scope when locking in process chains
    0001051957  Correction: TIME_OUT during dialog confirmation of processes
    0001083660  Report for error stack analysis
    Nothing seems to help us. And SAP suggested a few options, which we implemented to no rescue.
    I’m sure that many of the customers have applied SP13, and want some feedback from them, if this is happening in their systems too?
    If so, how did you fix this issue?
    Or this situation is unique to us?Please note that no settings were changed as of SP13 to that of what they were in SP12(unless it is a side effect of the patch itself). Everything worked fine with SP12 and is still working on the BIP system. All the problems are in BIQ patched to SP13.
    Any pointers or insight would be appreciated. We have a customer msg open with SAP, and going back and forth, but nothing seemed to work as of today.
    Thanks,
    Voodi

    Not sure which OSS helped us get past the issue, as SAP asked us to apply a ton of notes. But along which the notes, SAP has some suggestions for us, which we think did the magic. After the implementation of the suggestin we never faced the same issue again. The suggestion by SAP:
    move the process chain callback in a batch job by executing
    program RSSM_TRACE_SWITCH and selecting the flag "verifcation
    of asynchronous processes - execute in batch".
    Lemme know if this doesnt fix the issue, I can give all the notes that SAP asked us to apply.
    Message was edited by:
            voodi

  • Data Change event triggering Process hangs in Process chain

    HI Folks,
    In a daily running Process chain we have a Data Change event triggering Process , to trigger broadcasting  settings
    This process is running for a long time , with no progress
    in SM50 , there are 2 process
    Process 1 : RSRD_BROADCAST_STARTER  Status : OnHold Reason : SLEEP
    Process 2 : SAPLRSRD_X_RUNTIME  Status : OnHold  Reason : RFC
    I tried to change the Parallel Processing setting as Number of Processes = 1
    But still the process is hanging.
    Any inputs will be a great help.
    Thanks
    Sonal......
    P.S : SAP_BW     700     0022     SAPKW70022     SAP NetWeaver BI 7.0 and EP 6.0
    Edited by: Sonal Patel on Feb 2, 2010 1:47 PM

    Hi sonal,
    I would suggest you to uninstall all the components and start all new again, n please make sure you have the following order :-
    1) install GUI 710 along with BEx 7.0 and 3.x complete.
    2) install BW AddOn (bw350gui710_8-10004473.exe latest one from Service market Place).
    3) Install BI AddOn (bi710sp11_1100-10004472.exe latest one from Service market Place).
    4) Install SAP precalc server (xPreCalServer10_1-10004472.exe, latest one from Service market Place).
    In service market place you can get the components from Downloads ->Support Packages and Patches -> Entry by Application Group -> "SAP Frontend Components"
    Also, plz make sure that you restart your Server OS after each and every installation.
    This would solve your problem.
    Rgds,
    Sreekul Nair

  • Event Data Change triggering process hangs in the process chain

    Hi,
    In a daily running process chain we have an event data change trigger for broadcast setting which goes to long running status very often and ultimately we have to cancel the job in precalcserver and manually execute the reports based on it. This step fails very often and  rarely it gets executed in the chain with a green status. I want to know the reason for the failure and the solution for permanent fix.
    On digging through the respective logs thru SLG1 I found the following error messages for the same. Please find it below if it can help u in analysis
    Any inputs will be a great help!!
    Thanks
    Kavya

    it's related to precal server, I guess it failed due to lack of memory or setting issue.
    Please do following
    1 Clear all precal server pendings
    2 After this, restart the server.
    3 Execute again.

  • InfoPackage Hangs when called from Process Chain

    We recently implemented the 2LIS_04_P_ARBPL DataSource and have scheduled the execution of a Delta InfoPackage in our nightly Process Chains.
    After working correctly for 2 weeks the InfoPackage has hung the last 3 nights. It is being called and when I view the process chain log it is in the yellow (in process) status. When I look in SM37 in R/3 the extractor has not been called.
    All of our master data and transactional data from other areas runs prior to this extractor and works perfectly via the process chain and if I force the InfoPackage to red and re-execute manually for 2LIS_04_P_ARBPL I have no problems.
    How/where should I troubleshoot this?

    Hi Jonathan,
    Goto your process chain-> Select the delta infopackage -> right click and select wait time and enter the time in seconds. You could set it to 600 secs(10 minutes).
    This would be a permanent solution to your problem as you need not go to BD87 each time for your data load.
    Bye
    Dinesh

Maybe you are looking for