Two ODSs share the same InfoSource but with different updata mode load?

Question

We've got two different ODSs (ODS1 and ODS2) for two respective clients (client 1 and client 2).  Client 1 has already going alive and in the InfoPackage, we only pick up ODS1 (Client 1) as feeding target and we have conducted initial load and several times of Delta loads for ODS1 (data load daily).  But now we are going to start to load data to ODS2 (Client 2) and at the same time we will have to continue our delta load to ODS1. 
It could not be possible that the two ODSs will be feeded data with different pace (ODS1: continue delta load, ODS2: initial load) if they share the same InfoSource.  Then what's the best way to resolve this issue?
Thanks

Answer 1

hi Pradip,
Tell you a bad news that the solution doesn't work on two of the EBP (a source system which is similar to R3, we've got 4 EBP ODS/InfoSources, but two of the four don't work with the last step listed below) ODSs/InfoSources.  The steps I took on production are:
1. Conduct Full Repair data load to ODS2;
2. Delete init option of ODS1 from Scheduler menu;
3. Run Init without data transfer to set delta pointer for both ODS1 and ODS2.
But the last step to run Init without data transfer has taken 1 whole day and eventually becomes red since it takes so long time to set delta pointer. 
When I said our solution worked is that I conducted the test on our GL ODS and the Init without data transfer took about 1 hour to finish. 
Also when we conduct the last step to do the Init without data transfer to click Start button to set pointer, a msg box titled "Activate ODS Data" pops up saying that "No requests have been selected for activation. Do you want to make a selection, or activate all the requests?" with buttons "Activate all requests", "Select requests" and "Cancel".  If clicking the button "Select requests", another msg box pops up to prompt to input a Date range, we didn't input any date range, just click continue, then the Init without data transfer will run forever!
Thank
Message was edited by: Kevin Smith