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

Similar Messages

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

Infopackage in process chain failing due to short dump on regular basis.

HI Experts,
There is a daily process chain in which one of the element (infopackage) fails due to short dump on regular basis (At least twice in a week) please find the message below
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Short text
SQL error in the database when accessing a table.
And in job log it is showing ARFCSTATE = SYSFAIL
We are able to resolve it just manual update and the process goes fine no issues but my question here is what is the exact reason for this and how to resolve it permanently or decrease the frequency of the error.
Please if any one can tell the root cause and the solution to avoid the issue in future on regular basis.
and also can any one elaborate what is ARFCSTATE = SYSFAIL,for trfc check we don't have access to SM58 in ECC side
and trfc is fine in bw side
Appreciate for not giving the general solutions like repeated solutions already posted in SDN
with regards,
musai

You can contact your BASIS person he can help you reg table space issue. it says used space is 98% and free space is 1.03%.
ask your basis to set a threshold to check the space and send a mail notification to all daily regarding the space allocation and utilization.
ARFCSTATE = SYSFAIL means the TRFC did not processed properly to the BW system from source.
Monitoring object with information about tRFC and qRFC calls that are waiting to be executed in this system; after they have been executed, they are deleted from table ARFCRSTATE.
Are there any hung TRFCs which are not processed to BW side. have you checked it
first check
load monitor -- menu -- environment -- job overview -- status of job(is it finsihed or not?) - check the job log -- ther try to find out the hung TRFc
press find --tyep "sysfail" ok -- it will display all the hung or fialed TRFCs which are not processed to BW system.
if you find the hung TID with respect to your load.. next goto SM58 trasaction to process the trfcs manually or use the load monitor menu -- environment -- transaction RFC -- source sys -- it will take you to same SM58 screen -- click F8 it will display the hung TRFc in that duration.
select the TRFc and click on F6 to process them manually.
also check the loackwaits anddead locks in ST04/DB6COCKPIT.( ask basis to check) if any dead locks are there they will take care of it.
check for short dumps in st22 if any and try to analyse.
Check the SM21 system logs.

Process chain error aleremote is locked

hi to all,
i got errors in process chain. the message asks me to go to environment>rfc transaction >in data warehouse
when i do that it says aleremote is locked. but when i look in sm12 there is no lock entry
can u please help me

If it's happened during ODS load, check the flag for 'post data to datatarget automatically' in the maintenance of your ods. If it is checked, uncheck it.
Also you can try repeating the failed step after some time.
If it's a failed load step then you need to delete the failed request first and then have to take necessary actions.
You can execute chain from where it has failed we have SAP standard program to do this.
RSPC_PROCESS_FINISH in se38. It will ask log id, Chain,Instance, Variant, status we give as 'G' the chain can understand that the previous process has completed and the next process may continue.
Thanks..

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 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.

Master Data Process chains failing due to special charecters?

hi experts,
we have done all the master data(FI,SD,LO,QM,PM,MM,PP,PS) and created process chains and transported into production system.
when we run the process chains we are facing lot of issues regarding special charecters.
for example. 0MAT_VEND_ATTR Data source.
MATERIAL VENDOR (field - IDNLF).
'UDGÅET
&''UDGÅR
&''UDGÅET
&''36/5599/LED./FÆLLES
&''SØTRANSPORT &
those are the special charecters are coming when i try to execute through RSKC the above Material Vendors, its giving different special chars for different MATERIAL VENDORS like below.
FÆLLESSØTRANSPORT
04/5160/FORSØGSAFD.
(5150)FORSØGSAFD.
like that there are about 15 master data chains are failing.
due to that reason the below transcation chars are not executing.
please suggest me is there any routine or is there any procedure to take care of unpredicted special charecters loading successfully into BW.
regards
venuscm

I don't think its a global setting problem.
Permit the char in RSKC...
Check with the functional team why they are getting Special char values in the loads. ask them to rectify the special char so that you can extract the same to BW side.
go through the blog links provided earlier in my post...
Check the below link which might be of some use to you,..
/people/jyothi.velpula/blog/2010/12/23/removing-invalid-characters-using-field-routine
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0afbb81-f219-2c10-4181-b20f6b10e373?quicklink=index&overridelayout=true
Edited by: prashanthk on Jan 3, 2011 5:35 PM

Process chain failure due to weekly maintanence

Hi experts,
we have BI sytem shutdown every week ok sundays due weekly system maintanence.In that process we have few process chain failure as well as batch job failures and each time we have to fix it by manual loading of data.
Any one help me fixing it once for ever.
Thanks for your help.
Thanks
Smitha.

Hi,
Is ur PC running when the system is shut down?? if yes then u have to fix manually...The best practice is to finish off the loads before the system is shut down. Make sure that all the deltas are pulled before the system is down..
try this for restarting PC
/people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
after cleaning up all the datatargets u can restart it as mentioned in the above link...
Regards,
B

Process chain failed due to activation of a DSO

Hi friends,
Three four days back the process chain has been failed due to the activation error.The issue was with data and i have deleted the request in manage screen and reloaded again as repeat of delta with corrections in PSA. Which is afterwards activation is successful. Now process chain is getting failed daily saying that request is not present in the DSO( Request is no longer exists in the DSO ). But manual activation of DSO is successful.
Please help me in this reagrd.
Regards,
anil
PS: I tried by removing process chain from scheduling and rescheduling back.

Hi........
Deleting request from the PSA will not help............what is the update mode of ur ODS..........if it is overwritten............then no probs...load the request again in the target...........if not..........then do one thing...........push the request again in the target.........then...........make the QM status red................then delete the request again............just check whether u face the same issue again or not...........
Generally we face this issue............suppose we load a delta request successfully in the target.........then we delete the request without making the QM status red............and after that next delta also loaded............then while activation...............it will ask for the deleted request...........I think there is some confusion...........and u can try the trick..............it may work............
Regards,
Debjani........

Process chain failing (due to back ground jobs)

Dear Friends
Did anybody help me in this topic.
The DTP's of the particular process chain is failing frequently.
The reason is background jobs causing error
why this happens every time?
Did parallel data loading in the DTP may cause any backgound error?
Is it possible for only one update to the DTP at a time?
Thanks in advance for your replies
With Regards
Riyad

Dear,
Check may be helpful and search SDN you will find many related posts.
Error Transporting Process Chain with 2 DTPs
Regards,
Syed Hussain.

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 "Job started" but that's it.
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 BI_PROCESS_TRIGGER or "Process Chain".
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

Objects Locked by Failed Process Chain

HI,
I cannot update certain infopackages as they are locked by a failed Process Chain update, however I have checked sm12 and there are no locked items showing, also I have gone into RSA1 --> tools Attrib Change Run and into the InfoObject List and ther are no objects so i cant run the Atrrib change run from their either.
So if there is no locked items in Sm12 well then how do i unlock them?
Do i need to mark the failed Process chain as complete or something?
Thanks.

Is this in the Source Code tab? Sorry i do not see where i should input the Timestamp or where i actually run the RSDDS_AGGR_MOD_CLOSE function module?
This is the code i see when i Run SE37 with RSDDS_AGGR_MOD_CLOSE
FUNCTION RSDDS_AGGR_MOD_CLOSE.
""Lokale Schnittstelle:
*" IMPORTING
*"     REFERENCE(I_CNSID) TYPE RSSID
*" EXCEPTIONS
*"      X_MESSAGE
DATA: l_timestmp type rs_timestmp.
get time stamp field l_timestmp.
UPDATE RSDDAGGRMODSTATE set   closedfl     = rs_c_true
                                TIMESTMP_END = l_timestmp
                          where cnsid = i_cnsid.
IF SY-SUBRC NE 0.
    perform x_message using 'RSDDS_AGGR_MOD_CLOSE-1-'.
ENDIF.
ENDFUNCTION.

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

Why will Process chain fail..

Hello,
Could you please provide me the reasons for failing process chains.
Thanks in advance,
G Raghu

Hi...........
1) Suppose a PC starts twice at the same time............then Start Process will fail due to Lock issue........PC will not proceed.......In this situation Start process will remain yellow for a long time......and if you check the job log.........you can see that job is cancelled.................
2) Suppose when a PC is in progress........someone again schedule the PC..........then it will stop at the point........when the PC was scheduled again..........it will not proceed furthur.........
3) Status of Data provider can fail............Suppose one target is not loaded in the defined time...........then this process will fail...........PC will stop.....
4) Drop Pass through can fail...................Suppose data is loade from Y1 to Y2.............but not loaded in Y3( Propagation memory).............this process will fail.....
5) Attribute change Run can fail................
6) * Run or Skip is fail*................Suppose whatever parameters maintained in table YGTTC_SKIP_PARAM for a IP does'nt match then this process will fail.................
7) Loads can fail due to several reasons.............
Hope this helps you........
Regards,
Debjani............

Process chain hangs due to locks in SM12

Similar Messages

Maybe you are looking for