Cube compression before Change run

Hello,
This might sound foolish, but I need to be sure...
Does anyone know if there's any implication if cube compression runs before attribute change run?
Thank you.

I don't think so either but I wanted to check if anyone experienced any issues arising from that sequence of execution. This cube contains a lot of data and I just want to be sure before proceeding.

Similar Messages

Archiving BI.7.0: Must data in InfoCube be compressed before archiving run?

Hi Expert
I have created a Data Archiving Process (DAP). It is execute by a archiving process variant in a process chain.
Archiving an InfoCube works fine when all requests are compressed.
However, when I have some requests in the InfoCube that isn't archived I get the following error:
07.11.2008 14:47:07 Data area to be archived is not completely compressed yet I RSDA 148
07.11.2008 14:47:07 Exception condition in row 105 of include CL_RSDA_ARCHIVING_REQUEST=====CM015 (program CL_RSDA_ARCHIVING_REQUEST=====CP) I RSDA 140
I cannot find anywhere it is stated that all requests have to be archived and I cannot find any OSS's about this subject as well.
Have you got any experience in this matter?
Thanks in advance and kind regards,
Torben

Hi,
First of all, i want to thank you for your help!
but i have a question about a case:
Loading Date     Loading N°      FISCYEAR     Order N°          Turnover
31/12/2007         1                          2007                     Order 1            100
01/01/2008         2                          2008                     Order 1            -50
02/01/2008         3                          2007                     Order 1             60
The loading date corresponds to the Request Date.
In our case, we have compressed Data wich Request Date is < 2008, and we want to archive data wich FISCYEAR = 2007.
In this case, we will find the chrgt 1 in the E-Table, and chrgt 2 & 3 in the F-Table.
The goal of the 3rd Loading is to recover Data wich correspond to the year 2007 and that has not been recovered by the SAP System .
For exemple, in my case, Data (wich come directly from the stores ) are sent everyday to SAP, but due to a problem, we didn't receive Data.
So, The 3rd Loading will allow us to recover those Data.
How will i do to archive the entire data that correponds to FISCYEAR = 2007, knowing that i do not have all of them in requests wich Loading Date is < 2008.
Thanks for your help.
Salah Lamaamla

How to run change run in process chain when it fails

HI All,
How to run attribute change run in process chain when it fails. Give me the procedure with clear description. Is there is any difference with 3.x versions in running this.
Thanks,
Pratap Reddy

Hi Pratap.
If BI Accelerator is not being implemented by ur company, in that case if change run fails u'll proceed by 'Repeat' process option as usual we do in 3.x.
If BIA is exists, in this scenario u can not repeat as we do in 3.x. U have to drop the indexes on cubes effecting that change run and run the change runs. Once it is finished recreate BIA Indexes on cubes.
Warm Regards,
Ramki

Cube Compression Problem

In the middle of a cube compression that was running in the background, the job short dumped.
I know why the job short dumped. It was due an invalid SQL statement, presumably because I tried to compress too many requests.
Problem is that the requests that I asked to be compressed in the cube are marked as "compressed". How do I "uncheck" those requests that I know are not compressed?

Wardell,
Requests get compressed one by one when you compress requests - hence if you are compressing 10 requests then it starts from request 1. If the job ends halfway then the requests that have been compressed till then stay compressed. It does not mean that the request has an incorrect compression status. If the request was getting compressed / scheduled for compression - you will get a clock icon against the request.
Also to double check - you refresh the screen and go to the collapse tab and see if the release button is not greyed out.
And go back to RSA1 and refresh tree and then go back to the manage tab and see the status.

Why you cannot compress data while attribute change run is active?

why you cannot compress data while attribute change run is active?
Also, are there any prerequisites before running a compression.
Will the aggregates get inactive after running compression?
Regards,
Simmi

Hi Simmi,
I'm not sure what are u looking for ..???? now u are asking whther if activation starts at the same time for 2 ODS,.. there wont be any problem if the activation starts parallelly..
but these activation fails if the change run is running for the common master data. So make sure that when ever change run is running the corresponding master data will gets lock. thats the reason why u can see locks in rollup, compressions or any other parallel change runs....
Hope this helps....
Assign points if this helps.
thanks
Vishnu

ABAP program to add in the process chain before the attribute change run

Hi
I need a ABAP program to add in the process chain before the attribute change run(process) to avoid the locks, can any one send me the program
Regards,
Satish

I am not sure of any standard program .... but you can write your own... should be a small one..
you can check if the table RSDMDENQ has entry for your InfoObject... if yes, then its locked.. if not.. its not locked

Do I need to run "Change run" if I have no aggregates in the cubes

Hello
Do I need to run "Change run" if I have no aggregates in the cubes?
If yes, why?
thanks

Hi there,
As said the change run will activate the modified records from a master data of a characteristic.
If this characteristic is used in any aggregate then the change run will also rearrange the aggregates.
Diogo.

Cubes locked in terminated change runs

Hi guys,
Couple of cubes are locked in terminated change run......... how do i resolve this as there are no locks set form them in sm12 or db01
what is the way to go..........
Thanks,
Your help will be rightly appreciated

Please 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.,etc.
Also you can try Tcode CHANGERUNMONI/program RSDDS_CHANGERUN_MONITOR to view this data.
The Problem is that there might be 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.
This blog will explain how to prevent this from happening.
http://sapbwneelam.blogspot.com/2007/08/how-to-avoid-attribute-change-run.html
Hope this helps.
Award points if useful.

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

Effect of Cube Compression on BIA index's

What effect does cube compression have on a BIA index?
Also does SAP recommend rebuilding indexes on some periodic basis and also can we automate index deletes and rebuild processes for a specific cube using the standard process chain variants or programs?
Thank you

<b>Compression:</b> DB statistics and DB indexes for the InfoCubes are less relevant once you use the BI Accelerator.
In the standard case, you could even completely forgo these processes. But please note the following aspects:
Compression is still necessary for inventory InfoCubes, for InfoCubes with a significant number of cancellation requests (i.e. high compression rate), and for InfoCubes with a high number of partitions in the F-table. Note that compression requires DB statistics and DB indexes (P-index).
DB statistics and DB indexes are not used for reporting on BIA-enabled InfoCubes. However for roll-up and change run, we recommend the P-index (package) on the F-fact table.
Furthermore: up-to-date DB statistics and (some) DB indexes are necessary in the following cases:
a)data mart (for mass data extraction, BIA is not used)
b)real-time InfoProvider (with most-recent queries)
Note also that you need compressed and indexed InfoCubes with up-to-date statistics whenever you switch off the BI accelerator index.
Hope it Helps
Chetan
@CP..

Attribute Change Run taking very Long time.

Hi Experts:
We are daily loading Master data from one common process chain. There are 33 Infoobjects which are getting activated in Attribute Change Run Process. This process is taking almost 3 hours to run daily; due to this it is impacting our other data load process chains.
Many times it happens that there is lock on cubes due to attribute change as attributes are getting aligned to same cube on which the roll up is running.
There are local chains below the attribute change run, which are also important to run.
Please help and suggest the workaround for the same.
Cheers,
Omkar

33 info objects in one ACR(attribute change run) is not a good idea.
Better to split the info objects and use multiple ACR.
During your ACR if transaction data load was on then lock issues always occurs.
Thats why we need to run master data loads first and later transaction data loads.
Which info object change run was troubling, better to note the info objects which are causing and try to put them in separate ACR and trigger it before start of your transaction data loads. so that it won't raise the same issue again.

Attribute Change Run process Locked for 0material..?

While loading Data from PSA(0Material field) to InfoCube,AttributeChangeRun had failed. How can we solve the problem means how we can load data to InfoCube after attribute change run successful.
Edited by: Mr D111 on May 12, 2010 2:41 PM

Hi,
What was the exact issue? As Attribute change run is a different step where as loading of data from PSA to cube is a different step...
So there is no reason of failure for attribute change run in between....
If ACR failed before to the loading of data to cube, then re-run the ACR from RSA1>Tools->aplly/monitor change run-->in the info objects list find the infoobject and execute....
Unless you clear this ACR failure issue you can't load the data to the cube as it may be in locked mode....
After this is successful, then u can load the data from PSA to cube.
rgds,

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

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

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

Cube compression before Change run

Similar Messages

Maybe you are looking for