Activation of M records failure in DSO in process chain during weekend

Hi Experts,
We have got same issue again but this time after a month's time.
Once again it happened during weekend and this is error message which is same as it was in the past : -
Error occurred while deciding partition number
PSA update failed
Process 000003 returned with errors
Background process BCTL_DBA2WH3T6167YSRG2JOPWJAHC terminated due to missing confirmation
Background process BCTL_DBA2WH3T6167YSRG2JOPWJAHC terminated due to missing confirmation
Background process BCTL_DBA2WH3T6167YSRG2JOPWJAHC terminated due to missing confirmation
Background process BCTL_DBA2WH3T6167YSRG2JOPWJAHC terminated due to missing confirmation
Background process BCTL_DBA2WH3T6167YSRG2JOPWJAHC terminated due to missing confirmation
Data pkgs 000001; Added records 1-; Changed records 0; Deleted records 0
Log for activation request ODSR_DBA2WH3T615GA6FOR093U3W7K data package 000001...000001
Errors occured when carrying out activation
Analyze errors and activate again, if necessary
Activation of M records from DataStore object ZDSO** terminated
I have done all the things suggested by the experts but still unable to understand this strange behaviour.
Please suggest your valuable thoughts regarding how to stop this from happening.
Regards
Sunny

Hi,
For the issue,
Background process BCTL_DBA2WH3T6167YSRG2JOPWJAHC terminated due to missing confirmation
You should make some adjustments to the Data Store object parameters, then you should be able to activate the request.
Please make the following adjustments in transaction RSODSO_SETTINGS (you can adjust this for each DataStore object):
1) Maximum package size (for activation).
   This you should reduce to 10000. Then the package processing would
   be less time consuming.
2) Maximum wait time for process (for activation)
   This could be increased to e.g. 600
See attached Note 1118205 for further information.
Regards,
Mani

Similar Messages

Loading from flat file to dso using process chains

hi,
i am using BI7.0
i am new to process chains
can anyone explain how to load data from flat file to dso using process chains(i have created all the objects created) preffered if explained with an example

You can find a lot info if you can searh SDN.
Metachain
Steps for Metachain :
1. Start ( In this variant set ur schedule times for this metachain )
2.Local Process Chain 1 ( Say its a master data process chain - Get into the start variant of this chain ( Sub chain - like any other chain ) and check the second radio button " Start using metachain or API " )
3.Local Process Chain 2 ( Say its a transaction data process chain do the same as in step 2 )
Steps for Process Chains in BI 7.0 for a Cube.
1. Start
2. Execute Infopackage
3. Delete Indexes for Cube
4.Execute DTP
5. Create Indexes for Cube
For DSO
1. Start
2. Execute Infopackage
3. Execute DTP
5. Activate DSO
For an IO
1. Start
2.Execute infopackage
3.Execute DTP
4.Attribute Change Run
Data to Cube thru a DSO
1. Start
2. Execute Infopackage ( loads till psa )
3.Execute DTP ( to load DSO frm PSA )
4.Activate DSO
5.Delete Indexes for Cube
6.Execute DTP ( to load Cube frm DSO )
7.Create Indexes for Cube
3.X
Master loading ( Attr, Text, Hierarchies )
Steps :
1.Start
2. Execute Infopackage ( say if you are loading 2 IO's just have them all parallel )
3.You might want to load in seq - Attributes - Texts - Hierarchies
4.And ( Connecting all Infopackages )
5.Attribute Change Run ( add all relevant IO's ).
Start
Infopackge1A(Attr)|Infopackge2A(Attr)
Infopackge1B(Txts)|Infopackge2B(Txts)
/_____________________|
Infopackge1C(Txts)______|
\_____________________|
___________________|
__\___________________|
___\__________________|
______ And Processer_ ( Connect Infopackge1C & Infopackge2B )
__________|__________
Attribute Change Run ( Add Infobject 1 & Infoobject 2 to this variant )
1. Start
2. Delete Indexes for Cube
3. Execute Infopackage
4.Create Indexes for Cube
For DSO
1. Start
2. Execute Infopackage
3. Activate DSO
For an IO
1.Start
2.Execute infopackage
3.Attribute Change Run
Data to Cube thru a DSO
1. Start
2. Execute Infopackage
3.Activate DSO
4.Delete Indexes for Cube
5.Execute Infopackage
6.Create Indexes for Cube
Some Links
http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/c08b3baaa59649e10000000a11402f/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/8da0cd90-0201-0010-2d9a-abab69f10045
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/19683495-0501-0010-4381-b31db6ece1e9
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/36693695-0501-0010-698a-a015c6aac9e1
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9936e790-0201-0010-f185-89d0377639db
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3507aa90-0201-0010-6891-d7df8c4722f7
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/263de690-0201-0010-bc9f-b65b3e7ba11c

Regarding activation of DSO in Process Chain

Hi All,
I am getting error in process Chain actvation of DSO
DataSource does not exist in version A in source system
Activation of M records from DataStore object ZPI_O53 terminated
Solution please

Hello Sunitha,
The DataSource has been changed or saved and it doesn't match with the BW datasource timestamp. So you have to replicate the datasource to BI and activate the transformation.
Thanks
Chandran

DSO & Associated Process Chains

Hello Expetrs,
I need to anyze some DSO's for any data load performance issues and associated Process chains. Is there any tables or direct way to figured out which process chains are associated with perticular DSO/InfoCube ? One more questions, is there any way to check data load performance issues for DSO/InfoCube ? Please help on this.
Many Thanks in Advance,
S. Patel

Hi Sunil,
I can suggest one alternative method for you.
goto SE16 --> give table name RSPCCHAIN
generally when we load DSO we will do activation.
in this table we have field called "type" --> in this field give ODSACTIVAT and execute.
you will get process chain which are loading to particular DSO.
If you want to find out for CUBEs, then give LOADING instead of ODSACTIVAT, but here you will all IP's and DTP which are included in process chains.
Regards,
Venkatesh

Unable to delete data target contents of Write-Optimized DSO in Process Chain

Hi Experts,
We are using SAP Net Weaver BW 7.01 version and we need to delete the entire data target contents of Write-Optimized DSO in the process chain before the next data load.
I included this step in process chain but still it is failing with errore message"Message not found (in main memory), Drop Cube Failed In Data Target"
This process type is working during BW 7.0 version but not in BW 7.01 version.
However i found that we can use the program RSSM_DELETE_WO_DSO_REQUESTS to delete old requests in the Write-Optimized DSO for BW 7.01 SP07 as per SAP Note 1437407 but still it's not working even after implementing this program as the Prerequisite to delete the request is the data mart status should be updated where it is not happening for the program.
We had an process type option to 'delete the requests from Write-Optimized DSO' directly in BW 7.3 but still not available in 7.01 version.
Could you please suggest me on how to resolve this issue in BW 7.01?
Many thanks for your help in advance.
Regards,
Madhu

Create ABAP program as attached code.
Then you can use that ABAP program in process chains through ABAP variant
ABAP varaint should have following properties
Select call mode as Synchronous; call from Local; and Program
Give your ABAP program name in "program name" and create one program variant for each write optimized DSO.
Please refer how to use ABAP program in process chains for further details.
Hope this helps

DTP failure which was in process chain after transport

Hi,
I created a DTP in Development Server and it get transported to QA successfully.
I also created a Prcocess Chain that execute that DTP. When I tried to transport this Process Chain to QA, transport was sucess but when i check in QA process chain was not in active mode. its showing the error that DTP is not in active A version.
Error:Process variant DTP_LOAD DTP_4AEIYC0UV528F7W1JL587E7HR does not exist in version A
I checked the DTP in QA and I noticed that the DTP has been converted to a different technical name which is not the same as the one I transported from Development.
Example: DTP DTP_LOAD DTP_4AEIYC0UV528F7W1JL587E7HR in Dev is converted to DTP_4AN4TVDRYNSMT95UGI48JVC6J in QA.
Please advise how I can transport the Process Chain that call this DTP from dev to QA

Hi Sri,
You need to collect your DTP along with the Process chain in the same request. When you migrate DTPs from DEV to QA , a new DTP ID are generated in QA system and your DTP in the Process chain points to DEV's DTP and that is why you get this error. You can also find more information when you turn on the " Detail View On" from the menu. This will display technical name of all the objects in your process chain.
so recollect your DTPs and the process chains objects in the same transport request and migrated to QA ,this will Fix you issue.
Hope it helps,
Cheers,
Balaji

How to stop th activation process of DSO in process chain

Hi,
we are loading the DSO by two load processand followed by activation process, but here one of the load process failed and i need to correct it manually, but when i make the failed request red in dso the next activation process is started. can i stop this activation process?, because i had to run this process after i manually correct the load request.
thanks

Hi,
You can stop or kill this job, by identifying the work process number and app. server from job log of activation job. by right clicking on activation process -> display message-> you can get this details. once you know about the server and work process, then go to SM51 -> select the app server and then select the work process and cancel it from menu options.
When you are loading 2 requests in parllel to a data target, it is always better to have an AND process before activating the Data in DSO. It will aviod this kind of errors and killing other jobs.

Unique Data Record Settings in DSO

Hello Experts,
I have checked Unique Data Record Settings in DSO.
Error Message while Activation of DSO through Process Chains.
Records already available in Activation Table
Duplicate Records
Activation error occurs & it specifies the Req No/Record No.
But in reality there are no duplicate records available in the specified Record No.
I faced this issue several times, why does this happen.
I guess this Unique Data Records Setting doesnt work.
Regards,
KV

Hi,
I am not sure why unique data setting is set, This is generally used when data with the same key will not come again or you are flushing the DSO and loading everyday. In normal cases it may happen for e.g there can be two records with the same sales document number as user might change the sales document twice.
So i think in u r case u dont need the check mark. Let me know if u have doubt.
Regards,
Viren

Incorrect data after activating the request through Process chain.

Dear SDN chaps.
Today morning. I encountered a strange issue in DSO..
I have DSO which is updating from the AL11(application server) flat file.
While i am loading it to PSA there were no issues and after loading it to the DSO there is no issue and its passing through the routine and the data is populating properly in NEW data Table .But after successful activation of the request through process i am getting the wrong records in active data table.
Then i deleted the request and reran it manually i mean triggered the DTP and ran the manual activation surprisingly accurate records are coming through manual process..
I am just wondering why it is not working through process chain and why it is showing incorrect records through process chain execution and how it is showing accurate records through manual uploading process..'
Could some one please help to come out from this..By the way mine is SAP BI 7 SP20 &SP05 for BW 7.01
Thanks
K M R

Hi Pra
Thanks for your response..
We are doing PSA deletion and then we are uploading the data to PSA as well as DSO.
Now the issue is not in the part of loading we are facing the issue in Actiation of request if i am executing the activation through process chain it is sucess but the values are incorrect. If i am doing the manual activation it sucess with correct data.
Even i tried with a new chain but still i am facing the issue.
Surprise thing is in new data table the data is perfect in both the ways like manual upate and Process chain update only during activation i am getting incorrect record in the active data table..
Appreciate your help on this....
Thanks
K M R
Edited by: K M R on Jul 9, 2010 11:09 AM

How to identify whether that particular process chain is active or not?

Hi all,
How to identify whether that particular process chain is active or not ?
thanxs
haritha

If see the process chain then it will not be greyed out if it is active. Or else check in these tables.
RSPCCHAIN
RSPCCHAINT
to check the logs
RSPCLOGS
RSPCPROCESSLOG
Give the chain name and check in the object version.
Khaja

Error during activation of DSO - Activation of M records from DataStore obj

Hi All,
Below is the error i am getting while activating the DSO, Even though similar post on this topic, solution not mentioned, any solution greatly appreciable.
When -
During Activation of DSO
State of DSO -
Request become "RED", It is available for reporting, some records in Active table, some in new table and some in new table.
Job Log -
Error when inserting the data record for data package
Process 000105 returned with errors
Error when inserting the data record for data package
Process 000106 returned with errors
Process 000107 returned with errors
Data pkgs 000001; Added records 1-; Changed records 0; Deleted records 0
Log for activation request ODSR_4GXKRYHMY97R9U62M6U52XXXY data package 000001...000001
Errors occured when carrying out activation
Analyze errors and activate again, if necessary
Activation of M records from DataStore object Z_DSPO terminated
Report RSODSACT1 ended with errors
Job cancelled after system exception ERROR_MESSAGE
Detail log -
Error when inserting the data record for data package 106
Message no. RSODSO_PROCESSING002
Diagnosis
Failed to store data records persistently. Possible causes are:
You tried to save a record that is already stored in the database.
This error only occurs with DataStore objects with option "Unique Data Records".
A unique index was created for the table of active data.
You can check this in the Data Warehousing Workbench by choosing "Display" for the DataStore object and opening the "Indexes" folder.
There is a technical problem on the database.
Thanks,

HI PT,
I am also getting the same error like i have loaded the data into DSO and tried to activate the init request but it has become red and checked in log found that there are some SID Generation errors so please give me the step by step solution.
SID Generation
Data Package 000056
Data Package 000064.
Thanks in advance,
Jay

Data Extraction failure from DSO to Cube

Hello Experts,
The Data load to Cube( zfiar_c03) from DSO (zfiar_03) using a full
update is failing throwing the error message"Incomplete update due to
errors in single records ".We had deleted the failed request from
infocube and loaded the the same req from psa by correcting or removing
the # values but it failed again resulting in the same error.
When we checked the previous successful requests which got loaded to
cube from dso it also contains the # values , but the loading was
successful.
our BW reporting is seriously impacted due to the failure coz our
collection,recievables..etc all business critical report is based on
this cube.
Request you all to help..
thanks,
Sapta

Hi Sapta Jyothi,
I am not sure what the actual problem is. But, from my prior experience, I fell this is related to the Process chain configuration provided you are using process chains.
If you are using a process chain , please check if there is any other failed step in the Process chain. If that is the case, even if the failure due to invalid entries is fixed the QM status of the load to the cube will not turn Green till the process chain status turns green or yellow. You can check from the details tab of the info-package load run and see if the process chain log step is red. If this is the case, then you will have to take action to see that other steps are completed succesfully. And also the Process chain in this case needs to be modelled in a way, such that, when a load to a cube fails the successive steps like creation of cube indeces should not be triggered.
Thanks ,
Nithin.

Process Chain - Follow on dependencies to DSO Activation

Hi, I have a Data Load Process where the start routine is dependent on DSO data that was just previously activated. For some reason it looks like the the time before the load and the time after the DSO activation are close by just seconds.
The Data Load Routine will drop records if the activated DSO data is not available and this seems like what I am witnessing. I thought there was a way to configure the chain or job to wait until the previous is completely done. or did that go away with 7.0...
Is there a way to make sure the loading process doesn't start until the previous DSO activation is completed and the data is available?
Thanks!

Hi,
Interuppt concept :
If a process chain is only processed either in part or in its entirity if more than one start condition is filled, you use this process type to specify the additional conditions.
The chain is started when the condition of the start process is filled. However, the interrupt process will interupt the processing of the chain (as long as its status is "active") up until the point at which the condition of the interrupt process is filled. Should the start process condition be filled again before the interupt process condition is filled, the chain will start again and will only run up until the point of interruption. As soon as the interrupt process condition is filled, the system continues the last run of the chain only. The earlier runs remain unchanged.
The interrupt process schedules an additional background job that starts based on the relevant condition. Therefore the interrupt process is not really active during the interrupt phase; it does not use any resources during this time.
If the interrupt processes are filled before the start process condition, the chain starts as soon as the start condition is filled; the interrupt process no longer interupts the chain because its condition has already been filled. If the interrupt process condition is is filled again before the start condition of the chain is filled, this does not influence the chain. It is not stopped by the interrupt process..
so basically your interrupt will wait for an event like ex:..YABAP_YGTRFCEVENTRAISE_0035 ... so you can raise that event eother by some job or some program..bUt for you i think adding the waiting timw will be better option ..
hope i cleared you ..
Regards,
Shikha

Error while activating data from new table of DSO to active table

HI,
while activating data from new table of DSO to active table i am getting
error message as "Error occurred while deciding partition number".
Plz any idea hoe to resolve this one.
thanks & regards
KPS MOORTHY

Hi
You are trying to update/upload the Records which are already been there in the DSO Active Data Table which has the partition.
Try to see the Record Nos already been activated and update/upload with selective, if possible.
You can trace the changes at Change log table for the same.
Hope it helps
Edited by: Aduri on Jan 21, 2009 10:38 AM

Process Chain Error while activating DSO

Hello.
1st, let me say that I'm pretty new to BI so I apologize for the stupid question :-S
I have a process chain (Warehouse Mangement) that failed this morning at the DSO data activation step. It's simply because some entries have lowercase value in a field that should not. I know how easy this is to fix in the transformation but my problem is more on how to fix the actual fail of the process chain. Can I edit the "non-activated" data in the DSO (only 2-3 records that I need to put in uppercase) and "repair" my process chain or should I proceed another way?
Thanks for your help.

Hi John.
If guess your Process Chain process ended in "Red color". Once you fix the error you can try to make "right-click" on the process with error and select "Repair". If this operation is "supported" by the activation process you won't have error.
But I really believe that you'll have to erase the request and launch the complete process (o set of related processes) once again. It's possible that the data you want its already in the NEW-DATA table of your ODS.
This tables is the following. /BIC/A<your ods tech-name>40
Hope it helps
gdmon.-

Activation of M records failure in DSO in process chain during weekend

Similar Messages

Maybe you are looking for