Hi All,
With out using funnel ,merge we have to combine two datasets ,by using orc admin utility..
Can anybody tell me solution and in the future we should not get any data issues.
Orcadmin utility
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The solution is to resist stupid requirements.
This is not what the orchadmin utility (note spelling) is intended to do.
Yes, of course, it can be done, but it is going to cost double the volume of data in disk space compared to the volume of data to be merged (a total of three times the volume at one point depending on when you delete the source Data Sets).
This is not what the orchadmin utility (note spelling) is intended to do.
Yes, of course, it can be done, but it is going to cost double the volume of data in disk space compared to the volume of data to be merged (a total of three times the volume at one point depending on when you delete the source Data Sets).
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
From an admin perspective, I would have a strong desire to slap anyone who took that approach. Taking an orchadmin command to merge two datasets. blah If the end result is another dataset, you'd be MUCH better off using the appropriate tools.
I agree with Ray W. Just because it "can" be done, does not mean it "should" be done.
If you are executing on a GRID environment, those orchadmin commands execute on your conductor node. That's not on the grid. The conductor CPU time is a limited resource as compared to your GRID CPU time. Farm of the dataset merge onto your GRID and leave your poor Conductor alone.
I agree with Ray W. Just because it "can" be done, does not mean it "should" be done.
If you are executing on a GRID environment, those orchadmin commands execute on your conductor node. That's not on the grid. The conductor CPU time is a limited resource as compared to your GRID CPU time. Farm of the dataset merge onto your GRID and leave your poor Conductor alone.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: