Delta Init DTP DSO- Cube loads all requests

Hi,
i've loaded several Full Request to a DSO (Datasource 2LIS_02_ITM).
I had to to fragment it to 3 months per Full load because otherwise the data volume was too much for the rollback segment.
Now i want to load these requests from the DSO to a Cube.
I created a Delta DTP and selected the "All new data by request" option.
The DTP starts as a Delta Init but selects all open requests at once and crashes with a "ORA-01555: snapshot too old..." error.
As a workaround i created several Full DTPs that only load part of the data but i really want to understand why the Delta Init doesn't work as expected and documented (to load request by request in a new process).
thanks
Carsten

Hemant Khemani wrote:>
> Please check if you have selected the option "Get All New Data Request by Request" in the Delta DTP.
> If you have selected this option then the delta DTP will select only one request (oldest - yet to be updated to the target) from the DSO.
That's the option i've selected.
When monitoring the DTP-Request i see in the head data that all requests from the DSO are selected at once.

Similar Messages

What happend to past delta data if we delete Delta INIT from Cube? safe ?

Hi Friends,
we have a cube where delta data is loaded daily from ODS.
So, cube have many delta requests and data is compressed.
Now have some problem and need to delete Delta INIT from this Cube and run fresh delta INIT again into Cube from ODS. Is that safe ?
If we do this...is there is any problem with past delta data availble in the Cube?
Please confirm..
Thanks
Tony

Hi,
I told you to check this before deleting the init as it very tough to manage it after that.
Now those delta request are missed and I dont think can be retrieved without doing a full repair with proper selection.
If you do a new init then there should be no request without a check for data mart status??
So you found it before deleting the init??Then you should not have deleted the init as I told earlier.
The only option is too reload the whole histroy again if you are not able to load it through selections in infopackage.
First do a selective deletion from the cube for the same selections and then schedule the full load for those selections from DSO.make sure these selections cover the whole scenario.
You cannot do anything else now to correct it.
If you data is not huge in cube then delete the whole data and reload it.
Schedule multiple loads from the DSO at the same time through different infopackages.
this will save time as weill will do the loads in quick time.
Thanks
Ajeet

Re-init of POS cube

Hello,
Should it not be possible to delete all data in a standard POS retail cube, delete the init request setting in data package, delete the delta queue AND THEN perform a new delta init?
This delta init should then pick up all data from the extraction queue..
Am I right?
I have problems with this re-init...
Best regards,
Fredrik

Hi Fredrik,
Yes it is possible to delete the Init request from the POS Retail cube and Intialization for source system in infopackagea also call the transaction RSA7 in your source system and delete the corresponding DataSource's delta queue for the relevant BW system.After that you must request the data again in the DeltaInit mode from BW.
Hope it helps...
Best Regards,
DMK
*Assign points if it helps...

Need of Change log deletion for a DSO, when DTP delta Init with Active Tabl

Hi,
Thanks for your time, please help me with the following
Scenario: I have Cube1 being updated from DSO1 with DTP delta, for quite some time. As per new requirement, I would need to create new data mart such that Cube2 gets updated from DSO1.
In order to Configure the delta, I am Considering Following options, please let me know, which one is right one.
Note: DSO1 is in Overwrite Mode.
Create one DTP with update Mode "Delta" , and "Active Table". I knew Delta Changes are captured in change log, but my understanding is, when you execute the DTP for the First time, it fetches the records from Active Table. And from 2nd Run onwards the very "same DTP" without "any changes" get the records from change log, even if we choose "Active Table".
is my understanding is Right?
Do I have to consider deleting the change log, because DSO1 is in Production from quite some time which is in Overwrite mode?
Do I have to create a DTP with Delta and Active Table, run the dtp Once(Init), then choose "Change Log for subsequent runs explicitly
please help me with these. I have reviewed many sap help articles and sdn threads but none of them were helpful. all of them explains, difference b/w active table and change log table, also gives scenarios like use a full DTP and then 2nd DTP with Delta without Data transfer. I am not looking for that kind of details.
Appreciate any help, Thanks again
Edited by: curious maven on Mar 28, 2011 8:35 AM

Hi Uma,
Thanks for your response.
to your question, If I need to load all the data from DSO1 to Cube1, answer is NO. if you read my post once again,
Existing Flow is : DSO1 --> Cube1 (Means, Active Table and Change Logs of DSO1 already Filled Up)
Requirement is: DSO1 --> Cube2. (Need to Init the Delta, and Detlas going forward)
My Questions:
(1) Imagine, DSO1 has 10 requests, so we see resepctive data in Active Table as well as Change Log. As a matter of fact, Data is being updated to DSO1 in Overwrite Mode, so all the changes(10 requests equivalent) would be captured in Change Log, which in turn helpful / used when we do Delta from DSO1 to any Cube, in my case, it used to update to Cube1. As per new requirement, it needs to update to Cube2.
My assumption is, if I choose "Active table and Delta in Extraction Tab" in DTP, During First Run (Delta Init), Data would be fethed from Active table. And the 2nd Run Onwards, delta records would be fetehced from Change Log automatically, even if we don't change the selection from Active Table to Change Log.
Is My Assumption Right?,
in this process, Do I have to Delete Change Log
(2) Do I have to Explicitly change DTP setting from "Active Table to Change Log" Once Delta Init has been run with setting "Active table" inorder to get Deltas from DSO1 --> Cube2 ?
Appreciate your help
Edited by: curious maven on Mar 30, 2011 3:14 PM
Edited by: curious maven on Mar 30, 2011 3:29 PM

Deleting failed request from DSO leading to delete of INIT of DSO to Cube

data flows from ds1, ds2 and ds3 to dso1 as delta. the data is then taken from dso1 to cube1 via delta
data flows from ds3 to dso2 as delta. the data is then taken from dso2 to cube 2 via delta.
when a data is loaded from ds1 or ds2 or ds3 to dso1.. or when data is loaded from ds3 to dso2.. now if we try to delete this un activiated request from lets say dso1. it gives and error that the init from dso1 to cube1 would be deleted as the data has already been data marted.
this happens even if the request in dso1 is inactive successful or inactive failed.
i did an init of ds1,ds2, ds3 to dso1. and also did an init from dso1 to cube1. but the problem persists.
though if all goes good. like no failures in the load, then all is well.
but if the load failed. say ds2 to dso1 failed. then when we attempt to delete this request from dso1, it says that it has already been uploaded to cube1 and the init will have to be deleted. here when we checked the datamart sign in dso1, it looks like the newly loaded n unactivated data is somehow assosiated with the dso1tocube1 init.
any thoughts?

Please give more info.
How have you connected DS01 and Cube 1? Transformation or update rules? How have you done the initialization?
What is the version SAP BW that you are using?
Have you checked any relevant SAP Notes?
Thanks,
Krishnan

Delete overlapping requests of same DTP from cube

Dear All,
i want to delete over lapping requests of same DTP in cube, but here while i am searching for the DTP in process variant, the system is not showing the DTP(it is active).
can you people have any suggestions.
Br,
Vamshi.

Hey Vamshi,
Is your DTP a full one or delta one ? Delete Overlapping reqs is not possible for Delta loads.
In Load Process and Post-Processing option you will find Delete Overlapping Requests from InfoCube, drag and drop and make the following settings:
Object Type = DTP
Object Name : DTP Name.
Check Edit all InfoCubes with the following Delete Selections and click on Delection Selection
Check Delete Existing Request and check Only Delete Req from same DTP
Activate and execute the PC.
Hope this helps!
Sheen

Question on Delta Init Loads

Hi All,
I have a basic question on Delta Inits. I am a beginner in BW and would truly appreciate any input.
At my company, we currently are doing delta loads on the cube 0RT_C35 (Material Movements). They did the Delta Inits prior to that.
Now if we were to add new fields to the cube and need to populate data to the new fields from the beggining, how do I go about doing it..?
Should I delete the Delta Init requests and redo the Delta Inits..? What will happen to the Delta loads that are running daily then..?
Can someone please give me the steps that I need to follow in a sequence.
Like I said, it might be a basic question..but I am not familiar with this process.
Appreciate your help.

Thank You very much Ravi.
I will not be doing it today based on the priority of the tasks..but this is something I will have to do eventually in the next 1-2 weeks. I will definitely let you know how it goes.
So once the mapping and everything is in place and is ready to be loaded, bascially I need to delete data from the datatarget, put the delta job on hold, reinit the delta requests and then I should be able to do the delta jobs again right..?
Thank You so much.
The other issue is that there are probably 25 Delta inits that they did based on the number range for the Material Nbr. But they have only 1 delta. So does the delta job cover the data for all the Delta Init requests..?
I am assigning full points to you for being such a great help. I will let you know when I actually end up doing this.
I will assign the remaining points when I close the request.
Thanks again

Process Chain Steps to upload into teh Cube for delta init

Hi All,
I have all the delta init info package in my Process chain for all the DSO themn i have DSO ACtivation step and third is Furhter Processing....
It ran Ok for all the DSO but it Did not update the data into the Infocubes... Also all my DSO setting is Update data into the data target,,, >> Set the status to ok automatically..
Plz let em know what i am missing ...
Thank you

Create a info package for the DSO to Cube by going to the 8 Datasource and load the data.
From the time you start delta you should not face any issues.
-Vikram

How to do delta loading again based on delta init time?

Hi experts,
   in my case, I have delta init (2000 - 9999) which successed on 3.1 (it's huge data and time consuming) after that, we have delta loading per day.
   unfortunately, we do some wrong process when we get delta failed, it's cause some data missing in BW.
   3.5   delta success
   3.4   delta fail, do right delta correction (repeat delta)
   3.3   delta fail, do wrong delta correction
   3.2   delta success
   3.1   delta init success
   in this case, we miss some records in 3.3 's request. if I going to fix this problem, formal way it should do delta init again then schedule daily delta. but since delta init is successful and need lot of time.
can I advoid do delta init again?? just do delta again base on delta init (3.1) ??
   thanks in advanced

Hi jie,
Whenver you incur a Failure when data is being loaded from R/3 systems to BW via DELTA. It means that the Records were not transferred during that load to BW from R/3.
Hence the next load is always a REPEAT DELTA.
It may happen at times that you may miss few records in this.
If so, then in that case do a repair request from infopackage scheduler and then load the missed records.
Then again start off with Delta and loads should not have any problems.
Else you need to do a Re-Init of Delta. And re - do all over again.
Cause every time we miss the records we need to bring them in via repair request.
Hope this helps.
Thanks,
Pradip Parmar

DTPs - Delta Init without Data transfer.

Hi All,
I am implementing the DTPs in my project where we replicate the old 3.x extractions with the bw7x functioanlity;
Can anyone tell me if their is way to implement the "Delta Init without Data transfer" scenario with DTPs for
both R/3 to BW(ODS) extraction or for the Datamarts - ODS to Cube within BW??
Thanks in advance!
Cheers
Rao

Hi Rao,
Yes u can achieve Initialization without data in BI 7 DTPs.
Goto ur DTp's Execute Tab, and Processing mode there drop down the list and select No Data Transfer,Delta Status in Source: Fetched.
Assign points if helpful.

Not Able to Load the Request in Target DSO

Hi,
we haddone reinitialiazation of the source system.. after that we did Init without data transfer to the target's.
After succesful init,we are doing Full Repiar Request to load the data into the Purchaisn DSO.It has around 15140000 records are there. we are loading targets with particular selection condition.
Now data has extracted from the source system and is there available ib PSA.but while loading to Target its not allowing to load the data in the targets.
We are getting the Folowing Error.
"Full 2,933,864 has overlapping selections with init. 0002933848: No updates into 0PUR_O01"
But we dont have any selection condition for the init load.
suggest me how to approach this issue...

Just a thought - I am not hungry for points.. but for new comer it would matter a lot....you should assign points for relevant reply ..thats way to say thank you here in SDN...
And if your question has been replied..please close the thread by markin it as answered...
Regards
--SA

Loading JSP Request Object on Application Init

Background:
I've been searching for close to two days for an answer to this question, it's full of gotchas and I can't quite get it figured out.
I have an application which contains several web services. These services load up listeners when the services are invoked which makes them available for input. The user has the option of disabling automatic load of these services and invoking them manually by typing in the local url and starting the app. The can allow the autoload which uses a the or allowing the auto load to start. Currently the local url is hardcoded in a property file and this is how the services knows the local endpoint to envoke when it autostarts.
     <servlet id="AutoStart_01">
     <servlet-name>autoStart</servlet-name>
     <servlet-class>com.loadmy.StartupClass.Here</servlet-class>
          <load-on-startup>1</load-on-startup>
     </servlet>
This works all fine and well until it's deployed onto a machine that runs a local weblogic cluster that has more than one jvm (and multiple ports) loading the application up.
Problem
The question is, how can you get the applicaton to recoginize the local url for the jvm that is running which can be on different ports? Here's what I've tried
A - Using Inet.Address - This doesn't let you know what port your application is on
B - Using the load servlet on start up ( Only the init() function is called and the request object hasn't been created and the request object is what contains ther protocol, server and port information)
C - Loading a jsp page (READ... purposefully loading a jsp page) on application start. The thought here is that this contains a request object, but unfortunately on this doesn't work in my servlet container (currently tomcat 6 but the application is for a web logic machine)
D - I thought about possibly using System.properties() but no luck there
I'm at witts end on this one and I know there is something that can recoginze the local servlet container and extract the url and port from it.
Any suggestions would be great.
Flabergasted [sic]

When you request from jsp1 comes to jsp2, it gets the request object.
Now if you want to pass the same request object ot next jsp3, then please call the forward(request, response) as below:
<jsp:forward page="jsp3.jsp">
//This will forward the same request, response object which is there in jsp2

Dtp error when loading data from one cube to another cube?

hi,experts
it seems strange that when I tick the some characteristics as navigational attributes in the cube , the error occurs during the execution of the DTP:error while updating to target Z* (Cube name ).
once i turn the flag off , no error appear. could anyone give me a clue ?
thanks in advance!

Hi,
When u make changes in the cube u need to make necessary changes in Transformation and activate the DTP.The checking of Navigational attributes in cube will appear in u r transformation as new fields where u need to create a mapping for them and then activate, also activate your DTP and then load the data. This should resolve your issue.
Regards

Table or view with the request status of all requests in a cube

Dear all,
I search the table or view which is used by Cube / Manage -> InfoProvider Administration (Requests).
Target is to get all status information of all requests started by one InfoPackage.
I found several tables alone but no view. I have currently
RSREQICODS, RSMDATASTATE, RSSELDONE.
Best regards.

I've found a solution for the problem:
*    Select all requests for one Infopackage
      SELECT distinct RNR from rsseldone into table ta_done where LOGDPID = IPak.
      LOOP AT ta_done
        INTO wa_done.
        WRITE: / 'Request: ', wa_done-RNR.
*       Select the maximum Request Number in the Cube
        SELECT SINGLE ICUBE RNSIDLAST from RSICCONT Into wa_cont where RNR = wa_done-RNR.
        WRITE: / 'Icube: ', wa_cont-ICUBE.
        WRITE: / 'Max: ', wa_cont-RNSIDLAST.
*       Check the Maximum Request with status technical and quality ok
        SELECT TECHOK QUALOK from RSMDATASTATE into table ta_state where INFOCUBE = wa_cont-ICUBE.
        LOOP AT ta_state INTO wa_state.
            WRITE: / 'ID TECHOK: ', wa_state-TECHOK.
            WRITE: / 'ID QUALOK: ', wa_state-QUALOK.
            IF wa_state-TECHOK > l_maxid AND wa_state-QUALOK > l_maxokid AND wa_state-QUALOK = wa_state-TECHOK.
               l_maxokid = wa_state-TECHOK.
            ENDIF.
        ENDLOOP.
        IF wa_cont-RNSIDLAST > l_maxokid OR wa_cont-RNSIDLAST = 0.
          WRITE: / 'Request is running with Request: ', wa_cont-RNSIDLAST.
        ELSE.
          WRITE: / 'all Green'.
          l_cont = 0.
        ENDIF.
     ENDLOOP.

DTP is not running by request by request?

Hi ,
Am loading data from DSO - > cube , by DTP which setting as extraction mode as Get all new data request by request.
In actual scenario i collected around 7 requests of data in DSO, so by functionality of Cube DTP setting Get all new data request by request when i run DTP ideally it should come as request by request to target cube, but in my case all requests are collecting in one request.
so what will be the reason of behaving like this?
cheers
vas

Hi,
The option(GET ALL NEW DATA Request by Request)which you mentioned work as delta only. for more details follows as bellow:
This indicator belongs to a data transfer process (DTP) that gets data from a DataSource or InfoPackage in delta mode. To prevent DTP requests from becoming too large (when the source contains a large amount of data) to be sent to the target as one DTP request, delta DTPs can be used to get the data request by request.
USE:
If you set this indicator, a DTP request only gets data from one request in the source.
When it completes processing, the DTP request checks whether the source contains any further new requests. If the source contains more requests, a new DTP request is automatically generated and processed.
Regards,
Suman

Delta Init DTP DSO- Cube loads all requests

Similar Messages

Maybe you are looking for