Attribute Change Run aborted with an error :Not all data indexed for index

Hi,
I have an issue where the master data Attribute Change Run aborted with an error pointing to the BWA:
Attribute Change Run aborted with an error :Not all data indexed for index
we tried to load only 0 data into it,the error still occured.

Detail message is following:
not all data was indexed for index 'GBP_BIC:XYCH_098('0' for '114')
creation of The BIA INDEX for infocube 'YBC_SD015' terminated while filling

Similar Messages

Error "Not all data could be changed in LC" when running DP macro

We are getting the error, "Not all data could be changed in LC" when running DP macros and we are not sure why. It seems to only happen when we are executing it via a Process Chain but not using the DP background processing scheduling. Does anyone know why this is happening?

Hi Stacy,
I hope you are seeing this in message spool. This message comes up for various reasons. We used to see a message saying "No data saved".
Some of the reasons could be " the new value (lets say 3 ) after the macro execution is same as after execution (3)".
See if some of the values are fixed and could not be changed.
I would take a selection id with just few values and execute the job for that selection id and compare the pre and after results. That should answer all your questions.

Attribute Change Run terminating - repeated several times - not locked

I had a failure in my master data chain tonight. The attribute change run that ran yesterday ran for 11k seconds and was cancelled (it says manually). When the chain ran tonight, the process failed again. I checked the log and it says "UNCAUGHT_EXCEPTION" and it created a short dump. I tried repeating to see if it did anything and it gave me the same message.
I went into the change run monitor and reset the status and manually tried to run the change run again. Same result "UNCAUGHT_EXCEPTION".
I then checked table RSDDAGGRMODSTATE and there was no blank CNSID entries, but there was a blank "completed flag" entry. I don't have change access to the table in prod so I cannot manually change it to X (meaning closed). I reset the status again in the chagne run monitor and the record with the blank "completed flag" disappeared. I repeated the change run and it failed again and a new record with the "completed flag" being blank appeared in the RSDDAGGRMODSTATE table.
I checked SM12 and there are no locks there. I'm on 7.0 so I can't manually right click on 0CUSTOMER and activate the master data either.
As a last resort I did run the function module RSDDS_AGGR_MOD_CLOSE but that short dumped too.
Any ideas? Please? This will fail my other chains that have 0CUSTOMER in the aggregates. Thanks.

HI,
Firstly try this FM RSDDS_AGGREGATES_MAINTAIN
if not possible
Try doing it manually
Uncaught exception may come due to many reasons
IN RSA1 go to tools and select attribute change run
Check the blog it shows you how to manually do attribute change run step by Step (for BI7.0 also)
/people/debjani.das/blog/2009/03/30/attribute-change-run-acr
Regards,
MADhu.
Edited by: MadhuMarupudi on Aug 21, 2009 5:49 AM

Error with Attribute Change Run - Urjent

Hi All,
In our scenario we will load master data from APO&ECC to BW.When we are doing attribute change run we are geetting short dump and jobs are cancelling every time .
Please fidn the details below.
Short Dump : ORA-14400 with ABAP/4 DBIF_RSQL_SQL_ERROR..
When I have searched in the forum I got some information saying that we need to drop the index and recreate the index.But we have around 40 cubes.Then how I am going to deside on which I need to the relavent settings.
Please provide me the proper answer.We are facing this problem from past last two days.
Regards
Ramakanth.

Hi,
You can try going to the monitor for Attribute change run from RSA1 >> tools >> apply change run or from Transaction RSATTR which will schedule/display attribute change run. Here you can have an option called change run monitor (Monitor icon). this wil show the status of change run including which all info objects are affected, and if its hitting the aggregates of any cubes. There are scenarios where the attribute change run failed with message that it was hitting/affecting aggregates of some infocubes. In case we had to switch off aggregates and trigger the change run again and then swtich on the aggregates after the change run is over.
And sometimes ACR goes on running for a long time in such case we need to check which Aggregate the ACR is currently changing and need to deactivate that aggregate.
But before deactivating an aggregate you need to check the data present in that and the usage of the aggregate.
Please use the table RSDDCHNGPROT and find out the infocube affected by this change run and de-activate "ALL" the aggregates
of the infocube listed under CNSID=0. Then start the change-run.
You can rebuild/refill the aggregates once the change-run is finished.This is necessary because there are inconsistencies in the aggregates
Most of the times we have problem with the Attribute Change Run(ACR) running because ACR and the Roll Up's for Aggregates cannot run in parallel.
Also you can try Tcode CHANGERUNMONI/program RSDDS_CHANGERUN_MONITOR to view this data.
176606 - Apply Hierarchy/Attribute change ... long runtime
175309 - Hierarchy/attribute - change run improved
oss note 322644
Hope this helps.
Thanks,
JituK

Master data attribute change run error

hi all,
plz tell me the procedure to overcome the masterdata attribute change run error.plz explain me with steps clearly
thanks in advance,
jack

Hi Jack,
The process of Attribute change run is just the activation of the Master data same as DSO's.
In RSA1>tools>Apply Hierarchy/Attribute change run(CRTL+F9). You can check your object for which the attribute change run has to be applied through the infoobject list.
Then execute. now the attribute change run is completed.
Please ensure the infoobject is activated.
Provide us the error message to give you more details.
Regards,
Ravi

Attribute change run Failing in Process Chain

Hi guys,
Every day my process chains is failing due to Attribute change run and I am maually running attribute change run.
And one more thing when the attr. change run is triggered automatically,then it is generating 2 change counters in RSATTR tcode instead of 1.
One is successfully completes and one is still in schedule.After 2days days it is showing like completed change count id.
Please help me.
Regards,
Tiragati.

Hi,
As you said Attribute change run step is failing every day.
can you post the error message. is it failing because of Lock issue or some other issue.
Mostly attribute change runs fails with lock issues. if its the same problem in your case. make sure that no master data objects runs at the time attribute change run runs.
Try to put some delay in the process of the Attribute change run so that it will not get failed.
Check if its the same ACR scheduled or diff objects?
Regards
KP

Attribute Change run canceled

Hi
I have loaded master data for an Infoobject and executed Attribute change run by saving that object and execute. I got the message like Attribute change run is canceled((protocol/shortdump) now i can not able to run any attribute change runs since save button is not available in the window and also unable to load data to the same infoobject getting errored and giving messsage locked by attribute change run i have checked in sm12 no locks exist on this object
Thanks
Vani

Hi,
You can try going to the monitor for Attribute change run from RSA1 >> tools >> apply change run or from Transaction RSATTR which will schedule/display attribute change run. Here you can have an option called change run monitor (Monitor icon). this wil show the status of change run including which all info objects are affected, and if its hitting the aggregates of any cubes. There are scenarios where the attribute change run failed with message that it was hitting/affecting aggregates of some infocubes. In case we had to switch off aggregates and trigger the change run again and then swtich on the aggregates after the change run is over. this may not be the exact issue you are facing.
Most of the times we have problem with the Attribute Change Run(ACR) running because ACR and the Roll Up's for Aggregates cannot run in parallel.
The Problem may be that there is another change run triggered parallely to yours.In any SAP System only One attribute change run can run at one point of time. i. e If one attribute change run is running in system from any process chain or for any project and 2nd one fails, if start at same time due to locking problem. Due to this entire data load fails.
Just check it there are any other change run active in SM37. Repeat your change run once the other change run is over.
And sometimes ACR goes on running for a long time in such case we need to check which Aggregate the ACR is currently changing and may need to deactivate that aggregate.
But before deactivating an aggregate you need to check the data present in that and the usage of the aggregate.
Also you can try Tcode CHANGERUNMONI/program RSDDS_CHANGERUN_MONITOR to view this data.
thanks,
JituK

Attribute change run taking more time

Hi Gurus
I am loading master data 0mat_plant everyday
nearly 2 to 3 lakhs record .The extracrion and loading is taking 30 min but attribute change run is taking 3 hrs .Is there any way to reduce attribute change run time.

Hi,
You can try going to the monitor for Attribute change run from RSA1 >> tools >> apply change run or from Transaction RSATTR which will schedule/display attribute change run. Here you can have an option called change run monitor (Monitor icon). this wil show the status of change run including which all info objects are affected, and if its hitting the aggregates of any cubes.
There are scenarios where the attribute change run failed with message that it was hitting/affecting aggregates of some infocubes. In case we had to switch off aggregates and trigger the change run again and then swtich on the aggregates after the change run is over. this may not be the exact issue you are facing.
And sometimes ACR goes on running for a long time in such case we need to check which Aggregate the ACR is currently changing and need to deactivate that aggregate.
But before deactivating an aggregate you need to check the data present in that and the usage of the aggregate.
Also you can try Tcode CHANGERUNMONI/program RSDDS_CHANGERUN_MONITOR to view this data.
Note 903886 - Hierarchy and attribute change run
thanks,
JituK

Regarding Attribute Change Run failure.

Dear All,
We have a process chain which contains many meta chains.
Now in each chain i mean meta chain there are attribute change runs
We have desegregated the attribute change run. is tere any method to place a check for attribute change run locks because at the last i have another attribute change run which is failing every day because of the attribute change run is still happenign in some chain.
how do i implement it?
Thanks in advance
Janardhan Kumar.

Hi Janardhan,
In master data process chain where you have added process of attribute change, just insert a program before this process:
The program is: RSDDS_CHANGERUN_MONITOR
This program will check for any another attr change run running at that time and if there's any other attr change run runnning locking the object which your next attr change run requires then this program will not allow your attr change run to run.
Once all the locks all cleared for attr change run it will trigger the next node.
This program has a do loop which keeps on checking until unless locks are cleared.
Regards,
Vij

Attribute Change Run in Process Chain failed with SQL 942 error

Hi,
Attribute change run in th eprocess chain failed with the message " SQL Error 942" and ran succesfully after repeating the step.Searched in Forums for similar error but the solutions were not apt.
Any pointers would be of great help!!
Thanks in advance,
Bhagyarekha.

Hi Bhagyarekha,
The reason behind that error could be:
An attempt is made to activate a characteristic whose compounding was replaced and whose navigation attributes were simultaneously deleted. The replacement of the compounding temporarily deletes the M view of the characteristic during internal activation. The process of deleting navigation attributes involves converting the attribute SID tables. However, the M-view of the characteristic, which has just been deleted, is needed for this conversion.
Check this SAP Note:
Note 684405 - Replacing the compounding and deleting navigation attr.
Hope it helps.
Veerendra.

Error in process chain with attribute change runs

We have one warning is coming in one process chain :A type "Attribute Change Run" process cannot precede process "Execute InfoPackage"
We checked the Process View , we found that there are number of attribute change run after each scheduling of Info package with different datasource but for same data target.
How to remove this warning .
Some onsite person has added this extra Attribute Change Run recently.

Hi Surendra,
If it is the same Info-object that is getting loaded through different Info-packages then have only 1 "Attribute Change Run" process at the end. You can ignore the warning.
Bye
Dinesh

Problem with Customer master Attribute change run

Hello Experts
Master data load process chain for 0Customer failed in system at attribute change run step.
Because of that failed instance when ever we try to reload data get error message
"Attributes of characteristic 0CUSTOMER are locked by terminated change run 468502640"
"Lock NOT set for: Loading master data attributes"
It seems that last attribute change run step had locked master data object and lock is not yet released.
Kindly advice resoluiton to this problem.
Thanks in advance
Regards
Sudeep

Failed due to lock issue. check in SM12 you can find lock with respect to your change run 468502640.
Looks like master data step is running.
Wait till the masterdata for attributes of 0CUSTOMER completes and them repeat the attribute change run step.
To repat the attribute change run
Rsa1 --> Menu Tools -->Apply Hierarchy/change run or use transaction RSATTR
Click on monitor and Start Terminated Changes Runs(monitoring of Change runs)
Here you can check the failed Attribute change run object in red status.
after completion fo the master data and check the locks and click on execute button over there.

Process chain error - Attribute change run

Hi,
I am creating a Process chain to load 4-5 master data with its text.
I get a error while executing :
it says : Attribut change run need to be set up.
what should i do
1 :where should i set it up and how ??
2 :why is that needed ??
I included it in the Process chain and still it says that i need to set it up in the administrative workbench .
Please help me understand .
Thanks,
GG

Hi , when i execute a Process chain it stops at the A Master data load package and i get that red.
if i double click it ,
It says that
Attributes are not yet maintained.
If i see the details,it says
Diagnosis
     The attributes have either not yet been created or activated.
     The data cannot be taken from the source system without maintained
     attributes. Therefore, this data request is not possible.
Procedure
     Maintain the attributes for this master data-InfoSource in the
     Administrator Workbench and then activate them.

ERROR while running attribute change run.

hi sap xperts,
I got an error while running the attribute change run in a process chain.
At first i got an error "The action is locked by a change run"
SO I DID THE FOLLOWING STEPS.
1.RUN ATTRIB CHANGE RUN MANUALLY IT RUN SUCCESSFULLY,but the process chain is still red.
Q1.Is there any way to link the manually run attrib chnage to process chain so that the process chain becomes Green?
2.SM12 - realease the locks and right click the pc and repeat.It didn't work
Q1.While removing the locks what should we remove,bcoz i removed all the locks?
3.I again removed the lock and repeat the process but still i didn't work.Now its chowing "SQL ERROR OCCURED WHILE ACCESSING"
So the Process chain got stuck,Can any body help me to run the attrib chnage run.
If possible can anybody send the Process chain monitoring documents to my email id:
<email ID removed>
please.thanks in advance,i know how to say thanks in sdn.

At any point in time only one attribute change run can run in the system. The other ACR's will fail due to locks. In your case, to set the process chain to green, try the following steps.
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.
The above steps will help you continue with the rest of the process chain (thus avoiding manual runs) but the failed step might still remain red. Hope this helps.

Error: [NQSError:13037] cannot connect to BI security service,Please make sure this is running properly (with SSL or not) in EM

Hi,
Im unable to open the RPD online getting following error.
Note: Im not done any changes. Its works good till yesterday EOD.
Error:
[NQSError:13037] cannot connect to BI security service,Please make sure this is running properly (with SSL or not) in EM.
[NQSError:37001] could not connect to the oracle BI server instance..
Kindly help me to fix this issue.

Hi,
Could you access the answer side.
Could you see the reports.
Do one thing, take a back up of NQS config file from <Oracle Location>\instance\instance1\config\obiserver folder\nqsconfig.ini file.
Copy nqs config file if you have already have a back up.
Restart the services and try once.
http://mkashu.blogspot.com
Regards,
VG

Attribute Change Run aborted with an error :Not all data indexed for index

Similar Messages

Maybe you are looking for