Process Chain error after Enpk1(7.01) upgrade - "Termination discovered"

Hello We have upgraded our BW from 7.0 to Enhpk1 (7.01) with latest stack.
After our upgrade I'm seeing our Process chain when a step errors out and there is a next step to continue with always link inspite of the error in prev step, but the Process chain does not continue and hangs and when checking the log it gives a prompt of "Termination discovered"
Gives a prompt something like this
"The analysis of chain ZP_MD_OTHER_CUST showed that process
ODSACTIVAT ZP_MD_OTHER_CUST_ACTV was terminated However the
occur) or a metachain Run 4KFMOYW9CGL10CGCQV2ZL691R could
not be ended due to the termination. It may be the case that
a metachain was not informed about the error Continue run
for chain ZP_MD_OTHER_CUST and any corresponding metachain?"
with yes or No prompt
So the chain hangs and does continue only after we enter Yes to the prompt.
We are in Q testing the upgrade this can be big issue when we dont our chain to hang for something that we want to continue always.
Opened a msg with SAP, they got back say its because of note 1398868 in the support pack, asked us to implement the manual update on RSADMIN and apply another note 1473491 - Chain not continued with termination and "ALWAYS" link.
But this has not fixed the issue, Have notified back to them and waiting.
If any of you have encountered this and resolved . pl let me know.
Thanks
Mayil

Since you just upgraded the source SAP system, it's likely that the delta queue doesn't exist for the data and has to be re-initialized. I'd suggest doing an Init w/o Data Transfer and do a Full Repair extraction to catch up on any missed data. From then on, you shouldn't have an issue with your Delta mode extraction from the source system.

Similar Messages

Common Process chain errors

Hi friends,
Can u please explain cause of below errors in process chain and how to rectify the problem ?
1. Deadlock error.
2. Error in unit conversion
3.Error 1 in update
4.Processing no data
5.Caller 70 missing
6.Idoc not processed completely.
Thanks...
Bala

Hi,
/people/mona.kapur/blog/2008/01/14/process-chain-errors
Deadlock
http://help.sap.com/saphelp_nw04s/helpdata/en/2e/44934257a5c86ae10000000a155106/frameset.htm
Dead Locks
2. Error in unit conversion
\Units of measure
3.Error 1 in update
When Src file is already open or not accessible.
4.Processing no data
theres no data selected after extraction
5.Caller 70 missing
" This error normally occurs whenever BW encounters error and is not able to classify them. There could be multiple reasons for the same
1) Whenever we are loading the Master Data for the first time, it creates SIDs. If system is unable to create SIDs for the records in the Data packet, we can get this error message.
2) If the Indexes of the cube are not deleted, then it may happen that the system may give the caller 70 error.
3)Whenever we are trying to load the Transactional data which has master data as one of the Characteristics and the value does not exist in Master Data table we get this error. System can have difficultly in creating SIDs for the Master Data and also load the transactional data.
4) If ODS activation is taking place and at the same time there is another ODS activation running parallel then in that case it may happen that the system may classify the error as caller 70. As there were no processes free for that ODS Activation.
5) It also occurs whenever there is a Read/Write occurring in the Active Data Table of ODS. For example if activation is happening for an ODS and at the same time the data loading is also taking place to the same ODS, then system may classify the error as caller 70.
6) It is a system error which can be seen under
the Status tab in the Job Over View.
solution:
" If the Master Data is getting loaded for the first time then in that case we can reduce the Data Package size and load the Info Package. Processing sometimes is based on the size of Data Package. Hence we can reduce the data package size and then reload the data again. We can also try to split the data load into different data loads
If the error occurs in the cube load then we can try to delete the indexes of the cube and then reload the data again.
If we are trying to load the Transactional and Master Data together and this error occurs then we can reduce the size of the Data Package and try reloading, as system may be finding it difficult to create SIDs and load data at the same time. Or we can load the Master Data first and then load Tranactional Data
If the error is happening while ODS activation cause of no processes free, or available for processing the ODS activation, then we can define processes in the T Code RSCUSTA2.
If error is occurring due to Read/Write in ODS then we need to make changes in the schedule time of the data loading.
Once we are sure that the data has not been extracted completely, we can then go ahead and delete the red request from the manage tab in the InfoProvider. Re-trigger the InfoPackage again.
Monitor the load for successful completion, and complete the further loads if any in the Process Chain.
6.Idoc not processed completely.
Here the request remains yellow (in process) and with the same details (as seen in the details tab of the monitor) for an abnormally long time. Many-a-times, the port for communication is not open and re-starting the load helps. For long running jobs, it may not be advisable to restart the extraction
Contact the BASIS administrator to push the IDOC.
Thanks

Step by Step documents for Process Chain Error Handling with Screen Shots

Hi
Is anybody having Step By Step Documents for Process Chain Error Handling with Screen Shots ?. Please forward it to me to my e-mail [email protected] . I will reward points to u immediately.
bye
Aamira Khan

Hi,
You can find lots of topic related to process chain issues in SDN.Please make a search in SDN.
https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_library&query=process+chain&adv=true&sdn_author_name=&sdn_updated_on_comparator=ge&sdn_updated_on=&sortby=cm_rnd_rankvalue
Regards.

Trigger a process chain(PC) after successfull completion of two other PCs

Hi All,
My requirement is to trigger a Process Chain only after successfull completion of two other process chain which are already scheduled to run at different times.
Please tell me how to achieve this into SAP-BW 3.5
Thanks
Jharna

Hi
It is very simple, I'm doing the same.
Insert Remote Process Chain at the end of the actual process chain and call the other process chain, here you need to give source , destination and process chain name in Remote process chain.
try it, it will work.
Thanks
Reddy

Process chains error

Hi all,
I converted the infopackagegroups to proces chains.It has more number of subsequent infopackages.After one infopackage execution,I added the attribute change run process.The following infopackage gives a warning message "Attribute change run process not allowed before this infopackage".Is ths warning ignorable?
If I am not adding the attribute change run process,the predecessor infopackage gives me warning"attribute run process must be followed for this infopackage".
Or should I have to add the attribute process parallely?
Any suggestions is appreciated.
One more doubt.How do I drag the process chains to the assigned nodes?At present my chains are in Not assigned nodes?
thanks.

Hi,
One more doubt.How do I drag the process chains to the assigned nodes?At present my chains are in Not assigned nodes?
To move ur process chain from notassigned.
Goto the edit mode of your process chain.
In top of ur menubar you can able to figure out a option called display component (or) ctrl +f11 (or) you can go to Process chain>attributes>Display component.
From there u can select the node, were u want to view ur process chain.
After completing the steps go back and come again to rspc. Now u can to view the process chain in ur list.

Process chains errors

Hi,
Any one can plz send the process chain errors in BI.I am in support so plz give some process chain errors.
sekhar.
Bye.

Hello Sekhar,
Please find the links might be it can help you..
Re: Process chain error for infopackage
process chains errors
http://help.sap.com/saphelp_nw70/helpdata/en/d3/53e03b8235953ee10000000a114084/content.htm
Please search in SDN you find more help..
Thanks,
Geeta

Process chains:Errors Occured..

i have selected my info objects 0CRM_PROD in rsa1 and i entered CALL MONITOR FOR BI OBJECT and then i got a monitor screen in that succesfull(42) it says...in that i have selected 0PRODUCT > TODAY DATE>
I FOUND THAT CR1 LIENT 100
02:04:56 (4 From 4 Records)i entered twise on this and i got HEADER STATUS DETAILS tabs...
in above DETAILS tab
we got a red colour in
Process chains : Error Occured
MD : Business partner & Product
like this... can u please suggest me the resolution for this...
please help me in this regard , thanks

Hi -
Please check
1) Do you have any Red request
2) Did you run delta twice
Regards
Astoria

What are the varoius type of process chain errors how we can solve them.

Hi,
I need to work with process chains maintainace , Can any body tell me what are the different type of process chain errors generelly we used to get ,how we can solve them . IF possible please provide me any document also so that i can solve my
abnormal problems for process chain errors.
Thanks in advance .

Hi,
1) Invalid characters while loading: When you are loading data then you may get some special characters like @#$%...e.t.c.then BW will throw an error like Invalid characters then you need to go through this RSKC transaction and enter all the Invalid chars and execute. It will store this data in RSALLOWEDCHAR table. Then reload the data. You won't get any error because now these are eligible chars done by RSKC.
2) IDOC Or TRFC Error: We can see the following error at u201CStatusu201D Screen:Sending packages from OLTP to BW lead to errorsDiagnosisNo IDocs could be sent to the SAP BW using RFC.System responseThere are IDocs in the source system ALE outbox that did not arrive in the ALE inbox of the SAP BW.Further analysis:Check the TRFC log.You can get to this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".Removing errors:If the TRFC is incorrect, check whether the source system is completely connected to the SAP BW. Check especially the authorizations of the background user in the source system.Action to be taken:If Source System connection is OK Reload the Data.
For more errors and solutions go thorugh the link below
http://indelasap.blogspot.com/2009/04/sap-bi-production-support-issues.html
Regards,
Marasa.

What are some of the process chain errors one comes across?

hi friends
What are some of the process chain errors one comes across?

Hello Kiran,
Here are some of the errors that come across...
-> Rollup not possible, no filled aggregates available
-> Error when starting the extraction program
-> The process step locked by another changerun
-> Info objet does not contain alpha confirming values
-> Errors due to non activated objects
-> Errors due to duplicate records
-> Errors due to locking
-> Problems because of connection problem between source and bw systems
-> Problems due to RFC
Hope this helps you
Cheers
SRS

How repeat a process step in a process chain automatically after error?

Hello guys.
Have some method to repeat automatically a process in a process chain after a error occur ?
Now, we need to make a manual procedure for repeat the process... We need make it more "fast", one "auto repeat" when failing.

Hi Leo,
Auto repeat of a process chain is always not ad visible as in most of the cases we can see the job got finished in SM37 and even spool got generated but unfortunately it will fail if any of the data package is wrong.In these cases we can skip the process chain and make it continue.
I have written a blog on the same.please go through it.i feel for those scenarios it is good.
How to override a process block in the process chain and make it force complete ?
My personal advice is to go and check the job log before repeating any process as the job may fail for n no of cases.it is a complex challenge of adding all those errors tracked.
Regards,
Kannan

Process chain Error: This AND process is not waiting for event RSPROCESS

Hi All,
I am facing an error in the process chain in PRD.
Error message: This AND process is not waiting for event RSPROCESS.
We had a process chain which had two sub chains which run parallel and below of this we had AND process type and below of the AND process we had 4 more jobs.
Once the two subchains got successfully loaded, the and process should turn to green and further 4 jobs should start.
It is a daily load , it worked fine from past years,but suddenly the AND processtype is getting failed.The thing is in the two subchains if one got completed, the AND process process is not waiting for 2nd subchain to get completed.The AND process is turning to RED (status: cancelled) . I tried to repeat the AND process once after above 2 subchains loaded, but it didnt worked.
And i removed the existing AND process and created a new one and placed it in same place and activated and schedules again.but still it is getting failed with same error.
Thanks in advance,
Sai Chand.S

Hi,
If you did any transports related to that metachain we face similar kind of issues.
not only the AND process , we need to remove all the process before executing the AND process and create it again.
It helps you, you said your in production So you should take the proper approvals and do it.
Regards,
Yerrabelli.

InfoPackage in Process Chain Error

Hi,
I am working on a 3.1 Dev system which was copied from the Production system. The R/3 system was also copied.
......Prod.....Dev
R/3.   LD1 --> LD3
BW.    LD6 --> LD5
The process chain is for Master Data Attributes.
The problem i'm having is that the infopackage runs perfectly when scheduled manualy. But, when it is run in the process chain it says it cannot run because of the following error.
"Source system LD1050 is incorrect; not possible to load data"
I had a similar problem with ODS activation which i resolved by running RSRV but cannot seem to figure out how the infopackage can be corrected.
Any help will be appreciated.
thanks
Sid
Message was edited by: Siddhartha Anand

Hi Anuj:
Looks interesting but I did not do this configuration and was wondering if you could elaborate on what this does.
Conversion of source system names after the trans
OrSrceSystTargSrceSy+
DD6_010   DD6_010   DD6 Client 010
LD1045    LD3196    LD3 Client 196
LD1046    LD3196    LD3 Client 196
LD1050    LD3196    LD3 Client 196
LD5010    LD5010    System LD5 Client 010
LD6010    LD5010    System LD5 Client 010
PD1120DEV PD1120DEV PD1 Client 120
Thanks
Sid

PROCESS CHAIN error "Incorrect start date"

hi sap gurus,
I have parent chain in that a newly created meta chain is creating problem.I am getting error in the process chains since two days i am not able to solve this.Can anybody try to help me.
error: Incorrect start date: 00.00.0000; Start time 00:00:00 RSM 847
After that the process chain is turning red,but when i manually execute the process chain its running properly.
Please help me its urgent.

hi gurus,
Its working fine now.
Solution:
first exchange the variant with the smae and then activate and run.After that it will work in the process chain.
Thanks a lot to every body,especially MOHAN KRISHNA,

Process Chain Error DBIF_RSQL_INVALID_RSQL

Hi,
One of my process chain has an error.
The PChain has this nodes:
- Start
- Data loader (to ODS)
- Data Transfer Process to ODS
- Activate
- Drop Cube Indexes
- Data Transfer Process to Cube
- Generate the Cube Indexes
but... the process mark an error in the "Data loader".
The error is:
Error: DBIF_RSQL_INVALID_RSQL
Excep. CX_SY_OPEN_SQL_DB
What Happened?
Error in ABAP Aplication program
The current ABAP program "CL_RSODSO_SEMANTIC_PACKETIZER=CP" had to be terminated because has come across a statment that unfortunately cannot be excecuted.
What can you do?
Note down which actions and inputs caused the error.
to process the problem further, contact you SAP system administrator.
using the transaction ST22 for ABAP dump analysis, you can look at and manage termination message and you can also keep them for a long time.
Note which actions and input led to the error.
For further help in handling problem, contact your SAP administrator.
You can use the ABAP dump analysis transaction ST22 to view and manage termination messages, in particular for long term reference.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class "CX_SY_OPEN_SQL_DB", was not caught in procedure "FETCH_PACKAGE" "(METHOD)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the exception would occur, the current program is terminated.
The reason for the exeption is:
the SQL statment generated from the SAP open SQL statment violates a restriction imposed by the underlying database system of the ABAP system.
Posible error causes:
- The maximum size of SQL statment was exceeded
- the statment contains too many input variables.
- to input data requires more space than is available.
The same process chain, is running in DEV, and not has errors. Run fine.
I hope. you can help me.
Thanks

Ricardo,
After reading your problem description it is clear that, the issue is in DataLoader process(ETL) and not process chain,
Description and Solution: RSQL Rrror: 13 usually indicates that some aspect of the database is violated.
One of the key reason could be the input data requires more space than is available in the system.
I'll recommend you to check system log in SM21
Also check the developer trace for relevant work process using ST11
Another reason could be dynamic select-statement (select-options table) which is filled (excessive) during runtime. Check with program developer and modify program to get a shorter statement or split the selection condition. Also from tuning standpoint I would recommend to modify following parameter,
dbs/io_buf_size
Let me know if this helps.
-Prakash Patil

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 error after Enpk1(7.01) upgrade - "Termination discovered"

Similar Messages

Maybe you are looking for