Delta request compression twice

hi sdn,
can we double compress the same request i already compressed the requst but i'm not able to find out tik mark against that reqst but job is completed successfully can we compress it again
regards
rubane

All your job log says that compression finished. And you also checked that data has been successfully moved out of F table to E table.
I am assuming that you have refreshed your session properly.
Could you also try out the following things.
Go to Manage -> Environment -> Complete Check of request ID -> Click on 'Complete availability check of all request IDs in the info-cube'.
Go to transaction RSRV -> Perform few checks for Info-Cube
Let me know the findings.
Soumya

Similar Messages

DELETE A DELTA REQUEST THAT WAS COMPRESSED !!

Dear Experts,
I've some inconsistent data that i'm trying to address.
So, I've delted a few requests out of ODS_1 >> which sends delta's to CUBE_1.
After that I went to manage for CUBE_1 and deleted couple of those common requests from CUBE_1.
Except one request XXXXXX for 11/1/05. When i'm trying to delte this request it says "This request has been aggregated, compressed or Scheduled".
It said the same thing for the few of the previous req's that i deleted. But after few minutes, it allowed me to delete them successfully.
This request is adamantly not going any further. So, I went ahead to the RSMO and changed the status from green to red on the STATUS tab. But it's still not letting me delete it.
I'm concerned that about two things:
1. how do i delete this delta request XXXXXX.
2. If resend the data from datastage to ODS_1 from 11/1 to date, it'll then send delta's to CUBE_1.
But the CUBE_1 already has this request XXXXXX for 11/1/05, it would create duplicate records. What would i do at that point.
Please guide me thru this.
Thank you,
Ti
Message was edited by: TI

You need to check to see if the Request you are trying to delete has been compressed in the base cube. Once a Request is compressed in the base cube, you can not delete it.
As Dinesh, mentions, the cause could also be that you have an agrregate that is set to automatically compress after the rollup, and you can not delete Requests from an aggregate that has been compressed either. Now if the Request has NOT been compressed in the base cube, and the problem is just due to the aggregate, then you can deactivate the aggregate, whihc should allow you to then delete the Request from the base cube.
If the request has been compressed in the base cube, I think you really have only a couple of options -
Reload the cube - might be the easiest if the cube is not to big.
Selective Deletion might work if you can identify criteria that would only point to the data that had been loaded in that Request. Possible, but not likely - depends on the cube design and data.
If you still have the data in the PSA you use that to create a flat file that you would reverse all the key figure signs and then load that to the cube from a flat file data source you define to offset the data from the Request that you can not backout. Another variation would be to try to generate a similar reversing flat file from the source ODS. The PSA is probably a better approach if you have the data still there.
So ...
The first thing is to identify why you can not delete th Request - due to is compression in the base cube or compression in an aggregate.
This is why you shouldn't compress Requests in the base cube until you have verfied the data.

Issue with Delta Request

Hi Friends,
I have an issue with loading.
1. From source 2lis_13_VDITM, data loads to 2 targets.
ZIC_SEG, 0SD_C03.and from 0sd_C03 it again loads to ZSD_C03W and ZSD_C03M through DTP.
I have done a repair full load on 08.08.2011 to PSA and loaded this request manually to cube ZIC_seg.
I forgoted to delete this request in PSA as i dont want to load this to other targets.
Before i notice ,already delta requests got loaded and has pulled my repair full request also to other targets.
As i have not done any selective deltions on other cubes there may be double entries.
I am planning to do the below steps inorder to rectify the issue.
1. Do a selective deletion of the delta request in all 3 targets which got loaded on 8th along with repair full.
2. Delete the repair full request from PSA.
So now delta request which got loaded after repair full request, is left in PSA.
My question is if my PC runs today will this delta request in PSA also pulls again to cube through DTP?
Kindly share any other ideas please urgent...
Regards,
Banu

Hi Banu,
If the data in the CUBE's is not compressed, then follow the below steps
1)Delete the latest request in CUBE ZIC_SEG
2)Delete the latest request from cubes ZSD_C03W and ZSD_C03M and then from 0SD_C03.
3)load the delta request manually using DTP from your cubes(in DTP you can load by giving request number). to cubes ZIC_SEG and 0SD_C03.
3)now run the delta DTP to load the delta request from 0SD_C03 to ZSD_C03W and ZSD_C03M.
Next when your PC runs it will load only that particular day delta request.
It will work
Regards,
Venkatesh

0IC_C03 Request Compression Status

Hi Friends,
We have loaded data into the Inventory InfoCube 0IC_C03. The Deltas are running.
I would like to know that how the 2LIS_03_BF is compressed for certain Request number. Beacuse while validating the data in for the cube inventory cube .........we are getting mismatched values. When i go and see in the InfoCube requests there is Repeat Delta for the 2LIS_03_BF. I want to know that how that Request compressed in the cube whether it is copressed with Marker Update or No Marker Update.
Thanks&Regards
Anand

Hi,
You can check this at the compression log as below
goto ---> Info Cube MANAGE --> COLLAPSE --> LOG ---> select the date of the request and click on ->APPLICATION LOG.
You will find APPLICATION LOG SCREEN just execute you will find the request and double click on that the you will find the log as below.
Mass upsert of markers executed (13781 data records)
you can check the log.
Regards,
Prabhakar.

DTP Delta request for open hub destination.

Hi expert,
As you know, In BW 7.0, open hub destination is used for open hub service, and you can create tranformation/DTP for the destination. and in some case the DTP delta is enabled.
my questions are
1) in the context menu of open hub destination, I did not find something like manage, which could list all the DTP request executed for this open hub destination..but for normal infocube or ods, you can find a list.
2) if the DTP could enable the delta, where can I delete the latest delta request, and have a new load..
3) I assume the DTP could be excuted with batch integrated with process chain by process type 'DTP', right ? if the destination type is third party tool, can it also be integrated with process chain ?
4) can give some obvious difference of InfoSpoke and open hub destination in terms of advantage and disadvantage..
Thanks a lot for the feedback.
Best Regards,
Bin

Hi ,
Please look at the links below . hope it helps .
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d063282b-937d-2b10-d9ae-9f93a7932403?QuickLink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e830a690-0201-0010-ac86-9689620a8bc9?QuickLink=index&overridelayout=true
Regards
Santosh

Is it mandatory to delte all the previous delta request.

Hi Gurus,
I got strucked up with the following issue. Please help
We have two infocubes called regional and global cubes.
We are loading data from regional infocube in to global info cube through delta update.
But the values did not tied up. so I ran the INIT and loaded the data succesfully. Now Is it mandatory to delte all the previous delta request which are already loaded in to the global infocube.

Hi,
You need to delete the data from cube and need to do init accrodingly load the data.
Thanks & Regards,
Ramnaresh.

How is it possible that a target has two deltas requests with the exact sam

HI,
How is it possible that a target has two deltas requests with the exact same records?

Hi Mohammed,
There are couple of reason behind it.
main reason is
take one scenario we have DSO as source and cube as target.
Now DSO contains only 1 request, which i have loaded to cube by using delta.
after that i have deleted DSO content by using right click on it and delete data.
(hope u know that it will not delete request from target automatically)
now once again i have loaded same request from datasource to DSO
and then loaded delta again from DSO to cube.
In this case for 1 single request in DSO you can see 2 request in cube with same data.
Regards,
Ashish

Aggregated delta request

Hi Experts,
In my cube one delta request is aggregated (Rollup).
Is it possible to delete that request.
Thanks
Ajay

Hi..........
Yes,but as shikha already sid u hav to Roll back the request..............because once roll up is done....... data moves from F fact table to E fact table..............in E fact table request numer does'nt exist...............so we cannot delete request..........
So first deactivate the aggregates.........since it is a delta request....don't forget to make the QM status red................to set back the init pointer..............otherwise data will be lost............then delete the request.................after reloading the request............again activate and re-fill the aggregates manually............
Regards,
Debjani........

Erraneous delta request

There is a delta request in the infopackage that I need to delete. I am getting an erraneous delta request message. I want to kill the request. How do I do it? I checked in the scheduler options but I do not see an option for deleting the request. When I click on the stop job (recycle bin icon) i keep getting the same message. I would appreciate a response.

Found out the problem. Delete requests from all data targets first.

Delta Request

I have a delta request that Failed, Do i need to change the QM setting before i can reload it from psa?

Hi,
For delta failures, first you need to change the QM status to RED.
Then delete the request from data targets.
Go for repeating Delta by scheduling the infopak/repeat in process chain.
It asks for repeat of last delta. click on yes.
Now the repeat Delta upload will work fine.

Delete the delta request

Hi BW Experts,
I have a doubt, please make clear it.
Daily delta, first it goes to ODS and then it is updated to further data target i.e, Infocube.
Suppose today (22-09-2007) delta has been running successful in ODS as well as Infocube.
If i delete the 15-09-2007 Request (Which is Delta Request only) from both ODS and Infocube, what will happen?
Is there any problem in ODS and Infocube?
Please give me the reply.
And my Second Question is:
What is the main purpose of DB Statistics.
Thanks in advance.
Regards,
Anjali

hi,
if suppose u r deleting the particular delta request from ods and cube means
data update through that request no will be deleted from both cube and ods.
DB Statistics. it's mainly for OLAP run time analysis, query run time analysis
if helpful provide points
regards
harikrishna.N

Error in loading delta request to ODS

Dear All,
i am not being able to load data from ODS to another ODS and Cube. It is saying "the last delta update was incorrect therefore, no new delta update possible".
i guess i need to delete the old delta update request.
can you all help me. its a bit urgent.

i have done all the possible steps as guided by you all. i am still not being able to load it.
i will tel you my process flow:
i have a process chain which is loading data to source ODS and subsequently to another ODS and Cube.
But there was an errror in loading the data to source ODS today. So i deleted the request from the source ODS and from the other ODS and CUBE.
Now i loaded data to source ODS successfuly. and tried loading data from source ODS to other ODS and CUBE.
But the request ended with errors. so i deleted the request again from target ODS and CUBE.
Now when i m again loading data to target ODS and Cube then it is saying
1) "Delta request REQU_CGSYNH9QR02W5WZOQBDPTHP99 is incorrect in the monitor"
2)A repeat needs to be requested
3)Data target 0CRM_C04 still includes delta request REQU_CGSYNH9QR02W5WZOQBDPTHP99
4)Data target 0CRM_OPMO still includes delta request REQU_CGSYNH9QR02W5WZOQBDPTHP99
5)If the repeat is now loaded, then after the load
6)there could be duplicate data in the data targets
7)Request the repeat?
CONTINUE CANCEL
what do i do now?

CUBE (Delta Request)

Hello,
   Can we delete a delta request from cube
Scenario is
      Delta Request 1    (Loaded on 12/07/06)
      Delta Request 2    (Loaded on 11/07/06)
      Delta Request 3    (Loaded on 10/07/06)
      Delta Request 4    (Loaded on 09/07/06)
      Delta Request 5    (Loaded on 08/07/06)
Can we delete Delta Request 4 from the Cube and the next delta won't be effected
Thanks

Yes this is possible Krishna. The other requests will not be affected, but may be the data will change.
Hope this helps...

Delta Request deletion from info object

Hi,
We are loading 'DELTA's' for master data to an info object.
Last night delta was failed due to idoc error.
how can i delete the delta request from the info object and re do the delta again...
I inserted the info object as data target so that i can get an option of manage on context menu...but when i did that there are no requests show in the manage of info object
how can i delete failed data request from an info object and re do the delta again
Thanks

Hi BW KING,
An infoobject can be a data target and also use direct update. Are you loading using an InfoSource? Check where you have the load infopackage, if it's under an infosource, you can do that. If you have your infopackage under the infoobject "icon" (without update rules), then you don't have the option to manage the loads.
Hope this helps.
Regards,
Diego

Saturday we schedule delta request

HI
Saturday we schedule delta request and monday we come to know that delta request are fail.
how to get back the delta.
THANKS.
ASIM

Hi.......
Is anyone repeat the load without making the QM status red..........otherwise everything is fine...........
Just make the QM status red to set back the Delta pointer........then delete the Bad request from the target............then repeat the Load...........the system will ask u for Repeat Delta.............just go for Repeat delta ..........it will pick all the records that were not picked due to the failed load..............along with that new or changed records(if any)...........
And if u r in BI 7.0............and Delta DTP failed............then just delete the bad request from the target........and again schedule the DTP.......
Regards,
Debjani.............

Delta request compression twice

Similar Messages

Maybe you are looking for