Question:
Hi,
we load a cube from 2 infosource using full update . we have enabled Delete exsisting requests with full and initial runs option.
This worked fine till yesterday, when we created aggregates on the cube.
we enabled automatic roll up of the requests for the cube. now after last nights load i have :
2 requests A & B from 21st load
2 requests C & D from 22nd load
and something that i have never seen till now.
2 requests "Reversal from A" & "Reversal from B"
the last 2 requests have QM & Technical status as yellow and it is not available for reporting.
i am lost to what i am supposed to do now. can any one explain whats happening ?
_________________
Change is The only Constant Factor in Life
Answer:
Haven't experienced it myself, this is just a guess : as your request were rolled up in the aggregate, you cannot 'just' delete it from the cube automatically during your subsequent uploads; so perhaps the system is trying to 'simulate' the deletion by reversing the content of the request or something like that. You don't speak about the content of the reports, are they correct ?
As I said, it's only a guess; I would not have tried to answer this post without your pm asking it.
Ch
Answer:
I did not experience the problem myself, but could the cause be, that after you delete the contents of the cube, also the contents of the aggregates are deleted, and you need to performa an initial roll-up into the aggregates which is for some reason different then a normal roll-up (in the process chain, two different process exist for initial and delta roll-up). If this is your problem, you could consider using a process chain, to get your upload running smoothly
Answer:
When you have aggregates on an InfoCube, you cannot delete a request from the InfoCube (as already posted by CHC) without deactivating the aggregates first. You could include this in your Process Chain (if you have one of course).
Since your requests seem to "stay" in yellow... did you check for short dumps? Did you check the system log as well? Usually a request that stays yellow for a while, has some error to it (it will turn red as soon as the time frame as set in customizing has past).
cheers,
El Belgio
Answer:
When you have aggregates on an InfoCube, you cannot delete a request from the InfoCube (as already posted by CHC) without deactivating the aggregates first. You could include this in your Process Chain (if you have one of course).
Since your requests seem to "stay" in yellow... did you check for short dumps? Did you check the system log as well? Usually a request that stays yellow for a while, has some error to it (it will turn red as soon as the time frame as set in customizing has past).
cheers,
El Belgio
El Belgio,
we are on 2.1c so no process chains.
i checked for dumps but we had none. this has occured on 2 consecutive days.
i have had to deactivate the aggregates to keep things running.
regards
TJ
_________________
Change is The only Constant Factor in Life