on 12-12-2013 2:41 PM
HIello All,
I wanted to know when we use info package with full update and info package with data transfer?
I have gone through some documents from SCN. I understood following points
1 ) Full load : It brings all the data from the source system.It does not enable the delta.
2) Init with Data transfer : It brings all the data from the source system and it also enables the delta
3) init without data transfer : it does not brings the data from source system once you run the info package .But it will enable delta.
you can run full load first ..then in order to get the delta loads , you need to run Init without data transfer ..
4)Delta ( update tab option in Info package) : By executing this info package , we are able to load the delta records into the bw system.
....
Assume that Data source is Delta enable .. you are running info package first time . On what basis you decide to run info package Full/Init with data transfer..?what is the main difference between them?
Awaiting for your valuable responses..
Thanks Ganesh and Raman both of you for your valuable points...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Raj,
I disagree with Raman, as you simply can't play around with Init with or without data transfer.
Reason is, if you have huge data in the source system and doing an INIT mostly ended up in failure, cos the maximum package size is 20000 KB. I experienced it many times.
In this case, what you have to do is to perform a full load based on specific selections, like you can bring year wise data by giving proper selections in the infopackage. (Splitting data into multiple packages)
Once all the data are pulled to BW, and in order to set delta pointer, you need to perform INIT without data transfer, as all your data are pulled already by FULL LOAD.
Hope this clears.
Br, H
Hi,
Might be, accepted.
As BW consultant if he understand very well about info pack options then he can know which option need to use as per the data volume.
As you said if source have huge data then no one will run init with data.transfer.
Along with data failure, we may have chance to miss newly creating records also. because init with data transfer will take more hours to load data and enable delta.
in case of LO we miss delta records also which are creating in that time.
Thanks
Hi RT,
When the source is delta enable and you want to use delta, you will generally use "2) Init with Data transfer" if it work.
But sometimes the init data is far to large to load, so you will run out of system resources or you don't have enough time to complete in the maintenance window, in this case, you can use "1) Full load" along with selection to split the data to overcome the problem, and after you complete the init data load with "1) Full load", you use "3) init without data transfer" to init the delta. (or vise versa depends on how to freeze the init data)
Wish it help
Regards
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Whatever you understand is perfect..these are the options present in BI system for delta.
Its depend on you which option you want to follow
case 1 you want historical data with delta you can go for any of following option result will be same
a) execute infopackage with option initialize delta with data transfer
b)execute full package then initialize delta without data transfer then delta package
Case 2 you want only delta do not want historical data
a)execute infopackage initialize delta without data transfer then delta package.
Regards,
Ganesh Bothe
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
91 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
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.