on 04-11-2005 10:25 PM
Hi,
I am trying to load data from one ODS Object(ODS1) to another ODS Object(ODS2) with delta update. I need to delete data in ODS2 before update the delta (to keep only delta update data in ODS2). But if I delete the data in ODS2 it deletes the initalize request and delta can not be updated. Is there any way that we can maintain delta with this scenario.
Thanks in advance,
Ram
Hi Ram,
it sounds too easy...what about a deletion of your init request in ODS2 (after an uploading of your last delta) and, after that, an init without data transfer ?
Hope it helps !
Bye,
Roberto
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ram,
but why do you want (or need) to have an automation in this process ? You have to perform this task (request and init channel deletion and then an init without data transfer) only one-shot ! Once you done that, you can easily manage your delta requests as before (in your already existing process chain)...(otherwise I'm not exactly understand your scenario..)
Hope it helps !
Bye,
Roberto
Roberto,
Ram's idea is to delete data in ODS2 every time new data is coming from ODS 1. The single init doesn't help here because the second delta doesn't delete the first delta. But your idea is right.
Ram, the process chain needs to contain the following steps:
1. Delete data ODS2.
2. Init without data transfer ODS1 -> ODS2
3. Upload data into ODS1.
4. Delta ODS1->ODS2.
Best regards
Dirk
ram,
i have a similar requirement - here's how i'm doing this: i created an extra keyfigure (just a flag) whenever new data is received by ODS1. whenever i transfer data from ODS1 to ODS2, i just use full upload, for all records that has an empty keyfigure flag record. when the record/s are all transferred, i change this flag to some other value (say, 'X'), to indicate that it has already been transferred. that way i can delete my ODS2 every time.
i know this is a cheap trick, but it works for me, so i'm all good with it. if anyone has any negative comments about this, do let me know.
if we've helped, don't forget to kindly give us all points. 😃
ryan.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ram,
I guess the way out is using Selective Deletion...can you use cal day to do this? Or if you do not any definite char by which you can selectively delete, may be you can add a dummy request number characteristic to the ODS and then use its values to delete th eprevious request's data out of the ODS.
Hope this helps...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.