We have to load data from multiple tables(oracle is the db) but there is no join condition between these tables. Let me give you an example
I have 5 columns that needs to loaded into a target table. But the first column (col1) does not have any join conditions between other 4 columns, col2 also does not have a any join condition with other three. But rest columns can be joined(col3,col4,col5). How can the data be loaded. Please advice.
FYI: We are using DS 8.7.UNIX(OS), Oracle(DB)
dataload from multiple tables, there is no join condition
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 36
- Joined: Fri May 21, 2010 12:40 am
- Location: Bangalore
dataload from multiple tables, there is no join condition
Sandeep Chandrashekar
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Where is the specification of what has to be loaded into each target column from each source (the "source to target mapping" document)?
If there is no common column Join would appear to be out of the question unless some kind of common column can be generated.
If there is no common column Join would appear to be out of the question unless some kind of common column can be generated.
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.
-
- Participant
- Posts: 36
- Joined: Fri May 21, 2010 12:40 am
- Location: Bangalore
Target columns to be populated in given in the requirement document. As i said earlier first two columns does not have any join with other three. To make it clear. logic goes like this
source Col1- query table A - load into target col1
source Col2-query table B-load into target col2
source Col3-Query table C-load into target col3
source Col4-Query table D(which has join condition with C)- load into target col4
source Col5-Query table E(which has join condition with D)-load into target col5
source Col1- query table A - load into target col1
source Col2-query table B-load into target col2
source Col3-Query table C-load into target col3
source Col4-Query table D(which has join condition with C)- load into target col4
source Col5-Query table E(which has join condition with D)-load into target col5
Sandeep Chandrashekar
Clear? Go back to whomever produced that specification and ask them how that is supposed to work. Without the join rules documented it is pretty much useless. All you know at this point is (I assume) what D & E records go in the table with a C record. But A & B? Who the heck knows? No-one on this side of the glass.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 36
- Joined: Fri May 21, 2010 12:40 am
- Location: Bangalore
Craig,
yes, always we can go back to System Engineer on this requirement. But let me tell you the same kind of requirement was implemented using Java. There variables was used to store this col1 and col2 values( let me clarify here this col1 and col2 value will be same for that particular load) and this variables were passed into sql queries whil loading the data. Can we do along the same lines using datastage.
yes, always we can go back to System Engineer on this requirement. But let me tell you the same kind of requirement was implemented using Java. There variables was used to store this col1 and col2 values( let me clarify here this col1 and col2 value will be same for that particular load) and this variables were passed into sql queries whil loading the data. Can we do along the same lines using datastage.
Sandeep Chandrashekar
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
Should have clarified that right away. It's an important piece of information.Sandeepch19 wrote:(let me clarify here this col1 and col2 value will be same for that particular load)
Of course, that's what job parameters are for. Or if your queries from the first two tables result in a single value, simply include them in the source SQL.Sandeepch19 also wrote:and this variables were passed into sql queries whil loading the data. Can we do along the same lines using datastage.
All Ray and I have been saying was you needed the rules defined for the relationship between these five tables, the rest is cake.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers