hi,
data loaded to from oracle db to seq file and hahsfiles and key columns are column1 and column2. but column2have null data.in the next job joined based on key columns both seq file and hash file but condition not failed even though null values in column2.could you please clarify seq file and hash file how will handle null data ..
hash file lookup
Moderators: chulett, rschirm, roy
hash file lookup
Thanks
REDDY
REDDY
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Firstly, the correct nomenclature is "hashed" file, not "hash" file.
It's perfectly OK for non-key fields to contain NULL, just as it would be in a database join.
The hashed file even allows for part of the key to be null, in a multi-column key. (You may disagree with this, but it's how it works.)
Provided that the fields are marked as nullable, the field value - whether NULL or not - will be transferred to the output link of the Transformer stage where there is a key match.
It's perfectly OK for non-key fields to contain NULL, just as it would be in a database join.
The hashed file even allows for part of the key to be null, in a multi-column key. (You may disagree with this, but it's how it works.)
Provided that the fields are marked as nullable, the field value - whether NULL or not - will be transferred to the output link of the Transformer stage where there is a key match.
Last edited by ray.wurlod on Mon Jul 06, 2015 10:36 pm, edited 1 time in total.
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.
Re: hash file lookup
1. Is it really NULL?vinsashi wrote:but column2have null data.
2. Can you able to query the data in Oracle where col2 is null?
Thanks
Ram
----------------------------------
Revealing your ignorance is fine, because you get a chance to learn.
Ram
----------------------------------
Revealing your ignorance is fine, because you get a chance to learn.
Hi,
below is my sample query. where column2 have null data in both tables. if execute in db no records.
SELECT * FROM table1 a,table2 b
WHERE a.column1=b.columns1
and a.column2=b.column2
same scenario in datastage job its passing records to output.
by using seq file and hashed file. its ignoring column2 join.
below is my sample query. where column2 have null data in both tables. if execute in db no records.
SELECT * FROM table1 a,table2 b
WHERE a.column1=b.columns1
and a.column2=b.column2
same scenario in datastage job its passing records to output.
by using seq file and hashed file. its ignoring column2 join.
Thanks
REDDY
REDDY